Project

Profile

Help

Story #4767

As a user, I can copy non-modular Erratum with referenced RPMs and their dependencies

Added by ttereshc over 2 years ago. Updated almost 2 years ago.

Status:
CLOSED - DUPLICATE
Priority:
Normal
Assignee:
-
Sprint/Milestone:
-
Start date:
Due date:
% Done:

0%

Estimated time:
Platform Release:
Groomed:
Yes
Sprint Candidate:
No
Tags:
Sprint:
Quarter:

Description

An Erratum itself is metadata and it's not very useful without content it refers too.
The content is listed in the pkglist of an Erratum.

Terminology:
- there is no such thing as Erratum dependencies.
- RPMs listed in an Erratum represent content of an Erratum.
- RPM dependencies = RPM-to-RPM dependencies aka when one RPM depend on the other RPM.
- depsolving strategy (conservative and non-conservative in pulp2) is relevant to RPM dependencies only.

The common use case is to copy an Erratum and all the content it refers to with its dependencies, so it is possible to apply an Erratum and update all the content it suggests to update.

Use cases to support:
- copy Erratum itself without anything (already implemented, it should continue to work)
- copy Erratum with its referenced RPMs and with RPM dependencies using the dependency solving strategy specified by user

Some examples can be found here

History

#1 Updated by ttereshc over 2 years ago

  • Description updated (diff)

#2 Updated by dalley over 2 years ago

  • Groomed changed from No to Yes

#3 Updated by dalley almost 2 years ago

  • Parent task changed from #4762 to #6017

#4 Updated by dalley almost 2 years ago

  • Status changed from NEW to CLOSED - DUPLICATE

For tracking purposes, https://pulp.plan.io/issues/4768 is a superset of this issue

#5 Updated by dalley almost 2 years ago

  • Parent task deleted (#6017)

Please register to edit this issue

Also available in: Atom PDF