[cvsnt] Problem using binary option -kB
arthur.barrett at march-hare.com
Thu May 3 12:30:30 BST 2007
You could try downloading the latest test build of 2.5.04 from cvsnt.org/archive and try that on a test machine. It may have been spotted and fixed, but I'm sceptical.
From: Fabrice PUBILIER [mailto:fabrice.pubilier at atosorigin.com]
Sent: Thu 5/3/2007 6:16 PM
To: Arthur Barrett; cvsnt at cvsnt.org
Subject: RE: [cvsnt] Problem using binary option -kB
Thanks for your answer.
I guess it's something that should be written in the cvsnt -B option to warn
We're using CVSNT on a big Excel File that is modified about 130 times a
month, and with the requirement to keep a 3 months history...
That's definitly not a good way to use CVS but I'm trying to deal with what
I get in our Project Managment and I tried to lower the growing size using
the optimized algorithm, I should have stayed with the old -kb tough!
> -----Message d'origine-----
> De : Arthur Barrett [mailto:arthur.barrett at march-hare.com]
> Envoyé : mercredi 2 mai 2007 23:24
> À : fabrice.pubilier at atosorigin.com; cvsnt at cvsnt.org
> Objet : RE: [cvsnt] Problem using binary option -kB
> I don't recommend the use of cvs admin -o, and definitely not
> with -kB...
> I can understand you needing to free up some space with -kb
> revisions, but -kB revisions should be small enough (and disk
> space cheap enough) that it is no longer required to remove revisions.
> In short: if you are going to use cvs admin -o, use -kb, if
> you want to avoid cvs admin -o, use -kB.
> You've probably found a bug, but due to the above reasons
> it's unlikely that anyone on the commercial side are going to
> spend time trying to fix it in the near future - but of
> course you (or anyone else) can checkout the sources and fix
> it and submit a patch to cvsnt-dev which we'll gladly put
> into the next build.
> Arthur Barrett
> -----Original Message-----
> From: cvsnt-bounces at cvsnt.org on behalf of Fabrice PUBILIER
> Sent: Thu 5/3/2007 3:38 AM
> To: cvsnt at cvsnt.org
> Subject: [cvsnt] Problem using binary option -kB
> I have some binaries on a repository that I monthly clean-up
> removing revisions between tags, I use the command:
> cvs admin -o Begin:End
> I recently discovered that the binaries are not correctly
> patched anymore since I posted them with the -kB option
> instead of -kb, so I made a few
> Here is the configuration with my tests
> Client: Concurrent Versions System (CVSNT) 2.5.03 (Scorpio) Build 2260
> Server: Concurrent Versions System (CVSNT) 2.5.03 (Scorpio) Build 2382
> - FilePostedUsing-kB ==>
> cvs -z9 -w admin -o 1.5 -- "FilePostedUsing-kB" (in directory
> RCS file:
> cvs admin: inflate: invalid distance too far back cvs [admin
> aborted]: reading from server: Input/output error
> - FilePostedUsing-kb ==> Ok with binaries removal and no
> problem to get back old posts before the deleted revisions.
> Is there any problem with the new algorithm to compress binaries?
> For instance on my production repository here is my configuration:
> Client: Concurrent Versions System (CVSNT) 2.0.51d (client/server)
> Server: Concurrent Versions System (CVSNT) 2.0.26 (client/server)
> I manage to remove revisions in both case (-kb end -kB) but
> the -kB operation render old revision unpatchable:
> When I try to get an old revision before some deleted ones
> here is what I
> cvs [server aborted]: Binary patch failed
> Any help would be welcome,
> Atos Origin
> cvsnt mailing list
> cvsnt at cvsnt.org
More information about the cvsnt