Rough Guide to doing Stable Point Releases in Debian
----------------------------------------------------
-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
-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)
-o Update version number in README, README.html and dists/README
-o Update the 'Debian<n>.<n>r<n>' symlink in dists/
-o Clean up dists/stable/ChangeLog (add header, basically)
-o Update fields in suite table in postgresql (see below)
-
-o Run 'dak dominate --force -s stable'
-o Run 'dak generate-filelist -s stable'
-o Run apt-ftparchive generate apt.conf.stable
-o Run 'dak generate-releases --force-touch --apt-conf apt.conf.stable stable'
-
-
-
-
+- 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 <propups.unstable
+cp /srv/release.debian.org/www/${suitename}/${newrev%%.*}/${newrev}/propups.testing .
+dak control-suite --force --add testing <propups.testing
+
+- ask rms if they have RMs to do.
+# dak rm -s ${suite} -R -p -d ### -m '###' ###
+- Copy in entries from /srv/ftp.debian.org/web/removals.txt:
+# $EDITOR ${ftpdir}/dists/${suite}/ChangeLog
+
+- and then check if they have a d-i update. if so, bash:
+diver=20130613+deb7u3+b1
+dak copy-installer -s ${pusuite} -d ${suite} ${diver}
+
+# set dioldver to "empty" if there is no old to remove
+dioldver=20130613+deb7u3
+if [ "${dioldver}" != "empty" ]; then
+ cd $ftpdir/dists/${suite}/main
+ for iarch in $(dak admin s-a list-arch ${suite}); do
+ if [ -d "installer-${iarch}/${dioldver}" ]; then
+ echo "Moving installer-${iarch}/${dioldver} to morgue"
+ mkdir -p "${base}/morgue/d-i/installer-${iarch}/"
+ mv "installer-${iarch}/${dioldver}" "${base}/morgue/d-i/installer-${iarch}/"
+ fi
+ done
+
+ # Remove old version also from proposed-updates
+ cd $ftpdir/dists/${pusuite}/main
+ for iarch in $(dak admin s-a list-arch ${suite}); do
+ rm -rf -- "installer-${iarch}/${dioldver}"
+ done
+fi
+cd $ftpdir/dists/${suite}
+
+- Updates for win32-loader?
+cd ${ftpdir}/tools/win32-loader
+if [ -d ${suitename}-proposed-updates ]; then
+ rm -r ${suite}
+ mv ${suitename}-proposed-updates ${suite}
+fi
+cd ${ftpdir}
+
+- Update version number in README, README.html and dists/README,
+ Clean up dists/stable/ChangeLog (add header, basically). bash:
+
+cd ${ftpdir}/dists/${suite}
+
+date_long=$(date "+%A, %-dth %B %Y" | sed 's/1th/1st/; s/2th/2nd/; s/3th/3rd/')
+date_iso=$(date "+%Y-%m-%d")
+date_short=$(date "+%a, %d %b %Y")
+sed -e "1i======================================\n${date_short} - Debian ${newrev} released\n======================================" -i ChangeLog
+sed -e "/^${suite}/ s/Debian ${oldrev}/Debian ${newrev}/" -i ../README
+sed -e "s/Debian ${oldrev}/Debian ${newrev}/g; /Debian ${newrev}/ s/released .*\\./released ${date_long}./" -i ../../README
+sed -e "s/Debian ${oldrev}/Debian ${newrev}/g; /Debian ${newrev}/ s/released .*\\./released ${date_long}./; /meta name=\"Modified\"/ s/content=\".*\"/content=\"${date_iso}\"/" -i ../../README.html
+
+# Inspect changes. Regular expressions might be a bit fragile.
+for f in README README.html dists/README dists/${suite}/ChangeLog; do
+ diff -u ${mirrordir}/ftp-master/${f} ${ftpdir}/${f}
+done
+
+# If changes are needed:
+cd ${ftpdir}/dists/${suite}
+$EDITOR ChangeLog ../README ../../README ../../README.html
+rm -f -- ./*~ ../*~ ../../*~
+
+- Update the 'Debian<n>.<n>r<n>' 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 <<EOF
begin;
-update suite set version = '5.0.6' where suite_name = 'stable';
-update suite set description = 'Debian 5.0.6 Released 04 September 2010' 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 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<n>.<n>r<n>' 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.
+update suite set version = '${newrev}' where suite_name = '${suite}';
+update suite set description = 'Debian ${newrev} Released ${mdate}' where suite_name = '${suite}';
+commit;
+EOF
+
+- prepare for gps. bash:
+dak dominate --force -s ${suite}
+- check output from cruft report:
+dak cruft-report -s ${suite}
+- if cruft was removed: go back to run dominate again
+
+- if cruft was removed: update changelog from /srv/ftp.debian.org/web/removals.txt:
+# $EDITOR ${ftpdir}/dists/${suite}/ChangeLog
+
+- Let SRM see if all is ok
+
+- then:
+dak generate-packages-sources2 --force -s ${suite},${pusuite} && dak contents generate -f -s ${suite} -a ftp-master
+
+- For wheezy: update main/i18n/Index
+if [[ ${suitename} == wheezy ]]; then
+ ${scriptsdir}/generate-i18n-Index "${ftpdir}/dists/${suite}"
+fi
+
+- Generate Releases:
+dak generate-releases -f -s ${suite} ${pusuite}
+# Remove InRelease: Release can be signed by both ftpmaster & stable release keys
+rm ${ftpdir}/dists/${suite}/InRelease
+
+- have the SRMs sign it and put the signature in.
+cd ${ftpdir}/dists/${suite}
+cat /srv/release.debian.org/www/${suitename}/${newrev%%.*}/${newrev}/Release-${newrev}.gpg >> 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
projects / dak.git / blobdiff