[Pulp-dev] Package in a different repo does not get added to package list on Module
ipanova at redhat.com
Wed Mar 18 13:04:41 UTC 2020
This has always been a grey area:
what if the user who has created RepoA cannot access content to the repoB
and yet we are 'stealing' the content from repoB?
Senior Software Engineer| Pulp| Red Hat Inc.
"Do not go where the path may lead,
go instead where there is no path and leave a trail."
On Tue, Mar 17, 2020 at 7:41 PM Pavel Picka <ppicka at redhat.com> wrote:
> started to work on #6295  and by now at sync we look only for actual
> (repository we are syncing) packages if they are modular and connect to
> To fix this issue we will need to check content from other repositories
> (already synced) what can have a really huge impact on sync time in case of
> big repositories.
> Do we want to get through all pulp content (RPM packages) when syncing new
> repository with modulemd? Or idea can be to extend sync API call with new
> argument to scan (all or specific) repositories.
> I think we would like to keep performance of sync so better to discuss
> Thank you
>  https://pulp.plan.io/issues/6295
> Pavel Picka
> Red Hat
> Pulp-dev mailing list
> Pulp-dev at redhat.com
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the Pulp-dev