cvsps-import imports $CVSROOT/CVSROOT
Bug #156974 reported by
Mark Chernev
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
CVS to Bazaar importer |
Confirmed
|
Medium
|
Unassigned |
Bug Description
cvsps-import revno: 57
Bazaar (bzr) 0.91.0
"bzr cvsps-import $CVSROOT . output" imports $CVSROOT/CVSROOT, even though it contains nothing but CVS metadata that's useless to the user once the import is completed.
So, the way it stands now, the user would have to manually delete CVSROOT from his repository after the import is complete, whereas it should have never been imported in the first place.
In a discussion on #bzr it was suggested that a cvsps-import have a switch option to allow $CVSROOT/CVSROOT to be imported, in the corner cases where a user may want the CVS metadata after all.
To post a comment you must log in.
To restate my stance from IRC:
I think the more likely bug is that cvsps-import [easily] lets you
import the root of the repository. While you CAN use CVS in that way,
I've never heard anybody recommend it without chemical assistance, and
actually _using_ CVS that way would be remarkably unpleasant. So, I
tend to think that trying to import the root of the repo is more
likely to be a user error than a real request, and the proper response
isn't "ignore CVSROOT/", but rather "refuse [in the absence of
--force]". And if they really DO want to import the whole repo as one
branch, I tend to think they may well want CVSROOT/ too.
If somebody REALLY wants to import the root of the repo, but without
CVSROOT/, it can be done by manipulation of ignore patterns.
Realistically, only via ~/.bazaar/ignore. Perhaps cvsps-import should
allow some way to pre-seed the tree so you could stuff a .bzrignore in
there ahead of time; that would also allow pre-setting the format of
the target branch, etc.