Bug#361214: RED state exception crashes on sparc64 SMP

2006-04-22 Thread Jurij Smakov
Hi Blars, According to Fabio Massimo Di Nitto, who is the Ubuntu sparc kernel maintainer, quite a lot of fixes went into the sparc64 SMP code recently, so the recent upstream snapshot is worth to try. I have built a 2.6.17-rc2 kernel from today's snapshot of Linus' git tree. It boots fine on m

Bug#364338: fix?

2006-04-22 Thread Joey Hess
I tried just removing the LD_ASSUME_KERNEL=2.4 setting from /usr/sbin/mkinitrd, and also from /usr/share/initrd-tools/scripts/e2fsprogs, which also sets it, and that seems to work ok on both 2.4 and 2.6 (generating initrd for 2.4 kernel). -- see shy jo signature.asc Description: Digital signatu

Re: uncoordinated upload

2006-04-22 Thread Frederik Schueler
Hello, On Sat, Apr 22, 2006 at 04:00:08PM -0700, Jurij Smakov wrote: > On Sun, 23 Apr 2006, Bastian Blank wrote: > >2.6.16.10 is scheduled for tomorrow. More than one upload per day is not > >good for the buildd network. > > I would say that more than one upload per *week* is too much for the >

Bug#364338: LD_ASSUME_KERNEL is broken

2006-04-22 Thread Joey Hess
retitle 364338 LD_ASSUME_KERNEL is broken tag 364338 d-i severity 364338 serious confirmed 364338 reassign 364338 initrd-tools thanks Here's a sh -x trace of mkinitrd running on a 2.4 kernel and failing: ++ LD_ASSUME_KERNEL=2.4 ++ ldd /sbin/modprobe

Processed: LD_ASSUME_KERNEL is broken

2006-04-22 Thread Debian Bug Tracking System
Processing commands for [EMAIL PROTECTED]: > retitle 364338 LD_ASSUME_KERNEL is broken Bug#364338: kernel-image-2.4.27-3-k7: Failed to create initrd image. Changed Bug title. > tag 364338 d-i Bug#364338: LD_ASSUME_KERNEL is broken There were no tags set. Tags added: d-i > severity 364338 serious

Re: uncoordinated upload

2006-04-22 Thread Jurij Smakov
On Sun, 23 Apr 2006, Bastian Blank wrote: 2.6.16.10 is scheduled for tomorrow. More than one upload per day is not good for the buildd network. I would say that more than one upload per *week* is too much for the buildds, especially now, when stable releases often consist of a single few-lin

Re: uncoordinated upload

2006-04-22 Thread Norbert Tretkowski
* Bastian Blank wrote: > On Sat, Apr 22, 2006 at 11:53:36PM +0200, Norbert Tretkowski wrote: > > I can't remember notices before 2.6.16-8 and 2.6.16-9 were > > uploaded. > > There was. Where? > > 2.6.16-8 broke alpha builds, because 2.6.16.6 is buggy. I just > > wanted to fix it. > > 2.6.16.10

Re: uncoordinated upload

2006-04-22 Thread Bastian Blank
On Sat, Apr 22, 2006 at 11:53:36PM +0200, Norbert Tretkowski wrote: > * Bastian Blank wrote: > > Don't upload 2.6.16-10 without any notice. > I can't remember notices before 2.6.16-8 and 2.6.16-9 were uploaded. There was. > 2.6.16-8 broke alpha builds, because 2.6.16.6 is buggy. I just wanted > t

Bug#364353: marked as done (linux-image-2.6.15-1-k7: Fails to mount root file system)

2006-04-22 Thread Debian Bug Tracking System
Your message dated Sat, 22 Apr 2006 23:50:13 +0200 with message-id <[EMAIL PROTECTED]> and subject line Bug#364353: linux-image-2.6.15-1-k7: Fails to mount root file system has caused the attached Bug report to be marked as done. This means that you claim that the problem has been dealt with. If

Re: uncoordinated upload

2006-04-22 Thread Norbert Tretkowski
* Bastian Blank wrote: > Don't upload 2.6.16-10 without any notice. I can't remember notices before 2.6.16-8 and 2.6.16-9 were uploaded. 2.6.16-8 broke alpha builds, because 2.6.16.6 is buggy. I just wanted to fix it. Norbert -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with

Bug#364353: linux-image-2.6.15-1-k7: Fails to mount root file system

2006-04-22 Thread Claus Christensen
Package: linux-image-2.6.15-1-k7 Version: 2.6.15-7bpo1 Severity: critical Justification: breaks the whole system It says "Waiting for root file system" and then it stalls. -- System Information: Debian Release: 3.1 Architecture: i386 (i686) Kernel: Linux 2.6.8-3-k7 Locale: LANG=en_DK, LC_CTYPE=e

Bug#364338: kernel-image-2.4.27-3-k7: Failed to create initrd image.

2006-04-22 Thread Shaun Jackman
Package: kernel-image-2.4.27-3-k7 Version: 2.4.27-10sarge2 Severity: normal Unpacking kernel-image-2.4.27-3-k7 (from .../kernel-image-2.4.27-3-k7_2.4.27-10sarge2_i386.deb) ... Selecting previously deselected package kernel-image-2.4-k7. Unpacking kernel-image-2.4-k7 (from .../kernel-image-2.4-k7

Processed: Re: Bug#364277: linux-image-2.6.12-1-k7: snd_via82xx unresolve symbol

2006-04-22 Thread Debian Bug Tracking System
Processing commands for [EMAIL PROTECTED]: > reassign 364277 linux-2.6 Bug#364277: linux-image-2.6.12-1-k7: snd_via82xx unresolve symbol Warning: Unknown package 'linux-image-2.6.12-1-k7' Bug reassigned from package `linux-image-2.6.12-1-k7' to `linux-2.6'. > -- Stopping processing here. Please

Re: sarge upgrade - linux, grub conflict

2006-04-22 Thread Andreas Barth
* Martin Schulze ([EMAIL PROTECTED]) [060422 11:17]: > Bastian Blank wrote: > > On Tue, Apr 18, 2006 at 05:04:53PM +0200, maximilian attems wrote: > > > waldi why not add your patch to update-grub to the next stable release? > > Please keep in mind that you can't rely on a current sarge installati

uncoordinated upload

2006-04-22 Thread Bastian Blank
Hi nobse Don't upload 2.6.16-10 without any notice. Bastian -- ... The prejudices people feel about each other disappear when they get to know each other. -- Kirk, "Elaan of Troyius", stardate 4372.5 signature.asc Description: Digital signature

Re: sarge upgrade - linux, grub conflict

2006-04-22 Thread Thiemo Seufer
Martin Schulze wrote: > Bastian Blank wrote: > > On Tue, Apr 18, 2006 at 05:04:53PM +0200, maximilian attems wrote: > > > waldi why not add your patch to update-grub to the next stable release? > > Please keep in mind that you can't rely on a current sarge installation > when it is upgraded to etc

Bug#364301: initramfs-tools: Please show what is being done on upgrades

2006-04-22 Thread Frans Pop
Package: initramfs-tools Version: 0.60 Something I find extremely annoying at the moment is that initramfs-tools is silent when it generates an initrd during upgrade of, for example, udev. What I get on e.g. my sparc is: Setting up udev (0.090-1) ... Installing new version of config file

linux-2.6_2.6.16-9_m68k.changes is NEW

2006-04-22 Thread Debian Installer
linux-headers-2.6-amiga_2.6.16-9_m68k.deb to pool/main/l/linux-2.6/linux-headers-2.6-amiga_2.6.16-9_m68k.deb linux-headers-2.6-bvme6000_2.6.16-9_m68k.deb to pool/main/l/linux-2.6/linux-headers-2.6-bvme6000_2.6.16-9_m68k.deb linux-headers-2.6-hp_2.6.16-9_m68k.deb to pool/main/l/linux-2.6/linux

Processing of linux-2.6_2.6.16-9_m68k.changes

2006-04-22 Thread Archive Administrator
linux-2.6_2.6.16-9_m68k.changes uploaded successfully to localhost along with the files: linux-headers-2.6.16-1-all_2.6.16-9_m68k.deb linux-headers-2.6.16-1-all-m68k_2.6.16-9_m68k.deb linux-headers-2.6.16-1_2.6.16-9_m68k.deb linux-image-2.6.16-1-amiga_2.6.16-9_m68k.deb linux-headers-2.6.1

Re: sarge upgrade - linux, grub conflict

2006-04-22 Thread Martin Schulze
Bastian Blank wrote: > On Tue, Apr 18, 2006 at 05:04:53PM +0200, maximilian attems wrote: > > waldi why not add your patch to update-grub to the next stable release? Please keep in mind that you can't rely on a current sarge installation when it is upgraded to etch, in other words, you can't depen