documented APT archive management practices.

diff --git a/repo/publish b/repo/publish
index b7269c99c227bc2eb9db4db024fa2ef55beb0138..f12ae9f04ee07a00f8517ea96a99239ce1565db3 100755 (executable)
--- a/repo/publish
+++ b/repo/publish
@@ -2,4 +2,4 @@
 
 # simple reminder script to publish the repository to the usual spot:
 
-rsync -avz --delete dists pool root@george.riseup.net:/srv/apt/
+rsync -avz --delete dists pool archivemaster@george.riseup.net:/srv/apt/

diff --git a/website/archive-key.mdwn b/website/archive-key.mdwn
index 6aa71f30b3a45a19e03837e1e284654b92ccbce4..3fb5a6ce6d273829d78dcbb94b32d38adaaf9cb3 100644 (file)
--- a/website/archive-key.mdwn
+++ b/website/archive-key.mdwn
@@ -83,4 +83,29 @@ the future.
 
 In the event of a new archive maintainer, the entire archive will be
 rebuilt from signed tags in [the monkeysphere git
-repository](/community), rather than trying to piece together 
+repository](/community), rather than trying to re-verify the entire
+old archive.
+
+## Maintaining the archive ##
+
+To create a new archive including a single monkeysphere package from
+tag `$TAG` on architecture `$ARCH`, do:
+
+       git clone git://git.monkeysphere.info/monkeysphere
+       cd monkeysphere
+       git tag -v $TAG
+       git checkout $TAG
+       debuild -uc -us
+       cd repo
+       reprepro -C monkeysphere include experimental ../$TAG_$ARCH.changes
+
+When you get a package from a separate architecture `$NEWARCH`, do:
+
+       cd repo
+       reprepro -C monkeysphere includedeb experimental ../$TAG_NEWARCH.deb
+
+To publish the archive, make sure you have access to
+`archivemaster@george.riseup.net`, and then do:
+
+       cd repo
+       ./publish