| Summary: | no rpm owns some files/dirs + leftovers after uninstall | ||
|---|---|---|---|
| Product: | Red Hat Software Collections | Reporter: | Ondřej Pták <optak> |
| Component: | httpd | Assignee: | Jan Kaluža <jkaluza> |
| Status: | CLOSED ERRATA | QA Contact: | Ondřej Pták <optak> |
| Severity: | unspecified | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | httpd24 | CC: | jkaluza, jorton, kanderso, optak |
| Target Milestone: | beta | ||
| Target Release: | 2.2 | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | httpd24-1.1-12.el7 | Doc Type: | Bug Fix |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2016-05-31 10:17: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: | |
|
Description
Ondřej Pták
2016-03-22 01:18:12 UTC
Most of these are coming from libcurl/libnghttp2; can you whitelist them? Nothing very serious. I'm not sure how this: /opt/rh/httpd24/root/usr/lib64/httpd/modules/libphp5.so ... gets left behind, checking with Remi. We are not sure out what created that libphp5.so in that particular location. Is it a symlink? No package /opt/rh/httpd24/root/usr/lib64/httpd/modules/libphp5.so available. None of php54-php, php55-php, rh-php56-php create that file. /opt/rh/httpd24/root/usr/lib64/httpd/modules/libphp5.so is caused by another test. For the rest, I can add that to the whitelist, but I'm not sure it's the right think to do. I would prefer to solve this by letting libcurl/libnghttp2 to own that files/dirs (not necessary this release). Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHBA-2016:1154 |