What would latest point to? The most recent release? or nightly? Part of
the challenge is that katello-agent doesn't always work the previous
version so if you pulled "lateast" without updating your server it might
break things.
> What would latest point to? The most recent release? or nightly? Part of
> the challenge is that katello-agent doesn't always work the previous
> version so if you pulled "lateast" without updating your server it might
> break things.
>
> Eric
Or make it easier in general to sync community repos. It's always been
in the back of my mind about introducing an alternative provider to the
Red Hat one, that would let users sync CentOS, EPEL, and our repos, just
by checking a box like they do for Red Hat products.
···
On Wed, Nov 18, 2015 at 02:08:02PM -0500, Eric D Helms wrote:
@Eric - I didn't realise there was a lack of backwards compatibility (a
matrix of what does work together would help). Obviously you have nightly
already (which is a bit bleedin' edge for our needs), but if 'latest' for
katello and 'latest' for katello-agent were released in step…so if you
released 2.5 of Katello (as stable/prod), and the 2.4 client was compatible
(and the most recent/stable/prod client), 'latest' would point to each of
them (in their respective repos).
@Stephen - that sounds interesting. I think I'd need to see more of what
you are discussing to understand. I do find the way the RHEL products are
pulled into Katello a bit restrictive - e.g. the names are fixed and you
can't add further repos under the 'Red Hat…' product.
On an unrelated note, and just whilst I have you, I'm finding Katello far
more stable/reliable/faster. Thanks for all the hard work.
···
On 18 November 2015 at 19:15, Stephen Benjamin wrote:
On Wed, Nov 18, 2015 at 02:08:02PM -0500, Eric D Helms wrote:
What would latest point to? The most recent release? or nightly? Part of
the challenge is that katello-agent doesn’t always work the previous
version so if you pulled “lateast” without updating your server it might
break things.
Or make it easier in general to sync community repos. It’s always been
in the back of my mind about introducing an alternative provider to the
Red Hat one, that would let users sync CentOS, EPEL, and our repos, just
by checking a box like they do for Red Hat products.