Bug 144
Summary: | terminfo files location changed | ||
---|---|---|---|
Product: | [Retired] Red Hat Linux | Reporter: | ondrej.pejsa |
Component: | ncurses | Assignee: | Cristian Gafton <gafton> |
Status: | CLOSED WONTFIX | QA Contact: | |
Severity: | low | Docs Contact: | |
Priority: | low | ||
Version: | 5.2 | CC: | ondrej.pejsa |
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | i386 | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 1998-11-20 13:35:32 UTC | Type: | --- |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: |
Description
ondrej.pejsa
1998-11-20 10:38:12 UTC
This is one of the RPM shortcomings - we can not reliably replace one directory with a symlink to another directory when upgrading the rpm. This will take some engineering efforts to fix it in the rpm and terminfo is not the only package that experiences problems because of that. Basically only the programs that have ncurses linked statically in experience this problem. As always, staically linking libraries into executables is a BAD thing. *** Bug 151 has been marked as a duplicate of this bug. *** Is it possible to work around this RPM problem by creating symlinks in the %post script instead of putting symlinks into the package itself? That would work in an idal world where we know that no other package is providing files under /usr/lib/terminfo. In real life we can not guarantee that, so doing a "rm -rf /usr/lib/terminfo" on a live filesystem is a no-go. What about something like % post if [ ! -e /usr/lib/terminfo ]; then ln -s /usr/share/terminfo /usr/lib/terminfo fi ? It's not perfect, but at least harmless and would help some people FEDORA-2020-d358d5b0d8 has been pushed to the Fedora 32 stable repository. If problem still persists, please make note of it in this bug report. FEDORA-2020-7a574982d6 has been pushed to the Fedora 31 stable repository. If problem still persists, please make note of it in this bug report. FEDORA-2020-0fedf74544 has been pushed to the Fedora 33 stable repository. If problem still persists, please make note of it in this bug report. FEDORA-EPEL-2020-66f3795e72 has been pushed to the Fedora EPEL 8 stable repository. If problem still persists, please make note of it in this bug report. FEDORA-EPEL-2020-7dbefa245f has been pushed to the Fedora EPEL 7 stable repository. If problem still persists, please make note of it in this bug report. |