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

Bug#1035297: unblock: qemu/1:7.2+dfsg-6



04.05.2023 00:00, Sebastian Ramacher wrote:
..
1. sync with upstream qemu stable/bugfix 7.2.1 release, by removing
    all patches in debian/patches/master/ and replacing them all with
    single debian/patches/v7.2.1.diff which is a diff between upstream
    qemu 7.2.0 and 7.2.1 releases.  This is a bulk of the changes in there.
    See "Other info" section below for more information.

2. Includes upstream qemu stable/bugfix 7.2.2 release.
    Upstream 7.2.2 needs its own comment.  Historically, qemu stable
    were managed up until next major release is out.  Here, 7.2.2
    was planned to be tagged the next day after 8.0.0 has been
    released (8.0 release didn't follow its schedule because of the
    amount of bugfixes needed there).  So by the historical practice
    7.2.2 should not be released. But I plan to change this practice,
    by providing a bit more support for previous major release of
    qemu, past the next major release date, and also plan to perform
    at least one more 7.2 upstream stable/bugfix release. We're
    discussing this on the qemu side.  Either way, 7.2.2 is officially
    tagged in the upstream qemu git tree:
       https://gitlab.com/qemu-project/qemu/-/tags/v7.2.2
    so it's only matter of making a tarball out of it and making
    an official announcement.

So why is that added as a patch instead of uploading the new upstream
release?

It's been done this way in qemu debian package for ages, for decades.
I don't remember anymore why it is. All previous stable qemu releases
has been applied as patches to debian. It's always qemu-n.m
(instead of qmu-n.m.p) and a patch n.m.p.diff on top.  I think it might
be relate to the huge size of orig.tar.gz and tiny stable/bugfix release
difference on top (but later we reduced orig.tar.gz greatly by removing
submodules which exists as separate packages in debian).  Maybe we should
stop doing this strange thing, but that's not bookworm material I guess.
I already packaged 8.0 instead of 8.0.0 for bookworm+1 :)

This wont make the diff smaller though.

Speaking of actual 7.2.2, I can't reach Michael Roth, who did all
official qemu releases during recent years (it is his gpg key which
is used to sign the tarballs).  I hope to get 7.2.2 out for real.

Thanks!

/mjt


Reply to: