Re: [buildd] Action plan to get buildds getting online again
Ingo Jürgensmann dixit:
> 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?
I might be able to run an ARAnyM buildd; there used to be a few
of them, but I’d like to see the majority of buildds to run on
real iron.
> 3) What needs to be built (first)? Of course the toolchain should be
> self-hosted and we need base and related stuff.
Erm. We have that already. (Just don’t forget to add “unreleased”.)
If I could get access to wanna-build and instructions how to mark
packages for “please don’t autobuild this right now” and “that one
is fine”, that would be great.
Best thing to start is probably the boring: the 10'000 or so packages
that match lib*-perl and python-* :)
> 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
RSAv2. I think 2048 bit should be a good compromise between bearable
speed and security. Also, do have a look at SSH connection multiplexing:
http://www.stremler.net/Code/cvs_tricks/cvs-over-ssh-advanced2.html
I basically just open up a background ssh connection to all ARAnyM
boxen I run (7 right now…) and then reuse that every time, and open
an SSH background connection to where I dput things later after booting
one of them. Setup is, approximately, this (note I just keep using root
with no regular user even existing on the boxen, though I probably
shouldn’t):
root@ara4:~ # cat .dput.cf
[dpo]
fqdn = ftp.debian-ports.org
incoming = /incoming/
login = anonymous
allow_dcut = 1
method = ftp
[fw]
login = tg
fqdn = freewrt.org
method = rsync
allow_unsigned_uploads = 1
incoming = ~tg/incoming/
root@ara4:~ # cat .ssh/config
Host fw
Hostname freewrt.org
User tg
Host *
ControlPath /run/.ctl.%r@%h:%p
Then I can run
# cd /var/cache/pbuilder/result
# dput fw *.changes
And on the target system, I run debrsign, dput to dpo, and move stuff
into my archives. Were I just to upload to Debian-Ports, I could run
debrsign on the m68k boxen (the heavy work of signing is done on my
trusted BSD machine only anyway) followed by dput to dpo. I’d open an
SSH connection muxmaster to the BSD machine with the key then.
bye,
//mirabilos
--
Darwinism never[…]applied to wizardkind. There's a more than fair amount of[…]
stupidity in its gene-pool[…]never eradicated[…]magic evens the odds that way.
It's[…]harder to die for us than[…]muggles[…]wonder if, as technology[…]better
[…]same will[…]happen there too. Dursleys' continued existence indicates so.
Reply to: