Your message dated Sun, 29 Jan 2017 20:49:18 +0000 with message-id <e1cxwpw-0005dg...@fasolo.debian.org> and subject line Bug#852820: fixed in dpkg 1.18.21 has caused the Debian Bug report #852820, regarding Testsuite-Restrictions field is hard to use 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.) -- 852820: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=852820 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
--- Begin Message ---Package: dpkg-dev Version: 1.18.19 >From the patch from Iain Lane: +This field declares the comma-separated union of all test restrictions +(\fBRestrictions\fP fields in \fIdebian/tests/control\fP file). This is quite awkward to use correctly, and is a hazard to correct implementation. For example, dgit's debian/tests/control contains several tests marked with Dgit-specific Restrictions with x-dgit-... names. The result is that with 1.18.10ubuntu1, we would see this in dgit's .dsc: Testsuite-Restrictions: x-dgit-intree-only x-dgit-git-only x-dgit-schroot-build If not interpreted very carefully, this would give a test suite runner the erroneous impression that none of the tests can be run. Also, Iain's stated use case in #847926 does not require anything new in the .dsc and hence Sources.gz. All that is required to get the full information (debian/tests/control) is to extract the source package. That extraction of the source package has to be done anyway no matter how the tests will be run. If we do need more information in Sources.gz then maybe the set of combinations of restrictions ought to be listed. But then the features might be useful too. I'm sorry that I'm reporting this bug now, due to happening to see the message on debian-dpkg. But really I think: * Changes to the .dsc format and hence to the Sources format should be discussed more widely than a bug on debian-dpkg. * Changes to the handling of autopkgtest (DEP-8) metadata should be discussed on autopkgtest-devel (or other DEP-8 related places). Thanks, 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.
--- End Message ---
--- Begin Message ---Source: dpkg Source-Version: 1.18.21 We believe that the bug you reported is fixed in the latest version of dpkg, 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 852...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Guillem Jover <guil...@debian.org> (supplier of updated dpkg 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: SHA512 Format: 1.8 Date: Sun, 29 Jan 2017 20:29:58 +0100 Source: dpkg Binary: dpkg libdpkg-dev dpkg-dev libdpkg-perl dselect Architecture: source Version: 1.18.21 Distribution: unstable Urgency: medium Maintainer: Dpkg Developers <debian-d...@lists.debian.org> Changed-By: Guillem Jover <guil...@debian.org> Description: dpkg - Debian package management system dpkg-dev - Debian package development tools dselect - Debian package management front-end libdpkg-dev - Debian package management static library libdpkg-perl - Dpkg perl modules Closes: 852820 Changes: dpkg (1.18.21) unstable; urgency=medium . [ Guillem Jover ] * Revert "Generate Testsuite-Restrictions fields from the test restrictions in dpkg-source into .dsc files". This change is contentious and should have been discussed more widely. Given that this has been live only for a couple of days, the impact should be minimal, but still something to take into account once and if this gets reintroduced. Closes: #852820 * Perl modules: - Map alternative or old ELF machine types to canonical ones. We need those to match on the encoded ABI, otherwise dpkg-shlibdeps will not be able to find the objects. . [ Updated man pages translations ] * German (Helge Kreutzmann). Checksums-Sha1: ec9cc1e1c8e817956c9a31734e34db82317d6f5a 2032 dpkg_1.18.21.dsc 44694e7f43d03b48362713d44207976f202c95a6 4519476 dpkg_1.18.21.tar.xz ba2e3fab059b8a3a8118927006fa5495c5eddf26 7301 dpkg_1.18.21_amd64.buildinfo Checksums-Sha256: 1a1ad2bd0abd5be01b151de19e08e7e735f17760897fe3c1a227cdaeb9ce4ef0 2032 dpkg_1.18.21.dsc 60f29cd0aa0eeb3e470ddc51d44b43fa0d3194c88b1f0cf0f07dfbba58c14e27 4519476 dpkg_1.18.21.tar.xz 075087b2c13988dbeef1ae002a93db3dc9d143cab94bf077cbb413ddba6e0726 7301 dpkg_1.18.21_amd64.buildinfo Files: 770abd5f6ae347748f1394a3bc618fa0 2032 admin required dpkg_1.18.21.dsc a8297e95775624fc8a7b289b61dff0a7 4519476 admin required dpkg_1.18.21.tar.xz 774750cf4c4513fd1ef34473f1e6740d 7301 admin required dpkg_1.18.21_amd64.buildinfo -----BEGIN PGP SIGNATURE----- iQIzBAEBCgAdFiEETz509DYFDBD1aWV0uXK/PqSuV6MFAliOStQACgkQuXK/PqSu V6PGhA//R+RoNYYFGxF2rU5SeRrUmUwe1k6RT38wRww3rtGN8wHK/HpIWwAtpl9n PWrCxzrkHv3M3ve/dtox6RlYUVsmwJ3pU18cPRbU9qVSFVH2F+8z/y+lZAjBPmdY D6+PUEbUAPQKZQi0z6tiY/S8ak2VMkv4PWajMNTwOuSSiikwoQLa+HCM77/7foIo 5Q6J9a/ZpIhYKYRtICCsxW5Eu8PjQ/6M0mHVvslJGOU0mm5tlUVfyk4i5z/B+BSW VASliwKv+4RSSPbias9g1yHEzmJz2hDaePB6w27xMS4g2C+gvRNWMsZm0YmjTgf8 Y28hSTwrBaH6youyM3vJCJbE3tulqo4yUB5H/rqyY0VHSZkDoeyp12nlm/kvhfzp GXoiKUWBc2O3FspyyXzMJKUFaKnCpNiNnLcgy8O0npjkea35jVdENIZEG8DgnlFw ZoJfRQPEmWsicGJHJK/jAEGggkkVsGDWQaEN0oz4PLtvatpN0uCWUV8WK40xHvg1 9ZcUr6hO+oRSDMDKDFdQQsaZmBpdeZh0+r5s8zOeAKOJlS+KHHOnAUAJJ3PBtsmM oSVhE0mwbKVmKh1ZXJa72WgNTaeTGb0EoXQJrGFKkDl3YTzXmeEKP1DnZSD9ZUQO c2E0qY93zHLyWRvpvYXRfnTRAXahrD3OWfWDsfLBpCHMm3+rx+Y= =iqQr -----END PGP SIGNATURE-----
--- End Message ---
