Re: gdcm is marked for autoremoval from testing

To: Debian testing autoremoval watch <debian-release@lists.debian.org>, Debian Med Packaging Team <debian-med-packaging@lists.alioth.debian.org>
Cc: Mathieu Malaterre <malat@debian.org>, Pino Toscano <pino@debian.org>, Gianfranco Costamagna <costamagnagianfranco@yahoo.it>
Subject: Re: gdcm is marked for autoremoval from testing
From: Andreas Tille <andreas@an3as.eu>
Date: Tue, 15 Jul 2014 09:34:05 +0200
Message-id: <20140715073405.GF12063@an3as.eu>
In-reply-to: <E1X6uWD-0002F3-RG@franck.debian.org>
References: <E1X6uWD-0002F3-RG@franck.debian.org>

Hi Release team,

I wonder why gdcm is marked for autoremoval since the bug is fixed in
testing and unstable.  Am I missing something?

Gianfranco, Pino:  Thanks a lot for your NMU!

Kind regards

      Andreas.

On Tue, Jul 15, 2014 at 04:39:10AM +0000, Debian testing autoremoval watch wrote:
> gdcm 2.4.2-1 is marked for autoremoval from testing on 2014-08-14
> 
> It is affected by these RC bugs:
> 751432: gdcm: compatibility with poppler 0.26.x

-- 
http://fam-tille.de

Reply to:

Follow-Ups:
- Re: gdcm is marked for autoremoval from testing
  - From: Mathieu Malaterre <malat@debian.org>
- Re: gdcm is marked for autoremoval from testing
  - From: Gianfranco Costamagna <costamagnagianfranco@yahoo.it>

Prev by Date: Re: Handling s390 libc ABI change in Debian
Next by Date: Re: gdcm is marked for autoremoval from testing
Previous by thread: Bug#751525: marked as done (transition: poppler 0.26)
Next by thread: Re: gdcm is marked for autoremoval from testing
Index(es):
- Date
- Thread