[Pulp-list] pulp-2to3-migration 0.11.2 is Generally Available

See the announcement here: https://github.com/pulp/community/discussions/24 ___ Pulp-list mailing list Pulp-list@redhat.com https://listman.redhat.com/mailman/listinfo/pulp-list

[Pulp-list] pulp_rpm 3.11.1 is Generally Available

pulp_rpm 3.11.1 has been released. It is compatible with pulpcore 3.7 and up to pulpcore 3.12. This release contains a couple of fixes for the issues introduced in 3.11.0. For more details and a full list of changes, see the changelog. PyPI: https://pypi.org/project/pulp-rpm/3.11.1/ Changelog:

Re: [Pulp-list] As a user, how to clear/clean contents in pulp?

Good idea. I filed the docs story https://pulp.plan.io/issues/8842 to track that. Thanks, Tanya On Mon, May 31, 2021 at 12:13 PM Quirin Pamp wrote: > Perhaps there should be an "Orphan Cleanup" workflow section here: > https://docs.pulpproject.org/pulpcore/workflows/index.html ? > It could

[Pulp-list] pulp_rpm 3.12.0 is Generally Available

pulp_rpm 3.12.0 has been released. It is compatible with pulpcore 3.12 and the upcoming pulpcore 3.13. This release introduces: - support for automatic publishing and distributing - ability to synchronize Oracle ULN repositories It also contains bug fixes in many areas, including advisory

[Pulp-list] pulp_rpm 3.11.0 is Generally Available

pulp_rpm 3.11.0 has been released. It is compatible with pulpcore 3.7 and up to pulpcore 3.12. It has support for the new changes in modularity (static_context) and a set of important fixes, including the decreased memory consumption at sync time. For more details and full list of changes, see

Re: [Pulp-list] pulp-2to3-migration Only one migration plan can run or be reset at a time

Adding pulp-list back, missed the reply-all button. On Tue, May 18, 2021 at 10:27 AM Tanya Tereshchenko wrote: > Hello Ben, > > Just to be clear, the reset step is optional. It's only needed if > something went very wrong and you'd like to start migration of a certain > plug

[Pulp-list] pulp-2to3-migration 0.11.1 is Generally Available

The pulp-2to3-migration 0.11.1 is now generally available. It is compatible with pulpcore 3.6 and up to 3.12. This release contains bug fixes: - for pulp_deb migration - for systems which started using pulp2 long time ago - for systems having corrupted docker content For more details and full

[Pulp-list] pulpcore 3.12.2 is Generally Available

Pulpcore 3.12.2 is now available [0]. This release contains a backport which fixes handling of repositories with non-sha256 checksums. For more details, see the 3.12.2 changelog [1]. # Installation and Upgrade Users should use the 3.12.2 release of pulp_installer [2] to install or upgrade their

[Pulp-list] pulpcore 3.7.6 is Generally Available

Pulpcore 3.7.6 is now available [0]. This release contains a backport which fixes handling of repositories with non-sha256 checksums. For more details, see the 3.7.6 changelog [1]. # Installation and Upgrade Users should use the 3.7.6 release of pulp_installer [2] to install or upgrade their

[Pulp-list] pulpcore 3.7.5 is Generally Available

Pulpcore 3.7.5 is now available [0]. This release contains backports needed for pulp-2to3-migration plugin cases to handle artifacts better. It also allows to install a newer PyYAML package to address CVE-2020-14343 [1]. For more details, see the 3.7.5 changelog [2]. # Installation and Upgrade

[Pulp-list] pulp-2to3-migration 0.11.0 is Generally Available

The pulp-2to3-migration 0.11.0 is now generally available. It is compatible with pulpcore 3.6 and up to the 3.12. This release has some performance improvements and it also introduces a configuration option to control the size of the batch your content migration deals with. For more details and

Re: [Pulp-list] [Pulp-dev] PulpCon 2021

On Wed, Mar 31, 2021 at 2:39 PM Melanie Corr wrote: > > > Ar Céad 31 Márta 2021 ag 13:36, scríobh Grant Gainey : > >> On Wed, Mar 31, 2021 at 8:00 AM David Davis >> wrote: >> >>> After talking to some people this morning, it sounds like November 8-12 >>> would also work. I think people would

[Pulp-list] pulp-2to3-migration 0.10.0 is Generally Available

The pulp-2to3-migration 0.10.0 is now generally available. It is compatible with pulpcore 3.6 and up to the upcoming 3.12. This release contains mostly fixes for re-migration cases and it's also a compatibility release with the upcoming pulpcore 3.12. For more details and full list of changes,

[Pulp-list] pulpcore 3.7.4 is Generally Available

Pulpcore 3.7.4 is now available [0]. This release contains only one backport [1] for Pulp not to load .env files from the user environment. # Installation and Upgrade Users should use the 3.7.4 release of pulp_installer [2] to install or upgrade their installations. This version of the installer

[Pulp-list] pulp-2to3-migration 0.9.0 is Generally Available

The pulp-2to3-migration 0.9.0 is now generally available. It is compatible with pulpcore 3.6 and up to the upcoming 3.11. Here are some highlights: - more performance improvements for migration re-runs - various bug fixes for re-migration cases - adjusted docs examples to use pulp CLI instead

[Pulp-list] pulp_file 1.6.0 is Generally Available

The pulp-file 1.6.0 is now generally available. It is compatible with pulpcore 3.7 and up to the upcoming 3.11. It's mostly a compatibility release with some bug fixes and doc improvements. For more details and full list of changes, see the changelog. PyPI:

Re: [Pulp-list] 'utf8' codec can't decode byte 0x9c in position 1: invalid start byte

Hi, This is likely related to this bugfix https://pulp.plan.io/issues/723 which was released in 2.12.2 in pulp_rpm, make sure that pulp_rpm plugin is up to date. Looking at the traceback, you seem to use nodes. They are deprecated starting with 2.12, and it's possible that something stopped

[Pulp-list] pulp-2to3-migration 0.8.0 is Generally Available

The pulp-2to3-migration 0.8.0 is now generally available. It is compatible with pulpcore 3.6 and up to 3.10. Here are some highlights: - pulp_deb support (added migration for remaining content types) - performance improvements for migration re-runs - provided a default configuration for

Re: [Pulp-list] epel syncs all advisories every time

if there is any demand for such a feature. The solution won't be ideal, any automated conflict resolution for the remaining cases would be under use-it-at-your-own-risk category. Tanya On Wed, Feb 10, 2021 at 3:34 PM Tanya Tereshchenko wrote: > Great, it confirms that the advisory is recrea

Re: [Pulp-list] how do I remove migration plugin and data

update and test again > > > > -- > *From:* Winberg Adam > *Sent:* 10 February 2021 16:15 > *To:* Tanya Tereshchenko > *Cc:* pulp-list@redhat.com > *Subject:* Re: [Pulp-list] how do I remove migration plugin and data > > > > Could you sh

Re: [Pulp-list] epel syncs all advisories every time

w day (i.e. after epel repo metadata has been updated). > > I created an issue for this, https://pulp.plan.io/issues/8229, since I > don't think an advisory should be replaced in Pulp if the only changed > metadata is 'updated_date'. But I might not see the whole picture. > > //A

Re: [Pulp-list] epel syncs all advisories every time

Hi Adam, If you see this AdvisoryConflict for the migrated repos, please file an issue https://pulp.plan.io/projects/migration/issues/new Pulp2 managed advisories in a completely different way so there could be pkglist discrepancies when trying to update them (because Fedora advisories often

Re: [Pulp-list] how do I remove migration plugin and data

Hi Adam, There is a story filed to add an ability to remove a plugin and its data. Please follow it here https://pulp.plan.io/issues/7822 and feel free to leave a comment to express your interest or reasons to remove. We plan to work on it relatively soon, but it was not on a high priority list

[Pulp-list] pulpcore 3.10.0 is Generally Available

Pulpcore 3.10.0 [0] and pulp_installer 3.10.0 [1] have been released. Details of the most important changes are available in our blog [2]. For a full list of changes, please check the changelog for pulpcore [3] and pulp_installer [4]. Try to upgrade right away! It should be possible to upgrade

[Pulp-list] pulp-2to3-migration 0.7.0 is Generally Available

The pulp-2to3-migration 0.7.0 is now generally available. It is compatible with pulpcore 3.6 and up to the future 3.10. Here are some highlights: - performance improvements for simple migration plans, some parts run in multiple tasks in parallel - improved reliability of the remigration in case

[Pulp-list] pulp-2to3-migration 0.6.0 is Generally Available

The pulp-2to3-migration 0.6.0 is now generally available. It is compatible with pulpcore 3.6 and up to the future 3.9. Here are some highlights: - pulp_deb support (packages only at the moment) is in tech preview - ability to start migration from scratch - ability to skip corrupted Pulp 2

Re: [Pulp-list] [Pulp-dev] pulp3 operations

Hi Erik, Thank you so much for sharing! A great example of using Python bindings for client tooling. I'm adding pulp-list to share it with more users, and not only developers. Thank you, Tanya On Sat, Nov 14, 2020 at 6:43 PM Erik K. Whitesides wrote: > Hi - not sure if anyone is interested,