Re: Making trixie debootstrap-able again?

[Cyril Brulebois]

Hi,

Cyril Brulebois  (2024-04-26):
> I'm not sure how we reached this situation but there are a bunch of
> packages in trixie that are not in a suitable state. To reproduce, a
> simple `debootstrap trixie /tmp/trixie` on amd64 is sufficient.

That works again, presumably following the configuration changes in
britney made it complete again, finally migrating stuff.

> Note: I've limited my exploration to amd64, which kept me busy
> already…

That proviso is still true.


Cheers,
-- 
Cyril Brulebois (k...@debian.org)
D-I release manager -- Release team member -- Freelance Consultant


signature.asc
Description: PGP signature

Re: Making trixie debootstrap-able again?

[Holger Levsen]

hi kibi,

fwiw, bootstraping trixie still works using mmdebstrap, while it fails
with debootstrap and cdebootstrap.

I've notified #-release about the debootstrap breakage on the 24th
and added that mmdebstrap was still working on the 25th...

https://jenkins.debian.net/job/reproducible_mmdebstrap_trixie/ etc show
this nicely.


-- 
cheers,
Holger

 ⢀⣴⠾⠻⢶⣦⠀
 ⣾⠁⢠⠒⠀⣿⡁  holger@(debian|reproducible-builds|layer-acht).org
 ⢿⡄⠘⠷⠚⠋⠀  OpenPGP: B8BF54137B09D35CF026FE9D 091AB856069AAA1C
 ⠈⠳⣄

If it feels like we’re breaking climate records every year, it’s because we are.


signature.asc
Description: PGP signature

Re: Making trixie debootstrap-able again?

[Cyril Brulebois]

Cyril Brulebois  (2024-04-26):
> Anyway, I wanted to see if suggesting (I wouldn't go as far as requesting
> because I'm really not sure this would be the right course of action, more
> details below) a new binNMU of coreutils within testing would be
> sufficient to make trixie debootstrap-able again, I built a modified
> repository, and try debootstrap against it, only to find more problems:
>  - util-linux binaries (e.g. fdisk) depend on libreadline8, which is gone.
>  - iproute2 depends on libtirpc3, which is gone.
> 
> I guess the reason is similar, the former I tracked down to the same block
> of hints as before:
> 
> # 2024-04-23; done 2024-04-25
> # help some t64 packages migrate
> […]
> force-hint readline/8.2-4
> 
> The latter I tracked down to thisone:
> 
> # 2024-04-23; done 2024-04-26
> # get t64 unstuck
> urgent libtirpc/1.3.4+ds-1.3
> force-hint libtirpc/1.3.4+ds-1.3
> 
> Again, I have absolutely no clue regarding the best course of action at
> this point. I can't even perform clean builds to check what a binNMU in
> testing would look like, as I can't debootstrap a clean environment (and
> therefore only tested rebuilds in an existing, devel-oriented, unclean
> trixie chroot).

Looks like I forgot to mention the final results: with the modified
repository stuffed with (unclean) rebuilds of coreutils, iproute2, and
util-linux, I'm able to debootstrap trixie again.

(I've hacked a repository together from scratch, based on the failed
debootstrap's apt cache, adding rebuilt packages, and injecting new
dependencies manually; I could redo that cleanly by forking trixie's
current Packages instead, but I'm not sure it's really worth the
efforts, esp. given rebuilt packages are “tainted” anyway.)


Cheers,
-- 
Cyril Brulebois (k...@debian.org)
D-I release manager -- Release team member -- Freelance Consultant


signature.asc
Description: PGP signature