Project

Profile

Help

Issue #3902

Recursive module copy doesn't follow intended modular behaviour

Added by milan about 3 years ago. Updated over 2 years ago.

Status:
CLOSED - NOTABUG
Priority:
Normal
Assignee:
-
Sprint/Milestone:
-
Start date:
Due date:
Estimated time:
Severity:
2. Medium
Version:
Platform Release:
OS:
Triaged:
No
Groomed:
No
Sprint Candidate:
No
Tags:
Pulp 2
Sprint:
Quarter:

Description

Recursive copy of module artifacts should prefer the modular dependencies implied while at the same time, Pulp should keep the conservative dependency solving ; these requirements contradict each other.

Say module Frog has a frog-1.rpm and fly-1.rpm artifacts and that frog-1.rpm has the Requires: fly dependency.
If a source repository contains frog-1.rpm, fly-1.rpm and the destination repository contains fly-2.rpm, the fly-1.rpm won't be recursively copied because of an already satisfied dependency fly-2.rpm being present in the target repository.
This breaks the expected modular behavior.

Notes

This actually seems to work OK because Pulp always copies first-level module dependencies and unless the module is broken by not shipping/listing custom artifact versions necessary for the module to (buind and) run, this might be just enough:

History

#1 Updated by milan about 3 years ago

  • Status changed from NEW to CLOSED - NOTABUG

Update after triage.

#2 Updated by bmbouter over 2 years ago

  • Tags Pulp 2 added

Please register to edit this issue

Also available in: Atom PDF