The Debian stretch release implicitly inflicts some mandatary (new
apt keys!) as well as some minor recommended housekeeping on an
existing mini-buildd installation.
So this is what I would recommend you to do -- assuming a basic
setup, near to what the wizards would set up automatically.
Given how the configuration currently works (i.e., affecting
dependencies when you change things), you might want
- to stop the daemon before starting your housekeeping
- and try to get all your changes done in one flow (to minimize the costly "PCA action" on repos and chroots later...)
1.0.30 adds wizard-support for new sources now available (like
buster, stretch-backports, jessie-backports-sloppy, and also the new
Ubuntu release). Obviously not mandatory, but it will really helps in
Please check the home page overview if that version
is available for the system your mini-buildd runs on.
With 1.0.30 installed, run (in the admin configuration):
- Sources:Archives Debian wizard: Will get you deb.debian.org (you may want to remove httpredir.debian.org).
- Sources:Sources Debian wizard: Will get you new sources for buster, stretch-backports and jessie-backports-sloppy.
- Sources:Priority sources Extras wizard: Adds new prio sources stretch-backports and jessie-backports-sloppy.
You will need these two additional keys after stretch=stable:
"CBF8D6FD518E17E1": Jessie Stable Release Key <firstname.lastname@example.org>
"EF0F382A1A7B6500": Debian Stable Release Key (9/stretch) <email@example.com>
Add these keys to the AptKeys instances if they are not already there, verify and make them shiny green.
Then, add these two keys to the stretch Source.
See: https://ftp-master.debian.org/keys.html, debian-archive-keyring package, apt-key.
Stretch's release version (as configured in the stretch Source)
should currently be "STRETCH" or "~STRETCH". Now with stretch
released, this must be replaced by the actual release version.
FWIW: This default scheme will put you in the position to distinguish
between packages build while stretch was rolling, and after stretch
was released, just via the package version -- hinting you on what
packages you might want/need to rebuild on the actual finsihed stable
To do this, just go the the stretch Source instance, reveal the "Extra" section, and either
- Recommended: Override with "90" or remove the override string (this let's mbd guess on check, which will lead to "90" for 1.0.x).
- Override with "9" (this is the new scheme also adapted by Debian backports now, and default in upcoming release 1.2.x of mini-buildd).
Note that using "9" may lead to dist-upgrade issues for packages
from, for example, a jessie distribution using "80" -- for packages
with otherwise the very same versioning. So only use that if you
(understand this and) are up to instruct your repo users on remedies,
or if you are using the new scheme consistently already anyway.
Be sure to have the new buster Source activated (PCA):
- Run Repositories:Distributions:Default wizard, which should give you the new Distribution for buster.
- Add the new buster Distribution to the resp. repositories.
- Run Chroots:Default wizard (on the backend you are using). Thus should give new buster chroots.
... now that you are at it anyway :).
mini-buildd always keeps the base chroots up to date, so this is
actually not strictly really necessary. However ;), as a safeguard
against any possible evilry that might have crept into your existing
base chroots, you might want to do this; there are no drawbacks, it
just take some time.
Just Remove the chroots you want to recreate, and then run PCA on it again.
Be sure everything you want is finally "green" in the admin config
overview (merciless run "PCA" on everything that's not ;).
Then, don't forget to restart the Daemon once (either by clicking an
stop/start as admin in the web app) or just by just restarting the
# service mini-buildd restart
-- else you might experience subtle misbehaviours ;).
In case you have mutiple instances, you unfortunately need to do these
manual updates (or at least parts of it) on each of these.
In case you created new Distributions, you should build new keyring
packages (and migrate the new packages up to stable, at least for