Ruediger Meier wrote:
> On Tuesday 31 January 2017, Ruediger Meier wrote:
>> On Monday 30 January 2017, Greg Freemyer wrote:
>> > On Mon, Jan 30, 2017 at 11:28 AM, reinhard hennig
>> > <reinhard.hen...@freenet.de> wrote:
>> > > my administration providing 12.000 Linux clients would appreciate
>> > > continueing evergreen with Leap42.2, because it is planned
>> > > to switch to leap 42.2 (13.2 at the moment) in a couple of
>> > > months.
>> > >
>> > > That would be great.
>> > I don't know if it is working out, but the fundamental concept of
>> > Leap is that the 42.x series is easy to upgrade between. In
>> > theory, 42.2 is 42.1 with a major service pack.
>> > Major changes will be held back until 43.x.
>> That's the theory. In practice seems that any packager/maintainer
>> changes their packages however they want.
>> For example one of my packages (sbcl) was even not building anymore
>> for 42,2 although it was fine for 42.1. I've asked to revert the
>> other incompatible change which broke my package but no chance ...
>> I've had to change my package too otherwise they would have even
>> removed my package from 42.2! Even this was a known issue, avoiding
>> or reverting incompatible changes is obviously not important for
> ... and it happened again. They upgraded 42.3 to texlive-2016 and it
> breaks again. Evergreen is still needed.
Upgrading 42.1 the other day broke a customer system for me.
Per Jessen, Zürich (7.2°C)
http://www.cloudsuisse.com/ - your owncloud, hosted in Switzerland.
Evergreen mailing list