Michael Tokarev <email@example.com> (08/07/2012): > Package: release.debian.org > Severity: normal > User: firstname.lastname@example.org > Usertags: unblock > > Please unblock package qemu-kvm. Please note that the package has > already been uploaded to unstable, because I incorrectly assumed it > is the way to go during the freeze time. Please excuse me for that, > it was made due to my lack of understanding of the process. > > As I wrote in email on Jul-14 <4FD9FC84.email@example.com>, > https://lists.debian.org/debian-release/2012/06/msg00370.html , > upstream delayed the final release of next stable qemu-kvm version > due to a few last-minute regressions found there. The actual > release happened 2 Jul, ie, after the wheezy freeze. > > I managed to upload a prerelease of the package before freeze, > numbered 1.1~z0+dfsg-1 -- in last 40 minutes before freeze, > when I returned from my vacation. However, this was based on > a prerelease (which happened to become a release 2 days later), > and it had a few glitches which are now sorted. > > The new uploaded package is based on the actual 1.1.0 upstream > tarball, which is different from the "fake upstream" tarball > I had previously only in one file, KVM_VERSION, -- previous > version had an -rc4 in it, new version has proper 1.1.0. So > the current orig.tar didn't really changed. You really should have let the freeze-exception-granted version migrate to testing first. The diff between testing and unstable is *INSANE*. 1832 files changed, 290208 insertions(+), 110147 deletions(-) > --- qemu-kvm-1.1~z0+dfsg/debian/changelog 2012-06-30 23:21:49.000000000 +0400 > +++ qemu-kvm-1.1.0+dfsg/debian/changelog 2012-07-07 16:15:07.000000000 +0400 > @@ -1,3 +1,22 @@ > +qemu-kvm (1.1.0+dfsg-1) unstable; urgency=low > + > + * 1.1.0 upstream release, finally. No changes from the previous source. > + * added two patches from upstream qemu-kvm/stable-1.1 branch: > + qemu-kvm-Add-missing-default-machine-options.patch > + qemu-kvm-virtio-Do-not-register-mask-notifiers-witho.patch > + (Closes: #679788) > + * mention closing of #640139, #672112 by 1.1 > + * store cpus-x86_64.conf in /usr/share/kvm not /etc/kvm (Closes: #680609) > + * align-ram_size-to-8k-boundary.patch - force guest memory size to be a > + multiple of 8KiB, to stop SIGSEGV when guest tries to access last partial > + memory page. (Closes: #677528) > + * dont-try-to-hotplug-cpu.patch (from Ubuntu package). CPU hot-plug > + never really worked in qemu-kvm correctly. This temporary patch > + disables this feature, returning an error instead of crashing. > + (Closes: #680551) > + > + -- Michael Tokarev <firstname.lastname@example.org> Tue, 03 Jul 2012 18:01:33 +0400 > + > qemu-kvm (1.1~z0+dfsg-1) unstable; urgency=low What matters is the diff between testing and unstable, see comment above. :( Mraw, KiBi.
Description: Digital signature