Back to bug 1701605
| Who | When | What | Removed | Added |
|---|---|---|---|---|
| Red Hat Bugzilla | 2019-04-19 20:30:02 UTC | Pool ID | 0 | 79 |
| Kamil Dudka | 2019-04-19 22:17:55 UTC | CC | ashankar, codonell, dj, fweimer, kdudka, mnewsome, pfrankli | |
| Component | bash | glibc | ||
| Assignee | svashisht | glibc-bugzilla | ||
| QA Contact | kvolny | qe-baseos-tools | ||
| Florian Weimer | 2019-04-23 11:43:28 UTC | Status | NEW | ASSIGNED |
| Summary | The locale command returns a vague error message if the LOCPATH environment variable is defined. | glibc: The locale command returns a vague error message if the LOCPATH environment variable is defined. | ||
| Florian Weimer | 2019-04-23 11:59:43 UTC | Link ID | Sourceware 24478 | |
| Florian Weimer | 2019-04-24 12:34:31 UTC | Keywords | Patch | |
| Florian Weimer | 2019-04-30 16:24:08 UTC | Target Release | --- | 8.1 |
| Component | glibc | glibc | ||
| Version | 7.6 | 8.1 | ||
| Product | Red Hat Enterprise Linux 7 | Red Hat Enterprise Linux 8 | ||
| Florian Weimer | 2019-04-30 16:25:06 UTC | Pool ID | 79 | 182 |
| Carlos O'Donell | 2019-05-08 22:37:37 UTC | Deadline | 2019-05-22 | |
| Assignee | glibc-bugzilla | ashankar | ||
| Sergey Kolosov | 2019-05-09 13:38:21 UTC | CC | skolosov | |
| Carlos O'Donell | 2019-05-15 16:10:25 UTC | Blocks | 1684553 | |
| Arjun Shankar | 2019-05-22 15:50:31 UTC | Status | ASSIGNED | MODIFIED |
| Fixed In Version | glibc-2.28-57.el8 | |||
| Doc Text | Cause: The locale program did not provide any diagnostics for the LOCPATH environment variable. Consequence: When locale returned erroneous output because of an invalid LOCPATH, the cause of this error was not clear. Fix: The locale program has now been fixed so as to warn that the LOCPATH environment variable has been set whenever it encounters an error during execution. Result: The locale program now reports the LOCPATH environment variable along with any underlying errors encountered by it. | |||
| Doc Type | If docs needed, set a value | Bug Fix | ||
| errata-xmlrpc | 2019-05-31 19:14:48 UTC | Status | MODIFIED | ON_QA |
| Florian Weimer | 2019-06-05 15:13:22 UTC | Depends On | 1717492 | |
| Matt Newsome | 2019-06-17 11:36:47 UTC | Blocks | 1721112 | |
| Matt Newsome | 2019-06-17 11:37:40 UTC | Blocks | 1721112 | |
| Vladimír Slávik | 2019-07-12 16:00:27 UTC | CC | vslavik | |
| Docs Contact | vslavik | |||
| Lucie Vařáková | 2019-08-19 13:53:28 UTC | CC | lmanasko | |
| Docs Contact | vslavik | ajamaiya | ||
| Sergey Kolosov | 2019-09-03 12:44:12 UTC | Status | ON_QA | VERIFIED |
| Abhimanyu Jamaiyar | 2019-09-06 13:45:29 UTC | Doc Text | Cause: The locale program did not provide any diagnostics for the LOCPATH environment variable. Consequence: When locale returned erroneous output because of an invalid LOCPATH, the cause of this error was not clear. Fix: The locale program has now been fixed so as to warn that the LOCPATH environment variable has been set whenever it encounters an error during execution. Result: The locale program now reports the LOCPATH environment variable along with any underlying errors encountered by it. | .The `locale` program now warns about the `LOCPATH` environment variable being set whenever it encounters an error during execution Previously,the `locale` program did not provide any diagnostics for the `LOCPATH` environment variable. As a consequence, the locale command `-glibc` returned an error message while defining the `LOCPATH` environment variable. The `locale` program is now set to warn that the `LOCPATH` environment variable has been set any time it encounters an error during execution. As a result, the locale program now reports the `LOCPATH` environment variable along with any underlying errors that it encounters. |
| Flags | needinfo?(ashankar) | |||
| Arjun Shankar | 2019-09-10 14:20:10 UTC | Flags | needinfo?(ashankar) | |
| Abhimanyu Jamaiyar | 2019-09-10 15:46:16 UTC | Doc Text | .The `locale` program now warns about the `LOCPATH` environment variable being set whenever it encounters an error during execution Previously,the `locale` program did not provide any diagnostics for the `LOCPATH` environment variable. As a consequence, the locale command `-glibc` returned an error message while defining the `LOCPATH` environment variable. The `locale` program is now set to warn that the `LOCPATH` environment variable has been set any time it encounters an error during execution. As a result, the locale program now reports the `LOCPATH` environment variable along with any underlying errors that it encounters. | .The `locale` program now warns about the `LOCPATH` environment variable being set whenever it encounters an error during execution Previously, the `locale` program did not provide any diagnostics for the `LOCPATH` environment variable when it encountered errors due to an invalid `LOCPATH`. The `locale` program is now set to warn that the `LOCPATH` environment variable has been set any time it encounters an error during execution. As a result, the locale program now reports the `LOCPATH` environment variable along with any underlying errors that it encounters. |
| Flags | needinfo?(ashankar) | |||
| Arjun Shankar | 2019-09-12 18:51:49 UTC | Flags | needinfo?(ashankar) | |
| Abhimanyu Jamaiyar | 2019-10-30 12:59:41 UTC | Doc Text | .The `locale` program now warns about the `LOCPATH` environment variable being set whenever it encounters an error during execution Previously, the `locale` program did not provide any diagnostics for the `LOCPATH` environment variable when it encountered errors due to an invalid `LOCPATH`. The `locale` program is now set to warn that the `LOCPATH` environment variable has been set any time it encounters an error during execution. As a result, the locale program now reports the `LOCPATH` environment variable along with any underlying errors that it encounters. | .The `locale` command now warns about `LOCPATH` being set whenever it encounters an error during execution Previously, the `locale` command did not provide any diagnostics for the `LOCPATH` environment variable when it encountered errors due to an invalid `LOCPATH`. The `locale` command is now set to warn that `LOCPATH` has been set any time it encounters an error during execution. As a result, `locale` now reports `LOCPATH` along with any underlying errors that it encounters. |
| errata-xmlrpc | 2019-11-05 00:10:20 UTC | Status | VERIFIED | RELEASE_PENDING |
| errata-xmlrpc | 2019-11-05 21:29:04 UTC | Status | RELEASE_PENDING | CLOSED |
| Resolution | --- | ERRATA | ||
| Last Closed | 2019-11-05 21:29:04 UTC | |||
| errata-xmlrpc | 2019-11-05 21:29:25 UTC | Link ID | Red Hat Product Errata RHSA-2019:3513 | |
| Red Hat One Jira (issues.redhat.com) | 2020-11-14 10:16:55 UTC | Link ID | Red Hat Issue Tracker - Private RHELPLAN-17454 | |
| Pavel Najman | 2021-09-17 12:17:42 UTC | Pool ID | sst_platform_tools_rhel_8 | sst_pt_gcc_glibc_rhel_8 |
| Mark O'Brien | 2023-07-18 14:30:35 UTC | Pool ID | sst_pt_glibc_rhel_8 | sst_pt_libraries_rhel_8 |
Back to bug 1701605