Project

Profile

Help

Issue #3853

closed

Recursive copy doesn't take conflicts into account

Added by milan almost 6 years ago. Updated about 5 years ago.

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

Description

Recursive copy doesn't take conflicts into account. This leads into broken repositories when only few units a time are being copied.
Imagine following hypothetical recursive copy scenario:

  • foo requires webserver and conflicts with libnginx
  • nginx provides webserver and libnginx
  • httpd provides webserver while it doesn't provide libnginx
  • the source repository contains both httpd and nginx rpms
  • pulp not processing the conflicts attribute, a user copying foo to the empty repository might end up with nginx being pulled in
  • dnf panics trying to install foo from the target repository

This might not have been reported sooner as the usual use case seems to be many units are being copied at a time.
Or perhaps nothing ever conflicts with libnginx ;)


Related issues

Related to Pulp - Task #3175: Update plugin docs after REST API changes are mergedCLOSED - CURRENTRELEASEbizhang

Actions

Also available in: Atom PDF