$ git cvsimport -d :pserver:cvs@cvs.fefe.de:/cvs libowfat hint: Using 'master' as the name for the initial branch. This default branch name hint: is subject to change. To configure the initial branch name to use in all hint: of your new repositories, which will suppress this warning, call: hint: hint: git config --global init.defaultBranch <name> hint: hint: Names commonly chosen instead of 'master' are 'main', 'trunk' and hint: 'development'. The just-created branch can be renamed via this command: hint: hint: git branch -m <name> Initialized empty Git repository in /tmp/cvsps/.git/ Can't exec "cvsps": No such file or directory at /usr/lib64/git-core/git-cvsimport line 760, <GEN0> line 3. Could not start cvsps: No such file or directory git cvsimport: fatal: cvsps reported error
According to git-cvsimport man page: "WARNING: git 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 cvs2git or cvs-fast-export." "Splitting the CVS log into patch sets is done by cvsps. At least version 2.1 is required."
Known and previously discussed on the dev ml. Someone needs to fix git cvsimport (presumably someone upstream). cvsps is old dead stuff and has been replaced by cvs-fast-export.
(In reply to David Walser from comment #2) > Known and previously discussed on the dev ml. Someone needs to fix git > cvsimport (presumably someone upstream). cvsps is old dead stuff and has > been replaced by cvs-fast-export. When was that? I don't manage to find that dev ml mail. However, I did find bug 25646 about the same issue. It was closed as WONTFIX, because (see bug#25646, comment#3): > Closing this, we can't afford to do upstream job. > Also, we can't provide deprecated upstream lib or app. > > Reporter, please, if you want, report like Lewis requested in Comment 2. The requested reporting was for https://gitlab.com/esr/cvs-fast-export to ask to add this functionality
Source RPM: git-2.37.3-1.mga9.src.rpm => git-2.37.3-1.mga9, cvs-fast-export-1.59-1.mga9CC: (none) => marja11Whiteboard: (none) => UPSTREAM
If this is not going to be fixed why we even ship git-cvs if we know it's broken and doesn't do what it's supposed to do?
It was over a year ago Marja, and our ml search feature is terrible. But yes Jani, if there's a way to disable the git cvsimport subcommand, that would probably be prudent.
(In reply to David Walser from comment #5) > > But yes Jani, if there's a way to disable the git cvsimport subcommand, that > would probably be prudent. Assigning to all packagers collectively for that, because we don't have a registered maintainer for git.
Assignee: bugsquad => pkg-bugsSummary: git-cvs: git cvsimport fails because of missing cvsps => Disable git cvsimport (was: git-cvs: git cvsimport fails because of missing cvsps)Source RPM: git-2.37.3-1.mga9, cvs-fast-export-1.59-1.mga9 => git-2.37.3-1.mga9
git-cvsimport is now removed from git-2.37.3-2.mga9.
Status: NEW => RESOLVEDResolution: (none) => FIXED