[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: Making trixie debootstrap-able again?




On 27/04/2024 00:14, Sebastian Ramacher wrote:
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.

Other packages that need help (discovered while trying to rebuild packages for the armhf architecture).

Source package man-db. man-db is a dependency of debhelper, and the version in testing depends on libgdbm6, preventing build for any package that depend on libgdbm6t64.

```
$ rmadison man-db
man-db     | 2.12.0-3         | testing                  | source, amd64, arm64, armel, armhf, i386, mips64el, ppc64el, s390x
man-db     | 2.12.1-1         | unstable                 | source, amd64, arm64, armel, armhf, i386, mips64el, ppc64el, riscv64, s390x
```

Binary packages libbpf1 and libbpf-dev, the latest binNMU didn't migrate to testing for armel and armhf, and prevent rebuilding iproute2

```
$ rmadison libbpf-dev
libbpf-dev | 1:1.3.0-2+b1      | testing            | amd64, arm64, i386, mips64el, ppc64el, s390x
libbpf-dev | 1:1.3.0-2+b1      | unstable           | amd64, arm64, armel, armhf, i386, mips64el, ppc64el, riscv64, s390x
```

Best,


-- 
Arnaud Rebillout / OffSec / Kali Linux Developer

Reply to: