In F41, I needed to rebuild my own gvfs to include those patches so my backup software would work correctly: https://gitlab.gnome.org/GNOME/gvfs/-/merge_requests/226 In F42, it seems that 1.57.x versions of gvfs which include those changes were not brought in, and the F43 version fails to build in rawhide. Please update gvfs in F42 (you will probably need to also rebuild msgraph, as the old builds of 0.3.x are in the process of being deleted after being unused). Reproducible: Always
So there is a rather nasty problem here with msgraph: DEBUG util.py:459: Problem 1: package gnome-online-accounts-devel-3.54.2-1.fc43.x86_64 from build requires libgoa-1.0.so.0()(64bit), but none of the providers can be installed DEBUG util.py:459: - package gnome-online-accounts-devel-3.54.2-1.fc43.x86_64 from build requires libgoa-backend-1.0.so.2()(64bit), but none of the providers can be installed DEBUG util.py:459: - package gnome-online-accounts-devel-3.54.2-1.fc43.x86_64 from build requires gnome-online-accounts(x86-64) = 3.54.2-1.fc43, but none of the providers can be installed DEBUG util.py:459: - package gnome-online-accounts-3.54.2-1.fc43.x86_64 from build requires gvfs-goa, but none of the providers can be installed ... DEBUG util.py:459: - nothing provides libmsgraph-0.so.1()(64bit) needed by gvfs-goa-1.56.1-6.fc43.x86_64 from build that is: we are trying to build gvfs against the *new* msgraph. But gvfs buildrequires pkgconfig(goa-1.0) which is provided by gnome-online-accounts-devel, that requires gnome-online-accounts, that requires gvfs-goa, and *that* requires the *old* libmsgraph . We have a dependency loop here which makes it impossible to build gvfs against a new msgraph, and I honestly don't immediately see how to resolve it. *Possibly* we could separate libgoa from gnome-online-accounts? If we then had libgoa-devel which required libgoa (but not g-o-a), and libgoa could *not* require gvfs-goa, I think that would break the loop. But other than that, I can't actually see a resolution that's not a gross hack. Anybody? See also https://bugzilla.redhat.com/show_bug.cgi?id=2347492 .
https://bodhi.fedoraproject.org/updates/FEDORA-2025-76454cb09e will make gvfs buildable again, so nmontero should be able to resolve this soon.
FEDORA-2025-c707c9f85b (gnome-online-accounts-3.54.2-5.fc42, gvfs-1.57.2-1.fc42, and 1 more) has been submitted as an update to Fedora 42. https://bodhi.fedoraproject.org/updates/FEDORA-2025-c707c9f85b
FEDORA-2025-c707c9f85b 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-c707c9f85b` You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2025-c707c9f85b See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.
FEDORA-2025-c707c9f85b (gnome-online-accounts-3.54.2-5.fc42, gvfs-1.57.2-1.fc42, and 1 more) has been pushed to the Fedora 42 stable repository. If problem still persists, please make note of it in this bug report.