Re: Arch qualification for buster: call for DSA, Security, toolchain concerns

On Fri, 2018-06-29 at 11:44 +0100, Luke Kenneth Casson Leighton wrote: [...] > On Fri, Jun 29, 2018 at 10:35 AM, Adam D. Barratt > wrote: > > > >  what is the reason why that package is not moving forward? > > > > I assume you're referring to the dpkg upload t

Re: Arch qualification for buster: call for DSA, Security, toolchain concerns

On Fri, 2018-06-29 at 10:20 +0100, Luke Kenneth Casson Leighton wrote: [...] >  debian-riscv has been repeatedly asking for a single zero-impact > line > to be included in *one* file in *one* dpkg-related package which > would > allow riscv to stop being a NMU architecture and become part of >

Re: Porter roll call for Debian Stretch

On Sun, 2016-10-09 at 21:12 +0300, Adrian Bunk wrote: > [ adding debian-powerpc ] > > On Sun, Oct 09, 2016 at 06:54:44PM +0200, Moritz Mühlenhoff wrote: > > Niels Thykier schrieb: > > > If I am to support powerpc as a realease architecture for Stretch, I > > > need to know

Re: Porter roll call for Debian Stretch

On Fri, 2016-09-30 at 19:04 +, Niels Thykier wrote: > As for "porter qualification" > = > > We got burned during the Jessie release, where a person answered the > roll call for sparc and we kept sparc as a release architecture for > Jessie. However, we ended up

Re: binNMUs: please exercise some care

On 2015-10-23 11:56, Thorsten Glaser wrote: On Fri, 23 Oct 2015, Emilio Pozuelo Monfort wrote: I didn't say once per arch. I said once per package, which is worse. I normally schedule binNMUs for several dozens packages. Multiply that by several But you need to look the number up anyway?

Re: binNMUs: please exercise some care

On 2015-10-23 13:28, Thorsten Glaser wrote: [...] On Fri, 23 Oct 2015, Adam D. Barratt wrote: [...] It's also not quite that simple, even working things out by hand - see #599128 for example. Hm, I’m still under the impression that the +bN suffix to the Debian version of the package

Re: binNMUs: please exercise some care

On 2015-10-23 12:02, Thorsten Glaser wrote: On Fri, 23 Oct 2015, Adam D. Barratt wrote: wanna-build does, yes, but at least the Release Team tend to use the "wb" wrapper tool which automatically works out the next free number on each architecture. Ah, cool – so we have onl

Re: powerpc qualification for Wheezy

On Wed, 2012-05-16 at 13:19 +0100, Adam D. Barratt wrote: 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

powerpc qualification for Wheezy

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

Re: GCC-4.5 as the default for (at least some) architectures

On Wed, 2011-03-02 at 02:34 +0100, Matthias Klose wrote: I'll make gcc-4.5 the default for (at least some) architectures within the next two weeks before more transitions start. GCC-4.5 is already used as the default compiler for almost any other distribution, so there shouldn't be many

Errors starting wirless driver on 17 G4 PowerBook

The output when $ sudo ifup eth1 SIOCSIFFLAGS: No such file or directory SIOCSIFFLAGS: No such file or directory Failed to bring up eth1. It looks like in dmesg the bcm43xx is found when booting (using ubuntu on this box). However the interface is not reconized or connected to bcm43xx. [snip}

Re: Errors starting wirless driver on 17 G4 PowerBook

Adam D wrote: The output when $ sudo ifup eth1 SIOCSIFFLAGS: No such file or directory SIOCSIFFLAGS: No such file or directory Failed to bring up eth1. It looks like in dmesg the bcm43xx is found when booting (using ubuntu on this box). However the interface is not reconized

Re: Errors starting wirless driver on 17 G4 PowerBook

Sebastian Muszynski wrote: Am Samstag, 21. Oktober 2006 23:02 schrieb Adam D: [ 88.139217] bcm43xx: Error: Microcode bcm43xx_microcode5.fw not available or load failed. The trouble is that you haven't used fwcutter to extract the bcm43xx firmware of your mac osx drivers... try (apt-cache

Re: eth0: ERROR while getting interface flags: No such device

Michael Schmitz wrote: On an older 2.6.11.9 kernel I can use my eth0 port but on my newer 2.6.17.11 kernel I have not been able to use eth0 and get this error. sungem.c:v0.98 8/24/03 David S. Miller (davem@redhat.com) PHY ID: 1410cc1, addr: 0 eth0: Sun GEM (PCI) 10/100/1000BaseT Ethernet

eth0: ERROR while getting interface flags: No such device

I have had my 17PB in and out of Apple service this last month and a half and I am back installing Linux on the book. I brought over the system from my 15 TI and recompiled the kernel. On an older 2.6.11.9 kernel I can use my eth0 port but on my newer 2.6.17.11 kernel I have not been able

Re: 17 Powerbook fan turns on when starting into Ubuntu Dapper

Another question: Has people been able to get the keyboard to light up in Linux for the 17 PB? Thanks, -Adam Everything on the 17 works! except the modem. you need the pbbuttons package to fix the lightning. Børge Ok, everything is looking good with some minor diff changes in

Re: 17 Powerbook fan turns on when starting into Ubuntu Dapper

BXrge Holen wrote: On Wednesday 16 August 2006 05:31, Adam D wrote: Sven Luther wrote: On Fri, Aug 11, 2006 at 12:32:34AM +0200, Børge Holen wrote: On Friday 11 August 2006 00:17, Adam D wrote: Adam D wrote: BXrge Holen wrote: On Thursday 10 August 2006 23:53, Adam D wrote: OK, I decided

Re: 17 Powerbook fan turns on when starting into Ubuntu Dapper

Rick Thomas wrote: On Aug 15, 2006, at 11:31 PM, Adam D wrote: Every Debian install disk has graphic issues when starting into Debian. As soon as the kernel boots I get funky graphic lines that wave on the screen. I don't get any of this when using the Ubuntu install disk at all

Re: 17 Powerbook fan turns on when starting into Ubuntu Dapper

Sven Luther wrote: On Fri, Aug 11, 2006 at 12:32:34AM +0200, Børge Holen wrote: On Friday 11 August 2006 00:17, Adam D wrote: Adam D wrote: BXrge Holen wrote: On Thursday 10 August 2006 23:53, Adam D wrote: OK, I decided to just install Ubuntu on the 2nd Gen 17 powerbook with ext3

17 Powerbook fan turns on when starting into Ubuntu Dapper

OK, I decided to just install Ubuntu on the 2nd Gen 17 powerbook with ext3 as the file system and it works for now instead of booting into xfs. Upon startup and starting the network interfaces and then the portmap the fan turns on full throttle and spins for a while. It is semi loud and is

Re: 17 Powerbook fan turns on when starting into Ubuntu Dapper

BXrge Holen wrote: On Thursday 10 August 2006 23:53, Adam D wrote: OK, I decided to just install Ubuntu on the 2nd Gen 17 powerbook with ext3 as the file system and it works for now instead of booting into xfs. Upon startup and starting the network interfaces and then the portmap the fan

Re: 17 Powerbook fan turns on when starting into Ubuntu Dapper

Adam D wrote: BXrge Holen wrote: On Thursday 10 August 2006 23:53, Adam D wrote: OK, I decided to just install Ubuntu on the 2nd Gen 17 powerbook with ext3 as the file system and it works for now instead of booting into xfs. Upon startup and starting the network interfaces

Re: 17 Powerbook fan turns on when starting into Ubuntu Dapper

BXrge Holen wrote: On Friday 11 August 2006 00:17, Adam D wrote: Adam D wrote: BXrge Holen wrote: On Thursday 10 August 2006 23:53, Adam D wrote: OK, I decided to just install Ubuntu on the 2nd Gen 17 powerbook with ext3 as the file system and it works for now instead of booting into xfs

Re: 17 Powerbook fan turns on when starting into Ubuntu Dapper

Charles Plessy wrote: Le Thu, Aug 10, 2006 at 02:53:34PM -0700, Adam D a écrit : Upon startup and starting the network interfaces and then the portmap the fan turns on full throttle and spins for a while. It is semi loud and is rather annoying. Is there a way not to have the fan spin when

Re: accessing hfs journeling in 2.6.16.14 fixed?

ruben wrote: At Tue, 09 May 2006 14:26:04 +0200, Johannes Berg wrote: On Tue, 2006-05-09 at 05:18 -0700, Adam D wrote: I can mount HFSplus however... # mount -t hfsplus /dev/hda5 /mnt/x # touch test touch: cannot touch `test': Read-only file system If you'd bother to check the kernel

Re: accessing hfs journeling in 2.6.16.14 fixed?

Adam D wrote: Bernhard Reiter wrote: On Sat, May 06, 2006 at 03:59:47PM -0700, Adam D wrote: Has anyone else not been able to access HFS journaling file systems? Ever since I upgraded my kernel to 2.6.16.12 and have been able to access HFSX but lost any mounting of HFS journaling

Re: accessing hfs journeling in 2.6.16.14 fixed?

Bernhard Reiter wrote: On Sat, May 06, 2006 at 03:59:47PM -0700, Adam D wrote: Has anyone else not been able to access HFS journaling file systems? Ever since I upgraded my kernel to 2.6.16.12 and have been able to access HFSX but lost any mounting of HFS journaling. Is this fixed

accessing hfs journeling in 2.6.16.14 fixed?

Has anyone else not been able to access HFS journaling file systems? Ever since I upgraded my kernel to 2.6.16.12 and have been able to access HFSX but lost any mounting of HFS journaling. Is this fixed in 2.6.16.14? -Adam -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of

Re: Solid lockup on latest benh 2.6 kernel + PB 12

On Tue, 2004-02-17 at 05:22, Benjamin Herrenschmidt wrote: On Tue, 2004-02-17 at 12:36, David Pye wrote: Hi, I've got an Albook G4 12 powerbook (NVidia GFX) and I have been experiencing a number of hard crashes since installing the latest benh rsync'd kernel and Debian Sid (same