-
-
Notifications
You must be signed in to change notification settings - Fork 15
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
perl core only releases of dual life modules do not show up in CPANSA::DB #190
Comments
Okay, I see this issue, and I suspect that it's going to take some major surgery to fix this. For IPC::Cmd, the version I'll have to think about this. Module::Corelist can probably help. This would be in the util/generate script. Despite what should happen, we still have to respond to it. Some other things to complain about:
|
I've been looking at this and the data structure that everything expects has no way to handle this. But, this is a symptom of a larger problem. A module can show up in different distributions through its life, so mapping a package name to a dist isn't that simple. You have to map a (package,version) pair to a dist. And, for dual-lived modules, that (package,version) pair can map to multiple distributions. I think the first thing that needs to change is For dual-lived modules, something needs to recognize the namespace is in one distribution by its reports are cataloged in another. But maybe we can cheat by looking through corelist that injecting versions we find there into the version list in their CPAN packages. Go through the list of versions for a dist, see if every version in corelist is there, and add ones that aren't. That doesn't solve the bigger problem though. |
I'm able to add some corelist versions to the version list for a dist in the CPANSA::DB. However, this is imperfect. For example, The next thing is making these new entries useable. I think it works for this issue, using the unreleased versions I have locally (from 846691d). I'm not confident this is solid yet so I'm going to play with it a bit more.
|
Production releases of the perl interpreter at times are shipped with distributions with a version number containing an underscore.
Without any knowledge of the generation process of the CPANSA database it seems, that vulnerable distributions with version numbers interpreted as indicating a development release are not considered for inclusion. This assumption sometimes fails for "core first"-distributions (at least that is how I understand the perl interpreter release process).
Let's take the cored IPC::Cmd module as an example in order to demonstrate the case:
This is a byproduct of the belated reviewing of your version of pull request briandfoy/cpan-audit#62 requested by you. Expect some patches and comments there in the following weeks.
The text was updated successfully, but these errors were encountered: