[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
RE: update
From: |
Teala Spitzbarth |
Subject: |
RE: update |
Date: |
Sat, 18 Aug 2001 18:40:24 -0700 |
Good point Josh,
cvs status would warn of sticky tags as well
as report what revision was in the working
copy vs what one was in the repository.
Having a stick tag/date would be the most obvious reason
for the file not getting updated.
I'm too quick to look in the Entries file - sorry for
spreading my bad habits :-)
Cheers,
Teala
-----Original Message-----
From: Josh Baudhuin [mailto:address@hidden
Sent: Friday, August 17, 2001 6:38 PM
To: CVSpost (E-mail)
Subject: RE: update
Well, another thing to check--it is too late to do so now, is whether or
not the file was "stuck" on any particular revision.
cvs status <file>
will reveal whether or not there is a sticky date or sticky tag
associated with the file which would keep it at a particular base rev.
in your sandbox.
> -----Original Message-----
> From: address@hidden [mailto:address@hidden Behalf
Of
> Teala Spitzbarth
> Sent: Friday, August 17, 2001 5:33 PM
> To: Schwenk, Jeanie; CVSpost (E-mail)
> Cc: Kennedy, Dean
> Subject: RE: update
>
>
> Hmm, from the cvs output that you describe
> (M) it looks like cvs just thought it was locally modified.
> It didn't do a merge. That, to me, implies that cvs
> thought the file was 'up-to-date' in your working copy, and
> locally modified.
>
> The thing I would have checked (before you had blown away the
> file and re-did the update) - would have been the CVS/Entries
> file and seen what version of startComponents.cfg
> was listed in the Entries file.... if it was listing 1.3,
> then at some point your working copy had already been updated.
> If it listed 1.2, and cvs didn't do a merge on the update, then
> that sounds like a bug....
>
> Cheers,
> Teala
>
> -----Original Message-----
> From: Schwenk, Jeanie [mailto:address@hidden
> Sent: Friday, August 17, 2001 5:05 PM
> To: CVSpost (E-mail)
> Cc: Kennedy, Dean
> Subject: update
>
>
> We've had a cvs update that didn't work. The file
startComponents.cfg
> version 1.2 was in my scripts directory. The scripts directory had
been
> checked out days before from the repository. Another user modified
the
> file
> the file and checked it in (version 1.3). I did a cvs update and got
> the "M
> startComponents.cfg" but the file did not actually update.
>
> In order to get the updated file, I had to delete the file in my
> directory
> THEN do an update. Now I have the correct file.
>
> Could it be a permissions problem? The scripts directory is wide open
> and
> the file had permissions rw-rw-r--. When I do an update, does the
> update
> run as me or as CVS? Could that be why it didn't update or is it
> something
> else?
>
> This is a serious issue and I need to understand what happened.
>
> Jeanie
>
> _______________________________________________
> Info-cvs mailing list
> address@hidden
> http://mail.gnu.org/mailman/listinfo/info-cvs
>
> _______________________________________________
> Info-cvs mailing list
> address@hidden
> http://mail.gnu.org/mailman/listinfo/info-cvs
>
_______________________________________________
Info-cvs mailing list
address@hidden
http://mail.gnu.org/mailman/listinfo/info-cvs
- update, Schwenk, Jeanie, 2001/08/17
- RE: update, Teala Spitzbarth, 2001/08/17
- RE: update,
Teala Spitzbarth <=