Pulp - 2.20.0 about 6 months late (07/16/2019) 96% 27 issues (26 closed — 1 open) Related issues Issue #4818: Updating a yum_repo_metadata_file unit silently does nothing Actions Issue #4869: Use RPMTAG_MODULARITYLABEL to determine modular RPM Actions Issue #4880: Missing rpms in erratum pkglist when an erratum appears in multiple repos caused wrong applicability calculation. Actions Issue #4892: ISO repo copy can lead to a duplicates in a target repo and corrupted manifest Actions Story #4868: As a user, I can list modules in a repository with "pulp-admin rpm content module...." Actions Test #4930: NaUse RPMTAG_MODULARITYLABEL to determine modular RPM Actions Test #4943: ISO repo copy can lead to a duplicates in a target repo and corrupted manifest Actions Test #4995: Modules are incorrectly copied when their artifacts shadow the names of non-modular RPM dependencies Actions
Pulp 3 RPM MVP 100% 13 issues (13 closed — 0 open) Related issues Issue #3952: Using the ErrataRelatedModelSaver can result in creating incomplete content. Actions Issue #4013: UpdateRecord index row size is too large Actions Issue #4014: UpdateCollections/UpdateCollectionPackages are synced/stored incorrectly Actions Issue #4026: DNF does not show published errata Actions Issue #4031: MemoryError during sync of a repo with many errata Actions Issue #4033: updateinfo.xml is published with "unknown checksum" type if it's not present in a remote repo Actions Task #3199: Create model(s) for a Package content type Actions Task #3201: Create model(s) for Erratum content type Actions Task #3998: Store UpdateReference information during sync Actions Story #3202: As a user, I can sync RPM/SRPM/Erratum from a remote Yum/DNF repository Actions Story #3204: As a user, I can publish RPM/Erratum in a way that is consumable by yum/dnf Actions Story #3417: As a user, I have a README.md with documentation in it Actions Story #4163: As a user, I can install pulp_rpm using the Ansible installer Actions
Pulp 3.x RPM (Katello release) A release with all the features needed for Katello to switch to Pulp 3 RPM plugin. 12% 23 issues (0 closed — 23 open) Related issues Issue #6018: As a user, I have an API for copying content between repositories Actions Task #5158: Analyze existing opensource projects to potentially be used for applicability calculation Actions Task #5934: Implement API for applicability Actions Task #5935: Model and build relations between Advisory and Package Actions Task #5936: Build additional fixtures to represent all cases needed to test applicability Actions Task #5937: Write tests for checking applicability correctness Actions Task #5938: Add swagger docs for applicability API Actions Task #5939: Benchmark performance and optimize applicability Actions Task #5940: Implement backend initial calculation of applicability Actions Story #4761: As a user, I have RPM dependency solving Actions Story #4762: [Epic] As a user, I can copy content Actions Story #4908: [Epic] As a user, I can manage modular content Actions Story #5110: [Epic] As a user, I can manage Kickstart repositories Actions Story #5111: [Epic] As a user, I can calculate applicability Actions Story #5112: [Epic] As a user, I can manage auxiliary content types Actions Story #5113: [Epic] Sync optimizations and features Actions Story #5114: [Epic] Publish features Actions Story #5117: [Epic] As a user, I can export RPM repositories Actions Story #5127: {Epic] As a user, I can migrate all RPM plugin content from Pulp2 to Pulp3 Actions Story #5429: As a user, I can manage custom repository metadata Actions Story #5933: As a user I can determine applicability in pulp3 Actions Story #5950: Add database support for comparing EVRs Actions Story #6019: As a user, I can specify content to be copied by the content's pulp_href Actions
.
.
.