Description of Problem: Because this package contains unowned directories, they will be created with the current umask. When having restrictive administrator settings (umask 077) ordinary user will not have access to them and can not use them. Another problem occurs when removing packages. Then orphaned directories are remaining. | $ rpm -qf /usr/lib/perl5/vendor_perl/5.8.0/i386-linux-thread-multi/Crypt/SSLeay /usr/lib/perl5/vendor_perl/5.8.0/i386-linux-thread-multi/Crypt/SSLeay/CTX.pm | file /usr/lib/perl5/vendor_perl/5.8.0/i386-linux-thread-multi/Crypt/SSLeay is not owned by any package | perl-Crypt-SSLeay-0.45-2 Version-Release number of selected component (if applicable): perl-Crypt-SSLeay-0.45-2 How Reproducible: 100% Steps to Reproduce: 1. umask 077 2. make sure that perl-Crypt-SSLeay is uninstalled completely (rm -rf /usr/lib/perl5/vendor_perl/5.8.0/i386-linux-thread-multi/Crypt/SSLeay) 3. rpm -U perl-Crypt-SSLeay-0.45-2.* 4. ls -l /usr/lib/perl5/vendor_perl/5.8.0/i386-linux-thread-multi/Crypt/SSLeay 5. start perl script using this module 6. rpm -e perl-Crypt-SSLeay-0.45-2 Actual Results: | drwx------ 2 root root 4096 Sep 13 15:11 /usr/lib/perl5/vendor_perl/5.8.0/i386-linux-thread-multi/Crypt/SSLeay at 4; script can not find package at 5 and /usr/lib/perl5/vendor_perl/5.8.0/i386-linux-thread-multi/Crypt/SSLeay still exists after 6.
This package has not been cleaned up since then, so likely still needs fixing.
Created attachment 119219 [details] Suggested fix + other improvements
thanks built