Has anyone else noticed that reposync is now, for some channels, downloading RPMs to an additional subdirectory structure -- and that createrepo is not handling it?
For example, systemd-219-62.el7_6.5.x86_64.rpm showed up in /s/systemd-219-62.el7_6.5.x86_64.rpm instead of the parent directory. That'd be fine if createrepo found the subdirectories, but it doesn't.
It appears to me that Red Hat changed the structure of some of the channels but haven't updated the related tools to handle it. How are others handling this locally?
Hi Jeff,
Please check out this knowledgebase solution article :
When using reposync to update a local repo, why is it downloading all of the packages again?
As of March 4th, the repositories no longer place all of the rpms directly into the Packages directory. Each rpm will now be in a sub directory of Packages based on the first character of the package.
You may also want to read this discussion from the Customer Portal Community :
Red Hat Workstation Repo RPM Folder Change?
Regards,
Christian
Hi Jeff,
Please check out this knowledgebase solution article :
When using reposync to update a local repo, why is it downloading all of the packages again?
As of March 4th, the repositories no longer place all of the rpms directly into the Packages directory. Each rpm will now be in a sub directory of Packages based on the first character of the package.
You may also want to read this discussion from the Customer Portal Community :
Red Hat Workstation Repo RPM Folder Change?
Regards,
Christian
Red Hat
Learning Community
A collaborative learning environment, enabling open source skill development.