Re: Clarifying "invalid tag signature file" error message from git filter-branch (and others)
- From
Brandon Casey <casey@nrlssc.navy.mil>
- Date
- Dec 12, 2008, 16:44 UTC
- Message-ID
- <pM7a12pzXF7_bo-ZbyAqPidB0DEgwMnL3L42vDjdMAOFi2m_ib8CBw@cipher.nrlssc.navy.mil>
- In-Reply-To
- <87zlj1hd0r.fsf@rho.meyering.net>
Jim Meyering wrote:
> "James Youngman" <jay@gnu.org> wrote: >> On Thu, Dec 11, 2008 at 11:13 PM, Brandon Casey <casey@nrlssc.navy.mil> wrote:
Show 15 quoted lines
>>> What tool was used to convert this repository to git? It should be corrected >>> to produce valid annotated tags. Especially if it is a tool within git. >> I don't know, Jim Meyering will know though, so I CC'ed him. > > I used parsecvs, probably with git-master from the date of > the initial conversion (check the archives for actual date). > That was long enough ago that it was almost certainly before > git-mktag learned to be more strict about its inputs. > > James, since you're about to rewrite the history, you may want to > start that process from a freshly-cvs-to-git-converted repository. > > I'm not very happy about using cvsparse (considering it's not > really being maintained, afaik), so if the git crowd > can recommend something better, I'm all ears.
I've only used git-cvsimport. AFAIK it creates light-weight tags in git rather than annotated tags.
It also uses an unmaintained tool: cvsps. There are some additional patches in a git repository somewhere that fix a few known problems.
You could try that James.
-brandon