Home Wiki > openSUSE:Evergreen
Sign up | Login

(Redirected from Evergreen)

openSUSE:Evergreen

tagline: From openSUSE

This page describes the community maintenance project with codename Evergreen, that extends openSUSE Maintenance after the end of SUSE provided maintenance.


Evergreen

What is it?

"Evergreen" is a community effort to prolong maintenance of selected openSUSE versions as they reach official end-of-life and are listed among the discontinued distributions.

Supported distributions

The only currently supported distribution is openSUSE 11.4. Previous, current and next supported distributions can be found in the table below:

Distribution Status Support start Support end Maintainer notes
openSUSE 11.1 inactive wrosenauer Talk - Contributions Support has basically stopped meanwhile. We are still accepting updates and fixes there but nobody is watching and fixing issues.
openSUSE 11.2 inactive May 12th 2011 November 30th 2013 lijews Talk - Contributions Has not received regular updates after beginning of December 2013.
openSUSE 11.4 active November 5th 2012 July 2014 wrosenauer Talk - Contributions lijews Talk - Contributions
openSUSE 13.1 planned May 2015 November 2016

The newest Evergreen supported release is openSUSE 11.4. Official announcement of it was made in November 2012. The next openSUSE version which is planned to be supported by Evergreen project is 13.1.

openSUSE 11.1 was supported for three years in the end. That's what we want to provide at least for all future versions as well. It was also possible to provide updates for all parts of the distribution and therefore that's the goal for later releases as well.

How to activate

Version 11.4

  • In YAST or via zypper, add the update repository as outlined below and accept the new key offered.

Nothing else should be needed to make the update stack behave exactly as before with patch, delta-rpm support etc. Security patches and critical bug fixes will flow to the Evergreen enabled openSUSE 11.4 simply by occasionally running YaST Online Update or "zypper patch" in a root terminal.

The user/administrator should be mindful that enabled repositories other than those for openSUSE 11.4 oss, non-oss, packman and Evergreen may both introduce instabilities and YaST/zypper reported inconsistencies which will need to be settled as required for continued security and stability.

Version 11.2

Most of 11.2 info was moved to Evergreen 11.2 wiki page.

How to migrate

There are two possible ways to migrate to some Evergreen covered openSUSE version. The first one use online repository and is mostly covered in the following link. Another way is to use DVD (still can be taken from here) and choose Upgrade during initial screens of Install Process.

Remember - every update can be dangerous to your data, so ALWAYS backup important files.

Note: I didn't test switching from KDE3 (from Evergreen 11.1) to KDE4. If someone knows any issues please provide tips and/or warnings here.

Communication

Communication currently happens via the mailing list evergreen. This list is mainly meant for packagers and contributors but can be used by users as well. But you should be able to get help on the common openSUSE list as well.

Lead developer of the project is Wolfgang Rosenauer.

Stefan Lijewski is leading Evergreen for the 11.2 version while for 11.4 it's a combined effort.

Update Policy

An update policy is not yet in place, but in general it will align along the regular openSUSE maintenance policies.


Team members

Testing

Since we are a small community doing Evergreen we would appreciate if users could join us in testing upcoming updates. For 11.4 this just means to add the following repository to the software management

and report issues through our mailing list.

Packager information

From Evergreen:11.4 we decided to follow openSUSE maintenance workflow. So if you want to update packages for Evergreen supported distribution version which is higher then 11.2 follow steps below.

Version 11.4 and higher

Typically you just want to update some Evergreen package. Then you have to create a maintenance branch, just like for regular openSUSE project. But for Evergreen there are other attributes, where osc should look for affected packages and update project. Note: beware that the following may not work using webui. Packagers are strongly encourages to use osc command line.

The workflow should looks like this:

  • create maintenance branch:
osc mbranch -u Evergreen:UpdateProject -a Evergreen:Maintained $PACKAGE
  • check it out:
osc co home:LOGIN:branches:Evergreen_Maintained:$PACKAGE
  • now you should have sources for all Evergreen maintained projects under:
home:LOGIN:branches:Evergreen_Maintained:$PACKAGE
  • now you can update sources, add patches, test build, document changes and so on;\
  • check-in your packages to server
osc ci
  • at the end you should create or update patchinfo package:
cd home:LOGIN:branches:Evergreen_Maintained:$PACKAGE; osc patchinfo
  • fill the patchinfo using your favorite editor or webui
  • if you created patchinfo locally submit them as well
osc ci
  • at the end create maintenance incident for Evergreen project:
osc mr -a Evergreen:MaintenanceProject

Version 11.2 and lower

Most of 11.2 info was moved to Evergreen 11.2 wiki page.

Update status

An overview of the current update status with the fixed or improved packages is shown on the page Evergreen 11.1 and Evergreen 11.2.

openSUSE links