Re: Tooling for rebuilding outdated Built-Using
On Thu, Jun 19, 2025 at 11:47:10PM +0200, Sylvain Beucler wrote:
>...
> AFAICS it's overall consistent with the other tooling, except for the extra
> 'supermin' (which doesn't seem to contain static executables).
Embedded in the supermin binary is a statically linked init.
The more general point is that it would be wrong to assume that
Built-Using would be the same on all architectures, in the supermin
case static linking happens with either musl or glibc depending on
the architecture.
> On 18/06/2025 19:31, Adrian Bunk wrote:
> > Note that in LTS you will afterwards need either either manual
> > Build-Depends on the new version (if making a manual upload) or
> > extra-depends (when making a normal binNMU) since the pre-LTS
> > version of the glibc packages is in the chroots.
> >
> > In the latter case any future DLAs (e.g. for bash or qemu) would again
> > be built against the pre-LTS glibc.
> >
> > A solution for that would be either generating bullseye-security chroots
> > in setup-all-dchroots and using them, or dist-upgrade at the start of
> > the build.
>
> Thanks for the info!
>
> Is this specific to essential packages pre-installed in the buildd chroots?
It's specific to everything pre-installed in the buildd chroots,
in addition to essential packages this also includes build essential
packages as well as apt, ca-certificates and fakeroot that are neither.
> Cheers!
> Sylvain
cu
Adrian
Reply to: