[Pulp-list] pulp3 sync epel repo

[Brian Bouterse]

I agree a single mirror as the source URL is what is expected currently.

Neither pulp_rpm for either Pulp2 or Pulp3 (not GA yet) implement metalink
support currently. You can file a feature request against Pulp3 to request
this feature here:  https://pulp.plan.io/projects/pulp_rpm/issues/new



On Sat, Oct 12, 2019 at 9:03 PM aaron.t.wyllie <aaron.t.wyllie at gmail.com>
wrote:

> EPEL metalinks point to any number of hosted repositories with the closest
> and fastest being chosen each time.
>
> I would suggest chosing a single provider from the EPEL mirrors list as
> your source URL.  You could also point it at the primary repository that
> will be commented out in the epel.repo file.
>
> I don't know the specifics behind why Pulp would fail but I suspect that
> it is not able to arbitrarily change the source URL every time it is sync'd
> as provided through a metalink value.
>
>
> -------- Original message --------
> From: "Bin Li (BLOOMBERG/ 120 PARK)" <bli111 at bloomberg.net>
> Date: 10/12/19 20:30 (GMT-05:00)
> To: pulp-list at redhat.com
> Subject: [Pulp-list] pulp3 sync epel repo
>
> We are able to use "reposync" command to sync epel repo with the metalink,
> metalink=
> https://mirrors.fedoraproject.org/metalink?repo=epel-source-7&arch=$basearch,
> defined in the yum.repo.d. Pulp3 failed to sync to the same url which we
> defined in the remote. Is this expected behavior? What url should we use to
> sync the epel repo?
>
> Thanks
> _______________________________________________
> Pulp-list mailing list
> Pulp-list at redhat.com
> https://www.redhat.com/mailman/listinfo/pulp-list
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://listman.redhat.com/archives/pulp-list/attachments/20191014/d313a657/attachment.htm>