On 2014-12-28 13:34, Philipp Kern wrote: > 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 With the help of Hector Oron, we have been able to setup this on the porterbox of 4 architectures: arm64, armel, armhf and mips. This has been done by allowing the d-i role account on the porterboxes. As a nice side effect, this mean that d-i people can now do/fix the setup themselves without having to go through the buildd team. The code used is available in the porterbox branch of the di-autobuild git. Note that the chroots on the porterbox are created in a very similar way than on the newer buildds (it's even done by the same script IIRC), so the problems should be similar. For example both were affected by bug#775136. > instance binNMUing the unstable d-i into experimental every day, or > similar.) BinNMUing the unstable d-i into experimental actually doesn't really work as it doesn't take into account the changes done on the debian-installer package itself. It is not uploaded that often, so it's important to have daily-builds to test it. Cheers, Aurelien -- Aurelien Jarno GPG: 4096R/1DDD8C9B aurelien@aurel32.net http://www.aurel32.net
Attachment:
signature.asc
Description: Digital signature