sandweb-users

[Sandweb-users] Re: Sandweb repository issues

[Robert H. <ro...@ro...>]

Hi Alainna,


No worries. I prefer if people mail the sandweb-users list so that
problems/resolutions can be shared.

Maybe I am confused about what you are saying, but I think you
are not clear on how CVS works.. (see http://cvshome.org)

In CVS, each user makes a private checkout (aka "sandbox") and modifies
their work in there. When they are done, they attempt to check in
to the main repository ("/cvs_root").

If someone else has checked in to the same file before them, they
get a notification and CVS attempts to merge the changes. If the
merge fails, the user gets a conflict notification and merges
the changes themselves, then attempts to check in again.

Noone should ever be modifying anything in /cvs_root directly; you
need to go through CVS.



Hope that helps,
Rob Helmer



On Tue, Jun 22, 2004 at 02:22:39PM -0400, Alainna C. Wonders wrote:
> Hi Robert,
> 
> I got your email address off of your website; I hope you don't mind.
> 
> We're having some serious difficulties with the repository.  It seems
> that when we configure the repository section in Sandweb as such below: 
> 
> Name: CVSROOT
> Server hostname: localhost
> Username: awonders
> Vcs type: cvs 
> Connection: local
> Root: /cvs_root/
> 
> It will create /usr/local/share/sandweb/users/username/cvs_root/$files.
> 
> We need sandweb to point EVERYone to /cvs_root so they can share their
> development files.
> 
> I tried to symlink (probably a major no-no) all of the user directories
> to /cvs_root/ and gave it all the permissions of apache:cvsusers, and
> got a little further but no where near where we need to be.  
> 
> I'm hoping that I'm just screwing up and not doing it right.  Any help
> you can offer, I'd really appreciate.
> 
> Thanks Robert. 
> 
> 
> Alainna C. Wonders
> Jr. Systems Administrator, ISSO
> Applied Hydro-Acoustic Research, Inc.
> Voice: 703-968-6129 
> Email: awo...@ah...
> 
> 
> 

[Sandweb-users] Re: Sandweb repository issues

[Robert H. <ro...@ro...>]

In SandWeb, click on the module name to get to the "browse module" menu.
You should see a pulldown select form that has a "commit" option on it.


--
Rob


On Tue, Jun 22, 2004 at 02:31:46PM -0400, Alainna C. Wonders wrote:
> So how would one check in files after editing them? 
> 
> 
> -----Original Message-----
> From: Robert Helmer [mailto:ro...@ro...] 
> Sent: Tuesday, June 22, 2004 2:43 PM
> To: Alainna C. Wonders
> Cc: san...@li...
> Subject: Re: Sandweb repository issues
> 
> 
> Hi Alainna,
> 
> 
> No worries. I prefer if people mail the sandweb-users list so that
> problems/resolutions can be shared.
> 
> Maybe I am confused about what you are saying, but I think you are not
> clear on how CVS works.. (see http://cvshome.org)
> 
> In CVS, each user makes a private checkout (aka "sandbox") and modifies
> their work in there. When they are done, they attempt to check in to the
> main repository ("/cvs_root").
> 
> If someone else has checked in to the same file before them, they get a
> notification and CVS attempts to merge the changes. If the merge fails,
> the user gets a conflict notification and merges the changes themselves,
> then attempts to check in again.
> 
> Noone should ever be modifying anything in /cvs_root directly; you need
> to go through CVS.
> 
> 
> 
> Hope that helps,
> Rob Helmer
> 
> 
> 
> On Tue, Jun 22, 2004 at 02:22:39PM -0400, Alainna C. Wonders wrote:
> > Hi Robert,
> > 
> > I got your email address off of your website; I hope you don't mind.
> > 
> > We're having some serious difficulties with the repository.  It seems 
> > that when we configure the repository section in Sandweb as such 
> > below:
> > 
> > Name: CVSROOT
> > Server hostname: localhost
> > Username: awonders
> > Vcs type: cvs
> > Connection: local
> > Root: /cvs_root/
> > 
> > It will create 
> > /usr/local/share/sandweb/users/username/cvs_root/$files.
> > 
> > We need sandweb to point EVERYone to /cvs_root so they can share their
> 
> > development files.
> > 
> > I tried to symlink (probably a major no-no) all of the user 
> > directories to /cvs_root/ and gave it all the permissions of 
> > apache:cvsusers, and got a little further but no where near where we
> need to be.
> > 
> > I'm hoping that I'm just screwing up and not doing it right.  Any help
> 
> > you can offer, I'd really appreciate.
> > 
> > Thanks Robert.
> > 
> > 
> > Alainna C. Wonders
> > Jr. Systems Administrator, ISSO
> > Applied Hydro-Acoustic Research, Inc.
> > Voice: 703-968-6129
> > Email: awo...@ah...
> > 
> > 
> > 
> 
> 
> 

[Sandweb-users] RE: Sandweb repository issues

[Alainna C. W. <awo...@ah...>]

I think the issue is when I specify the parameters as such: 

Name: cvsroot
Server hostname: localhost
Username: awonders
Vcs type: cvs
Connection: local
Root: /cvs_root/

It isn't seeing the modules (I've already imported two).  

This means I can't check out anything. 


-----Original Message-----
From: Robert Helmer [mailto:ro...@ro...] 
Sent: Tuesday, June 22, 2004 2:54 PM
To: Alainna C. Wonders
Cc: san...@li...
Subject: Re: Sandweb repository issues


In SandWeb, click on the module name to get to the "browse module" menu.
You should see a pulldown select form that has a "commit" option on it.


--
Rob


On Tue, Jun 22, 2004 at 02:31:46PM -0400, Alainna C. Wonders wrote:
> So how would one check in files after editing them?
> 
> 
> -----Original Message-----
> From: Robert Helmer [mailto:ro...@ro...]
> Sent: Tuesday, June 22, 2004 2:43 PM
> To: Alainna C. Wonders
> Cc: san...@li...
> Subject: Re: Sandweb repository issues
> 
> 
> Hi Alainna,
> 
> 
> No worries. I prefer if people mail the sandweb-users list so that 
> problems/resolutions can be shared.
> 
> Maybe I am confused about what you are saying, but I think you are not

> clear on how CVS works.. (see http://cvshome.org)
> 
> In CVS, each user makes a private checkout (aka "sandbox") and 
> modifies their work in there. When they are done, they attempt to 
> check in to the main repository ("/cvs_root").
> 
> If someone else has checked in to the same file before them, they get 
> a notification and CVS attempts to merge the changes. If the merge 
> fails, the user gets a conflict notification and merges the changes 
> themselves, then attempts to check in again.
> 
> Noone should ever be modifying anything in /cvs_root directly; you 
> need to go through CVS.
> 
> 
> 
> Hope that helps,
> Rob Helmer
> 
> 
> 
> On Tue, Jun 22, 2004 at 02:22:39PM -0400, Alainna C. Wonders wrote:
> > Hi Robert,
> > 
> > I got your email address off of your website; I hope you don't mind.
> > 
> > We're having some serious difficulties with the repository.  It 
> > seems
> > that when we configure the repository section in Sandweb as such 
> > below:
> > 
> > Name: CVSROOT
> > Server hostname: localhost
> > Username: awonders
> > Vcs type: cvs
> > Connection: local
> > Root: /cvs_root/
> > 
> > It will create
> > /usr/local/share/sandweb/users/username/cvs_root/$files.
> > 
> > We need sandweb to point EVERYone to /cvs_root so they can share 
> > their
> 
> > development files.
> > 
> > I tried to symlink (probably a major no-no) all of the user
> > directories to /cvs_root/ and gave it all the permissions of 
> > apache:cvsusers, and got a little further but no where near where we
> need to be.
> > 
> > I'm hoping that I'm just screwing up and not doing it right.  Any 
> > help
> 
> > you can offer, I'd really appreciate.
> > 
> > Thanks Robert.
> > 
> > 
> > Alainna C. Wonders
> > Jr. Systems Administrator, ISSO
> > Applied Hydro-Acoustic Research, Inc.
> > Voice: 703-968-6129
> > Email: awo...@ah...
> > 
> > 
> > 
> 
> 
> 

[Sandweb-users] RE: Sandweb repository issues

[Robert H. <ro...@ro...>]

Sorry I missed this email from you.

You need to specify which module you want to checkout in the "sandbox" 
menu, SandWeb doesn't list them otherwise (more a limitation of CVS than 
SandWeb unfortunately).


On Tue, 22 Jun 2004 12:12pm, Alainna C. Wonders wrote:
> I think the issue is when I specify the parameters as such:
>
> Name: cvsroot
> Server hostname: localhost
> Username: awonders
> Vcs type: cvs
> Connection: local
> Root: /cvs_root/
>
> It isn't seeing the modules (I've already imported two).
>
> This means I can't check out anything.
>
>
> -----Original Message-----
> From: Robert Helmer [mailto:ro...@ro...]
> Sent: Tuesday, June 22, 2004 2:54 PM
> To: Alainna C. Wonders
> Cc: san...@li...
> Subject: Re: Sandweb repository issues
>
>
> In SandWeb, click on the module name to get to the "browse module" 
> menu.
> You should see a pulldown select form that has a "commit" option on it.
>
>
> --
> Rob
>
>
> On Tue, Jun 22, 2004 at 02:31:46PM -0400, Alainna C. Wonders wrote:
>>  So how would one check in files after editing them?
>>
>>
>>  -----Original Message-----
>>  From: Robert Helmer [mailto:ro...@ro...]
>>  Sent: Tuesday, June 22, 2004 2:43 PM
>>  To: Alainna C. Wonders
>>  Cc: san...@li...
>>  Subject: Re: Sandweb repository issues
>>
>>
>>  Hi Alainna,
>>
>>
>>  No worries. I prefer if people mail the sandweb-users list so that
>>  problems/resolutions can be shared.
>>
>>  Maybe I am confused about what you are saying, but I think you are not
>
>>  clear on how CVS works.. (see http://cvshome.org)
>>
>>  In CVS, each user makes a private checkout (aka "sandbox") and
>>  modifies their work in there. When they are done, they attempt to
>>  check in to the main repository ("/cvs_root").
>>
>>  If someone else has checked in to the same file before them, they get
>>  a notification and CVS attempts to merge the changes. If the merge
>>  fails, the user gets a conflict notification and merges the changes
>>  themselves, then attempts to check in again.
>>
>>  Noone should ever be modifying anything in /cvs_root directly; you
>>  need to go through CVS.
>>
>>
>>
>>  Hope that helps,
>>  Rob Helmer
>>
>>
>>
>>  On Tue, Jun 22, 2004 at 02:22:39PM -0400, Alainna C. Wonders wrote:
>>  > Hi Robert,
>>  >
>>  > I got your email address off of your website; I hope you don't mind.
>>  >
>>  > We're having some serious difficulties with the repository.  It
>>  > seems
>>  > that when we configure the repository section in Sandweb as such
>>  > below:
>>  >
>>  > Name: CVSROOT
>>  > Server hostname: localhost
>>  > Username: awonders
>>  > Vcs type: cvs
>>  > Connection: local
>>  > Root: /cvs_root/
>>  >
>>  > It will create
>>  > /usr/local/share/sandweb/users/username/cvs_root/$files.
>>  >
>>  > We need sandweb to point EVERYone to /cvs_root so they can share
>>  > their
>>
>>  > development files.
>>  >
>>  > I tried to symlink (probably a major no-no) all of the user
>>  > directories to /cvs_root/ and gave it all the permissions of
>>  > apache:cvsusers, and got a little further but no where near where we
>>  need to be.
>>  >
>>  > I'm hoping that I'm just screwing up and not doing it right.  Any
>>  > help
>>
>>  > you can offer, I'd really appreciate.
>>  >
>>  > Thanks Robert.
>>  >
>>  >
>>  > Alainna C. Wonders
>>  > Jr. Systems Administrator, ISSO
>>  > Applied Hydro-Acoustic Research, Inc.
>>  > Voice: 703-968-6129
>>  > Email: awo...@ah...
>>  >
>>  >
>>  >
>>
>>
>>

Re: [Sandweb-users] RE: Sandweb repository issues

[Robert H. <rh...@cu...>]

Great :)

Now to check in, click on the module name (linked from the sandbox 
menu under the "Module name" column).  You should see a list of files 
in your checkout. 

Modify one or more of them, by uploading over or editing the existing
files (you can edit by clicking on the file, and then clicking "edit").

Pull down the "CVS Command" menu and select "commit". Press the "Go"
button. 




On Tue, Jun 22, 2004 at 03:49:41PM -0400, Alainna C. Wonders wrote:
> Okay, excellent, I figured out how to check out.  Now how do I check in?
> 
> 
> :) 
> 
> Thanks!
> Alainna
> 
> -----Original Message-----
> From: san...@li...
> [mailto:san...@li...] On Behalf Of Robert
> Helmer
> Sent: Tuesday, June 22, 2004 3:43 PM
> To: Alainna C. Wonders
> Cc: san...@li...
> Subject: [Sandweb-users] RE: Sandweb repository issues
> 
> 
> Sorry I missed this email from you.
> 
> You need to specify which module you want to checkout in the "sandbox" 
> menu, SandWeb doesn't list them otherwise (more a limitation of CVS than
> 
> SandWeb unfortunately).
> 
> 
> On Tue, 22 Jun 2004 12:12pm, Alainna C. Wonders wrote:
> > I think the issue is when I specify the parameters as such:
> >
> > Name: cvsroot
> > Server hostname: localhost
> > Username: awonders
> > Vcs type: cvs
> > Connection: local
> > Root: /cvs_root/
> >
> > It isn't seeing the modules (I've already imported two).
> >
> > This means I can't check out anything.
> >
> >
> > -----Original Message-----
> > From: Robert Helmer [mailto:ro...@ro...]
> > Sent: Tuesday, June 22, 2004 2:54 PM
> > To: Alainna C. Wonders
> > Cc: san...@li...
> > Subject: Re: Sandweb repository issues
> >
> >
> > In SandWeb, click on the module name to get to the "browse module"
> > menu.
> > You should see a pulldown select form that has a "commit" option on
> it.
> >
> >
> > --
> > Rob
> >
> >
> > On Tue, Jun 22, 2004 at 02:31:46PM -0400, Alainna C. Wonders wrote:
> >>  So how would one check in files after editing them?
> >>
> >>
> >>  -----Original Message-----
> >>  From: Robert Helmer [mailto:ro...@ro...]
> >>  Sent: Tuesday, June 22, 2004 2:43 PM
> >>  To: Alainna C. Wonders
> >>  Cc: san...@li...
> >>  Subject: Re: Sandweb repository issues
> >>
> >>
> >>  Hi Alainna,
> >>
> >>
> >>  No worries. I prefer if people mail the sandweb-users list so that  
> >> problems/resolutions can be shared.
> >>
> >>  Maybe I am confused about what you are saying, but I think you are 
> >> not
> >
> >>  clear on how CVS works.. (see http://cvshome.org)
> >>
> >>  In CVS, each user makes a private checkout (aka "sandbox") and  
> >> modifies their work in there. When they are done, they attempt to  
> >> check in to the main repository ("/cvs_root").
> >>
> >>  If someone else has checked in to the same file before them, they 
> >> get  a notification and CVS attempts to merge the changes. If the 
> >> merge  fails, the user gets a conflict notification and merges the 
> >> changes  themselves, then attempts to check in again.
> >>
> >>  Noone should ever be modifying anything in /cvs_root directly; you  
> >> need to go through CVS.
> >>
> >>
> >>
> >>  Hope that helps,
> >>  Rob Helmer
> >>
> >>
> >>
> >>  On Tue, Jun 22, 2004 at 02:22:39PM -0400, Alainna C. Wonders wrote:
> 
> >> > Hi Robert,  >
> >>  > I got your email address off of your website; I hope you don't
> mind.
> >>  >
> >>  > We're having some serious difficulties with the repository.  It
> >>  > seems
> >>  > that when we configure the repository section in Sandweb as such
> >>  > below:
> >>  >
> >>  > Name: CVSROOT
> >>  > Server hostname: localhost
> >>  > Username: awonders
> >>  > Vcs type: cvs
> >>  > Connection: local
> >>  > Root: /cvs_root/
> >>  >
> >>  > It will create
> >>  > /usr/local/share/sandweb/users/username/cvs_root/$files.
> >>  >
> >>  > We need sandweb to point EVERYone to /cvs_root so they can share
> >>  > their
> >>
> >>  > development files.
> >>  >
> >>  > I tried to symlink (probably a major no-no) all of the user  > 
> >> directories to /cvs_root/ and gave it all the permissions of  > 
> >> apache:cvsusers, and got a little further but no where near where we
> 
> >> need to be.  >
> >>  > I'm hoping that I'm just screwing up and not doing it right.  Any
> >>  > help
> >>
> >>  > you can offer, I'd really appreciate.
> >>  >
> >>  > Thanks Robert.
> >>  >
> >>  >
> >>  > Alainna C. Wonders
> >>  > Jr. Systems Administrator, ISSO
> >>  > Applied Hydro-Acoustic Research, Inc.
> >>  > Voice: 703-968-6129
> >>  > Email: awo...@ah...
> >>  >
> >>  >
> >>  >
> >>
> >>
> >>
> 
> 
> -------------------------------------------------------
> This SF.Net email sponsored by Black Hat Briefings & Training. Attend
> Black Hat Briefings & Training, Las Vegas July 24-29 - 
> digital self defense, top technical experts, no vendor pitches, 
> unmatched networking opportunities. Visit www.blackhat.com
> _______________________________________________
> Sandweb-users mailing list
> San...@li...
> https://lists.sourceforge.net/lists/listinfo/sandweb-users
> 
> 
> 

[Sandweb-users] Sandweb Repository Issues

[Alainna C. W. <awo...@ah...>]

Okay, I've got a couple things straight, unfortunately I still am at a
loss for what is happening here...

I specify the following parameters for the repository: 

Name: CVSROOT
Server hostname: localhost
Username: awonders
Vcs type: CVS
Connection: local
Root: /cvs_root/

When I key in a module (specifically aspl_scripts) it says it can't find
the module (but it DOES exist in CVS; I did add it through the command
line).  So I try to update it and this is what I get: 

cvs update: cannot open CVS/Entries for reading: No such file or
directory
cvs update: nothing known about aspl_scripts
cvs [update aborted]: cannot open CVS/Root: No such file or directory

What is CVS/Entries and CVS/Root?  I haven't specified those anywhere.  

Thanks!

Alainna

Re: [Sandweb-users] Sandweb Repository Issues

[Robert H. <ro...@ro...>]

Hi Alainna,


Are you able to check out this module using the command line, e.g.:

cvs -d /cvs_root co aspl_scripts


"CVS/Entries" and "CVS/Root" appear inside a valid checkout. 
CVS uses "CVS" subdirectories inside a checkout to keep state on
what is happening in the checkout, to compare against the repository.



--
Rob


On Wed, Jun 23, 2004 at 08:53:31AM -0400, Alainna C. Wonders wrote:
> Okay, I've got a couple things straight, unfortunately I still am at a
> loss for what is happening here...
> 
> I specify the following parameters for the repository: 
> 
> Name: CVSROOT
> Server hostname: localhost
> Username: awonders
> Vcs type: CVS
> Connection: local
> Root: /cvs_root/
> 
> When I key in a module (specifically aspl_scripts) it says it can't find
> the module (but it DOES exist in CVS; I did add it through the command
> line).  So I try to update it and this is what I get: 
> 
> cvs update: cannot open CVS/Entries for reading: No such file or
> directory
> cvs update: nothing known about aspl_scripts
> cvs [update aborted]: cannot open CVS/Root: No such file or directory
> 
> What is CVS/Entries and CVS/Root?  I haven't specified those anywhere.  
> 
> Thanks!
> 
> Alainna
> 
> 
> 
> 
> -------------------------------------------------------
> This SF.Net email sponsored by Black Hat Briefings & Training.
> Attend Black Hat Briefings & Training, Las Vegas July 24-29 - 
> digital self defense, top technical experts, no vendor pitches, 
> unmatched networking opportunities. Visit www.blackhat.com
> _______________________________________________
> Sandweb-users mailing list
> San...@li...
> https://lists.sourceforge.net/lists/listinfo/sandweb-users
>