Issue #9055: package group pulls in newer version of package - RPM Support - Pulp

Actions

Send by e-mail Copy link

Issue #9055

closed

package group pulls in newer version of package

Added by quartsize almost 3 years ago. Updated over 2 years ago.

Status:

CLOSED - CURRENTRELEASE

Priority:

Normal

Assignee:

Sprint/Milestone:

3.14.0

Start date:

Due date:

Estimated time:

Severity:

1. Low

Version:

Platform Release:

OS:

Triaged:

Groomed:

Sprint Candidate:

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

Actions

Copy link

Updated by pulpbot almost 3 years ago

Status changed from NEW to POST

PR: https://github.com/pulp/pulp_rpm/pull/2038

Actions

Copy link

Updated by dalley almost 3 years 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.