Skip to main content
commvault.com commvault.com
Question

RPM Group field for native packages

  • March 18, 2026
  • 2 replies
  • 19 views
downhill
Explorer
Forum|alt.badge.img+11

Hi guys, we ran into an issue deploying an RPM created from the 11.40.42 base which I’m wondering if anyone else has. If you run “rpm -qip ournewcvlt.rpm” it returns the following:

Name        : ournewcvlt.11.40.42.Instance001
Version     : 11.4000.1372.42
Release     : 1.el8
Architecture: x86_64
Install Date: (not installed)
Group       : Applications/Archiving

The last field there “Group” is not a Unix Group in the traditional sense but appears to conflict with other aspects of our repos environment. The question is - there doesn’t seem to be any control over this and we wonder if it is possible to modify this.

I found howto: repack RPM for nicer name or add extra files | Community but that doesn’t exactly speak to it. Does anyone know if we snag the blah.src.rpm file before it gets cleaned up if we can modify the Group. 

Essentially it affects dependencies for a couple other packages.

thanks

2 replies

J
Vaulter
Forum|alt.badge.img+9
  • Jace RossVaulter
  • Vaulter
  • March 19, 2026

Hi downhill,

The group field in RPM spec is a requirement of rpm creation for older Linux releases. It looks as though it’s deprecated and considered optional in most distros I’ve been able to check. It also looks like we no longer support distributions that old (RHEL 5.0 and earlier) so there’s no reason I know of that it should be in the spec.

I would suggest raising an incident with support so this can be raised with development, unless there’s a specific reason, the group spec shouldn’t be used on Commvault native packages.

Cheers,

Jace Ross, Senior Technical SME
downhill
Explorer
Forum|alt.badge.img+11
  • downhillExplorer
  • Author
  • Explorer
  • March 20, 2026

Thanks Jace, I did open a ticket on this and will follow up here later depending on outcome.

    Terms & ConditionsAccessibility statement