Hi Hilmar,

* Preuße, Hilmar <[email protected]> [2026-06-26 23:58]:
I've merged the commit, run a test build and tested using diffoscope. The most striking difference is that /usr/include/proftpd/Make.rules now lists the user, which called sbuild:

INSTALL_USER=hille
INSTALL_GROUP=hille

I guess the official builders would list nobody/nogroup here.

Sorry, I forgot to mention and it will be sbuild/sbuild.

For the Debian packages this does not matter, as we use a customised Make.rules file. For others, let's see.

That was also my conclusion.


* Preuße, Hilmar <[email protected]> [2026-06-27 00:50]:
Am 24.06.2026 um 14:47 schrieb Jochen Sprickerhof:
The problem is that it uses Rules-Requires-Root: binary-targets and with
that fakeroot and that influences the build result. As the fakeroot
package is not recorded in the buildinfo file, we can't use it during
the rebuild and the generated binaries differ.


Does it make sense to figure out, why it is not in the buildinfo...or eventually hard code the BD on fakeroot? Should an "Rules-Requires-Root: binary-targets" automatically trigger installation of fakeroot?

Not really, see my explanation in:

https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1140645#15

Note that we reproduced over 98% of testing already and up to now only found three packages that have fakeroot problem (proftpd-dfsg, procmail and debian-installer (fixed in git)).

Cheers Jochen

Attachment: signature.asc
Description: PGP signature

Reply via email to