Rough Guide to doing Stable Point Releases in Debian ---------------------------------------------------- - sudo to dak - bash: suite=stable suitename=wheezy pusuite=proposed-updates oldrev=7.6 newrev=7.7 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 pg_timestamp pre_${suite}_${newrev} cd ~ mkdir -p ${suite}_${newrev} cd ${suite}_${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: dak make-changelog -s ${pusuite} -b ${suite} | cat - ${ftpdir}/dists/${suite}/ChangeLog | sponge ${ftpdir}/dists/${suite}/ChangeLog 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 ~/${suite}_${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 <> Contents-${carch}.new; gzip -9v Contents-${carch}.new; mv Contents-${carch}.new.gz Contents-${carch}.gz; done rm {main,contrib,non-free}/Contents-* fi - 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} 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.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: 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 &