Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Created attachment 935169[details]
reposync script
Description of problem:
When mirroring a RHEL 7 repository using reposync, and requesting that the comps.xml and metadata also be downloaded, the directory structure that is created is in error.
When using reposync in RHEL 6.5, the following structure is created in the reposync process:
Base directory
--- rhel-7-supplementary-rpms
------ Packages
where the comp/metadata is loaded in the 'rhel-7-supplementary-rpms' directory and all the rpm packages are loaded in the 'Packages' directory. This is consistent with what you normally get if you use yum to download packages and use the option keepcache=1 to retain the downloaded packages.
Note: rhel-7-supplementary-rpms is used as a typical example. This occurs for any repository that is downloaded.
When using reposync in RHEL 7.0, the following structure is created.
Base directory
--- rhel-7-supplementary-rpms
Both the package and metadata are loaded in the same 'rhel-7-supplementary-rpms' directory. They are not segregated out separately. This requires you to manually search for and extract the metadata if you need to use it. A tedious process for large repositories.
Version-Release number of selected component (if applicable):
RHEL 7.0
How reproducible:
Always.
Steps to Reproduce: (see attached test script)
1. Run reposync
2. Use reposync options --downloadcomps and --download-metadata
3.
Actual results: Output directory structure
Base directory
--- rhel-7-xxxxxx-rpms
Expected results: Output directory structure
Base directory
--- rhel-7-xxxxxx-rpms
------ Packages
Additional info:
The correct results can be obtained by downloading the latest yum-utils package from the RHEL 6.5 repo, extracting the reposync executable, and using it instead of the RHEL 7.0 /usr/bin/reposync package. This is the workaround I am currently using.
Comment 3Valentina Mukhamedzhanova
2014-09-10 07:47:26 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, 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://rhn.redhat.com/errata/RHBA-2015-0401.html
Created attachment 935169 [details] reposync script Description of problem: When mirroring a RHEL 7 repository using reposync, and requesting that the comps.xml and metadata also be downloaded, the directory structure that is created is in error. When using reposync in RHEL 6.5, the following structure is created in the reposync process: Base directory --- rhel-7-supplementary-rpms ------ Packages where the comp/metadata is loaded in the 'rhel-7-supplementary-rpms' directory and all the rpm packages are loaded in the 'Packages' directory. This is consistent with what you normally get if you use yum to download packages and use the option keepcache=1 to retain the downloaded packages. Note: rhel-7-supplementary-rpms is used as a typical example. This occurs for any repository that is downloaded. When using reposync in RHEL 7.0, the following structure is created. Base directory --- rhel-7-supplementary-rpms Both the package and metadata are loaded in the same 'rhel-7-supplementary-rpms' directory. They are not segregated out separately. This requires you to manually search for and extract the metadata if you need to use it. A tedious process for large repositories. Version-Release number of selected component (if applicable): RHEL 7.0 How reproducible: Always. Steps to Reproduce: (see attached test script) 1. Run reposync 2. Use reposync options --downloadcomps and --download-metadata 3. Actual results: Output directory structure Base directory --- rhel-7-xxxxxx-rpms Expected results: Output directory structure Base directory --- rhel-7-xxxxxx-rpms ------ Packages Additional info: