Hi we've been made aware on #d-release that my hints broke debootstrap. I am working through the remaining packages that are relevant for debootstrap, but it takes some time.
On 2024-04-26 18:35:59 +0200, Cyril Brulebois wrote: > 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. > > Note: I've limited my exploration to amd64, which kept me busy already… > > An obvious first problem is coreutils, which picked a Pre-Depends on > libssl3 (not the t64 one), which… disappeared from testing between the > 2024-04-24 14:58:20 and 2024-04-24 20:51:02 (checked by looking at > Packages.gz for amd64 via snapshot.debian.org). The core problem is that deboostrap fails to understand versioned Provides. libssl3t64 on amd64: Package: libssl3t64 Source: openssl Version: 3.2.1-3 Installed-Size: 7302 Maintainer: Debian OpenSSL Team <pkg-openssl-de...@alioth-lists.debian.net> Architecture: amd64 Replaces: libssl3 Provides: libssl3 (= 3.2.1-3) Depends: libc6 (>= 2.34), libzstd1 (>= 1.5.5), zlib1g (>= 1:1.1.4) Breaks: libssl3 (<< 3.2.1-3), openssh-client (<< 1:9.4p1), openssh-server (<< 1:9.4p1), python3-m2crypto (<< 0.38.0-4) Description-en: Secure Sockets Layer toolkit - shared libraries This package is part of the OpenSSL project's implementation of the SSL and TLS cryptographic protocols for secure communication over the Internet. . It provides the libssl and libcrypto shared libraries. Description-md5: 88547c6206c7fbc4fcc7d09ce100d210 Multi-Arch: same Homepage: https://www.openssl.org/ Section: libs Priority: optional Filename: pool/main/o/openssl/libssl3t64_3.2.1-3_amd64.deb Size: 2243528 MD5sum: 8919d70ec8be690308f3970878113b1a SHA256: 84bf4abab84da9c8a2bdd2b161ae02d4de78657fe77483bf7656d8a368344add So that britney dropped libssl3 from testing on !armel !armhf is fine in genaral, but britney does not account for deboostrap not supporting versioned Provides. That's the same for all the other packages involved in bootstraping. > 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). I am currently looking into making coreutils and systemd (which needs glib2.0) migrate. I hope to have it back in a debootstrapable-step after the weekend. If you are aware of more apckages that need help, please let us know. Cheers -- Sebastian Ramacher
