Bug 162303
Summary: | Installation of perl module Archive::Zip fails - Read only directory being written too | ||
---|---|---|---|
Product: | [Fedora] Fedora | Reporter: | Adam <adam> |
Component: | perl-Archive-Zip | Assignee: | Warren Togami <wtogami> |
Status: | CLOSED NOTABUG | QA Contact: | |
Severity: | medium | Docs Contact: | |
Priority: | medium | ||
Version: | 4 | CC: | perl-devel |
Target Milestone: | --- | Keywords: | Security |
Target Release: | --- | ||
Hardware: | i686 | ||
OS: | Linux | ||
URL: | http://www.perlmonks.com/?node_id=471824 | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2005-07-02 08:27:39 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
Adam
2005-07-02 03:44:41 UTC
Fedora is not responsible for CPAN installations, which you use at your own risk, so I have to mark this NOTABUG. If you want Archive::Zip conveniently in FC4, you could just run 'yum install perl-Archive-Zip'. The package is a standard component in Core. I suspect that the issue here is down to running "make test" as root anyway. root can write to directories that don't have the write enable bit set. Try building and testing the module as a regular user. Adam, The correct way to report problems in CPAN perl modules is to use the CPAN bug reporting system which is located at the following address: http://rt.cpan.org/ This particular problem has already been reported upstream. Please see: Bug #13426 make test fail in Archive::Zip 1.15 http://rt.cpan.org/NoAuth/Bug.html?id=13426 Additional info * CPAN: Archive::Zip module page http://search.cpan.org/dist/Archive-Zip/ * Archive::Zip opened bugs http://rt.cpan.org/NoAuth/Bugs.html?Dist=Archive-Zip The opened bugs page can also be reached from the CPAN module page. Just follow the "View/Report Bugs" link: Links: [...] [...] [View/Report bugs] [...] Regards, jpo [1] Unless stated otherwise by the module author/maintainer (the README file is a good place to start looking for this information) |