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

Bug#601939: marked as done (Request for freeze exception for libclamunrar 0.96.4-1)

Your message dated Mon, 1 Nov 2010 18:10:12 +0100
with message-id <20101101171012.GC4770@radis.liafa.jussieu.fr>
and subject line Re: Bug#601939: Request for freeze exception for libclamunrar 0.96.4-1
has caused the Debian Bug report #601939,
regarding Request for freeze exception for libclamunrar 0.96.4-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.)


-- 
601939: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=601939
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message --- 
Package: release.debian.org

Hi release team,

As a freeze exception was requested for clamav (#601900), I'd also ask for such
an exception for non-free libclamunrar 0.96.4-1 to have matching versions in
squeeze. Now clearly a freeze exception for libclamunrar depends on one being
granted for clamav. Of course, the freeze exception is just one way to go.
Should you prefer not to grant libclamunrar a freeze exception, we would need to
remove the current binary packages from squeeze as these are seriously outdated.

Thanks a lot,
Michael

libclamunrar (0.96.4-1) unstable; urgency=low

  * New upstream version
  * Bumped standards version to 3.9.1 (no changes).

 -- Michael Tautschnig <mt@debian.org>  Tue, 26 Oct 2010 00:16:24 +0200

Attachment: pgpO_UXlJ7XQp.pgp
Description: PGP signature


--- End Message ---
--- Begin Message --- 
On Mon, Nov  1, 2010 at 17:38:00 +0100, Michael Tautschnig wrote:

> Err, you're right. There is no change that would be causing incompatibilities,
> hence my assertion was wrong. It does fix one or two memleaks and contain some
> beautifications, but there aren't any API or ABI breakages.
> 
OK, I've unblocked the new version as I had looked at it anyway and the
changes seemed harmless enough (famous last words).

Thanks,
Julien

Attachment: signature.asc
Description: Digital signature


--- End Message ---
Reply to: