Your message dated Thu, 15 Jun 2023 00:19:51 +0000 with message-id <e1q9ain-00b7ds...@fasolo.debian.org> and subject line Bug#1033503: fixed in dgit 11.0 has caused the Debian Bug report #1033503, regarding dgit autopkgtests broken by git 2.40 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 ow...@bugs.debian.org immediately.) -- 1033503: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1033503 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
--- Begin Message ---Package: dgit Version: 10.7 Control: affects -1 git Some of dgit's tests create strange git objects, to test error handling. For example, to avoid a repetition of #849041. git 2.40, just uploaded to unstable, has this change: | * "git hash-object" now checks that the resulting object is well | formed with the same code as "git fsck". | (merge 8e4309038f jk/hash-object-fsck later to maint). This was probably a good idea. So, dgit's tests need to be updated. Normally I would file this bug as RC and make the necessary changes. However, we are currently in the freeze for bookworm. Information on tracker.d.o suggests that git is not going to migrate to bookworm anyway, without an unblock from the release team. I don't see an unblock request in https://bugs.debian.org/release.debian.org . Release team: do you think we (dgit maintainers) should update the test suite now, for bookworm ? The changes would be limited to tests, but the new checks in git mean we'll need to take a different approach for some of them, which might be complex or messy. Unhelpfully, there is also #1032826, which prevents "dgit import-dsc" working for the current git.dsc in bookworm. I think this situation is RC. I haven't filed a bug against src:git because I think we can fix this just by changing the infrastructure - I'm talking to DSA about this - but if that turns out to be impossible, we may need to upload a no-source-changes src:git :-/. Thanks for everyone's attention and advice/opinions. Thanks, Ian. -- Ian Jackson <ijack...@chiark.greenend.org.uk> These opinions are my own. Pronouns: they/he. If I emailed you from @fyvzl.net or @evade.org.uk, that is a private address which bypasses my fierce spamfilter.
--- End Message ---
--- Begin Message ---Source: dgit Source-Version: 11.0 Done: Ian Jackson <ijack...@chiark.greenend.org.uk> 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 1033...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Ian Jackson <ijack...@chiark.greenend.org.uk> (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 ftpmas...@ftp-master.debian.org) -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 Format: 1.8 Date: Thu, 15 Jun 2023 00:53:22 +0100 Source: dgit Architecture: source Version: 11.0 Distribution: unstable Urgency: medium Maintainer: Ian Jackson <ijack...@chiark.greenend.org.uk> Changed-By: Ian Jackson <ijack...@chiark.greenend.org.uk> Closes: 904969 959760 1033503 Changes: dgit (11.0) unstable; urgency=medium . Bugfix with compatibility implications: * Pass --no-source-only-changes to sbuild (when building binaries). Fixes operation with SOURCE_ONLY_CHANGES locally overridden. (Incompatible with sbuild <0.78; to work around, say dgit --sbuild!:--no-source-only-changes.). [Report from Sean Whitton] Closes: #904969. . Documentation: * dgit-maint-{merge,rebase}(7): Cross-reference to gitrevisions(7). [Sean Whitton, Ian Jackson] Closes: #959760. . Removal: * Abolish dgit-badcommit-fixup (the remedial script for #849041). If ancient repositories are found which need fixing, install dgit.deb 10.7 or earlier (eg from Debian bookworm and earlier). . Testing; * Tests: work around git changes in 2.40 relating to commit verification. Skipping tests involving now-uncreatable objects. Closes: #1033503. Checksums-Sha1: 532975d4af908f4286b1ffa2a0fa1d250b1c2b2a 1856 dgit_11.0.dsc 9e4280c679be31334acf0c6d511ce8f113fc69b2 681195 dgit_11.0.tar.gz Checksums-Sha256: 47cf0ec76095bd3c0ef4c338ecd5d4244103a6e0149144638e1f92749d1b57ce 1856 dgit_11.0.dsc 8f995919904e1f2a124cb30fdbdaa9fc3dc1e3b351b61e734e56932944e874e3 681195 dgit_11.0.tar.gz Files: 8e1c04d85f2ca3708edb662a1337aeb3 1856 devel optional dgit_11.0.dsc 0b7900588b805ff31406ef013ffc8272 681195 devel optional dgit_11.0.tar.gz -----BEGIN PGP SIGNATURE----- iQEzBAEBCAAdFiEEVZrkbC1rbTJl58uh4+M5I0i1DTkFAmSKU5gACgkQ4+M5I0i1 DTkQAwgAlxpsJZVmb/jRjz1AI16uN+6VV8CW7Htuy9rBxW3DdR4RhPKagbFqWbOR cxeeuJanXYPUXkNiI8NYaA1hoa9RNO+zMXEm5S0tCXNROzfpdrAAEZJoiVuYwDNW PRhd22WxLpYn+2Phr6pGgirHto295FbJpno0HFpyLTJ8xtHrsQFvYIFyi0ZX+0yJ AyrQ+hLBJepdXQUGsMWGZjz0mSexgilifExM3XbDOsIymcy7O2xop6YJVTsHbOdx xjEYvWypevx3kMEVbdqQ3na9GgDbTR5FlUNvdVgXFhnvAdOvRIODKehxqoH7M+9Q PQIMdP1yfHrYaSdqtH1sPoMwRxcgXA== =EXjh -----END PGP SIGNATURE-----
--- End Message ---
