![]() ![]() glibc included in the query to demonstrate that dnf *is* able to list installed/available packages that are actually installed.Ģ1:13:22 0 dnf -disableexcludes=all list dwm libgit2 stratis glibc Originally saw issue with 'dnf list updates', narrowed down to help debugging. No guarantees, at all, that this will be fixed before the release of 37.Dnf complains about a conflict with dwm and stratis, which it can't even find, and libgit2, which is available but not installed on my system. Or is this something that the package maintainers will fix soon enough? If you want something that you're certain still works after an update, I'd recommend you stick to the current released version of Fedora, and not use Rawhide. However, note that fedora rawhide is the rolling-release, kind-of-experimental version of Fedora, until at some point they freeze it, start concentrating on fixing (exactly such!) bugs, and then roll the next release if nothing broke for a while. ![]() It probably should not have happened looks like there's a version bump that's only been partially done. It might already be solved, or it might need maintainer intervention, in which case you could help upstream, if you know your way around fedora packaging and have knowledge of the affected software. You can remove cached packages by executing 'dnf clean packages'.įile /usr/lib64/libjavascriptcoregtk-4.1.so.0.2.0 conflicts between attempted installs of webkit2gtk4.1-jsc-2.37.86_64 and javascriptcoregtk4.1-2.37.86_64 The downloaded packages were saved in cache until the next successful transaction. Glibc-headers-x86 noarch 2.36-1.fc37 rawhide 574 k Last metadata expiration check: 0:05:29 ago on Mon 02:59:00 PM EDT. ![]() I understand this is beta, was curious how often breaks like this happen as well. Is this something I can fix out? Or is this something that the package maintainers will fix soon enough? I've also run a dnf clean but it didn't work either. I can't remove the conflicting package without it warning me it'll remove gnome. I'm not sure if this is an error on the package maintainers end and it will resolve itself? Below is my output from trying to update my packages using dnf update. ![]()
0 Comments
Leave a Reply. |