Project

Profile

Help

Issue #8114

Wrong deps are copied to the repo when using "recursive" option to copy rpms

Added by dalley 11 months ago. Updated 10 months ago.

Status:
CLOSED - CURRENTRELEASE
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:
Sprint:
Quarter:

Description

Clone of #8110 for Pulp 3


Related issues

Related to RPM Support - Backport #8123: Backport Request: 8114 (Wrong deps are copied to the repo when using "recursive" option to copy rpms) to 3.7CLOSED - WONTFIX

<a title="Actions" class="icon-only icon-actions js-contextmenu" href="#">Actions</a>
Copied from RPM Support - Issue #8110: Wrong deps are copied to the repo when using "recursive" option to copy rpmsCLOSED - CURRENTRELEASE<a title="Actions" class="icon-only icon-actions js-contextmenu" href="#">Actions</a>

Associated revisions

Revision 5f8d84f5 View on GitHub
Added by dalley 11 months ago

Fix a mistake when producing RPM dependencies.

Mistake copied from Pulp 2.

[nocoverage]

re: #8114 https://pulp.plan.io/issues/8114

History

#1 Updated by dalley 11 months ago

  • Copied from Issue #8110: Wrong deps are copied to the repo when using "recursive" option to copy rpms added

#2 Updated by dalley 11 months ago

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

Accidentally used "re:" in the tag instead of "closes:"

https://github.com/pulp/pulp_rpm/pull/1919

#3 Updated by iballou 11 months ago

  • Related to Backport #8123: Backport Request: 8114 (Wrong deps are copied to the repo when using "recursive" option to copy rpms) to 3.7 added

#4 Updated by dalley 10 months ago

  • Sprint/Milestone set to 3.9.0

#5 Updated by pulpbot 10 months ago

  • Status changed from MODIFIED to CLOSED - CURRENTRELEASE

Please register to edit this issue

Also available in: Atom PDF