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

Bug#709629: marked as done (nmu: libavg/1.7.1-3)

Your message dated Fri, 24 May 2013 19:22:19 +0100
with message-id <1369419739.18864.6.camel@jacala.jungle.funky-badger.org>
and subject line Re: Bug#709629: nmu: libavg/1.7.1-3
has caused the Debian Bug report #709629,
regarding nmu: libavg/1.7.1-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.)


-- 
709629: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=709629
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


Please schedule binNMUs for libavg to drop python2.6 dependencies.

#701304 shouldn't be a problem anymore, I was able to reproduce the
build failure some days ago, but it seems the cause of the problem has
been somehow fixed (it was related to boost1.53, IIRC), as I'm
currently able to rebuild libavg now.

nmu libavg_1.7.1-3 . ALL . -m 'Drop python2.6'

--- End Message ---
--- Begin Message --- 
On Fri, 2013-05-24 at 16:55 +0200, Luca Falavigna wrote:
> Please schedule binNMUs for libavg to drop python2.6 dependencies.
> 
> #701304 shouldn't be a problem anymore, I was able to reproduce the
> build failure some days ago, but it seems the cause of the problem has
> been somehow fixed (it was related to boost1.53, IIRC), as I'm
> currently able to rebuild libavg now.

Scheduled.

Regards,

Adam

--- End Message ---
Reply to: