Description of problem: I just installed galeon with "yum install galeon" and noticed that its postinstall scriptlet displays stuff to stderr that should be redirected to /dev/null: gconfd-2: no process killed Version-Release number of selected component (if applicable): galeon-2.0.3-13.fc8 How reproducible: I've only done it once, and haven't tried to reproduce it, however it should be 100% reproduceable so long as the conditions are met that cause the errors to be displayed to stderr. Steps to Reproduce: 1. Make sure galeon is not already installed on your system. 2. Make sure gconfd-2 is not running currently. 3. "yum install galeon" Actual results: Running Transaction Installing: galeon ######################### [1/1] gconfd-2: no process killed Installed: galeon.x86_64 0:2.0.3-13.fc8 Complete! Additional info: The correct fix for this problem is to redirect stderr and stdout to /dev/null on any commands in the script(s) that we don't want to see any errors about during installation. I'll attach a suggested fix shortly.
Created attachment 253891 [details] Full output of "yum install galeon" showing error.
Created attachment 254641 [details] patch to clean up rpm scriptlets for galeon.spec Here's a patch to clean up the scriptlets, not yet tested, but it should work. All I've done is enclose each script within braces and perform stderr/stdout redirection on the collective, as well as discarding the return code of the collective. I'm building a test package and will give an update when I've tested it.
Fixed in CVS thanks.
Testing results: pts/0 root@hammer:/home/mharris/rpmbuild/8/RPMS# rpm -Uvh galeon-2.0.3-14.fc8athlon64.x86_64.rpm Preparing... ########################################### [100%] 1:galeon ########################################### [100%] pts/0 root@hammer:/home/mharris/rpmbuild/8/RPMS# Looks good.