{"thread":{"id":"16680","subject":"Clarifying \"invalid tag signature file\" error message from git filter-branch (and others)","startedAt":"2008-12-11T10:14:03Z","lastAt":"2008-12-12T16:53:40Z","messageCount":10,"participants":["James Youngman","Brandon Casey","Jim Meyering","Jakub Narebski"],"isPatch":false,"patchVersion":null,"patchTotal":null},"messages":[{"id":"97590","messageId":"c5df85930812110214k2e12d926m60856fb630d45e80@mail.gmail.com","threadId":"16680","inReplyTo":null,"subject":"Clarifying \"invalid tag signature file\" error message from git filter-branch (and others)","fromName":"James Youngman","fromEmail":"jay@gnu.org","sentAt":"2008-12-11T10:14:03Z","receivedAt":"2008-12-11T10:14:03Z","isPatch":false,"sender":{"key":"jay@gnu.org","avatar":"https://gravatar.com/avatar/8b346a7ca8e7b6f8ca5db01dd6cdb5a5d886013dfbf23105186fb8b036534e67?d=mp&s=160"},"body":"What do the errors \"error: char88: malformed tagger field\" and \"fatal:\ninvalid tag signature file\" and \"Could not create new tag object for\nFINDUTILS-4_1-10\" signify in the session below?\n\nAre any of those errors correctable (I can re-run the tree rewrite\nscript as many times as needed, I'm just using it on a test repository\nfor now).\n\nThe script I'm invoking calls git filter-branch; I've attached the script.\n\n$ bash ~/source/GNU/findutils/logrewrite.sh\nfatal: Not a git repository\nRewrite 9afb13614381c4bfa22f515c18cbfe6f54798330 (1587/1587)\nRef 'refs/heads/master' was rewritten\nFINDUTILS-4_1-10 -> FINDUTILS-4_1-10\n(ce25eb352de8dc53a9a7805ba9efc1c9215d28c2 ->\n79221244237bc408ced0c37f3c3476d53e665801)\nerror: char88: malformed tagger field\nfatal: invalid tag signature file\nCould not create new tag object for FINDUTILS-4_1-10\n$\n\nThanks,\nJames.\n"},{"id":"97624","messageId":"P7E-5meNX4tXFurN9mnRguFHdJG1jaZYTn6WxFFpECSJ68KyYT3wqQ@cipher.nrlssc.navy.mil","threadId":"16680","inReplyTo":"c5df85930812110214k2e12d926m60856fb630d45e80@mail.gmail.com","subject":"Re: Clarifying \"invalid tag signature file\" error message from git filter-branch (and others)","fromName":"Brandon Casey","fromEmail":"casey@nrlssc.navy.mil","sentAt":"2008-12-11T21:06:06Z","receivedAt":"2008-12-11T21:06:06Z","isPatch":false,"sender":{"key":"drafnel@gmail.com","avatar":"https://avatars.githubusercontent.com/u/921167?v=4"},"body":"James Youngman wrote:\n> What do the errors \"error: char88: malformed tagger field\" and \"fatal:\n> invalid tag signature file\" and \"Could not create new tag object for\n> FINDUTILS-4_1-10\" signify in the session below?\n\nIt means the tagger field in the tag does not follow the correct form.\nSpecifically the testing in git-mktag (called by filter-branch) does:\n\n * Check for correct form for name and email\n * i.e. \" <\" followed by \"> \" on _this_ line\n * No angle brackets within the name or email address fields.\n * No spaces within the email address field.\n\nWhat does 'git cat-file tag FINDUTILS-4_1-10' show you?\n\n> Are any of those errors correctable (I can re-run the tree rewrite\n> script as many times as needed, I'm just using it on a test repository\n> for now).\n\nIf there are only a few, then you can manually retag with a corrected\ntagger field, and then run your script.\n\nOf course, depending on the output of the cat-file call above, the\ntesting in git-mktag may need to be relaxed.\n\n-brandon\n"},{"id":"97631","messageId":"c5df85930812111434m879f1faq80c64286714c3a1f@mail.gmail.com","threadId":"16680","inReplyTo":"P7E-5meNX4tXFurN9mnRguFHdJG1jaZYTn6WxFFpECSJ68KyYT3wqQ@cipher.nrlssc.navy.mil","subject":"Re: Clarifying \"invalid tag signature file\" error message from git filter-branch (and others)","fromName":"James Youngman","fromEmail":"jay@gnu.org","sentAt":"2008-12-11T22:34:53Z","receivedAt":"2008-12-11T22:34:53Z","isPatch":false,"sender":{"key":"jay@gnu.org","avatar":"https://gravatar.com/avatar/8b346a7ca8e7b6f8ca5db01dd6cdb5a5d886013dfbf23105186fb8b036534e67?d=mp&s=160"},"body":"On Thu, Dec 11, 2008 at 9:06 PM, Brandon Casey wrote:\n> James Youngman wrote:\n>> What do the errors \"error: char88: malformed tagger field\" and \"fatal:\n>> invalid tag signature file\" and \"Could not create new tag object for\n>> FINDUTILS-4_1-10\" signify in the session below?\n>\n> It means the tagger field in the tag does not follow the correct form.\n> Specifically the testing in git-mktag (called by filter-branch) does:\n>\n> * Check for correct form for name and email\n> * i.e. \" <\" followed by \"> \" on _this_ line\n> * No angle brackets within the name or email address fields.\n> * No spaces within the email address field.\n>\n> What does 'git cat-file tag FINDUTILS-4_1-10' show you?\n\nBefore conversion:\n$ git cat-file tag FINDUTILS-4_1-10\nobject ce25eb352de8dc53a9a7805ba9efc1c9215d28c2\ntype commit\ntag FINDUTILS-4_1-10\ntagger Kevin Dalley\n\nThe conversion:\n\nAfter conversion:\n$ git cat-file tag FINDUTILS-4_1-10\nobject ce25eb352de8dc53a9a7805ba9efc1c9215d28c2\ntype commit\ntag FINDUTILS-4_1-10\ntagger Kevin Dalley\n\nThis is in the repo at\nhttp://git.savannah.gnu.org/gitweb/?p=findutils.git;a=commit;h=ce25eb352de8dc53a9a7805ba9efc1c9215d28c2\n\n>> Are any of those errors correctable (I can re-run the tree rewrite\n>> script as many times as needed, I'm just using it on a test repository\n>> for now).\n>\n> If there are only a few, then you can manually retag with a corrected\n> tagger field, and then run your script.\n>\n> Of course, depending on the output of the cat-file call above, the\n> testing in git-mktag may need to be relaxed.\n>\n> -brandon\n>\n"},{"id":"97637","messageId":"LhfS_uc2B_Gje7rXd1882RMsQfSRjOEsBT24Z1Yza_bWhgl9lI-ZhQ@cipher.nrlssc.navy.mil","threadId":"16680","inReplyTo":"c5df85930812111434m879f1faq80c64286714c3a1f@mail.gmail.com","subject":"Re: Clarifying \"invalid tag signature file\" error message from git filter-branch (and others)","fromName":"Brandon Casey","fromEmail":"casey@nrlssc.navy.mil","sentAt":"2008-12-11T23:13:36Z","receivedAt":"2008-12-11T23:13:36Z","isPatch":false,"sender":{"key":"drafnel@gmail.com","avatar":"https://avatars.githubusercontent.com/u/921167?v=4"},"body":"James Youngman wrote:\n> On Thu, Dec 11, 2008 at 9:06 PM, Brandon Casey wrote:\n>> James Youngman wrote:\n>>> What do the errors \"error: char88: malformed tagger field\" and \"fatal:\n>>> invalid tag signature file\" and \"Could not create new tag object for\n>>> FINDUTILS-4_1-10\" signify in the session below?\n>> It means the tagger field in the tag does not follow the correct form.\n>> Specifically the testing in git-mktag (called by filter-branch) does:\n>>\n>> * Check for correct form for name and email\n>> * i.e. \" <\" followed by \"> \" on _this_ line\n>> * No angle brackets within the name or email address fields.\n>> * No spaces within the email address field.\n>>\n>> What does 'git cat-file tag FINDUTILS-4_1-10' show you?\n> \n> Before conversion:\n> $ git cat-file tag FINDUTILS-4_1-10\n> object ce25eb352de8dc53a9a7805ba9efc1c9215d28c2\n> type commit\n> tag FINDUTILS-4_1-10\n> tagger Kevin Dalley\n\nThe tagger field is missing an email address, a timestamp, and a timezone. It\nshould look something like:\n\n tagger Kevin Dalley 1229036026 -0800\n\ngit-mktag prevents improperly formatted tags from being created by checking\nthat these fields exist and are well formed.\n\nIf you know the correct values for the missing fields, then you could\nrecreate the tags before doing the filter-branch. If they are unknown, it\nseems valid enough to use the values from the commit that the tag points\nto.\n\ni.e.\n\n tagger Kevin Dalley 830638152 -0000\n\nWhat tool was used to convert this repository to git? It should be corrected\nto produce valid annotated tags. Especially if it is a tool within git.\n\n\nThe tag below was actually not converted. filter-branch bailed\nout during the conversion and so left it alone.\n\n> The conversion:\n> \n> After conversion:\n> $ git cat-file tag FINDUTILS-4_1-10\n> object ce25eb352de8dc53a9a7805ba9efc1c9215d28c2\n> type commit\n> tag FINDUTILS-4_1-10\n> tagger Kevin Dalley\n> \n> This is in the repo at\n> http://git.savannah.gnu.org/gitweb/?p=findutils.git;a=commit;h=ce25eb352de8dc53a9a7805ba9efc1c9215d28c2\n\n-brandon\n"},{"id":"97644","messageId":"c5df85930812111559p287ea6afk54a9759302288d5e@mail.gmail.com","threadId":"16680","inReplyTo":"LhfS_uc2B_Gje7rXd1882RMsQfSRjOEsBT24Z1Yza_bWhgl9lI-ZhQ@cipher.nrlssc.navy.mil","subject":"Re: Clarifying \"invalid tag signature file\" error message from git filter-branch (and others)","fromName":"James Youngman","fromEmail":"jay@gnu.org","sentAt":"2008-12-11T23:59:29Z","receivedAt":"2008-12-11T23:59:29Z","isPatch":false,"sender":{"key":"jay@gnu.org","avatar":"https://gravatar.com/avatar/8b346a7ca8e7b6f8ca5db01dd6cdb5a5d886013dfbf23105186fb8b036534e67?d=mp&s=160"},"body":"On Thu, Dec 11, 2008 at 11:13 PM, Brandon Casey wrote:\n\n>> Before conversion:\n>> $ git cat-file tag FINDUTILS-4_1-10\n>> object ce25eb352de8dc53a9a7805ba9efc1c9215d28c2\n>> type commit\n>> tag FINDUTILS-4_1-10\n>> tagger Kevin Dalley\n>\n> The tagger field is missing an email address, a timestamp, and a timezone. It\n> should look something like:\n>\n> tagger Kevin Dalley 1229036026 -0800\n>\n> git-mktag prevents improperly formatted tags from being created by checking\n> that these fields exist and are well formed.\n>\n> If you know the correct values for the missing fields, then you could\n\nYes for the email address. But as for the timestamp, it's not in\nthe tag file; that only contains the sha1.\nThere is a timestamp in the object being tagged, is that the timestamp\nyou are talking about?\n\n$ git show --pretty=raw ce25eb352de8dc53a9a7805ba9efc1c9215d28c2\ncommit ce25eb352de8dc53a9a7805ba9efc1c9215d28c2\ntree 752cca144d39bc55d05fbe304752b274ba22641c\nparent 9a998755249b0c8c47e8657cff712fa506aa30fc\nauthor Kevin Dalley 830638152 +0000\ncommitter Kevin Dalley 830638152 +0000\n\n *** empty log message ***\n\ndiff --git a/debian.Changelog b/debian.Changelog\nindex e3541eb..d0cd295 100644\n--- a/debian.Changelog\n+++ b/debian.Changelog\n@@ -1,5 +1,7 @@\n Sat Apr 27 12:29:06 1996 Kevin Dalley\n\n\n+ * find.info, find.info-1, find.info-2: updated to match find.texi\n+\n * debian.rules (debian): update debian revision to 10\n\n * getline.c (getstr): verify that nchars_avail is *really* greater\n\n\n\n\n\n> recreate the tags before doing the filter-branch. If they are unknown, it\n> seems valid enough to use the values from the commit that the tag points\n> to.\n>\n> i.e.\n>\n> tagger Kevin Dalley 830638152 -0000\n>\n> What tool was used to convert this repository to git? It should be corrected\n> to produce valid annotated tags. Especially if it is a tool within git.\n\nI don't know, Jim Meyering will know though, so I CC'ed him.\n\n\n> The tag below was actually not converted. filter-branch bailed\n> out during the conversion and so left it alone.\n\nI see.\n\nThanks,\nJames.\n"},{"id":"97690","messageId":"87zlj1hd0r.fsf@rho.meyering.net","threadId":"16680","inReplyTo":"c5df85930812111559p287ea6afk54a9759302288d5e@mail.gmail.com","subject":"Re: Clarifying \"invalid tag signature file\" error message from git filter-branch (and others)","fromName":"Jim Meyering","fromEmail":"jim@meyering.net","sentAt":"2008-12-12T11:02:44Z","receivedAt":"2008-12-12T11:02:44Z","isPatch":false,"sender":{"key":"jim@meyering.net","avatar":"https://avatars.githubusercontent.com/u/710630?v=4"},"body":"\"James Youngman\" wrote:\n> On Thu, Dec 11, 2008 at 11:13 PM, Brandon Casey wrote:\n>\n>>> Before conversion:\n>>> $ git cat-file tag FINDUTILS-4_1-10\n>>> object ce25eb352de8dc53a9a7805ba9efc1c9215d28c2\n>>> type commit\n>>> tag FINDUTILS-4_1-10\n>>> tagger Kevin Dalley\n>>\n>> The tagger field is missing an email address, a timestamp, and a timezone. It\n>> should look something like:\n>>\n>> tagger Kevin Dalley 1229036026 -0800\n>>\n>> git-mktag prevents improperly formatted tags from being created by checking\n>> that these fields exist and are well formed.\n>>\n>> If you know the correct values for the missing fields, then you could\n>\n> Yes for the email address. But as for the timestamp, it's not in\n> the tag file; that only contains the sha1.\n> There is a timestamp in the object being tagged, is that the timestamp\n> you are talking about?\n>\n> $ git show --pretty=raw ce25eb352de8dc53a9a7805ba9efc1c9215d28c2\n> commit ce25eb352de8dc53a9a7805ba9efc1c9215d28c2\n> tree 752cca144d39bc55d05fbe304752b274ba22641c\n> parent 9a998755249b0c8c47e8657cff712fa506aa30fc\n> author Kevin Dalley 830638152 +0000\n> committer Kevin Dalley 830638152 +0000\n>\n> *** empty log message ***\n>\n> diff --git a/debian.Changelog b/debian.Changelog\n> index e3541eb..d0cd295 100644\n> --- a/debian.Changelog\n> +++ b/debian.Changelog\n> @@ -1,5 +1,7 @@\n> Sat Apr 27 12:29:06 1996 Kevin Dalley\n> \n>\n> + * find.info, find.info-1, find.info-2: updated to match find.texi\n> +\n> * debian.rules (debian): update debian revision to 10\n>\n> * getline.c (getstr): verify that nchars_avail is *really* greater\n>\n>\n>\n>\n>\n>> recreate the tags before doing the filter-branch. If they are unknown, it\n>> seems valid enough to use the values from the commit that the tag points\n>> to.\n>>\n>> i.e.\n>>\n>> tagger Kevin Dalley 830638152 -0000\n>>\n>> What tool was used to convert this repository to git? It should be corrected\n>> to produce valid annotated tags. Especially if it is a tool within git.\n>\n> I don't know, Jim Meyering will know though, so I CC'ed him.\n\nI used parsecvs, probably with git-master from the date of\nthe initial conversion (check the archives for actual date).\nThat was long enough ago that it was almost certainly before\ngit-mktag learned to be more strict about its inputs.\n\nJames, since you're about to rewrite the history, you may want to\nstart that process from a freshly-cvs-to-git-converted repository.\n\nI'm not very happy about using cvsparse (considering it's not\nreally being maintained, afaik), so if the git crowd\ncan recommend something better, I'm all ears.\n"},{"id":"97705","messageId":"c5df85930812120805q43b96faal31fa93e7d317fcc4@mail.gmail.com","threadId":"16680","inReplyTo":"87zlj1hd0r.fsf@rho.meyering.net","subject":"Re: Clarifying \"invalid tag signature file\" error message from git filter-branch (and others)","fromName":"James Youngman","fromEmail":"jay@gnu.org","sentAt":"2008-12-12T16:05:19Z","receivedAt":"2008-12-12T16:05:19Z","isPatch":false,"sender":{"key":"jay@gnu.org","avatar":"https://gravatar.com/avatar/8b346a7ca8e7b6f8ca5db01dd6cdb5a5d886013dfbf23105186fb8b036534e67?d=mp&s=160"},"body":"On Fri, Dec 12, 2008 at 11:02 AM, Jim Meyering wrote:\n> \"James Youngman\" wrote:\n>> On Thu, Dec 11, 2008 at 11:13 PM, Brandon Casey wrote:\n>>\n>>>> Before conversion:\n>>>> $ git cat-file tag FINDUTILS-4_1-10\n>>>> object ce25eb352de8dc53a9a7805ba9efc1c9215d28c2\n>>>> type commit\n>>>> tag FINDUTILS-4_1-10\n>>>> tagger Kevin Dalley\n>>>\n>>> The tagger field is missing an email address, a timestamp, and a timezone. It\n>>> should look something like:\n>>>\n>>> tagger Kevin Dalley 1229036026 -0800\n>>>\n>>> git-mktag prevents improperly formatted tags from being created by checking\n>>> that these fields exist and are well formed.\n>>>\n>>> If you know the correct values for the missing fields, then you could\n>>\n>> Yes for the email address. But as for the timestamp, it's not in\n>> the tag file; that only contains the sha1.\n>> There is a timestamp in the object being tagged, is that the timestamp\n>> you are talking about?\n>>\n>> $ git show --pretty=raw ce25eb352de8dc53a9a7805ba9efc1c9215d28c2\n>> commit ce25eb352de8dc53a9a7805ba9efc1c9215d28c2\n>> tree 752cca144d39bc55d05fbe304752b274ba22641c\n>> parent 9a998755249b0c8c47e8657cff712fa506aa30fc\n>> author Kevin Dalley 830638152 +0000\n>> committer Kevin Dalley 830638152 +0000\n>>\n>> *** empty log message ***\n>>\n>> diff --git a/debian.Changelog b/debian.Changelog\n>> index e3541eb..d0cd295 100644\n>> --- a/debian.Changelog\n>> +++ b/debian.Changelog\n>> @@ -1,5 +1,7 @@\n>> Sat Apr 27 12:29:06 1996 Kevin Dalley\n>> \n>>\n>> + * find.info, find.info-1, find.info-2: updated to match find.texi\n>> +\n>> * debian.rules (debian): update debian revision to 10\n>>\n>> * getline.c (getstr): verify that nchars_avail is *really* greater\n>>\n>>\n>>\n>>\n>>\n>>> recreate the tags before doing the filter-branch. If they are unknown, it\n>>> seems valid enough to use the values from the commit that the tag points\n>>> to.\n>>>\n>>> i.e.\n>>>\n>>> tagger Kevin Dalley 830638152 -0000\n>>>\n>>> What tool was used to convert this repository to git? It should be corrected\n>>> to produce valid annotated tags. Especially if it is a tool within git.\n>>\n>> I don't know, Jim Meyering will know though, so I CC'ed him.\n>\n> I used parsecvs, probably with git-master from the date of\n> the initial conversion (check the archives for actual date).\n> That was long enough ago that it was almost certainly before\n> git-mktag learned to be more strict about its inputs.\n>\n> James, since you're about to rewrite the history, you may want to\n> start that process from a freshly-cvs-to-git-converted repository.\n\nMaybe, but then afaik CVS tags don't have timestamps, so some of the\ndata that git-mktag seems to want doesn't exist anyway.\n\nBut until we know the answer to the next question, I don't think we\nknow how we would generate such a freshly-converted repository.\n\n> I'm not very happy about using cvsparse (considering it's not\n> really being maintained, afaik), so if the git crowd\n> can recommend something better, I'm all ears.\n\nThanks,\nJames.\n"},{"id":"97708","messageId":"ivc7ylNVmqD2RhGdI10MyG1ySwq00RZSzeh_UXbU05mhkw5od1QN8Q@cipher.nrlssc.navy.mil","threadId":"16680","inReplyTo":"c5df85930812111559p287ea6afk54a9759302288d5e@mail.gmail.com","subject":"Re: Clarifying \"invalid tag signature file\" error message from git filter-branch (and others)","fromName":"Brandon Casey","fromEmail":"casey@nrlssc.navy.mil","sentAt":"2008-12-12T16:21:30Z","receivedAt":"2008-12-12T16:21:30Z","isPatch":false,"sender":{"key":"drafnel@gmail.com","avatar":"https://avatars.githubusercontent.com/u/921167?v=4"},"body":"James Youngman wrote:\n> On Thu, Dec 11, 2008 at 11:13 PM, Brandon Casey wrote:\n> \n>>> Before conversion:\n>>> $ git cat-file tag FINDUTILS-4_1-10\n>>> object ce25eb352de8dc53a9a7805ba9efc1c9215d28c2\n>>> type commit\n>>> tag FINDUTILS-4_1-10\n>>> tagger Kevin Dalley\n>> The tagger field is missing an email address, a timestamp, and a timezone. It\n>> should look something like:\n>>\n>> tagger Kevin Dalley 1229036026 -0800\n>>\n>> git-mktag prevents improperly formatted tags from being created by checking\n>> that these fields exist and are well formed.\n>>\n>> If you know the correct values for the missing fields, then you could\n> \n> Yes for the email address. But as for the timestamp, it's not in\n> the tag file; that only contains the sha1.\n> There is a timestamp in the object being tagged, is that the timestamp\n> you are talking about?\n\nYes and no. I meant that if you knew the \"real\" timestamp, possibly by\nextracting it from the original repository, then you can use that.\nOtherwise yes, as a workaround, use the timestamp in the object being\ntagged.\n\n> $ git show --pretty=raw ce25eb352de8dc53a9a7805ba9efc1c9215d28c2\n> commit ce25eb352de8dc53a9a7805ba9efc1c9215d28c2\n> tree 752cca144d39bc55d05fbe304752b274ba22641c\n> parent 9a998755249b0c8c47e8657cff712fa506aa30fc\n> author Kevin Dalley 830638152 +0000\n> committer Kevin Dalley 830638152 +0000\n\nThe committer information should be used, though in this repository it will\nprobably always be the same as the author.\n\n-brandon\n"},{"id":"97709","messageId":"pM7a12pzXF7_bo-ZbyAqPidB0DEgwMnL3L42vDjdMAOFi2m_ib8CBw@cipher.nrlssc.navy.mil","threadId":"16680","inReplyTo":"87zlj1hd0r.fsf@rho.meyering.net","subject":"Re: Clarifying \"invalid tag signature file\" error message from git filter-branch (and others)","fromName":"Brandon Casey","fromEmail":"casey@nrlssc.navy.mil","sentAt":"2008-12-12T16:44:03Z","receivedAt":"2008-12-12T16:44:03Z","isPatch":false,"sender":{"key":"drafnel@gmail.com","avatar":"https://avatars.githubusercontent.com/u/921167?v=4"},"body":"Jim Meyering wrote:\n> \"James Youngman\" wrote:\n>> On Thu, Dec 11, 2008 at 11:13 PM, Brandon Casey wrote:\n\n>>> What tool was used to convert this repository to git? It should be corrected\n>>> to produce valid annotated tags. Especially if it is a tool within git.\n>> I don't know, Jim Meyering will know though, so I CC'ed him.\n> \n> I used parsecvs, probably with git-master from the date of\n> the initial conversion (check the archives for actual date).\n> That was long enough ago that it was almost certainly before\n> git-mktag learned to be more strict about its inputs.\n> \n> James, since you're about to rewrite the history, you may want to\n> start that process from a freshly-cvs-to-git-converted repository.\n> \n> I'm not very happy about using cvsparse (considering it's not\n> really being maintained, afaik), so if the git crowd\n> can recommend something better, I'm all ears.\n\nI've only used git-cvsimport. AFAIK it creates light-weight tags in\ngit rather than annotated tags.\n\nIt also uses an unmaintained tool: cvsps. There are some additional\npatches in a git repository somewhere that fix a few known problems.\n\nYou could try that James.\n\n-brandon\n"},{"id":"97711","messageId":"m3bpvhgws3.fsf@localhost.localdomain","threadId":"16680","inReplyTo":"87zlj1hd0r.fsf@rho.meyering.net","subject":"Re: Clarifying \"invalid tag signature file\" error message from git filter-branch (and others)","fromName":"Jakub Narebski","fromEmail":"jnareb@gmail.com","sentAt":"2008-12-12T16:53:40Z","receivedAt":"2008-12-12T16:53:40Z","isPatch":false,"sender":{"key":"jnareb@gmail.com","avatar":"https://avatars.githubusercontent.com/u/2706?v=4"},"body":"Jim Meyering writes:\n\n> I used parsecvs, probably with git-master from the date of\n> the initial conversion (check the archives for actual date).\n> That was long enough ago that it was almost certainly before\n> git-mktag learned to be more strict about its inputs.\n> \n> James, since you're about to rewrite the history, you may want to\n> start that process from a freshly-cvs-to-git-converted repository.\n> \n> I'm not very happy about using parsecvs (considering it's not\n> really being maintained, afaik), so if the git crowd\n> can recommend something better, I'm all ears.\n\nThe page you might want to consult is\n\n http://git.or.cz/gitwiki/InterfacesFrontendsAndTools\n\nThere you have listed git-cvsimport, which uses cvsps to extract\npatchset, is in git, and is as far as I know the only tool that allow\nincremental import; parsecvs which requires access to *,v files you\nuse; cvs2svn (cvs2git) which have learned fast-import format and can\nbe used to import (fast) CVS repositories, but incremental import\n(difficult that it is) is only in plans, AFAIK.\n\nSo I would recommend trying cvs2svn / cvs2git.\n-- \nJakub Narebski\nPoland\nShadeHawk on #git\n"}]}