Your message dated Thu, 19 Jan 2017 01:33:47 +0000
with message-id <[email protected]>
and subject line Bug#851716: fixed in dgit 3.6
has caused the Debian Bug report #851716,
regarding dgit: commit checks may be too strict
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)
--
851716: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=851716
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: dgit
I have been trying to set up a dgit server for raspbian.
Unfortunately the dgit server rejected my push claiming commit
71e128629ec786f3e45f2cffdf0792125b76e520 had missing metadata.
Further investigation shows that this commit is present on dgit.debian.org
https://browse.dgit.debian.org/xen.git/commit/?id=71e128629ec786f3e45f2cffdf0792125b76e520
And further investigation seems to show it originates from xen upstream
http://xenbits.xen.org/gitweb/?p=xen.git;a=commit;h=71e128629ec786f3e45f2cffdf0792125b76e520
I find the checking code almost impenetrable but I think it's refusing the
commit because the author has an email but no name.
Github seems quite happy with the commit as does git fsck, so IMO this is a
case of dgit being too strict.
There is supposedly a policy code I can use to make dgit ignore the check but
whenever I try and add it to my policy I get
dgit-repos-server: policy hook failed (or rejected) (2048)
I have tried three different ways of adding it to the policy
1. Changing bitmask=0 to bitmask=8
2. Adding bitmask=$(( bitmask | `policyflags 'NOCOMMITCHECK'` )) just before
the exit command
3. Adding bitmask=$(( bitmask | 8 )) just before the exit command
--- End Message ---
--- Begin Message ---
Source: dgit
Source-Version: 3.6
We believe that the bug you reported is fixed in the latest version of
dgit, which is due to be installed in the Debian FTP archive.
A summary of the changes between this version and the previous one is
attached.
Thank you for reporting the bug, which will now be closed. If you
have further comments please address them to [email protected],
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Ian Jackson <[email protected]> (supplier of updated dgit package)
(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing [email protected])
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256
Format: 1.8
Date: Thu, 19 Jan 2017 01:15:03 +0000
Source: dgit
Binary: dgit dgit-infrastructure
Architecture: all source
Version: 3.6
Distribution: unstable
Urgency: medium
Maintainer: Ian Jackson <[email protected]>
Changed-By: Ian Jackson <[email protected]>
Closes: 851716 851728 851800
Description:
dgit - git interoperability with the Debian archive
dgit-infrastructure - dgit server backend infrastructure
Changes:
dgit (3.6) unstable; urgency=medium
.
Bugfixes:
* Actually use the url from a Dgit .dsc field naming an unknown distro.
Closes:#851728.
* Add dummy implementation of file_in_archive_aptget copied from
file_in_archive_dummycat. Re:#851697. [ Peter Green ]
.
Minor improvements:
* Use `confess' to print a stack trace in a couple of internal error
rcases.
.
Infrastructure:
* Properly honour NOCOMMITCHECK policy hook exit status.
Closes:#851800.
* Do not reject commits with no author/committer name (but still insist
on email address and date). Peter Green reports that eg
71e128629ec786f3 in upstream xen.git is such a commit (and is accepted
by github). Closes:#851716.
.
Test suite:
* downstream-gitless: Test import of .dsc from unknown distro.
* downstream-gitless: Test import of .dsc with unsafe url.
Checksums-Sha1:
115eb862423e93e1fe067cf6b6540b4994af6540 1496 dgit_3.6.dsc
315b9d7015d06bed8cce72eef7a369ef07ecf261 396153 dgit_3.6.tar.gz
a850c53b37fac4007c29f5781c31e2910855f85d 46340 dgit-infrastructure_3.6_all.deb
0a544ae40c449e6b4e1c76048d7c2d01175eecbf 130868 dgit_3.6_all.deb
8bc86885046205194f793736a6d8ffbece6ab069 4516 dgit_3.6_amd64.buildinfo
Checksums-Sha256:
73bbcc40c6f2d87623f2c9fce94738f3358da8ae6b0a20fce505c7e23d6c1c5b 1496
dgit_3.6.dsc
9ff38cd3b336d4b8b66a1bf008863da23815320ad8f58635d4a0a1e68cc8eb90 396153
dgit_3.6.tar.gz
ca08b2da01f38c4d9d8738b6db6b1c1437a397cbd78517e64a4b3966ba506a9b 46340
dgit-infrastructure_3.6_all.deb
678bd79eca0c962d581fa1e058e157bc0d288a4485f3c44c7ceb3e77dd369b74 130868
dgit_3.6_all.deb
d3824f396f6bb0e01fcdc8dd674ab5a6cb277780bb3acd0ddbb12d1618351259 4516
dgit_3.6_amd64.buildinfo
Files:
6f71d567daa5289b5073a751c658d05b 1496 devel optional dgit_3.6.dsc
e6ce9942d189d2674bc6de6270c04350 396153 devel optional dgit_3.6.tar.gz
d92c4297831057a14e737f784eb3728e 46340 devel extra
dgit-infrastructure_3.6_all.deb
75263be5c223b40c04a7f350236288d6 130868 devel optional dgit_3.6_all.deb
eff4c245207fc414eb6086a3aff5d8e3 4516 devel optional dgit_3.6_amd64.buildinfo
-----BEGIN PGP SIGNATURE-----
iQEzBAEBCAAdFiEEVZrkbC1rbTJl58uh4+M5I0i1DTkFAliAE4cACgkQ4+M5I0i1
DTk8HAf9HdYGoYbVhYu1OPFAmOM/LztnOXwUniGN+lmq5C8rRfezpxaquFK9Trt4
OP8Em9bZsRol0jgiY8J5TdVOrM6z0kLP8AvSxAdQlKe/cAWyd2V1BJ1pxI45pDC5
9b4tl46nTzHHOuihO2TwFsDF3bY2WD9+NPi48gtqn8GsrMe+xhGFqRCAz9lS+9x5
ELny3LLMzo8afdQHFzFUb17GanNfqrf4zx+8sxwr1nJWScyguCpAZZCWzOoq9cvm
o9u8UipzYTtOgCYI1ObNOQDBf+6Am87m9j9EjLenjIYMZJczqHrLDLwPGH5U4E2C
wk41y5/d4kwdpBC76jlp79t6a2H9pg==
=Fd+p
-----END PGP SIGNATURE-----
--- End Message ---
