[Pulp-list] Pulp 2.10.1 Beta 1 now available!
Pulp 2.10.1 Beta 1 is now available in the beta repositories: https://repos.fedorapeople.org/repos/pulp/pulp/beta/2.10/ This release includes bug fixes to Pulp Platform, the RPM Plugin, and the OSTree plugin. Upgrading = The 2.10 beta repositories are included in the pulp repo files: https://repos.fedorapeople.org/repos/pulp/pulp/fedora-pulp.repo for fedora 23 & 24 https://repos.fedorapeople.org/repos/pulp/pulp/rhel-pulp.repo for RHEL 6 & 7 After enabling the pulp-2.10-beta repository, you'll want to follow the standard upgrade path with migrations: > $ sudo systemctl stop httpd pulp_workers pulp_resource_manager pulp_celerybeat > $ sudo yum upgrade > $ sudo -u apache pulp-manage-db > $ sudo systemctl start httpd pulp_workers pulp_resource_manager > pulp_celerybeat Issues Addressed These issues are fixed in Pulp 2.10.1: OSTree Support 2237Published repositories are copied instead of linked 2213Proxy URL for remotes not properly constructed. Pulp 2328Repository syncs show all units updated even when there are no changes 2287Cannot get docker v2 repo tags list 2278Remove checksum_type from the srpm and drpm collections 2277Content published using move (instead of copy) causes 404 due to selinux denial. 2221rsync distributor doesn't remove files from remote when rsyncing empty repository with --delete 2049Django RemovedInDjango110Warning in logs for missing TEMPLATES setting 1766Pulp API is incompatible with Django 1.10 1392Misleading nodes quickstart howto RPM Support 2326Publishes fail 2257unit test failure: "AppRegistryNotReady: Apps aren't loaded yet." 2242Package signature ID checking is broken when syncing in packages 2227Only first pkglist is synced for erratum even if multiple are present 2190Unit is associated with the repo before it is copied to the final location View this list in Redmine: http://bit.ly/2eqCCZe signature.asc Description: OpenPGP digital signature ___ Pulp-list mailing list Pulp-list@redhat.com https://www.redhat.com/mailman/listinfo/pulp-list
[Pulp-list] Pulp migration order
We're working on some custom Pulp migrations to fix up some data issues in our Pulp installation. https://docs.pulpproject.org/dev-guide/newtypesupport/plugin/migrations.html The migration mechanism has an annoying restriction: there aren't allowed to be any gaps in the migration sequence. For example, if I have 0001_my_first_migration.py and 0003_add_email_addresses_to_users.py then pulp-manage-db won't run migration 3 due to the absence of a migration numbered 2. There is a good reason for it not to work this way: this means that the next number in the sequence is in contention between all separately developed patches which might need to add migrations. For example, if there are currently migrations 1-3, multiple developers working on new migrations concurrently are all forced to use number 4 (otherwise their code won't run) but in the end, only one of them can "win" and all the others will have to renumber theirs later. If the migrations are independent from each other, that's wasted time. Compare with e.g. ActiveRecord where migrations are "numbered" by timestamp at time of generation, and there's no problem merging branches where unrelated migrations were authored separately. http://guides.rubyonrails.org/active_record_migrations.html Is there a particular reason for the current pulp migration system to work this way? ___ Pulp-list mailing list Pulp-list@redhat.com https://www.redhat.com/mailman/listinfo/pulp-list
