Red Hat Bugzilla – Bug 202354
control-center %post script errors make for a noisy but incorrect installation
Last modified: 2007-11-30 17:11:40 EST
Description of problem:
As a result of typos in a %post script one gets during an installation
(many lines skipped)
`/schemas/apps/gnome_settings_daemon/power_manager/start_power_manager' to key
I/O warning : failed to load external entity " "
Failed to open ` ': No such file or directory
This is a result of a trailing blank on a line
Also instead of
/etc/gconf/schemas/fontilus.schemas themus.schemas >& /dev/null
it should be there
/etc/gconf/schemas/themus.schemas >& /dev/null
Actually postuninstall script is even in a worse shape. There are trailing
blanks all over the place, making intended continuation lines ineffective,
and a bare "themus.schemas" instead of a full path is also there.
Version-Release number of selected component (if applicable):
Looking closer "a worse shape" for postuninstall script is not
correct. It is really the same as for %post. A trailing blank
where it should not be one and missing path to themus.schemas.
What version of control-center? I'm not seeing this in the cvs spec file...
(Maybe it already got fixed?)
Oh, it looks like Matthias already fixed it:
+* Sun Aug 13 2006 Matthias Clasen <email@example.com> - 2.15.01-2.fc6
+- fix spec file (pointed out by Yanko Kaneti)
> What version of control-center?
> Version-Release number of selected component (if applicable):
This is what showed up in the latest rawhide.
> Oh, it looks like Matthias already fixed it
Hm, something seems to be out of sync somehwere. Here is what
'rpm -q --changelog control-center' has to say:
* Sun Aug 13 2006 Matthias Clasen <firstname.lastname@example.org> - 2.15.90-1.fc6
- Update to 2.15.91
* Mon Aug 07 2006 Karsten Hopp <email@example.com> 2.15.90-4
- add fix for new libebook api
Yes, I realize that versions on the right hand side are going backwards.
Unless "2.15.01-2.fc6" in what you quote was really supposed to
be "2.15.91-2.fc6"? Could somebody please to check?
typo in the changelog version number, will be fixed in the next build