[buildd] Action plan to get buildds getting online again
Hi!
I already mailed in the past weeks some sort of plan to get the buildds
working again. Then I discovered that the SSH keys of the buildds got
removed from debian-ports.org. In a short off-list discussion with
Wouter and Aurelien we came to the conclusion to take this to the list
and work out an action plan to get the buildds back online and working
again.
So, let's start with it...
1) Who will run a buildd? 24/7 operation and a good internet connection
are required (DSL or similar is quite common nowadays). Do we split
tasks between host and buildd maintainers?
2) Where will the buildds be run? Running them in the basement of your
home gives quick access, but most likely we need one or the other public
accessible machine. There's still an offer from NMMN in Hamburg to host
some machines in their office (kullervo, crest, elgar?)
3) What needs to be built (first)? Of course the toolchain should be
self-hosted and we need base and related stuff.
4) More things needed? What kind of SSH keys are nowadays en-vogue?
RSA? DSA? How will the length impact SSH performance on m68k? What is
our aim? Do we target on re-inclusion in Debian with full archive or do
it in a different way like reduced set of packages (base, required, ...)
and everything else on a best-effort basis?
5) Anything else?
--
Ciao... // Fon: 0381-2744150
. Ingo \X/ http://blog.windfluechter.net
gpg pubkey: http://www.juergensmann.de/ij_public_key.
Reply to: