Your message dated Tue, 9 Jun 2026 05:02:02 +0200
with message-id <[email protected]>
and subject line Re: Bug#1095791: dpkg: incompatible and Policy-violating R³
default change breaks packages’ builds
has caused the Debian Bug report #1095791,
regarding dpkg: incompatible and Policy-violating R³ default change breaks
packages’ builds
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.)
--
1095791: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1095791
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Source: dpkg
Version: 1.22.13
Severity: serious
Justification: Policy §5.6.31
X-Debbugs-Cc: [email protected]
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.
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.
--- End Message ---
--- Begin Message ---
Hi!
Closing this now.
Thanks,
Guillem
--- End Message ---
