Please be aware that puppet-pulp only supports Pulp 2.13.0 and up in git
master. Specifially it needs e1a4c26f59c6cc20603c8e4dbaddee16b65a1462[1]
which means we need to decide on what to do with the module in the
installer. We can do a new release, but that would be a major release.
The alternative is to just backport that patch in a patch release.
[1]:
https://github.com/Katello/puppet-pulp/commit/e1a4c26f59c6cc20603c8e4dbaddee16b65a1462
On Fri, Jun 30, 2017 at 09:22:10AM -0400, Tom McKay wrote:
+1 There are a number of fixes in pulp-2.13 related to syncing container
images from registries. The schema-2 will perhaps cause some visual oddness
in UI but not blocker to functionality. I would suggest raising the
priority of those issues for fixing by katello-3.15.
On Fri, Jun 30, 2017 at 9:11 AM, Justin Sherrill <[email protected]>
wrote:
+1, there is a nasty bug that prevents the syncing of some yum repos which
sadly isn't being backported. That seems severe enough to warrant pulling
it in IMHO.
Justin
On 06/28/2017 08:36 PM, Eric D Helms wrote:
Devs,
I am proposing to update Katello 3.4 to Pulp 2.13.2 in order to pull in a
number of fixes that are affecting users. These updates would move us to
the most recent stable release of Pulp and prevent users from having to do
work arounds to fix repositories that occasionally break.
One question is around changes to how Docker Schema V2 are handled and are
addressed by the open PR [1]. The inclination is to include that change
along with the update.
If anyone has any objects, questions or approval please speak up. This
would most likely be done as a stand-alone release update to limit the
amount of change.
[1] https://github.com/Katello/katello/pull/6775
--
You received this message because you are subscribed to the Google Groups
"foreman-dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
For more options, visit https://groups.google.com/d/optout.
