Your message dated Tue, 14 Feb 2012 14:07:45 +0100
with message-id <[email protected]>
and subject line Re: Bug#657288: transition: gdcm
has caused the Debian Bug report #657288,
regarding transition: gdcm
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 [email protected]
immediately.)
--
657288: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=657288
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: release.debian.org
Severity: normal
User: [email protected]
Usertags: transition
GDCM 2.2.0 introduces a new ABI, as seen on #655783 and al.
Since API (whatever that means for C++) is preserved, would it be a good time to
- move gdcm 2.2.0 from experimental to unstable
- binNMU insighttoolkit
igstk is not using gdcm API and thus does not required a rebuild
Thanks
-- System Information:
Debian Release: 6.0.1
APT prefers stable-updates
APT policy: (500, 'stable-updates'), (500, 'stable'), (200, 'testing'), (100,
'unstable')
Architecture: amd64 (x86_64)
Kernel: Linux 2.6.32-5-amd64 (SMP w/2 CPU cores)
Locale: LANG=en_US.utf8, LC_CTYPE=en_US.utf8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
--- End Message ---
--- Begin Message ---
Mathieu Malaterre <[email protected]> (25/01/2012):
> GDCM 2.2.0 introduces a new ABI, as seen on #655783 and al. Since API
> (whatever that means for C++) is preserved, would it be a good time to
> - move gdcm 2.2.0 from experimental to unstable
> - binNMU insighttoolkit
>
> igstk is not using gdcm API and thus does not required a rebuild
AFAICT: Everything's done, closing.
Mraw,
KiBi.
signature.asc
Description: Digital signature
--- End Message ---
