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

Bug#632467: buildd.debian.org: Please update perl-* in all unstable chroots



Package: buildd.debian.org
Severity: normal

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256

We have at least 3 packages (libclass-xsaccessor-perl,
libdevel-cover-perl, libpar-packer-perl) that have
    Depends: perl (>= $currentversion), perl (<< $nextversion)
because they need the exact perl version at runtime that was used
during build.

So after the upload of perl 5.12.4 I requested binNUMs (#632307)
which were promptly scheduled (thanks, Adam) and also promptly done
by the buildds.

Unfortunately the results are not as expected: When I look at
http://packages.debian.org/sid/libclass-xsaccessor-perl and the logs
at https://buildd.debian.org/status/package.php?p=libclass-xsaccessor-perl
I see that only amd64 and kfreebsd-i386 have picked up the new
dependencies, and all other buildds are still using some older perl
version.

Would it be possible to update the unstable chroots to the version of
perl* that's actually in unstable, i.e. 5.12.4-1 for all release
architectures?

Or is there some other way to handle this situation, now or in
general?

Cheers,
gregor


-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.11 (GNU/Linux)

iQIcBAEBCAAGBQJODxo/AAoJELs6aAGGSaoG774P/jtKLDoh4vuMtKvI9sc8VCkw
ILq+Zl3/QS546dLnQ5/cKN6thOAsht3R6cpkmygnRA+DMilBgeOKGOhqiNi8IhdE
Qw4VADip+Aq6cD7J90j12pLpPxeismZIX9UiPFqzGO9eG3QvDvp3/COKJzoCTnjT
4crM0We1YNXwNufIGjCChgke5nqdJD//+zBVQbtOefF56PIEJwG50Lz3ei88unf6
/ND5Y83esnRTdl05C/ul0Ay039T/FOI98DylTkkIwpy0soz+HXjQL+LrZ+K9eLzC
itgeiCcGWNA8TFMuzk+4rb+O8ps4zYozV0/D72ZstIhfUoYtMcNbciLU2yFxdySb
qhyMH1atm2JDSXZk5QTyWqwfwTHYwuK0rM1IX10ux5aAM7SIytWrtWrVCKv7xTn/
VquWYPzp2brlKR1NIm/OxlsaecQcGo+7JvtHkbIaBEBbhu7AEb+8g9Q/JcG/sSmO
rnRijEKGrEHMvJuB9iwEYkm38/G+h/SrH4yt6l0ekmdrNPWEssS0fvO1WzvuOaBh
d1aJFoUdGMlTEulvZ5QdWWM7aLcmR7RPNFJL6V55/oBeKrMwroeoFsV9Bxj8KN0M
ZUYKn1wuGYnoqiWDPaLnmU8Ktl5I5O4Pk+oWgf17saSTyXFCmwxgRb31R4CF8fX6
tPNedWdDofDjF9hQddH2
=liLT
-----END PGP SIGNATURE-----



Reply to: