The release announcement for the last version of CVSps had a note that sounds like it's suggesting that CVSps should either be augmented or replaced by cvs-fast-export: http://freecode.com/projects/cvsps/releases/359891 http://freecode.com/projects/cvs-fast-export I don't know that this is something that needs to be addressed right away, but I thought it might be a good idea to bring this to the cvsps package maintainer's attention. Reproducible: Steps to Reproduce:
5+ years on... Can this bug be closed? We have survived this far without any action on it.
CC: (none) => lewyssmith
No, it still should be fixed. We just need someone who is interested in maintaining this stuff. Nobody has been since blino stopped packaging.
So I can import cvs-fast-export (1.47) does this one obsoletes/provides older cvsps?
CC: (none) => geiger.david68210
Also will git-cvs correctly working afterwards?
(In reply to David GEIGER from comment #3) > So I can import cvs-fast-export (1.47) does this one obsoletes/provides > older cvsps? Yes I think so. (In reply to David GEIGER from comment #4) > Also will git-cvs correctly working afterwards? Does git-cvs even use cvsps anymore?
In git-cvsimport.txt from git source it is said that: *WARNING:* `git cvsimport` uses cvsps version 2, which is considered deprecated; it does not work with cvsps version 3 and later. If you are performing a one-shot import of a CVS repository consider using http://cvs2svn.tigris.org/cvs2git.html[cvs2git] or http://www.catb.org/esr/cvs-fast-export/[cvs-fast-export].
Interesting. Well, that certainly backs up the idea that we should replace it. It'd probably be worth mentioning it in the Release Notes so that people are aware of it.
Ok cvs-fast-export-1.47 imported now in Cauldron and also it obsolete/provide old cvsps!
Note added in Release Notes. Thanks!
Resolution: (none) => FIXEDStatus: NEW => RESOLVED