Description of problem: while upgrading an earlier version with rpm -Uvh i get the following error (which i think is related to SELinux) rpm -Uvh --force allegro_4.2.1-2.fc7_i386.rpm Preparing... ########################################### [100%] 1:allegro ########################################### [100%] chcon: can't apply partial context to unlabeled file /usr/lib/allegro/4.2.1/alleg-vga.so Version-Release number of selected component (if applicable): 4.2.1-2 How reproducible: rpm -Uvh --force allegro_4.2.1-2.fc7_i386.rpm Steps to Reproduce: 1.rpm -Uvh --force allegro_4.2.1-2.fc7_i386.rpm 2. 3. Actual results: Preparing... ########################################### [100%] 1:allegro ########################################### [100%] chcon: can't apply partial context to unlabeled file /usr/lib/allegro/4.2.1/alleg-vga.so Expected results: Preparing... ########################################### [100%] 1:allegro ########################################### [100%] Additional info: i was using apt-get to distribution upgrade from fc6 to fc7 (which went quite well :-)
The unlabeled file error means that for some reason the original wasn't labeled maybe because you're using apt-get (which is not supported), more likely because you have selinux disabled. Notice that this error message is harmless in case you've selinux disabled. jnovy, I do think that since it is harmless we should hide it by adding 2> /dev/null to the chcon command in the %post script, agreed?
originally, i've installed it with yum. so i guess it should have been labeled. btw. i thought that the running rpm underling yum or apt-get does the work no matter what i use to update the system with. i know it's now a big issue, but i thought you guys might want to smooth it out.
(In reply to comment #2) > originally, i've installed it with yum. so i guess it should have been labeled. > > btw. i thought that the running rpm underling yum or apt-get does the work no > matter what i use to update the system with. > It does, which is why I wrote "maybe because you're using apt-get", with emphasizes on the maybe. > i know it's now a big issue, but i thought you guys might want to smooth it out. > We do, thanks for reporting, but first we need to know why this happens, are you running with selinux disabled?
yes, selinux is disabled. and btw. i used apt-get because yum had many packedges that it couldn't upgrade so i used apt-get to move from fc6 to fc7 (first, i tried upgrading from fc7 dvd, but... anaconda crashed, which is a different bug :-(
Thanks, that explains the error. The next rawhide push should contain 4.2.1-3, which has the error output in this scenario silenced (the error was already ignored).
(In reply to comment #5) > The next rawhide push should contain 4.2.1-3, which has the error output in this > scenario silenced (the error was already ignored). > Scrap that, allegro doesn't build on rawhide at the moment, see bug 247256