Your message dated Wed, 06 Feb 2013 13:10:03 +0000 with message-id <e161dd997d26490d8816c5a9fbfdcf98@mail.adsl.funky-badger.org> and subject line Re: Bug#699465: t-p-u: gdcm 2.2.0-14 has caused the Debian Bug report #699465, regarding t-p-u: gdcm 2.2.0-14 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.) -- 699465: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=699465 Debian Bug Tracking System Contact owner@bugs.debian.org with problems
--- Begin Message ---
- To: Debian Bug Tracking System <submit@bugs.debian.org>
- Subject: t-p-u: gdcm 2.2.0-14
- From: Mathieu Malaterre <malat@debian.org>
- Date: Thu, 31 Jan 2013 18:36:07 +0100
- Message-id: <20130131173607.14567.45556.reportbug@lirispat.univ-lyon1.fr>
Package: release.debian.org Severity: normal As per §5.13.3. Direct updates to testing, I'd like to ask permission for direct upload to testing for package gdcm. In order to fix #699379, I would need to upload 2.2.0-14, by-passing the current 2.2.1-1 sitting in unstable. -- System Information: Debian Release: 6.0.6 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'stable'), (200, 'testing'), (100, 'unstable') Architecture: amd64 (x86_64) Kernel: Linux 3.2.0-0.bpo.4-amd64 (SMP w/8 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash
--- End Message ---
--- Begin Message ---
- To: <699465-done@bugs.debian.org>
- Cc: Julien Cristau <jcristau@debian.org>, Mathieu Malaterre <malat@debian.org>
- Subject: Re: Bug#699465: t-p-u: gdcm 2.2.0-14
- From: "Adam D. Barratt" <adam@adam-barratt.org.uk>
- Date: Wed, 06 Feb 2013 13:10:03 +0000
- Message-id: <e161dd997d26490d8816c5a9fbfdcf98@mail.adsl.funky-badger.org>
- In-reply-to: <1360098587.26370.4.camel@jacala.jungle.funky-badger.org>
- References: <20130131173607.14567.45556.reportbug@lirispat.univ-lyon1.fr> <9bacbff5798dc3db0e9a6964292bae99@mail.adsl.funky-badger.org> <CA+7wUswiYH9xESF=LE28x4aD+9mb_YeLLYJVh-LFQstCYMoPNg@mail.gmail.com> <1359825792.4425.8.camel@jacala.jungle.funky-badger.org> <CA+7wUsxh+VwFmJsz4ePTFvGjLv1JccKSk_uZikGq0uGv=HKkNg@mail.gmail.com> <20130204222336.GF8837@radis.cristau.org> <CA+7wUsyXTS_YuKNH31VA1UfNb9wz4kht-PGtPzPE0-MsQ=1GXQ@mail.gmail.com> <20130205210808.GL8837@radis.cristau.org> <1360098587.26370.4.camel@jacala.jungle.funky-badger.org>
On 05.02.2013 21:09, Adam D. Barratt wrote:On Tue, 2013-02-05 at 22:08 +0100, Julien Cristau wrote:On Tue, Feb 5, 2013 at 08:50:08 +0100, Mathieu Malaterre wrote:> On Mon, Feb 4, 2013 at 11:23 PM, Julien Cristau <jcristau@debian.org> wrote: > > Nope, having a fixed gdcm is a blocker for mono's migration to testing, > > please fix this ASAP in sid and testing (or let me know if you can't and> > I'll NMU). > > Sorry I missed that point. I really do appreciate your offer, so > please go ahead and NMU as you need. > Thanks. Uploaded 2.2.0-14.1 to tpu, and 2.2.1-1.1 to sid. Release team, please unblock the former.Once it's had chance to hit the buildds, sure. :-)Unblocked; thanks. Regards, Adam
--- End Message ---