Thanks for the reply, but the suggested workaround for workstation fails complaining about conflicting requests. I’m a bit confused how the libostree issue affects non-silverblue installs; any insight onto that one?
Moring. You can trysudo dnf downgrade ostree-libs && flatpak update or sudo flatpak update
Flatpak uses the libostree shared library (ostree-libs on Fedora).
Thanks for all the suggestions… I realized after re-reading the output that I had gnome-nightly there, a leftover from a past package; a simple flatpak remote-delete gnome-nightly and flatpak update seems to have fixed the issue.
I did not need to downgrade ostree-libs, interestingly enough.
Yeah, thanks Jan… I spoke too soon. Yesterday, everything resolved correctly without errors, but today the input issue remains and the proposed workaround results in errors:
Error:
Problem: problem with installed package ostree-2023.4-1.fc38.x86_64
- package ostree-2023.4-1.fc38.x86_64 from @System requires libostree-1.so.1(LIBOSTREE_2023.4)(64bit), but none of the providers can be installed
- package ostree-2023.4-1.fc38.x86_64 from @System requires ostree-libs(x86-64) = 2023.4-1.fc38, but none of the providers can be installed
- package ostree-2023.4-1.fc38.x86_64 from updates requires libostree-1.so.1(LIBOSTREE_2023.4)(64bit), but none of the providers can be installed
- package ostree-2023.4-1.fc38.x86_64 from updates requires ostree-libs(x86-64) = 2023.4-1.fc38, but none of the providers can be installed
- package ostree-2023.1-2.fc38.x86_64 from fedora requires ostree-libs(x86-64) = 2023.1-2.fc38, but none of the providers can be installed
- cannot install both ostree-libs-2023.3-3.fc38.x86_64 from @commandline and ostree-libs-2023.4-1.fc38.x86_64 from @System
- cannot install both ostree-libs-2023.3-3.fc38.x86_64 from @commandline and ostree-libs-2023.1-2.fc38.x86_64 from fedora
- cannot install both ostree-libs-2023.3-3.fc38.x86_64 from @commandline and ostree-libs-2023.4-1.fc38.x86_64 from updates
- conflicting requests
(try to add '--allowerasing' to command line to replace conflicting packages or '--skip-broken' to skip uninstallable packages)
I know I can add --allowerasing to the command, but don’t love to do that; however, I suppose it’s the only way to force this downgrading, eh?
Because you have ostree installed (most people don’t). ostree depends on ostree-libs of the same version. If you only specify a URL to a ostree-libs rpm, dnf can’t resolve where to get the corresponding ostree rpm.
So instead you can just downgrade to release repo, and dnf can find the corresponding ostree version in the repo:
sudo dnf downgrade ostree-libs
This is also mentioned multiple times in the replies to the common issue. The common issue has been updated to suggest this command instead of using a Koji URL.
I saw the same issue today, I haven’t updated (dnf or flatpak) in roughly two weeks.
Since the ostree package was mentioned on this thread, I ran sudo dnf remove ostree — dnf returns anaconda packages and malcontent-control ('parental controls UI`) as dependent packages.
The package is installed on my Fedora 38 VM, created two days ago in gnome-boxes (minimal changes, I only removed gnome-software, updated and changed some Gnome settings):
I was wrong about that. I mixed up some info; flatpak depends on ostree-libs… but flatpak-libs depends on ostree, and the GUI app stores depend on flatpak-libs. So Workstation users do indeed have ostree.
Regardless, the workaround in the common issue is correct now. Let’s point people there instead of here.