Re: [Evergreen] Continuing evergreen with Leap42.2

2017-02-24 Thread Rüdiger Meier
On 02/23/2017 06:00 PM, Christian Boltz wrote: Hello, Am Donnerstag, 23. Februar 2017, 13:46:51 CET schrieb Ruediger Meier: On Thursday 23 February 2017, Carlos E. R. wrote: What worries me is that we got 2 kernel updates in a month. Several updates this month that require a reboot

Re: [Evergreen] Continuing evergreen with Leap42.2

2017-02-24 Thread Per Jessen
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 >> > >> > wrote: >> > > my administration providing 12.000 Linux clients would

Re: [Evergreen] Continuing evergreen with Leap42.2

2017-02-23 Thread Christian Boltz
Hello, Am Donnerstag, 23. Februar 2017, 13:46:51 CET schrieb Ruediger Meier: > On Thursday 23 February 2017, Carlos E. R. wrote: > > What worries me is that we got 2 kernel updates in a month. Several > > updates this month that require a reboot (systemd, apparmor...). Not > > good for server

Re: [Evergreen] Continuing evergreen with Leap42.2

2017-02-23 Thread Christian
Am 23.02.2017 um 17:13 schrieb Carlos E. R.: > The point is, one does not expect that many updates in a stable release. We should not complain about getting updates and sec fixes ... such fast and without any specific 'Patchday' ... ... or do you prefer to sit and wait for fixes for weeks to get

Re: [Evergreen] Continuing evergreen with Leap42.2

2017-02-23 Thread Steven Caron
, 2017 11:13 AM To: evergreen@lists.rosenauer.org Subject: Re: [Evergreen] Continuing evergreen with Leap42.2 NOTICE: This email was received from an EXTERNAL sender ___ Evergreen mailing list

Re: [Evergreen] Continuing evergreen with Leap42.2

2017-02-23 Thread Ruediger Meier
On Thursday 23 February 2017, Carlos E. R. wrote: > On 2017-02-23 13:46, Ruediger Meier wrote: > > On Thursday 23 February 2017, Carlos E. R. wrote: > >> El 2017-02-22 a las 11:37 +0100, Ruediger Meier escribió: > >>> ... and it happened again. They upgraded 42.3 to texlive-2016 and > >>> it

Re: [Evergreen] Continuing evergreen with Leap42.2

2017-02-23 Thread Carlos E. R.
On 2017-02-23 13:46, Ruediger Meier wrote: > On Thursday 23 February 2017, Carlos E. R. wrote: >> El 2017-02-22 a las 11:37 +0100, Ruediger Meier escribió: >>> ... and it happened again. They upgraded 42.3 to texlive-2016 and >>> it breaks again. Evergreen is still needed. >> >> That will be

Re: [Evergreen] Continuing evergreen with Leap42.2

2017-02-23 Thread Ruediger Meier
On Thursday 23 February 2017, Carlos E. R. wrote: > El 2017-02-22 a las 11:37 +0100, Ruediger Meier escribió: > >> 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

Re: [Evergreen] Continuing evergreen with Leap42.2

2017-02-22 Thread Ruediger Meier
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 > > > > wrote: > > > my administration providing 12.000 Linux clients would appreciate > > > continueing evergreen

Re: [Evergreen] Continuing evergreen with Leap42.2

2017-01-31 Thread Ruediger Meier
On Monday 30 January 2017, Greg Freemyer wrote: > On Mon, Jan 30, 2017 at 11:28 AM, reinhard hennig > > wrote: > > my administration providing 12.000 Linux clients would appreciate > > continueing evergreen with Leap42.2, because it is planned > > to switch to leap