Bug #71622 for Git-DescribeVersion: FYI bug, "fatal: Not a git repository: $valid

Wed Oct 12 04:51:47 2011 mca1001 [...] users.sourceforge.net - Ticket created

Subject:

FYI bug, "fatal: Not a git repository: $valid_workingcopy\n"

Hi Randy, Thank you for writing Dist::Zilla::Plugin::Git::DescribeVersion. I had previously hacked something similar, http://perlunit.git.sourceforge.net/git/gitweb.cgi?p=perlunit/perlunit;a=history;f=inc/GetVersion.pm but you're quite right, that is not a sane way to proceed! This is just to let you know about https://rt.cpan.org/Ticket/Display.html?id=71621 ["fatal: Not a git repository: $valid_workingcopy\n" under Dist::Zilla::Plugin::@blah] in which a constellation alignment of packages causes Git::DescribeVersion to fail due to changed $/ ($INPUT_RECORD_SEPARATOR or $RS). I'm not sure there is anything you need to do, except perhaps consider falling back to a different git access mechanism when one fails? I hope this is useful, -- Matthew

Wed Oct 12 06:08:38 2011 mca1001 [...] users.sourceforge.net - Reference by ticket #71626 added

Wed Oct 19 18:08:58 2011 RWSTAUNER [...] cpan.org - Correspondence added

Thanks for reporting! I changed it to fallback to the next method on failure as you suggested. I additionally localized $/ for Git::Repository to work around that specific issue.

Wed Oct 19 18:08:58 2011 The RT System itself - Status changed from 'new' to 'open'

Wed Oct 19 18:08:58 2011 RWSTAUNER [...] cpan.org - Status changed from 'open' to 'resolved'

Bug #71622 for Git-DescribeVersion: FYI bug, "fatal: Not a git repository: $valid_workingcopy\n"