X-Git-Url: https://git.decadent.org.uk/gitweb/?a=blobdiff_plain;f=docs%2FREADME.stable-point-release;h=e395adf9ccb028373936743b890e0fabfde599fd;hb=6b166bcde615272deee920b1ca0f24ec32e9f720;hp=2b82733034916881caf808e7895e6c81a7f4b559;hpb=99c872bc2990bb43daf30a12bffc23f6dfb074f9;p=dak.git

diff --git a/docs/README.stable-point-release b/docs/README.stable-point-release
index 2b827330..e395adf9 100644
--- a/docs/README.stable-point-release
+++ b/docs/README.stable-point-release
@@ -6,8 +6,8 @@ Rough Guide to doing Stable Point Releases in Debian
 suite=stable
 suitename=wheezy
 pusuite=proposed-updates
-oldrev=7.2
-newrev=7.3
+oldrev=7.6
+newrev=7.7
 export SCRIPTVARS=/srv/ftp-master.debian.org/dak/config/debian/vars
 . $SCRIPTVARS
 . "${configdir}/common"
@@ -37,19 +37,23 @@ cd ${ftpdir}/dists/${pusuite}
 mv -t "${pumorguedir}" -n -- *.changes
 
 - -r0 additions?
-  For example new d-i.
+  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:
-like, cat /srv/release.debian.org/www/squeeze/6.0/6.0.4/propup.unstable | dak control-suite --add unstable
-Note: unstable first, then testing
+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.
-- check output from cruft report:
-dak cruft-report -s ${suite}
 - and then check if they have a d-i update. if so, bash:
 # set dioldver to "empty" if there is no old to remove
-diver=20130613+deb7u1+b1
+diver=20130613+deb7u2+b3
 dak copy-installer -s ${pusuite} -d ${suite} ${diver}
-dioldver=20130613+deb7u1
+dioldver=20130613+deb7u2+b1
 cd $ftpdir/dists/${suite}/main
 if [ "${dioldver}" != "empty" ]; then
     for iarch in $(dak admin s-a list-arch ${suite}); do
@@ -64,9 +68,9 @@ cd $ftpdir/dists/${suite}
 
 - Updates for win32-loader?
 cd ${ftpdir}/tools/win32-loader
-if [ -d ${suitename}-proposed-updates ]; then
+if [ -d ${suite}-proposed-updates ]; then
     rm -r ${suite}
-    mv ${suitename}-proposed-updates ${suite}
+    mv ${suite}-proposed-updates ${suite}
 fi
 cd ${ftpdir}
 
@@ -93,6 +97,9 @@ EOF
 
 - prepare for gps. bash:
 dak dominate --force -s ${suite}
+- check output from cruft report:
+dak cruft-report -s ${suite}
+
 dak generate-filelist -s ${suite}
 
 - Let SRM see if all is ok
@@ -127,6 +134,10 @@ 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: