Your message dated Sun, 27 May 2012 12:20:36 +0200
with message-id <20120527102035.gr8...@mraw.org>
and subject line Re: Bug#673800: transition: grib-api
has caused the Debian Bug report #673800,
regarding transition: grib-api
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)
--
673800: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=673800
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
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
--- End Message ---
--- Begin Message ---
Cyril Brulebois <k...@debian.org> (27/05/2012):
> They stay because of:
> > # Broken Depends:
> > magics++: libmagplus3 [amd64 armel armhf i386 ia64 kfreebsd-amd64
> > kfreebsd-i386 mipsel powerpc s390]
>
> I've just moved the tracker from ongoing to finished, and I'll
> investigate this magics++ thing later on.
Easily fixed, I've hinted magics++ this way:
| # 20120527
| # RC bug fix doesn't mean 10 days:
| age-days 3 magics++/2.14.11-1
→
| trying: magics++
| accepted: magics++
Old binaries are gone, closing accordingly.
Mraw,
KiBi.
signature.asc
Description: Digital signature
--- End Message ---
