Bug 554491
| Summary: | /var/lib/BackupPC should be excluded from locate(1) database | ||
|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | Joel Uckelman <uckelman> |
| Component: | BackupPC | Assignee: | Bernard Johnson <bjohnson> |
| Status: | CLOSED ERRATA | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
| Severity: | medium | Docs Contact: | |
| Priority: | low | ||
| Version: | 14 | CC: | bjohnson, fedora |
| Target Milestone: | --- | ||
| Target Release: | --- | ||
| Hardware: | x86_64 | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Fixed In Version: | BackupPC-3.2.1-1.el5 | Doc Type: | Bug Fix |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2011-08-09 01:37:56 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
Joel Uckelman
2010-01-11 20:27:03 UTC
I think BackupPC rpm do not have to change any file owned by another package (maybe I'm wrong, but I'm almost sure of that). If you do not want backup tree to be added in locate db, I think the only solution you have is to add the path yourself to the updatedb.conf file. Another solution would be to add /var/lib/BackupPC to default updatedb.conf file, but I do not really know if it's a good idea, and how to request that. The thing I can do for now is to add the trick in the README.fedora file. (In reply to comment #1) > > Another solution would be to add /var/lib/BackupPC to default updatedb.conf > file, but I do not really know if it's a good idea, and how to request that. The person to ask about that would be the maintainer of the mlocate RPM, since updatedb.conf is owned by that package. (In reply to comment #1) > I think BackupPC rpm do not have to change any file owned by another package > (maybe I'm wrong, but I'm almost sure of that). > I don't see anything in the packaging guidelines which prohibits the install script for a package from editing a config file belonging to another package: https://fedoraproject.org/wiki/Packaging/Guidelines In fact, I can think of at least one example of this: Whenever you install a new shell (e.g., bash, zsh, csh), the path to its binary is added to /etc/shells. Similarly, the path is removed when you uninstall a shell. But /etc/shells is owned by the setup package, not by any of the shell packages. You could do sed -e '/PRUNEPATHS/s/"$/ \/var\/lib\/BackupPC"/' /etc/updatedb.conf for installation, and sed -e '/PRUNEPATHS/s/[ ]*\/var\/lib\/BackupPC//' /etc/updatedb.conf for removal. This remains broken in BackupPC-3.1.0-16.fc14.x86_64. This message is a reminder that Fedora 13 is nearing its end of life. Approximately 30 (thirty) days from now Fedora will stop maintaining and issuing updates for Fedora 13. 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 '13'. 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 13'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 13 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 Replying to clear NEEDINFO... BackupPC-3.2.1-1.fc14 has been submitted as an update for Fedora 14. https://admin.fedoraproject.org/updates/BackupPC-3.2.1-1.fc14 BackupPC-3.2.1-1.fc15 has been submitted as an update for Fedora 15. https://admin.fedoraproject.org/updates/BackupPC-3.2.1-1.fc15 BackupPC-3.2.1-1.el5 has been submitted as an update for Fedora EPEL 5. https://admin.fedoraproject.org/updates/BackupPC-3.2.1-1.el5 BackupPC-3.2.1-1.el6 has been submitted as an update for Fedora EPEL 6. https://admin.fedoraproject.org/updates/BackupPC-3.2.1-1.el6 Package BackupPC-3.2.1-1.el5: * should fix your issue, * was pushed to the Fedora EPEL 5 testing repository, * should be available at your local mirror within two days. Update it with: # su -c 'yum update --enablerepo=epel-testing BackupPC-3.2.1-1.el5' as soon as you are able to. Please go to the following url: https://admin.fedoraproject.org/updates/BackupPC-3.2.1-1.el5 then log in and leave karma (feedback). BackupPC-3.2.1-1.fc14 has been pushed to the Fedora 14 stable repository. If problems still persist, please make note of it in this bug report. BackupPC-3.2.1-1.fc15 has been pushed to the Fedora 15 stable repository. If problems still persist, please make note of it in this bug report. BackupPC-3.2.1-1.el6 has been pushed to the Fedora EPEL 6 stable repository. If problems still persist, please make note of it in this bug report. BackupPC-3.2.1-1.el5 has been pushed to the Fedora EPEL 5 stable repository. If problems still persist, please make note of it in this bug report. |