Bug 2182004

Summary: reposync produces wrong metadata when using both -n and --download-metadata options
Product: Red Hat Enterprise Linux 9 Reporter: Jaroslav Mracek <jmracek>
Component: dnf-plugins-coreAssignee: Jaroslav Mracek <jmracek>
Status: CLOSED ERRATA QA Contact: swm-qe
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 9.3CC: james.antill, mbanas, nsella
Target Milestone: rcKeywords: Triaged
Target Release: ---Flags: pm-rhel: mirror+
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: dnf-plugins-core-4.3.0-6.el9 Doc Type: No Doc Update
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2023-11-07 08:54:31 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Jaroslav Mracek 2023-03-27 08:30:53 UTC
This bug was initially created as a copy of Bug #2132383

I am copying this bug because: 



Description of problem:
When running reposync with both options -n and --download-metadata, it downloads only newest package versions but full metadata that contain all remote package versions. This is very confusing.

Version-Release number of selected component (if applicable):
yum-utils-1.1.31-54.el7_8.noarch


How reproducible:
always

Steps to Reproduce:
1. reposync -n --download-metadata ...
2. dnf list --show-duplicates
3.

Actual results:
dnf produces a list of packages we never download

Expected results:
dnf only produces a list of packages we really downloaded

Additional info:
I'd expect reposync either complain about using both options at the same time or fix the downloaded metadata so that it only contains the newest packages

Comment 1 Jaroslav Mracek 2023-03-27 08:32:41 UTC
I created a PR with update of documentation - https://github.com/rpm-software-management/dnf-plugins-core/pull/483

Comment 9 errata-xmlrpc 2023-11-07 08:54:31 UTC
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory (dnf-plugins-core bug fix and enhancement update), and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHBA-2023:6641