From Bugzilla Helper: User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7.10) Gecko/20050909 Fedora/1.7.10-1.5.2 Description of problem: The fedora-logos rpm contains /usr/lib/anaconda-runtime/boot/syslinux-splash.png. This directory is unowned, if not having anaconda installed (Note: fedora-logos is independent from without anaconda*) Version-Release number of selected component (if applicable): fedora-logos-1.1.31-1 How reproducible: Always Steps to Reproduce: 1. yum install fedora-logos 2. yum remove anaconda-runtime 3. # rpm -qf /usr/lib/anaconda-runtime/boot/syslinux-splash.png fedora-logos-1.1.31-1 # rpm -qf /usr/lib/anaconda-runtime/boot file /usr/lib/anaconda-runtime/boot is not owned by any package # rpm -qf /usr/lib/anaconda-runtime file /usr/lib/anaconda-runtime is not owned by any package Actual Results: cf. above. Expected Results: /usr/lib/anaconda-runtime/boot/syslinux-splash.png is installed into a directory not owned by any parent package. => fedora-logos must own /usr/lib/anaconda-runtime and /usr/lib/anaconda-runtime/boot This causes these directories to stay around on the filesystem, when users remove the fedora-logos rpm. Additional info:
This needs anaconda-runtime to track ownership of its files better, since it requires fedora-logos.
Jeremy, what do you think here? Do we want fedora-logos to own that dir, or what? I'm pretty sure we don't want fedora-logos to depend on anaconda-runtime...
Hello? It's been 19 months since last reply. If anaconda-runtime depends on fedora-logos, perhaps either move the files owned by fedora-logos somewhere else, or as Ralf suggested, make fedora-logos own the directories concerned?
*** Bug 442146 has been marked as a duplicate of this bug. ***
the following folders should be owned by fedora-logos: /usr/lib/anaconda-runtime /usr/lib/anaconda-runtime/boot /usr/share/anaconda /usr/share/anaconda/pixmaps
The following folders should be owned by fedora-logos: /usr/lib/anaconda-runtime /usr/lib/anaconda-runtime/boot /usr/share/anaconda /usr/share/anaconda/pixmaps /usr/share/kde-settings /usr/share/kde-settings/kde-profile /usr/share/kde-settings/kde-profile/default /usr/share/kde-settings/kde-profile/default/share /usr/share/kde-settings/kde-profile/default/share/icons /usr/share/kde-settings/kde-profile/default/share/icons/Fedora-KDE /usr/share/kde-settings/kde-profile/default/share/icons/Fedora-KDE/16x16 /usr/share/kde-settings/kde-profile/default/share/icons/Fedora-KDE/16x16/places /usr/share/kde-settings/kde-profile/default/share/icons/Fedora-KDE/24x24 /usr/share/kde-settings/kde-profile/default/share/icons/Fedora-KDE/24x24/places /usr/share/kde-settings/kde-profile/default/share/icons/Fedora-KDE/32x32 /usr/share/kde-settings/kde-profile/default/share/icons/Fedora-KDE/32x32/places /usr/share/kde-settings/kde-profile/default/share/icons/Fedora-KDE/36x36 /usr/share/kde-settings/kde-profile/default/share/icons/Fedora-KDE/36x36/places /usr/share/kde-settings/kde-profile/default/share/icons/Fedora-KDE/48x48 /usr/share/kde-settings/kde-profile/default/share/icons/Fedora-KDE/48x48/places /usr/share/kde-settings/kde-profile/default/share/icons/Fedora-KDE/96x96 /usr/share/kde-settings/kde-profile/default/share/icons/Fedora-KDE/96x96/places /usr/share/kde4 /usr/share/kde4/apps /usr/share/kde4/apps/ksplash /usr/share/kde4/apps/ksplash/Themes /usr/share/rhgb
this bug is still present in fedora-logos-9.99.0-1.fc10
Fixed in fedora-logos-10.0.1-1.fc10