Your message dated Mon, 20 Jan 2020 20:12:13 +0200
with message-id
<CAM8zJQuOhSOz6OR5eUc5=4F7Pd=ytpgcpyw4h7wno3js9sc...@mail.gmail.com>
and subject line Re: Bug#949353: nmu: elastix_4.9.0-1 and nifti2dicom_0.4.11-1
has caused the Debian Bug report #949353,
regarding nmu: elastix_4.9.0-1 and nifti2dicom_0.4.11-1
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.)
--
949353: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=949353
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: binnmu
nmu elastix_4.9.0-1 . amd64 i386 . unstable . -m "Rebuild with libgdcm3.0 and
libinsighttoolkit4.13"
nmu nifti2dicom_0.4.11-1 . amd64 i386 . unstable . -m "Rebuild with libgdcm3.0
and libinsighttoolkit4.13"
Seem to be remnants of an incomplete transition 3 months ago.
--- End Message ---
--- Begin Message ---
On Mon, 20 Jan 2020 at 07:51, Adrian Bunk <b...@debian.org> wrote:
> nmu elastix_4.9.0-1 . amd64 i386 . unstable . -m "Rebuild with libgdcm3.0 and
> libinsighttoolkit4.13"
> nmu nifti2dicom_0.4.11-1 . amd64 i386 . unstable . -m "Rebuild with
> libgdcm3.0 and libinsighttoolkit4.13"
>
> Seem to be remnants of an incomplete transition 3 months ago.
Scheduled. I'm not sure if nifti2dicom will migrate with the arch all
binaries not being built on a buildd, but I expect your NMU from
#906706 to fix that.
--- End Message ---
