[cvsnt] Re: cvs removed jars always corrupted
Jacob Kjome
hoju at visi.com
Fri May 12 03:34:34 BST 2006
At 05:51 PM 5/11/2006, you wrote:
>On Fri, 12 May 2006 00:41:27 +0200, Bo Berglund
><bo.berglund at telia.com> wrote:
>
>>Since 2260 also has a branch related problem in the auditing area I'd
>>go for 2322 if I were you.
>
>And from just a little while ago it would be build 2329...
>
Ok, I'll try that tomorrow. Thanks. BTW, here's a note that I had
thought I sent to the list, but ended up sending to myself because
the reply-to header ends up being to the person who sent the original
mail, not the mailing list as so many other lists do. Anyway, here
it is. Not sure if it will provide any more information, but maybe
you'll see something wrong in the commands? Otherwise, I'll report
back whether the upgrade succeeded or not...
Just to make it perfectly clear what I am doing, here's a copy of the sequence
of events. I've simply copied the text from TortoiseCVS for each step I took:
add, commit, tag, remove, commit. After the tag step, I checked out the tag in
a separate directory. The jar was fine. After I removed and
committed, the jar
referenced by the tag became corrupt, just as I described
previously. Below are
the steps. I hope it helps in figuring out the problem...
thanks,
Jake
In C:\dev\ArbitraryPlayWithFeaturesModule: "C:\Program
Files\TortoiseCVS\cvs.exe" "-q" "-z6" "add" "-kbx" "commons-io-1.1.jar"
CVSROOT=:pserver:SomeUser at someserver:2401:/cvs/repo
cvs server: use 'cvs commit' to add this file permanently
Success, CVS operation completed
In C:\dev\ArbitraryPlayWithFeaturesModule: "C:\Program
Files\TortoiseCVS\cvs.exe" "-q" "-z6" "commit" "-m" "adding new binary"
"commons-io-1.1.jar"
CVSROOT=:pserver:SomeUser at someserver:2401:/cvs/repo
RCS file: /cvs/repo/ArbitraryPlayWithFeaturesModule/commons-io-1.1.jar,v
done
Checking in commons-io-1.1.jar;
/cvs/repo/ArbitraryPlayWithFeaturesModule/commons-io-1.1.jar,v <--
commons-io-1.1.jar
initial revision: 1.1
done
Success, CVS operation completed
In C:\dev\ArbitraryPlayWithFeaturesModule: "C:\Program
Files\TortoiseCVS\cvs.exe" "-q" "-z6" "tag" "-c"
"ArbitraryPlayWithFeaturesModule_1_0" "commons-io-1.1.jar"
CVSROOT=:pserver:SomeUser at someserver:2401:/cvs/repo
T commons-io-1.1.jar
Success, CVS operation completed
In C:\dev\ArbitraryPlayWithFeaturesModule: "C:\Program
Files\TortoiseCVS\cvs.exe" "-q" "-z6" "edit" "-z" "-c" "commons-io-1.1.jar"
CVSROOT=:pserver:SomeUser at someserver:2401:/cvs/repo
Success, CVS operation completed
In C:\dev\ArbitraryPlayWithFeaturesModule: "C:\Program
Files\TortoiseCVS\cvs.exe" "-q" "-z6" "remove" "commons-io-1.1.jar"
CVSROOT=:pserver:SomeUser at someserver:2401:/cvs/repo
cvs server: use 'cvs commit' to remove this file permanently
Success, CVS operation completed
Tortoise Tip: Use "cvs commit" on the folder that the file is in to remove it
permanently.
Tortoise Tip: Any removed files have been moved to the Recycle Bin.
You can undo the remove by restoring the file from the Recycle Bin and doing a
CVS Add. Note that CVS
does not keep track of folders explicitly; if you wish to remove a folder,
remove the files inside it, then do a
CVS Update. This requires that the preference setting 'Prune empty folders' is
enabled.
In C:\dev\ArbitraryPlayWithFeaturesModule: "C:\Program
Files\TortoiseCVS\cvs.exe" "-q" "-z6" "commit" "-m" "removing binary"
"commons-io-1.1.jar"
CVSROOT=:pserver:SomeUser at someserver:2401:/cvs/repo
Removing commons-io-1.1.jar;
/cvs/repo/ArbitraryPlayWithFeaturesModule/commons-io-1.1.jar,v <--
commons-io-1.1.jar
new revision: delete; previous revision: 1.1
done
Success, CVS operation completed
>HTH
>
>/Bo
>(Bo Berglund, developer in Sweden)
>_______________________________________________
>cvsnt mailing list
>cvsnt at cvsnt.org
>http://www.cvsnt.org/cgi-bin/mailman/listinfo/cvsnt
More information about the cvsnt
mailing list