Control: severity -1 normal Hi!
On Wed, 2025-02-12 at 04:16:29 +0100, Thorsten Glaser wrote: > Source: dpkg > Version: 1.22.13 > Severity: serious > Justification: Policy §5.6.31 > X-Debbugs-Cc: t...@mirbsd.de > dpkg 1.22.13 implemented a backwards-incompatible change, > violating Policy (which states the default value is most > certainly *not* “no”) and breaking builds of packages. This was proposed, coordinated in debian-devel and debian-release, and a MBF done, and then the changed was deployed: https://lists.debian.org/debian-devel/2024/11/msg00535.html https://lists.debian.org/debian-devel/2024/12/msg00029.html https://lists.debian.org/debian-devel/2024/12/msg00358.html https://lists.debian.org/debian-devel/2025/01/msg00022.html https://lists.debian.org/debian-release/2024/12/msg00435.html https://lists.debian.org/debian-release/2025/01/msg00028.html https://lists.debian.org/debian-release/2025/01/msg00203.html While the work to make packages build w/o root has been going on for years now, with the conditions where this applies having been tightened increasingly over time, culminating in this change. In this case policy is just lagging, #1092193 (in general policy is not prescriptive, it follows practice). > dpkg (1.22.13) unstable; urgency=medium > - Dpkg::BuildDriver::DebianRules: Change default R³ value to «no». > > I’ve confirmed that an explicit “Rules-Requires-Root: binary-targets” > ceteris paribus fixes the build, so the breakage was indeed introduced > by this dpkg change. Please revert it. Is this with an out of archive package? If so dpkg-deb should have warned about the problem, otherwise this was then probably missed in one of the mass rebuilds, but I'd be happy to try make this change more smooth. I was pondering about perhaps adding a NEWS entry in the dpkg-dev package, although that still does not help with CI systems and similar. (That's why I'm not closing this right away.) There is also #1092193, which I need to come back to, but in my mind this would be more in the direction as mentioned above, of trying to give better notice or similar. On Thu, 2025-02-13 at 10:01:39 +0100, Gioele Barabucci wrote: > shouldn't this bug be filed instead against debian-policy for not having > recorded the (silent) consensus [1] reached between November 2024 and > January 2025? > > [1] > https://linux.debian.devel.narkive.com/7bK6YbqZ/mbf-proposing-rules-requires-root-no-being-the-new-default This was already filed, ah, and the change is already in the «next» debian-policy branch, commit 7ef35446b3e7ec8fcb823924d160fa2b168a77c9. Thanks, Guillem
