Bug 1717492 - glibc: The locale command returns a vague error message if the LOCPATH environment variable is defined.
Summary: glibc: The locale command returns a vague error message if the LOCPATH enviro...
Keywords:
Status: CLOSED ERRATA
Alias: None
Deadline: 2019-05-22
Product: Fedora
Classification: Fedora
Component: glibc
Version: 29
Hardware: All
OS: Linux
unspecified
medium
Target Milestone: ---
Assignee: Florian Weimer
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks: 1701605
TreeView+ depends on / blocked
 
Reported: 2019-06-05 15:13 UTC by Florian Weimer
Modified: 2019-11-05 14:36 UTC (History)
9 users (show)

Fixed In Version: glibc-2.29.9000-17.fc31 glibc-2.29-15.fc30 glibc-2.28-32.fc29
Clone Of: 1701605
Environment:
Last Closed: 2019-11-05 14:36:51 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)

Description Florian Weimer 2019-06-05 15:13:22 UTC
+++ This bug was initially created as a clone of Bug #1701605 +++

Description of problem:
The locale command returns a vague error message if the LOCPATH environment variable is defined.

[root@rhel75test gregs]# locale
locale: Cannot set LC_CTYPE to default locale: No such file or directory
locale: Cannot set LC_MESSAGES to default locale: No such file or directory
locale: Cannot set LC_ALL to default locale: No such file or directory
.
.
.

Comment 1 Florian Weimer 2019-06-06 09:04:44 UTC
Upstream commit:

commit e485b2b6e006a7efa5d73e6be7e357a395c77fe3
Author: Florian Weimer <fweimer>
Date:   Tue Apr 23 18:16:26 2019 +0200

    locale: Add LOCPATH diagnostics to the locale program
    
    The implementation of quote_string is based on support_quote_blob.
    
    Reviewed-by: Carlos O'Donell <carlos>

Comment 2 Florian Weimer 2019-06-06 09:05:09 UTC
And, for completeness:

commit 439bf53496d6ed5fcef1d2e71793b46369f8205f
Author: Florian Weimer <fweimer>
Date:   Wed Apr 24 07:31:29 2019 +0200

    locale/tst-locale-locpath: Run test only for $(run-built-tests) == yes

Comment 3 Fedora Update System 2019-06-06 16:14:05 UTC
FEDORA-2019-62a3a5c89d has been submitted as an update to Fedora 30. https://bodhi.fedoraproject.org/updates/FEDORA-2019-62a3a5c89d

Comment 4 Fedora Update System 2019-06-06 18:16:40 UTC
FEDORA-2019-cd0e4f3119 has been submitted as an update to Fedora 29. https://bodhi.fedoraproject.org/updates/FEDORA-2019-cd0e4f3119

Comment 5 Fedora Update System 2019-06-07 01:07:34 UTC
glibc-2.29-15.fc30 has been pushed to the Fedora 30 testing repository. If problems still persist, please make note of it in this bug report.
See https://fedoraproject.org/wiki/QA:Updates_Testing for
instructions on how to install test updates.
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2019-62a3a5c89d

Comment 6 Fedora Update System 2019-06-07 05:08:35 UTC
glibc-2.28-33.fc29 has been pushed to the Fedora 29 testing repository. If problems still persist, please make note of it in this bug report.
See https://fedoraproject.org/wiki/QA:Updates_Testing for
instructions on how to install test updates.
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2019-cd0e4f3119

Comment 7 Fedora Update System 2019-06-10 00:53:07 UTC
glibc-2.29-15.fc30 has been pushed to the Fedora 30 stable repository. If problems still persist, please make note of it in this bug report.

Comment 8 Fedora Update System 2019-06-22 02:56:13 UTC
glibc-2.28-33.fc29 has been pushed to the Fedora 29 stable repository. If problems still persist, please make note of it in this bug report.

Comment 9 Ben Cotton 2019-10-31 19:06:21 UTC
This message is a reminder that Fedora 29 is nearing its end of life.
Fedora will stop maintaining and issuing updates for Fedora 29 on 2019-11-26.
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 EOL if it remains open with a
Fedora 'version' of '29'.

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.

Thank you for reporting this issue and we are sorry that we were not 
able to fix it before Fedora 29 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, you are encouraged  change the 'version' to a later Fedora 
version prior this bug is closed as described in the policy above.

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.


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