Description of problem: Can shared-mime-info %ghost a few items in /usr/share/mime? Once the mime cache is generated the unknown files look a bit odd Version-Release number of selected component (if applicable): shared-mime-info-1.8-2.fc26.x86_64 How reproducible: Steps to Reproduce: 1.Install minimal system 2.rpm -qf /usr/share/mime/* 2. 3. Actual results: file /usr/share/mime/XMLnamespaces is not owned by any package file /usr/share/mime/aliases is not owned by any package file /usr/share/mime/application is not owned by any package file /usr/share/mime/audio is not owned by any package file /usr/share/mime/generic-icons is not owned by any package file /usr/share/mime/globs is not owned by any package file /usr/share/mime/globs2 is not owned by any package file /usr/share/mime/icons is not owned by any package file /usr/share/mime/image is not owned by any package file /usr/share/mime/inode is not owned by any package file /usr/share/mime/magic is not owned by any package file /usr/share/mime/message is not owned by any package file /usr/share/mime/mime.cache is not owned by any package file /usr/share/mime/model is not owned by any package file /usr/share/mime/multipart is not owned by any package shared-mime-info-1.8-2.fc26.x86_64 file /usr/share/mime/subclasses is not owned by any package file /usr/share/mime/text is not owned by any package file /usr/share/mime/treemagic is not owned by any package file /usr/share/mime/types is not owned by any package file /usr/share/mime/version is not owned by any package file /usr/share/mime/video is not owned by any package file /usr/share/mime/x-content is not owned by any package file /usr/share/mime/x-epoc is not owned by any package Expected results: Since these files a generated via shared-mime-info and automatically created, can they be added as %ghost and noverify? Additional info:
This bug appears to have been reported against 'rawhide' during the Fedora 28 development cycle. Changing version to '28'.
This message is a reminder that Fedora 28 is nearing its end of life. On 2019-May-28 Fedora will stop maintaining and issuing updates for Fedora 28. 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 EOL if it remains open with a Fedora 'version' of '28'. 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. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 28 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, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. 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.
This bug appears to have been reported against 'rawhide' during the Fedora 31 development cycle. Changing version to '31'.
This bug appears to have been reported against 'rawhide' during the Fedora 31 development cycle. Changing version to 31.
This bug appears to have been reported against 'rawhide' during the Fedora 33 development cycle. Changing version to 33.
This package has changed maintainer in the Fedora. Reassigning to the new maintainer of this component.
This should be an easy fix, I'll have a look.
The content of the directories is presumably created by update-mime-database. Not sure how to know upfront what files to %ghost. The shared-mime-info package can own the directories, but owning the files might be actually tricky.
https://lists.fedoraproject.org/archives/list/packaging@lists.fedoraproject.org/thread/Q3OC2JTNSTBJ55PI47BB3NNR2C56K33V/
Handled by https://src.fedoraproject.org/rpms/shared-mime-info/pull-request/1
FEDORA-2020-bf5b8e7ebb has been pushed to the Fedora 34 stable repository. If problem still persists, please make note of it in this bug report.
FEDORA-2020-4effbf97aa has been pushed to the Fedora ELN stable repository. If problem still persists, please make note of it in this bug report.