Re: restricted sourceless ARM uploads

2007-01-29 Thread K. Richard Pixley
I know I'm late to the party, but one big win about qemu build servers is that they can be instantly cloned, replicated, and shared. We can't do that with real hardware. --rich -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]

Re: restricted sourceless ARM uploads

2006-12-23 Thread Wookey
On 2006-12-20 19:58 +0100, Bill Allombert wrote: On Wed, Dec 20, 2006 at 12:32:25PM -0600, Bill Gatliff wrote: Could you try those packages on hedges? (You can get developer access from Wookey if you need it). Hedges has 512MB real and 1.5GB swap. And unlike leisner, the netwinders,

Re: restricted sourceless ARM uploads

2006-12-21 Thread Kevin Mark
On Wed, Dec 20, 2006 at 06:40:06PM +0100, Aurelien Jarno wrote: Wookey a écrit : On 2006-12-20 17:39 +0100, Aurelien Jarno wrote: Hi, For those who don't know, I have setup 8 emulated ARM build daemons and started to upload packages. To know why and for more information, see [1].

Re: restricted sourceless ARM uploads

2006-12-21 Thread Wouter Verhelst
On Wed, Dec 20, 2006 at 06:50:12PM +0100, Sam Hocevar wrote: On Wed, Dec 20, 2006, Bill Gatliff wrote: For the faster arches, i.e. the ARM9 machines and above, I'm thinking that we should stick with real hardware so there's no question that the binaries will run properly. Pardon

Re: restricted sourceless ARM uploads

2006-12-21 Thread Sam Hocevar
On Thu, Dec 21, 2006, Wouter Verhelst wrote: Pardon me sir, but can that claim that binaries built on so-called real hardware will unquestionably run (as opposed to, if I understand correcly, binaries built on an emulated platform) be backed up by any facts, examples, experimentation

restricted sourceless ARM uploads

2006-12-20 Thread Aurelien Jarno
Hi, For those who don't know, I have setup 8 emulated ARM build daemons and started to upload packages. To know why and for more information, see [1]. These afternoon I saw on #debian-release: 15:52:11 aj | # unilateral action to run an emulated buildd -- all arm changes sidelined until

Re: restricted sourceless ARM uploads

2006-12-20 Thread Wookey
On 2006-12-20 17:39 +0100, Aurelien Jarno wrote: Hi, For those who don't know, I have setup 8 emulated ARM build daemons and started to upload packages. To know why and for more information, see [1]. Very impressive piece of work aurelien! We ought to discuss if there is any significant

Re: restricted sourceless ARM uploads

2006-12-20 Thread Aurelien Jarno
Wookey a écrit : On 2006-12-20 17:39 +0100, Aurelien Jarno wrote: Hi, For those who don't know, I have setup 8 emulated ARM build daemons and started to upload packages. To know why and for more information, see [1]. Very impressive piece of work aurelien! We ought to discuss if there is

Re: restricted sourceless ARM uploads

2006-12-20 Thread Bill Gatliff
Wookey wrote: On 2006-12-20 17:39 +0100, Aurelien Jarno wrote: Hi, For those who don't know, I have setup 8 emulated ARM build daemons and started to upload packages. To know why and for more information, see [1]. Very impressive piece of work aurelien! We ought to discuss if there

Re: restricted sourceless ARM uploads

2006-12-20 Thread Aurelien Jarno
Wookey a écrit : On 2006-12-20 17:39 +0100, Aurelien Jarno wrote: Hi, For those who don't know, I have setup 8 emulated ARM build daemons and started to upload packages. To know why and for more information, see [1]. Very impressive piece of work aurelien! We ought to discuss if there is

Re: restricted sourceless ARM uploads

2006-12-20 Thread Bill Allombert
On Wed, Dec 20, 2006 at 05:05:21PM +, Wookey wrote: On 2006-12-20 17:39 +0100, Aurelien Jarno wrote: Hi, For those who don't know, I have setup 8 emulated ARM build daemons and started to upload packages. To know why and for more information, see [1]. Very impressive piece of

Re: restricted sourceless ARM uploads

2006-12-20 Thread Sam Hocevar
On Wed, Dec 20, 2006, Bill Gatliff wrote: For the faster arches, i.e. the ARM9 machines and above, I'm thinking that we should stick with real hardware so there's no question that the binaries will run properly. Pardon me sir, but can that claim that binaries built on so-called real

Re: restricted sourceless ARM uploads

2006-12-20 Thread Aurelien Jarno
Aurelien Jarno a écrit : * Packages that failed to build because the build daemon netwinder is fucked for weeks wrt to /usr/lib/libtasn1.so.3.0.6 cpufire-applet_1.2-2 gnome-session_2.14.3-4 The situation is actually worse than what I expected. This build daemon seems to loose files

Re: restricted sourceless ARM uploads

2006-12-20 Thread Bill Gatliff
Bill: A very basic reason is that some packages require 1GB of RAM to build in finite time and there are no arm and m68k buildd with that amount of RAM. Could you try those packages on hedges? (You can get developer access from Wookey if you need it). Hedges has 512MB real and 1.5GB

Re: restricted sourceless ARM uploads

2006-12-20 Thread Bill Allombert
On Wed, Dec 20, 2006 at 12:32:25PM -0600, Bill Gatliff wrote: Could you try those packages on hedges? (You can get developer access from Wookey if you need it). Hedges has 512MB real and 1.5GB swap. And unlike leisner, the netwinders, or nslu2s, it's expandable if needed. No use, this

Re: restricted sourceless ARM uploads

2006-12-20 Thread Mirco Bauer
Hi Aurelien, I can give some details about the Mono related packages that failed to build before but worked for you. I reply inline. On Wed, 2006-12-20 at 17:39 +0100, Aurelien Jarno wrote: * Packages that now build fine: blam_1.8.3-2 (for 40 days) blam failed because of a runtime bug

Re: restricted sourceless ARM uploads

2006-12-20 Thread Aurelien Jarno
Mirco Bauer a écrit : Hi Aurelien, I can give some details about the Mono related packages that failed to build before but worked for you. I reply inline. On Wed, 2006-12-20 at 17:39 +0100, Aurelien Jarno wrote: * Packages that now build fine: blam_1.8.3-2 (for 40 days) Oops, there

Re: restricted sourceless ARM uploads

2006-12-20 Thread Russ Allbery
Aurelien Jarno [EMAIL PROTECTED] writes: * Also those package (and they are plenty others), could be tagged not-for-us. This would spare some build daemon time, and would ease to see which packages have really failed to build or not. [...] openafs_1.4.2-4 As the OpenAFS co-maintainer,