nbdkit fails to build with Python 3.9.0a3. This test has failed, but I can't tell from the log why or what exactly is failing: FAIL test-xz-curl (exit status: 1) For the build logs, see: https://copr-be.cloud.fedoraproject.org/results/@python/python3.9/fedora-rawhide-x86_64/01238125-nbdkit/ For all our attempts to build nbdkit with Python 3.9, see: https://copr.fedorainfracloud.org/coprs/g/python/python3.9/package/nbdkit/ Testing and mass rebuild of packages is happening in copr. You can follow these instructions to test locally in mock if your package builds with Python 3.9: https://copr.fedorainfracloud.org/coprs/g/python/python3.9/ Let us know here if you have any questions. Python 3.9 will be included in Fedora 33. To make that update smoother, we're building Fedora packages with early pre-releases of Python 3.9. A build failure prevents us from testing all dependent packages (transitive [Build]Requires), so if this package is required a lot, it's important for us to get it fixed soon. We'd appreciate help from the people who know this package best, but if you don't want to work on this now, let us know so we can try to work around it on our side.
This is an intermittent bug (very infrequent) in libguestfs related to a change in how the kernel enumerates drives, so we can no longer rely on drives appearing inside the guest in the same order that they appear on the qemu command line. From the log: [ 3.412270] scsi host2: Virtio SCSI HBA [ 3.432372] scsi 2:0:0:0: Direct-Access QEMU QEMU HARDDISK 2.5+ PQ: 0 ANSI: 5 [ 3.437796] scsi 2:0:1:0: Direct-Access QEMU QEMU HARDDISK 2.5+ PQ: 0 ANSI: 5 [ 3.564935] input: ImExPS/2 Generic Explorer Mouse as /devices/platform/i8042/serio1/input/input3 [ 3.688998] sd 2:0:0:0: Attached scsi generic sg0 type 0 [ 3.692889] sd 2:0:1:0: Power-on or device reset occurred [ 3.697865] sd 2:0:1:0: Attached scsi generic sg1 type 0 [ 3.699479] sd 2:0:1:0: [sda] 8388608 512-byte logical blocks: (4.29 GB/4.00 GiB) [ 3.700701] sd 2:0:1:0: [sda] Write Protect is off [ 3.702375] sd 2:0:0:0: Power-on or device reset occurred [ 3.704629] sd 2:0:0:0: [sdb] 206881 512-byte logical blocks: (106 MB/101 MiB) [ 3.705271] sd 2:0:0:0: [sdb] Write Protect is off [ 3.706386] sd 2:0:0:0: [sdb] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA [ 3.708224] sd 2:0:1:0: [sda] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA We were expecting Linux to enumerate the 4GB disk as the second disk. Work is ongoing upstream to fix this. However in this case I expect it'll be fixed just by rerunning the test. *** This bug has been marked as a duplicate of bug 1804207 ***