openSUSE:Packaging for Leap
|Cette page n'est pas encore traduite (ou pas complètement)|
Cet article a besoin d'être traduit. Merci de participer au travail si vous en avez le temps et la compétence.
- 1 When can packages be submitted into Leap
- 2 How to add a new package to an openSUSE Leap release in development
- 3 How to upgrade a package in an openSUSE Leap release in development
- 4 How to add a new package to a released openSUSE Leap version
- 5 Development Information
When can packages be submitted into Leap
In general, packages can only be added to an openSUSE Leap version during its development, not after its release. Any exceptions have to be approved and processed by the Maintenance team.
Packages that are already in openSUSE Factory will not automatically show up in Leap. Acceptance in Factory usually is a precondition though.
How to add a new package to an openSUSE Leap release in development
Note that openSUSE Leap 42.3 and 15.0 are now under maintenance. This section applies to openSUSE Leap 15.1
For people familiar with the Factory Development Model, Factory serves a purpose for Leap similar to the purpose a Devel Project serves for Factory.
By default new packages for Leap must either come from SLE or be accepted in Factory first.
Preferably new packages should be introduced on the opensuse-factory list with a link to the submit request. A good introduction contains information on the state of the upstream project, how maintainable it is and what the purpose of having it in the distribution will be.
Example of submitting from the Factory devel project:
It's also possible to submit from Factory but that requires extra hacks:
Because of bugs in OBS, ~/.oscrc must have submitrequest_on_accept_action unset, and there must be no --cleanup nor --no-cleanup specified on the osc command line. Otherwise, OBS would return a permission error.
The following example shows how to submit a package from SLE:
If a package for Leap for whatever reason cannot be taken from either SLE or Factory the reason for that should be explained in the submit request.
How to upgrade a package in an openSUSE Leap release in development
In general version updates of packages in minor Leap version upgrades are possible. The packager should carefully consider the pros and cons of such upgrades for the users though. Within a major version Leap is considered stable, so overly disruptive and incompatible changes are to be avoided.
After careful consideration of the pros and cons the same process as with new packages applies. I.e. packages must be accepted in Factory first.
How to add a new package to a released openSUSE Leap version
- packages with free software license 
- packages with non free licenses 
- updates for packages with free software license 
- updates for packages with non free licenses 
Many packages in openSUSE Leap 15.1 come from other projects. During the development phase release engineers may pull package updates from those. A mapping file specifies the origin of each package.
- SUSE Linux Enterprise packages: pulled automatically
- Factory package updates: pulled automatically until package freeze.
RPM Distro Version Macros
- suse_version 1315 for the full time life of SLE12 and openSUSE:Leap:42.x
- suse_version 1500 for the full time life of SLE15 and openSUSE:Leap:15.x
- additionally is_opensuse 1 for openSUSE:Leap:* to mark differences
|SLE15:GA||SLE15:SP1||Backports:SLE-15||Leap 15.0||Leap 15.1||Tumbleweed|
|SLE12:GA||SLE12:SP1||SLE12:SP2||SLE12:SP3||SLE12:SP4||Backports:SLE-12||Leap 42.1||Leap 42.2||Leap 42.3|
- never rely on this version, it may change
- leap_version is deprecated, use is_opensuse and sle_version instead
- Backports:* projects inherit the %sle_version macro from the corresponding SLE release
- %is_backports macro is set on all openSUSE:Backports:SLE-*-* projects
For cross distribution have a look here: openSUSE:Build_Service_cross_distribution_howto
Tips and Tricks
Package not checked in for weeks
Build failure in Staging:adi
All package submissions are built isolated in openSUSE:Leap:15.1:Staging:adi:<number> to make sure the submission is complete. Sometimes that fails due to different configurations in the devel project for example. Sometimes other packages need to be grouped into the same project. Talk to the release team if a package needs manual help there.
The 15.1 submissions wait for the submission to Factory in order to pass reviews there. Sometimes leaf packages have to wait a long time due to low priority. If a Factory submission is stuck e.g. in legal review for too long and it affects 15.1 talk to the release team so they can adjust priorities.
Packages submitted by someone other than the Factory package maintainer(s) have a review set to the devel project/package to ask for permission by the Factory package maintainer. If there's no reply for too long, try adding a comment in the request to get some attention or talk to the project maintainers directly.