Note: This is a public test instance of Red Hat Bugzilla. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback at bugzilla.redhat.com.
Bug 169282 - fedora-logos should own /usr/lib/anaconda-runtime
Summary: fedora-logos should own /usr/lib/anaconda-runtime
Keywords:
Status: CLOSED RAWHIDE
Alias: None
Product: Fedora
Classification: Fedora
Component: fedora-logos
Version: rawhide
Hardware: All
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Tom "spot" Callaway
QA Contact:
URL:
Whiteboard:
: 442146 (view as bug list)
Depends On: 189415
Blocks: F10Target
TreeView+ depends on / blocked
 
Reported: 2005-09-26 14:31 UTC by Ralf Corsepius
Modified: 2008-11-06 21:26 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2008-11-06 21:26:03 UTC
Type: ---
Embargoed:

Attachments (Terms of Use)

Description Ralf Corsepius 2005-09-26 14:31:20 UTC 
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:
Comment 1 Jesse Keating 2006-04-19 20:32:47 UTC 
This needs anaconda-runtime to track ownership of its files better, since it
requires fedora-logos.
Comment 2 Jesse Keating 2006-06-21 21:02:37 UTC 
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...
Comment 5 Michel Alexandre Salim 2008-01-27 02:53:35 UTC 
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?
Comment 6 Matthias Clasen 2008-05-06 04:06:15 UTC 
*** Bug 442146 has been marked as a duplicate of this bug. ***
Comment 7 petrosyan 2008-05-13 14:42:04 UTC 
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
Comment 8 petrosyan 2008-05-21 03:44:15 UTC 
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
Comment 9 petrosyan 2008-08-04 17:01:21 UTC 
this bug is still present in fedora-logos-9.99.0-1.fc10
Comment 10 Tom "spot" Callaway 2008-11-06 21:26:03 UTC 
Fixed in fedora-logos-10.0.1-1.fc10
Note You need to log in before you can comment on or make changes to this bug.