Description of problem: the integrity check for the fonts-KOI8-R-* packages reports modified files: "rpm -V fonts-KOI8-R-1.0-10.fc8 fonts-KOI8-R-100dpi-1.0-10.fc8 fonts-KOI8-R-75dpi-1.0-10.fc8": S.5....T /usr/share/fonts/KOI8-R/misc/fonts.dir S.5....T /usr/share/fonts/KOI8-R/100dpi/fonts.dir S.5....T /usr/share/fonts/KOI8-R/75dpi/fonts.dir Although this is not a big problem, rpm -V should not report changes in files which are changed automatically on purpose (like fonts.dir, ...). Other font packages have solved the problem e.g. using something like this in the %files section ( %{fontdir}/*.ttf %verify(not md5 size mtime) %{fontdir}/fonts.dir %verify(not md5 size mtime) %{fontdir}/fonts.scale Version-Release number of selected component (if applicable): e.g. fonts-KOI8-R-100dpi-1.0-10.fc8
This message is a reminder that Fedora 8 is nearing its end of life. Approximately 30 (thirty) days from now Fedora will stop maintaining and issuing updates for Fedora 8. 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 WONTFIX if it remains open with a Fedora 'version' of '8'. 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 prior to Fedora 8's end of life. Bug Reporter: Thank you for reporting this issue and we are sorry that we may not be able to fix it before Fedora 8 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 please change the 'version' of this bug to the applicable version. If you are unable to change the version, please add a comment here and someone will do it for you. 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. The process we are following is described here: http://fedoraproject.org/wiki/BugZappers/HouseKeeping
I've seen this problem in F10, too. I've attached a patch to the spec file which should solve the problem in a similar way the other fonts packages did: e.g. %verify(not md5 size mtime) %{bmpfontdir}/fonts.alias
Created attachment 326047 [details] patch which fixes the verify options for the fonts.dir/cache files
This message is a reminder that Fedora 10 is nearing its end of life. Approximately 30 (thirty) days from now Fedora will stop maintaining and issuing updates for Fedora 10. 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 WONTFIX if it remains open with a Fedora 'version' of '10'. 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 prior to Fedora 10's end of life. Bug Reporter: Thank you for reporting this issue and we are sorry that we may not be able to fix it before Fedora 10 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 please change the 'version' of this bug to the applicable version. If you are unable to change the version, please add a comment here and someone will do it for you. 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. The process we are following is described here: http://fedoraproject.org/wiki/BugZappers/HouseKeeping
Fedora 10 changed to end-of-life (EOL) status on 2009-12-17. Fedora 10 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. Thank you for reporting this bug and we are sorry it could not be fixed.