On Mon, Nov 27, 2017 at 12:38 PM, Brian Bouterse <[email protected]> wrote:
> A Katello user visited the #pulp-dev channel who was affected by a bug in > Pulp 2.13.2 that was fixed in Pulp 2.13.4. The only fix for the user is for > Katello to upgrade the version it is distributing from 2.13.2 -> 2.13.4. > > What if Pulp bits were delivered to Katello users directly from the Pulp > repos? For the 2.13.z for example that would be these repos [0]. You can > lock onto a specific x.y version of Pulp and just have clients receive > z-stream Pulp releases as they become available. > > What do Katello devs think about a change like this? > +1 to this from myself. It reduces our efforts and gets users fixes faster. In the past pulp was not reliable to do this, but the past 5 or so 2.Y releases have been stable enough and I do not believe we've seen an issue that would have held us back from including a z-release. What would need to happen to make a change like this? > We'd need to: * update https://github.com/theforeman/foreman-packaging/blob/rpm/develop/katello/katello-repos/katello.repo#L12-L17 to point to a specific release * update documentation around updating pulp https://theforeman.org/plugins/katello/developers.html#upgrading-pulp * update tool belt: https://github.com/theforeman/tool_belt i'd recommend we file a katello issue to track these 3 items if there are no objections Justin > > [0]: https://repos.fedorapeople.org/pulp/pulp/stable/2.13/ > > -Brian > > -- > 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. > -- 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.
