Description of problem: When running livecd-creator I got the following message printed out when the solar plugin was installed: warning: %post(plymouth-plugin-solar-0.6.0-1.fc10.i386) scriptlet failed, exit status 1 plymouth-libs, plymouth-scripts and plymouth-plugin-label had all already been installed before plymouth-plugin-solar. Version-Release number of selected component (if applicable): How reproducible: Steps to Reproduce: 1.I was run livecd-creator trying to build a new games spin and was pointing to a number of local repositories for F10 including Everything, Updates, Updates-testing and one I created with some recent F10 updates that haven't made it to updates or updates-testing yet. 2. 3. Actual results: Expected results: Additional info:
Strange because I updated with the plymouth-plugin-solar from updates-testing and received no errors upon package update. plymouth-plugin-solar scripts: $ rpm -q plymouth-plugin-solar --scripts postinstall scriptlet (using /bin/sh): export LIB=lib if [ $1 -eq 1 ]; then /usr/sbin/plymouth-set-default-plugin solar fi postuninstall scriptlet (using /bin/sh): export LIB=lib if [ $1 -eq 0 ]; then if [ "$(/usr/sbin/plymouth-set-default-plugin)" == "solar" ]; then /usr/sbin/plymouth-set-default-plugin text fi fi Could it be that "plymouth-set-default-plugin" does not exist prior to it being called? It is contained in "plymouth-scripts-0.6.0-0.2008.11.17.3.fc10.i386" so is that being installed?
I wouldn't expect to see it on an update as the package its scripts need are likely to already be installed. It is something you would see on a fresh install or a livecd build. And even there you could get random successes in spite of a missing dependency requirement depending on the order in which packages get installed. My guess is that some command that is used by the script wasn't installed, causing the script to fail. It looked like most or all of the intentional failure paths in the script printed an error message to stderr and I didn't see any other messages.
Bruno, please read my comment again. I listed exactly what the scripts do. It seems there is no requirement by plymouth-plugin-solar for the plymouth-scripts package. This is the problem.
plymouth-plugin-solar requires /usr/sbin/plymouth-set-default-plugin which effectively does the same thing. plymouth-scripts had already been installed by the time plymouth-plugin-solar was installed in the case I saw the error message, so I am not convinced a Requires(pre): plymouth-scripts will prevent this.
Bruno, just to be sure, you're doing a 32-bit spin on a 32-bit machine?
Yes. And both the build machine and the target are F10. I did notice a post today of a patch on the live cd list mentioning that using --tmpdir can cause dependency problems. I am using the --tmpdir option, so perhaps what I am seeing is related to what that patch is fixing. I can test that theory out tonight.
I tried applying the forthcoming patch to create.py from livecd-tools and I am still seeing the error message while building the games spin. So it doesn't seem to be related to the --tmpdir issue reported on the livecd list.
This is also happening in F11 (Rawhide): Installing: plymouth-plugin-solar ################### [ 683/1260] warning: %post(plymouth-plugin-solar-0.6.0-2.fc11.i386) scriptlet failed, exit status 1
I can`t reproduce it with F11 (Rawhide 1 week close to GA). Bruno does it still fail for you? -- Fedora Bugzappers volunteer triage team https://fedoraproject.org/wiki/BugZappers
I will be building a livedvd image later today and will save the output so I can look for the error message.
I think plymouth has changed enough since the report that this can be closed. There isn't even a plymouth-plugin-solar any more (it's now plymouth-theme-solar). I did run livecd-creator to make a custom game spin and didn't see any errors related to plymouth dependencies. The charge theme gets pulled in instead of solar. But without evidence of a bug I think it's best just to close this.
Hello We're glad it's fixed and you're able to create your custom spins again. I change the Status to "Closed - Worksforme". Thank you for your contribution to Fedora. -- Fedora Bugzappers volunteer triage team https://fedoraproject.org/wiki/BugZappers