I downloaded and installed the Flat Remix Icons through the dnfdragora software. I then removed them with sudo dnf remove [...] and all but four were removed.
Now, I see them via Gnome Tweaks>Appearance but with a .rpmmoved extension:
Flat-Remix-Blue-Light.rpmmoved
Flat-Remix-Green-Light.rpmmoved
Flat-Remix-Red-Light.rpmmoved
Flat-Remix-Yellow-Light.rpmmoved
Where did they go? How in the world can I clean that up?
I haven’t used the “flat remix” icons. Would you know what packages these were please? The only files that are not touched by rpm during transaction are configuration files. So it’s possible that these are configuration files left over after the uninstallation and so require manual removal.
Sorry @marko23 : why does one need to remove the files manually? All files installed by the rpm should be owned by it, so that if they are installed by the rpm, they should be removed by the rpm also. So, if that isn’t happening, this is a packaging bug.
.rmpmoved isn’t standard package name but a package bug. I looked around for a while with same problem and finally searched in the whole file system for things suffixed . rmpmoved that brings you to /user/share/icons with folder Flat-Remix … logical but strange …
Hrm, I think if removing the rpm isn’t removing all files from the package, that’s a packaging bug that should be reported. I don’t see a bug here about this, so could you folks file one please?
If a system is upgraded from a version less than or equal to flat-remix-icon-theme-0.0.20211214
That system will end up with .rpmmoved directories for:
Flat-Remix-Blue-Light.rpmmoved
Flat-Remix-Green-Light.rpmmoved
Flat-Remix-Red-Light.rpmmoved
Flat-Remix-Yellow-Light.rpmmoved
I’d still say it’s a bug, but I haven’t looked into what component it is with too.
It’s fine to replace whatever with *.rpmmoved, but when the package is uninstalled, this should be removed. The docs confirm this:
“Additionally, you should define the /path/to/dir.rpmmoved directory as a %ghost entry in the %files list in the package’s spec file, so that the directory is not entirely orphaned and can be deleted if the package is ever uninstalled and the directory is empty.”
So, unless the user her put something in the directory to make it “not empty”, it should be removed on uninstalling the package.
So, if the spec is fine, it’s a bug with rpm itself (!)—which isn’t removing the files.
I guess we’ve solved the issue here, and if anyone is interested, they can follow up to isolate the component.