The Debian jessie release implicitly inflicts some mandatary (new apt keys!) as well as some recommended (jessie! stretch! backports-sloppy!) housekeeping on an existing mini-buildd installation.
So this is what I would recommend you to do:
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.6 adds wizard-support for new sources now available (like stretch, jessie-backports, wheezy-backports-sloppy, and also the new Ubuntu release). Obviously not mandatory, but it will really help you housekeeping.
Note that for both wheezy and jessie, you will find packages in the Hellfield Archive in the resp. stable suite immediately. "Official" Debian backports will follow after it hits testing (i.e., via jessie-backports and wheezy-backports-sloppy).
There are two new keys that you need now:
- 7638D0442B90D010 New Jessie Archive Key - CBF8D6FD518E17E1 New Jessie Stable Key
Add these keys to the AptKeys instances if they are not already there, verify and make them shiny green.
See: https://ftp-master.debian.org/keys.html, debian-archive-keyring package, apt-key.
Now, go to the Sources instances, and update these exiting sources:
- jessie: Add 7638D0442B90D010 and CBF8D6FD518E17E1
- wheezy: Add 7638D0442B90D010
- sid: Add 7638D0442B90D010
- wheezy-backports: Add 7638D0442B90D010
Afaik, these are all old sources which "broke" (i.e., the check on the sources fails now, and will inactivate the source eventually) with the new keys introduced on repos with the jessie release.
Jessie's release version (as configured in the jessie Source) should currently be "JESSIE" or "~JESSIE". Now with jessie 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 jessie was rolling, and after jessie was released, just via the package version -- hinting you on what packages you might want/need to rebuild on the actual finsihed stable release.
Do do this, just go the the jessie Source instance, reveal the "Extra" section, and either
- Recommended: Override with "80" or remove the override string (this let's mbd guess on check, which will lead to "80" for 1.0.x).
- Override with "8" (this is the new scheme also adapted by Debian backports now).
Note that using "8" may lead to dist-upgrade issues for packages from, for example, a wheezy distribution using "70" -- 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.
This is default when jessie is created now by the wizards, so this is recommended.
mini-buildd always keeps the base chroots up to date, so this is actually not really necessary (what's more, if you followed this guide, you should have been forced to re-build them anyway, having changed the jessie source).
However ;) , as a safeguard against any evilry while jessie was rolling that might have influenced yor current base chroot, you might consider to rebuild them once now.
If so, just use the "Priority Sources: Extras" wizard to add the source, and then add that to the wheezy Distribution.