Package: dgit
Version: 9.6
Control: fixed -1 9.5
Severity: serious
check_for_git always returns falseish for the Debian repos because of
a bug in dgit's handling of WWW::Curl's (correct) behaviour with
CURLOPT_NOBODY.
As a result, dgit fetch/clone sometimes fails to stitch in the earlier
dgit push history from dgit-repos:
One possible symptom is this something like this:
synthesised git commit from .dsc 16.3.0-2.1
3ace5cdf35eed10c4a0b83b3f2804882b6343840
a330c7d56988941b518afbd479563698e3056d85 dgit repo server tip (last push) ? at
/usr/bin/dgit line 3467.
main::__ANON__("3ace5cdf35eed10c4a0b83b3f2804882b6343840", "dgit repo
server tip (last push)") called at /usr/bin/dgit line 3470
main::fetch_from_archive() called at /usr/bin/dgit line 3898
main::fetch_one() called at /usr/bin/dgit line 3918
main::dofetch() called at /usr/bin/dgit line 4886
main::cmd_fetch() called at /usr/bin/dgit line 7798
Ian.
--
Ian Jackson <ijack...@chiark.greenend.org.uk> These opinions are my own.
If I emailed you from an address @fyvzl.net or @evade.org.uk, that is
a private address which bypasses my fierce spamfilter.
