CVS weirdness (sticky tags set unexpectedly and files change without changing)
Is anyone else experiencing this behavior?
It seems that some files get the sticky tag set on them. The sticky tag that is used is a version number of that file. This results in those files not being updated when I use "update project" and also results in me not being able to check them back into CVS if I make modifications to them unless I first update them and clear the sticky tag. This can, however, result in a conflict since the file may have changed.
Is anybody else experiencing this problem?
I also have been experiencing weird behavior on a few files that seem to get marked as changed although they have not changed. This doesn't happen to many files, just a select few and always the same files.
Anybody?
Please sign in to leave a comment.
Em Tue, 15 Jun 2004 16:58:26 +0400, Stefan Freyr Stefansson escreveu:
I am. Sometimes I get a sticky tag on a file which is the version number
of that file. This usually happens on files that I'm working on, so I
haven't been bitten by the 'not updated' bug, but by another annoying, but
not really serious bug: when I try to commit the file I get an error from
the CVS server saying something like 'stick tag 1.95 on xxx.java is not a
branch'. When this happens I just do an update on the file with the 'clear
all sticky tags' checkbox turned on, and then commit the file.
It never happened to me this could be an IDEA thing. I hate our cvs server
for it's slowness, so I think I was blaming it for this strange behaviour
too. I'm running Pallada on Linux + CVSNT on Windows 2003 Server (you
would usually exected the other way around, huh?).
--
Marcus Brito <pazu@animegaiden.com.br>
I assume you use Pallada + :pserver + CVS server on Unix?
what file type are the files that appear changed although they arent't?
marked as changed, you mean "M" ?
I have also seen this. Just as you described. Our setup is :pserver + linux cvs server.
We see the sticky problem daily with the latest builds including 2114.
Our setup is :pserver and cvnnt. This is becoming a big problem. Has
anyone submitted a bug? This is stopship. Also see the marked as changed
weird state problem but it is only annoying compared to the sticky issue.
Jon
Stefan Freyr Stefansson wrote:
seen this too with pserver
I have this exact same problem as well. Running IDEA on WindowsXP and CVS (pserver) on a linux server.
Fixed in 2119.
--
Olesya Smirnova
Developer
JetBrains, Inc
http://www.jetbrains.com
"Develop with pleasure!"
"Jon Steelman" <jon@cc.gatech.edu> wrote in message
news:camthr$u4t$1@is.intellij.net...
>
>
that is used is a version number of that file. This results in those files
not being updated when I use "update project" and also results in me not
being able to check them back into CVS if I make modifications to them
unless I first update them and clear the sticky tag. This can, however,
result in a conflict since the file may have changed.
get marked as changed although they have not changed. This doesn't happen to
many files, just a select few and always the same files.
Yes I have Pallada (on Debian Linux client machine) + :pserver + CVS server on Debian Linux server machine.
The files that are being "changed" are regular java files (although not all of them as I said... just a select few).
They are marked changed inside IDEA, I haven't checked in the CVS file viewer or in CVS command line to see if they are marked there as well but I'd imagine so. It behaves exactly like IDEA "touched" the files and gave them a new timestamp.
Great! Thanks.
Are both problems fixed or just the sticky problem?
Super.
Olesya Smirnova (JetBrains) wrote:
Yes, actually it was one problem. Sorry for inconvenience...
--
Olesya Smirnova
Developer
JetBrains, Inc
http://www.jetbrains.com
"Develop with pleasure!"
"Stefan Freyr Stefansson" <stefanf@althingi.is> wrote in message
news:20991430.1087308791518.JavaMail.itn@is.intellij.net...
>
Stefan Freyr Stefansson wrote:
Yes. I have this as well - for no apparent reason the revision is turned
into a sticky tag. Very weird. Happens in a project where there are
sticky tags (branches) being used (in which case a file 'drops' off the
branc - very annoying), but also in projects that have no branches/other
sticky tags whatsoever.
CU,
Edwin