From: ronnie sahlberg <ronniesahlberg@gmail.com>
To: Stefan Weil <sw@weilnetz.de>
Cc: "Peter Maydell" <peter.maydell@linaro.org>,
"Michael Tokarev" <mjt@tls.msk.ru>, "Peter Lieven" <pl@kamp.de>,
qemu-devel <qemu-devel@nongnu.org>,
"Paolo Bonzini" <pbonzini@redhat.com>,
"Aurélien Jarno" <aurelien@aurel32.net>
Subject: Re: [Qemu-devel] [RFC] How to handle feature regressions in new QEMU releases
Date: Wed, 16 Jul 2014 10:23:14 -0700 [thread overview]
Message-ID: <CAN05THSFm4nOr5aAXhBjJomwb8Dt-2dnU6GRKdDa=g_2QS3aMw@mail.gmail.com> (raw)
In-Reply-To: <53C6B24D.4020403@weilnetz.de>
On Wed, Jul 16, 2014 at 10:11 AM, Stefan Weil <sw@weilnetz.de> wrote:
> Am 16.07.2014 18:49, schrieb Paolo Bonzini:
>> Il 16/07/2014 18:28, Stefan Weil ha scritto:
>>> Debian testing includes a brand new libiscsi, but it
>>> does not include libiscsi.pc, so pkg-config won't know that it is
>>> available and configure will disable libiscsi.
>>
>> That's a packaging bug.
>
> CC'ing Michael as he is the Debian maintainer of this package and
> Aurélien who maintains QEMU for Debian.
>
> Michael, should I send a Debian bug report for libiscsi-dev? Would an
> update of libiscsi for Debian stable be reasonable if versions older
> than 1.9 are too buggy to be used?
If you ask debian to upgrade. Could you ask them to wait and upgrade after I
have release the next version, hopefully if all goes well, at the end
of this week?
It contains new functionality, thanks to plieven, to better handle
cases where active/passive storage arrays
perform failover.
> I must admit that I'm a little bit
> surprised because iSCSI support worked for me quite well the last time I
> used it with Debian wheezy.
I think, and plieven please correct me if I am wrong, earlier version
would work reasonably well for basic use
but there were bugs and gaps in functionality that made it ill suited
for enterprise environments.
>
> Regards
> Stefan
>
>>
>>> I have a patch which
>>> fixes this, so QEMU for Debian testing could include libiscsi again.
>>>
>>> Is a feature regression like this one acceptable? Do we need additional
>>> testing (maybe run the build bots with --enable-xxx, so builds fail when
>>> xxx no longer works)?
>>
>> As mentioned in the e49ab19fcaa617ad6cdfe1ac401327326b6a2552 commit
>> message, this was intentional. I was reluctant to do it, but ultimately
>> Peter Lieven convinced me that it isn't just about using fancy new APIs;
>> libiscsi was too buggy to be useful until release 1.8.0 (even 1.9.0
>> requires a patch to avoid segfaults, and many more if you want to run it
>> on ARM).
>>
>> Paolo
>
>
next prev parent reply other threads:[~2014-07-16 17:23 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-16 0:26 [Qemu-devel] [ANNOUNCE] QEMU 2.1.0-rc2 is now available Michael Roth
2014-07-16 16:28 ` [Qemu-devel] [RFC] How to handle feature regressions in new QEMU releases (was: [ANNOUNCE] QEMU 2.1.0-rc2 is now available) Stefan Weil
2014-07-16 16:46 ` Peter Maydell
2014-07-16 17:37 ` [Qemu-devel] [RFC] How to handle feature regressions in new QEMU releases Peter Lieven
2014-07-16 16:49 ` Paolo Bonzini
2014-07-16 17:11 ` Stefan Weil
2014-07-16 17:23 ` ronnie sahlberg [this message]
2014-07-16 17:29 ` Michael Tokarev
2014-07-24 0:37 ` ronnie sahlberg
2014-07-24 10:10 ` Michael Tokarev
2014-07-16 17:36 ` Peter Lieven
2014-07-16 17:28 ` Michael Tokarev
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='CAN05THSFm4nOr5aAXhBjJomwb8Dt-2dnU6GRKdDa=g_2QS3aMw@mail.gmail.com' \
--to=ronniesahlberg@gmail.com \
--cc=aurelien@aurel32.net \
--cc=mjt@tls.msk.ru \
--cc=pbonzini@redhat.com \
--cc=peter.maydell@linaro.org \
--cc=pl@kamp.de \
--cc=qemu-devel@nongnu.org \
--cc=sw@weilnetz.de \
/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).