Pulp 3: -
comps.xml relation issues - PR for PackageGroups which removes relations completely - https://github.com/pulp/pulp_rpm/pull/1745 - Backward incompatible change in REST API - Ok, because it’s a bug fix - Likely no usage outside of copy which can handle it without knowing the relations - AI: discuss if other relations for comps needs to be removed or only packages to groups - Rethinking SLES Remote as a separate Remote - Maybe it’s not more usable? - https://github.com/pulp/pulp_rpm/pull/1729#issuecomment-641478315 - Keep one Remote - Make parameter name specific - sles_auth_token - Have one rpm specific downloader, don’t call it anything specific, so in the future we can add more functionality to it to avoid the case with mutually exclusive downloaders - Do we still need the ‘Pulp3 RPM blocker’ tag or can we remove it? - We can remove it - bmbouter will handle it - Do we have any timeline for https://pulp.plan.io/issues/5200 - dkliban to try to come up with rough design during the sprint - Client certs w/ Remote (newline problem) - Need to use at notation (@~/file) not a string for correct process of control chars - CentOS 8 kickstart repo bug - https://pulp.plan.io/issues/6568 - dkliban to reach out to productmd dev Pulp 2: - Failed content view deletions - https://bugzilla.redhat.com/show_bug.cgi?id=1743776#c13 - https://git.io/Jf98f - AI: ttereshc to look at response/patch Open PRs: - https://github.com/pulp/pulp_rpm/pulls Triage: - Un-triaged bugs https://pulp.plan.io/projects/pulp_rpm/issues?query_id=30 - Didn’t have time to cover it, will do it online today or on Monday
_______________________________________________ Pulp-dev mailing list Pulp-dev@redhat.com https://www.redhat.com/mailman/listinfo/pulp-dev