I need a build machine

I need a build machine to work on torouter and other packaging related thing - specifically, I require the ability to build OpenWRT related Tor packages, OpenWRT images and perhaps unrelated, I need a place to build ttdnsd for Debian and OpenWRT.

Later, I'll need a machine or a place to put these packages - I assume this means that I'll need access to the archive and package repo machine.

added component::archived/torouter owner::weasel priority::medium resolution::fixed status::closed type::defect labels

What properties does this build machine need?

Do your needs overlap with Erinn's needs for her build machine? (Perhaps they overlap with the specific VMs she is already making?)

For ttdnsd - I require a debian machine that can build packages for all of our supported platforms (debian/ubuntu); for OpenWRT, I just need a Debian machine with gcc and other libraries for building OpenWRT.

So yeah, the build machine would be a nice machine to use - it's already setup, I'd just need a shell or a shell in a VM.

I think probably Jake should get an account on dixie and be taught how to use the chroots we have their for his ttdnsd package.

For OpenWRT, I'm not sure. It sounds like it isn't very complex, so part of me wants to say another chroot on dixie is the right answer, but dixie could be easily overloaded. Since I also want/need a Linux VM for Android release builds, maybe we could combine them into a new VM, the Orbot/OpenWRT VM? I'd say running Debian, named 'oakridge'.

Just for further detail, I want a separate VM for this (not just a a new chroot) for the Android stuff because they have made it annoying/difficult/maybe impossible (without a lot of hackery) to set up their SDK without a GUI.

Ugh, have there. Need coffee.

Access to dixie is probably the right answer. For the crossbuild stuff probably a dedicated chroot.

ioerror now has access to dixie, can run sbuild to build debian packages, and has a chroot for openwrt stuff.

Trac:
Status: new to closed
Resolution: N/A to fixed

closed

mentioned in issue #6809 (closed)