Description of problem: libnfs 6 introduces a significant API change - https://github.com/sahlberg/libnfs/commit/5e8f7ce273308eb77f94248f4501e574a703c1a5 - which breaks build of qemu's NFS support. For now libnfs is being held at version 5, but the maintainer would like to bump it to 6. We need to either fix qemu to build against the new API, or drop the NFS support from qemu. See upstream discussions https://lists.nongnu.org/archive/html/qemu-block/2024-12/msg00151.html and https://lists.nongnu.org/archive/html/qemu-block/2025-01/msg00480.html . Current upstream qemu attempts to disable the NFS support if it detects the newer libnfs API, but this doesn't "work" for us as our build explicitly enables it - https://src.fedoraproject.org/rpms/qemu/blob/rawhide/f/qemu.spec#_1861 . We'd have to set have_block_nfs to 0 to disable it in the package build.
I've committed a patch to rawhide that should be compatible with libnfs6. We'll need libnfs6 re-tagged into rawhide before I trigger a new QEMU build though.
"There's a side tag available for the rebuilds: fedpkg build --target=f42-build-side-102002" - https://bugzilla.redhat.com/show_bug.cgi?id=2331668#c11 can you build it on that side tag? Thanks.
I don't see any patch, though? The last commit at https://src.fedoraproject.org/rpms/qemu/commits/rawhide as I write this was by me, four days ago.
(In reply to Adam Williamson from comment #3) > I don't see any patch, though? The last commit at > https://src.fedoraproject.org/rpms/qemu/commits/rawhide as I write this was > by me, four days ago. My bad, forgot to push it. (In reply to Adam Williamson from comment #2) > "There's a side tag available for the rebuilds: fedpkg build > --target=f42-build-side-102002" - > https://bugzilla.redhat.com/show_bug.cgi?id=2331668#c11 That doesn't seem to actually exist :-(
current side tag: f42-build-side-104263
We're now blocked from building QEMU because ncurses is broken since GCC 15 https://bugzilla.redhat.com/show_bug.cgi?id=2342514
We're now blocked from buildnig QEMU because gcc broken int128 support on s390x https://bugzilla.redhat.com/show_bug.cgi?id=2342831
Fixed in qemu-9.2.0-17.fc42
> Fixed in qemu-9.2.0-17.fc42 Nope, you built it into the main f42 target, not the side-tag, so it still used old libnfs5
Sorry for screwing that up. Looks like latest side tag build is still failing, gcc in it is missing the s390 fix.
Ok, finally built into the side tag as qemu-9.2.0-20.fc42. So presumably we should be good to merge the side tag into rawhide if QEMU was the last blocker for libnfs6.
FEDORA-2025-d3a96f5085 (gvfs-1.56.1-6.fc43, libnfs-6.0.2-2.fc43, and 3 more) has been submitted as an update to Fedora 43. https://bodhi.fedoraproject.org/updates/FEDORA-2025-d3a96f5085
FEDORA-2025-052559f83a (gvfs-1.56.1-6.fc42, libnfs-6.0.2-2.fc42, and 3 more) has been submitted as an update to Fedora 42. https://bodhi.fedoraproject.org/updates/FEDORA-2025-052559f83a
FEDORA-2025-052559f83a has been pushed to the Fedora 42 testing repository. Soon you'll be able to install the update with the following command: `sudo dnf upgrade --enablerepo=updates-testing --refresh --advisory=FEDORA-2025-052559f83a` You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2025-052559f83a See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.
There's a failing CI test on F43 preventing the whole update to be pushed: https://osci-jenkins-1.ci.fedoraproject.org/job/fedora-ci/job/dist-git-pipeline/job/master/486472/
FEDORA-2025-d3a96f5085 (gvfs-1.56.1-6.fc43, libnfs-6.0.2-2.fc43, and 3 more) has been pushed to the Fedora 43 stable repository. If problem still persists, please make note of it in this bug report.
FEDORA-2025-052559f83a (gvfs-1.56.1-6.fc42, libnfs-6.0.2-2.fc42, and 3 more) has been pushed to the Fedora 42 stable repository. If problem still persists, please make note of it in this bug report.