Steps to reproduce:
$ cd
$ rm -rf d
$ mkdir d
$ cd d
$ mkdir repo
$ cvs -d $PWD/repo init
$ mkdir repo/module
$ export CVSROOT=$PWD/repo
$ mkdir working
$ cd working
$ cvs co module
cvs checkout: Updating module
$ cd module
$ echo hi >file
$ cvs add file
cvs add: scheduling file `file' for addition
cvs add: use `cvs commit' to add this file permanently
$ cvs ci -m 'add file'
cvs commit: Examining .
/home/ian/d/repo/module/file,v <-- file
initial revision: 1.1
$ cd ~/d
$ find /home/ian/d/repo/module
/home/ian/d/repo/module
/home/ian/d/repo/module/file,v
$ cvsconvert /home/ian/d/repo/module
Observed behaviour:
cvsconvert: repo does not exist.
Expected behaviour:
Either an error message saying only relative paths are supported,
or correct functioning.
Additional notes:
Providing the relative path didn't work for me either with a
different error. I'm not sure if this ought to be another bug:
$ cvsconvert repo/module
fatal: You are on a branch yet to be born
cvsconvert: cat repo-module.git.fi | (cd repo-module-git >/dev/null; git fast-import --quiet --done && git checkout) returned 128.
I first experienced this with the version in buster, 1.44-1, which was
able to handle the repo I needed to convert. I have repro'd this in a
sid schroot.
In practice, I think probably *fixing* this will be rather hard but it
is probably easy to improve the error message. For now I am reporting
this bug, if for no other reason than to help the next user.
Thanks,
Ian.