From: "Daniel P. Berrangé" <berrange@redhat.com>
To: "Marc-André Lureau" <marcandre.lureau@redhat.com>
Cc: qemu-devel <qemu-devel@nongnu.org>,
"Bonzini, Paolo" <pbonzini@redhat.com>,
"Hoffmann, Gerd" <kraxel@redhat.com>,
Frediano Ziglio <fziglio@redhat.com>
Subject: Re: [Qemu-devel] [PATCH for-4.0 v2] configure: bump spice-server required version to 0.12.6
Date: Wed, 28 Nov 2018 14:54:09 +0000 [thread overview]
Message-ID: <20181128145409.GN24355@redhat.com> (raw)
In-Reply-To: <CAMxuvayS9ja1H-ftsahECEJU+T6EE8-KcYTpDnii8KdJHwaYmw@mail.gmail.com>
On Wed, Nov 28, 2018 at 06:46:37PM +0400, Marc-André Lureau wrote:
> Hi
>
> On Wed, Nov 28, 2018 at 6:33 PM Daniel P. Berrangé <berrange@redhat.com> wrote:
> >
> > On Wed, Nov 28, 2018 at 06:21:35PM +0400, Marc-André Lureau wrote:
> > > Looking at chardev/spice.c code, I realize compilation was broken for
> > > a while with spice-server < 0.12.3. I propose to bump required version
> > > to 0.12.6, released 3y ago, instead of adding more #ifdef.
> >
> > As mentioned last time this patch was posted[1], any changes in the
> > min required versions should follow our supported build platforms
> > support statement:
>
> Sorry, I totally forgot that.
>
> >
> > https://qemu.weilnetz.de/doc/qemu-doc.html#Supported-build-platforms
> >
> > Preferrably the commit message should list the version in each of the
> > main distros, such as in a0722409bcb980ecdab8330d4c716a73c9fcb489
> >
> > At a glance it looks like Debian Jessie is likely to be the determining
> > vote with 0.12.5 as its newest version.
>
> https://repology.org/metapackage/spice/versions
>
> Debian Oldstable
> oldstable/main spice 0.12.5
>
> https://wiki.debian.org/DebianReleases
>
> ~June 6th 2020 (LTS)
>
> But the current stable, Stretch, was released on June 17th 2017.
>
> So we are stuck with spice server 0.12.5 until +2y, June 17th 2019 ?
Yep, but that means one more dev cycle - 4.0
We're free to drop Jessie once QEMU 4.1 opens for development at
end of April / early May.
Regards,
Daniel
--
|: https://berrange.com -o- https://www.flickr.com/photos/dberrange :|
|: https://libvirt.org -o- https://fstop138.berrange.com :|
|: https://entangle-photo.org -o- https://www.instagram.com/dberrange :|
next prev parent reply other threads:[~2018-11-28 14:54 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-28 14:21 [Qemu-devel] [PATCH for-4.0 v2] configure: bump spice-server required version to 0.12.6 Marc-André Lureau
2018-11-28 14:33 ` Daniel P. Berrangé
2018-11-28 14:46 ` Marc-André Lureau
2018-11-28 14:54 ` Daniel P. Berrangé [this message]
2018-11-29 8:06 ` Hoffmann, Gerd
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20181128145409.GN24355@redhat.com \
--to=berrange@redhat.com \
--cc=fziglio@redhat.com \
--cc=kraxel@redhat.com \
--cc=marcandre.lureau@redhat.com \
--cc=pbonzini@redhat.com \
--cc=qemu-devel@nongnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).