Bug 375271 - gnome-panel installation scripts are noisy
gnome-panel installation scripts are noisy
Product: Fedora
Classification: Fedora
Component: gnome-panel (Show other bugs)
All Linux
low Severity low
: ---
: ---
Assigned To: Ray Strode [halfline]
Fedora Extras Quality Assurance
Depends On:
  Show dependency treegraph
Reported: 2007-11-10 19:58 EST by Michal Jaegermann
Modified: 2009-07-14 12:15 EDT (History)
0 users

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2009-07-14 12:15:43 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description Michal Jaegermann 2007-11-10 19:58:16 EST
Description of problem:

Updates to the current rawhide have effects like these:
  Updating  : gnome-panel                  ##################### [263/534]
I/O warning : failed to load external entity "/etc/gconf/schemas/intlclock.schemas"
Failed to open `/etc/gconf/schemas/intlclock.schemas': No such file or directory
WARNING: multiple <locale> nodes for locale `en_US', ignoring all past first

File /etc/gconf/schemas/intlclock.schemas is provided by gnome-panel
package itself so the first warning likely comes from that
package preinstall scriptlet but if this really immaterial then
maybe both stdin and stderr should be sent to /dev/null and not
only the first one.

OTOH "multiple <locale> nodes for locale `en_US'" warning
is still present after the package was installed and on tries
to rerun "--makefile-install-rule" part of a corresponding
postinstall scriptlet.  Is that important?  No way to tell.
If not then why not to send that to /dev/null as well?

Version-Release number of selected component (if applicable):
Comment 1 Michal Jaegermann 2007-11-10 20:15:30 EST
BTW - I looked around on my system trying to guess what may trigger
that "multiple <locale> nodes" complaint and I still have no idea.
A value of LANG happens to be here en_CA.UTF-8

OTOH a strace output seems to indicate that 
is unhealthy and indeed that file seems to have "en_US" repeating.
Comment 2 Bug Zapper 2008-05-13 23:52:18 EDT
Changing version to '9' as part of upcoming Fedora 9 GA.
More information and reason for this action is here:
Comment 3 Bug Zapper 2009-06-09 19:09:53 EDT
This message is a reminder that Fedora 9 is nearing its end of life.
Approximately 30 (thirty) days from now Fedora will stop maintaining
and issuing updates for Fedora 9.  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 '9'.

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 9'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 9 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 please change the 'version' of this 
bug to the applicable version.  If you are unable to change the version, 
please add a comment here and someone will do it for you.

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: 
Comment 4 Bug Zapper 2009-07-14 12:15:43 EDT
Fedora 9 changed to end-of-life (EOL) status on 2009-07-10. Fedora 9 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.

Note You need to log in before you can comment on or make changes to this bug.