Processed: These are powerpc kernel package issues.
Processing commands for [EMAIL PROTECTED]: clone 295710 -1 -2 Bug#295710: kernel-image-2.6-powerpc: please add CONFIG_BRIDGE_NF_EBTABLE Bug 295710 cloned as bugs 297833-297834. reassign 295710 kernel-patch-powerpc-2.6.8 Bug#295710: kernel-image-2.6-powerpc: please add CONFIG_BRIDGE_NF_EBTABLE Bug reassigned from package `kernel-image-2.6-powerpc' to `kernel-patch-powerpc-2.6.8'. reassign -1 kernel-patch-powerpc-2.6.9 Bug#297833: kernel-image-2.6-powerpc: please add CONFIG_BRIDGE_NF_EBTABLE Warning: Unknown package 'kernel-patch-powerpc-2.6.9' Bug reassigned from package `kernel-image-2.6-powerpc' to `kernel-patch-powerpc-2.6.9'. reassign -2 kernel-patch-powerpc-2.6.10 Bug#297834: kernel-image-2.6-powerpc: please add CONFIG_BRIDGE_NF_EBTABLE Bug reassigned from package `kernel-image-2.6-powerpc' to `kernel-patch-powerpc-2.6.10'. thanks Stopping processing here. Please contact me if you need assistance. Debian bug tracking system administrator (administrator, Debian Bugs database) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#297794: kernel-image-2.4.27-powerpc: postinst almost completely missing, breaks installer
On Wed, Mar 02, 2005 at 11:10:28PM +, Colin Watson wrote: Package: kernel-image-2.4.27-powerpc Version: 2.4.27-3 Severity: critical The complete contents of kernel-image-2.4.27-powerpc.postinst are now as follows: #!/bin/sh set -e # Automatically added by dh_installmodules if [ $1 = configure ] [ -x /sbin/update-modules ]; then update-modules /dev/null fi # End automatically added section When inserting this packages into a test image, the /vmlinux symlink is naturally never created, and the installation fails. Please fix this immediately, preferably by reverting to the previous well-tested postinst from kernel-package. Ah, and you told me you tested the package on monday :/ Oh well, fix should be incoming today. I reject the severity of critical here though, as this problem will only affect unsupported installation path (namely oldworld floppy installs with miboot, which is non-free and thus not supported, and disactivated in sarge d-i). Also, the patch you supplied is broken and untested, as it reverts an important fix in the current svn. Furthermore, since the package escaped NEW yesterday, and i will be able to upload a fixed version less than 24h of being made aware of it, i certainly reject the accusation of this problem delaying the rc3 schedule by a week, and fint it really insulting. And finally, there is *NO* need to rebuild the 2.4.27 kernel .udebs for this, as the only difference between 2.4.27-3 and 2.4.27-4 will be the addition of the post/pre/rm/inst scripts, which are removed for the udebs. This mean there is absolutely no difference in the source code used to generate those .udebs, and anyone accusing me of GPL violation because of it really has no understanding of the GPL. Really pissed by the way i am threated by the d-i and RM guys about this. Sven Luther -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Processed: Re: Bug#297882: kernel-image-2.6.10-1-686 : Unable to mount usb flash disk
Processing commands for [EMAIL PROTECTED]: reassign 297882 kernel-image-2.6.10-1-686 Bug#297882: kernel-image-2.6.10-1-686 : Unable to mount usb flash disk Warning: Unknown package 'kernel-image' Bug reassigned from package `kernel-image' to `kernel-image-2.6.10-1-686'. -- Stopping processing here. Please contact me if you need assistance. Debian bug tracking system administrator (administrator, Debian Bugs database) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#298000: kernel-image-2.6.8-2-686: airo driver fail to work with AIRONET Wireless Communications PC4800 (rev 01) [PCI 14b9:0350]
Package: kernel-image-2.6.8-2-686 Version: 2.6.8-13 Severity: important I recently tried to upgrade the kernel of one of my machines from 2.4.27 to 2.6.8. Most of the upgrade when fine, but the network card in the machine didn't work with the new kernel. The machine have several network cards, but the one in use is a WLAN card (PCI). discover recognized it and loaded the airo module for it, and the airo module recognized the card and claimed everything was just fine. These are the relevant lspci (-n) lines: :00:0e.0 Network controller: AIRONET Wireless Communications PC4800 (rev 01) :00:0e.0 0280: 14b9:0350 (rev 01) But, when dhclient tried to get an IP address, no replies from the DHCP server was detected. The stats from ifconfig reported lots of 'misc' errors on the TX line, but no pakcages transmitted. When the module was loaded, these messages were reported to syslog: kernel: PCI: Setting latency timer of device :00:0e.0 to 64 kernel: airo: cmd= 111 kernel: airo: status= 7f11 kernel: airo: Rsp0= 2 kernel: airo: Rsp1= 0 kernel: airo: Rsp2= 0 kernel: airo: Doing fast bap_reads kernel: airo: MAC enabled eth0 0:40:96:3a:64:bb kernel: airo: Finished probing for PCI adapters After trying several times to rmmod and modprobe the airo module, and running dhclient on the interface, the kernel started to send out lots of messages like this: kernel: airo: Bad size 58569 kernel: airo: Bad size 6106 kernel: airo: Bad size 26500 kernel: airo: Bad size 58570 kernel: airo: Bad size 6107 kernel: airo: Bad size 58571 kernel: airo: Bad size 58572 In between, it sent a few messages like this: kernel: airo: BAP error 4000 0 At this point, I decided to reboot back to the 2.4 kernel. How can I get the 2.6 kernel working with this PCI card? Without a working network driver for the WLAN card, I can't use the machine, so I have to stick with the 2.4 kernel for now. -- System Information: Debian Release: 3.1 APT prefers testing APT policy: (500, 'testing') Architecture: i386 (i686) Kernel: Linux 2.4.27-2-686 Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968) Versions of packages kernel-image-2.6.8-2-686 depends on: ii coreutils [fileutils] 5.2.1-2The GNU core utilities ii fileutils 5.2.1-2The GNU file management utilities ii initrd-tools 0.1.77 tools to create initrd image for p ii module-init-tools 3.2-pre1-2 tools for managing Linux kernel mo -- no debconf information -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Processed: merge bugs
Processing commands for [EMAIL PROTECTED]: reassign 297724 initrd-tools Bug#297724: kernel-image-2.6.8-10-amd64-k8 fials to install Bug reassigned from package `kernel-image-2.6.8-10-amd64-k8' to `initrd-tools'. merge 295412 297724 Bug#295412: initrd-tools: Fails to ignore 32bit emulation layer on ldd calls Bug#297724: kernel-image-2.6.8-10-amd64-k8 fials to install Bug#279382: 64-bit kernel - ldd - mkinitrd issue Bug#292080: error installing kernel-image-2.6.8-9-em64t-p4-smp Bug#295422: kernel-image-2.6.8-9-amd64-k8-smp: unable to install new kernels Merged 279382 292080 295412 295422 297724. thanks Stopping processing here. Please contact me if you need assistance. Debian bug tracking system administrator (administrator, Debian Bugs database) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Processing of kernel-patch-powerpc-2.4.27_2.4.27-4_powerpc.changes
kernel-patch-powerpc-2.4.27_2.4.27-4_powerpc.changes uploaded successfully to localhost along with the files: kernel-patch-powerpc-2.4.27_2.4.27-4.dsc kernel-patch-powerpc-2.4.27_2.4.27-4.tar.gz kernel-patch-2.4.27-apus_2.4.27-4_powerpc.deb kernel-headers-2.4.27-apus_2.4.27-4_powerpc.deb kernel-image-2.4.27-apus_2.4.27-4_powerpc.deb kernel-build-2.4.27-apus_2.4.27-4_powerpc.deb kernel-patch-2.4.27-nubus_2.4.27-4_powerpc.deb kernel-headers-2.4.27-nubus_2.4.27-4_powerpc.deb kernel-image-2.4.27-nubus_2.4.27-4_powerpc.deb kernel-build-2.4.27-nubus_2.4.27-4_powerpc.deb kernel-patch-2.4.27-powerpc_2.4.27-4_powerpc.deb kernel-headers-2.4.27-powerpc_2.4.27-4_powerpc.deb kernel-image-2.4.27-powerpc_2.4.27-4_powerpc.deb kernel-build-2.4.27-powerpc_2.4.27-4_powerpc.deb kernel-image-2.4.27-powerpc-smp_2.4.27-4_powerpc.deb kernel-build-2.4.27-powerpc-smp_2.4.27-4_powerpc.deb kernel-image-2.4.27-powerpc-small_2.4.27-4_powerpc.deb kernel-build-2.4.27-powerpc-small_2.4.27-4_powerpc.deb Greetings, Your Debian queue daemon -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#297794: marked as done (kernel-image-2.4.27-powerpc: postinst almost completely missing, breaks installer)
Your message dated Thu, 03 Mar 2005 17:02:34 -0500 with message-id [EMAIL PROTECTED] and subject line Bug#297794: fixed in kernel-patch-powerpc-2.4.27 2.4.27-4 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 now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what I am talking about this indicates a serious mail system misconfiguration somewhere. Please contact me immediately.) Debian bug tracking system administrator (administrator, Debian Bugs database) -- Received: (at submit) by bugs.debian.org; 2 Mar 2005 23:10:31 + From [EMAIL PROTECTED] Wed Mar 02 15:10:31 2005 Return-path: [EMAIL PROTECTED] Received: from chiark.greenend.org.uk [193.201.200.170] (mail) by spohr.debian.org with esmtp (Exim 3.35 1 (Debian)) id 1D6cz9-0006Az-00; Wed, 02 Mar 2005 15:10:31 -0800 Received: from [192.168.124.112] (helo=riva.lab.dotat.at) by chiark.greenend.org.uk (Debian Exim 3.35 #1) with esmtp (return-path [EMAIL PROTECTED]) id 1D6cz7-0004Tg-00 for [EMAIL PROTECTED]; Wed, 02 Mar 2005 23:10:29 + Received: from cjwatson by riva.lab.dotat.at with local (Exim 3.35 #1 (Debian)) for [EMAIL PROTECTED] id 1D6cz6-0003Dp-00; Wed, 02 Mar 2005 23:10:28 + Date: Wed, 2 Mar 2005 23:10:28 + From: Colin Watson [EMAIL PROTECTED] To: [EMAIL PROTECTED] Subject: kernel-image-2.4.27-powerpc: postinst almost completely missing, breaks installer Message-ID: [EMAIL PROTECTED] Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.3.28i X-Debbugs-CC: debian-boot@lists.debian.org Delivered-To: [EMAIL PROTECTED] X-Spam-Checker-Version: SpamAssassin 2.60-bugs.debian.org_2005_01_02 (1.212-2003-09-23-exp) on spohr.debian.org X-Spam-Status: No, hits=-11.0 required=4.0 tests=BAYES_00,HAS_PACKAGE, X_DEBBUGS_CC autolearn=ham version=2.60-bugs.debian.org_2005_01_02 X-Spam-Level: Package: kernel-image-2.4.27-powerpc Version: 2.4.27-3 Severity: critical The complete contents of kernel-image-2.4.27-powerpc.postinst are now as follows: #!/bin/sh set -e # Automatically added by dh_installmodules if [ $1 = configure ] [ -x /sbin/update-modules ]; then update-modules /dev/null fi # End automatically added section When inserting this packages into a test image, the /vmlinux symlink is naturally never created, and the installation fails. Please fix this immediately, preferably by reverting to the previous well-tested postinst from kernel-package. Thanks, -- Colin Watson [EMAIL PROTECTED] --- Received: (at 297794-close) by bugs.debian.org; 3 Mar 2005 22:08:20 + From [EMAIL PROTECTED] Thu Mar 03 14:08:20 2005 Return-path: [EMAIL PROTECTED] Received: from newraff.debian.org [208.185.25.31] (mail) by spohr.debian.org with esmtp (Exim 3.35 1 (Debian)) id 1D6yUW-0001Cm-00; Thu, 03 Mar 2005 14:08:20 -0800 Received: from katie by newraff.debian.org with local (Exim 3.35 1 (Debian)) id 1D6yOw-0002Kz-00; Thu, 03 Mar 2005 17:02:34 -0500 From: Sven Luther [EMAIL PROTECTED] To: [EMAIL PROTECTED] X-Katie: $Revision: 1.55 $ Subject: Bug#297794: fixed in kernel-patch-powerpc-2.4.27 2.4.27-4 Message-Id: [EMAIL PROTECTED] Sender: Archive Administrator [EMAIL PROTECTED] Date: Thu, 03 Mar 2005 17:02:34 -0500 Delivered-To: [EMAIL PROTECTED] X-Spam-Checker-Version: SpamAssassin 2.60-bugs.debian.org_2005_01_02 (1.212-2003-09-23-exp) on spohr.debian.org X-Spam-Status: No, hits=-6.0 required=4.0 tests=BAYES_00,HAS_BUG_NUMBER autolearn=no version=2.60-bugs.debian.org_2005_01_02 X-Spam-Level: Source: kernel-patch-powerpc-2.4.27 Source-Version: 2.4.27-4 We believe that the bug you reported is fixed in the latest version of kernel-patch-powerpc-2.4.27, which is due to be installed in the Debian FTP archive: kernel-build-2.4.27-apus_2.4.27-4_powerpc.deb to pool/main/k/kernel-patch-powerpc-2.4.27/kernel-build-2.4.27-apus_2.4.27-4_powerpc.deb kernel-build-2.4.27-nubus_2.4.27-4_powerpc.deb to pool/main/k/kernel-patch-powerpc-2.4.27/kernel-build-2.4.27-nubus_2.4.27-4_powerpc.deb kernel-build-2.4.27-powerpc-small_2.4.27-4_powerpc.deb to pool/main/k/kernel-patch-powerpc-2.4.27/kernel-build-2.4.27-powerpc-small_2.4.27-4_powerpc.deb kernel-build-2.4.27-powerpc-smp_2.4.27-4_powerpc.deb to pool/main/k/kernel-patch-powerpc-2.4.27/kernel-build-2.4.27-powerpc-smp_2.4.27-4_powerpc.deb kernel-build-2.4.27-powerpc_2.4.27-4_powerpc.deb to pool/main/k/kernel-patch-powerpc-2.4.27/kernel-build-2.4.27-powerpc_2.4.27-4_powerpc.deb kernel-headers-2.4.27-apus_2.4.27-4_powerpc.deb to pool/main/k/kernel-patch-powerpc-2.4.27/kernel-headers-2.4.27-apus_2.4.27-4_powerpc.deb
kernel-patch-powerpc-2.4.27_2.4.27-4_powerpc.changes ACCEPTED
Accepted: kernel-build-2.4.27-apus_2.4.27-4_powerpc.deb to pool/main/k/kernel-patch-powerpc-2.4.27/kernel-build-2.4.27-apus_2.4.27-4_powerpc.deb kernel-build-2.4.27-nubus_2.4.27-4_powerpc.deb to pool/main/k/kernel-patch-powerpc-2.4.27/kernel-build-2.4.27-nubus_2.4.27-4_powerpc.deb kernel-build-2.4.27-powerpc-small_2.4.27-4_powerpc.deb to pool/main/k/kernel-patch-powerpc-2.4.27/kernel-build-2.4.27-powerpc-small_2.4.27-4_powerpc.deb kernel-build-2.4.27-powerpc-smp_2.4.27-4_powerpc.deb to pool/main/k/kernel-patch-powerpc-2.4.27/kernel-build-2.4.27-powerpc-smp_2.4.27-4_powerpc.deb kernel-build-2.4.27-powerpc_2.4.27-4_powerpc.deb to pool/main/k/kernel-patch-powerpc-2.4.27/kernel-build-2.4.27-powerpc_2.4.27-4_powerpc.deb kernel-headers-2.4.27-apus_2.4.27-4_powerpc.deb to pool/main/k/kernel-patch-powerpc-2.4.27/kernel-headers-2.4.27-apus_2.4.27-4_powerpc.deb kernel-headers-2.4.27-nubus_2.4.27-4_powerpc.deb to pool/main/k/kernel-patch-powerpc-2.4.27/kernel-headers-2.4.27-nubus_2.4.27-4_powerpc.deb kernel-headers-2.4.27-powerpc_2.4.27-4_powerpc.deb to pool/main/k/kernel-patch-powerpc-2.4.27/kernel-headers-2.4.27-powerpc_2.4.27-4_powerpc.deb kernel-image-2.4.27-apus_2.4.27-4_powerpc.deb to pool/main/k/kernel-patch-powerpc-2.4.27/kernel-image-2.4.27-apus_2.4.27-4_powerpc.deb kernel-image-2.4.27-nubus_2.4.27-4_powerpc.deb to pool/main/k/kernel-patch-powerpc-2.4.27/kernel-image-2.4.27-nubus_2.4.27-4_powerpc.deb kernel-image-2.4.27-powerpc-small_2.4.27-4_powerpc.deb to pool/main/k/kernel-patch-powerpc-2.4.27/kernel-image-2.4.27-powerpc-small_2.4.27-4_powerpc.deb kernel-image-2.4.27-powerpc-smp_2.4.27-4_powerpc.deb to pool/main/k/kernel-patch-powerpc-2.4.27/kernel-image-2.4.27-powerpc-smp_2.4.27-4_powerpc.deb kernel-image-2.4.27-powerpc_2.4.27-4_powerpc.deb to pool/main/k/kernel-patch-powerpc-2.4.27/kernel-image-2.4.27-powerpc_2.4.27-4_powerpc.deb kernel-patch-2.4.27-apus_2.4.27-4_powerpc.deb to pool/main/k/kernel-patch-powerpc-2.4.27/kernel-patch-2.4.27-apus_2.4.27-4_powerpc.deb kernel-patch-2.4.27-nubus_2.4.27-4_powerpc.deb to pool/main/k/kernel-patch-powerpc-2.4.27/kernel-patch-2.4.27-nubus_2.4.27-4_powerpc.deb kernel-patch-2.4.27-powerpc_2.4.27-4_powerpc.deb to pool/main/k/kernel-patch-powerpc-2.4.27/kernel-patch-2.4.27-powerpc_2.4.27-4_powerpc.deb kernel-patch-powerpc-2.4.27_2.4.27-4.dsc to pool/main/k/kernel-patch-powerpc-2.4.27/kernel-patch-powerpc-2.4.27_2.4.27-4.dsc kernel-patch-powerpc-2.4.27_2.4.27-4.tar.gz to pool/main/k/kernel-patch-powerpc-2.4.27/kernel-patch-powerpc-2.4.27_2.4.27-4.tar.gz Announcing to debian-devel-changes@lists.debian.org Closing bugs: 297794 Thank you for your contribution to Debian. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#290398: usb_storage issue: A (not so) funny way to (or to not) delete files.
Hi, Daniele P. wrote: Subject: usb_storage issue: A (not so) funny way to (or to not) delete files. Package: kernel-image-2.6.8-1-386 Version: 2.6.8-10 Severity: grave This seems excessive to me, see below. 2) Usb storage device physically set to read only 3) Mount it as rw (mount -o rw /dev/sdc1 /media/usb), file system is vfat. 4) mv my_favorite_file /media/usb echo success success 5) And there was much rejoicing (!) All right, the correct behavior would be that the kernel warns you and then mounts the device read-only instead of rw, as the mdk kernel does. The code for doing this is set up by configuring CONFIG_USB_STORAGE_RW_DETECT before compiling the kernel. However, this code is considered experimental upstream, and has been disabled in debian in kernel-image-2.6.8-i386 version 2.6.8-4 and later, because it was believed this would help with bug #268184. In the end, it turns out that bug #268184 is caused by something else, so unless I missed some info, CONFIG_USB_STORAGE_RW_DETECT could be safely reenabled. You can check if you get the correct behavior with a kernel where CONFIG_USB_STORAGE_RW_DETECT is enabled (for example http://snapshot.debian.net/archive/2004/10/09/debian/pool/main/k/kernel-image-2.6.8-i386/kernel-image-2.6.8-1-386_2.6.8-3_i386.deb or by compiling your own). [ note for the maintainer: according to the kernel doc, hardware failing with CONFIG_USB_STORAGE_RW_DETECT should be reported to upstream ([EMAIL PROTECTED]), so that the check can be selectively disabled for them. I think they are added to the file linux/drivers/usb/storage/unusual_devs.h ] IMHO the grave severity is a bit overblown for this bug. Sure, it causes data loss, but only indirectly and through a mistake of the user. The same behavior has existed all along the 2.4 kernel series, and people live with that. Also, having to recompile the kernels at this point of time could severely hinder the release, which does not seem worth it. If you agree with this analysis, please downgrade the bug to important, and/or reassign it to kernel-image-2.6.10-1-386 so that it can be taken care of in unstable without hindering Sarge. Thanks, BC -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
