Some powerpc buildd chroots are ancient

[John Paul Adrian Glaubitz]

Hello,

https://buildd.debian.org/status/fetch.php?pkg=itcl4&arch=powerpc&ver=4.3.1-1&stamp=1729591114&raw=0
Package versions: ... gcc_4:13.2.0-7 ... perl_5.38.2-5
Still using gcc 13 implies the chroot hasn't been regenerated since
early July.
Still using perl 5.38 means that for some perl packages every package
built on the buildd will revert a perl 5.40 transition rebuild.

I have checked the dsa-puppet configuration and couldn't an obvious problem.

But I'm started to get tired with all these problems and having to solve these
on my own. I want to nuke this from orbit.

Sorry, I'm frustrated.

Adrian

[John Paul Adrian Glaubitz]

Hi Adrian,

https://buildd.debian.org/status/fetch.php?pkg=itcl4&arch=powerpc&ver=4.3.1-1&stamp=1729591114&raw=0
Package versions: ... gcc_4:13.2.0-7 ... perl_5.38.2-5
Still using gcc 13 implies the chroot hasn't been regenerated since
early July.
Still using perl 5.38 means that for some perl packages every package
built on the buildd will revert a perl 5.40 transition rebuild.

I have updated the chroots manually now as a workaround.

Could you trigger a binNMU for all the affected Perl packages?

My first analysis shows that the issue must be in setup-all-dchroots as
manually passing "-a powerpc" to the debootstrap call fixes the issue.

https://salsa.debian.org/debian-ports-team/dsa-puppet/-/blob/master/modules/schroot/files/setup-all-dchroots?ref_type=heads

Thanks,
Adrian

[Adrian Bunk]

Post by John Paul Adrian Glaubitz
..

https://buildd.debian.org/status/fetch.php?pkg=itcl4&arch=powerpc&ver=4.3.1-1&stamp=1729591114&raw=0
Package versions: ... gcc_4:13.2.0-7 ... perl_5.38.2-5
Still using gcc 13 implies the chroot hasn't been regenerated since
early July.
Still using perl 5.38 means that for some perl packages every package
built on the buildd will revert a perl 5.40 transition rebuild.

I have updated the chroots manually now as a workaround.

Thanks.

Post by John Paul Adrian Glaubitz
Could you trigger a binNMU for all the affected Perl packages?

I already did that earlier (with --extra-depends), the last one was
libberkeleydb-perl.

Post by John Paul Adrian Glaubitz
...
Thanks,
Adrian

cu
Adrian