Red Hat Bugzilla – Full Text Bug Listing
|Summary:||cpanm bundle lots of library and is not listed on fesco page|
|Product:||[Fedora] Fedora||Reporter:||Michael Scherer <misc>|
|Component:||perl-App-cpanminus||Assignee:||Petr Pisar <ppisar>|
|Status:||CLOSED RAWHIDE||QA Contact:||Fedora Extras Quality Assurance <extras-qa>|
|Version:||18||CC:||fweimer, mmaslano, perl-devel, ppisar|
|Fixed In Version:||perl-App-cpanminus-1.6927-3.fc21||Doc Type:||Bug Fix|
|Doc Text:||Story Points:||---|
|Last Closed:||2013-09-11 04:35:23 EDT||Type:||Bug|
|oVirt Team:||---||RHEL 7.3 requirements from Atomic Host:|
|Bug Depends On:||929254|
|Bug Blocks:||504493, 952282|
Description Michael Scherer 2013-02-04 08:27:29 EST
According to the comment in the spec, and the source of cpanm, there is lots of perl modules bundle into the main software. While the way cpanm work kinda mandate it, I think there should be some tracking for it, only for security update reasons. I would suggest to contact fesco and see what to do ( ie, either unbundle, or get a bundle exception, and list the module on the appropriate page, with appropriate provides bundled(foo) tags )
Comment 1 Marcela Mašláňová 2013-02-04 10:14:52 EST
Did you look in to the tarball? It is not bundled like copied the module, but the "function" is copied into the main code. cpanm does it to have a minimal dependency chain, which is a must for this kind of a tool. Also the bundling exception is given by FPC not FESCo. If you still believe it should be acked by FPC, then please feel free to reopen.
Comment 2 Michael Scherer 2013-02-04 11:28:22 EST
Yes, I have read the source code, and I am aware of the reason on why cpanm do it ( hence the "While the way cpanm work kinda mandate it" part in my first comment ). But as I said, I think this should be tracked somewhere. I have seen how the code is bundled and I know this would be quite hard to unbundle, but I am not FPC, so in the end, it is up to them to decide, not to me, hence the request to see with them. If I was the one to decide, I would grant a exception, provided we can find what is bundled, so if any security issue arise, we can quickly see this should be fixed in cpanm too. For example there is a bundle of JSON::PP or HTTP::Tiny, and I picking these 2 because they are either consuming untrusted input or network stuff, so could in theory be problematic. And in all case, the packaging guidelines are quite clear on what to do if there if there is a bundle : https://fedoraproject.org/wiki/Packaging:No_Bundled_Libraries#Requirement_if_you_bundle This include adding a link to the ticket for the exception. And while the ticket look like bureaucracy ( since I think the exception would be granted ), I think only FPC can edit the wiki page with bundled exceptions list, and that would be used as a reference source, and so must be up to date. The fact that only part of the code is copied doesn't make it less a problematic copy from a tracking point of view. So yes, i think something should be done, and the current process and documentation requires some group to do it, and that's FPC as you correctly said.
Comment 3 Marcela Mašláňová 2013-02-05 03:46:57 EST
Filed as: https://fedorahosted.org/fpc/ticket/250 I wonder if the wiki is checked by security team for possible CVEs.
Comment 4 Petr Pisar 2013-04-15 11:22:15 EDT
*** Bug 952281 has been marked as a duplicate of this bug. ***
Comment 5 Florian Weimer 2013-04-15 11:34:00 EDT
As of upstream version 1.6108, the situation is even worse because the bundled sources are now obfuscated.
Comment 6 Petr Pisar 2013-08-02 11:20:07 EDT
I have unbundled version 1.6927, but it requires these unpackaged modules: perl(Module::CPANfile) perl(version::vpp) I guess core-only version::vpp is useless. Standard perl(version) should be enough.
Comment 7 Marcela Mašláňová 2013-08-05 04:57:18 EDT
I agree, standard perl(version) should be enough, when I was looking on this package.
Comment 8 Fedora Admin XMLRPC Client 2013-08-12 09:14:49 EDT
This package has changed ownership in the Fedora Package Database. Reassigning to the new owner of this component.