[Pulp-list] question wrt copying errata from 1 repo to another
mhrivnak at redhat.com
Tue Feb 10 13:19:54 UTC 2015
Copying just an errata will add it to the updateinfo.xml file in the destination repo. --recursive will additionally copy the rpms it references and any dependencies they have.
----- Original Message -----
From: "Jo De Troy" <jo.de.troy at gmail.com>
To: pulp-list at redhat.com
Sent: Tuesday, February 10, 2015 3:57:58 AM
Subject: Re: [Pulp-list] question wrt copying errata from 1 repo to another
thanks for the quick reply. It works fine with the --recursive flag.
What I don't understand is what the copy of errata does without the recursive flag, it seems like without the recursive flag the repo is unusable.
Or is this specific for the copy of errata only.
On 9 February 2015 at 17:22, Jo De Troy < jo.de.troy at gmail.com > wrote:
I'm pretty new to Pulp and I tried following 1 of the recipes in the documentation.
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 \
When publishing the repo I see there are 614 errata published. But when running yum check-update on a client I get nothing back.
Should I see symlinks or anything else in the published repo folder? Or is it normal there is only a repodata folder in there? Any hint on where I need to start looking to find out what is wrong?
Pulp-list mailing list
Pulp-list at redhat.com
More information about the Pulp-list