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

Bug#725968: pu: package libvirt/0.9.12.2-1



Hi,

Guido Günther wrote (10 Oct 2013 15:22:45 GMT) :
> On Thu, Oct 10, 2013 at 03:38:33PM +0200, Cyril Brulebois wrote:
> [..snip..] 
>> For the record, we tend to prefer having debdiff (or at least debian
>> changelogs) posted to the BTS. Right now I have absolutely no idea which
>> bugs you're trying to get fixed, and whether fixes landed in testing or
>> unstable.

> libvirt (0.9.12.2-1) wheezy-proposed-updates; urgency=low

>   * [77a7135] Adjust gbp.conf for Wheezy point releases
>   * [b457e3f] New upstream version 0.9.12.1
>   * [ae6e265] New upstream version 0.9.12.2
>   * [2d07b5c] Drop patches fixed upstream.
>         Include-stdint.h-for-uint32_t.patch
>         Revert-rpc-Discard-non-blocking-calls-only-when-nece.patch
>         fix-leak-virStorageBackendLogicalMakeVol.patch
>         qemu-Add-support-for-no-user-config.patch
>         qemu-Fix-off-by-one-error-while-unescaping-monitor-s.patch
>         rpc-Fix-crash-on-error-paths-of-message-dispatching.patch
>         security/CVE-2012-3445.patch
>         security/Fix-crash-in-remoteDispatchDomainMemoryStats.patch
>         security/security-Fix-libvirtd-crash-possibility.patch
>         upstream/Fix-libvirtd-crash-when-destroying-a-domain-with-att.patch
>         upstream/Fix-race-condition-when-destroying-guests.patch

>  -- Guido Günther <agx@sigxcpu.org>  Tue, 01 Oct 2013 21:45:08 +0200

> This also fixes CVE-2013-4311 once we have a fixed polkit in wheezy.

>> But seriously, a 15MB diff is nowhere reviewable. Even if most of it is
>> automake bootstrap and patches moving around.

> The patches (outside debian/) were all reviewed by upstream and mostly
> incorporate the diff Debian was carrying back upstream so we can release
> further updates from that branch.

I suspect that the changelog snippet that Guido sent does not address
what Cyril was asking (more specifically: which bugs you're trying to
get fixed, and whether fixes landed in testing or unstable).

On the positive side, I can see one thing that could possibly help:
a diff between the current version in stable, with the Debian patches
applied, and the proposed update. It would automatically filter out
the move of Debian-specific patches to the upstream source, and
hopefully it will be of a size that the release team is happy
to review.

Cheers,
--
  intrigeri
  | GnuPG key @ https://gaffer.ptitcanardnoir.org/intrigeri/intrigeri.asc
  | OTR fingerprint @ https://gaffer.ptitcanardnoir.org/intrigeri/otr.asc


Reply to: