Re: SL7x and the 'epel' repo

[John Pilkington]

On 29/03/15 14:44, Tom H wrote:

On Fri, Mar 27, 2015 at 6:04 AM, John Pilkington j.p...@tesco.net wrote:

On 27/03/15 08:53, Tom H wrote:


Point releases are just a snapshot of the packages at a certain point
in time, like Debian 6.x/7.x and Ubuntu 12.04.x/14.04.x.

RHEL offers its customers an EUS program for them to remain at a point
release and get security updates but it doesn't publish the EUS
sources in the same way that it doesn't publish the ELS sources.


But my original point was that glib2-2.36.3-5, which I see in SL7x, was
incompatible with the new (in epel-testing) qtwebkit, which needed
glib2-2.40.0-4 from SL7rolling built off TUV's 7.1


If it's in epel-testing, why shouldn't only work with 7rolling?

Even if it were in epel, since RH released 7.1 threee weeks ago and
it's EPEL's target, why should EPEL care about SL (and CentOS) being
behind the curve?

I wasn't making a complaint.  I found something I didn't expect and 
thought it worth a 'heads-up.'

Re: SL7x and the 'epel' repo

[Tom H]

On Fri, Mar 27, 2015 at 11:45 AM, Steve Gaarder
gaar...@math.cornell.edu wrote:

 In that case, I'm thinking that it could be useful to maintain an EPEL
 mirror that does not get updated between TUV's release and the SL release. I
 could do that for my own use or it could be a community effort. Thoughts?

I was going to suggest the same two emails earlier but I didn't
because I couldn't think of an appropriate cut-off date to stop
rsyncing (When TUV publishes the point release? Would that be too
late? If yes to the latter, then when?). I assume that you restart
rsyncing once SL publishes the point release.