Description of problem: When I tried to update f20 box to f21 using dnf I get following error Error: Transaction check error: file /usr/share/themes/Adwaita/gtk-3.0/gtk.css from install of gnome-themes-standard-3.13.90-1.fc21.x86_64 conflicts with file from package adwaita-gtk3-theme-3.10.0-2.fc20.x86_64 Version-Release number of selected component (if applicable): adwaita-gtk3-theme-3.10.0-2.fc20.x86_64 How reproducible: always Steps to Reproduce: 1. 2. 3. Actual results: not able to update Expected results: should allow update without a problem Additional info:
gtk3 has obsoletes that cover adwaita-gtk3-theme and yum correctly removes adwaita-gtk3-theme on upgrades. Looks like DNF needs some more work in this area to make this work. This is the obsoletes that gtk3 currently has: Obsoletes: adwaita-gtk3-theme < 3.13.3 Provides: adwaita-gtk3-theme = %{version}-%{release} http://pkgs.fedoraproject.org/cgit/gtk3.git/tree/gtk3.spec#n76 Reassigning to DNF.
Hi, thanks for the report. We'll take a look.
We'd definitely need the solver debugdata [1] though. Thanks! [1] http://dnf.baseurl.org/2013/11/25/reporting-depsolving-bugs/
Created attachment 930734 [details] add debugdata output
This seems to be a packaging error. On complete upgrades, gtk3 gets rid of adwaita-gtk3-theme correctly. But in the given update path, when only doing ugprade of gnome-themes-standard, there's no reason why gtk3 version should be affected and consequently there is nothing obsoleting adwaita-gtk3-theme. Over to adwaita.
From the packaging side, we only support performing whole system upgrades and do not support updating a single package at a time.
huh? What packaging/fedora guideline is that? ah, you probably mean "we" as in "us, desktop".
Even if that was true (which is perfectly acceptable), there are ways how to ensure the update does not break the way that is described here, so this is still a valid bug and pretty nasty one at that. How am I as a standard user supposed to know about this decision that you guys in desktop team made? If you require your packages to be updated as a set, then set the dependencies to be version specific.
Sorry guys, I forgot to update the ticket. I helped another user on irc with the same issue two weeks ago. He was doing a F20->F21 upgrade with yum and using --skip-broken. Due to broken dependencies in rpmfusion, --skip-broken led to yum skipping most of the available packages and only pulling in a handful of new packages in the transaction. In particular, it pulled in new gnome-themes-standard, but skipped new gtk3. This led to the gtk3 obsoletes not being considered at all (the new gtk3 packages obsoletes adwaita-gtk3-theme). I've now added explicit Conflicts to gnome-themes-standard to avoid running into this in the future, http://pkgs.fedoraproject.org/cgit/gnome-themes-standard.git/commit/?id=b79fc190d6a36785a9429b65a134d2ff38df0472 Thanks for the help everyone!