[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#698039: marked as done (nmu: pygtk_2.24.0-3)

Your message dated Sat, 19 Jan 2013 12:58:00 +0100
with message-id <20130119115800.GX5676@radis.cristau.org>
and subject line Re: Bug#698039: nmu: pygtk_2.24.0-3
has caused the Debian Bug report #698039,
regarding nmu: pygtk_2.24.0-3
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.)


-- 
698039: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=698039
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
Control: block 685812 by -1

Dear Release Team,

I determined that pygtk is affected by the python-numpy ABI breakage (see
#685812). A rebuild is therefore necessary. A binNMU is enough because the
correct dependency on python-numpy >= 1:1.6.1-1 will be generated (i.e. partial
upgrades won't be broken).

nmu pygtk_2.24.0-3 . ALL . -m "Rebuild against python-numpy >= 1:1.6.1-1 because of ABI change (see #685812)"

Cheers,

-- 
 .''`.    Sébastien Villemot
: :' :    Debian Developer
`. `'     http://www.dynare.org/sebastien
  `-      GPG Key: 4096R/381A7594

Attachment: signature.asc
Description: Digital signature


--- End Message ---
--- Begin Message --- 
On Sun, Jan 13, 2013 at 10:55:40 +0100, Sébastien Villemot wrote:

> Package: release.debian.org
> Severity: normal
> User: release.debian.org@packages.debian.org
> Usertags: binnmu
> Control: block 685812 by -1
> 
> Dear Release Team,
> 
> I determined that pygtk is affected by the python-numpy ABI breakage (see
> #685812). A rebuild is therefore necessary. A binNMU is enough because the
> correct dependency on python-numpy >= 1:1.6.1-1 will be generated (i.e. partial
> upgrades won't be broken).
> 
> nmu pygtk_2.24.0-3 . ALL . -m "Rebuild against python-numpy >= 1:1.6.1-1 because of ABI change (see #685812)"
> 
Scheduled, thanks.

Cheers,
Julien

Attachment: signature.asc
Description: Digital signature


--- End Message ---
Reply to: