Project

Profile

Help

Story #4768

Story #4762: [Epic] As a user, I can copy content

Story #6017: [Epic] As a user, when copying content, dependencies of that content are also copied

As a user, I can copy Erratum with their referenced Modules and RPMs, and their dependencies

Added by ttereshc over 1 year ago. Updated 7 months ago.

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

100%

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.
Modules and RPMs are listed in the pkglist of an Erratum.

Terminology:
- there is no such thing as Erratum dependencies.
- Modules/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.
- Module dependencies = Module-to-Module dependencies aka when one Module depend on the other Module. (Module doesn't depend on any RPMs, Module contains RPMs(artifacts) which are always copied with it.)
- 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 Modules and RPMs
* Modules dependencies
* RPM dependencies using the dependency solving strategy specified by user

Some examples can be found here

Associated revisions

Revision 9078fab4 View on GitHub
Added by dalley 9 months ago

Add dependency solving for modulemd and modulemd_defaults

  • Copy modules that are dependencies of other modules
  • Copy modules when their artifacts are copied
  • Copy the modulemd_default if it exists when a module it references is copied

re: #4768 https://pulp.plan.io/issues/4768 closes: #4162 https://pulp.plan.io/issues/4162

Revision 64f85f59 View on GitHub
Added by dalley 9 months ago

Add support for incremental update (errata copy w/ referenced rpms)

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

History

#1 Updated by ttereshc over 1 year ago

  • Description updated (diff)

#2 Updated by ttereshc over 1 year ago

  • Description updated (diff)

#3 Updated by ttereshc over 1 year ago

  • Description updated (diff)

#4 Updated by dalley over 1 year ago

  • Groomed changed from No to Yes

#5 Updated by dalley 11 months ago

  • Parent task changed from #4762 to #6017

#6 Updated by dalley 9 months ago

  • Status changed from NEW to ASSIGNED
  • Assignee set to dalley

#7 Updated by dalley 9 months ago

  • Subject changed from As a user, I can copy modular Erratum with referenced Modules/RPMs and their dependencies to As a user, I can copy Erratum with referenced RPMs (including modular RPMs) and their dependencies

Merging two stories into one

#8 Updated by dalley 9 months ago

@Tanya, re: the wording of this issue -- do "modular errata" actually reference modules directly? I thought they just reference modular RPMs?

Edit: They do reference modules directly, but the modules in our fixtures don't do this.

#9 Updated by dalley 9 months ago

  • Subject changed from As a user, I can copy Erratum with referenced RPMs (including modular RPMs) and their dependencies to As a user, I can copy Erratum with their referenced Modules and RPMs, and their dependencies

#10 Updated by dalley 9 months ago

  • Status changed from ASSIGNED to MODIFIED
  • % Done changed from 0 to 100

#11 Updated by dalley 7 months ago

  • Sprint/Milestone set to Pulp RPM 3.3.0

#12 Updated by dalley 7 months ago

  • Status changed from MODIFIED to CLOSED - CURRENTRELEASE

Please register to edit this issue

Also available in: Atom PDF