- Email: firstname.lastname@example.org
- Registered on: 01/05/2016
- Last connection: 03/14/2018
- Pulp (Developer, 01/06/2016)
- RPM Support (Developer, 01/06/2016)
- Puppet Support (Developer, 01/06/2016)
- Docker Support (Developer, 01/06/2016)
- Python Support (Developer, 01/06/2016)
- Packaging (Developer, 01/06/2016)
- Crane (Developer, 01/06/2016)
- OSTree Support (Developer, 01/06/2016)
- Debian Support (Developer, 01/06/2016)
- Nectar (Developer, 01/06/2016)
- External (Developer, 03/21/2017)
- File Support (Developer, 07/17/2017)
- Plugin Template (Manager, Developer, 10/04/2017)
PR was merged without approval from all the reviewers. The commit was reverted.
Please re-open PR and merge only after all reviewers approve PR.
Thanks Issue #3253 (ASSIGNED): UnicodeDecodeError in case of a non-ASCII character in comments provided ......
This reverts commit 5df74b2755e06fcb8f10b803dca0fb607c96a9d9.
re #3253 Revision 3fba75b8 (pulp): Revert "UnicodeDecodeError in comments provided with SSL cert/key"
Do we want to close this one as a WONTFIX? so it will be clear that we didn't add support for DNF. Is it ok from rel-eng standpoint?
I get that the docs and blog post were created and the docs should go into release. But for users it ... Story #1875: As a user, I can manage consumers that use DNF package managerWith Pulp3 so far underway, and not including consumers at all, adding this to Pulp2 is unlikely. I think we should do two things:
1. Create a blog post describing an alternate set of tooling (like ansible) to manage consumers via.
Add support for suse errata Revision f0ffdac0: Merge pull request #1088 from werwty/suse
"issued" date is not blank in Pulp database. After some discussion with reporter, this date is likey not parsed correctly by Katello, so Katello issue will be filed. Issue #3435: Account for different datetime format in Suse errataSuse uses a different datetime format than what pulp currently expects. Instead of a formatted data and time, they use seconds since Epoch. This is preventing pulp from correctly parsing the date, leading to a blank entry.
It seems like "RPMs and SRPMs are treated as the same at the point when decision what to download is made":https://github.com/pulp/pulp_rpm/blob/175aec177acb7538972f345b974a1361ccb59b52/plugins/pulp_rpm/plugins/importers/yum/sync.py#L616... Issue #3440: It is not possible to skip SRPMs during sync, only together with RPMsThis feature is needed by Suse users in particular. Suse it appears bundles both rpms and srpms in the same repo. As a user I would like to say "ignore srpm"
Pulp document https://docs.pulpproject.org/plugins/pulp_rpm/tech-reference/y...
Also available in: Atom