checking a keyserver should warn at level INFO, since it is a potential information...

[monkeysphere.git] / website / archive-key.mdwn

diff --git a/website/archive-key.mdwn b/website/archive-key.mdwn
index 6aa71f30b3a45a19e03837e1e284654b92ccbce4..898c7e56ad433dd8bb113e9cd10dfae9185980dc 100644 (file)
--- a/website/archive-key.mdwn
+++ b/website/archive-key.mdwn
@@ -1,5 +1,6 @@
 [[meta title="Monkeysphere archive signing key"]]
 [[!template id="nav"]]
+[[toc ]]
 
 ## Verifying the key ##
 
@@ -83,4 +84,30 @@ 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 binary package built from a separate architecture
+`$NEWARCH` that you want to include with the archive, 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