X-Git-Url: https://git.decadent.org.uk/gitweb/?a=blobdiff_plain;f=docs%2FREADME.stable-point-release;h=26384d148cc95841de07c977a6dfcfd619b8fb24;hb=1b9be6a7800899a1ecadd8a0170015c954e2c3ce;hp=eb1116a977b588e09db53cdb702a99495781a083;hpb=e38ec49727ef15c6dcad16f7ebdb56e8e254d568;p=dak.git diff --git a/docs/README.stable-point-release b/docs/README.stable-point-release index eb1116a9..26384d14 100644 --- a/docs/README.stable-point-release +++ b/docs/README.stable-point-release @@ -1,30 +1,101 @@ Rough Guide to doing Stable Point Releases in Debian ---------------------------------------------------- -o Install, reject and remove packages as directed by the SRM +o Dump projectb for backup purposes. +o get everything listed, dak control-suite -l proposed-updates > p-u.list +o generate the changelog using dak make-changelog -s proposed-updates -b stable | cat - ${ftpdir}/dists/stable/ChangeLog | sponge ${ftpdir}/dists/stable/ChangeLog +o add everything to stable: cat p-u.list |dak control-suite --add stable +o remove everything from proposed-updates, dak control-suite -r proposed-updates < p-u.list +o sync with stable RM if there is any propup needed. do it, if so. +o ask rms if they have RMs to do. +o If you installed a debian-installer upload; migrate the relevant + installer-*/$release directory from proposed-updates to stable. + (Including potentially removing older versions) + dak copy-installer helps +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 fields in suite table in postgresql (see below) + +o dak dominate --force -s stable +o dak generate-filelist -s stable +o Let SRM see if all is ok +o dak generate-packages-sources -s stable ; dak contents generate -f -s stable +o dak generate-releases -f -s stable +o Check if a mirror push is needed or next dinstall is enough. for a push +o if so: + TRACEFILE="${ftpdir}/project/trace/ftp-master.debian.org" + DATE_SERIAL=$(date +"%Y%m%d01") + FILESOAPLUS1=$(awk '/serial/ { print $3+1 }' ${TRACEFILE} ) + if [ "$DATE_SERIAL" -gt "$FILESOAPLUS1" ]; then + SERIAL="$DATE_SERIAL" + else + SERIAL="$FILESOAPLUS1" + fi + date -u > ${TRACEFILE} + echo "Using dak v1" >> ${TRACEFILE} + echo "Running on host: $(hostname -f)" >> ${TRACEFILE} + echo "Archive serial: ${SERIAL}" >> ${TRACEFILE} + cd ${mirrordir} + rsync -aH --link-dest ${ftpdir} --delete --delete-after --ignore-errors ${ftpdir}/. . + + date -u > /srv/ftp.debian.org/web/mirrorstart + echo "Using dak v1" >> /srv/ftp.debian.org/web/mirrorstart + echo "Running on host $(hostname -f)" >> /srv/ftp.debian.org/web/mirrorstart + sudo -H -u archvsync /home/archvsync/runmirrors > ~dak/runmirrors.log 2>&1 & + + +begin; +update suite set version = '6.0.2' where suite_name = 'stable'; +update suite set description = 'Debian 6.0.2 Released 25 June 2011' where suite_name = 'stable'; + +------------------------------------------------------------------------ +Old doc: + + +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 Decruft stable in coordination with SRMs + o Do anything in proposed-updates/TODO -o Close any applicable potato bugs (hint: http://bugs.debian.org/cgi-bin/pkgreport.cgi?pkg=ftp.debian.org&include=potato) -o Update README and dists/README +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 Comment out "Untouchable" in katie.conf[-non-US] -o Run 'jenna -s' -o Run apt-ftparchive generate apt.conf.stable[-non-US] -o Uncomment "Untouchable" in katie.conf[-non-US] -o Update version fields in katie.conf[-non-US] -o Update fields in suite table in postgresql -o Copy tree/directory for stable to apt.conf[-non-US], run ziyi, remove it from apt.conf[-non-US] - -Yes, this sucks and more of it should be automated. - -update suite set version = '2.2r5' where id = 2; -update suite set version = '2.2r6' where id = 3; -update suite set version = '3.0-testing' where id = 4; -update suite set version = '3.0' where id = 5; -update suite set version = '3.0-testing-updates' where id = 6; -update suite set description = 'Debian 2.2r5 Released 10th January 2002' where id = 2; -update suite set description = 'Proposed Updates for Debian 2.2r5 - Not Released' where id = 3; -update suite set description = 'Debian 3.0 Testing distribution - Not Released' where id = 4; -update suite set description = 'Debian 3.0 Unstable - Not Released' where id = 5; -update suite set description = 'Debian 3.0 Testing distribution updates - Not Released' where id = 6; +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.