Home Home > Tag > Maintenance
Sign up | Login

Posts Tagged ‘Maintenance’

openSUSE Leap 42.3 End of Life is Extended

August 8th, 2018 by

The usual lifetime of openSUSE Leap minor versions have traditionally received updates for about 18 months, but the minor version of Leap 42.3 is being extended.

The last minor version of the Leap 42 series was scheduled to be maintained until January 2019, but that has changed thanks to SUSE committing to additional months of maintenance and security updates. Leap 42.3 is based on SUSE Linux Enterprise Server 12 Service Pack (SP) 3  and SUSE has agreed to keep publishing updates for Leap 42.3 until June 2019.

This means the extended End of Life for Leap 42.3 will increase the total lifetime of the Leap 42 series to 44 months.

Users of the openSUSE Leap 42 series are encouraged to use the additional months to prepare the upgrade to Leap 15, which was released in May.

Those who can’t migrate production servers to the new major version in time may want to take a (commercial) SLE subscription into consideration, which provides even a longer lifecycle. The proximity of Leap 42’s base system to SLE 12 keeps the technical effort to migrate workflows from Leap to SLE low.

 

12.1 update repository changes

February 20th, 2012 by

Teams from the openSUSE Buildservice and openSUSE Maintenance worked together since weeks now to integrate openSUSE distribution maintenance support into the Buildservice on build.opensuse.org.

There were a lot of changes and a lot of places had to be adapted, but finally they got it working: maintenance updates for openSUSE 12.1 are now handled inside the openSUSE Buildservice without further need of SUSE internal scripts (well: we still will have some of them running as backup for a while now).

As a lot of people were involved in this task and a lot of code has been written, some smaller bugs might still be included, even if everyone tries to avoid failures. One of the most visible bugs was the unsigned 12.1 update repository from 2012-02-18 until 2012-02-19: the reason was a sync script that tried to pull the repository from a wrong location where the signing was not yet done with the new setup.  We apologize for the trouble and irritation caused and really appreciate all the reports from our users about that broken repository – as this shows the high amount of interest and knowledge about the security impact such an unsigned repository has.