Bering-uClibc 6.x - Developer Guide - The Release Process

From bering-uClibc
Revision as of 12:56, 1 September 2019 by Kapeka (Talk | contribs) (Commit Packages to SF SCM with

Jump to: navigation, search
The Release Process
Prev Bering-uClibc 6.x - Developer Guide


The target audience for this page are LEAF maintainers and admins.

The page describes the release process, mostly as reminder. Note: Various steps require (different) administrator privileges.

Rebuild new release from source

It is recommended to do a completly fresh build from the sources. Use the command:

./buildtool distclean

Compile the build environment and all packages.


To compile build environments and packages for all supported architectures in one go, the shell script has been added in the tools directory. To save time, it is also possible to blacklist packages that are known fail to build or only necessary for special tasks (e.g. valgrind.lrp).

Sign Packages with GPG maintainer key

Starting with LEAF Bering-uClibc 6.2.2 we do provide gpg-signed Packages.

The Packages are signed with a maintainer key. The available and valid keys are collected in /root/.gnupg/LEAF_sigkeys.gpg.

initrd.lrp has to be signed with an external signature, all other Packages are signed with an inline signature.

To accomplish that task, run:


if [ -z "$1" ]
echo 'missing architecture e.g. i486-unknown-linux-uclibc' 

PROGPATH=$( dirname $0 )


# sign initrd.lrp with detached signature
gpg  --passphrase "$PASSPHRASE" -u $USERID -b $PROGPATH/package/$1/initrd.lrp

#sign the remaining files and move the gpg-signed version to *.lrp
for i in $(ls $PROGPATH/package/$1/*.lrp)
[ $i = $PROGPATH/package/$1/initrd.lrp ] && continue
gpgv --keyring ~/.gnupg/LEAF_sigkeys.gpg --quiet $i > /dev/null 2>&1 &&
echo signing package $i
gpg --passphrase "$PASSPHRASE" -u $USERID --sign $i
mv $i.gpg $i

rm -f $PROGPATH/package/$1/sha*sum.list
sha1sum $PROGPATH/package/$1/* > $PROGPATH/package/$1/sha1sum.list
sha512sum $PROGPATH/package/$1/* > $PROGPATH/package/$1/sha512sum.list

Create images and source tarball

Create the images:

fakeroot ./ --kernel-arch geode --image-type syslinux --variant serial
fakeroot ./ --kernel-arch i486  --image-type isolinux --variant vga
fakeroot ./ --kernel-arch i486  --image-type syslinux --variant serial
fakeroot ./ --kernel-arch i486  --image-type syslinux --variant vga
fakeroot ./ --kernel-arch i686  --image-type syslinux --variant vga
fakeroot ./ --kernel-arch i686  --image-type isolinux --variant vga

It is a good idea to finally test the newly build version with qemu:

qemu-system-i386 -enable-kvm -m 512 -cdrom image/Bering-uClibc_6.0.0-nn_i486_isolinux_vga.iso 

Create the sources tarball as required by SF policy:

cd [path to git]bering-uclibc$ 
git archive --format=tgz -9 HEAD -o [your/upload-dir]/Bering-uClibc_6.0.0-nn_src.tgz

Tag release in LEAF Bering-uClibc git repository

[path to git]/leaf/bering-uclibc# git tag -a -m "Release of LEAF Bering-uClibc 6.0.0-nn" v6.0.0-nn
[path to git]/leaf/bering-uclibc# git push origin v6.0.0-nn

Create Readme (and Announcement)

This should be obvious. Announcements are not made on a regular basis though. We do have a Changelog in this wiki, and when releasing at SF a note will be send to subscribed users if a new release is available..

Upload files to SF FRS

Login to SF FRS

Create New Folder, named with the release version.

Change to the created folder and upload Readme, the Images and the source tarball.

Commit Packages to SF SCM with

To make the release available for the upgrade utility it has finally added to the Packages repository.

Therefor copy from the directory [Packages repository]/tools to your build directory and run:

./ -p /opt/leaf/git/packages -r 6.0.0 -b /leaf/master/

The options are:

-p -- path to git Packages repository
-r -- release version
-b -- path to your build directory containing the (signed) Packages in package[toolchain]/

Finally switch to your Packages repository and push the new version:

git push origin 6.0.0


Prev Up