RPM Support

Is this ticket related to:

(1) hosting a zypper repository with pulp;

or

(2) building the pulp installation packages for the SLES environment?

I have an immediate need for the latter, though would certainly appreciate the former as well.
Currently working on a proof-of-concept for using pulp to host our puppet modules in-house.

I'd be willing to help test rpm's for deploying pulp to SLES using zypper.
If that is not what this ticket is about, please advise me so I can submit a ticket requesting such support.

Thanks,
-- Hugh

On 06/05/2015 05:53 PM, Pulp wrote:

(1) hosting a zypper repository with pulp;

or

(2) building the pulp installation packages for the SLES environment?

I believe this ticket is about the former.

--
Randy Barlow

SLES 11 import works as well as in openSUSE, with the minor note that you need to remember to include your mirroring credentials in the feed URL for the RPM repo (e.g. https://username:password@susecdn/). Republishing the repo via pulp and consuming it in a SLES 11 system works perfectly.

SLES 12 syncing doesn't work because SLES 12 introduced a new authorization mechanism (GET query param), and the pulp_rpm yum importer mangles that query param by unconditionally adding a trailing slash to the entire URL. That is filed as #1348, which blocks this.

For SLES 12, I wrote a quick patch to address #1348, and while it tested just fine in pulp, manual testing to see if the SLES 12 issues were fixed revealed that things are a bit more difficult than I'd hoped.

I'm putting together a new issue to thoroughly explain the problem, along with some thoughts about how we might fix it.

With the exception of syncing from SLES 12+ repositories (support for those will come with story #1358), pulp's SLES support is identical to openSUSE's. Details can be found in #927, comment 23: https://pulp.plan.io/issues/927#note-23