Bug#577209: nmu: Please schedule binNMUs against libdbi-perl
Package: release.debian.org
Severity: normal
User: release.debian.org@packages.debian.org
Usertags: binnmu
User: release.debian.org@packages.debian.org
Usertags: binnmu
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256
It looks like the arch:any packages build-depending on libdbi-perl
need binNMUs against the new libdbi-perl 1.610.90-1.
Please note that libdbd-mysql-perl already saw a sourceful upload;
I've now locally verified that libdbd-sqlite3-perl errors out and
works after a rebuild.
If my grep-dctrl foo worked this should be:
nmu libdbd-odbc-perl_1.23-1 . ALL . -m "Rebuilt against new libdbi-perl."
nmu libdbd-pg-perl_2.17.1-1 . ALL . -m "Rebuilt against new libdbi-perl."
nmu libdbd-sqlite2-perl_2:0.33-8 . ALL . -m "Rebuilt against new libdbi-perl."
nmu libdbd-sqlite3-perl_1.29-1 . ALL . -m "Rebuilt against new libdbi-perl."
nmu libdbd-sybase-perl_1.00-3 . ALL . -m "Rebuilt against new libdbi-perl."
nmu libdbix-oo-perl_0.0.9-2 . ALL . -m "Rebuilt against new libdbi-perl."
nmu libpoe-component-dbiagent-perl_0.26-1 . ALL . -m "Rebuilt against new libdbi-perl."
nmu libtfbs-perl_0.5.svn.20091128-1 . ALL . -m "Rebuilt against new libdbi-perl."
nmu olive_1.3-3 . ALL . -m "Rebuilt against new libdbi-perl."
nmu sympa_5.4.7-1 . ALL . -m "Rebuilt against new libdbi-perl."
Cheers,
gregor, who hopes he got his first binNMU request right
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.10 (GNU/Linux)
iQIcBAEBCAAGBQJLwH9EAAoJELs6aAGGSaoGY1oQAItBdW+SUNNWwPnIdPfEu95N
0x/C+USGh2d6Q4BfGiRGPgaIl3WYVyrrITwYPdSp5LI5z2ouZ0nhWK2Xb3DW1rc7
zi5D86XSIKER83bPVD2qd5AfDf9x1FXhrq73OGIIbmD8A4S+Wt09L8pM5foEEEJp
AtwT575FoSmlVclJt63ByBzbm8t2NrxZiwQu+aeNQQ+BcBF6BUmmbge5k9xKbP26
FT/lsvaQKHRtkEnWcVxxzpGUcPXB1PyutVW4XAPghD3h/+7iEA4EJ+1EGa5jR6L2
AoqoWDPQUaGYnBkxz4fkdNVq5Vpjm88t06SVB4ofqgFKBN1mdPlL2IPgcJOxfBD8
O7zMTyTxq3pdfYjmRVhZfunp4AcBU9YfdmAB4hVefyEBte+hnymTWn+DexokDaVi
6PO+ipHg4qVkqcnfok1AmY2QBhvs/n4w2D/npUM5ghz3/O8exDC9EBf/3YbmgiKN
jwFPGDX/Yd1vuFDQ/aCPS9gI9GlxlFHYocjYLWtNHPng7CMAy9ssrBILvzA3bI+A
f9qwmFJa2BlJxfeJi+LEWQ/PPdl1C59xeL3hGH3+Ro5kJQAVFuyGC4eK4BNPmG/3
1f0O1eC4+8joRDzmcaKuMfnhHMRvrvhnpImRD2iro5jX4y9E5lv0BUWk7JBks7eU
dG8KBKCe6ZB4w28MDnBb
=R2TB
-----END PGP SIGNATURE-----
Reply to: