From 3f0f4919052c294f54c77ba50398461b89014770 Mon Sep 17 00:00:00 2001 From: Daniel Kahn Gillmor Date: Tue, 2 Sep 2008 12:24:50 -0400 Subject: [PATCH] documented APT archive management practices. --- repo/publish | 2 +- website/archive-key.mdwn | 27 ++++++++++++++++++++++++++- 2 files changed, 27 insertions(+), 2 deletions(-) diff --git a/repo/publish b/repo/publish index b7269c9..f12ae9f 100755 --- 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 6aa71f3..3fb5a6c 100644 --- 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 -- 2.26.2