You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
What steps will reproduce the problem?
1. The repostitory julindex.git is located at /srv/git/
2. The config file bugzilla.cfg:
repo: /srv/git/
login: auto@bugs.julit.com
pass: XXX
bugzilla: https://bugs.julit.com/
3. perl /srv/bugzilla/extensions/VCS/hook.pl
--config=/srv/git/julindex.git/bugzilla.cfg --project julindex.git --revision
d059b317ca3c2c23c4ee41ee9b6ad26f0f610a9b --bug 37
What is the expected output? What do you see instead?
Bugzilla Error: (32000) An error occurred while attempting to fetch commit
d059b317ca3c2c23c4ee41ee9b6ad26f0f610a9b from the "julindex.git" project in the
"/srv/git/" repository. Sometimes this means that you specified an invalid
repository or project. The error was: rev-parse confused me -
/srv/git/julindex.git/ does not have trailing Status: 200 OK at
/usr/share/perl5/Git.pm line 195.
What version of the product are you using? On what operating system?
Debian lenny using Bugzilla 3.6.2
Please provide any additional information below.
Original issue reported on code.google.com by kra...@glatzor.de on 28 Oct 2010 at 6:55
The text was updated successfully, but these errors were encountered:
Ah, thanks! I hadn't tested Git support yet because I knew that it would not
work inside of Bugzilla, since Git.pm is not taint-safe, and Git.pm is what
VCI's Git driver is using, and VCI is the backend for the VCS extension.
I will look into this, but it may take a little while to fix, since VCI may
need some siginficant re-writes.
Original comment by avatrax...@gmail.com on 28 Oct 2010 at 9:03
Hi, is there any chance that we can fix this one? I was able to hack Git.pm to
let me go further than described in the initial comment, but it is now
complaining that I am trying to access non existing commit (which I am certain
does exist).
Do you have any points where to start so we can help fixing the problem?
Original comment by antonin....@gmail.com on 19 May 2011 at 6:11
Original issue reported on code.google.com by
kra...@glatzor.de
on 28 Oct 2010 at 6:55The text was updated successfully, but these errors were encountered: