[Pulp-list] incorrect RPM paths in sync attempts

Alan Milligan alan.milligan at last-bastion.net
Mon Apr 27 03:57:37 UTC 2015


Hi,

Trying to set up a sync feed against my yum channels, I'm getting
incorrect RPM paths according to my yum server logs.  For example, with
a repo feed https://linux.last-bastion.net/LBN/up2data/cloud/19, package
attempts are made for (eg)
https://linux.last-bastion.net/LBN/up2date/cloud/rubygem-boxgrinder-bastion-1.0.10-1.lbn19.noarch.rpm
(it's dropped the '19' directory from the url path) - and thus the
package not found....

I'm wondering if there's not something nasty going on - there is logic
to munge the location in the xml (but that only looks like for the
localised distributor, not the importer).

I use xml:base within my location directives in primary.xml:

<location xml:base="https://linux.last-bastion.net/LBN/up2date/cloud/19"
href="rubygem-boxgrinder-bastion-1.0.10-1.lbn19.noarch.rpm"/>

This is of course valid schema repodata, and all of the same yum
libraries handle all of this validly on the same pulp server.  Note that
this is a pure xml-based yum repo (no sqlite).  This is on pulp 2.6.0.

Anyone have any ideas?

Alan




More information about the Pulp-list mailing list