qemu-devel
[Top][All Lists]
Advanced

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

Re: [Qemu-devel] [RFC] How to handle feature regressions in new QEMU rel


From: Paolo Bonzini
Subject: Re: [Qemu-devel] [RFC] How to handle feature regressions in new QEMU releases
Date: Wed, 16 Jul 2014 18:49:28 +0200
User-agent: Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Thunderbird/24.6.0

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.

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



reply via email to

[Prev in Thread] Current Thread [Next in Thread]