On Tue, Oct 13, 2009 at 02:22:28AM +0200, Wesley W. Terpstra wrote: > * Do the autobuilders build packages uploaded as experimental? (eg: to > confirm a successful port) Yes, it works just like unstable but without the propogation and associated headaches. > * Is making an unstable upload really as easy as setting the changes file to > experimental? Yup. > * Can a package uploaded to experimental be migrated to unstable? > * I definitely don't want this happen automatically > * At some point I probably want to push the newest versions from > experimental to unstable (to facilitate building the new architectures) and > then upload a new 'final' version that gets autobuilt for all the new > targets, landing in unstable. When you upload to unstable with a higher version number, the experimental package is removed. The unstable version propogates normally. [1] > Finally, how can I determine which debian autobuilders have >1GB of RAM > (required for a successful build). The full list of machinery is [2]. 1: http://www.debian.org/doc/developers-reference/resources.html#s4.6.4 2: http://db.debian.org/machines.cgi -- Jonathan Wiltshire 1024D: 0xDB800B52 / 4216 F01F DCA9 21AC F3D3 A903 CA6B EA3E DB80 0B52 4096R: 0xD3524C51 / 0A55 B7C5 1223 3942 86EC 74C3 5394 479D D352 4C51
Attachment:
signature.asc
Description: Digital signature