kernel-latest-2.6-i386_101_i386.changes ACCEPTED

Accepted: kernel-headers-2.6-386_101_i386.deb to pool/main/k/kernel-latest-2.6-i386/kernel-headers-2.6-386_101_i386.deb kernel-headers-2.6-686-smp_101_i386.deb to pool/main/k/kernel-latest-2.6-i386/kernel-headers-2.6-686-smp_101_i386.deb kernel-headers-2.6-686_101_i386.deb to pool/main/k/ker

Processing of kernel-latest-2.6-i386_101_i386.changes

kernel-latest-2.6-i386_101_i386.changes uploaded successfully to localhost along with the files: kernel-latest-2.6-i386_101.dsc kernel-latest-2.6-i386_101.tar.gz kernel-headers-2.6-386_101_i386.deb kernel-image-2.6-386_101_i386.deb kernel-headers-2.6-686_101_i386.deb kernel-image-2.6-68

Bug#287939: kernel-image-2.4.27-1-k7: synchronisation with a Palm on ttyS0 is broken

Package: kernel-image-2.4.27-1-k7 Version: 2.4.27-6 Severity: important Since I have install the 2.4.27 I can't synchronise my Palm IIIxe connected on ttyS0 with jpilot or pilot-xfer. The connection is established but the identification failed. If I run with the 2.4.26 there is no problem, I can

Bug#287934: kernel-image-2.6.9-9-amd64-k8: kernel: drivers/usb/input/hid-core.c: input irq status -84 received

Package: kernel-image-2.6.9-9-amd64-k8 Version: 2.6.9-4 Severity: normal the usb subsystem keepts throwing this warning, all the time I move the mouse: Dec 30 11:33:54 athlon kernel: drivers/usb/input/hid-core.c: input irq status -84 received Dec 30 11:34:21 athlon last message repeated 7 times

Bug#287933: kernel-image-2.6.8-powerpc: [prep] upping the network interface (de4x5DecChip 21140 based) freezes the kernel.

Package: kernel-image-2.6.8-powerpc Severity: important Tags: upstream As the subject says, the motorola powerstack (utah motherboard) has an onboard decchip 21140 (pci-id 1011:0009), and modprobing the de4x5 module works fine, but as soon as we access the interface, it freezes the kernel. It was

Bug#283619: marked as done (kernel-image-2.6.8-powerpc: Please rebuild against latest kernel-source 2.6.8-9)

Your message dated Fri, 31 Dec 2004 01:02:48 +0100 with message-id <[EMAIL PROTECTED]> and subject line Fixed, obviously, and even uploading 2.6.8-8 against kernel-source 2.6.8-11 :) has caused the attached Bug report to be marked as done. This means that you claim that the problem has been dealt

Processed: reassign

Processing commands for [EMAIL PROTECTED]: > reassign 272045 kernel-image-2.6.8-1-686-smp Bug#272045: kernel-image-2.6.8-1-smp: fails to build initrd Bug reassigned from package `kernel-image-2.6.8-1-smp' to `kernel-image-2.6.8-1-686-smp'. > thanks Stopping processing here. Please contact me if

kernel-patch-powerpc-2.6.8_2.6.8-8_powerpc.changes ACCEPTED

Accepted: kernel-build-2.6.8-power3-smp_2.6.8-8_powerpc.deb to pool/main/k/kernel-patch-powerpc-2.6.8/kernel-build-2.6.8-power3-smp_2.6.8-8_powerpc.deb kernel-build-2.6.8-power3_2.6.8-8_powerpc.deb to pool/main/k/kernel-patch-powerpc-2.6.8/kernel-build-2.6.8-power3_2.6.8-8_powerpc.deb kernel

Processing of kernel-patch-powerpc-2.6.8_2.6.8-8_powerpc.changes

kernel-patch-powerpc-2.6.8_2.6.8-8_powerpc.changes uploaded successfully to localhost along with the files: kernel-patch-powerpc-2.6.8_2.6.8-8.dsc kernel-patch-powerpc-2.6.8_2.6.8-8.tar.gz kernel-headers-2.6.8_2.6.8-8_powerpc.deb kernel-image-2.6.8-power3_2.6.8-8_powerpc.deb kernel-build

kernel-patch-powerpc-2.6.9_2.6.9-2_powerpc.changes UNACCEPT

Rejected: Rejected: kernel-image-power3-smp_2.6.9-2_powerpc.deb: old version (100) in unstable >= new version (2.6.9-2) targeted at unstable. Rejected: Rejected: kernel-patch-powerpc-2.6.9_2.6.9-2_all.deb: old version (2.6.9-3) in unstable >= new version (2.6.9-2) targeted at unstable. Rejected:

kernel-image-2.6.8-sparc_2.6.8-6_sparc.changes ACCEPTED

Accepted: kernel-build-2.6.8-2_2.6.8-6_sparc.deb to pool/main/k/kernel-image-2.6.8-sparc/kernel-build-2.6.8-2_2.6.8-6_sparc.deb kernel-headers-2.6.8-2-sparc32_2.6.8-6_sparc.deb to pool/main/k/kernel-image-2.6.8-sparc/kernel-headers-2.6.8-2-sparc32_2.6.8-6_sparc.deb kernel-headers-2.6.8-2-spar

kernel-image-2.4.27-i386_2.4.27-7_i386.changes ACCEPTED

Accepted: kernel-build-2.4.27-2_2.4.27-7_i386.deb to pool/main/k/kernel-image-2.4.27-i386/kernel-build-2.4.27-2_2.4.27-7_i386.deb kernel-headers-2.4.27-2-386_2.4.27-7_i386.deb to pool/main/k/kernel-image-2.4.27-i386/kernel-headers-2.4.27-2-386_2.4.27-7_i386.deb kernel-headers-2.4.27-2-586tsc

kernel-image-2.6.9-i386_2.6.9-4_i386.changes ACCEPTED

Accepted: kernel-headers-2.6.9-2-386_2.6.9-4_i386.deb to pool/main/k/kernel-image-2.6.9-i386/kernel-headers-2.6.9-2-386_2.6.9-4_i386.deb kernel-headers-2.6.9-2-686-smp_2.6.9-4_i386.deb to pool/main/k/kernel-image-2.6.9-i386/kernel-headers-2.6.9-2-686-smp_2.6.9-4_i386.deb kernel-headers-2.6.9

kernel-image-2.6.8-i386_2.6.8-11_i386.changes ACCEPTED

Accepted: kernel-headers-2.6.8-2-386_2.6.8-11_i386.deb to pool/main/k/kernel-image-2.6.8-i386/kernel-headers-2.6.8-2-386_2.6.8-11_i386.deb kernel-headers-2.6.8-2-686-smp_2.6.8-11_i386.deb to pool/main/k/kernel-image-2.6.8-i386/kernel-headers-2.6.8-2-686-smp_2.6.8-11_i386.deb kernel-headers-2

Bug#284485: marked as done (failed loading alsa driver)

Your message dated Thu, 30 Dec 2004 14:03:58 -0500 with message-id <[EMAIL PROTECTED]> and subject line Bug#284356: fixed in kernel-image-2.4.27-i386 2.4.27-7 has caused the attached Bug report to be marked as done. This means that you claim that the problem has been dealt with. If this is not the

Bug#284463: marked as done (Alsa modules no longer load after minor kernel update)

Your message dated Thu, 30 Dec 2004 14:03:58 -0500 with message-id <[EMAIL PROTECTED]> and subject line Bug#284356: fixed in kernel-image-2.4.27-i386 2.4.27-7 has caused the attached Bug report to be marked as done. This means that you claim that the problem has been dealt with. If this is not the

Bug#284371: marked as done (kernel-image-2.4.27-1-k7: broken i2c modules)

Your message dated Thu, 30 Dec 2004 14:03:58 -0500 with message-id <[EMAIL PROTECTED]> and subject line Bug#284356: fixed in kernel-image-2.4.27-i386 2.4.27-7 has caused the attached Bug report to be marked as done. This means that you claim that the problem has been dealt with. If this is not the

Bug#284356: marked as done (incompatability with modules from -2 version of same package)

Your message dated Thu, 30 Dec 2004 14:03:58 -0500 with message-id <[EMAIL PROTECTED]> and subject line Bug#284356: fixed in kernel-image-2.4.27-i386 2.4.27-7 has caused the attached Bug report to be marked as done. This means that you claim that the problem has been dealt with. If this is not the

Bug#284253: marked as done (debian-installer: [netboot-x86] there is a module versioning issue in 2.6 and 2.4 netboot images.)

Your message dated Thu, 30 Dec 2004 14:03:58 -0500 with message-id <[EMAIL PROTECTED]> and subject line Bug#284356: fixed in kernel-image-2.4.27-i386 2.4.27-7 has caused the attached Bug report to be marked as done. This means that you claim that the problem has been dealt with. If this is not the

Bug#286444: marked as done (kernel-source-2.4.27: Version symbols mismatch with kernel-image-2.4.27-1-686-smp)

Your message dated Thu, 30 Dec 2004 14:03:58 -0500 with message-id <[EMAIL PROTECTED]> and subject line Bug#284356: fixed in kernel-image-2.4.27-i386 2.4.27-7 has caused the attached Bug report to be marked as done. This means that you claim that the problem has been dealt with. If this is not the

Bug#284138: marked as done (kernel-image-2.6.9-1-686: "Pentium 4", not "Pentium IV")

Your message dated Thu, 30 Dec 2004 14:06:48 -0500 with message-id <[EMAIL PROTECTED]> and subject line Bug#284138: fixed in kernel-image-2.6.8-i386 2.6.8-11 has caused the attached Bug report to be marked as done. This means that you claim that the problem has been dealt with. If this is not the

Bug#284181: marked as done (alsa-modules-2.4.27-1-686: plenty of unresolved symbols)

Your message dated Thu, 30 Dec 2004 14:03:58 -0500 with message-id <[EMAIL PROTECTED]> and subject line Bug#284356: fixed in kernel-image-2.4.27-i386 2.4.27-7 has caused the attached Bug report to be marked as done. This means that you claim that the problem has been dealt with. If this is not the

Bug#284683: marked as done (alsa-modules-2.4.27-1-k7: Unresolved symbols)

Your message dated Thu, 30 Dec 2004 14:03:58 -0500 with message-id <[EMAIL PROTECTED]> and subject line Bug#284356: fixed in kernel-image-2.4.27-i386 2.4.27-7 has caused the attached Bug report to be marked as done. This means that you claim that the problem has been dealt with. If this is not the

Bug#287153: marked as done (depmod: *** Unresolved symbols)

Your message dated Thu, 30 Dec 2004 14:03:58 -0500 with message-id <[EMAIL PROTECTED]> and subject line Bug#284356: fixed in kernel-image-2.4.27-i386 2.4.27-7 has caused the attached Bug report to be marked as done. This means that you claim that the problem has been dealt with. If this is not the

Bug#285847: marked as done (kernel-headers-2.6.8-1-sparc64: not usable for building modules)

Your message dated Thu, 30 Dec 2004 14:06:36 -0500 with message-id <[EMAIL PROTECTED]> and subject line Bug#285847: fixed in kernel-image-2.6.8-sparc 2.6.8-6 has caused the attached Bug report to be marked as done. This means that you claim that the problem has been dealt with. If this is not the

Bug#283619: Should be retitled to request build against kernel-source-2.6.8 -11?

Hi, Bug # 283619 (severity "grave" and tagged "security") requests a rebuild of powerpc 2.6.8 kernel images against kernel-source 2.6.8-9. But the changelog for the latest version of kernel-image-2.6.8-powerpc, version 2.6.8-7, says it was rebuilt against kernel-source 2.6.8-10. Shouldn't this b

Bug#285301: marked as done (initrd-tools: typo in mkinitrd)

Your message dated Thu, 30 Dec 2004 12:47:05 -0500 with message-id <[EMAIL PROTECTED]> and subject line Bug#285301: fixed in initrd-tools 0.1.76 has caused the attached Bug report to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is no

Bug#247054: marked as done (initrd-tools: Support for initrd booting encrypted root filesystems)

Your message dated Thu, 30 Dec 2004 12:47:05 -0500 with message-id <[EMAIL PROTECTED]> and subject line Bug#247054: fixed in initrd-tools 0.1.76 has caused the attached Bug report to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is no

initrd-tools_0.1.76_i386.changes ACCEPTED

Accepted: initrd-tools_0.1.76.dsc to pool/main/i/initrd-tools/initrd-tools_0.1.76.dsc initrd-tools_0.1.76.tar.gz to pool/main/i/initrd-tools/initrd-tools_0.1.76.tar.gz initrd-tools_0.1.76_all.deb to pool/main/i/initrd-tools/initrd-tools_0.1.76_all.deb Announcing to debian-devel-changes@lists

Processing of initrd-tools_0.1.76_i386.changes

initrd-tools_0.1.76_i386.changes uploaded successfully to localhost along with the files: initrd-tools_0.1.76.dsc initrd-tools_0.1.76.tar.gz initrd-tools_0.1.76_all.deb Greetings, Your Debian queue daemon

Bug#284952: Confirming this and raising severity

severity 284952 grave thanks Hi, I can confirm this bug. Note that things are fine after the USB key is unmounted but before it is physically unplugged. The freeze happens the moment it is physically removed. This is with kernel-image-2.6.9-powerpc version 2.6.9-3, udev 0.050-2, hal 0.4.2-5, ho

Processed: Confirming this and raising severity

Processing commands for [EMAIL PROTECTED]: > severity 284952 grave Bug#284952: kernel-image-2.6.9-powerpc: freeze when unplugging USB storage Severity set to `grave'. > thanks Stopping processing here. Please contact me if you need assistance. Debian bug tracking system administrator (administr

Bug#287867: kernel-image-2.6.9-powerpc: Console mouse cursor (with gpm) behaves oddly in 2.6.9

Package: kernel-image-2.6.9-powerpc Version: 2.6.9-3 Severity: normal Hello, I just tried upgrading from kernel 2.6.8 to 2.6.9, and found a strange behavior in the gpm cursor. The cursor is now invisible, and when moving it around the console, all text it passes over disappears (turns black, lik

kernel-image-2.4.27-i386_2.4.27-7_i386.changes is NEW

(new) kernel-build-2.4.27-2_2.4.27-7_i386.deb optional devel Headers for building modules for Linux 2.4.27 This package provides kernel header files for building modules for the precompiled kernel images on i386. (new) kernel-headers-2.4.27-2-386_2.4.27-7_i386.deb optional devel Linux 2.4.27 kern

Processing of kernel-image-2.4.27-i386_2.4.27-7_i386.changes

kernel-image-2.4.27-i386_2.4.27-7_i386.changes uploaded successfully to localhost along with the files: kernel-image-2.4.27-i386_2.4.27-7.dsc kernel-image-2.4.27-i386_2.4.27-7.tar.gz kernel-headers-2.4.27-2_2.4.27-7_i386.deb kernel-pcmcia-modules-2.4.27-2-586tsc_2.4.27-7_i386.deb kernel-

kernel-source-2.4.27_2.4.27-7_i386.changes ACCEPTED

Accepted: kernel-doc-2.4.27_2.4.27-7_all.deb to pool/main/k/kernel-source-2.4.27/kernel-doc-2.4.27_2.4.27-7_all.deb kernel-patch-debian-2.4.27_2.4.27-7_all.deb to pool/main/k/kernel-source-2.4.27/kernel-patch-debian-2.4.27_2.4.27-7_all.deb kernel-source-2.4.27_2.4.27-7.diff.gz to pool/main/

Bug#268450: marked as done (ld-linux.so.2 is mapped too low in memory causing intermittent ldd failures on sparc64)

Your message dated Thu, 30 Dec 2004 05:32:28 -0500 with message-id <[EMAIL PROTECTED]> and subject line Bug#268450: fixed in kernel-source-2.4.27 2.4.27-7 has caused the attached Bug report to be marked as done. This means that you claim that the problem has been dealt with. If this is not the cas

Bug#286226: marked as done (Compiler errors with new 2.4.27-6 (-5 works))

Your message dated Thu, 30 Dec 2004 05:32:28 -0500 with message-id <[EMAIL PROTECTED]> and subject line Bug#286226: fixed in kernel-source-2.4.27 2.4.27-7 has caused the attached Bug report to be marked as done. This means that you claim that the problem has been dealt with. If this is not the cas

Processing of kernel-source-2.4.27_2.4.27-7_i386.changes

kernel-source-2.4.27_2.4.27-7_i386.changes uploaded successfully to localhost along with the files: kernel-source-2.4.27_2.4.27-7.dsc kernel-source-2.4.27_2.4.27-7.diff.gz kernel-patch-debian-2.4.27_2.4.27-7_all.deb kernel-doc-2.4.27_2.4.27-7_all.deb kernel-source-2.4.27_2.4.27-7_all.deb

Bug#284356: SONAME bumping and d-i

On Wed, Dec 22, 2004 at 10:39:57PM +0900, Horms wrote: > Hi, > > I have put together the packages that I would like to upload as > kernel-source-2.4.27 2.4.27-7 and kernel-image-2.4.27-i386 2.4.27-7. > > This includes increasing the SONAME to 2. > Could anyone who is interesetd please take a look

Re: Installing on a Dual CPU G5 Powermac?

> > Nope, the kernel in d-i does not boot this G5. John Koskie indicated > > (in this thread) that he has seen the same problem with newer G5 > > hardware (him and Paddy de Burca report having used d-i on similar, > > somewhat older G5 machines with sucess though). > > Well, the real problem is tha

Re: 2.4.27-7?

On Tue, Dec 28, 2004 at 01:08:01PM -0800, Joshua Kwan wrote: > Guys, > > Are we ready for 2.4.27-7? sparc kernel images are waiting on it (#268450.) Hi Josh, I am going to tag and upload now. -- Horms