Bug#684705: marked as done (RM: libumberlog/0.2.1-1)
Your message dated Mon, 13 Aug 2012 21:46:42 +0100
with message-id <1344890802.1515.8.camel@jacala.jungle.funky-badger.org>
and subject line Re: Bug#684705: RM: libumberlog/0.2.1-1
has caused the Debian Bug report #684705,
regarding RM: libumberlog/0.2.1-1
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.)
--
684705: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=684705
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: rm
Please remove libumberlog from wheezy, as a new upstream version is
about to be released, which will not be backwards compatible. Having
an incompatible version in wheezy would be counter productive, and
including the new one is far too late already.
So the best option is to not ship libumberlog in wheezy.
--- End Message ---
--- Begin Message ---
On Mon, 2012-08-13 at 10:54 +0200, Gergely Nagy wrote:
> Please remove libumberlog from wheezy, as a new upstream version is
> about to be released, which will not be backwards compatible. Having
> an incompatible version in wheezy would be counter productive, and
> including the new one is far too late already.
>
> So the best option is to not ship libumberlog in wheezy.
Removal hint added.
Regards,
Adam
--- End Message ---
Reply to: