Bug 156407 - /usr/lib/qt-3.3/etc/settings/qtrc should be marked as a config file in the .spec file
/usr/lib/qt-3.3/etc/settings/qtrc should be marked as a config file in the .s...
Product: Red Hat Enterprise Linux 4
Classification: Red Hat
Component: redhat-artwork (Show other bugs)
All Linux
medium Severity medium
: ---
: ---
Assigned To: David Zeuthen
Depends On:
  Show dependency treegraph
Reported: 2005-04-29 16:31 EDT by R P Herrold
Modified: 2013-03-05 22:43 EST (History)
1 user (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2012-06-20 11:55:01 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description R P Herrold 2005-04-29 16:31:06 EDT
# rpm -Va
S.5....T    /usr/lib/qt-3.3/etc/settings/qtrc
Description of problem:---------^  there should be a 'c' there

... properly, this file is a configuration file, and should be so marked in the
.spec file so that RPM may properly know to save a .rpmsave, etc
Comment 1 R P Herrold 2006-07-14 22:48:11 EDT
ping - this one line spec file change to mark what is clearly a config file,
cannot take a year -- PLEASE, can we get it changed?
Comment 2 R P Herrold 2007-01-08 18:16:53 EST
still unfixed -- still a config file, still owned by the same package -- 

what is needed to get this noted as a config file?

$ rpm -V redhat-artwork
missing   c /root/.gtkrc
S.5....T    /usr/lib/qt-3.3/etc/settings/qtrc
Comment 3 R P Herrold 2007-02-25 18:27:13 EST
ping -- RHEL 4.5 is coming -- Shall this 20 second fix get included?
Comment 4 R P Herrold 2007-03-29 11:24:25 EDT
This is an easyfix -- how do I get it done in the 4.5 beta?
Comment 5 R P Herrold 2008-04-08 14:05:41 EDT
Is any further information needed to advance this bug?  I see it is still in NEW
Comment 6 R P Herrold 2008-12-08 09:35:46 EST
another 8 months for a one character change.

How does this get addressed?
Comment 7 Jiri Pallich 2012-06-20 11:55:01 EDT
Thank you for submitting this issue for consideration in Red Hat Enterprise Linux. The release for which you requested us to review is now End of Life. 
Please See https://access.redhat.com/support/policy/updates/errata/

If you would like Red Hat to re-consider your feature request for an active release, please re-open the request via appropriate support channels and provide additional supporting details about the importance of this issue.

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