Broadcast? Mention in the irc/matrix room. Maybe Twitter, email.
Building a package for a new release
Assuming we have just released 3.3, the following instructions will merge that
code into the upstream branch (which is used to create the Debian diff) and
then merged again in the debian branch (where the Debian code lives). We then
use git-buildpackage to build the package and tag it, then push those changes
back in the repository.
cd provisiongit pull# if you previously ran release.sh, run:git reset --hard 7.x-3.4# otherwise run this next line:dch -v 3.3 -D unstable new upstream releasegit-buildpackage -email@example.com aegir ../build-area/aegir3-provision_3.3_i386.changes
Note: Version numbers are slightly different in Debian - we use the "magic"
~ separator to indicate that 3.0~alpha2 is actually lower than 3.0...
Packages are initially uploaded to the unstable repository for initial
test builds. The idea is that this final package can be moved to testing for
broader testing, using the command:
Sometimes you want to have a test package for a given branch without going
through a full release. This can be done by pushing the feature branch to GitLab.
You can then download the packages as build artefacts.
To develop third party extensions to Aegir on Debian, it is recommended to
install the Debian packages. If you are working on Aegir core, this could be a
bit trickier since the files are not where you expect them to be and are not
deployed as git repositories however.
You can, however, copy in place a .git directory using the following:
This will bring back a bunch of files that are removed from the Debian package,
so it will yield warnings on uninstall of the Debian package but it should
You can do something similar with the frontend.
The stable repository should contain the latest release. The testing repository
will also contain the latest release (unless we're in the process of building a
release) but could have fixes to the Debian package that are being tested. The
unstable repository is automatically built from the stable branch and may be
To see what changes are done to the Debian package, see the
which is maintained on the debian
To see which version of the package is currently available in the repository,
you will unfortunately need to parse
the Packages file for
Replacing an expired key
gpg --gen-keygpg --list-keysgpg --keyserver pgp.mit.edu --send-keys <key id>sudo -u reprepro -igpg --search-keys <key id>gpg --fingerprint firstname.lastname@example.org ; gpg --check-sigs email@example.com # check if this is the real keyecho allow * by key <key id> >> /srv/reprepro/conf/uploaders
reprepro@zeus:~$ gpg --edit-key 3376CCF9gpg> expireChanging expiration time for the primary key.Please specify how long the key should be valid. 0 = key does not expire <n> = key expires in n days <n>w = key expires in n weeks <n>m = key expires in n months <n>y = key expires in n yearsKey is valid for? (0) 3yKey expires at Sat 12 Oct 2019 09:12:54 AM EDTIs this correct? (y/N) ygpg> savegpg --armor --export 3376CCF9 > key.asc