[6242] in Release_7.7_team
Installers merged (and apt repository merger thoughts)
daemon@ATHENA.MIT.EDU (Tim Abbott)
Sat Feb 28 21:33:09 2009
Date: Sat, 28 Feb 2009 21:32:12 -0500 (EST)
From: Tim Abbott <tabbott@MIT.EDU>
To: athena10@mit.edu
cc: release-team@mit.edu
Message-ID: <alpine.DEB.2.00.0902281837380.1796@vinegar-pot.mit.edu>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
X-Spam-Flag: NO
X-Spam-Score: 0.00
Hello,
I've now merged added the functionality of the current Debathena installer
to the Athena 10 installer to my satisfation. I changed several
references to "Athena 10" to "Debathena" in the text since it is my
understanding that is our current plan, but probably more adjustments of
the text will be desireable.
I set the stated documentation site from athena10.mit.edu to
http://debathena.mit.edu/beta, which we'll need to eventually update. I
made the "error" function not include "exit 1" so that one can easily
print more than one line of error output. I also fixed some whitespace
errors and use of echo instead of output (etc.).
I dropped the auto-compile openafs modules feature, and opted instead for
printing instructions. We may want to revisit this in the future, but
because maintaining openafs modules requires running "m-a a-i openafs"
occasionally, I think that we should avoid have them do it manually the
first time and thus have them have an idea of what is going on when AFS
fails the next time they upgrade their kernel.
A couple of differences remain between what is in svn and what is deployed
on debathena.mit.edu:
- s/athena10.mit.edu/debathena.mit.edu/. This should be easy to change
at our leisure once the apt repositories themselves are merged.
- s/beta//. This is easy to change once we move the website updates to
the main debathena.mit.edu location (if that is indeed our plan).
- The initial signing keys (and filenames, and their sha1sums) are
different.
My current theory for this is that we should take the
debathena-archive-keyring.asc file that I generated with both the
Debathena and Athena 10 keys in it and use it for this purpose. I've
placed a copy of this file in /mit/debathena/apt so that the only change
we would need to make to switch to it for Debathena's installer is
updating the installer script itself.
I've also packaged this file for distribution in the
debathena-archive-keyring package, so that users who previously installed
Debathena or Athena 10 will eventually upgrade to have the keyring package
installed. This will be useful for when we eventually want to stop using
one of the two keys. It will probably also be useful for the purpose
Debian uses the debian-archive-keyring package for, namely, being able to
rotate our crypto keys every once in a while.
In the shorter term, geofft is working on a patch to reprepro that allows
it to support signing an apt repository with two different keys. We would
thus have our repository signed with both the Debathena and Athena 10
signing keys for a transitional period, at the expense of having to
maintain a patched reprepro on our upload server. This approach might be
the most expedient way to merge our apt repository URIs without causing
people to get "unsigned repository" errors.
-Tim Abbott
