Bug#498143: Please detect non-ISO block devices masquerading as Debian CDs
tags 498143 pending thanks On Tuesday 25 August 2009, Chris Lamb wrote: > To frame my thoughts here, this is to support d-i when invoked from > Debian Live USB sticks - as Debian Live knows the target media when > building the USB image, "try-usb=true" is appended to all generated > "usb with d-i" images. Hmmm. If that is really the only use case then maybe that should just be documented in the changelog and in comments in appropriate places. If it is not actually useful for regular users, then it should of course _not_ be documented in the installation guide. I was missing that context. Thanks for adding that. So I've dropped the documentation patch and committed the others, with a few cosmetic changes. Cheers, FJP -- To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Processed: Re: Bug#498143: Please detect non-ISO block devices masquerading as Debian CDs
Processing commands for cont...@bugs.debian.org: > tags 498143 pending Bug #498143 [cdrom-detect] Please detect non-ISO block devices masquerading as Debian CDs Added tag(s) pending. > thanks Stopping processing here. Please contact me if you need assistance. Debian bug tracking system administrator (administrator, Debian Bugs database) -- To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Processing of linux-kernel-di-sparc-2.6_1.41lenny5_multi.changes
linux-kernel-di-sparc-2.6_1.41lenny5_multi.changes uploaded successfully to localhost along with the files: linux-kernel-di-sparc-2.6_1.41lenny5.tar.gz scsi-common-modules-2.6.26-2-sparc64-di_1.41lenny5_sparc.udeb kernel-image-2.6.26-2-sparc64-di_1.41lenny5_sparc.udeb xfs-modules-2.6.26-2-sparc64-di_1.41lenny5_sparc.udeb linux-kernel-di-sparc-2.6_1.41lenny5.dsc ppp-modules-2.6.26-2-sparc64-di_1.41lenny5_sparc.udeb multipath-modules-2.6.26-2-sparc64-di_1.41lenny5_sparc.udeb nic-modules-2.6.26-2-sparc64-di_1.41lenny5_sparc.udeb fat-modules-2.6.26-2-sparc64-di_1.41lenny5_sparc.udeb plip-modules-2.6.26-2-sparc64-di_1.41lenny5_sparc.udeb ide-modules-2.6.26-2-sparc64-di_1.41lenny5_sparc.udeb crypto-dm-modules-2.6.26-2-sparc64-di_1.41lenny5_sparc.udeb sata-modules-2.6.26-2-sparc64-di_1.41lenny5_sparc.udeb crypto-modules-2.6.26-2-sparc64-di_1.41lenny5_sparc.udeb pata-modules-2.6.26-2-sparc64-di_1.41lenny5_sparc.udeb ext3-modules-2.6.26-2-sparc64-di_1.41lenny5_sparc.udeb jfs-modules-2.6.26-2-sparc64-di_1.41lenny5_sparc.udeb scsi-modules-2.6.26-2-sparc64-di_1.41lenny5_sparc.udeb nls-core-modules-2.6.26-2-sparc64-di_1.41lenny5_sparc.udeb ipv6-modules-2.6.26-2-sparc64-di_1.41lenny5_sparc.udeb usb-modules-2.6.26-2-sparc64-di_1.41lenny5_sparc.udeb reiserfs-modules-2.6.26-2-sparc64-di_1.41lenny5_sparc.udeb crypto-core-modules-2.6.26-2-sparc64-di_1.41lenny5_sparc.udeb isofs-modules-2.6.26-2-sparc64-di_1.41lenny5_sparc.udeb usb-storage-modules-2.6.26-2-sparc64-di_1.41lenny5_sparc.udeb cdrom-core-modules-2.6.26-2-sparc64-di_1.41lenny5_sparc.udeb ata-modules-2.6.26-2-sparc64-di_1.41lenny5_sparc.udeb scsi-core-modules-2.6.26-2-sparc64-di_1.41lenny5_sparc.udeb md-modules-2.6.26-2-sparc64-di_1.41lenny5_sparc.udeb zlib-modules-2.6.26-2-sparc64-di_1.41lenny5_sparc.udeb Greetings, Your Debian queue daemon -- To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Processing of linux-kernel-di-amd64-2.6_1.53lenny5_multi.changes
linux-kernel-di-amd64-2.6_1.53lenny5_multi.changes uploaded successfully to localhost along with the files: isofs-modules-2.6.26-2-amd64-di_1.53lenny5_amd64.udeb cdrom-core-modules-2.6.26-2-amd64-di_1.53lenny5_amd64.udeb serial-modules-2.6.26-2-amd64-di_1.53lenny5_amd64.udeb nic-wireless-modules-2.6.26-2-amd64-di_1.53lenny5_amd64.udeb nic-extra-modules-2.6.26-2-amd64-di_1.53lenny5_amd64.udeb pcmcia-storage-modules-2.6.26-2-amd64-di_1.53lenny5_amd64.udeb nic-pcmcia-modules-2.6.26-2-amd64-di_1.53lenny5_amd64.udeb usb-modules-2.6.26-2-amd64-di_1.53lenny5_amd64.udeb jfs-modules-2.6.26-2-amd64-di_1.53lenny5_amd64.udeb pata-modules-2.6.26-2-amd64-di_1.53lenny5_amd64.udeb nic-modules-2.6.26-2-amd64-di_1.53lenny5_amd64.udeb zlib-modules-2.6.26-2-amd64-di_1.53lenny5_amd64.udeb scsi-core-modules-2.6.26-2-amd64-di_1.53lenny5_amd64.udeb crypto-dm-modules-2.6.26-2-amd64-di_1.53lenny5_amd64.udeb kernel-image-2.6.26-2-amd64-di_1.53lenny5_amd64.udeb scsi-common-modules-2.6.26-2-amd64-di_1.53lenny5_amd64.udeb reiserfs-modules-2.6.26-2-amd64-di_1.53lenny5_amd64.udeb nic-usb-modules-2.6.26-2-amd64-di_1.53lenny5_amd64.udeb acpi-modules-2.6.26-2-amd64-di_1.53lenny5_amd64.udeb ata-modules-2.6.26-2-amd64-di_1.53lenny5_amd64.udeb ide-core-modules-2.6.26-2-amd64-di_1.53lenny5_amd64.udeb input-modules-2.6.26-2-amd64-di_1.53lenny5_amd64.udeb ext2-modules-2.6.26-2-amd64-di_1.53lenny5_amd64.udeb linux-kernel-di-amd64-2.6_1.53lenny5.tar.gz irda-modules-2.6.26-2-amd64-di_1.53lenny5_amd64.udeb pcmcia-modules-2.6.26-2-amd64-di_1.53lenny5_amd64.udeb ipv6-modules-2.6.26-2-amd64-di_1.53lenny5_amd64.udeb ppp-modules-2.6.26-2-amd64-di_1.53lenny5_amd64.udeb mouse-modules-2.6.26-2-amd64-di_1.53lenny5_amd64.udeb ntfs-modules-2.6.26-2-amd64-di_1.53lenny5_amd64.udeb crc-modules-2.6.26-2-amd64-di_1.53lenny5_amd64.udeb mmc-modules-2.6.26-2-amd64-di_1.53lenny5_amd64.udeb xfs-modules-2.6.26-2-amd64-di_1.53lenny5_amd64.udeb firewire-core-modules-2.6.26-2-amd64-di_1.53lenny5_amd64.udeb ide-modules-2.6.26-2-amd64-di_1.53lenny5_amd64.udeb ufs-modules-2.6.26-2-amd64-di_1.53lenny5_amd64.udeb crypto-core-modules-2.6.26-2-amd64-di_1.53lenny5_amd64.udeb ext3-modules-2.6.26-2-amd64-di_1.53lenny5_amd64.udeb nic-shared-modules-2.6.26-2-amd64-di_1.53lenny5_amd64.udeb fb-modules-2.6.26-2-amd64-di_1.53lenny5_amd64.udeb floppy-modules-2.6.26-2-amd64-di_1.53lenny5_amd64.udeb usb-storage-modules-2.6.26-2-amd64-di_1.53lenny5_amd64.udeb virtio-modules-2.6.26-2-amd64-di_1.53lenny5_amd64.udeb fat-modules-2.6.26-2-amd64-di_1.53lenny5_amd64.udeb scsi-modules-2.6.26-2-amd64-di_1.53lenny5_amd64.udeb crypto-modules-2.6.26-2-amd64-di_1.53lenny5_amd64.udeb core-modules-2.6.26-2-amd64-di_1.53lenny5_amd64.udeb parport-modules-2.6.26-2-amd64-di_1.53lenny5_amd64.udeb usb-serial-modules-2.6.26-2-amd64-di_1.53lenny5_amd64.udeb plip-modules-2.6.26-2-amd64-di_1.53lenny5_amd64.udeb md-modules-2.6.26-2-amd64-di_1.53lenny5_amd64.udeb nls-core-modules-2.6.26-2-amd64-di_1.53lenny5_amd64.udeb uinput-modules-2.6.26-2-amd64-di_1.53lenny5_amd64.udeb sata-modules-2.6.26-2-amd64-di_1.53lenny5_amd64.udeb loop-modules-2.6.26-2-amd64-di_1.53lenny5_amd64.udeb multipath-modules-2.6.26-2-amd64-di_1.53lenny5_amd64.udeb linux-kernel-di-amd64-2.6_1.53lenny5.dsc qnx4-modules-2.6.26-2-amd64-di_1.53lenny5_amd64.udeb scsi-extra-modules-2.6.26-2-amd64-di_1.53lenny5_amd64.udeb Greetings, Your Debian queue daemon -- To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Processing of linux-kernel-di-armel-2.6_1.32lenny5_multi.changes
linux-kernel-di-armel-2.6_1.32lenny5_multi.changes uploaded successfully to localhost along with the files: multipath-modules-2.6.26-2-versatile-di_1.32lenny5_armel.udeb crypto-modules-2.6.26-2-versatile-di_1.32lenny5_armel.udeb reiserfs-modules-2.6.26-2-versatile-di_1.32lenny5_armel.udeb jfs-modules-2.6.26-2-iop32x-di_1.32lenny5_armel.udeb minix-modules-2.6.26-2-orion5x-di_1.32lenny5_armel.udeb nls-core-modules-2.6.26-2-ixp4xx-di_1.32lenny5_armel.udeb jfs-modules-2.6.26-2-orion5x-di_1.32lenny5_armel.udeb loop-modules-2.6.26-2-iop32x-di_1.32lenny5_armel.udeb linux-kernel-di-armel-2.6_1.32lenny5.tar.gz usb-modules-2.6.26-2-orion5x-di_1.32lenny5_armel.udeb crc-modules-2.6.26-2-versatile-di_1.32lenny5_armel.udeb isofs-modules-2.6.26-2-iop32x-di_1.32lenny5_armel.udeb usb-storage-modules-2.6.26-2-iop32x-di_1.32lenny5_armel.udeb ide-core-modules-2.6.26-2-iop32x-di_1.32lenny5_armel.udeb crypto-dm-modules-2.6.26-2-orion5x-di_1.32lenny5_armel.udeb ext2-modules-2.6.26-2-orion5x-di_1.32lenny5_armel.udeb input-modules-2.6.26-2-ixp4xx-di_1.32lenny5_armel.udeb crc-modules-2.6.26-2-iop32x-di_1.32lenny5_armel.udeb usb-storage-modules-2.6.26-2-ixp4xx-di_1.32lenny5_armel.udeb cdrom-core-modules-2.6.26-2-iop32x-di_1.32lenny5_armel.udeb usb-modules-2.6.26-2-versatile-di_1.32lenny5_armel.udeb nic-usb-modules-2.6.26-2-versatile-di_1.32lenny5_armel.udeb ext3-modules-2.6.26-2-versatile-di_1.32lenny5_armel.udeb nic-modules-2.6.26-2-versatile-di_1.32lenny5_armel.udeb crypto-core-modules-2.6.26-2-iop32x-di_1.32lenny5_armel.udeb md-modules-2.6.26-2-iop32x-di_1.32lenny5_armel.udeb nic-shared-modules-2.6.26-2-orion5x-di_1.32lenny5_armel.udeb usb-modules-2.6.26-2-iop32x-di_1.32lenny5_armel.udeb linux-kernel-di-armel-2.6_1.32lenny5.dsc nic-usb-modules-2.6.26-2-ixp4xx-di_1.32lenny5_armel.udeb nls-core-modules-2.6.26-2-orion5x-di_1.32lenny5_armel.udeb kernel-image-2.6.26-2-versatile-di_1.32lenny5_armel.udeb sata-modules-2.6.26-2-iop32x-di_1.32lenny5_armel.udeb jffs2-modules-2.6.26-2-orion5x-di_1.32lenny5_armel.udeb ext3-modules-2.6.26-2-orion5x-di_1.32lenny5_armel.udeb md-modules-2.6.26-2-orion5x-di_1.32lenny5_armel.udeb multipath-modules-2.6.26-2-orion5x-di_1.32lenny5_armel.udeb fat-modules-2.6.26-2-orion5x-di_1.32lenny5_armel.udeb ext3-modules-2.6.26-2-iop32x-di_1.32lenny5_armel.udeb kernel-image-2.6.26-2-orion5x-di_1.32lenny5_armel.udeb sata-modules-2.6.26-2-ixp4xx-di_1.32lenny5_armel.udeb crypto-modules-2.6.26-2-iop32x-di_1.32lenny5_armel.udeb ata-modules-2.6.26-2-ixp4xx-di_1.32lenny5_armel.udeb md-modules-2.6.26-2-ixp4xx-di_1.32lenny5_armel.udeb reiserfs-modules-2.6.26-2-ixp4xx-di_1.32lenny5_armel.udeb crypto-dm-modules-2.6.26-2-versatile-di_1.32lenny5_armel.udeb scsi-core-modules-2.6.26-2-ixp4xx-di_1.32lenny5_armel.udeb ext2-modules-2.6.26-2-ixp4xx-di_1.32lenny5_armel.udeb core-modules-2.6.26-2-ixp4xx-di_1.32lenny5_armel.udeb crc-modules-2.6.26-2-ixp4xx-di_1.32lenny5_armel.udeb nls-core-modules-2.6.26-2-iop32x-di_1.32lenny5_armel.udeb fat-modules-2.6.26-2-versatile-di_1.32lenny5_armel.udeb input-modules-2.6.26-2-orion5x-di_1.32lenny5_armel.udeb crypto-core-modules-2.6.26-2-versatile-di_1.32lenny5_armel.udeb usb-storage-modules-2.6.26-2-versatile-di_1.32lenny5_armel.udeb core-modules-2.6.26-2-orion5x-di_1.32lenny5_armel.udeb nic-modules-2.6.26-2-iop32x-di_1.32lenny5_armel.udeb nic-modules-2.6.26-2-ixp4xx-di_1.32lenny5_armel.udeb ext2-modules-2.6.26-2-versatile-di_1.32lenny5_armel.udeb sata-modules-2.6.26-2-orion5x-di_1.32lenny5_armel.udeb scsi-common-modules-2.6.26-2-versatile-di_1.32lenny5_armel.udeb reiserfs-modules-2.6.26-2-iop32x-di_1.32lenny5_armel.udeb nic-usb-modules-2.6.26-2-orion5x-di_1.32lenny5_armel.udeb jfs-modules-2.6.26-2-ixp4xx-di_1.32lenny5_armel.udeb loop-modules-2.6.26-2-orion5x-di_1.32lenny5_armel.udeb usb-modules-2.6.26-2-ixp4xx-di_1.32lenny5_armel.udeb fat-modules-2.6.26-2-iop32x-di_1.32lenny5_armel.udeb crypto-modules-2.6.26-2-orion5x-di_1.32lenny5_armel.udeb multipath-modules-2.6.26-2-iop32x-di_1.32lenny5_armel.udeb fat-modules-2.6.26-2-ixp4xx-di_1.32lenny5_armel.udeb kernel-image-2.6.26-2-iop32x-di_1.32lenny5_armel.udeb usb-storage-modules-2.6.26-2-orion5x-di_1.32lenny5_armel.udeb scsi-core-modules-2.6.26-2-iop32x-di_1.32lenny5_armel.udeb core-modules-2.6.26-2-iop32x-di_1.32lenny5_armel.udeb ext3-modules-2.6.26-2-ixp4xx-di_1.32lenny5_armel.udeb sata-modules-2.6.26-2-versatile-di_1.32lenny5_armel.udeb kernel-image-2.6.26-2-ixp4xx-di_1.32lenny5_armel.udeb crc-modules-2.6.26-2-orion5x-di_1.32lenny5_armel.udeb crypto-core-modules-2.6.26-2-orion5x-di_1.32lenny5_armel.udeb scsi-core-modules-2.6.26-2-versatile-di_1.32lenny5_armel.udeb multipath-modules-2.6.26-2-ixp4xx-di_1.32lenny5_armel.udeb reiserfs-modules-2.6.26-2-orion5x-di_1.32lenny5_armel.udeb loop-modules-2.6.26-2-versatile-di_1.32lenny5_armel.udeb md-modules-2.6.26-2-versatile-di_1.32lenny5_ar
linux-kernel-di-hppa-2.6_1.38lenny5_multi.changes ACCEPTED
Accepted: cdrom-core-modules-2.6.26-2-parisc-di_1.38lenny5_hppa.udeb to pool/main/l/linux-kernel-di-hppa-2.6/cdrom-core-modules-2.6.26-2-parisc-di_1.38lenny5_hppa.udeb cdrom-core-modules-2.6.26-2-parisc64-di_1.38lenny5_hppa.udeb to pool/main/l/linux-kernel-di-hppa-2.6/cdrom-core-modules-2.6.26-2-parisc64-di_1.38lenny5_hppa.udeb crypto-core-modules-2.6.26-2-parisc-di_1.38lenny5_hppa.udeb to pool/main/l/linux-kernel-di-hppa-2.6/crypto-core-modules-2.6.26-2-parisc-di_1.38lenny5_hppa.udeb crypto-core-modules-2.6.26-2-parisc64-di_1.38lenny5_hppa.udeb to pool/main/l/linux-kernel-di-hppa-2.6/crypto-core-modules-2.6.26-2-parisc64-di_1.38lenny5_hppa.udeb crypto-dm-modules-2.6.26-2-parisc-di_1.38lenny5_hppa.udeb to pool/main/l/linux-kernel-di-hppa-2.6/crypto-dm-modules-2.6.26-2-parisc-di_1.38lenny5_hppa.udeb crypto-dm-modules-2.6.26-2-parisc64-di_1.38lenny5_hppa.udeb to pool/main/l/linux-kernel-di-hppa-2.6/crypto-dm-modules-2.6.26-2-parisc64-di_1.38lenny5_hppa.udeb crypto-modules-2.6.26-2-parisc-di_1.38lenny5_hppa.udeb to pool/main/l/linux-kernel-di-hppa-2.6/crypto-modules-2.6.26-2-parisc-di_1.38lenny5_hppa.udeb crypto-modules-2.6.26-2-parisc64-di_1.38lenny5_hppa.udeb to pool/main/l/linux-kernel-di-hppa-2.6/crypto-modules-2.6.26-2-parisc64-di_1.38lenny5_hppa.udeb ext3-modules-2.6.26-2-parisc-di_1.38lenny5_hppa.udeb to pool/main/l/linux-kernel-di-hppa-2.6/ext3-modules-2.6.26-2-parisc-di_1.38lenny5_hppa.udeb ext3-modules-2.6.26-2-parisc64-di_1.38lenny5_hppa.udeb to pool/main/l/linux-kernel-di-hppa-2.6/ext3-modules-2.6.26-2-parisc64-di_1.38lenny5_hppa.udeb ide-modules-2.6.26-2-parisc-di_1.38lenny5_hppa.udeb to pool/main/l/linux-kernel-di-hppa-2.6/ide-modules-2.6.26-2-parisc-di_1.38lenny5_hppa.udeb ide-modules-2.6.26-2-parisc64-di_1.38lenny5_hppa.udeb to pool/main/l/linux-kernel-di-hppa-2.6/ide-modules-2.6.26-2-parisc64-di_1.38lenny5_hppa.udeb input-modules-2.6.26-2-parisc-di_1.38lenny5_hppa.udeb to pool/main/l/linux-kernel-di-hppa-2.6/input-modules-2.6.26-2-parisc-di_1.38lenny5_hppa.udeb input-modules-2.6.26-2-parisc64-di_1.38lenny5_hppa.udeb to pool/main/l/linux-kernel-di-hppa-2.6/input-modules-2.6.26-2-parisc64-di_1.38lenny5_hppa.udeb ipv6-modules-2.6.26-2-parisc-di_1.38lenny5_hppa.udeb to pool/main/l/linux-kernel-di-hppa-2.6/ipv6-modules-2.6.26-2-parisc-di_1.38lenny5_hppa.udeb ipv6-modules-2.6.26-2-parisc64-di_1.38lenny5_hppa.udeb to pool/main/l/linux-kernel-di-hppa-2.6/ipv6-modules-2.6.26-2-parisc64-di_1.38lenny5_hppa.udeb kernel-image-2.6.26-2-parisc-di_1.38lenny5_hppa.udeb to pool/main/l/linux-kernel-di-hppa-2.6/kernel-image-2.6.26-2-parisc-di_1.38lenny5_hppa.udeb kernel-image-2.6.26-2-parisc64-di_1.38lenny5_hppa.udeb to pool/main/l/linux-kernel-di-hppa-2.6/kernel-image-2.6.26-2-parisc64-di_1.38lenny5_hppa.udeb linux-kernel-di-hppa-2.6_1.38lenny5.dsc to pool/main/l/linux-kernel-di-hppa-2.6/linux-kernel-di-hppa-2.6_1.38lenny5.dsc linux-kernel-di-hppa-2.6_1.38lenny5.tar.gz to pool/main/l/linux-kernel-di-hppa-2.6/linux-kernel-di-hppa-2.6_1.38lenny5.tar.gz loop-modules-2.6.26-2-parisc-di_1.38lenny5_hppa.udeb to pool/main/l/linux-kernel-di-hppa-2.6/loop-modules-2.6.26-2-parisc-di_1.38lenny5_hppa.udeb loop-modules-2.6.26-2-parisc64-di_1.38lenny5_hppa.udeb to pool/main/l/linux-kernel-di-hppa-2.6/loop-modules-2.6.26-2-parisc64-di_1.38lenny5_hppa.udeb md-modules-2.6.26-2-parisc-di_1.38lenny5_hppa.udeb to pool/main/l/linux-kernel-di-hppa-2.6/md-modules-2.6.26-2-parisc-di_1.38lenny5_hppa.udeb md-modules-2.6.26-2-parisc64-di_1.38lenny5_hppa.udeb to pool/main/l/linux-kernel-di-hppa-2.6/md-modules-2.6.26-2-parisc64-di_1.38lenny5_hppa.udeb multipath-modules-2.6.26-2-parisc-di_1.38lenny5_hppa.udeb to pool/main/l/linux-kernel-di-hppa-2.6/multipath-modules-2.6.26-2-parisc-di_1.38lenny5_hppa.udeb multipath-modules-2.6.26-2-parisc64-di_1.38lenny5_hppa.udeb to pool/main/l/linux-kernel-di-hppa-2.6/multipath-modules-2.6.26-2-parisc64-di_1.38lenny5_hppa.udeb nic-modules-2.6.26-2-parisc-di_1.38lenny5_hppa.udeb to pool/main/l/linux-kernel-di-hppa-2.6/nic-modules-2.6.26-2-parisc-di_1.38lenny5_hppa.udeb nic-modules-2.6.26-2-parisc64-di_1.38lenny5_hppa.udeb to pool/main/l/linux-kernel-di-hppa-2.6/nic-modules-2.6.26-2-parisc64-di_1.38lenny5_hppa.udeb ppp-modules-2.6.26-2-parisc-di_1.38lenny5_hppa.udeb to pool/main/l/linux-kernel-di-hppa-2.6/ppp-modules-2.6.26-2-parisc-di_1.38lenny5_hppa.udeb ppp-modules-2.6.26-2-parisc64-di_1.38lenny5_hppa.udeb to pool/main/l/linux-kernel-di-hppa-2.6/ppp-modules-2.6.26-2-parisc64-di_1.38lenny5_hppa.udeb scsi-modules-2.6.26-2-parisc-di_1.38lenny5_hppa.udeb to pool/main/l/linux-kernel-di-hppa-2.6/scsi-modules-2.6.26-2-parisc-di_1.38lenny5_hppa.udeb scsi-modules-2.6.26-2-parisc64-di_1.38lenny5_hppa.udeb to pool/main/l/linux-kernel-di-hppa-2.6/scsi-modules-2.6.26-2-parisc64-di_1.38lenny5_hppa.udeb usb-modules-2.6.26-2-parisc-di_1.38lenny5_hppa.udeb to pool/main/l/linux-kernel-di-hppa-2.6/usb-modules-2.6.26-2-parisc
linux-kernel-di-alpha-2.6_0.37lenny5_multi.changes ACCEPTED
Accepted: ata-modules-2.6.26-2-alpha-generic-di_0.37lenny5_alpha.udeb to pool/main/l/linux-kernel-di-alpha-2.6/ata-modules-2.6.26-2-alpha-generic-di_0.37lenny5_alpha.udeb cdrom-core-modules-2.6.26-2-alpha-generic-di_0.37lenny5_alpha.udeb to pool/main/l/linux-kernel-di-alpha-2.6/cdrom-core-modules-2.6.26-2-alpha-generic-di_0.37lenny5_alpha.udeb core-modules-2.6.26-2-alpha-generic-di_0.37lenny5_alpha.udeb to pool/main/l/linux-kernel-di-alpha-2.6/core-modules-2.6.26-2-alpha-generic-di_0.37lenny5_alpha.udeb crc-modules-2.6.26-2-alpha-generic-di_0.37lenny5_alpha.udeb to pool/main/l/linux-kernel-di-alpha-2.6/crc-modules-2.6.26-2-alpha-generic-di_0.37lenny5_alpha.udeb crypto-core-modules-2.6.26-2-alpha-generic-di_0.37lenny5_alpha.udeb to pool/main/l/linux-kernel-di-alpha-2.6/crypto-core-modules-2.6.26-2-alpha-generic-di_0.37lenny5_alpha.udeb crypto-dm-modules-2.6.26-2-alpha-generic-di_0.37lenny5_alpha.udeb to pool/main/l/linux-kernel-di-alpha-2.6/crypto-dm-modules-2.6.26-2-alpha-generic-di_0.37lenny5_alpha.udeb crypto-modules-2.6.26-2-alpha-generic-di_0.37lenny5_alpha.udeb to pool/main/l/linux-kernel-di-alpha-2.6/crypto-modules-2.6.26-2-alpha-generic-di_0.37lenny5_alpha.udeb ext3-modules-2.6.26-2-alpha-generic-di_0.37lenny5_alpha.udeb to pool/main/l/linux-kernel-di-alpha-2.6/ext3-modules-2.6.26-2-alpha-generic-di_0.37lenny5_alpha.udeb fat-modules-2.6.26-2-alpha-generic-di_0.37lenny5_alpha.udeb to pool/main/l/linux-kernel-di-alpha-2.6/fat-modules-2.6.26-2-alpha-generic-di_0.37lenny5_alpha.udeb fb-modules-2.6.26-2-alpha-generic-di_0.37lenny5_alpha.udeb to pool/main/l/linux-kernel-di-alpha-2.6/fb-modules-2.6.26-2-alpha-generic-di_0.37lenny5_alpha.udeb ide-core-modules-2.6.26-2-alpha-generic-di_0.37lenny5_alpha.udeb to pool/main/l/linux-kernel-di-alpha-2.6/ide-core-modules-2.6.26-2-alpha-generic-di_0.37lenny5_alpha.udeb ide-modules-2.6.26-2-alpha-generic-di_0.37lenny5_alpha.udeb to pool/main/l/linux-kernel-di-alpha-2.6/ide-modules-2.6.26-2-alpha-generic-di_0.37lenny5_alpha.udeb ipv6-modules-2.6.26-2-alpha-generic-di_0.37lenny5_alpha.udeb to pool/main/l/linux-kernel-di-alpha-2.6/ipv6-modules-2.6.26-2-alpha-generic-di_0.37lenny5_alpha.udeb isofs-modules-2.6.26-2-alpha-generic-di_0.37lenny5_alpha.udeb to pool/main/l/linux-kernel-di-alpha-2.6/isofs-modules-2.6.26-2-alpha-generic-di_0.37lenny5_alpha.udeb jfs-modules-2.6.26-2-alpha-generic-di_0.37lenny5_alpha.udeb to pool/main/l/linux-kernel-di-alpha-2.6/jfs-modules-2.6.26-2-alpha-generic-di_0.37lenny5_alpha.udeb kernel-image-2.6.26-2-alpha-generic-di_0.37lenny5_alpha.udeb to pool/main/l/linux-kernel-di-alpha-2.6/kernel-image-2.6.26-2-alpha-generic-di_0.37lenny5_alpha.udeb linux-kernel-di-alpha-2.6_0.37lenny5.dsc to pool/main/l/linux-kernel-di-alpha-2.6/linux-kernel-di-alpha-2.6_0.37lenny5.dsc linux-kernel-di-alpha-2.6_0.37lenny5.tar.gz to pool/main/l/linux-kernel-di-alpha-2.6/linux-kernel-di-alpha-2.6_0.37lenny5.tar.gz md-modules-2.6.26-2-alpha-generic-di_0.37lenny5_alpha.udeb to pool/main/l/linux-kernel-di-alpha-2.6/md-modules-2.6.26-2-alpha-generic-di_0.37lenny5_alpha.udeb multipath-modules-2.6.26-2-alpha-generic-di_0.37lenny5_alpha.udeb to pool/main/l/linux-kernel-di-alpha-2.6/multipath-modules-2.6.26-2-alpha-generic-di_0.37lenny5_alpha.udeb nic-extra-modules-2.6.26-2-alpha-generic-di_0.37lenny5_alpha.udeb to pool/main/l/linux-kernel-di-alpha-2.6/nic-extra-modules-2.6.26-2-alpha-generic-di_0.37lenny5_alpha.udeb nic-modules-2.6.26-2-alpha-generic-di_0.37lenny5_alpha.udeb to pool/main/l/linux-kernel-di-alpha-2.6/nic-modules-2.6.26-2-alpha-generic-di_0.37lenny5_alpha.udeb nic-shared-modules-2.6.26-2-alpha-generic-di_0.37lenny5_alpha.udeb to pool/main/l/linux-kernel-di-alpha-2.6/nic-shared-modules-2.6.26-2-alpha-generic-di_0.37lenny5_alpha.udeb nic-wireless-modules-2.6.26-2-alpha-generic-di_0.37lenny5_alpha.udeb to pool/main/l/linux-kernel-di-alpha-2.6/nic-wireless-modules-2.6.26-2-alpha-generic-di_0.37lenny5_alpha.udeb nls-core-modules-2.6.26-2-alpha-generic-di_0.37lenny5_alpha.udeb to pool/main/l/linux-kernel-di-alpha-2.6/nls-core-modules-2.6.26-2-alpha-generic-di_0.37lenny5_alpha.udeb parport-modules-2.6.26-2-alpha-generic-di_0.37lenny5_alpha.udeb to pool/main/l/linux-kernel-di-alpha-2.6/parport-modules-2.6.26-2-alpha-generic-di_0.37lenny5_alpha.udeb plip-modules-2.6.26-2-alpha-generic-di_0.37lenny5_alpha.udeb to pool/main/l/linux-kernel-di-alpha-2.6/plip-modules-2.6.26-2-alpha-generic-di_0.37lenny5_alpha.udeb ppp-modules-2.6.26-2-alpha-generic-di_0.37lenny5_alpha.udeb to pool/main/l/linux-kernel-di-alpha-2.6/ppp-modules-2.6.26-2-alpha-generic-di_0.37lenny5_alpha.udeb reiserfs-modules-2.6.26-2-alpha-generic-di_0.37lenny5_alpha.udeb to pool/main/l/linux-kernel-di-alpha-2.6/reiserfs-modules-2.6.26-2-alpha-generic-di_0.37lenny5_alpha.udeb rtc-modules-2.6.26-2-alpha-generic-di_0.37lenny5_alpha.udeb to pool/main/l/linux-kernel-di-alpha-2.6/rtc-modules-2.6.26-2-alpha-generic-di_0.37lenn
linux-kernel-di-i386-2.6_1.76lenny5_multi.changes ACCEPTED
Accepted: acpi-modules-2.6.26-2-486-di_1.76lenny5_i386.udeb to pool/main/l/linux-kernel-di-i386-2.6/acpi-modules-2.6.26-2-486-di_1.76lenny5_i386.udeb acpi-modules-2.6.26-2-686-bigmem-di_1.76lenny5_i386.udeb to pool/main/l/linux-kernel-di-i386-2.6/acpi-modules-2.6.26-2-686-bigmem-di_1.76lenny5_i386.udeb ata-modules-2.6.26-2-486-di_1.76lenny5_i386.udeb to pool/main/l/linux-kernel-di-i386-2.6/ata-modules-2.6.26-2-486-di_1.76lenny5_i386.udeb ata-modules-2.6.26-2-686-bigmem-di_1.76lenny5_i386.udeb to pool/main/l/linux-kernel-di-i386-2.6/ata-modules-2.6.26-2-686-bigmem-di_1.76lenny5_i386.udeb cdrom-core-modules-2.6.26-2-486-di_1.76lenny5_i386.udeb to pool/main/l/linux-kernel-di-i386-2.6/cdrom-core-modules-2.6.26-2-486-di_1.76lenny5_i386.udeb cdrom-core-modules-2.6.26-2-686-bigmem-di_1.76lenny5_i386.udeb to pool/main/l/linux-kernel-di-i386-2.6/cdrom-core-modules-2.6.26-2-686-bigmem-di_1.76lenny5_i386.udeb core-modules-2.6.26-2-486-di_1.76lenny5_i386.udeb to pool/main/l/linux-kernel-di-i386-2.6/core-modules-2.6.26-2-486-di_1.76lenny5_i386.udeb core-modules-2.6.26-2-686-bigmem-di_1.76lenny5_i386.udeb to pool/main/l/linux-kernel-di-i386-2.6/core-modules-2.6.26-2-686-bigmem-di_1.76lenny5_i386.udeb crc-modules-2.6.26-2-486-di_1.76lenny5_i386.udeb to pool/main/l/linux-kernel-di-i386-2.6/crc-modules-2.6.26-2-486-di_1.76lenny5_i386.udeb crc-modules-2.6.26-2-686-bigmem-di_1.76lenny5_i386.udeb to pool/main/l/linux-kernel-di-i386-2.6/crc-modules-2.6.26-2-686-bigmem-di_1.76lenny5_i386.udeb crypto-core-modules-2.6.26-2-486-di_1.76lenny5_i386.udeb to pool/main/l/linux-kernel-di-i386-2.6/crypto-core-modules-2.6.26-2-486-di_1.76lenny5_i386.udeb crypto-core-modules-2.6.26-2-686-bigmem-di_1.76lenny5_i386.udeb to pool/main/l/linux-kernel-di-i386-2.6/crypto-core-modules-2.6.26-2-686-bigmem-di_1.76lenny5_i386.udeb crypto-dm-modules-2.6.26-2-486-di_1.76lenny5_i386.udeb to pool/main/l/linux-kernel-di-i386-2.6/crypto-dm-modules-2.6.26-2-486-di_1.76lenny5_i386.udeb crypto-dm-modules-2.6.26-2-686-bigmem-di_1.76lenny5_i386.udeb to pool/main/l/linux-kernel-di-i386-2.6/crypto-dm-modules-2.6.26-2-686-bigmem-di_1.76lenny5_i386.udeb crypto-modules-2.6.26-2-486-di_1.76lenny5_i386.udeb to pool/main/l/linux-kernel-di-i386-2.6/crypto-modules-2.6.26-2-486-di_1.76lenny5_i386.udeb crypto-modules-2.6.26-2-686-bigmem-di_1.76lenny5_i386.udeb to pool/main/l/linux-kernel-di-i386-2.6/crypto-modules-2.6.26-2-686-bigmem-di_1.76lenny5_i386.udeb efi-modules-2.6.26-2-486-di_1.76lenny5_i386.udeb to pool/main/l/linux-kernel-di-i386-2.6/efi-modules-2.6.26-2-486-di_1.76lenny5_i386.udeb efi-modules-2.6.26-2-686-bigmem-di_1.76lenny5_i386.udeb to pool/main/l/linux-kernel-di-i386-2.6/efi-modules-2.6.26-2-686-bigmem-di_1.76lenny5_i386.udeb ext2-modules-2.6.26-2-486-di_1.76lenny5_i386.udeb to pool/main/l/linux-kernel-di-i386-2.6/ext2-modules-2.6.26-2-486-di_1.76lenny5_i386.udeb ext2-modules-2.6.26-2-686-bigmem-di_1.76lenny5_i386.udeb to pool/main/l/linux-kernel-di-i386-2.6/ext2-modules-2.6.26-2-686-bigmem-di_1.76lenny5_i386.udeb ext3-modules-2.6.26-2-486-di_1.76lenny5_i386.udeb to pool/main/l/linux-kernel-di-i386-2.6/ext3-modules-2.6.26-2-486-di_1.76lenny5_i386.udeb ext3-modules-2.6.26-2-686-bigmem-di_1.76lenny5_i386.udeb to pool/main/l/linux-kernel-di-i386-2.6/ext3-modules-2.6.26-2-686-bigmem-di_1.76lenny5_i386.udeb fat-modules-2.6.26-2-486-di_1.76lenny5_i386.udeb to pool/main/l/linux-kernel-di-i386-2.6/fat-modules-2.6.26-2-486-di_1.76lenny5_i386.udeb fat-modules-2.6.26-2-686-bigmem-di_1.76lenny5_i386.udeb to pool/main/l/linux-kernel-di-i386-2.6/fat-modules-2.6.26-2-686-bigmem-di_1.76lenny5_i386.udeb fb-modules-2.6.26-2-486-di_1.76lenny5_i386.udeb to pool/main/l/linux-kernel-di-i386-2.6/fb-modules-2.6.26-2-486-di_1.76lenny5_i386.udeb fb-modules-2.6.26-2-686-bigmem-di_1.76lenny5_i386.udeb to pool/main/l/linux-kernel-di-i386-2.6/fb-modules-2.6.26-2-686-bigmem-di_1.76lenny5_i386.udeb firewire-core-modules-2.6.26-2-486-di_1.76lenny5_i386.udeb to pool/main/l/linux-kernel-di-i386-2.6/firewire-core-modules-2.6.26-2-486-di_1.76lenny5_i386.udeb firewire-core-modules-2.6.26-2-686-bigmem-di_1.76lenny5_i386.udeb to pool/main/l/linux-kernel-di-i386-2.6/firewire-core-modules-2.6.26-2-686-bigmem-di_1.76lenny5_i386.udeb floppy-modules-2.6.26-2-486-di_1.76lenny5_i386.udeb to pool/main/l/linux-kernel-di-i386-2.6/floppy-modules-2.6.26-2-486-di_1.76lenny5_i386.udeb floppy-modules-2.6.26-2-686-bigmem-di_1.76lenny5_i386.udeb to pool/main/l/linux-kernel-di-i386-2.6/floppy-modules-2.6.26-2-686-bigmem-di_1.76lenny5_i386.udeb ide-core-modules-2.6.26-2-486-di_1.76lenny5_i386.udeb to pool/main/l/linux-kernel-di-i386-2.6/ide-core-modules-2.6.26-2-486-di_1.76lenny5_i386.udeb ide-core-modules-2.6.26-2-686-bigmem-di_1.76lenny5_i386.udeb to pool/main/l/linux-kernel-di-i386-2.6/ide-core-modules-2.6.26-2-686-bigmem-di_1.76lenny5_i386.udeb ide-modules-2.6.26-2-486-di_1.76lenny5_i386.udeb to pool/main/l/linux
Re: Ban of Uwe Bugla from debian mailinglists
Alexander Wirt dijo [Mon, Aug 24, 2009 at 09:14:48PM +0200]: > Hi, > > Unfortunately I have to announce that we have banned Uwe Bugla from our > mailinglists. In the last days he showed an attitude on our lists that is not > acceptable in any way ([1-4] and more). We already gave him a warning, > but this didn't helped. > > We really don't have anything against a good argument, but such attitude is > neither wanted nor accepted on our lists (see netiquette [5] and our Code > of Conduct [6]). > > This ban will initially last for two weeks. After that period it will be > lifted, but if such events happen again we will reimpose it permanently. Thanks for your hard work. I also stand behind you on this one, and I'd also support you if the ban were to be made permanent. I am no debian-boot frequent follower, but I do know this project does not need non-contributors with the level of aggressivity this guy has. Thanks, -- Gunnar Wolf • gw...@gwolf.org • (+52-55)5623-0154 / 1451-2244 pgpjhtu0MDUB5.pgp Description: PGP signature
linux-kernel-di-mipsel-2.6_1.8lenny5_multi.changes ACCEPTED
Accepted: cdrom-core-modules-2.6.26-2-4kc-malta-di_1.8lenny5_mipsel.udeb to pool/main/l/linux-kernel-di-mipsel-2.6/cdrom-core-modules-2.6.26-2-4kc-malta-di_1.8lenny5_mipsel.udeb cdrom-core-modules-2.6.26-2-r5k-cobalt-di_1.8lenny5_mipsel.udeb to pool/main/l/linux-kernel-di-mipsel-2.6/cdrom-core-modules-2.6.26-2-r5k-cobalt-di_1.8lenny5_mipsel.udeb cdrom-core-modules-2.6.26-2-sb1-bcm91250a-di_1.8lenny5_mipsel.udeb to pool/main/l/linux-kernel-di-mipsel-2.6/cdrom-core-modules-2.6.26-2-sb1-bcm91250a-di_1.8lenny5_mipsel.udeb cdrom-core-modules-2.6.26-2-sb1a-bcm91480b-di_1.8lenny5_mipsel.udeb to pool/main/l/linux-kernel-di-mipsel-2.6/cdrom-core-modules-2.6.26-2-sb1a-bcm91480b-di_1.8lenny5_mipsel.udeb crypto-core-modules-2.6.26-2-r5k-cobalt-di_1.8lenny5_mipsel.udeb to pool/main/l/linux-kernel-di-mipsel-2.6/crypto-core-modules-2.6.26-2-r5k-cobalt-di_1.8lenny5_mipsel.udeb crypto-dm-modules-2.6.26-2-4kc-malta-di_1.8lenny5_mipsel.udeb to pool/main/l/linux-kernel-di-mipsel-2.6/crypto-dm-modules-2.6.26-2-4kc-malta-di_1.8lenny5_mipsel.udeb crypto-dm-modules-2.6.26-2-r5k-cobalt-di_1.8lenny5_mipsel.udeb to pool/main/l/linux-kernel-di-mipsel-2.6/crypto-dm-modules-2.6.26-2-r5k-cobalt-di_1.8lenny5_mipsel.udeb crypto-dm-modules-2.6.26-2-sb1-bcm91250a-di_1.8lenny5_mipsel.udeb to pool/main/l/linux-kernel-di-mipsel-2.6/crypto-dm-modules-2.6.26-2-sb1-bcm91250a-di_1.8lenny5_mipsel.udeb crypto-dm-modules-2.6.26-2-sb1a-bcm91480b-di_1.8lenny5_mipsel.udeb to pool/main/l/linux-kernel-di-mipsel-2.6/crypto-dm-modules-2.6.26-2-sb1a-bcm91480b-di_1.8lenny5_mipsel.udeb crypto-modules-2.6.26-2-4kc-malta-di_1.8lenny5_mipsel.udeb to pool/main/l/linux-kernel-di-mipsel-2.6/crypto-modules-2.6.26-2-4kc-malta-di_1.8lenny5_mipsel.udeb crypto-modules-2.6.26-2-r5k-cobalt-di_1.8lenny5_mipsel.udeb to pool/main/l/linux-kernel-di-mipsel-2.6/crypto-modules-2.6.26-2-r5k-cobalt-di_1.8lenny5_mipsel.udeb crypto-modules-2.6.26-2-sb1-bcm91250a-di_1.8lenny5_mipsel.udeb to pool/main/l/linux-kernel-di-mipsel-2.6/crypto-modules-2.6.26-2-sb1-bcm91250a-di_1.8lenny5_mipsel.udeb crypto-modules-2.6.26-2-sb1a-bcm91480b-di_1.8lenny5_mipsel.udeb to pool/main/l/linux-kernel-di-mipsel-2.6/crypto-modules-2.6.26-2-sb1a-bcm91480b-di_1.8lenny5_mipsel.udeb fat-modules-2.6.26-2-4kc-malta-di_1.8lenny5_mipsel.udeb to pool/main/l/linux-kernel-di-mipsel-2.6/fat-modules-2.6.26-2-4kc-malta-di_1.8lenny5_mipsel.udeb fat-modules-2.6.26-2-r5k-cobalt-di_1.8lenny5_mipsel.udeb to pool/main/l/linux-kernel-di-mipsel-2.6/fat-modules-2.6.26-2-r5k-cobalt-di_1.8lenny5_mipsel.udeb fat-modules-2.6.26-2-sb1-bcm91250a-di_1.8lenny5_mipsel.udeb to pool/main/l/linux-kernel-di-mipsel-2.6/fat-modules-2.6.26-2-sb1-bcm91250a-di_1.8lenny5_mipsel.udeb fat-modules-2.6.26-2-sb1a-bcm91480b-di_1.8lenny5_mipsel.udeb to pool/main/l/linux-kernel-di-mipsel-2.6/fat-modules-2.6.26-2-sb1a-bcm91480b-di_1.8lenny5_mipsel.udeb fb-modules-2.6.26-2-sb1-bcm91250a-di_1.8lenny5_mipsel.udeb to pool/main/l/linux-kernel-di-mipsel-2.6/fb-modules-2.6.26-2-sb1-bcm91250a-di_1.8lenny5_mipsel.udeb fb-modules-2.6.26-2-sb1a-bcm91480b-di_1.8lenny5_mipsel.udeb to pool/main/l/linux-kernel-di-mipsel-2.6/fb-modules-2.6.26-2-sb1a-bcm91480b-di_1.8lenny5_mipsel.udeb ide-modules-2.6.26-2-4kc-malta-di_1.8lenny5_mipsel.udeb to pool/main/l/linux-kernel-di-mipsel-2.6/ide-modules-2.6.26-2-4kc-malta-di_1.8lenny5_mipsel.udeb ide-modules-2.6.26-2-sb1-bcm91250a-di_1.8lenny5_mipsel.udeb to pool/main/l/linux-kernel-di-mipsel-2.6/ide-modules-2.6.26-2-sb1-bcm91250a-di_1.8lenny5_mipsel.udeb ide-modules-2.6.26-2-sb1a-bcm91480b-di_1.8lenny5_mipsel.udeb to pool/main/l/linux-kernel-di-mipsel-2.6/ide-modules-2.6.26-2-sb1a-bcm91480b-di_1.8lenny5_mipsel.udeb input-modules-2.6.26-2-4kc-malta-di_1.8lenny5_mipsel.udeb to pool/main/l/linux-kernel-di-mipsel-2.6/input-modules-2.6.26-2-4kc-malta-di_1.8lenny5_mipsel.udeb input-modules-2.6.26-2-sb1-bcm91250a-di_1.8lenny5_mipsel.udeb to pool/main/l/linux-kernel-di-mipsel-2.6/input-modules-2.6.26-2-sb1-bcm91250a-di_1.8lenny5_mipsel.udeb input-modules-2.6.26-2-sb1a-bcm91480b-di_1.8lenny5_mipsel.udeb to pool/main/l/linux-kernel-di-mipsel-2.6/input-modules-2.6.26-2-sb1a-bcm91480b-di_1.8lenny5_mipsel.udeb ipv6-modules-2.6.26-2-4kc-malta-di_1.8lenny5_mipsel.udeb to pool/main/l/linux-kernel-di-mipsel-2.6/ipv6-modules-2.6.26-2-4kc-malta-di_1.8lenny5_mipsel.udeb ipv6-modules-2.6.26-2-r5k-cobalt-di_1.8lenny5_mipsel.udeb to pool/main/l/linux-kernel-di-mipsel-2.6/ipv6-modules-2.6.26-2-r5k-cobalt-di_1.8lenny5_mipsel.udeb ipv6-modules-2.6.26-2-sb1-bcm91250a-di_1.8lenny5_mipsel.udeb to pool/main/l/linux-kernel-di-mipsel-2.6/ipv6-modules-2.6.26-2-sb1-bcm91250a-di_1.8lenny5_mipsel.udeb ipv6-modules-2.6.26-2-sb1a-bcm91480b-di_1.8lenny5_mipsel.udeb to pool/main/l/linux-kernel-di-mipsel-2.6/ipv6-modules-2.6.26-2-sb1a-bcm91480b-di_1.8lenny5_mipsel.udeb isofs-modules-2.6.26-2-4kc-malta-di_1.8lenny5_mipsel.udeb to pool/main/l/linux-kernel-di-mipsel-2.6/isofs-modules-2.
linux-kernel-di-mips-2.6_1.9lenny5_multi.changes ACCEPTED
Accepted: cdrom-core-modules-2.6.26-2-4kc-malta-di_1.9lenny5_mips.udeb to pool/main/l/linux-kernel-di-mips-2.6/cdrom-core-modules-2.6.26-2-4kc-malta-di_1.9lenny5_mips.udeb cdrom-core-modules-2.6.26-2-sb1-bcm91250a-di_1.9lenny5_mips.udeb to pool/main/l/linux-kernel-di-mips-2.6/cdrom-core-modules-2.6.26-2-sb1-bcm91250a-di_1.9lenny5_mips.udeb cdrom-core-modules-2.6.26-2-sb1a-bcm91480b-di_1.9lenny5_mips.udeb to pool/main/l/linux-kernel-di-mips-2.6/cdrom-core-modules-2.6.26-2-sb1a-bcm91480b-di_1.9lenny5_mips.udeb crypto-core-modules-2.6.26-2-r4k-ip22-di_1.9lenny5_mips.udeb to pool/main/l/linux-kernel-di-mips-2.6/crypto-core-modules-2.6.26-2-r4k-ip22-di_1.9lenny5_mips.udeb crypto-core-modules-2.6.26-2-r5k-ip32-di_1.9lenny5_mips.udeb to pool/main/l/linux-kernel-di-mips-2.6/crypto-core-modules-2.6.26-2-r5k-ip32-di_1.9lenny5_mips.udeb crypto-dm-modules-2.6.26-2-4kc-malta-di_1.9lenny5_mips.udeb to pool/main/l/linux-kernel-di-mips-2.6/crypto-dm-modules-2.6.26-2-4kc-malta-di_1.9lenny5_mips.udeb crypto-dm-modules-2.6.26-2-r4k-ip22-di_1.9lenny5_mips.udeb to pool/main/l/linux-kernel-di-mips-2.6/crypto-dm-modules-2.6.26-2-r4k-ip22-di_1.9lenny5_mips.udeb crypto-dm-modules-2.6.26-2-r5k-ip32-di_1.9lenny5_mips.udeb to pool/main/l/linux-kernel-di-mips-2.6/crypto-dm-modules-2.6.26-2-r5k-ip32-di_1.9lenny5_mips.udeb crypto-dm-modules-2.6.26-2-sb1-bcm91250a-di_1.9lenny5_mips.udeb to pool/main/l/linux-kernel-di-mips-2.6/crypto-dm-modules-2.6.26-2-sb1-bcm91250a-di_1.9lenny5_mips.udeb crypto-dm-modules-2.6.26-2-sb1a-bcm91480b-di_1.9lenny5_mips.udeb to pool/main/l/linux-kernel-di-mips-2.6/crypto-dm-modules-2.6.26-2-sb1a-bcm91480b-di_1.9lenny5_mips.udeb crypto-modules-2.6.26-2-4kc-malta-di_1.9lenny5_mips.udeb to pool/main/l/linux-kernel-di-mips-2.6/crypto-modules-2.6.26-2-4kc-malta-di_1.9lenny5_mips.udeb crypto-modules-2.6.26-2-r4k-ip22-di_1.9lenny5_mips.udeb to pool/main/l/linux-kernel-di-mips-2.6/crypto-modules-2.6.26-2-r4k-ip22-di_1.9lenny5_mips.udeb crypto-modules-2.6.26-2-r5k-ip32-di_1.9lenny5_mips.udeb to pool/main/l/linux-kernel-di-mips-2.6/crypto-modules-2.6.26-2-r5k-ip32-di_1.9lenny5_mips.udeb crypto-modules-2.6.26-2-sb1-bcm91250a-di_1.9lenny5_mips.udeb to pool/main/l/linux-kernel-di-mips-2.6/crypto-modules-2.6.26-2-sb1-bcm91250a-di_1.9lenny5_mips.udeb crypto-modules-2.6.26-2-sb1a-bcm91480b-di_1.9lenny5_mips.udeb to pool/main/l/linux-kernel-di-mips-2.6/crypto-modules-2.6.26-2-sb1a-bcm91480b-di_1.9lenny5_mips.udeb fat-modules-2.6.26-2-4kc-malta-di_1.9lenny5_mips.udeb to pool/main/l/linux-kernel-di-mips-2.6/fat-modules-2.6.26-2-4kc-malta-di_1.9lenny5_mips.udeb fat-modules-2.6.26-2-sb1-bcm91250a-di_1.9lenny5_mips.udeb to pool/main/l/linux-kernel-di-mips-2.6/fat-modules-2.6.26-2-sb1-bcm91250a-di_1.9lenny5_mips.udeb fat-modules-2.6.26-2-sb1a-bcm91480b-di_1.9lenny5_mips.udeb to pool/main/l/linux-kernel-di-mips-2.6/fat-modules-2.6.26-2-sb1a-bcm91480b-di_1.9lenny5_mips.udeb fb-modules-2.6.26-2-sb1-bcm91250a-di_1.9lenny5_mips.udeb to pool/main/l/linux-kernel-di-mips-2.6/fb-modules-2.6.26-2-sb1-bcm91250a-di_1.9lenny5_mips.udeb fb-modules-2.6.26-2-sb1a-bcm91480b-di_1.9lenny5_mips.udeb to pool/main/l/linux-kernel-di-mips-2.6/fb-modules-2.6.26-2-sb1a-bcm91480b-di_1.9lenny5_mips.udeb ide-modules-2.6.26-2-4kc-malta-di_1.9lenny5_mips.udeb to pool/main/l/linux-kernel-di-mips-2.6/ide-modules-2.6.26-2-4kc-malta-di_1.9lenny5_mips.udeb ide-modules-2.6.26-2-sb1-bcm91250a-di_1.9lenny5_mips.udeb to pool/main/l/linux-kernel-di-mips-2.6/ide-modules-2.6.26-2-sb1-bcm91250a-di_1.9lenny5_mips.udeb ide-modules-2.6.26-2-sb1a-bcm91480b-di_1.9lenny5_mips.udeb to pool/main/l/linux-kernel-di-mips-2.6/ide-modules-2.6.26-2-sb1a-bcm91480b-di_1.9lenny5_mips.udeb input-modules-2.6.26-2-4kc-malta-di_1.9lenny5_mips.udeb to pool/main/l/linux-kernel-di-mips-2.6/input-modules-2.6.26-2-4kc-malta-di_1.9lenny5_mips.udeb input-modules-2.6.26-2-sb1-bcm91250a-di_1.9lenny5_mips.udeb to pool/main/l/linux-kernel-di-mips-2.6/input-modules-2.6.26-2-sb1-bcm91250a-di_1.9lenny5_mips.udeb input-modules-2.6.26-2-sb1a-bcm91480b-di_1.9lenny5_mips.udeb to pool/main/l/linux-kernel-di-mips-2.6/input-modules-2.6.26-2-sb1a-bcm91480b-di_1.9lenny5_mips.udeb ipv6-modules-2.6.26-2-4kc-malta-di_1.9lenny5_mips.udeb to pool/main/l/linux-kernel-di-mips-2.6/ipv6-modules-2.6.26-2-4kc-malta-di_1.9lenny5_mips.udeb ipv6-modules-2.6.26-2-r4k-ip22-di_1.9lenny5_mips.udeb to pool/main/l/linux-kernel-di-mips-2.6/ipv6-modules-2.6.26-2-r4k-ip22-di_1.9lenny5_mips.udeb ipv6-modules-2.6.26-2-r5k-ip32-di_1.9lenny5_mips.udeb to pool/main/l/linux-kernel-di-mips-2.6/ipv6-modules-2.6.26-2-r5k-ip32-di_1.9lenny5_mips.udeb ipv6-modules-2.6.26-2-sb1-bcm91250a-di_1.9lenny5_mips.udeb to pool/main/l/linux-kernel-di-mips-2.6/ipv6-modules-2.6.26-2-sb1-bcm91250a-di_1.9lenny5_mips.udeb ipv6-modules-2.6.26-2-sb1a-bcm91480b-di_1.9lenny5_mips.udeb to pool/main/l/linux-kernel-di-mips-2.6/ipv6-modules-2.6.26-2-sb1a-bcm91480b-di_1.9lenny5_mips.ud
Bug#543443: installation-reports: eventual success on QNAP TS-219
Package: installation-reports Severity: normal -- Package-specific info: Boot method: network Image version: 20090819 daily, http://people.debian.org/~joeyh/d-i/armel/images/20090819-23:51/kirkwood/network-console/qnap/ts-219/ Date: 2009-08-20 Machine: QNAP TS-219 Partitions: Disks are partitioned as 1GB + the rest: testament:~# fdisk -l /dev/sda Disk /dev/sda: 1500.3 GB, 1500301910016 bytes 255 heads, 63 sectors/track, 182401 cylinders Units = cylinders of 16065 * 512 = 8225280 bytes Disk identifier: 0x6e29c273 Device Boot Start End Blocks Id System /dev/sda1 1 122 979933+ 82 Linux swap / Solaris /dev/sda2 123 182401 1464156067+ fd Linux raid autodetect sdb has an identical layout. sdb1 is swap, sda1 is currently unused. sd?2 are combined into md0 with software RAID1: testament:~# cat /proc/mdstat Personalities : [raid1] md0 : active raid1 sda2[2] sdb2[0] 1464155968 blocks [2/1] [U_] [=>...] recovery = 26.6% (390349632/1464155968) finish=216.6min speed=82586K/sec md0 is the only physical volume in a LVM volume group: testament:~# lvdisplay --- Logical volume --- LV Name/dev/testament/root ... LV Size46.56 GB ... --- Logical volume --- LV Name/dev/testament/srv ... LV Size1.32 TB Base System Installation Checklist: [O] = OK, [E] = Error (please elaborate below), [ ] = didn't try it Initial boot: [E] Detect network card:[O] Configure network: [O] Detect CD: [O] Load installer modules: [O] Detect hard drives: [E] Partition hard drives: [O] Install base system:[O] Clock/timezone setup: [O] User/password setup:[O] Install tasks: [O] Install boot loader:[O] Overall install:[O] Comments/Problems: I constructed a serial console cable according to tbm's documentation and used it with a USB <-> 3.3V serial adaptor, which was useful to get the thing booted, but may have caused some of the problems it helped me to solve - the 3.3V power from my laptop's USB was apparently enough to keep the board running even with the AC adaptor unplugged! I flashed the daily build kernel/ramdisk by booting into the QNAP firmware (only the minimal version in flash - I never installed anything from the supplied CDs to the disks) and using the flash-debian script; however, I ended up loading them over tftp instead. Booting with the serial console appeared to stop at the stage of starting init; I never got a shell on the serial port, and d-i never got as far as doing DHCP, for some reason (the server's logs indicate that it never received a request). In the absence of a shell, I couldn't debug this. I eventually booted from tftp with: setenv serverip 10.13.0.1 setenv ipaddr 10.13.0.35 setenv bootargs console=ttyS0,115200n8 root=/dev/ram rw initrd=0xa0,0x90 BOOT_DEBUG=9 tftpboot 0xa0 ts219-initrd.gz tftpboot 0x80 ts219-kernel bootm 0x80 (Changes compared with tbm's instructions: he used the wrong size for the initrd, causing truncation and boot failure; also, I added BOOT_DEBUG to be able to get an early shell.) To work around the failure to run things from init, I exited from the first shell offered, then ran dhclient, debian-installer-startup and debian-installer (in that order) in the second (run just before init), and never actually allowed init to start. With hindsight, running dhclient was probably unnecessary. d-i on the serial console eventually told me it was starting the SSH server, and I switched to SSH for the rest of the installation. At the "partition disks" stage, no disks were found or offered for partitioning; dmesg reported that both SATA links were down. I tried forcing a scan (echo 1 > /sys/class/scsi_host/host2/scan and the same for host3), which caused the Samsung disk in bay 2 (host3) to wake up and be detected as sda; the Western Digital disk in bay 1 (host2) was still not detected. I continued the install onto the Samsung disk only, configuring it for a degraded 2-disk RAID1 array. As a result of the strange hacks I'd done to start d-i, exiting from the main menu with "finish installation" didn't work. I used the "magic sysrq key" on the serial console (Break S Break U Break O) to shut down wthout data loss. I now realise that the detailed installation logs were probably lost during this process; sorry about that. I suspected that the serial console providing partial power to the board might be causing problems, so I disconnected it before the first boot of the installed system. As I'd hoped, both disks were brought up correctly in the installed system, so I duplicated the partition layout from the installed Samsung (now sdb) onto the uninitialized Western Digital (now sda), and added it to the RAID array. -- Please make sure that the hardware-summary log file, and any other installation logs that you think
Bug#543256: tasksel maintainer's perspective
A problem with providing some global way of turning off recommends by default in d-i is that tasks are now being maintained with the implicit and explicit assumption that recommends are installed by default. So, if recommends are turned off, tasks can be broken in both subtle and obvious ways. Frans touched on this in his mail, but AFAIK the set of "required recommends" is much larger than busybox and libgl1-mesa-dri[1]. See tasksel's changelog for 2.79 for many more, and note that more will have a tendancy to be added over time. Also note that the (er, my) inability to keep track of such required recommends is why recommends were turned on in tasksel in the first place. Also, the gnome metapackage is being maintained with similar implicit and explicit assumptions about recommends. And reversing that may not be to the taste of the maintainers or users of the package. For example, I'm about to file a bug requesting that network-manager-gnome be demoted to a recommends. Knowing that recommends will be installed by default gives the maintainer the ability to support such tweaks while still being sure that users who install the package will get a usable and standard gnome system. If the maintainer has to worry about users who choose to disable all recommends, he will be forced to keep network-manager a depends. Thus, supporting users who want to disable all recommends tends to reduce the total configurability of Debian. IMHO the best we can do is to implement the option, but document it as likely to install a broken system unless the user manually knows just what missing bits to install. Or not implement the option, which seems equivilant from here. (BTW, did you notice the annoying samba questions when installing the desktop task? It was an unncessary recommends in cups, which was quite quickly fixed once brought to the package maintainer's attention.) -- see shy jo [1] Which is still listed explicitly in the desktop task, actually. signature.asc Description: Digital signature
Bug#543268: patch
I have a patch for this (attached) but as I was writing it I became unconvinced that this isn't just bloat. After all, the user can be added to groups via preseed/late_command. And most cases that involve the user to groups seem likely to already use preseed/late_command, either to install additional packages, or otherwise configure something that adds groups. Still, passwd/user-extra-groups is not bloat since it makes sense to be able to control what the installer does (rather than having to go in and undo it if you don't want the user in groups). And passwd/user-extra-groups does have a symmetric appeal to it, and the bloat is quite small. -- see shy jo Index: scripts/togit/d-i.conf === --- scripts/togit/d-i.conf (revision 60140) +++ scripts/togit/d-i.conf (working copy) @@ -1614,6 +1614,7 @@ # cannot handle that, so I have to skip this initial revision. All # that gets lost is the first commit message and a s/_/-/, so a branch # does not seem to be called for. +# TODO figure out a better way match /trunk/retriever/choose_mirror/ end match Index: manual/en/appendix/preseed.xml === --- manual/en/appendix/preseed.xml (revision 60066) +++ manual/en/appendix/preseed.xml (working copy) @@ -1198,6 +1198,9 @@ # The user account will be added to some standard initial groups. To # override that, use this. #d-i passwd/user-default-groups string audio cdrom video +# To add the user to additional groups, while keeping them in the +# default groups, use this. +#d-i passwd/user-extra-groups string fuse Index: packages/user-setup/user-setup-apply === --- packages/user-setup/user-setup-apply(revision 60407) +++ packages/user-setup/user-setup-apply(working copy) @@ -141,9 +141,11 @@ fi if [ -n "$USER" ]; then - db_get passwd/user-default-groups - for group in $RET; do - $log $chroot $ROOT adduser "$USER" $group >/dev/null 2>&1 || true + for type in default extra; do + db_get passwd/user-$type-groups + for group in $RET; do + $log $chroot $ROOT adduser "$USER" $group >/dev/null 2>&1 || true + done done fi Index: packages/user-setup/debian/user-setup-udeb.templates === --- packages/user-setup/debian/user-setup-udeb.templates(revision 60407) +++ packages/user-setup/debian/user-setup-udeb.templates(working copy) @@ -22,6 +22,12 @@ Default: audio cdrom dialout floppy video plugdev netdev powerdev scanner bluetooth Description: for internal use only +# Allow adding user to extra groups in addition to the default +Template: passwd/user-extra-groups +Type: string +Default: +Description: for internal use only + Template: passwd/root-login Type: boolean Default: true Index: packages/user-setup/debian/changelog === --- packages/user-setup/debian/changelog(revision 60407) +++ packages/user-setup/debian/changelog(working copy) @@ -1,7 +1,11 @@ user-setup (1.29) UNRELEASED; urgency=low + [ Colin Watson ] * Upgrade to debhelper v7. + [ Joey Hess ] + * Add preseedable passwd/user-extra-groups. Closes: #543268 + -- Colin Watson Fri, 14 Aug 2009 23:31:03 +0100 user-setup (1.28) unstable; urgency=low signature.asc Description: Digital signature
Incomplete upload found in Debian upload queue
Probably you are the uploader of the following file(s) in the Debian upload queue directory: linux-kernel-di-armel-2.6_1.32lenny5.dsc linux-kernel-di-armel-2.6_1.32lenny5.tar.gz This looks like an upload, but a .changes file is missing, so the job cannot be processed. If no .changes file arrives within 23:26:14, the files will be deleted. If you didn't upload those files, please just ignore this message. Greetings, Your Debian queue daemon -- To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Processing of linux-kernel-di-powerpc-2.6_1.48lenny5_multi.changes
linux-kernel-di-powerpc-2.6_1.48lenny5_multi.changes uploaded successfully to localhost along with the files: ide-modules-2.6.26-2-powerpc-di_1.48lenny5_powerpc.udeb pcmcia-storage-modules-2.6.26-2-powerpc64-di_1.48lenny5_powerpc.udeb serial-modules-2.6.26-2-powerpc64-di_1.48lenny5_powerpc.udeb uinput-modules-2.6.26-2-powerpc-di_1.48lenny5_powerpc.udeb pcmcia-modules-2.6.26-2-powerpc64-di_1.48lenny5_powerpc.udeb scsi-extra-modules-2.6.26-2-powerpc64-di_1.48lenny5_powerpc.udeb reiserfs-modules-2.6.26-2-powerpc64-di_1.48lenny5_powerpc.udeb kernel-image-2.6.26-2-powerpc64-di_1.48lenny5_powerpc.udeb scsi-core-modules-2.6.26-2-powerpc64-di_1.48lenny5_powerpc.udeb cdrom-core-modules-2.6.26-2-powerpc-di_1.48lenny5_powerpc.udeb md-modules-2.6.26-2-powerpc64-di_1.48lenny5_powerpc.udeb ata-modules-2.6.26-2-powerpc64-di_1.48lenny5_powerpc.udeb mouse-modules-2.6.26-2-powerpc64-di_1.48lenny5_powerpc.udeb md-modules-2.6.26-2-powerpc-di_1.48lenny5_powerpc.udeb serial-modules-2.6.26-2-powerpc-di_1.48lenny5_powerpc.udeb fat-modules-2.6.26-2-powerpc-di_1.48lenny5_powerpc.udeb jfs-modules-2.6.26-2-powerpc-di_1.48lenny5_powerpc.udeb kernel-image-2.6.26-2-powerpc-di_1.48lenny5_powerpc.udeb usb-modules-2.6.26-2-powerpc64-di_1.48lenny5_powerpc.udeb affs-modules-2.6.26-2-powerpc64-di_1.48lenny5_powerpc.udeb ufs-modules-2.6.26-2-powerpc-di_1.48lenny5_powerpc.udeb usb-storage-modules-2.6.26-2-powerpc-di_1.48lenny5_powerpc.udeb ppp-modules-2.6.26-2-powerpc-di_1.48lenny5_powerpc.udeb floppy-modules-2.6.26-2-powerpc64-di_1.48lenny5_powerpc.udeb crypto-core-modules-2.6.26-2-powerpc64-di_1.48lenny5_powerpc.udeb ppp-modules-2.6.26-2-powerpc64-di_1.48lenny5_powerpc.udeb fancontrol-modules-2.6.26-2-powerpc64-di_1.48lenny5_powerpc.udeb mouse-modules-2.6.26-2-powerpc-di_1.48lenny5_powerpc.udeb ext3-modules-2.6.26-2-powerpc-di_1.48lenny5_powerpc.udeb xfs-modules-2.6.26-2-powerpc64-di_1.48lenny5_powerpc.udeb nic-shared-modules-2.6.26-2-powerpc64-di_1.48lenny5_powerpc.udeb usb-serial-modules-2.6.26-2-powerpc64-di_1.48lenny5_powerpc.udeb floppy-modules-2.6.26-2-powerpc-di_1.48lenny5_powerpc.udeb crypto-dm-modules-2.6.26-2-powerpc64-di_1.48lenny5_powerpc.udeb nic-shared-modules-2.6.26-2-powerpc-di_1.48lenny5_powerpc.udeb multipath-modules-2.6.26-2-powerpc64-di_1.48lenny5_powerpc.udeb sata-modules-2.6.26-2-powerpc64-di_1.48lenny5_powerpc.udeb usb-modules-2.6.26-2-powerpc-di_1.48lenny5_powerpc.udeb linux-kernel-di-powerpc-2.6_1.48lenny5.tar.gz fat-modules-2.6.26-2-powerpc64-di_1.48lenny5_powerpc.udeb loop-modules-2.6.26-2-powerpc64-di_1.48lenny5_powerpc.udeb uinput-modules-2.6.26-2-powerpc64-di_1.48lenny5_powerpc.udeb ata-modules-2.6.26-2-powerpc-di_1.48lenny5_powerpc.udeb nic-extra-modules-2.6.26-2-powerpc-di_1.48lenny5_powerpc.udeb firewire-core-modules-2.6.26-2-powerpc-di_1.48lenny5_powerpc.udeb isofs-modules-2.6.26-2-powerpc-di_1.48lenny5_powerpc.udeb core-modules-2.6.26-2-powerpc64-di_1.48lenny5_powerpc.udeb jfs-modules-2.6.26-2-powerpc64-di_1.48lenny5_powerpc.udeb ext2-modules-2.6.26-2-powerpc-di_1.48lenny5_powerpc.udeb hfs-modules-2.6.26-2-powerpc-di_1.48lenny5_powerpc.udeb nic-pcmcia-modules-2.6.26-2-powerpc64-di_1.48lenny5_powerpc.udeb firewire-core-modules-2.6.26-2-powerpc64-di_1.48lenny5_powerpc.udeb zlib-modules-2.6.26-2-powerpc64-di_1.48lenny5_powerpc.udeb pcmcia-storage-modules-2.6.26-2-powerpc-di_1.48lenny5_powerpc.udeb nic-modules-2.6.26-2-powerpc-di_1.48lenny5_powerpc.udeb nic-pcmcia-modules-2.6.26-2-powerpc-di_1.48lenny5_powerpc.udeb pata-modules-2.6.26-2-powerpc-di_1.48lenny5_powerpc.udeb pata-modules-2.6.26-2-powerpc64-di_1.48lenny5_powerpc.udeb ufs-modules-2.6.26-2-powerpc64-di_1.48lenny5_powerpc.udeb nls-core-modules-2.6.26-2-powerpc-di_1.48lenny5_powerpc.udeb ipv6-modules-2.6.26-2-powerpc-di_1.48lenny5_powerpc.udeb reiserfs-modules-2.6.26-2-powerpc-di_1.48lenny5_powerpc.udeb scsi-common-modules-2.6.26-2-powerpc64-di_1.48lenny5_powerpc.udeb scsi-core-modules-2.6.26-2-powerpc-di_1.48lenny5_powerpc.udeb scsi-extra-modules-2.6.26-2-powerpc-di_1.48lenny5_powerpc.udeb nic-modules-2.6.26-2-powerpc64-di_1.48lenny5_powerpc.udeb input-modules-2.6.26-2-powerpc-di_1.48lenny5_powerpc.udeb crypto-modules-2.6.26-2-powerpc64-di_1.48lenny5_powerpc.udeb core-modules-2.6.26-2-powerpc-di_1.48lenny5_powerpc.udeb nls-core-modules-2.6.26-2-powerpc64-di_1.48lenny5_powerpc.udeb pcmcia-modules-2.6.26-2-powerpc-di_1.48lenny5_powerpc.udeb nic-extra-modules-2.6.26-2-powerpc64-di_1.48lenny5_powerpc.udeb ext3-modules-2.6.26-2-powerpc64-di_1.48lenny5_powerpc.udeb crypto-dm-modules-2.6.26-2-powerpc-di_1.48lenny5_powerpc.udeb crypto-modules-2.6.26-2-powerpc-di_1.48lenny5_powerpc.udeb xfs-modules-2.6.26-2-powerpc-di_1.48lenny5_powerpc.udeb multipath-modules-2.6.26-2-powerpc-di_1.48lenny5_powerpc.udeb ide-modules-2.6.26-2-powerpc64-di_1.48lenny5_powerpc.udeb isofs-modules-2.6.26-2-powerpc64-di_1.48lenny5_
Processing of linux-kernel-di-mips-2.6_1.9lenny5_multi.changes
linux-kernel-di-mips-2.6_1.9lenny5_multi.changes uploaded successfully to localhost along with the files: md-modules-2.6.26-2-r4k-ip22-di_1.9lenny5_mips.udeb ipv6-modules-2.6.26-2-sb1a-bcm91480b-di_1.9lenny5_mips.udeb crypto-dm-modules-2.6.26-2-r4k-ip22-di_1.9lenny5_mips.udeb input-modules-2.6.26-2-sb1a-bcm91480b-di_1.9lenny5_mips.udeb xfs-modules-2.6.26-2-sb1-bcm91250a-di_1.9lenny5_mips.udeb isofs-modules-2.6.26-2-sb1a-bcm91480b-di_1.9lenny5_mips.udeb crypto-modules-2.6.26-2-sb1-bcm91250a-di_1.9lenny5_mips.udeb ide-modules-2.6.26-2-4kc-malta-di_1.9lenny5_mips.udeb usb-modules-2.6.26-2-4kc-malta-di_1.9lenny5_mips.udeb kernel-image-2.6.26-2-r5k-ip32-di_1.9lenny5_mips.udeb crypto-dm-modules-2.6.26-2-sb1-bcm91250a-di_1.9lenny5_mips.udeb reiserfs-modules-2.6.26-2-sb1-bcm91250a-di_1.9lenny5_mips.udeb usb-storage-modules-2.6.26-2-sb1-bcm91250a-di_1.9lenny5_mips.udeb scsi-core-modules-2.6.26-2-sb1a-bcm91480b-di_1.9lenny5_mips.udeb reiserfs-modules-2.6.26-2-r5k-ip32-di_1.9lenny5_mips.udeb fat-modules-2.6.26-2-sb1-bcm91250a-di_1.9lenny5_mips.udeb loop-modules-2.6.26-2-r4k-ip22-di_1.9lenny5_mips.udeb crypto-core-modules-2.6.26-2-r4k-ip22-di_1.9lenny5_mips.udeb crypto-modules-2.6.26-2-r5k-ip32-di_1.9lenny5_mips.udeb crypto-modules-2.6.26-2-4kc-malta-di_1.9lenny5_mips.udeb md-modules-2.6.26-2-sb1a-bcm91480b-di_1.9lenny5_mips.udeb kernel-image-2.6.26-2-r4k-ip22-di_1.9lenny5_mips.udeb scsi-core-modules-2.6.26-2-sb1-bcm91250a-di_1.9lenny5_mips.udeb crypto-modules-2.6.26-2-r4k-ip22-di_1.9lenny5_mips.udeb ipv6-modules-2.6.26-2-r4k-ip22-di_1.9lenny5_mips.udeb scsi-modules-2.6.26-2-sb1a-bcm91480b-di_1.9lenny5_mips.udeb crypto-modules-2.6.26-2-sb1a-bcm91480b-di_1.9lenny5_mips.udeb ide-modules-2.6.26-2-sb1-bcm91250a-di_1.9lenny5_mips.udeb isofs-modules-2.6.26-2-4kc-malta-di_1.9lenny5_mips.udeb nls-core-modules-2.6.26-2-4kc-malta-di_1.9lenny5_mips.udeb multipath-modules-2.6.26-2-4kc-malta-di_1.9lenny5_mips.udeb crypto-dm-modules-2.6.26-2-4kc-malta-di_1.9lenny5_mips.udeb jfs-modules-2.6.26-2-r4k-ip22-di_1.9lenny5_mips.udeb scsi-common-modules-2.6.26-2-sb1a-bcm91480b-di_1.9lenny5_mips.udeb cdrom-core-modules-2.6.26-2-sb1a-bcm91480b-di_1.9lenny5_mips.udeb reiserfs-modules-2.6.26-2-4kc-malta-di_1.9lenny5_mips.udeb sata-modules-2.6.26-2-sb1-bcm91250a-di_1.9lenny5_mips.udeb ipv6-modules-2.6.26-2-sb1-bcm91250a-di_1.9lenny5_mips.udeb input-modules-2.6.26-2-4kc-malta-di_1.9lenny5_mips.udeb md-modules-2.6.26-2-r5k-ip32-di_1.9lenny5_mips.udeb fat-modules-2.6.26-2-sb1a-bcm91480b-di_1.9lenny5_mips.udeb md-modules-2.6.26-2-4kc-malta-di_1.9lenny5_mips.udeb ipv6-modules-2.6.26-2-r5k-ip32-di_1.9lenny5_mips.udeb cdrom-core-modules-2.6.26-2-4kc-malta-di_1.9lenny5_mips.udeb scsi-common-modules-2.6.26-2-sb1-bcm91250a-di_1.9lenny5_mips.udeb jfs-modules-2.6.26-2-r5k-ip32-di_1.9lenny5_mips.udeb scsi-modules-2.6.26-2-sb1-bcm91250a-di_1.9lenny5_mips.udeb multipath-modules-2.6.26-2-sb1-bcm91250a-di_1.9lenny5_mips.udeb nls-core-modules-2.6.26-2-sb1a-bcm91480b-di_1.9lenny5_mips.udeb cdrom-core-modules-2.6.26-2-sb1-bcm91250a-di_1.9lenny5_mips.udeb jfs-modules-2.6.26-2-4kc-malta-di_1.9lenny5_mips.udeb crypto-core-modules-2.6.26-2-r5k-ip32-di_1.9lenny5_mips.udeb usb-modules-2.6.26-2-sb1a-bcm91480b-di_1.9lenny5_mips.udeb kernel-image-2.6.26-2-4kc-malta-di_1.9lenny5_mips.udeb ppp-modules-2.6.26-2-4kc-malta-di_1.9lenny5_mips.udeb loop-modules-2.6.26-2-4kc-malta-di_1.9lenny5_mips.udeb fb-modules-2.6.26-2-sb1a-bcm91480b-di_1.9lenny5_mips.udeb jfs-modules-2.6.26-2-sb1-bcm91250a-di_1.9lenny5_mips.udeb xfs-modules-2.6.26-2-sb1a-bcm91480b-di_1.9lenny5_mips.udeb md-modules-2.6.26-2-sb1-bcm91250a-di_1.9lenny5_mips.udeb sata-modules-2.6.26-2-sb1a-bcm91480b-di_1.9lenny5_mips.udeb kernel-image-2.6.26-2-sb1-bcm91250a-di_1.9lenny5_mips.udeb linux-kernel-di-mips-2.6_1.9lenny5.tar.gz kernel-image-2.6.26-2-sb1a-bcm91480b-di_1.9lenny5_mips.udeb multipath-modules-2.6.26-2-r4k-ip22-di_1.9lenny5_mips.udeb multipath-modules-2.6.26-2-sb1a-bcm91480b-di_1.9lenny5_mips.udeb ipv6-modules-2.6.26-2-4kc-malta-di_1.9lenny5_mips.udeb fb-modules-2.6.26-2-sb1-bcm91250a-di_1.9lenny5_mips.udeb loop-modules-2.6.26-2-sb1a-bcm91480b-di_1.9lenny5_mips.udeb loop-modules-2.6.26-2-r5k-ip32-di_1.9lenny5_mips.udeb xfs-modules-2.6.26-2-4kc-malta-di_1.9lenny5_mips.udeb reiserfs-modules-2.6.26-2-r4k-ip22-di_1.9lenny5_mips.udeb usb-storage-modules-2.6.26-2-sb1a-bcm91480b-di_1.9lenny5_mips.udeb rtc-modules-2.6.26-2-sb1a-bcm91480b-di_1.9lenny5_mips.udeb sata-modules-2.6.26-2-4kc-malta-di_1.9lenny5_mips.udeb loop-modules-2.6.26-2-sb1-bcm91250a-di_1.9lenny5_mips.udeb jfs-modules-2.6.26-2-sb1a-bcm91480b-di_1.9lenny5_mips.udeb xfs-modules-2.6.26-2-r4k-ip22-di_1.9lenny5_mips.udeb input-modules-2.6.26-2-sb1-bcm91250a-di_1.9lenny5_mips.udeb crypto-dm-modules-2.6.26-2-r5k-ip32-di_1.9lenny5_mips.udeb xfs-modules-2.6.26-2-r5k-ip32-di_1.9lenny5_mips.udeb ide-m
Processing of linux-kernel-di-mipsel-2.6_1.8lenny5_multi.changes
linux-kernel-di-mipsel-2.6_1.8lenny5_multi.changes uploaded successfully to localhost along with the files: fat-modules-2.6.26-2-sb1a-bcm91480b-di_1.8lenny5_mipsel.udeb xfs-modules-2.6.26-2-sb1-bcm91250a-di_1.8lenny5_mipsel.udeb fat-modules-2.6.26-2-sb1-bcm91250a-di_1.8lenny5_mipsel.udeb crypto-modules-2.6.26-2-r5k-cobalt-di_1.8lenny5_mipsel.udeb sata-modules-2.6.26-2-sb1-bcm91250a-di_1.8lenny5_mipsel.udeb crypto-modules-2.6.26-2-4kc-malta-di_1.8lenny5_mipsel.udeb rtc-modules-2.6.26-2-sb1-bcm91250a-di_1.8lenny5_mipsel.udeb multipath-modules-2.6.26-2-4kc-malta-di_1.8lenny5_mipsel.udeb loop-modules-2.6.26-2-sb1a-bcm91480b-di_1.8lenny5_mipsel.udeb scsi-common-modules-2.6.26-2-sb1-bcm91250a-di_1.8lenny5_mipsel.udeb ipv6-modules-2.6.26-2-r5k-cobalt-di_1.8lenny5_mipsel.udeb jfs-modules-2.6.26-2-sb1-bcm91250a-di_1.8lenny5_mipsel.udeb nls-core-modules-2.6.26-2-4kc-malta-di_1.8lenny5_mipsel.udeb crypto-modules-2.6.26-2-sb1-bcm91250a-di_1.8lenny5_mipsel.udeb crypto-modules-2.6.26-2-sb1a-bcm91480b-di_1.8lenny5_mipsel.udeb ipv6-modules-2.6.26-2-sb1-bcm91250a-di_1.8lenny5_mipsel.udeb scsi-core-modules-2.6.26-2-sb1-bcm91250a-di_1.8lenny5_mipsel.udeb kernel-image-2.6.26-2-r5k-cobalt-di_1.8lenny5_mipsel.udeb nfs-modules-2.6.26-2-r5k-cobalt-di_1.8lenny5_mipsel.udeb ipv6-modules-2.6.26-2-4kc-malta-di_1.8lenny5_mipsel.udeb md-modules-2.6.26-2-4kc-malta-di_1.8lenny5_mipsel.udeb nls-core-modules-2.6.26-2-r5k-cobalt-di_1.8lenny5_mipsel.udeb input-modules-2.6.26-2-sb1a-bcm91480b-di_1.8lenny5_mipsel.udeb linux-kernel-di-mipsel-2.6_1.8lenny5.tar.gz fat-modules-2.6.26-2-4kc-malta-di_1.8lenny5_mipsel.udeb kernel-image-2.6.26-2-sb1a-bcm91480b-di_1.8lenny5_mipsel.udeb ppp-modules-2.6.26-2-4kc-malta-di_1.8lenny5_mipsel.udeb usb-storage-modules-2.6.26-2-4kc-malta-di_1.8lenny5_mipsel.udeb multipath-modules-2.6.26-2-r5k-cobalt-di_1.8lenny5_mipsel.udeb sata-modules-2.6.26-2-4kc-malta-di_1.8lenny5_mipsel.udeb ppp-modules-2.6.26-2-r5k-cobalt-di_1.8lenny5_mipsel.udeb usb-modules-2.6.26-2-sb1-bcm91250a-di_1.8lenny5_mipsel.udeb usb-modules-2.6.26-2-sb1a-bcm91480b-di_1.8lenny5_mipsel.udeb fb-modules-2.6.26-2-sb1a-bcm91480b-di_1.8lenny5_mipsel.udeb jfs-modules-2.6.26-2-4kc-malta-di_1.8lenny5_mipsel.udeb fb-modules-2.6.26-2-sb1-bcm91250a-di_1.8lenny5_mipsel.udeb crypto-dm-modules-2.6.26-2-4kc-malta-di_1.8lenny5_mipsel.udeb scsi-modules-2.6.26-2-sb1-bcm91250a-di_1.8lenny5_mipsel.udeb ide-modules-2.6.26-2-sb1-bcm91250a-di_1.8lenny5_mipsel.udeb xfs-modules-2.6.26-2-sb1a-bcm91480b-di_1.8lenny5_mipsel.udeb loop-modules-2.6.26-2-sb1-bcm91250a-di_1.8lenny5_mipsel.udeb usb-modules-2.6.26-2-4kc-malta-di_1.8lenny5_mipsel.udeb kernel-image-2.6.26-2-sb1-bcm91250a-di_1.8lenny5_mipsel.udeb ipv6-modules-2.6.26-2-sb1a-bcm91480b-di_1.8lenny5_mipsel.udeb reiserfs-modules-2.6.26-2-r5k-cobalt-di_1.8lenny5_mipsel.udeb cdrom-core-modules-2.6.26-2-r5k-cobalt-di_1.8lenny5_mipsel.udeb loop-modules-2.6.26-2-4kc-malta-di_1.8lenny5_mipsel.udeb crypto-dm-modules-2.6.26-2-r5k-cobalt-di_1.8lenny5_mipsel.udeb crypto-dm-modules-2.6.26-2-sb1-bcm91250a-di_1.8lenny5_mipsel.udeb linux-kernel-di-mipsel-2.6_1.8lenny5.dsc cdrom-core-modules-2.6.26-2-4kc-malta-di_1.8lenny5_mipsel.udeb isofs-modules-2.6.26-2-sb1a-bcm91480b-di_1.8lenny5_mipsel.udeb usb-storage-modules-2.6.26-2-sb1a-bcm91480b-di_1.8lenny5_mipsel.udeb input-modules-2.6.26-2-4kc-malta-di_1.8lenny5_mipsel.udeb md-modules-2.6.26-2-sb1a-bcm91480b-di_1.8lenny5_mipsel.udeb crypto-core-modules-2.6.26-2-r5k-cobalt-di_1.8lenny5_mipsel.udeb md-modules-2.6.26-2-sb1-bcm91250a-di_1.8lenny5_mipsel.udeb ppp-modules-2.6.26-2-sb1-bcm91250a-di_1.8lenny5_mipsel.udeb ppp-modules-2.6.26-2-sb1a-bcm91480b-di_1.8lenny5_mipsel.udeb nls-core-modules-2.6.26-2-sb1a-bcm91480b-di_1.8lenny5_mipsel.udeb multipath-modules-2.6.26-2-sb1-bcm91250a-di_1.8lenny5_mipsel.udeb scsi-common-modules-2.6.26-2-sb1a-bcm91480b-di_1.8lenny5_mipsel.udeb isofs-modules-2.6.26-2-4kc-malta-di_1.8lenny5_mipsel.udeb kernel-image-2.6.26-2-4kc-malta-di_1.8lenny5_mipsel.udeb rtc-modules-2.6.26-2-sb1a-bcm91480b-di_1.8lenny5_mipsel.udeb multipath-modules-2.6.26-2-sb1a-bcm91480b-di_1.8lenny5_mipsel.udeb xfs-modules-2.6.26-2-4kc-malta-di_1.8lenny5_mipsel.udeb reiserfs-modules-2.6.26-2-sb1-bcm91250a-di_1.8lenny5_mipsel.udeb cdrom-core-modules-2.6.26-2-sb1a-bcm91480b-di_1.8lenny5_mipsel.udeb scsi-modules-2.6.26-2-sb1a-bcm91480b-di_1.8lenny5_mipsel.udeb loop-modules-2.6.26-2-r5k-cobalt-di_1.8lenny5_mipsel.udeb input-modules-2.6.26-2-sb1-bcm91250a-di_1.8lenny5_mipsel.udeb ide-modules-2.6.26-2-4kc-malta-di_1.8lenny5_mipsel.udeb sata-modules-2.6.26-2-sb1a-bcm91480b-di_1.8lenny5_mipsel.udeb jfs-modules-2.6.26-2-sb1a-bcm91480b-di_1.8lenny5_mipsel.udeb reiserfs-modules-2.6.26-2-4kc-malta-di_1.8lenny5_mipsel.udeb scsi-core-modules-2.6.26-2-sb1a-bcm91480b-di_1.8lenny5_mipsel.udeb md-modules-2.6.26-2-r5k-cobalt-di_1.8lenny5_mipsel.udeb cdrom-
Processing of linux-kernel-di-i386-2.6_1.76lenny5_multi.changes
linux-kernel-di-i386-2.6_1.76lenny5_multi.changes uploaded successfully to localhost along with the files: cdrom-core-modules-2.6.26-2-686-bigmem-di_1.76lenny5_i386.udeb nic-wireless-modules-2.6.26-2-486-di_1.76lenny5_i386.udeb zlib-modules-2.6.26-2-486-di_1.76lenny5_i386.udeb nic-shared-modules-2.6.26-2-686-bigmem-di_1.76lenny5_i386.udeb mouse-modules-2.6.26-2-686-bigmem-di_1.76lenny5_i386.udeb nic-usb-modules-2.6.26-2-486-di_1.76lenny5_i386.udeb cdrom-core-modules-2.6.26-2-486-di_1.76lenny5_i386.udeb ide-core-modules-2.6.26-2-486-di_1.76lenny5_i386.udeb ppp-modules-2.6.26-2-686-bigmem-di_1.76lenny5_i386.udeb zlib-modules-2.6.26-2-686-bigmem-di_1.76lenny5_i386.udeb scsi-common-modules-2.6.26-2-486-di_1.76lenny5_i386.udeb irda-modules-2.6.26-2-686-bigmem-di_1.76lenny5_i386.udeb nic-modules-2.6.26-2-686-bigmem-di_1.76lenny5_i386.udeb pcmcia-storage-modules-2.6.26-2-686-bigmem-di_1.76lenny5_i386.udeb kernel-image-2.6.26-2-486-di_1.76lenny5_i386.udeb scsi-extra-modules-2.6.26-2-686-bigmem-di_1.76lenny5_i386.udeb isofs-modules-2.6.26-2-486-di_1.76lenny5_i386.udeb multipath-modules-2.6.26-2-686-bigmem-di_1.76lenny5_i386.udeb irda-modules-2.6.26-2-486-di_1.76lenny5_i386.udeb qnx4-modules-2.6.26-2-686-bigmem-di_1.76lenny5_i386.udeb usb-serial-modules-2.6.26-2-686-bigmem-di_1.76lenny5_i386.udeb scsi-extra-modules-2.6.26-2-486-di_1.76lenny5_i386.udeb pcmcia-modules-2.6.26-2-686-bigmem-di_1.76lenny5_i386.udeb nls-core-modules-2.6.26-2-686-bigmem-di_1.76lenny5_i386.udeb jfs-modules-2.6.26-2-686-bigmem-di_1.76lenny5_i386.udeb nic-extra-modules-2.6.26-2-686-bigmem-di_1.76lenny5_i386.udeb ipv6-modules-2.6.26-2-686-bigmem-di_1.76lenny5_i386.udeb ata-modules-2.6.26-2-686-bigmem-di_1.76lenny5_i386.udeb core-modules-2.6.26-2-486-di_1.76lenny5_i386.udeb usb-storage-modules-2.6.26-2-686-bigmem-di_1.76lenny5_i386.udeb ext3-modules-2.6.26-2-686-bigmem-di_1.76lenny5_i386.udeb loop-modules-2.6.26-2-486-di_1.76lenny5_i386.udeb input-modules-2.6.26-2-686-bigmem-di_1.76lenny5_i386.udeb floppy-modules-2.6.26-2-486-di_1.76lenny5_i386.udeb scsi-core-modules-2.6.26-2-486-di_1.76lenny5_i386.udeb ipv6-modules-2.6.26-2-486-di_1.76lenny5_i386.udeb ext2-modules-2.6.26-2-686-bigmem-di_1.76lenny5_i386.udeb nls-core-modules-2.6.26-2-486-di_1.76lenny5_i386.udeb nic-modules-2.6.26-2-486-di_1.76lenny5_i386.udeb ext2-modules-2.6.26-2-486-di_1.76lenny5_i386.udeb usb-modules-2.6.26-2-486-di_1.76lenny5_i386.udeb xfs-modules-2.6.26-2-686-bigmem-di_1.76lenny5_i386.udeb nic-wireless-modules-2.6.26-2-686-bigmem-di_1.76lenny5_i386.udeb linux-kernel-di-i386-2.6_1.76lenny5.tar.gz fat-modules-2.6.26-2-486-di_1.76lenny5_i386.udeb kernel-image-2.6.26-2-686-bigmem-di_1.76lenny5_i386.udeb ide-core-modules-2.6.26-2-686-bigmem-di_1.76lenny5_i386.udeb nic-extra-modules-2.6.26-2-486-di_1.76lenny5_i386.udeb ntfs-modules-2.6.26-2-686-bigmem-di_1.76lenny5_i386.udeb pcmcia-storage-modules-2.6.26-2-486-di_1.76lenny5_i386.udeb parport-modules-2.6.26-2-686-bigmem-di_1.76lenny5_i386.udeb pata-modules-2.6.26-2-486-di_1.76lenny5_i386.udeb plip-modules-2.6.26-2-686-bigmem-di_1.76lenny5_i386.udeb ext3-modules-2.6.26-2-486-di_1.76lenny5_i386.udeb input-modules-2.6.26-2-486-di_1.76lenny5_i386.udeb crypto-dm-modules-2.6.26-2-486-di_1.76lenny5_i386.udeb jfs-modules-2.6.26-2-486-di_1.76lenny5_i386.udeb scsi-modules-2.6.26-2-686-bigmem-di_1.76lenny5_i386.udeb fat-modules-2.6.26-2-686-bigmem-di_1.76lenny5_i386.udeb ide-modules-2.6.26-2-486-di_1.76lenny5_i386.udeb fb-modules-2.6.26-2-486-di_1.76lenny5_i386.udeb serial-modules-2.6.26-2-686-bigmem-di_1.76lenny5_i386.udeb xfs-modules-2.6.26-2-486-di_1.76lenny5_i386.udeb mouse-modules-2.6.26-2-486-di_1.76lenny5_i386.udeb core-modules-2.6.26-2-686-bigmem-di_1.76lenny5_i386.udeb uinput-modules-2.6.26-2-486-di_1.76lenny5_i386.udeb md-modules-2.6.26-2-686-bigmem-di_1.76lenny5_i386.udeb usb-modules-2.6.26-2-686-bigmem-di_1.76lenny5_i386.udeb crypto-modules-2.6.26-2-686-bigmem-di_1.76lenny5_i386.udeb nic-pcmcia-modules-2.6.26-2-686-bigmem-di_1.76lenny5_i386.udeb uinput-modules-2.6.26-2-686-bigmem-di_1.76lenny5_i386.udeb acpi-modules-2.6.26-2-486-di_1.76lenny5_i386.udeb crypto-dm-modules-2.6.26-2-686-bigmem-di_1.76lenny5_i386.udeb reiserfs-modules-2.6.26-2-486-di_1.76lenny5_i386.udeb ntfs-modules-2.6.26-2-486-di_1.76lenny5_i386.udeb md-modules-2.6.26-2-486-di_1.76lenny5_i386.udeb sata-modules-2.6.26-2-686-bigmem-di_1.76lenny5_i386.udeb usb-storage-modules-2.6.26-2-486-di_1.76lenny5_i386.udeb scsi-core-modules-2.6.26-2-686-bigmem-di_1.76lenny5_i386.udeb plip-modules-2.6.26-2-486-di_1.76lenny5_i386.udeb scsi-common-modules-2.6.26-2-686-bigmem-di_1.76lenny5_i386.udeb crypto-core-modules-2.6.26-2-486-di_1.76lenny5_i386.udeb virtio-modules-2.6.26-2-486-di_1.76lenny5_i386.udeb scsi-modules-2.6.26-2-486-di_1.76lenny5_i386.udeb usb-serial-modules-2.6.26-2-486-di_1.76lenny5_i386.udeb pp
Processing of linux-kernel-di-hppa-2.6_1.38lenny5_multi.changes
linux-kernel-di-hppa-2.6_1.38lenny5_multi.changes uploaded successfully to localhost along with the files: usb-storage-modules-2.6.26-2-parisc-di_1.38lenny5_hppa.udeb crypto-core-modules-2.6.26-2-parisc-di_1.38lenny5_hppa.udeb ipv6-modules-2.6.26-2-parisc-di_1.38lenny5_hppa.udeb crypto-modules-2.6.26-2-parisc64-di_1.38lenny5_hppa.udeb linux-kernel-di-hppa-2.6_1.38lenny5.tar.gz ext3-modules-2.6.26-2-parisc-di_1.38lenny5_hppa.udeb loop-modules-2.6.26-2-parisc64-di_1.38lenny5_hppa.udeb cdrom-core-modules-2.6.26-2-parisc-di_1.38lenny5_hppa.udeb md-modules-2.6.26-2-parisc-di_1.38lenny5_hppa.udeb ppp-modules-2.6.26-2-parisc64-di_1.38lenny5_hppa.udeb crypto-core-modules-2.6.26-2-parisc64-di_1.38lenny5_hppa.udeb usb-modules-2.6.26-2-parisc-di_1.38lenny5_hppa.udeb crypto-dm-modules-2.6.26-2-parisc-di_1.38lenny5_hppa.udeb ide-modules-2.6.26-2-parisc-di_1.38lenny5_hppa.udeb multipath-modules-2.6.26-2-parisc-di_1.38lenny5_hppa.udeb scsi-modules-2.6.26-2-parisc64-di_1.38lenny5_hppa.udeb usb-modules-2.6.26-2-parisc64-di_1.38lenny5_hppa.udeb usb-storage-modules-2.6.26-2-parisc64-di_1.38lenny5_hppa.udeb ppp-modules-2.6.26-2-parisc-di_1.38lenny5_hppa.udeb loop-modules-2.6.26-2-parisc-di_1.38lenny5_hppa.udeb linux-kernel-di-hppa-2.6_1.38lenny5.dsc kernel-image-2.6.26-2-parisc-di_1.38lenny5_hppa.udeb nic-modules-2.6.26-2-parisc64-di_1.38lenny5_hppa.udeb input-modules-2.6.26-2-parisc64-di_1.38lenny5_hppa.udeb ext3-modules-2.6.26-2-parisc64-di_1.38lenny5_hppa.udeb ide-modules-2.6.26-2-parisc64-di_1.38lenny5_hppa.udeb crypto-dm-modules-2.6.26-2-parisc64-di_1.38lenny5_hppa.udeb input-modules-2.6.26-2-parisc-di_1.38lenny5_hppa.udeb ipv6-modules-2.6.26-2-parisc64-di_1.38lenny5_hppa.udeb crypto-modules-2.6.26-2-parisc-di_1.38lenny5_hppa.udeb md-modules-2.6.26-2-parisc64-di_1.38lenny5_hppa.udeb cdrom-core-modules-2.6.26-2-parisc64-di_1.38lenny5_hppa.udeb multipath-modules-2.6.26-2-parisc64-di_1.38lenny5_hppa.udeb scsi-modules-2.6.26-2-parisc-di_1.38lenny5_hppa.udeb kernel-image-2.6.26-2-parisc64-di_1.38lenny5_hppa.udeb nic-modules-2.6.26-2-parisc-di_1.38lenny5_hppa.udeb Greetings, Your Debian queue daemon -- To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Processing of linux-kernel-di-alpha-2.6_0.37lenny5_multi.changes
linux-kernel-di-alpha-2.6_0.37lenny5_multi.changes uploaded successfully to localhost along with the files: linux-kernel-di-alpha-2.6_0.37lenny5.dsc multipath-modules-2.6.26-2-alpha-generic-di_0.37lenny5_alpha.udeb usb-serial-modules-2.6.26-2-alpha-generic-di_0.37lenny5_alpha.udeb parport-modules-2.6.26-2-alpha-generic-di_0.37lenny5_alpha.udeb scsi-modules-2.6.26-2-alpha-generic-di_0.37lenny5_alpha.udeb scsi-extra-modules-2.6.26-2-alpha-generic-di_0.37lenny5_alpha.udeb ppp-modules-2.6.26-2-alpha-generic-di_0.37lenny5_alpha.udeb nic-shared-modules-2.6.26-2-alpha-generic-di_0.37lenny5_alpha.udeb cdrom-core-modules-2.6.26-2-alpha-generic-di_0.37lenny5_alpha.udeb zlib-modules-2.6.26-2-alpha-generic-di_0.37lenny5_alpha.udeb sata-modules-2.6.26-2-alpha-generic-di_0.37lenny5_alpha.udeb core-modules-2.6.26-2-alpha-generic-di_0.37lenny5_alpha.udeb fat-modules-2.6.26-2-alpha-generic-di_0.37lenny5_alpha.udeb crypto-dm-modules-2.6.26-2-alpha-generic-di_0.37lenny5_alpha.udeb ipv6-modules-2.6.26-2-alpha-generic-di_0.37lenny5_alpha.udeb ext3-modules-2.6.26-2-alpha-generic-di_0.37lenny5_alpha.udeb md-modules-2.6.26-2-alpha-generic-di_0.37lenny5_alpha.udeb srm-modules-2.6.26-2-alpha-generic-di_0.37lenny5_alpha.udeb nic-extra-modules-2.6.26-2-alpha-generic-di_0.37lenny5_alpha.udeb ide-modules-2.6.26-2-alpha-generic-di_0.37lenny5_alpha.udeb reiserfs-modules-2.6.26-2-alpha-generic-di_0.37lenny5_alpha.udeb ata-modules-2.6.26-2-alpha-generic-di_0.37lenny5_alpha.udeb scsi-common-modules-2.6.26-2-alpha-generic-di_0.37lenny5_alpha.udeb isofs-modules-2.6.26-2-alpha-generic-di_0.37lenny5_alpha.udeb crypto-modules-2.6.26-2-alpha-generic-di_0.37lenny5_alpha.udeb jfs-modules-2.6.26-2-alpha-generic-di_0.37lenny5_alpha.udeb rtc-modules-2.6.26-2-alpha-generic-di_0.37lenny5_alpha.udeb kernel-image-2.6.26-2-alpha-generic-di_0.37lenny5_alpha.udeb usb-storage-modules-2.6.26-2-alpha-generic-di_0.37lenny5_alpha.udeb plip-modules-2.6.26-2-alpha-generic-di_0.37lenny5_alpha.udeb scsi-core-modules-2.6.26-2-alpha-generic-di_0.37lenny5_alpha.udeb ide-core-modules-2.6.26-2-alpha-generic-di_0.37lenny5_alpha.udeb nls-core-modules-2.6.26-2-alpha-generic-di_0.37lenny5_alpha.udeb crypto-core-modules-2.6.26-2-alpha-generic-di_0.37lenny5_alpha.udeb linux-kernel-di-alpha-2.6_0.37lenny5.tar.gz xfs-modules-2.6.26-2-alpha-generic-di_0.37lenny5_alpha.udeb uinput-modules-2.6.26-2-alpha-generic-di_0.37lenny5_alpha.udeb crc-modules-2.6.26-2-alpha-generic-di_0.37lenny5_alpha.udeb fb-modules-2.6.26-2-alpha-generic-di_0.37lenny5_alpha.udeb usb-modules-2.6.26-2-alpha-generic-di_0.37lenny5_alpha.udeb nic-wireless-modules-2.6.26-2-alpha-generic-di_0.37lenny5_alpha.udeb nic-modules-2.6.26-2-alpha-generic-di_0.37lenny5_alpha.udeb Greetings, Your Debian queue daemon -- To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#498143: Please detect non-ISO block devices masquerading as Debian CDs
Frans Pop wrote:
> It would be much nicer if we could somehow display a dialog offering the
> alternative is mounting a CD fails.
To frame my thoughts here, this is to support d-i when invoked from Debian
Live USB sticks - as Debian Live knows the target media when building the
USB image, "try-usb=true" is appended to all generated "usb with d-i"
images.
Thus, their users never require such a prompt. Indeed, if they ever were in
a position to see it, their installation would already be in trouble.
Therefore, whilst I would agree that it would be desirable to ask the user
in that situation, I don't think this additional feature request should
block the underlying support for try-usb. Besides, the only known users who
genuinely need this "trick" right now are Debian Live, and they don't need
require a dialog.
Anyway, updated patch series attached with "boot-installer/parameters.xml"
docs and updated apt-setup changelog.
Regards,
--
,''`.
: :' : Chris Lamb
`. `'` la...@debian.org
`-
From b77e711482cd31392725e31bed8bde724d437058 Mon Sep 17 00:00:00 2001
From: Chris Lamb
Date: Fri, 24 Jul 2009 19:30:46 +0200
Subject: [PATCH 1/7] Add "usb-partition" argument to list-devices for detecting partitions on USB drives. Patch originally by Tormod Volden .
---
packages/debian-installer-utils/debian/changelog |5 +
packages/debian-installer-utils/list-devices | 17 +++--
2 files changed, 20 insertions(+), 2 deletions(-)
diff --git a/packages/debian-installer-utils/debian/changelog b/packages/debian-installer-utils/debian/changelog
index 2979010..213405f 100644
--- a/packages/debian-installer-utils/debian/changelog
+++ b/packages/debian-installer-utils/debian/changelog
@@ -1,11 +1,16 @@
debian-installer-utils (1.72) UNRELEASED; urgency=low
+ [ Colin Watson ]
* Upgrade to debhelper v7.
[ Aurelien Jarno ]
* Also ship other terminfo on GNU/kFreeBSD, they are also used in some
cases (e.g. installation through ssh).
+ [ Chris Lamb ]
+ * Add "usb-partition" argument to list-devices for detecting partitions on
+USB drives. Patch originally by Tormod Volden .
+
-- Colin Watson Thu, 13 Aug 2009 14:52:50 +0100
debian-installer-utils (1.71) unstable; urgency=low
diff --git a/packages/debian-installer-utils/list-devices b/packages/debian-installer-utils/list-devices
index b748be9..2a95b71 100755
--- a/packages/debian-installer-utils/list-devices
+++ b/packages/debian-installer-utils/list-devices
@@ -6,9 +6,9 @@ case $TYPE in
logger -t list-devices "deprecated parameter maybe-floppy"
TYPE=floppy
;;
-cd|disk|partition|floppy|maybe-usb-floppy) ;;
+cd|disk|partition|floppy|maybe-usb-floppy|usb-partition) ;;
*)
- echo "Usage: $0 cd|disk|partition|floppy|maybe-usb-floppy" >&2
+ echo "Usage: $0 cd|disk|partition|floppy|maybe-usb-floppy|usb-partition" >&2
exit 2
;;
esac
@@ -40,6 +40,12 @@ case $TYPE in
# Also allow misdetected USB devices
scan_partition=:
;;
+usb-partition)
+ for x in /sys/block/*/*; do
+ [ -d "$x" ] || continue
+ syspaths="${syspaths:+$syspaths }$x"
+ done
+ ;;
*)
for x in /sys/block/*; do
[ -d "$x" ] || continue
@@ -85,6 +91,13 @@ for x in $syspaths; do
match=:
fi
fi
+ # Disk partitions, but only on USB drives
+ if ! $match && [ "$TYPE" = usb-partition ]; then
+ if device_info env "$devpath" | grep -q '^ID_BUS=usb' && \
+ device_info env "$devpath" | grep -q '^ID_TYPE=disk'; then
+ match=:
+ fi
+ fi
if $match; then
if ! name="$(device_info name "$devpath")"; then
name="$(printf %s "${devpath##*/}" | \
--
1.6.3.3
From 51832db28d3271c140f103aad7e7da8a8585eddf Mon Sep 17 00:00:00 2001
From: Chris Lamb
Date: Fri, 24 Jul 2009 19:42:04 +0200
Subject: [PATCH 2/7] Append " fstype=iso9660" to mounting status messages.
---
packages/cdrom-detect/debian/cdrom-detect.postinst |9 +
packages/cdrom-detect/debian/changelog |4
2 files changed, 9 insertions(+), 4 deletions(-)
diff --git a/packages/cdrom-detect/debian/cdrom-detect.postinst b/packages/cdrom-detect/debian/cdrom-detect.postinst
index da0c1bb..5ead814 100755
--- a/packages/cdrom-detect/debian/cdrom-detect.postinst
+++ b/packages/cdrom-detect/debian/cdrom-detect.postinst
@@ -35,12 +35,12 @@ do
devices="$(list-devices cd; list-devices maybe-usb-floppy)"
for device in $devices; do
if mount -t iso9660 -o ro,exec $device /cdrom; then
- log "CD-ROM mount succeeded: device=$device"
+ log "CD-ROM mount succeeded: device=$device fstype=iso9660"
mounted=1
db_set cdrom-detect/cdrom_device $device
break
else
- log "CD-ROM mount failed: device=$device"
+ log "CD-ROM mount failed: device=$device fstype=iso9660"
fi
done
@@ -102,11 +102,12 @@ do
modprobe $module
fi
if mount -t iso9660 -o ro,exec $device /cdrom; then
- log "CD-ROM mount succeeded: device=$device"
+ log "CD-ROM mount succeeded: device=$device fstype=iso9660"
+ db
Re: Ban of Uwe Bugla from debian mailinglists
Hi, On Montag, 24. August 2009, Alexander Wirt wrote: > Unfortunately I have to announce that we have banned Uwe Bugla from our > mailinglists. In the last days he showed an attitude on our lists that is > not acceptable in any way ([1-4] and more). We already gave him a warning, > but this didn't helped. > > We really don't have anything against a good argument, but such attitude is > neither wanted nor accepted on our lists (see netiquette [5] and our Code > of Conduct [6]). > > This ban will initially last for two weeks. After that period it will be > lifted, but if such events happen again we will reimpose it permanently. Thank you. And keep up the good, and mostly invisible work, Holger signature.asc Description: This is a digitally signed message part.
Re: Ban of Uwe Bugla from debian mailinglists
This one time, at band camp, Alexander Wirt said: > Hi, > > Unfortunately I have to announce that we have banned Uwe Bugla from our > mailinglists. In the last days he showed an attitude on our lists that is not > acceptable in any way ([1-4] and more). We already gave him a warning, > but this didn't helped. Thank you. -- - | ,''`.Stephen Gran | | : :' :sg...@debian.org | | `. `'Debian user, admin, and developer | |`- http://www.debian.org | - signature.asc Description: Digital signature
Ban of Uwe Bugla from debian mailinglists
Hi, Unfortunately I have to announce that we have banned Uwe Bugla from our mailinglists. In the last days he showed an attitude on our lists that is not acceptable in any way ([1-4] and more). We already gave him a warning, but this didn't helped. We really don't have anything against a good argument, but such attitude is neither wanted nor accepted on our lists (see netiquette [5] and our Code of Conduct [6]). This ban will initially last for two weeks. After that period it will be lifted, but if such events happen again we will reimpose it permanently. Alex - Debian Listmaster [1] http://lists.debian.org/msgid-search/200908231951.02602.uwe.bu...@gmx.de [2] http://lists.debian.org/msgid-search/200908232109.02951.uwe.bu...@gmx.de [3] http://lists.debian.org/msgid-search/200908241709.37236.uwe.bu...@gmx.de [4] http://lists.debian.org/msgid-search/200908241841.24956.uwe.bu...@gmx.de [5] http://tools.ietf.org/html/rfc1855 [6] http://www.debian.org/MailingLists/#codeofconduct -- To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Re: Keymap problems in D-I (was: Re: Bugs in the latest Debian Sid installer)
On Mon, Aug 24, 2009 at 06:41:24PM +0200, Uwe Bugla wrote: > Although some people do not like me I do prefer real democratic communities > which are free from such authoritarian fascist no-brains. Thank God we're not a democracy. -- Steve Langasek Give me a lever long enough and a Free OS Debian Developer to set it on, and I can move the world. Ubuntu Developerhttp://www.debian.org/ slanga...@ubuntu.com vor...@debian.org signature.asc Description: Digital signature
Upcoming Lenny point release
Hi, The next Lenny point release (5.0.3) is scheduled for Saturday, September 5th. With the exception of already planned kernel and installer updates, stable NEW will be frozen during the weekend of August 29th - 30th. Regards, Adam -- To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
debconf 1.5.28: Please update debconf PO translation for the package debconf
Hi, You are noted as the last translator of the debconf translation for ...debconf (yes, even that package has debconf strings!). A new string was added so that dialogs that prompt users for media changes when debconf-apt-progress is used (for instance in D-I) have a properly translated title. I would be grateful if you could take the time and update it. To avoid a huge number of bug reports, I suggest you send your updates directly to me as it wouldn't you too long to make the update, including a review. There is no strict deadline as there will probably be several releases of debconf until Squeeze is released. Thanks in advance, # Swedish translation by: # Per Olofsson # Daniel Nylander , 2005 # msgid "" msgstr "" "Project-Id-Version: debian-installer\n" "Report-Msgid-Bugs-To: debc...@packages.debian.org\n" "POT-Creation-Date: 2009-08-24 19:24+0200\n" "PO-Revision-Date: 2006-09-07 23:38+0100\n" "Last-Translator: Daniel Nylander \n" "Language-Team: Swedish \n" "MIME-Version: 1.0\n" "Content-Type: text/plain; charset=UTF-8\n" "Content-Transfer-Encoding: 8bit\n" #. Type: select #. Choices #: ../templates:1001 msgid "Dialog" msgstr "Dialog" #. Type: select #. Choices #: ../templates:1001 msgid "Readline" msgstr "Readline" #. Type: select #. Choices #: ../templates:1001 msgid "Editor" msgstr "Redigerare" #. Type: select #. Choices #: ../templates:1001 msgid "Noninteractive" msgstr "Icke-interaktivt" #. Type: select #. Description #: ../templates:1002 msgid "Interface to use:" msgstr "Gränssnitt att använda:" #. Type: select #. Description #: ../templates:1002 msgid "" "Packages that use debconf for configuration share a common look and feel. " "You can select the type of user interface they use." msgstr "" "Paket som använder debconf för konfigurering delar ett gemensamt utseende. " "Du kan välja vilken sorts användargränssnitt de skall använda." #. Type: select #. Description #: ../templates:1002 msgid "" "The dialog frontend is a full-screen, character based interface, while the " "readline frontend uses a more traditional plain text interface, and both the " "gnome and kde frontends are modern X interfaces, fitting the respective " "desktops (but may be used in any X environment). The editor frontend lets " "you configure things using your favorite text editor. The noninteractive " "frontend never asks you any questions." msgstr "" "Dialogskalet är ett textbaserat fullskärmsgränssnitt medan readline-skalet " "använder ett mer traditionellt ren text-gränssnitt, och både Gnome- och KDE-" "skalen är moderna X-gränssnitt passande respektive skrivbordsmiljöer (men " "kan användas i vilken X-miljö som helst). Textredigeringsskalet låter dig " "konfigurera saker med ditt favorittextredigeringsprogram. Det icke-" "interaktiva skalet ställer aldrig några frågor till dig." #. Type: select #. Choices #: ../templates:2001 msgid "critical" msgstr "kritisk" #. Type: select #. Choices #: ../templates:2001 msgid "high" msgstr "hög" #. Type: select #. Choices #: ../templates:2001 msgid "medium" msgstr "medel" #. Type: select #. Choices #: ../templates:2001 msgid "low" msgstr "låg" #. Type: select #. Description #: ../templates:2002 msgid "Ignore questions with a priority less than:" msgstr "Ignorera frågor med lägre prioritet än:" #. Type: select #. Description #: ../templates:2002 msgid "" "Debconf prioritizes the questions it asks you. Pick the lowest priority of " "question you want to see:\n" " - 'critical' only prompts you if the system might break.\n" "Pick it if you are a newbie, or in a hurry.\n" " - 'high' is for rather important questions\n" " - 'medium' is for normal questions\n" " - 'low' is for control freaks who want to see everything" msgstr "" "Debconf prioriterar frågor den ställer till dig. Välj den lägsta " "prioritetsnivån för frågor du vill se:\n" " - \"kritisk\" frågar dig endast om systemet kan skadas.\n" "Välj den om du är nybörjare eller har bråttom..\n" " - \"hög\" är för ganska viktiga frågor\n" " - \"medel\" är för normala frågor\n" " - \"låg\" är för kontrolltokar som vill se allt som händer" #. Type: select #. Description #: ../templates:2002 msgid "" "Note that no matter what level you pick here, you will be able to see every " "question if you reconfigure a package with dpkg-reconfigure." msgstr "" "Notera att oavsett vilken nivå du väljer här är det möjligt att se varje " "fråga om du konfigurerar om ett paket med dpkg-reconfigure." #. Type: text #. Description #: ../templates:3001 msgid "Installing packages" msgstr "Installerar paket" #. Type: text #. Description #: ../templates:4001 msgid "Please wait..." msgstr "Var god vänta..." #. Type: text #. Description #. This string is the 'title' of dialog boxes that prompt users #. when they need to insert a new medium (most often a CD or DVD) #. to install a package or a collection of packages #: ../templates:6001 msgid "Media change" msgstr "" #~ msgid "Ignore questions with a priority less than..." #~
debconf 1.5.28: Please update debconf PO translation for the package debconf
Hi, You are noted as the last translator of the debconf translation for ...debconf (yes, even that package has debconf strings!). A new string was added so that dialogs that prompt users for media changes when debconf-apt-progress is used (for instance in D-I) have a properly translated title. I would be grateful if you could take the time and update it. To avoid a huge number of bug reports, I suggest you send your updates directly to me as it wouldn't you too long to make the update, including a review. There is no strict deadline as there will probably be several releases of debconf until Squeeze is released. Thanks in advance, # translation of debconf_debian_po.po to Wolof # This file is distributed under the same license as the PACKAGE package. # Copyright (C) YEAR THE PACKAGE'S COPYRIGHT HOLDER. # Mouhamadou Mamoune Mbacke , 2006. # msgid "" msgstr "" "Project-Id-Version: debconf_debian_po\n" "Report-Msgid-Bugs-To: debc...@packages.debian.org\n" "POT-Creation-Date: 2009-08-24 19:24+0200\n" "PO-Revision-Date: 2006-09-09 17:53+\n" "Last-Translator: Mouhamadou Mamoune Mbacke \n" "Language-Team: Wolof \n" "MIME-Version: 1.0\n" "Content-Type: text/plain; charset=UTF-8\n" "Content-Transfer-Encoding: 8bit\n" "X-Generator: KBabel 1.9.1\n" #. Type: select #. Choices #: ../templates:1001 msgid "Dialog" msgstr "Dialog" #. Type: select #. Choices #: ../templates:1001 msgid "Readline" msgstr "Readline" #. Type: select #. Choices #: ../templates:1001 msgid "Editor" msgstr "Editor" #. Type: select #. Choices #: ../templates:1001 msgid "Noninteractive" msgstr "Noninteractive" #. Type: select #. Description #: ../templates:1002 msgid "Interface to use:" msgstr "Interfaas biñuy jëfandikoo:" #. Type: select #. Description #: ../templates:1002 msgid "" "Packages that use debconf for configuration share a common look and feel. " "You can select the type of user interface they use." msgstr "" "Paket yiy jëfandikoo debconfg ci seen komfiguraasioŋ, dañuy niróo jëmmu ak " "melo. Man ngaa tann fasoŋu interfaas bi nga bëgg ñukoy jëfandikoo." #. Type: select #. Description #: ../templates:1002 msgid "" "The dialog frontend is a full-screen, character based interface, while the " "readline frontend uses a more traditional plain text interface, and both the " "gnome and kde frontends are modern X interfaces, fitting the respective " "desktops (but may be used in any X environment). The editor frontend lets " "you configure things using your favorite text editor. The noninteractive " "frontend never asks you any questions." msgstr "" "Dialog ab interfaas bu karakteer la buy fees ekraŋ bi, readline bi moom " "dafay jëfandikoo tekst ordineer bu cosaan, gnome ak kde nak ñoom yu " "interfaas X yu jamonoo lañu, dëppóo ak seeni biro (waaye maneesna leena " "jëfandikoo ci béppu barab X). Editor nak dana la may nga jëfandikoo sa " "editoru tekst bila daxal kir komfigure linga bëgg. noninteractive nak dula " "laaj mukk benn laaj." #. Type: select #. Choices #: ../templates:2001 msgid "critical" msgstr "bu garaaw" #. Type: select #. Choices #: ../templates:2001 msgid "high" msgstr "bu kawe" #. Type: select #. Choices #: ../templates:2001 msgid "medium" msgstr "bu diggdóomu" #. Type: select #. Choices #: ../templates:2001 msgid "low" msgstr "bu suufe" #. Type: select #. Description #: ../templates:2002 msgid "Ignore questions with a priority less than:" msgstr "jéllalé laaj yi am piriyorite yu yées:" #. Type: select #. Description #: ../templates:2002 msgid "" "Debconf prioritizes the questions it asks you. Pick the lowest priority of " "question you want to see:\n" " - 'critical' only prompts you if the system might break.\n" "Pick it if you are a newbie, or in a hurry.\n" " - 'high' is for rather important questions\n" " - 'medium' is for normal questions\n" " - 'low' is for control freaks who want to see everything" msgstr "" "Debconf dafay jox laaj yimu lay laaj ay piritorite. Tannal piriyorite bi " "gëna suufe bi ngay bëgg diko gis:\n" " -'bu garaaw' dula laaj dara fiiyak sistem bi nekkul di bëgga dammu.\n" " Tann ko bu fekkee ab saabees nga, walla nga yàkkamti.\n" " -'bu kawe' ngir rekk laaj yi am solo lool.\n" " 'bu diggdóomu' ngir laaj yu ordineer\n" " 'bu suufe' ngir ñi nga xam ne dañuy bëgg di konturle leppu" #. Type: select #. Description #: ../templates:2002 msgid "" "Note that no matter what level you pick here, you will be able to see every " "question if you reconfigure a package with dpkg-reconfigure." msgstr "" "Xamal ne tolluwaay boo man di tann fii, du tee ngay mana gis laaj yéppu, bu " "fekkee dangay komfigure ab paket ak dpkg-reconfigure." #. Type: text #. Description #: ../templates:3001 msgid "Installing packages" msgstr "Mi ngi istale paket yi" #. Type: text #. Description #: ../templates:4001 msgid "Please wait..." msgstr "Muñal tuut..." #. Type: text #. Description #. This string is the 'title' of dialog boxes that prompt users #. when they need to insert a new medium (most
Re: Keymap problems in D-I (was: Re: Bugs in the latest Debian Sid installer)
Am Montag 24 August 2009 18:11:55 schrieb Wouter Verhelst: > On Mon, Aug 24, 2009 at 05:09:37PM +0200, Uwe Bugla wrote: > > Am Montag 24 August 2009 16:11:10 schrieb Wouter Verhelst: > > > On Mon, Aug 24, 2009 at 02:33:31PM +0200, Uwe Bugla wrote: > > > > If I do describe accurately a problem dealing with netinst image, > > > > and, as a consequence, I am asked to perform a test with a netboot > > > > image (which has technologically nothing to do with the netinst one > > > > > > This is so utterly and completely wrong it's not even funny. > > > > > > 99% of what's on the installer images is the same from one flavour to > > > the other. The only difference between flavours are the default > > > retrievers that are put on the image, the drivers that are available, > > > and what part of the base system is available. It *does* > > > technologically have a *lot* to do with the netinst one. > > > > Non-qualified superficial nonsense of a "would-like-to"-ranter! > > Er. I've actually *worked* on the installer. Not as much as I'd like, > but sure as hell more than you. > > > > It was a perfectly reasonable debugging attempt by Christian to see > > > whether he could reproduce it by using the image that was easiest for > > > him to try. > > > > Nonsense! See first point in how far! > > Rotfl. > > > > He didn't ask you to perform a test with a netboot image specifically, > > > > Lie! He in fact did! > > Not a lie; at most, a statement that wasn't clear enough so that you'd > understand what I meant. > > > > but rather asked you to perform a test with a daily build, to see > > > whether the problem still existed in the latest version. > > > > Crap! If noone did any kind of intervention on the images in the time > > window of some days, everything that changes is the date, but not the > > contents! > > Are you claiming that no development is happening on Debian at all? > > Any kind of change could have occurred in the mean time, and there's no > way that Christian (or, in fact, anyone) can know all of them by heart. > > > Miguels posting was the best prove that ever could have happened to > > me, showing that some things within the Debian installer developers do > > not work in practice as expected! > > Rotfl. > > > > Since these are > > > easiest to test with netboot images, it's not unreasonable for him to > > > point you to the netboot image -- though you may want to use something > > > else, and report on that. > > > > Your mental incapability easily shows that you even do not know the > > difference between a netboot and a netinst image (although I have > > explained it now for more than once, damn stupid!): > > I do not need to be 'explained' what the difference is between two > flavours of software *that I've worked on* by a person who hasn't and > whose name does not even remotely ring any bell to me in regards to said > software, thank you very much. > > > I would call that the highest possible state of cretinism (using > > medical terminology). Go to find a doctor please! > > > > > The fact that you *think* you know what you're talking about does not, > > > in any way, imply that you do; and it *certainly* does not give you the > > > right to be rude, to start calling people names, and to tell them that > > > they are incompetent. > > > > Leave that point up to me and please go to find a doctor, OK! > > > > > If you still believe you do, then kindly fuck off. > > > > Non-qualified stupid rant from the first word to the last - it's your > > expected task to fuck off from here - not me! > > No, it's yours. > > Listmasters: please take appropriate action regarding this user. He's > been extremely abusive to multiple developers, does not want to listen > to reason, has shown repeated proofs of arrogance and a superiority > complex, and is in general disruptive to normal discussion on the list. > > Thanks, Debian Listmasters! in the utmost important first state of priority that ever can be imagined we should ban fascist reactionary brains like Wouter Verhelst from everything that has to do with Debian or Linux.. Although some people do not like me I do prefer real democratic communities which are free from such authoritarian fascist no-brains. Cheers and best regards Uwe P. S.: Still enjoying Debian Sid - one of the best distros that I know since years. in spite of all the incredible human crap spread around here causing me nothing but pain -- To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Re: Keymap problems in D-I (was: Re: Bugs in the latest Debian Sid installer)
On Mon, Aug 24, 2009 at 05:09:37PM +0200, Uwe Bugla wrote: > Am Montag 24 August 2009 16:11:10 schrieb Wouter Verhelst: > > On Mon, Aug 24, 2009 at 02:33:31PM +0200, Uwe Bugla wrote: > > > If I do describe accurately a problem dealing with netinst image, and, > > > as a consequence, I am asked to perform a test with a netboot image > > > (which has technologically nothing to do with the netinst one > > > > This is so utterly and completely wrong it's not even funny. > > > > 99% of what's on the installer images is the same from one flavour to > > the other. The only difference between flavours are the default > > retrievers that are put on the image, the drivers that are available, > > and what part of the base system is available. It *does* technologically > > have a *lot* to do with the netinst one. > > Non-qualified superficial nonsense of a "would-like-to"-ranter! Er. I've actually *worked* on the installer. Not as much as I'd like, but sure as hell more than you. > > It was a perfectly reasonable debugging attempt by Christian to see > > whether he could reproduce it by using the image that was easiest for > > him to try. > > Nonsense! See first point in how far! Rotfl. > > He didn't ask you to perform a test with a netboot image specifically, > > Lie! He in fact did! Not a lie; at most, a statement that wasn't clear enough so that you'd understand what I meant. > > but rather asked you to perform a test with a daily build, to see > > whether the problem still existed in the latest version. > > Crap! If noone did any kind of intervention on the images in the time > window of some days, everything that changes is the date, but not the > contents! Are you claiming that no development is happening on Debian at all? Any kind of change could have occurred in the mean time, and there's no way that Christian (or, in fact, anyone) can know all of them by heart. > Miguels posting was the best prove that ever could have happened to > me, showing that some things within the Debian installer developers do > not work in practice as expected! Rotfl. > > Since these are > > easiest to test with netboot images, it's not unreasonable for him to > > point you to the netboot image -- though you may want to use something > > else, and report on that. > > Your mental incapability easily shows that you even do not know the > difference between a netboot and a netinst image (although I have > explained it now for more than once, damn stupid!): I do not need to be 'explained' what the difference is between two flavours of software *that I've worked on* by a person who hasn't and whose name does not even remotely ring any bell to me in regards to said software, thank you very much. > I would call that the highest possible state of cretinism (using > medical terminology). Go to find a doctor please! > > > The fact that you *think* you know what you're talking about does not, > > in any way, imply that you do; and it *certainly* does not give you the > > right to be rude, to start calling people names, and to tell them that > > they are incompetent. > > Leave that point up to me and please go to find a doctor, OK! > > > If you still believe you do, then kindly fuck off. > > Non-qualified stupid rant from the first word to the last - it's your > expected task to fuck off from here - not me! No, it's yours. Listmasters: please take appropriate action regarding this user. He's been extremely abusive to multiple developers, does not want to listen to reason, has shown repeated proofs of arrogance and a superiority complex, and is in general disruptive to normal discussion on the list. Thanks, -- The biometric identification system at the gates of the CIA headquarters works because there's a guard with a large gun making sure no one is trying to fool the system. http://www.schneier.com/blog/archives/2009/01/biometrics.html signature.asc Description: Digital signature
Re: Your attitude on debian mailinglists
Am Montag 24 August 2009 17:26:06 schrieben Sie: > Hi Uwe, > > I'm writing to you in my role as one of the debian listmasters. We > currently have several complaints from users about your behaviour on the > debian-boot mailinglist. I took a look on some of your mails (for example > <200908232109.02951.uwe.bu...@gmx.de>), that type of mails are really > unacceptable behaviour on your mailinglist. You may want to take a look on > the netiquette [1] or our code of conduct [2] before sending mails to one > of our mailinglists. > > This mails is some kind of a warning, if complaints against you continue I > will have ban you from the according mailinglist, if they even continue > after that I will have to ban you from lists.debian.org at all. > > I really hope that this is not neccessary. Please come back to a normal > discussion style. > > Thanks in advance > > Alex - Debian Listmaster > > [1] http://tools.ietf.org/html/rfc1855 > [2] http://www.debian.org/MailingLists/#codeofconduct Alex, unfortunately I cannot reproduce your above link for technical reasons. (i. e. for example what please?). Of course I do accept repression against me for going too far losing temper - no discussion about that. But on the other hand it would be nothing else but highly democratic in the sense of the meaning to give up protectionism of arrogant and stupid ignorant developers like Christian Perrier. If this is not being taken into consideration, bans against me and others are nothing but fascist behaviour in the end... 1. We do not live in the Roman Empire any longer (i. e. Quod licet Iovi non licet Bovi is obsolete, crap of the history) 2. Democracy means "Freedom of attitudes". Who thinks different is completely displaced here and elsewhere. 3. In fact I do respect netiquettes in the normal cases. Buit if "Nettiquettes" mean nothing else than protectionism of arrogant and stupid incapable people then nettiquettes are bunk, at least in my eyes. Cheers Uwe P. S.: Every fish stinks starting from the HEAD down to the TAIL, not vice versa! -- To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#543256: Make installing recommends optional
Hello Frans, On Sun, Aug 23, 2009 at 7:25 PM, Frans Pop wrote: > Attached patches (untested, but straightforward) for three components: > - base-installer, where the question is asked (at medium priority) and APT > is configured accordingly; the setting will persist for the installed > system; > - di-utils: apt-install will now respect the global setting instead of > always ignoring Recommends; > - pkgsel: same, and drop now redundant option to include Recommends for > "include" (preseeded additional) packages. [...] I enjoyed the patches a lot. The only thing I guess we might consider doing is loggin when pkgsel/include/install-recommends is used. This can help people to notice that the behaviour has change and that they need to update their preseeding files. In this case I think it is worth since it will be quite difficult to user to notice it otherwise. > I see two main advantages to going this way: > - empower our more professional and experienced users; > - D-I will be a lot more consistent, instead of some components behaving > one way and some the other. +1 -- Otavio Salvador O.S. Systems E-mail: ota...@ossystems.com.br http://www.ossystems.com.br Mobile: +55 53 9981-7854 http://projetos.ossystems.com.br -- To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Re: Keymap problems in D-I (was: Re: Bugs in the latest Debian Sid installer)
Am Montag 24 August 2009 16:11:10 schrieb Wouter Verhelst: > On Mon, Aug 24, 2009 at 02:33:31PM +0200, Uwe Bugla wrote: > > If I do describe accurately a problem dealing with netinst image, and, > > as a consequence, I am asked to perform a test with a netboot image > > (which has technologically nothing to do with the netinst one > > This is so utterly and completely wrong it's not even funny. > > 99% of what's on the installer images is the same from one flavour to > the other. The only difference between flavours are the default > retrievers that are put on the image, the drivers that are available, > and what part of the base system is available. It *does* technologically > have a *lot* to do with the netinst one. Non-qualified superficial nonsense of a "would-like-to"-ranter! > It was a perfectly reasonable debugging attempt by Christian to see > whether he could reproduce it by using the image that was easiest for > him to try. Nonsense! See first point in how far! > He didn't ask you to perform a test with a netboot image specifically, Lie! He in fact did! > but rather asked you to perform a test with a daily build, to see > whether the problem still existed in the latest version. Crap! If noone did any kind of intervention on the images in the time window of some days, everything that changes is the date, but not the contents! Miguels posting was the best prove that ever could have happened to me, showing that some things within the Debian installer developers do not work in practice as expected! > Since these are > easiest to test with netboot images, it's not unreasonable for him to > point you to the netboot image -- though you may want to use something > else, and report on that. Your mental incapability easily shows that you even do not know the difference between a netboot and a netinst image (although I have explained it now for more than once, damn stupid!): I would call that the highest possible state of cretinism (using medical terminology). Go to find a doctor please! > The fact that you *think* you know what you're talking about does not, > in any way, imply that you do; and it *certainly* does not give you the > right to be rude, to start calling people names, and to tell them that > they are incompetent. Leave that point up to me and please go to find a doctor, OK! > If you still believe you do, then kindly fuck off. Non-qualified stupid rant from the first word to the last - it's your expected task to fuck off from here - not me! Uwe -- To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Re: Keymap problems in D-I (was: Re: Bugs in the latest Debian Sid installer)
Am Montag 24 August 2009 14:46:18 schrieb Samuel Thibault: > Uwe Bugla, le Mon 24 Aug 2009 14:33:31 +0200, a écrit : > > If I do describe accurately a problem dealing with netinst image, and, as > > a consequence, I am asked to perform a test with a netboot image (which > > has technologically nothing to do with the netinst one - I do not have > > discless workstations and I do not have NICs with boot PROMs), this is a > > gesture that doesn't even intend to solve the problem itself, but instead > > tries to play it down with the proved intention that I give up filing > > bugs. > > ??!! > > Asking for checking with another kind of image is just the best way to > check whether the problem is in the common content of them or somewhere > in the difference between them. So such test is definitely a good thing > to do. Sounds correct theoretically, but in this special case is untrue unfortunately! The solution of the problem would have been to immediately have a look whether one of the following packages is part of the netinst image: Either: a. console-data plus console-common or even b. console-setup It was me to tell Christian that performing an install of a. after the first reboot (i. e. TOO LATE in so far as this MUST be part of the basic installation) solves the problem. It was Frans Pop telling Christian to have a look whether console-setup is part of the netinst image. In fact Christian did neither follow a. nor did he follow b.! > > This is just one example of Mr. Perriers behaviour far beyond of good and > > bad and this is the reason why I lose temper and thus decide not to > > cooperate with him any longer > > I fear you won't find many people to work with. Googling a bit gives me > a lot of results where developers have lost patience with you. Nothing but superficial verbal crap! Next time please ask me before you intend to use anything like that against me, or I will strictly ignore you for being superficial cause I hate superficial people! Otherwise stay quiet please! In the one case I helped to get rid of an incapable developer called Manu Abraham responsible for a card support discontinuity of TwinHan clones (DVB cards) for an amount of three kernels, i. e. 9 (!) months (2.6.14, 2.6.15, 2.6.16). This guy does not play his tricks against people much more intelligent and capable than he himself will ever be. In so far my engagement was not in vain In the second case I built up some public protest against a maintainer who is known to produce unusable kernels by winking through untested crap patches in an utmost sensitiive area called networking. His name is David S. Miller. I can show you postings where Linus Torvalds is putting tons of shit on David. The only difference is: At least in some parts of the Linux society we do not live in a context with democratic self-understanding. A quite reactionary principle rules instead which was described by the old Romans as follows: "Quod licet Jovi non licet Bovi!" That sounds real imbearable not only for persons like me but that's reality. Fact meanwhile is: Miller has become careful now, and that's exactly the behaviour that I intended. > > a. I as user (administrator) give a precise description of the problem > > that I have. Two or three feedback questions come back in some cases > > asking me to describe the thing more precisely if I am not good enough > > doing the description. > > b. But then the time is right to take action as far as the developer's > > part is concerned. > What you're forgetting is at least two things: > > - the developer may have no idea where the problem is, and thus can of > course _not_ take any action but asking for more tests. He received two hints from two sides - so forget about that point.. > - the developer may not have the time to take action _immediately_ and > thus asks for more tests In that specific case more tests are completely irrelevant, so your point of view is nothing but irrelevant, Samuel. > so that when he gets some time he will have > more clues about the issue. Acting this way asks for more time from > you, yes, but overall the problem can be fixed sooner, as the > developer can then take much more appropriate action. > > > I guess there are far better developers than Christian Perrier, not only > > as part of the Debian community. > > When reading your mails they'll probably just refuse to interact with > you. Their bad luck - not mine! I do prefer real men with butts in their trousers. Damn wimps are not welcome at all :) :) > Samuel Uwe -- To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Re: Keymap problems in D-I (was: Re: Bugs in the latest Debian Sid installer)
On Mon, Aug 24, 2009 at 02:33:31PM +0200, Uwe Bugla wrote: > If I do describe accurately a problem dealing with netinst image, and, > as a consequence, I am asked to perform a test with a netboot image > (which has technologically nothing to do with the netinst one This is so utterly and completely wrong it's not even funny. 99% of what's on the installer images is the same from one flavour to the other. The only difference between flavours are the default retrievers that are put on the image, the drivers that are available, and what part of the base system is available. It *does* technologically have a *lot* to do with the netinst one. It was a perfectly reasonable debugging attempt by Christian to see whether he could reproduce it by using the image that was easiest for him to try. He didn't ask you to perform a test with a netboot image specifically, but rather asked you to perform a test with a daily build, to see whether the problem still existed in the latest version. Since these are easiest to test with netboot images, it's not unreasonable for him to point you to the netboot image -- though you may want to use something else, and report on that. The fact that you *think* you know what you're talking about does not, in any way, imply that you do; and it *certainly* does not give you the right to be rude, to start calling people names, and to tell them that they are incompetent. If you still believe you do, then kindly fuck off. -- The biometric identification system at the gates of the CIA headquarters works because there's a guard with a large gun making sure no one is trying to fool the system. http://www.schneier.com/blog/archives/2009/01/biometrics.html signature.asc Description: Digital signature
Re: Keymap problems in D-I (was: Re: Bugs in the latest Debian Sid installer)
Uwe Bugla, le Mon 24 Aug 2009 14:33:31 +0200, a écrit : > If I do describe accurately a problem dealing with netinst image, and, as a > consequence, I am asked to perform a test with a netboot image (which has > technologically nothing to do with the netinst one - I do not have discless > workstations and I do not have NICs with boot PROMs), this is a gesture that > doesn't even intend to solve the problem itself, but instead tries to play it > down with the proved intention that I give up filing bugs. ??!! Asking for checking with another kind of image is just the best way to check whether the problem is in the common content of them or somewhere in the difference between them. So such test is definitely a good thing to do. > This is just one example of Mr. Perriers behaviour far beyond of good and bad > and this is the reason why I lose temper and thus decide not to cooperate > with > him any longer I fear you won't find many people to work with. Googling a bit gives me a lot of results where developers have lost patience with you. > a. I as user (administrator) give a precise description of the problem that I > have. Two or three feedback questions come back in some cases asking me to > describe the thing more precisely if I am not good enough doing the > description. > b. But then the time is right to take action as far as the developer's part > is > concerned. What you're forgetting is at least two things: - the developer may have no idea where the problem is, and thus can of course _not_ take any action but asking for more tests. - the developer may not have the time to take action _immediately_ and thus asks for more tests so that when he gets some time he will have more clues about the issue. Acting this way asks for more time from you, yes, but overall the problem can be fixed sooner, as the developer can then take much more appropriate action. > I guess there are far better developers than Christian Perrier, not only as > part of the Debian community. When reading your mails they'll probably just refuse to interact with you. Samuel -- To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Re: Keymap problems in D-I (was: Re: Bugs in the latest Debian Sid installer)
Am Montag 24 August 2009 02:02:36 schrieb Steve McIntyre: > Uwe Bugla wrote: > > A totally unnecessary personally abusive email targeted at a valued > Debian developer. I refuse to dignify the message by quoting any of > it. > > This kind of abusive message has no place within the Debian community, > and especially not targeted publically at a well-respected Debian > developer working on his own time to try and solve a problem. I have > contacted the Debian listmasters about this mail already. Do whatever you may wish about my mail. I do not mind for one second. If I do describe accurately a problem dealing with netinst image, and, as a consequence, I am asked to perform a test with a netboot image (which has technologically nothing to do with the netinst one - I do not have discless workstations and I do not have NICs with boot PROMs), this is a gesture that doesn't even intend to solve the problem itself, but instead tries to play it down with the proved intention that I give up filing bugs. This is just one example of Mr. Perriers behaviour far beyond of good and bad and this is the reason why I lose temper and thus decide not to cooperate with him any longer The other part is: This has become a nearly endless thread, and I am not used to that kind of rant. The procedure that I am used to is the following: a. I as user (administrator) give a precise description of the problem that I have. Two or three feedback questions come back in some cases asking me to describe the thing more precisely if I am not good enough doing the description. b. But then the time is right to take action as far as the developer's part is concerned. c. Then I can try the new resultt. d. And so on... But nothing of that "taking real action" happened: Except of endless seeming ranting and systematically playing down my descriptions giving me the impression that my described bugs ain't no bugs at all I cannot see any progress or attempt to really solve the described problems. Instead of that I am expected to reinstall my workstations (with incompatible disk images additionally - just imagine!) and thus throwing away hours of time for absolutely nothing. And if I refuse to do that because Mister Perriers logic at least to me appears more than strange and adventurous, if not to say completely aside, I am of course accused to be non-cooperative - how ridiculous! If I just calculate the enormous amount of time I spent on writing the bug reports with the one and only effect to face a discussion whether the bug I described is or isn't a bug at all then this output is a real poor one. That's all for today so far. I guess there are far better developers than Christian Perrier, not only as part of the Debian community. I would prefer to work with them on the described issues. Cheers Uwe Happy enlargement of your critical mind! -- To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Re: Bug#543256: Make installing recommends optional
On Mon, Aug 24, 2009 at 12:28:00AM -0700, Steve Langasek wrote: > On Mon, Aug 24, 2009 at 09:15:59AM +0200, Bj?rn Mork wrote: > > > I think the use case is users who are being control freaks about the set > > > of > > > packages on their systems. If the set of packages being pulled in as > > > recommends is *wrong* (they don't fit the Policy definition of > > > Recommends), > > > bugs should be filed against those packages and be fixed. If the set of > > > packages is *right*, then there's no good reason to give users a big > > > "ignore > > > Policy" button at install time. > > > The number of "yes, we want this" answers shows that the current set is > > wrong. > > No, it doesn't; all it shows is that there are people who are willing to > complain about installation of Recommends by default. They're complaining for no reason whatsoever? > > I'm hesitating, and have chosen to set APT::Install-Recommends False > > instead. > > I think that's self-evidently the wrong solution. If you don't want > avahi-daemon installed, you can uninstall that one package or use equivs or > do a variety of other things. It doesn't make sense to ignore all package > Recommends just because there's one particular package you don't want on > your system. For me, it's not one package, it's a lot of packages. Taking one example, openssh-server, if I install recommends I get about six packages I really, *really* don't want on all my servers. (That's one of the less annoying examples; other things I've installed pull in services as recommends, I believe avahi-daemon has crept in at one time or another). I'm not about to start listing dozens (probably hundreds, taken across all my machines) of packages in my manifests as "don't install this... and this... and this...". I do, however, recognise that I probably qualify as producing "unusual installations", so filing tons of bugs saying that practically every Recommends: entry in the archive is inappropriate just doesn't seem reasonable. I see "install no recommends" as an "I'm an unusual installation" button; putting that into the d-i UI is probably not really important (if you're unusual installation, you should know enough about preseeding to be able to handle that). It definitely needs to exist, though; if we make it impossible to avoid installing recommends, why bother with the distinction at all and just stick everything in Depends? - Matt -- To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Re: Bug#543256: Make installing recommends optional
On Mon, Aug 24, 2009 at 09:15:59AM +0200, Bjørn Mork wrote: > > I think the use case is users who are being control freaks about the set of > > packages on their systems. If the set of packages being pulled in as > > recommends is *wrong* (they don't fit the Policy definition of Recommends), > > bugs should be filed against those packages and be fixed. If the set of > > packages is *right*, then there's no good reason to give users a big "ignore > > Policy" button at install time. > The number of "yes, we want this" answers shows that the current set is > wrong. No, it doesn't; all it shows is that there are people who are willing to complain about installation of Recommends by default. > One example just out of my head: I've found that it is nearly impossible > to avoid avahi-daemon if APT::Install-Recommends is true. There are > multiple completely unrelated (IMHO) packages recommending it, like > sane-utils and rhythmbox. But are these bugs? I don't think the rhythmbox one is a bug. I'm not sure if the sane-utils one is a bug. > I guess a system without avahi-daemon is pretty unusual, given the number > of recommends pointing in that direction. That's not really a relevant measure of whether the Recommends are correct. > Should I start filing bugs anyway? Discussion on debian-devel first may be a better way to proceed. > I'm hesitating, and have chosen to set APT::Install-Recommends False > instead. I think that's self-evidently the wrong solution. If you don't want avahi-daemon installed, you can uninstall that one package or use equivs or do a variety of other things. It doesn't make sense to ignore all package Recommends just because there's one particular package you don't want on your system. -- Steve Langasek Give me a lever long enough and a Free OS Debian Developer to set it on, and I can move the world. Ubuntu Developerhttp://www.debian.org/ slanga...@ubuntu.com vor...@debian.org signature.asc Description: Digital signature
Re: Bug#543256: Make installing recommends optional
Steve Langasek writes: > I think the use case is users who are being control freaks about the set of > packages on their systems. If the set of packages being pulled in as > recommends is *wrong* (they don't fit the Policy definition of Recommends), > bugs should be filed against those packages and be fixed. If the set of > packages is *right*, then there's no good reason to give users a big "ignore > Policy" button at install time. The number of "yes, we want this" answers shows that the current set is wrong. I think the problem is that I as an administrator don't know whether my installation is "unusual" or not, making it hard to know whether I should file a bug against an unwanted Recommends or not. In fact, recommending is self-fulfilling. Only the unusual installations will avoid installing the recommended package... One example just out of my head: I've found that it is nearly impossible to avoid avahi-daemon if APT::Install-Recommends is true. There are multiple completely unrelated (IMHO) packages recommending it, like sane-utils and rhythmbox. But are these bugs? I guess a system without avahi-daemon is pretty unusual, given the number of recommends pointing in that direction. Should I start filing bugs anyway? I'm hesitating, and have chosen to set APT::Install-Recommends False instead. Bjørn -- To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
