Package: dpkg Version: 1.22.13 Control: block 1092190 by -1 Hi.
(Firstly, I should say thank you very much to Niels Thykier for your work on Rules-Requires-Root. Tidying this up is a big job which you've been doing very well. Speaking personally I have really appreciated the interactions I've had with you over my packages. Now, though, I'm afraid I come with the change request:) It seems likely to me that there will continue to be packages in the wild which this behavioural change will break - particularly including packages not part of Debian, packages from old Debian release, and perhaps whole derivative distros. In order to allow us to build old packages with new tooling, or out-of-distro packages, or whatever, I think dpkg-buildpackage should have a way to request the previous (bookworm-and-earlier) behaviour. I looked through the manpage and found --rules-requires-root, but that says that it disregards the Rules-Requires-Root field entirely, which isn't right. (And might also break things...) Could we please have a command line option to just change the default, so that trixie's dpkg-buildpackage can be used in circumstances where bookworm's would have worked ? We should probably consider whether we want to make this behaviour controllable by an environment variable, as well. That way a program which is trying to work with various different dpkg-buildpackage version (eg a CI job that runs with different images) wouldn't have to probe for the option. I'm filing this bug as "normal" because I think that's warranted by the behavioural regression for out-of-Debian users. Thanks for your attention. 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.
