RPMs version is truncated in container image scan

[pombredanne]

Originally posted by @pombredanne in aboutcode-org/scancode.io#1377

I've submitted a fix for this issue in PR #2030. The fix combines the RPM version and release fields to show the complete version string.

This is a scancode-toolkit issue at the root: this change if needed should take place upstream and not in this repo at all, most likely in https://github.com/aboutcode-org/scancode-toolkit/tree/develop/src/packagedcode rpm or rpm_installed or both.

[Jayant-kernel]

I am picking this up as discussed in scancode.io#1377. I'll submit a PR with the fix and tests shortly.
thank you.

[manvendra5345]

Hello! I’m interested in contributing to this project as part of GSoC.
Could you please assign this issue to me? I’d love to work on it and get started.
Thanks!

[VaaishnaviS]

Hi @pombredanne,
I have raised a PR please look into it.
PR #4685

What this PR does:

• Keeps existing rpm.package behavior (name-version) to avoid breaking current tests
• Adds a new full_version property that exposes version-release
• Fixes RPM filename construction to avoid duplicate release values
• Adds a regression test in test_pyrpm.py

This ensures RPM versions are no longer truncated in container image scans while remaining backward compatible.

If you’d like any changes, refinements, or additional tests, please let me know — I’m happy to update the PR accordingly.

Thanks :)

[ionfwsrijan]

Hi there,

I’m Srijan Jaiswal, and I’m eager to contribute to this project as part of my open-source contribution. I have reviewed this issue and feel confident that I can provide a solution since I have experience working with similar technologies in my past projects. Could you please assign this issue to me? I’d love to work on it and contribute to the project.

Best regards,
Srijan Jaiswal