On Thu, Sep 11, 2014 at 10:49:06PM +0200, Aurelien Jarno wrote: > If we choose this solution, here is a quick and dirty patch against > di-autobuild to do that. It's basically changing the hardcoded paths > and call to schroot. There is probably more fixes/cleanup to do, but > it's just a proof of concept to show this solution works without > additional privilege on the porterboxes. Note that I haven't tried the > upload part, but I guess it's just a matter of having the right packages > installed (if not already the case). > > We probably want to have a dedicated d-i account for that on the > porterbox. Also we have only one amd64/i386 porterbox, and the current > script doesn't support that, but that should be easy to test. > > If this solution is chosen, I'll be happy to continue working on this > script as time permits.
I'm ok with this approach for the time being. Obviously building on real infrastructure the way other stuff is built would be even better. (For instance binNMUing the unstable d-i into experimental every day, or similar.) Kind regards Philipp Kern
signature.asc
Description: Digital signature
