Hide Forgot
+++ This bug was initially created as a clone of Bug #547152 +++ Description of problem: It's impossible to create a livecd with "selinux --disabled" if system-config-firewall-base is not explicitly listed in the ks. This error also seems to occur if the selinux line is commented out. Version-Release number of selected component (if applicable): livecd-tools-16.9-1.fc16.x86_64 How reproducible: always Steps to Reproduce: 1. "selinux --disabled" in kickstart 2. make sure @admin-tools or system-config-firewall are in the package set Actual results: Error creating Live CD : Unable to disable SELinux because the installed package set did not include the file /usr/sbin/lokkit Expected results: This behavior is very confusing because /usr/sbin/lokkit actually is in the package set. livecd-tools should be smart enough to realize that lokkit/system-config-firewall-base are pulled in by system-config-firewall/@admin-tools --- Additional comment from wtogami on 2009-12-15 15:55:28 EST --- This is not a bug in livecd-tools. The bug should be against system-config-firewall? --- Additional comment from cwickert on 2009-12-15 17:24:57 EST --- Huh? The deps of the s-c-f packages are ok and the message comes from /usr/lib/python2.6/site-packages/imgcreate/kickstart.py which is part of livecd-tools. --- Additional comment from fedora-admin-xmlrpc on 2010-05-07 11:41:35 EDT --- This package has changed ownership in the Fedora Package Database. Reassigning to the new owner of this component. --- Additional comment from fabsh on 2010-08-02 04:32:41 EDT --- I can confirm this bug. Looks like a problem in livecd-tools to me as well. --- Additional comment from bruno on 2010-09-11 13:42:31 EDT --- Maybe. The call ayum.installHasFile(file) is used to check this. It may be inappropriate use by livecd-creator or there might be a yum bug. --- Additional comment from updates on 2010-09-12 00:19:32 EDT --- livecd-tools-034-1.fc14 has been submitted as an update for Fedora 14. https://admin.fedoraproject.org/updates/livecd-tools-034-1.fc14 --- Additional comment from updates on 2010-09-13 14:09:17 EDT --- livecd-tools-034-2.fc14 has been pushed to the Fedora 14 testing repository. If problems still persist, please make note of it in this bug report. If you want to test the update, you can install it with su -c 'yum --enablerepo=updates-testing update livecd-tools'. You can provide feedback for this update here: https://admin.fedoraproject.org/updates/livecd-tools-034-2.fc14 --- Additional comment from updates on 2010-09-14 23:22:16 EDT --- livecd-tools-034-7.fc14 has been submitted as an update for Fedora 14. https://admin.fedoraproject.org/updates/livecd-tools-034-7.fc14 --- Additional comment from updates on 2010-09-15 02:51:34 EDT --- livecd-tools-034-7.fc14 has been pushed to the Fedora 14 testing repository. If problems still persist, please make note of it in this bug report. If you want to test the update, you can install it with su -c 'yum --enablerepo=updates-testing update livecd-tools'. You can provide feedback for this update here: https://admin.fedoraproject.org/updates/livecd-tools-034-7.fc14 --- Additional comment from updates on 2010-09-15 23:46:20 EDT --- livecd-tools-034-7.fc14 has been pushed to the Fedora 14 stable repository. If problems still persist, please make note of it in this bug report. --- Additional comment from kparal on 2010-10-14 06:18:01 EDT --- This is still broken in F13. Any chance of pushing this fix also to F13? --- Additional comment from bruno on 2010-10-14 09:21:44 EDT --- At some point I think I would be willing to bring 034 to F13, since it is mostly a bug fix release and shouldn't break existing workflows. I'd like to wait until it has had a chance to get some serious testing before doing that though. If you have a special need for it now, you should be able to easily build an F13 version for your own use. --- Additional comment from bugs on 2012-01-08 00:29:24 EST --- This bug still occurs with livecd-tools in F16.
creator.py calls __can_handle_selinux(ayum) which supposedly checks to make sure lokkit is installed -- but only when selinux is running on the host. What is the output of getenforce on your build host?
This can probably be closed now without doubts, since lokkit is no longer used in imgcreate. But there's a new similar annoyance in bug #884878 in F18.
This message is a reminder that Fedora 16 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 16. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as WONTFIX if it remains open with a Fedora 'version' of '16'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version prior to Fedora 16's end of life. Bug Reporter: Thank you for reporting this issue and we are sorry that we may not be able to fix it before Fedora 16 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged to click on "Clone This Bug" and open it against that version of Fedora. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete. The process we are following is described here: http://fedoraproject.org/wiki/BugZappers/HouseKeeping
Fedora 16 changed to end-of-life (EOL) status on 2013-02-12. Fedora 16 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. Thank you for reporting this bug and we are sorry it could not be fixed.