Re: armel qualification for Wheezy

2012-05-16 Thread Adam D. Barratt
On Thu, 2012-05-17 at 00:59 +0100, peter green wrote: > The statement that all but one armel buildd is at the same location disagrees > with > the debian machines database. [...] > Metropolitan Area Network Darmstadt : arcadelt > DG-i: argento They may still be physically located there, but: wan

Re: Disable loading ipv6 on wheezy NSLU2 - resolved

2012-05-16 Thread Alan Snelgrove
I found the answers here http://wiki.debian.org/KernelModuleBlacklisting and https://wiki.archlinux.org/index.php/Blacklisting#Blacklisting When /etc/modprobe.d/ipv6.conf contains 'install ipv6 /bin/false' ipv6 is successfully not loaded. The problem I had with flash-kernel returning code 1 whe

Re: armel qualification for Wheezy

2012-05-16 Thread peter green
Comments on / additions and corrections to the content of http://release.debian.org/wheezy/arch_qualify.html would be appreciated, as would any other information you think is relevant to helping us determine armel's status for the release. The statement that all but one armel buildd is at the

Re: Disable loading ipv6 on wheezy NSLU2

2012-05-16 Thread Alan Snelgrove
On 15 May 2012, at 22:00, Alan Snelgrove wrote: > > On 15 May 2012, at 21:10, John Winters wrote: > >> On 15/05/12 18:46, Alan Snelgrove wrote: >> [snip] >>> I have read that adding ipv6.disable=1 to the kernel >>> line in the bootloader configuration fixes the problem. >>> >>> But I don't kno

Re: armel *and* armhf qualification for Wheezy

2012-05-16 Thread Mike Hommey
On Wed, May 16, 2012 at 04:56:39PM +0100, Steve McIntyre wrote: > On Wed, May 16, 2012 at 05:44:10PM +0200, Mike Hommey wrote: > >Hi Steve, > > Hey Mike, > > >On Wed, May 16, 2012 at 04:26:10PM +0100, Steve McIntyre wrote: > >> In terms of raw buildd CPU right now, I think we're doing OK, but > >

Re: armel *and* armhf qualification for Wheezy

2012-05-16 Thread Steve McIntyre
On Wed, May 16, 2012 at 05:44:10PM +0200, Mike Hommey wrote: >Hi Steve, Hey Mike, >On Wed, May 16, 2012 at 04:26:10PM +0100, Steve McIntyre wrote: >> In terms of raw buildd CPU right now, I think we're doing OK, but >> memory is more of a limiting factor with bigger C++ builds. > >As maintainer o

Re: armel *and* armhf qualification for Wheezy

2012-05-16 Thread Mike Hommey
Hi Steve, On Wed, May 16, 2012 at 04:26:10PM +0100, Steve McIntyre wrote: > In terms of raw buildd CPU right now, I think we're doing OK, but > memory is more of a limiting factor with bigger C++ builds. As maintainer of such a package that pushes buildds limits, I have a question. Isn't memory r

Re: armel *and* armhf qualification for Wheezy

2012-05-16 Thread Steve McIntyre
[ Responding for both armel and armhf ] On Wed, May 16, 2012 at 01:19:46PM +0100, Adam Barratt wrote: >Hi, > >With the sound of the ever approaching freeze ringing loudly in our ears, >we're (somewhat belatedly) looking at finalising the list of release >architectures for the Wheezy release. > >Co

armhf qualification for Wheezy

2012-05-16 Thread Adam D. Barratt
Hi, With the sound of the ever approaching freeze ringing loudly in our ears, we're (somewhat belatedly) looking at finalising the list of release architectures for the Wheezy release. Comments on / additions and corrections to the content of http://release.debian.org/wheezy/arch_qualify.html wou

armel qualification for Wheezy

2012-05-16 Thread Adam D. Barratt
Hi, With the sound of the ever approaching freeze ringing loudly in our ears, we're (somewhat belatedly) looking at finalising the list of release architectures for the Wheezy release. Comments on / additions and corrections to the content of http://release.debian.org/wheezy/arch_qualify.html wou