Community technical support mailing list was retired 2010 and replaced with a professional technical support team. For assistance please contact: Pre-sales Technical support via email to sales@march-hare.com.
Fabrice, 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. Regards, 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 cvsnt downloads at march-hare.com @CVSNT on Twitter CVSNT on Facebook Cc: Subject: [cvsnt] Problem using binary option -kB Hi, 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 tests: Here is the configuration with my tests Client: Concurrent Versions System (CVSNT) 2.5.03 (Scorpio) Build 2260 (client/server) Server: Concurrent Versions System (CVSNT) 2.5.03 (Scorpio) Build 2382 (client/server) - FilePostedUsing-kB ==> cvs -z9 -w admin -o 1.5 -- "FilePostedUsing-kB" (in directory C:\Dev_CdS\TestsCVSNT\) RCS file: /services/Repository_CVS/CelluleGC/TestsCVSNT/FilePostedUsing-kB.xls,v 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 get: cvs [server aborted]: Binary patch failed Any help would be welcome, Regards, Fabrice. Atos Origin _______________________________________________ cvsnt mailing list cvsnt at cvsnt.org cvsnt downloads at march-hare.com @CVSNT on Twitter CVSNT on Facebook http://www.cvsnt.org/cgi-bin/mailman/listinfo/cvsnt https://www.march-hare.com/cvspro/en.asp#downcvs