[Pulp-list] question wrt copying errata from 1 repo to another
claer at claer.hammock.fr
Tue Feb 10 11:04:15 UTC 2015
On Mon, Feb 09 2015 at 56:16, Randy Barlow wrote:
> On 02/09/2015 11:22 AM, Jo De Troy wrote:
> > I have 1 repo which downloads from RHN and I created a second repo to
> > create a set of 'approved' updates.
> > The creation of the repo's works fine and copying only the security
> > errata also seems to work.
> > But when I publish the 'errata' repo as http and adding this repo to the
> > yum config of a client the clients doesn't see any content in that repo.
> > When browsing to the repo I only see a repodata folder with basically an
> > empty filelist.xml.gz file
> > Can anybody help me in finding out what I'm doing wrong?
> > I'm running Pulp 2.5.3 on RHEL 6.6
> > I copyied the errata with the command below
> > pulp-admin --username=xxx --password=xxx rpm repo copy errata --match
> > type=security \
> > --from-repo-id=rhel6-x86_64-os --to-repo-id=rhel-6-x86_64-updates
> There is a --recursive flag for the errata copy that will copy the files
> that the errata reference. I believe it will do what you expect if you
> add that flag. Hope that helps!
Last time I checked, (2.4 release if I remember well ;)) The recursive flag
matches the rpm on the source and not on the destination. Is it now possible to
match the dependencies based on the objects available on the destination
More information about the Pulp-list