#debuild.me

  Wish I was at DebConf, have a great DC, everyone!

Hey y'all, As some may have seen, I've taken a shine to a project called [Firehose](https://github.com/fedora-static-analysis/firehose), and plan on helping this format support Debian. I really enjoy how it's looking so far, and plan on slowly building out scripts to output this format. The idea here is I'd use it to help with [debuild.me](http://debuild.me/), and eventually support larger archive runs. More to come.

It's working! (ish) Here are some snapshots (and fully automated as much as I could) This comprises a lot of work, so I'm fairly proud of it.     Feel free to browse over at [debuild.me](http://debuild.me/). Patches & feedback welcome!

I've been working (although; slowly) on dput-ng. I need to finish `dirt` (a tool to modify the config files, sorta like how `git` works at times), but it's otherwise mostly in the state it will be in upon our upload to unstable. good-intentioned co-maintainers and contributors are welcome. Code's in collab-maint, be sure to run big changes through us over in `#torabora` on `irc.oftc.net`. I've also spent some time on [debuild.me](http://debuild.me/), and I've written out most of the krufty bits, more changes to come. If anyone has ARM hardware suggestions, I'm open to them, but I'm thinking (from some `debian-arm` advice) that it'd be best to wait for the v8 goodies to drop. Godspeed!

Two bits here - debuild.me --------- I've started working on a site to host my build stuff, and i've called it debuild.me  None of it's active, and I'm going to be slowly using it more as it becomes more, well, implemented. atlantic, etc ------------- I've been working (mostly quietly) on a cut down buildd, to test packages I intend to sponsor over a couple of different conditions. I'm going to run deep source checks, build the package a few different ways, check the basics (lintian, piuparts, etc) and lots of other stuff I might think is a good idea while doing it. At it's core, it doens't use buildd nodes like the archive, rather, it uses aws. When I dput a package, it spins up at least one AWS instance, based on an AMI I set up (and update frequently), and builds on that. This means -- yes! -- No queues! :) It also means I need careful oversight of the nodes, and pay attention to not running up a big bill. It should also be noted, this is not for uploading a built package to the archive, this is for testing packages before uploading them to the archive. Ideas / patches welcome