Bug#709629: nmu: libavg/1.7.1-3

To: Debian Bug Tracking System <submit@bugs.debian.org>
Subject: Bug#709629: nmu: libavg/1.7.1-3
From: Luca Falavigna <dktrkranz@debian.org>
Date: Fri, 24 May 2013 16:55:34 +0200
Message-id: <[🔎] CADk7b0N+J=jBfkqNKjvMnx4ZYUqi7Hw4B5wf24YYNvrodY5B=g@mail.gmail.com>
Reply-to: Luca Falavigna <dktrkranz@debian.org>, 709629@bugs.debian.org

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'

Reply to:

Follow-Ups:
- Bug#709629: marked as done (nmu: libavg/1.7.1-3)
  - From: owner@bugs.debian.org (Debian Bug Tracking System)

Prev by Date: Bug#709618: camlp5 et al need hinting
Next by Date: Bug#709634: RM: ruby-activesupport-2.3/2.3.14-7, ruby-actionmailer-2.3/2.3.14-3, ruby-actionpack-2.3/2.3.14-5, ruby-activerecord-2.3/2.3.14-6, ruby-activeresource-2.3/2.3.14-3, ruby-rails-2.3/2.3.14-4
Previous by thread: Bug#709619: release.debian.org: [tools] migration.pl could show details of attempted hints
Next by thread: Bug#709629: marked as done (nmu: libavg/1.7.1-3)
Index(es):
- Date
- Thread