| Summary: | stray .pearrc files in / and /root/ | ||
|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | Alexander Ploumistos <alex.ploumistos> |
| Component: | php-pear | Assignee: | Remi Collet <fedora> |
| Status: | CLOSED EOL | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
| Severity: | unspecified | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | 28 | CC: | fedora, jorton, rpm |
| Target Milestone: | --- | ||
| Target Release: | --- | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | If docs needed, set a value | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2019-05-28 20:04:18 UTC | Type: | Bug |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
You can safely remove them. These are user configuration overrides (when pear/pecl config-set is called without system option). Notice the F25 packages should be far better (scriplet improvement) and I hope these won't appear anymore. Thanks, I'll be keeping an eye out for any new ones after the F25 release. This message is a reminder that Fedora 24 is nearing its end of life. Approximately 2 (two) weeks from now Fedora will stop maintaining and issuing updates for Fedora 24. 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 '24'. 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 24 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. I got another .pearrc in /, on the same VM, probably right after (more like during) the upgrade from F25 to F26 (12 July). I think it was absent in the meantime. This message is a reminder that Fedora 26 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 26. 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 '26'. 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 26 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. # ls -alh / […] -rw-r--r--. 1 root root 150 Apr 30 00:23 .pearrc […] 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. Fedora 28 changed to end-of-life (EOL) status on 2019-05-28. Fedora 28 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. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed. |
After the discussions on the devel list about /1 and /null, I took a look at my systems and I found a VM that runs some web applications which has a .pearrc file in / and another one in /root/, both containing the same configuration: #PEAR_Config 0.9 a:1:{s:10:"__channels";a:4:{s:12:"pecl.php.net";a:0:{}s:5:"__uri";a:0:{}s:11:"doc.php.net";a:0:{}s:20:"pear.dropbox-php.com";a:0:{}}} Based on their timestamps, /root/.pearrc was created some time in F23, while /.pearrc appeared on the day I upgraded the VM to F24. Neither seems to belong to a particular package. The php-pear package was pulled in by owncloud and I also have: php-pear-1.10.1-5.fc24.noarch php-pear-Auth-SASL-1.0.6-9.fc24.noarch php-pear-Cache-Lite-1.7.16-4.fc24.noarch php-pear-DB-1.9.2-2.fc24.noarch php-pear-HTTP-OAuth-0.3.2-2.fc24.noarch php-pear-HTTP-Request2-2.3.0-1.fc24.noarch php-pear-Log-1.13.1-1.fc24.noarch php-pear-Mail-1.3.0-2.fc24.noarch php-pear-MDB2-2.5.0-0.13.b5.fc24.noarch php-pear-Net-SMTP-1.7.2-1.fc24.noarch php-pear-Net-Socket-1.0.14-5.fc24.noarch php-pear-Net-URL2-2.2.1-1.fc24.noarch I grabbed the source rpm, unpacked it and every tarball inside it and grepped for .pearrc, but it does not seem to be explicitly created by something in the package: $ grep -r "\.pearrc" php-pear-1.10.1-5.fc24.src/ php-pear-1.10.1-5.fc24.src/PEAR_Manpages-1.10.0/PEAR_Manpages-1.10.0/man1/pear.1:.B $HOME/.pearrc php-pear-1.10.1-5.fc24.src/PEAR_Manpages-1.10.0/PEAR_Manpages-1.10.0/man5/pear.conf.5:.B $HOME/.pearrc php-pear-1.10.1-5.fc24.src/PEAR-1.10.1/PEAR-1.10.1/PEAR/Command/Channels.php:PEAR configuration (~/.pearrc on Unix-like systems). After logging php-pear-1.10.1-5.fc24.src/PEAR-1.10.1/PEAR-1.10.1/PEAR/Command/Channels.xml:PEAR configuration (~/.pearrc on Unix-like systems). After logging php-pear-1.10.1-5.fc24.src/PEAR-1.10.1/PEAR-1.10.1/PEAR/Command/Auth.php:PEAR configuration (~/.pearrc on Unix-like systems). After logging php-pear-1.10.1-5.fc24.src/PEAR-1.10.1/PEAR-1.10.1/PEAR/Command/Auth.xml:PEAR configuration (~/.pearrc on Unix-like systems). After logging php-pear-1.10.1-5.fc24.src/PEAR-1.10.1/PEAR-1.10.1/PEAR/Registry.php: $file = OS_WINDOWS ? 'pear.ini' : '.pearrc'; php-pear-1.10.1-5.fc24.src/PEAR-1.10.1/PEAR-1.10.1/PEAR/Config.php: $user_file = getenv('HOME') . $sl . '.pearrc'; php-pear-1.10.1-5.fc24.src/PEAR-1.10.1/PEAR-1.10.1/PEAR/Config.php: 'user' => getenv('HOME') . $sl . '.pearrc', I didn't find any mention of .pearrc in any of the other pear-php, owncloud, or php-owncloud-tarstreamer packages. Do you have any idea where these files might be coming from? Can I safely remove them?