{"thread":{"id":"51882","subject":"git-svn authors file in repo (Author: xxx not defined in .gitauthors file)","startedAt":"2019-09-19T14:34:27Z","lastAt":"2019-09-20T06:49:43Z","messageCount":3,"participants":["Joseph Mingrone","SZEDER Gábor","Eric Wong"],"isPatch":false,"patchVersion":null,"patchTotal":null},"messages":[{"id":"382582","messageId":"86o8zgfj82.fsf@phe.ftfl.ca","threadId":"51882","inReplyTo":null,"subject":"git-svn authors file in repo (Author: xxx not defined in .gitauthors file)","fromName":"Joseph Mingrone","fromEmail":"jrm@ftfl.ca","sentAt":"2019-09-19T14:34:21Z","receivedAt":"2019-09-19T14:34:27Z","isPatch":false,"sender":{"key":"jrm@ftfl.ca","avatar":"https://gravatar.com/avatar/6faaf635a0a3933e4bad6272de32e73fd165252515b9fb497549ca684c2bddf9?d=mp&s=160"},"body":"Hello,\n\nWe maintain a .gitauthors file for git-svn. When a new committer is\nadded to our project, a new entry is added to the .gitauthors file,\nbut we sometimes see errors like this:\n\n% git -C /usr/ports svn rebase\n M .gitauthors\nr512146 = 0c1f924ca984d53333beabb909ea53afb856c44b (refs/remotes/origin/trunk)\n M math/py-pystan/Makefile\nr512147 = acc387d4c8f3ebf904010bccc5679be06b184a9d (refs/remotes/origin/trunk)\n M deskutils/gworkspace-gwmetadata/Makefile\n...\n...\n...\nr512184 = 442bd1025776d5e3171be8e497ef2056dc47ff06 (refs/remotes/origin/trunk)\n M www/rubygem-passenger/Makefile\n M www/rubygem-passenger/distinfo\n D www/rubygem-passenger/files/patch-asio-libc++7\nW: -empty_dir: head/www/rubygem-passenger/files/patch-asio-libc++7\nr512185 = f1a1b447811ae84011288678136e185c83180b8e (refs/remotes/origin/trunk)\n M astro/xearth/files/freebsd.committers.markers\nAuthor: dmgk not defined in .gitauthors file\n\nThe new committer, dmgk, was added to .gitauthors in svn commit r512146,\nthen later he committed to the repository for the first time in r512185.\nIt seems that if these two commits are included in the same `git svn\nrebase`, the error above will occur.\n\nIs there a solution or workaround for this aside from each committer\nhaving an updated .gitauthors before doing `git svn rebase`. It's seems\nto be a chicken/egg issue; they first need the updated .gitauthors file,\nbut the way to get the updated .gitauthors files is to do `git svn\nrebase`.\n\nRegards,\n\nJoseph\n"},{"id":"382639","messageId":"20190919231833.GA9363@szeder.dev","threadId":"51882","inReplyTo":"86o8zgfj82.fsf@phe.ftfl.ca","subject":"Re: git-svn authors file in repo (Author: xxx not defined in .gitauthors file)","fromName":"SZEDER Gábor","fromEmail":"szeder.dev@gmail.com","sentAt":"2019-09-19T23:18:33Z","receivedAt":"2019-09-19T23:18:43Z","isPatch":false,"sender":{"key":"szeder.dev@gmail.com","avatar":"https://avatars.githubusercontent.com/u/116324?v=4"},"body":"On Thu, Sep 19, 2019 at 11:34:21AM -0300, Joseph Mingrone wrote:\n> Hello,\n> \n> We maintain a .gitauthors file for git-svn. When a new committer is\n> added to our project, a new entry is added to the .gitauthors file,\n> but we sometimes see errors like this:\n> \n> % git -C /usr/ports svn rebase\n> M .gitauthors\n> r512146 = 0c1f924ca984d53333beabb909ea53afb856c44b (refs/remotes/origin/trunk)\n> M math/py-pystan/Makefile\n> r512147 = acc387d4c8f3ebf904010bccc5679be06b184a9d (refs/remotes/origin/trunk)\n> M deskutils/gworkspace-gwmetadata/Makefile\n> ...\n> ...\n> ...\n> r512184 = 442bd1025776d5e3171be8e497ef2056dc47ff06 (refs/remotes/origin/trunk)\n> M www/rubygem-passenger/Makefile\n> M www/rubygem-passenger/distinfo\n> D www/rubygem-passenger/files/patch-asio-libc++7\n> W: -empty_dir: head/www/rubygem-passenger/files/patch-asio-libc++7\n> r512185 = f1a1b447811ae84011288678136e185c83180b8e (refs/remotes/origin/trunk)\n> M astro/xearth/files/freebsd.committers.markers\n> Author: dmgk not defined in .gitauthors file\n> \n> The new committer, dmgk, was added to .gitauthors in svn commit r512146,\n> then later he committed to the repository for the first time in r512185.\n> It seems that if these two commits are included in the same `git svn\n> rebase`, the error above will occur.\n> \n> Is there a solution or workaround for this aside from each committer\n> having an updated .gitauthors before doing `git svn rebase`. It's seems\n> to be a chicken/egg issue; they first need the updated .gitauthors file,\n> but the way to get the updated .gitauthors files is to do `git svn\n> rebase`.\n\nI have no idea how 'git svn' works and what this '.gitauthors' file\nis, so no workarounds from me... But this seems to be similar to the\nissue with '.gitattributes' in core Git that was fixed recently:\n\n https://public-inbox.org/git/20190902223944.897504-3-sandals@crustytoothpaste.net/\n\nPerhaps 'git svn rebase' should do the same, i.e. look out for commits\nchanging this '.gitauthors' file and re-read the file each time it is\nchanged.\n\nCc-ing Eric for git-svn know-how.\n\n"},{"id":"382644","messageId":"20190920064941.trlc3noyvgseid3m@dcvr","threadId":"51882","inReplyTo":"20190919231833.GA9363@szeder.dev","subject":"Re: git-svn authors file in repo (Author: xxx not defined in .gitauthors file)","fromName":"Eric Wong","fromEmail":"e@80x24.org","sentAt":"2019-09-20T06:49:41Z","receivedAt":"2019-09-20T06:49:43Z","isPatch":false,"sender":{"key":"e@80x24.org","avatar":null},"body":"SZEDER Gábor wrote:\n> On Thu, Sep 19, 2019 at 11:34:21AM -0300, Joseph Mingrone wrote:\n> > Hello,\n> > \n> > We maintain a .gitauthors file for git-svn. When a new committer is\n> > added to our project, a new entry is added to the .gitauthors file,\n> > but we sometimes see errors like this:\n> > \n> > % git -C /usr/ports svn rebase\n> > M .gitauthors\n> > r512146 = 0c1f924ca984d53333beabb909ea53afb856c44b (refs/remotes/origin/trunk)\n> > M math/py-pystan/Makefile\n> > r512147 = acc387d4c8f3ebf904010bccc5679be06b184a9d (refs/remotes/origin/trunk)\n> > M deskutils/gworkspace-gwmetadata/Makefile\n> > ...\n> > ...\n> > ...\n> > r512184 = 442bd1025776d5e3171be8e497ef2056dc47ff06 (refs/remotes/origin/trunk)\n> > M www/rubygem-passenger/Makefile\n> > M www/rubygem-passenger/distinfo\n> > D www/rubygem-passenger/files/patch-asio-libc++7\n> > W: -empty_dir: head/www/rubygem-passenger/files/patch-asio-libc++7\n> > r512185 = f1a1b447811ae84011288678136e185c83180b8e (refs/remotes/origin/trunk)\n> > M astro/xearth/files/freebsd.committers.markers\n> > Author: dmgk not defined in .gitauthors file\n> > \n> > The new committer, dmgk, was added to .gitauthors in svn commit r512146,\n> > then later he committed to the repository for the first time in r512185.\n> > It seems that if these two commits are included in the same `git svn\n> > rebase`, the error above will occur.\n> > \n> > Is there a solution or workaround for this aside from each committer\n> > having an updated .gitauthors before doing `git svn rebase`. It's seems\n> > to be a chicken/egg issue; they first need the updated .gitauthors file,\n> > but the way to get the updated .gitauthors files is to do `git svn\n> > rebase`.\n> \n> I have no idea how 'git svn' works and what this '.gitauthors' file\n> is, so no workarounds from me... But this seems to be similar to the\n> issue with '.gitattributes' in core Git that was fixed recently:\n> \n> https://public-inbox.org/git/20190902223944.897504-3-sandals@crustytoothpaste.net/\n> \n> Perhaps 'git svn rebase' should do the same, i.e. look out for commits\n> changing this '.gitauthors' file and re-read the file each time it is\n> changed.\n> \n> Cc-ing Eric for git-svn know-how.\n\nYes it's a bug in git-svn that we don't reload the authorsfile.\nA patch (and reviewers) would be welcome :>\nKinda surprised nobody reported it until now, or maybe I missed it.\n"}]}