Package: release.debian.org
Severity: normal
User: release.debian....@packages.debian.org
Usertags: transition
(please explain about the transition: impacted packages, reason, ...)
Dear Release team,
some time ago I have uploaded version 1.9.16 of grib_api to sid.
Since upstream has chosen to embed the full package version in the shlib
name via "libtool -release", this means that all reverse dependencies of
grib_api need to be recompiled with the new version to update their
dependencies.
The new shlib package is libgrib-api-1.9.16, which should eventually
replace libgrib-api-1.9.9.
Unfortunately I didn't realise I had to arrange a transition before
uploading the package. That is my fault, sorry.
Reverse dependencies according to dak rm -R -n grib-api (arch lists removed):
cdo: libcdi0
gnudatalanguage: gnudatalanguage
magics++: libmagplus3
pygrib: python-grib
ruby-grib: ruby-grib
# Broken Build-Depends:
cdo: libgrib-api-dev
emoslib: libgrib-api-dev (>= 1.9.9~)
gnudatalanguage: libgrib-api-dev
magics++: libgrib-api-dev
pygrib: libgrib-api-dev
ruby-grib: libgrib-api-dev
libgrib-api-tools
The grib_api API is stable enough, so a binary NMU of all reverse
dependencies should do.
Ben file (as far as I can understand how it works, untested):
is_affected = .depends ~ /libgrib-api-1.9.9|libgrib-api-1.9.16/
is_good = .depends ~ /libgrib-api-1.9.16/
is_bad = .depends ~ /libgrib-api-1.9.9/
Thank you,
Enrico
-- System Information:
Debian Release: wheezy/sid
APT prefers testing
APT policy: (500, 'testing')
Architecture: amd64 (x86_64)
Kernel: Linux 3.2.0-2-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
--
To UNSUBSCRIBE, email to debian-release-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive:
http://lists.debian.org/20120521140739.16954.42979.report...@viaza.enricozini.org
