Created attachment 589622 [details] root.log Description of problem: Build of F17 Live CD fails due to an issue with Plymouth. See attached root.log Version-Release number of selected component (if applicable): F18/Rawhide How reproducible: yes Steps to Reproduce: 1. http://koji.fedoraproject.org/koji/taskinfo?taskID=4129496 3. Actual results: Fails Expected results: A working configuration for plymouth or the like. Additional info: Maybe install caribou as suggested at: http://forums.fedoraforum.org/showthread.php?s=8fcfc3d888aff30874eb1be39febf741&p=1557764#post1557764 See also: https://bugzilla.redhat.com/show_bug.cgi?id=642617
(In reply to comment #0) > Build of F17 Live CD fails due to an issue with Plymouth. 1. You are building an F18 livecd 2. The problem is caused by the %postrans script of the kernel package.
(In reply to comment #1) > (In reply to comment #0) > > Build of F17 Live CD fails due to an issue with Plymouth. > > 1. You are building an F18 livecd Right. Sorry for any confusion. > 2. The problem is caused by the %postrans script of the kernel package. Do you have a patch? Maybe someone should reassign then to Component kernel. This bug seems to break all live medias. I guess it should get some higher alertness, shouldn't it?
It's not clear to me if this is a kernel issue, or a livecd-creator one.
latest log actually shows two issues: http://koji.fedoraproject.org/koji/getfile?taskID=4153282&name=root.log 1) livecd is creating a dracut.conf that includes ext4 module when ext4 is a built in. Harald said he'll fix dracut to work around dracut.conf files that do that. 2) livecd-creator is not handling some symlink (or so) right with copyfile and it's making it blow up. moving to livecd-creator for 2. I fixed the problem mentioned in the bug summary upstream here: http://cgit.freedesktop.org/plymouth/commit/?id=d80a23cb59aee76c430b738c33480d67d940d939 It's a dep ordering issue that keeps cropping up, so I've just removed the dep.
That error would seem to indicate that /etc/localtime is a symlink to the zoneinfo file instead of a copy. I wonder why? Changing the copyfile to copy2 works fine. Also, I'd like to encourage people to give livemedia-creator a try for creating live media for F17 and later. You can find it in the lorax package.
This changed in glibc recently: https://bugzilla.redhat.com/show_bug.cgi?id=822200
Regarding "livecd is creating a dracut.conf that includes ext4 module when ext4 is a built in. Harald said he'll fix dracut to work around dracut.conf files that do that." - is it possible the identical issue exists for ext3 but wasn't fixed? I just tried to generate a live image of Rawhide with livecd-creator and I'm looking at: E: No '/dev/log' or 'logger' included for syslog logging F: Failed to install ext3 F: installkernel failed in module kernel-modules mkinitrd failed warning: %posttrans(kernel-3.6.0-0.rc0.git2.1.fc18.x86_64) scriptlet failed, exit status 1
livecd-tools-17.12-1.fc17 has been submitted as an update for Fedora 17. https://admin.fedoraproject.org/updates/livecd-tools-17.12-1.fc17
Package livecd-tools-17.12-1.fc17: * should fix your issue, * was pushed to the Fedora 17 testing repository, * should be available at your local mirror within two days. Update it with: # su -c 'yum update --enablerepo=updates-testing livecd-tools-17.12-1.fc17' as soon as you are able to. Please go to the following url: https://admin.fedoraproject.org/updates/FEDORA-2012-11389/livecd-tools-17.12-1.fc17 then log in and leave karma (feedback).
livecd-tools-17.13-1.fc17 has been submitted as an update for Fedora 17. https://admin.fedoraproject.org/updates/livecd-tools-17.13-1.fc17
This should fix things (18.7 and 17.13) adamw who has reproduced the bug tested it and confirmed that it works. For some reason I don't see the problem on my setup using F16.
livecd-tools-17.14-1.fc17 has been submitted as an update for Fedora 17. https://admin.fedoraproject.org/updates/livecd-tools-17.14-1.fc17
livecd-tools-17.14-1.fc17 has been pushed to the Fedora 17 stable repository. If problems still persist, please make note of it in this bug report.
Any chance we can update the epel 6 version too?