Bug 141512
Summary: | /etc/issue{,.net} are replaced on installation of fedora-release package | ||
---|---|---|---|
Product: | [Fedora] Fedora | Reporter: | Aaron Gaudio <madcap> |
Component: | fedora-release | Assignee: | Elliot Lee <sopwith> |
Status: | CLOSED WONTFIX | QA Contact: | |
Severity: | medium | Docs Contact: | |
Priority: | medium | ||
Version: | 3 | CC: | wtogami |
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2004-12-01 21:11:11 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
Aaron Gaudio
2004-12-01 18:54:19 UTC
This is a policy decision with some tradeoffs that clearly causes problems in your situation. However, the overwriting is needed to make /etc/issue updates happen properly in certain other situations, so I'll probably stick with the current policy to upset the least number of people. I don't understand what the other situations are... if you use the confignoreplace option in the rpm spec (or whatever that option is), it will overwrite the existing /etc/issue if it hasn't been edited; otherwise it will create an /etc/issue.rpmnew and leave a custom-edited /etc/issue alone. I can't see any situation in which someone who has a custom-edited /etc/issue would need to have it always replaced with the standard /etc/issue (and in the few cases in which someone might want to do this, that's why the rpmnew file would be there). |