m68k not a release arch for etch; status in testing, future plans?

2006-09-17 Thread Steve Langasek
Hi folks, It's with some regret that I have to confirm that m68k is not going to be a release architecture for etch. I don't expect that this comes as any great surprise; m68k's shortfalls with regards to the release standards have been documented for some time, and in spite of what I know has be

bytal

2006-09-17 Thread John
Would you want:Want nice rolexes whackhumeanbilly.com -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Re: gcc status

2006-09-17 Thread Roman Zippel
Hi, On Fri, 8 Sep 2006, Wouter Verhelst wrote: > grmbl, build failed with corrupt files, and dmesg shows bad blocks on > the disk. I'll need to either replace it, or start doing some fsck; both > will take some time. > > If anyone else feels like taking this on, be my guest I just submitted a p

Re: linux-image-2.6-17-mac tries

2006-09-17 Thread Brad Boyer
On Fri, Sep 15, 2006 at 09:32:00AM +1000, Finn Thain wrote: > On Thu, 14 Sep 2006, Brian Morris wrote: > > i have been trying the 2.6.17 kernel on my old lcIII/performa450 > > (68030 no FPU). > ... > > block_queue_max_hardware_segments:set to minimum 1 > > (repeated 10x -between around scsci device

m68k syscalls for xserver-xorg-input-evdev

2006-09-17 Thread Drew Parsons
xserver-xorg-input-evdev 1.1.2 currently fails to build on m68k (cf. http://buildd.debian.org/fetch.php?&pkg=xserver-xorg-input-evdev&ver=1% 3A1.1.2-1&arch=m68k&stamp=1151064364&file=log&as=raw) This is because a new file inotify-syscalls.h has been added which defines syscalls for each specific a

[D-I] mass kernel udeb update and preparations for RC1

2006-09-17 Thread Frans Pop
(Reply-to set to debian-boot; please only add relevant port if needed.) Dear (d-i) porters, First mass upload of kernel udebs = Today I have uploaded kernel udeb updates to 2.6.17-9 _for all arches_. This is the first time using the 'massbuild' [1] script I wrote r