Project

Profile

Help

Issue #9055

package group pulls in newer version of package

Added by quartsize 3 months ago. Updated 2 months ago.

Status:
CLOSED - CURRENTRELEASE
Priority:
Normal
Assignee:
-
Sprint/Milestone:
Start date:
Due date:
Estimated time:
Severity:
1. Low
Version:
Platform Release:
OS:
Triaged:
No
Groomed:
No
Sprint Candidate:
No
Tags:
Sprint:
Quarter:

Description

I have a package exclusion filter in Katello to reject newer kernels for which I don't yet have compatible versions of out-of-tree modules, but I end up with the latest versions of the perf and kernel-tools packages because they are listed in the @performance and @core package groups, respectively.

So I'd like to propose that package groups only cause a package to be added if some version of the package wasn't already requested. I'm working on a patch.

I will also say, FWIW, that I wasn't expecting these sort of additions to be processed without depsolving enabled, such that my initial line of investigation started with the assumption that I must be accidentally enabling it somehow.


Related issues

Copied to RPM Support - Backport #9076: Backport 9055 "package group copy pulls in newer version of package" to 3.13.zCLOSED - WONTFIX

<a title="Actions" class="icon-only icon-actions js-contextmenu" href="#">Actions</a>

Associated revisions

Revision 6eaba3a7 View on GitHub
Added by quartsize 2 months ago

Only add package from package group if not already selected

closes: #9055 https://pulp.plan.io/issues/9055

History

#1 Updated by pulpbot 3 months ago

  • Status changed from NEW to POST

#2 Updated by dalley 3 months ago

Thanks for the report, and especially for the patch!

I will also say, FWIW, that I wasn't expecting these sort of additions to be processed without depsolving enabled, such that my initial line of investigation started with the assumption that I must be accidentally enabling it somehow.

Sorry about the confusion, perhaps we can improve the documentation in this area. Dependency solving is quite tricky because the performance cost of solving a "full" solution is quite high, and yet it's very important to have some basic functionality there. So where we draw the line is ensuring that the most basic and critical dependencies are always copied. For example copying an Errata / Advisory would be worse-than-useless if the RPMs it explicitly references as required updates are not copied along with it.

Your particular use issue does make sense and I think the patch is reasonable at first glance. Will review shortly.

#3 Updated by quartsize 2 months ago

  • Status changed from POST to MODIFIED

#4 Updated by dalley 2 months ago

  • Sprint/Milestone set to 260

#5 Updated by dalley 2 months ago

  • Copied to Backport #9076: Backport 9055 "package group copy pulls in newer version of package" to 3.13.z added

#6 Updated by dalley 2 months ago

  • Sprint/Milestone changed from 260 to 3.14.0

#7 Updated by pulpbot 2 months ago

  • Status changed from MODIFIED to CLOSED - CURRENTRELEASE

Please register to edit this issue

Also available in: Atom PDF