Description of problem:
We've already hit this problem when we reved pirut in 5.2, so I'd like to fix
it properly before we try i18n in core yum for 5.3. The fix is literally:
--- Python-2.5.1/Lib/gettext.py.plural 2007-09-10 11:38:57.000000000 -0400
+++ Python-2.5.1/Lib/gettext.py 2007-09-10 11:39:00.000000000 -0400
@@ -299,6 +299,8 @@ class GNUTranslations(NullTranslations):
item = item.strip()
if not item:
+ if item.startswith("#"):
if ':' in item:
k, v = item.split(':', 1)
k = k.strip().lower()
...and without it python gives a backtrace a couple of lines later (depending on
At the same time we might as well add the socket constants requested in Fedora
(literally just int values within the sockets module) and the XMLRPC fix (2
lines, only triggers on the failure path -- so no chance of causing a problem).
We might also want to get the update for CVE-2007-4965, although that hasn't
gone in Fedora yet.
All the patches from Fedora 9 apply directly, and there's currently no other BZ
about python problems ... so almost no chance we'll want to change python for 5.3.
This request was previously evaluated by Red Hat Product Management
for inclusion in the current Red Hat Enterprise Linux release, but
Red Hat was unable to resolve it in time. This request will be
reviewed for a future Red Hat Enterprise Linux release.
James: can you describe (or point to) a bit more detail on what the root problem
that posted patch in comment#0 fixes? I'd be interested in finding a reproducer
that QA can use for validation.
You note that additional patches will be added. Can you provide links to those
patches as well as any recommended reproducer/verification steps?
James, can you please provide a test case for this issue?
I cannot find any details about how to reproduce this bug.
Probably the easiest one is to revert the workaround in:
[Bug 431073] pirut crashs with german locale
Upstream bug: http://bugs.python.org/issue1448060
An advisory has been issued which should help the problem
described in this bug report. This report is therefore being
closed with a resolution of ERRATA. For more information
on therefore solution and/or where to find the updated files,
please follow the link below. You may reopen this bug report
if the solution does not work for you.