X-Git-Url: https://git.decadent.org.uk/gitweb/?a=blobdiff_plain;f=docs%2FREADME.stable-point-release;h=304795f1cd890312e493134072318bf9fff39d05;hb=4f3c7874fd19d380b106a9d4bbab0403ed089359;hp=176b33eb89d9c2aa3317ed9ad71639b7a847b4f7;hpb=16f731a893f0ba036a995c25b8b5f3490394070e;p=dak.git diff --git a/docs/README.stable-point-release b/docs/README.stable-point-release index 176b33eb..304795f1 100644 --- a/docs/README.stable-point-release +++ b/docs/README.stable-point-release @@ -1,52 +1,180 @@ Rough Guide to doing Stable Point Releases in Debian ---------------------------------------------------- -o run 'dak clean-proposed-updates' to get rid of obsolete .changes - from p-u ['dak clean-proposed-updates *.changes' from within p-u] -o [also check for obsolete .changes caused by 'dak rm'-ing from p-u] -o Update dak.conf (at least the section for Reject-Proposed-Updates, - before using 'dak reject-proposed-updates') -o Install, reject and remove packages as directed by the SRM using - 'dak process-accepted' (installs), 'dak reject-proposed-updates' - (rejects) and 'dak rm' (removals) - - NB: removing packages are not logged to the stable ChangeLog; you - need to do that byhand. - -o If you installed a debian-installer upload; migrate the relevant - installer-*/$release directory from proposed-updates to stable. - (Including potentially removing older versions) - -o Decruft stable in coordination with SRMs - -o Do anything in proposed-updates/TODO -o Close any applicable stable bugs - (hint: http://bugs.debian.org/cgi-bin/pkgreport.cgi?pkg=ftp.debian.org&include=etch) -o Update version number in README, README.html and dists/README -o Update the 'Debian.r' symlink in dists/ -o Clean up dists/stable/ChangeLog (add header, basically) -o Update version fields in dak.conf -o Update fields in suite table in postgresql (see below) - -o Run 'dak make-suite-file-list --force -s stable' -o Run apt-ftparchive generate apt.conf.stable -o Run 'dak generate-releases --force-touch --apt-conf apt.conf.stable stable' - -[Yes, this sucks and more of it should be automated. c.f. ~ajt/pointupdate] - -####################################################### - -update suite set version = '4.0r3' where suite_name = 'stable'; -update suite set description = 'Debian 4.0r3 Released 16th February 2008' where suite_name = 'stable'; - -Rough Guide to doing Old-Stable Point Releases in Debian --------------------------------------------------------- - -Pretty much as above, except that process-accepted doesn't know about -oldstable, so you have to do some surgery on it first to make it -support that. Probably want to disable cron.daily whilst doing so. -Also watch out for the installing_to_stable detection which doesn't -work well with the current layout of oldstable-proposed-updates (as a -symlink to $distro-proposed-updates). clean-proposed-updates, -cruft-report and most everything else support a -s/--suite so they -sould be fine to use. +- sudo to dak +- bash: +suitename=wheezy +newrev=7.10 + +export SCRIPTVARS=/srv/ftp-master.debian.org/dak/config/debian/vars +. $SCRIPTVARS +. "${configdir}/common" +. "${configdir}/dinstall.functions" +umask 022 +export LANG=C +export LC_ALL=C + +suite=$(psql -qAtc "SELECT suite_name FROM suite WHERE codename='${suitename}'") +oldrev=$(psql -qAtc "SELECT version FROM suite WHERE codename='${suitename}'") +case "${suite}" in + stable) pusuite=proposed-updates ;; + oldstable) pusuite=oldstable-proposed-updates ;; + *) pusuite=INVALID ;; +esac + +echo "Point release for ${suite} (${suitename}); old version: ${oldrev}, new: ${newrev}" +echo "Updates come from ${pusuite}" + +pg_timestamp pre_${suite}_${newrev} +cd ~ +mkdir -p ${suitename}_${newrev} +cd ${suitename}_${newrev} +dak control-suite -l ${pusuite} > ${pusuite}.list +dak control-suite -l ${suite} > ${suite}.list + +- ask SRMs if there is anything to be skipped from this release. If so + edit ${pusuite}.list (and later the Changelog too) +- bash: +# skip: list of *source* packages to skip, whitespace seperated +skip="" +if [ -n "${skip}" ]; then + mv ${pusuite}.list ${pusuite}.list.ori + grep -vFf <(dak ls -f heidi -S -s ${pusuite} ${skip}) ${pusuite}.list.ori > ${pusuite}.list +fi + +dak make-changelog -s ${pusuite} -b ${suite} | cat - ${ftpdir}/dists/${suite}/ChangeLog | sponge ${ftpdir}/dists/${suite}/ChangeLog +if [ -n "${skip}" ]; then + $EDITOR ${ftpdir}/dists/${suite}/ChangeLog +fi + +dak control-suite --add ${suite} < ${pusuite}.list +dak control-suite --remove ${pusuite} < ${pusuite}.list + +- clean up *.changes from proposed-updates: +# Be careful if uploads were not included in the point release. +pumorguedir="${base}/morgue/queues/$(date +%Y/%m)" +mkdir -p "${pumorguedir}" +cd ${ftpdir}/dists/${pusuite} +mv -t "${pumorguedir}" -n -- *.changes + +- -r0 additions? + For example new d-i. If so: +cd ~/${suitename}_${newrev} +cp /srv/release.debian.org/www/${suitename}/${newrev%%.*}/${newrev}/${suitename}-r0-additions.cs . +dak control-suite --add ${suitename}-r0 < ${suitename}-r0-additions.cs + +- sync with stable RM if there is any propup needed. do it, if so: +cp /srv/release.debian.org/www/${suitename}/${newrev%%.*}/${newrev}/propups.unstable . +dak control-suite --force --add unstable .r' symlink in dists/ +cd $ftpdir/dists/ +rm -f Debian${oldrev} +ln -s ${suitename} Debian${newrev} + +- Update fields in suite table in postgresql. + bash: + +mdate=$(date +"%d %B %Y") +psql projectb <> Release.gpg +gpg --no-default-keyring --keyring /usr/share/keyrings/debian-archive-keyring.gpg --trust-model=always --verify Release.gpg Release + +- Check if a mirror push is needed or next dinstall is enough. for a push +o if so, bash: +cd +${configdir}/cronscript mirror