El 5/5/25 a las 21:54, Pirate Praveen escribió:
On 05/05/2025 4:28 pm, Santiago Vila wrote:
When I'm debugging a package, I usually work in a directory-based chroot
(created with debootstrap). If I had to drop internet access, I would have
to use firewall rules or just unplug the cable, which would make other
tasks requiring internet in my computer not to work at the same time.
I would consider the real goal to be ensuring that the package
builds the same regardless of network being present or not,
and also regardless of the way you choose to build the package,
be it dpkg-buildpackage in a chroot, sbuild with unshare, sbuild
with schroot, pbuilder, etc. It's a requirement which helps
reproducibility.
at least in this specific instance, the final package remains the same
irrespective of whether you have internet access or not. So this does not
affect reproducibility at all. You just test more functionality if internet is
present, that is all.
On the contrary, in this specific instance the final outcome changed completely.
- In the buildds -> the package built fine because network access was forbidden
- In my archive rebuild setup -> the package failed to build because it was
accessing
the network and the service was giving 500 Error.
If we can't be sure if the package will build ok or not depending on external
factors,
then the package does not really contain the complete source code, so this is
not
only a reproducibility problem but also a DFSG-compliance issue.
Not only the .deb should always be the same, also the tests which pass or not
pass
should also be the same.
Thanks.
