Bug#796491: marked as done (nmu: magics++_2.24.7-6)
Your message dated Sat, 22 Aug 2015 12:05:58 +0200
with message-id <55D84986.3010406@xs4all.nl>
and subject line Re: Bug#796491: nmu: magics++_2.24.7-6
has caused the Debian Bug report #796491,
regarding nmu: magics++_2.24.7-6
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 owner@bugs.debian.org
immediately.)
--
796491: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=796491
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message ---
Package: release.debian.org
Severity: normal
User: release.debian.org@packages.debian.org
Usertags: binnmu
nmu magics++_2.24.7-6 . amd64 . unstable . -m "Rebuild with netcdf-cxx-legacy"
It was built with an outdated environment without all the new netcdf
packages on am64 by the maintainer, on the buildds the builds used the new
netcdf packages.
This is required for the netcdf transition (#791215), because magics++
blocks its reverse dependencies in the netcdf transition.
Kind Regards,
Bas
--- End Message ---
--- Begin Message ---
On 22-08-15 09:01, Bas Couwenberg wrote:
> nmu magics++_2.24.7-6 . amd64 . unstable . -m "Rebuild with netcdf-cxx-legacy"
>
> It was built with an outdated environment without all the new netcdf
> packages on am64 by the maintainer, on the buildds the builds used the new
> netcdf packages.
>
> This is required for the netcdf transition (#791215), because magics++
> blocks its reverse dependencies in the netcdf transition.
The NMU is no longer required, it was much faster to manually BinNMU
magics++ using the amd64 porterbox.
Kind Regards,
Bas
--
GPG Key ID: 4096R/6750F10AE88D4AF1
Fingerprint: 8182 DE41 7056 408D 6146 50D1 6750 F10A E88D 4AF1
--- End Message ---
Reply to: