Bug#380272: kernel-image-2.6-686-smp: cpqarray module fails to detect arrays
Hi macs, On Friday 28 July 2006 20:58, you wrote: > this is an not recommended local workaround, > you will have to take care of your own kernel security upgrade. I am aware of this, I am trying to be as helpful as possible and I do not believe there are any other local workarounds that will work, please prove me wrong. I am capable of updating the kernel as necessary but would much prefer the fix to be integrated into the official sources. If you are unwilling to make a change that I know works, I will file a bug report with the kernel developers instead. I know that pre 2.6.15 kernels do work as expected, I just dont have the kernel development experience to attempt to fix this as a module, so building it into the kernel works for me and I will go with that. > please answer to the requested questions or your bugreport is useless. I have already answered all of your questions. Have I missed any? Please read my responses more carefully before criticizing the bug report. Joshua -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#380411: 3c59x broken after swsuspend
Package: linux-2.6 Version: 2.6.17-4 after hibernate, my 3Com Corporation 3c556 Hurricane CardBus [Cyclone] (rev 10) (3c59x driver) fails to come back up. This is written on the console/xterm: Internet Systems Consortium DHCP Client V3.0.4 Copyright 2004-2006 Internet Systems Consortium. All rights reserved. For info, please visit http://www.isc.org/sw/dhcp/ SIOCSIFADDR: No such device eth0: ERROR while getting interface flags: No such device eth0: ERROR while getting interface flags: No such device FATAL: Module acpi_sbs not found. Bind socket to interface: No such device Failed to bring up eth0. And this is in dmesg: 3c59x: Donald Becker and others. www.scyld.com/network/vortex.html :00:0b.0: 3Com PCI 3c556 Laptop Tornado at c8830400. eth1: New link status: Connected (0001) *** EEPROM MAC address is invalid. 3c59x: vortex_probe1 fails. Returns -22 ACPI: PCI interrupt for device :00:0b.0 disabled 3c59x: probe of :00:0b.0 failed with error -22 Michael -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#380292: linux-image-2.6.16-2-k7-smp: upgrade re-ran lilo
On Sat, 29 Jul 2006, Ross Boylan wrote: > # Kernel Image management overrides > # See kernel-img.conf(5) for details > do_symlinks = Yes > do_initrd = Yes current i386 default bootloader in kernel-package is still lilo, so if lilo and /etc/lilo.conf is around than lilo gets installed. you can set it explicitly off, add the following line to kernel-img.conf: do_bootloader = No there are thoughts of switching that default, keeping your bug report as reminder. best regards -- maks -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#380292: linux-image-2.6.16-2-k7-smp: upgrade re-ran lilo
reassign 380292 kernel-package stop On Sat, Jul 29, 2006 at 11:20:55AM -0700, Ross Boylan wrote: > On Sat, Jul 29, 2006 at 07:29:21PM +0200, maximilian attems wrote: > > > ok cool, please post the output of > > dpkg-reconfigure linux-image-2.6.16-2-k7-smp > > > > -- > > maks > Script started on Sat Jul 29 11:15:17 2006 > iron:~# date; dpkg-reconfigure linux-image-2.6.16-2-k7-smp > Sat Jul 29 11:15:39 PDT 2006 > Running depmod. > Finding valid ramdisk creators. > Using mkinitramfs-kpkg to build the ramdisk. > Other valid candidates: mkinitramfs-kpkg mkinitrd.yaird > Not updating initrd symbolic links since we are being updated/reinstalled > (2.6.16-17 was configured last, according to dpkg) > Not updating image symbolic links since we are being updated/reinstalled > (2.6.16-17 was configured last, according to dpkg) > You already have a LILO configuration in /etc/lilo.conf > Testing lilo.conf ... > Testing successful. > Installing the partition boot sector... > Running /sbin/lilo ... > Installation successful. > iron:~# dpkg -S mkinitramfs-kpkg > initramfs-tools: /usr/sbin/mkinitramfs-kpkg > initramfs-tools: /usr/share/man/man8/mkinitramfs-kpkg.8.gz > iron:~# exit > exit > > Script done on Sat Jul 29 11:16:49 2006 aboves didn't run mkinitramfs-kpkg, so passing this to Manoj. he might need your make-kpkg settings, so please post cat /etc/kernel-img.conf > Ugh; looks like I've reinstalled lilo. Unfortunately, grub can't > install from within my system when it's running; at least, I haven't > found a way (EVMS is confusing it). try grub-install or if it fails the grub shell usally works -> http://www.itp.tuwien.ac.at/~mattems/blog/2006/01/18#grub_install all the best and thanks for your report. -- maks -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#380292: linux-image-2.6.16-2-k7-smp: upgrade re-ran lilo
On Sat, Jul 29, 2006 at 09:20:21PM +0200, maximilian attems wrote: > reassign 380292 kernel-package > stop > > On Sat, Jul 29, 2006 at 11:20:55AM -0700, Ross Boylan wrote: > > On Sat, Jul 29, 2006 at 07:29:21PM +0200, maximilian attems wrote: > > > > > ok cool, please post the output of > > > dpkg-reconfigure linux-image-2.6.16-2-k7-smp > > > > > > -- > > > maks > > Script started on Sat Jul 29 11:15:17 2006 > > iron:~# date; dpkg-reconfigure linux-image-2.6.16-2-k7-smp > > Sat Jul 29 11:15:39 PDT 2006 > > Running depmod. > > Finding valid ramdisk creators. > > Using mkinitramfs-kpkg to build the ramdisk. > > Other valid candidates: mkinitramfs-kpkg mkinitrd.yaird > > Not updating initrd symbolic links since we are being updated/reinstalled > > (2.6.16-17 was configured last, according to dpkg) > > Not updating image symbolic links since we are being updated/reinstalled > > (2.6.16-17 was configured last, according to dpkg) > > You already have a LILO configuration in /etc/lilo.conf > > Testing lilo.conf ... > > Testing successful. > > Installing the partition boot sector... > > Running /sbin/lilo ... > > Installation successful. > > iron:~# dpkg -S mkinitramfs-kpkg > > initramfs-tools: /usr/sbin/mkinitramfs-kpkg > > initramfs-tools: /usr/share/man/man8/mkinitramfs-kpkg.8.gz > > iron:~# exit > > exit > > > > Script done on Sat Jul 29 11:16:49 2006 > > aboves didn't run mkinitramfs-kpkg, so passing this to Manoj. > he might need your make-kpkg settings, so please post > cat /etc/kernel-img.conf > # Kernel Image management overrides # See kernel-img.conf(5) for details do_symlinks = Yes do_initrd = Yes > > > Ugh; looks like I've reinstalled lilo. Unfortunately, grub can't > > install from within my system when it's running; at least, I haven't > > found a way (EVMS is confusing it). > > try grub-install or if it fails the grub shell usally works > -> http://www.itp.tuwien.ac.at/~mattems/blog/2006/01/18#grub_install > Thanks for the tips. Ross -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#378344: closed by maximilian attems <[EMAIL PROTECTED]> (Re: Bug#378344: initramfs-tools: Should be able to force root device for update-initramfs)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 reopen 378344 thank you Hello, Maximilian, thanks for addressing my bug report. Your council does not help me all that much, though. I do not feel my concerns have been addressed. I try to repair this situation by answering some of your arguments, and also by explaining my concern more clearly. > the initramfs will just boot without any root bootarg, > beware that an root bootarg overides this hardcoding. > (initrd-tools compat + repair capability) So far, so good, yes. The problem I was experiencing: The initramfs will not be able to mount the desired LVM root unless LVM software is contained in that initramfs. And that software will not be contained in that initramfs, if the initramfs building-process had not understood that root is on LVM. And finally, there is no easy, well-documented way to force the initramfs building tools to use a particular root file system (and the software it deems neccessary to boot from it), or even a particular name for the current root file system (if that helps the building tools to discern where the file system lives). In particular, switching from non-LVM root to LVM root by simply providing arguments to the boot process through grub does *not* work. (Not that much compat+repair capability, really.) > once the bootloader points to the lvm2 root dev aka /dev/mapper/vgX-root > the box will happily boot from that, provided you have lvm2 installed > there. no need to regenerate the initrd. My experience is different. No happy boot. For me, it was not possible for /dev/mapper/vgX-root to even exist during the boot process, unless the initramfs itself already contains LVM software. At a minimum, vgchange needs to be present to activate vgX. But there is no easy way to force it to be there. That is the problem I'm trying to describe. Or if there is such an easy way, I have not found the documentation in the manual pages. > if there was previously _no_ lvm2 installed you need to update it > update-initramfs -u Again, my experience is different. When I newly install LVM2, my root at that point clearly is not under LVM2-control yet. In my experience, that fact is reason enough for "update-initramfs -u" to *not* copy LVM software to the initramfs. LVM software will not be picked up just because it is available, but only if the build scripts are convinced that the root file system actually lives on LVM. It becomes a chicken and egg problem. I cannot switch to a LVM2 root because I cannot boot into such a root, as long as the initramfs does not contain LVM2. And on the other hand, the initramfs will never pick up LVM2, unless I have already managed to boot into the LVM2 root. > this will go away soonest as lvm2 will get the hooks and regenerate > latest initramfs on install with relevant lvm2 boot scripts. Good news! But, for one, I would prefer my bug reports to be left open, util the bugs are actually fixed. And, secondly, I'm a bit sceptic. The regeneration process itself will still need to be changed from how it currently operates. Here is my concerned spelled out, I hope, more clearly: I consider the problem solved, if there is a documented way to move a system from an old setup, e.g., "root on /dev/hda5", to a new setup "root on some LVM". For a specific example, I may have bought and installed this shiny big new /dev/hdb, I may want to move my entire system to an LVM vg that lives on /dev/hdb, and then remove my old /dev/hda and give it to my daughter to play with. How do I do this? More general, I may want to play with any odd file system container that the initramfs-scripts support, and set up a dual boot for that purpose. This is not really a "root on LVM" issue, but a more general "move from root on A to root on B" issue. What is the general recipe? How do I do that? My suggested "I want this particular root" - option would solve all those problems, for LVM and any other file system containers the initramfs-generating scripts happen to support. "If you can mount it now, you can boot from it next time." Regards, and thank you for providing fine software and services, Andreas -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.1 (GNU/Linux) Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org iD8DBQFEy7EVnWrlKaIH40ARAvYCAJ91ALJ/BS7BcuFa33vN+amDEHcf9gCghi46 +ITVPYPGdDCtdb8nGmETyJ8= =gtSx -END PGP SIGNATURE- -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Processed: Re: Bug#378344 closed by maximilian attems <[EMAIL PROTECTED]> (Re: Bug#378344: initramfs-tools: Should be able to force root device for update-initramfs)
Processing commands for [EMAIL PROTECTED]: > reopen 378344 Bug#378344: initramfs-tools: Should be able to force root device for update-initramfs Bug reopened, originator not changed. > thank you Stopping processing here. Please contact me if you need assistance. Debian bug tracking system administrator (administrator, Debian Bugs database) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#380292: linux-image-2.6.16-2-k7-smp: upgrade re-ran lilo
On Sat, Jul 29, 2006 at 07:29:21PM +0200, maximilian attems wrote: > ok cool, please post the output of > dpkg-reconfigure linux-image-2.6.16-2-k7-smp > > -- > maks Script started on Sat Jul 29 11:15:17 2006 iron:~# date; dpkg-reconfigure linux-image-2.6.16-2-k7-smp Sat Jul 29 11:15:39 PDT 2006 Running depmod. Finding valid ramdisk creators. Using mkinitramfs-kpkg to build the ramdisk. Other valid candidates: mkinitramfs-kpkg mkinitrd.yaird Not updating initrd symbolic links since we are being updated/reinstalled (2.6.16-17 was configured last, according to dpkg) Not updating image symbolic links since we are being updated/reinstalled (2.6.16-17 was configured last, according to dpkg) You already have a LILO configuration in /etc/lilo.conf Testing lilo.conf ... Testing successful. Installing the partition boot sector... Running /sbin/lilo ... Installation successful. iron:~# dpkg -S mkinitramfs-kpkg initramfs-tools: /usr/sbin/mkinitramfs-kpkg initramfs-tools: /usr/share/man/man8/mkinitramfs-kpkg.8.gz iron:~# exit exit Script done on Sat Jul 29 11:16:49 2006 Ugh; looks like I've reinstalled lilo. Unfortunately, grub can't install from within my system when it's running; at least, I haven't found a way (EVMS is confusing it). -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#380292: linux-image-2.6.16-2-k7-smp: upgrade re-ran lilo
On Sat, Jul 29, 2006 at 10:29:12AM +0200, maximilian attems wrote: > reassign 380292 initramfs-tools > thanks > > > hello ross, > > On Fri, Jul 28, 2006 at 06:56:29PM -0700, Ross Boylan wrote: > yes it seems to be an initramfs-tools trouble. > lilo is only run if there is no /sbin/grub or no /boot/grub/menu.lst Is the statement "lilo is only run if..." about the basic kernel installation process? And initramfs-tools doesn't follow this logic? > but a /etc/lilo.conf and lilo -t runs successfully > please post output > dpkg -l grub ii grub 0.97-12 > ( [ -x /sbin/grub ] || [ -e /boot/grub/menu.lst ] ) || echo "no > grub" There is not output; both of the files in the tests exist. > does any of those file exist. Thanks. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#380292: linux-image-2.6.16-2-k7-smp: upgrade re-ran lilo
On Sat, Jul 29, 2006 at 10:08:49AM -0700, Ross Boylan wrote: > On Sat, Jul 29, 2006 at 10:29:12AM +0200, maximilian attems wrote: > > On Fri, Jul 28, 2006 at 06:56:29PM -0700, Ross Boylan wrote: > > > yes it seems to be an initramfs-tools trouble. > > lilo is only run if there is no /sbin/grub or no /boot/grub/menu.lst > Is the statement "lilo is only run if..." about the basic kernel > installation process? And initramfs-tools doesn't follow this logic? no this is current initramfs-tools logic. > > but a /etc/lilo.conf and lilo -t runs successfully > > > > please post output > > dpkg -l grub > ii grub 0.97-12 looks fine. > > ( [ -x /sbin/grub ] || [ -e /boot/grub/menu.lst ] ) || echo "no > > grub" > There is not output; both of the files in the tests exist. ok cool, please post the output of dpkg-reconfigure linux-image-2.6.16-2-k7-smp -- maks -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#380089: possibly inadequate solution
I won't comment on the silliness of the severity tennis played by the maintainer. The bug is critical even according to the release team. Anyway, I disagree with the way 0.73 fixes the bug: it replicates the functionality provided by mdadm >=2.5-1 into a hack within the package. Granted, the hack is only used when mdadm >=2.5-1 is not installed, but still, it's a hack. The maintainer failed to give any reasons why his solution is preferred over a simple conflict against mdadm <<2.5-1, which is what I proposed even before we started the transition. I do not see why we should have a hack ensuring that everything works when mdadm <<2.5-1 is installed, instead of just ensuring that a newer mdadm should be installed by means of a conflict. Then again, a conflict could possibly remove the mdadm package altogether, which would be equally bad. There seems to be no way to tell Debian to conflict with versions prior to a specific package's specific version, but to ensure an upgrade as a resolution conflict, not the package's removal. Please do not sponsor the package in its current state without ensuring that the maintainer knows what he's doing and has publicly documented his reasons for his choice. -- Please do not send copies of list mail to me; I read the list! .''`. martin f. krafft <[EMAIL PROTECTED]> : :' :proud Debian developer and author: http://debiansystem.info `. `'` `- Debian - when you have better things to do than fixing a system signature.asc Description: Digital signature (GPG/PGP)
Processing of usplash_0.3a_i386.changes
usplash_0.3a_i386.changes uploaded successfully to localhost along with the files: usplash_0.3a.dsc usplash_0.3a.tar.gz usplash_0.3a_i386.deb Greetings, Your Debian queue daemon -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
usplash_0.3a_i386.changes is NEW
(new) usplash_0.3a.dsc optional misc (new) usplash_0.3a.tar.gz optional misc (new) usplash_0.3a_i386.deb optional misc Userspace bootsplash utility Usplash is a userspace application that uses the Linux framebuffer interface to draw a splash screen at boot. It has a companion utility that is able to send commands to usplash, allowing information about the bootup sequence to be displayed in a more attractive way. Changes: usplash (0.3a) unstable; urgency=low . [ Petter Reinholdtsen ] * Initial upload to Debian (Closes: #356193) * usplash_write.c: Fix typo in fifo write code, 00-ssize-typo.patch. * usplash.c: Improve error messages when usplash fail to start, 01-bogl-error.patch. * usplash.h: Improve comment for USPLASH_FIFO, 02-header-comment.patch. * Make sure postrm call update-rc.d to remove the init.d script. . [ maximilian attems ] * Add the Debian kernel team as Maintainer. Petter and myself as Uploaders. * Add versioned dependency to initramfs-tools 0.72, which adds the fb boot scripts. * Standards-Version 3.7.2.0 without needed changes. * debian/copyright: Add pointer to latest Ubuntu release, small rephrasing. * Use a Debian version string, as there is no separate archive. * debian/usplash.postinst: Check if update-initramfs is really installed. Remove old unused rm_default_artwork(). * debian/usplash.postrm: Check if update-initramfs is really installed. * debian/patches: Split out Petter's changes as patches. * debian/rules: Add quilt handling for the patches. * debian/control: Add quilt build dependency. * .bzr, bogl/.cvsignore: Remove version control stuff in source package. * Add lsb-base-logging-ubuntu.sh from ubuntu lsb (3.1-10ubuntu2). * debian/rules: Install lsb-base-logging.sh. * usplash.lintian: Add lintian override for /etc/lsb-base-logging.sh, Debian lsb-base allows to set there the lsb functions. * debian/rules: Install lintian override. * debian/control: Provides bootsplash as discussed with otavio. Override entries for your package: Announcing to debian-devel-changes@lists.debian.org Closing bugs: 356193 Your package contains new components which requires manual editing of the override file. It is ok otherwise, so please be patient. New packages are usually added to the override file about once a week. You may have gotten the distribution wrong. You'll get warnings above if files already exist in other distributions. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Processing of linux-2.6_2.6.17-5_powerpc.changes
linux-2.6_2.6.17-5_powerpc.changes uploaded successfully to localhost along with the files: linux-2.6_2.6.17-5.dsc linux-2.6_2.6.17-5.diff.gz linux-doc-2.6.17_2.6.17-5_all.deb linux-manual-2.6.17_2.6.17-5_all.deb linux-patch-debian-2.6.17_2.6.17-5_all.deb linux-source-2.6.17_2.6.17-5_all.deb linux-support-2.6.17-1_2.6.17-5_all.deb linux-tree-2.6.17_2.6.17-5_all.deb linux-headers-2.6.17-1-all_2.6.17-5_powerpc.deb linux-headers-2.6.17-1-all-powerpc_2.6.17-5_powerpc.deb linux-headers-2.6.17-1_2.6.17-5_powerpc.deb linux-image-2.6.17-1-powerpc_2.6.17-5_powerpc.deb linux-headers-2.6.17-1-powerpc_2.6.17-5_powerpc.deb linux-image-powerpc_2.6.17-5_powerpc.deb linux-image-2.6-powerpc_2.6.17-5_powerpc.deb linux-headers-2.6-powerpc_2.6.17-5_powerpc.deb linux-image-2.6.17-1-powerpc-smp_2.6.17-5_powerpc.deb linux-headers-2.6.17-1-powerpc-smp_2.6.17-5_powerpc.deb linux-image-powerpc-smp_2.6.17-5_powerpc.deb linux-image-2.6-powerpc-smp_2.6.17-5_powerpc.deb linux-headers-2.6-powerpc-smp_2.6.17-5_powerpc.deb linux-image-2.6.17-1-powerpc-miboot_2.6.17-5_powerpc.deb linux-headers-2.6.17-1-powerpc-miboot_2.6.17-5_powerpc.deb linux-image-powerpc-miboot_2.6.17-5_powerpc.deb linux-image-2.6-powerpc-miboot_2.6.17-5_powerpc.deb linux-headers-2.6-powerpc-miboot_2.6.17-5_powerpc.deb linux-image-2.6.17-1-powerpc64_2.6.17-5_powerpc.deb linux-headers-2.6.17-1-powerpc64_2.6.17-5_powerpc.deb linux-image-powerpc64_2.6.17-5_powerpc.deb linux-image-2.6-powerpc64_2.6.17-5_powerpc.deb linux-headers-2.6-powerpc64_2.6.17-5_powerpc.deb linux-headers-2.6.17-1-vserver_2.6.17-5_powerpc.deb linux-image-2.6.17-1-vserver-powerpc_2.6.17-5_powerpc.deb linux-headers-2.6.17-1-vserver-powerpc_2.6.17-5_powerpc.deb linux-image-vserver-powerpc_2.6.17-5_powerpc.deb linux-image-2.6-vserver-powerpc_2.6.17-5_powerpc.deb linux-headers-2.6-vserver-powerpc_2.6.17-5_powerpc.deb linux-image-2.6.17-1-vserver-powerpc64_2.6.17-5_powerpc.deb linux-headers-2.6.17-1-vserver-powerpc64_2.6.17-5_powerpc.deb linux-image-vserver-powerpc64_2.6.17-5_powerpc.deb linux-image-2.6-vserver-powerpc64_2.6.17-5_powerpc.deb linux-headers-2.6-vserver-powerpc64_2.6.17-5_powerpc.deb kernel-image-powerpc_2.6.17-5_powerpc.deb kernel-image-2.6-powerpc_2.6.17-5_powerpc.deb kernel-image-powerpc-smp_2.6.17-5_powerpc.deb kernel-image-2.6-powerpc-smp_2.6.17-5_powerpc.deb kernel-image-power3_2.6.17-5_powerpc.deb kernel-image-2.6-power3_2.6.17-5_powerpc.deb kernel-image-power3-smp_2.6.17-5_powerpc.deb kernel-image-2.6-power3-smp_2.6.17-5_powerpc.deb kernel-image-power4_2.6.17-5_powerpc.deb kernel-image-2.6-power4_2.6.17-5_powerpc.deb kernel-image-power4-smp_2.6.17-5_powerpc.deb kernel-image-2.6-power4-smp_2.6.17-5_powerpc.deb Greetings, Your Debian queue daemon -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#378554: marked as done ([arm/armeb] Please enable CONFIG_USB_EHCI_SPLIT_ISO on NSLU2)
Your message dated Sat, 29 Jul 2006 07:34:25 -0700 with message-id <[EMAIL PROTECTED]> and subject line Bug#378554: fixed in linux-2.6 2.6.17-5 has caused the attached Bug report to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what I am talking about this indicates a serious mail system misconfiguration somewhere. Please contact me immediately.) Debian bug tracking system administrator (administrator, Debian Bugs database) --- Begin Message --- Package: linux-2.6 Version: 2.6.17-3 Severity: wishlist Playing audio to USB 1.1 devices through a USB 2.0 hub (I need to connect the audio device to a powered hub to avoid whining noise) requires CONFIG_USB_EHCI_SPLIT_ISO. This is already enabled on alpha, amd64, i386 and powerpc, please enable it for the NSLU2 as well. -- ilmari "A disappointingly low fraction of the human race is, at any given time, on fire." - Stig Sandbeck Mathisen --- End Message --- --- Begin Message --- Source: linux-2.6 Source-Version: 2.6.17-5 We believe that the bug you reported is fixed in the latest version of linux-2.6, which is due to be installed in the Debian FTP archive: kernel-image-2.6-power3-smp_2.6.17-5_powerpc.deb to pool/main/l/linux-2.6/kernel-image-2.6-power3-smp_2.6.17-5_powerpc.deb kernel-image-2.6-power3_2.6.17-5_powerpc.deb to pool/main/l/linux-2.6/kernel-image-2.6-power3_2.6.17-5_powerpc.deb kernel-image-2.6-power4-smp_2.6.17-5_powerpc.deb to pool/main/l/linux-2.6/kernel-image-2.6-power4-smp_2.6.17-5_powerpc.deb kernel-image-2.6-power4_2.6.17-5_powerpc.deb to pool/main/l/linux-2.6/kernel-image-2.6-power4_2.6.17-5_powerpc.deb kernel-image-2.6-powerpc-smp_2.6.17-5_powerpc.deb to pool/main/l/linux-2.6/kernel-image-2.6-powerpc-smp_2.6.17-5_powerpc.deb kernel-image-2.6-powerpc_2.6.17-5_powerpc.deb to pool/main/l/linux-2.6/kernel-image-2.6-powerpc_2.6.17-5_powerpc.deb kernel-image-power3-smp_2.6.17-5_powerpc.deb to pool/main/l/linux-2.6/kernel-image-power3-smp_2.6.17-5_powerpc.deb kernel-image-power3_2.6.17-5_powerpc.deb to pool/main/l/linux-2.6/kernel-image-power3_2.6.17-5_powerpc.deb kernel-image-power4-smp_2.6.17-5_powerpc.deb to pool/main/l/linux-2.6/kernel-image-power4-smp_2.6.17-5_powerpc.deb kernel-image-power4_2.6.17-5_powerpc.deb to pool/main/l/linux-2.6/kernel-image-power4_2.6.17-5_powerpc.deb kernel-image-powerpc-smp_2.6.17-5_powerpc.deb to pool/main/l/linux-2.6/kernel-image-powerpc-smp_2.6.17-5_powerpc.deb kernel-image-powerpc_2.6.17-5_powerpc.deb to pool/main/l/linux-2.6/kernel-image-powerpc_2.6.17-5_powerpc.deb linux-2.6_2.6.17-5.diff.gz to pool/main/l/linux-2.6/linux-2.6_2.6.17-5.diff.gz linux-2.6_2.6.17-5.dsc to pool/main/l/linux-2.6/linux-2.6_2.6.17-5.dsc linux-doc-2.6.17_2.6.17-5_all.deb to pool/main/l/linux-2.6/linux-doc-2.6.17_2.6.17-5_all.deb linux-headers-2.6-powerpc-miboot_2.6.17-5_powerpc.deb to pool/main/l/linux-2.6/linux-headers-2.6-powerpc-miboot_2.6.17-5_powerpc.deb linux-headers-2.6-powerpc-smp_2.6.17-5_powerpc.deb to pool/main/l/linux-2.6/linux-headers-2.6-powerpc-smp_2.6.17-5_powerpc.deb linux-headers-2.6-powerpc64_2.6.17-5_powerpc.deb to pool/main/l/linux-2.6/linux-headers-2.6-powerpc64_2.6.17-5_powerpc.deb linux-headers-2.6-powerpc_2.6.17-5_powerpc.deb to pool/main/l/linux-2.6/linux-headers-2.6-powerpc_2.6.17-5_powerpc.deb linux-headers-2.6-vserver-powerpc64_2.6.17-5_powerpc.deb to pool/main/l/linux-2.6/linux-headers-2.6-vserver-powerpc64_2.6.17-5_powerpc.deb linux-headers-2.6-vserver-powerpc_2.6.17-5_powerpc.deb to pool/main/l/linux-2.6/linux-headers-2.6-vserver-powerpc_2.6.17-5_powerpc.deb linux-headers-2.6.17-1-all-powerpc_2.6.17-5_powerpc.deb to pool/main/l/linux-2.6/linux-headers-2.6.17-1-all-powerpc_2.6.17-5_powerpc.deb linux-headers-2.6.17-1-all_2.6.17-5_powerpc.deb to pool/main/l/linux-2.6/linux-headers-2.6.17-1-all_2.6.17-5_powerpc.deb linux-headers-2.6.17-1-powerpc-miboot_2.6.17-5_powerpc.deb to pool/main/l/linux-2.6/linux-headers-2.6.17-1-powerpc-miboot_2.6.17-5_powerpc.deb linux-headers-2.6.17-1-powerpc-smp_2.6.17-5_powerpc.deb to pool/main/l/linux-2.6/linux-headers-2.6.17-1-powerpc-smp_2.6.17-5_powerpc.deb linux-headers-2.6.17-1-powerpc64_2.6.17-5_powerpc.deb to pool/main/l/linux-2.6/linux-headers-2.6.17-1-powerpc64_2.6.17-5_powerpc.deb linux-headers-2.6.17-1-powerpc_2.6.17-5_powerpc.deb to pool/main/l/linux-2.6/linux-headers-2.6.17-1-powerpc_2.6.17-5_powerpc.deb linux-headers-2.6.17-1-vserver-powerpc64_2.6.17-5_powerpc.deb to pool/main/l/linux-2.6/linux-headers-2.6.17-1-vserver-powerpc64_2.6.17-5_powerpc.deb linux-headers-2.6.17-1-vserver-powerpc_2.6.17-5_powerpc.deb to pool/main/l/linux-2.6/linux-headers-2.6.17-1-vserver-powerpc_2.6.17-5_powerpc.deb linux-headers-2.6.17-1-vserver_2.6.17-5_powerpc.deb to pool/main/l/linux-2.6/linux-h
linux-2.6_2.6.17-5_powerpc.changes ACCEPTED
Accepted: kernel-image-2.6-power3-smp_2.6.17-5_powerpc.deb to pool/main/l/linux-2.6/kernel-image-2.6-power3-smp_2.6.17-5_powerpc.deb kernel-image-2.6-power3_2.6.17-5_powerpc.deb to pool/main/l/linux-2.6/kernel-image-2.6-power3_2.6.17-5_powerpc.deb kernel-image-2.6-power4-smp_2.6.17-5_powerpc.deb to pool/main/l/linux-2.6/kernel-image-2.6-power4-smp_2.6.17-5_powerpc.deb kernel-image-2.6-power4_2.6.17-5_powerpc.deb to pool/main/l/linux-2.6/kernel-image-2.6-power4_2.6.17-5_powerpc.deb kernel-image-2.6-powerpc-smp_2.6.17-5_powerpc.deb to pool/main/l/linux-2.6/kernel-image-2.6-powerpc-smp_2.6.17-5_powerpc.deb kernel-image-2.6-powerpc_2.6.17-5_powerpc.deb to pool/main/l/linux-2.6/kernel-image-2.6-powerpc_2.6.17-5_powerpc.deb kernel-image-power3-smp_2.6.17-5_powerpc.deb to pool/main/l/linux-2.6/kernel-image-power3-smp_2.6.17-5_powerpc.deb kernel-image-power3_2.6.17-5_powerpc.deb to pool/main/l/linux-2.6/kernel-image-power3_2.6.17-5_powerpc.deb kernel-image-power4-smp_2.6.17-5_powerpc.deb to pool/main/l/linux-2.6/kernel-image-power4-smp_2.6.17-5_powerpc.deb kernel-image-power4_2.6.17-5_powerpc.deb to pool/main/l/linux-2.6/kernel-image-power4_2.6.17-5_powerpc.deb kernel-image-powerpc-smp_2.6.17-5_powerpc.deb to pool/main/l/linux-2.6/kernel-image-powerpc-smp_2.6.17-5_powerpc.deb kernel-image-powerpc_2.6.17-5_powerpc.deb to pool/main/l/linux-2.6/kernel-image-powerpc_2.6.17-5_powerpc.deb linux-2.6_2.6.17-5.diff.gz to pool/main/l/linux-2.6/linux-2.6_2.6.17-5.diff.gz linux-2.6_2.6.17-5.dsc to pool/main/l/linux-2.6/linux-2.6_2.6.17-5.dsc linux-doc-2.6.17_2.6.17-5_all.deb to pool/main/l/linux-2.6/linux-doc-2.6.17_2.6.17-5_all.deb linux-headers-2.6-powerpc-miboot_2.6.17-5_powerpc.deb to pool/main/l/linux-2.6/linux-headers-2.6-powerpc-miboot_2.6.17-5_powerpc.deb linux-headers-2.6-powerpc-smp_2.6.17-5_powerpc.deb to pool/main/l/linux-2.6/linux-headers-2.6-powerpc-smp_2.6.17-5_powerpc.deb linux-headers-2.6-powerpc64_2.6.17-5_powerpc.deb to pool/main/l/linux-2.6/linux-headers-2.6-powerpc64_2.6.17-5_powerpc.deb linux-headers-2.6-powerpc_2.6.17-5_powerpc.deb to pool/main/l/linux-2.6/linux-headers-2.6-powerpc_2.6.17-5_powerpc.deb linux-headers-2.6-vserver-powerpc64_2.6.17-5_powerpc.deb to pool/main/l/linux-2.6/linux-headers-2.6-vserver-powerpc64_2.6.17-5_powerpc.deb linux-headers-2.6-vserver-powerpc_2.6.17-5_powerpc.deb to pool/main/l/linux-2.6/linux-headers-2.6-vserver-powerpc_2.6.17-5_powerpc.deb linux-headers-2.6.17-1-all-powerpc_2.6.17-5_powerpc.deb to pool/main/l/linux-2.6/linux-headers-2.6.17-1-all-powerpc_2.6.17-5_powerpc.deb linux-headers-2.6.17-1-all_2.6.17-5_powerpc.deb to pool/main/l/linux-2.6/linux-headers-2.6.17-1-all_2.6.17-5_powerpc.deb linux-headers-2.6.17-1-powerpc-miboot_2.6.17-5_powerpc.deb to pool/main/l/linux-2.6/linux-headers-2.6.17-1-powerpc-miboot_2.6.17-5_powerpc.deb linux-headers-2.6.17-1-powerpc-smp_2.6.17-5_powerpc.deb to pool/main/l/linux-2.6/linux-headers-2.6.17-1-powerpc-smp_2.6.17-5_powerpc.deb linux-headers-2.6.17-1-powerpc64_2.6.17-5_powerpc.deb to pool/main/l/linux-2.6/linux-headers-2.6.17-1-powerpc64_2.6.17-5_powerpc.deb linux-headers-2.6.17-1-powerpc_2.6.17-5_powerpc.deb to pool/main/l/linux-2.6/linux-headers-2.6.17-1-powerpc_2.6.17-5_powerpc.deb linux-headers-2.6.17-1-vserver-powerpc64_2.6.17-5_powerpc.deb to pool/main/l/linux-2.6/linux-headers-2.6.17-1-vserver-powerpc64_2.6.17-5_powerpc.deb linux-headers-2.6.17-1-vserver-powerpc_2.6.17-5_powerpc.deb to pool/main/l/linux-2.6/linux-headers-2.6.17-1-vserver-powerpc_2.6.17-5_powerpc.deb linux-headers-2.6.17-1-vserver_2.6.17-5_powerpc.deb to pool/main/l/linux-2.6/linux-headers-2.6.17-1-vserver_2.6.17-5_powerpc.deb linux-headers-2.6.17-1_2.6.17-5_powerpc.deb to pool/main/l/linux-2.6/linux-headers-2.6.17-1_2.6.17-5_powerpc.deb linux-image-2.6-powerpc-miboot_2.6.17-5_powerpc.deb to pool/main/l/linux-2.6/linux-image-2.6-powerpc-miboot_2.6.17-5_powerpc.deb linux-image-2.6-powerpc-smp_2.6.17-5_powerpc.deb to pool/main/l/linux-2.6/linux-image-2.6-powerpc-smp_2.6.17-5_powerpc.deb linux-image-2.6-powerpc64_2.6.17-5_powerpc.deb to pool/main/l/linux-2.6/linux-image-2.6-powerpc64_2.6.17-5_powerpc.deb linux-image-2.6-powerpc_2.6.17-5_powerpc.deb to pool/main/l/linux-2.6/linux-image-2.6-powerpc_2.6.17-5_powerpc.deb linux-image-2.6-vserver-powerpc64_2.6.17-5_powerpc.deb to pool/main/l/linux-2.6/linux-image-2.6-vserver-powerpc64_2.6.17-5_powerpc.deb linux-image-2.6-vserver-powerpc_2.6.17-5_powerpc.deb to pool/main/l/linux-2.6/linux-image-2.6-vserver-powerpc_2.6.17-5_powerpc.deb linux-image-2.6.17-1-powerpc-miboot_2.6.17-5_powerpc.deb to pool/main/l/linux-2.6/linux-image-2.6.17-1-powerpc-miboot_2.6.17-5_powerpc.deb linux-image-2.6.17-1-powerpc-smp_2.6.17-5_powerpc.deb to pool/main/l/linux-2.6/linux-image-2.6.17-1-powerpc-smp_2.6.17-5_powerpc.deb linux-image-2.6.17-1-powerpc64_2.6.17-5_powerpc.deb to pool/main/l/linux-2.6/linux-image-2.6.17-1-powerpc64_2.6.17-5_powerpc.deb lin
linux-2.6 override disparity
There are disparities between your recently accepted upload and the override file for the following file(s): kernel-image-2.6-power3-smp_2.6.17-5_powerpc.deb: package says section is admin, override says base. kernel-image-2.6-power3-smp_2.6.17-5_powerpc.deb: package says priority is extra, override says optional. kernel-image-2.6-power3_2.6.17-5_powerpc.deb: package says section is admin, override says base. kernel-image-2.6-power3_2.6.17-5_powerpc.deb: package says priority is extra, override says optional. kernel-image-2.6-power4-smp_2.6.17-5_powerpc.deb: package says section is admin, override says base. kernel-image-2.6-power4-smp_2.6.17-5_powerpc.deb: package says priority is extra, override says optional. kernel-image-2.6-power4_2.6.17-5_powerpc.deb: package says section is admin, override says base. kernel-image-2.6-power4_2.6.17-5_powerpc.deb: package says priority is extra, override says optional. kernel-image-2.6-powerpc-smp_2.6.17-5_powerpc.deb: package says section is admin, override says base. kernel-image-2.6-powerpc-smp_2.6.17-5_powerpc.deb: package says priority is extra, override says optional. kernel-image-2.6-powerpc_2.6.17-5_powerpc.deb: package says section is admin, override says base. kernel-image-2.6-powerpc_2.6.17-5_powerpc.deb: package says priority is extra, override says optional. kernel-image-power3-smp_2.6.17-5_powerpc.deb: package says section is admin, override says base. kernel-image-power3-smp_2.6.17-5_powerpc.deb: package says priority is extra, override says optional. kernel-image-power3_2.6.17-5_powerpc.deb: package says section is admin, override says base. kernel-image-power3_2.6.17-5_powerpc.deb: package says priority is extra, override says optional. kernel-image-power4-smp_2.6.17-5_powerpc.deb: package says section is admin, override says base. kernel-image-power4-smp_2.6.17-5_powerpc.deb: package says priority is extra, override says optional. kernel-image-power4_2.6.17-5_powerpc.deb: package says section is admin, override says base. kernel-image-power4_2.6.17-5_powerpc.deb: package says priority is extra, override says optional. kernel-image-powerpc-smp_2.6.17-5_powerpc.deb: package says section is admin, override says base. kernel-image-powerpc-smp_2.6.17-5_powerpc.deb: package says priority is extra, override says optional. kernel-image-powerpc_2.6.17-5_powerpc.deb: package says section is admin, override says base. kernel-image-powerpc_2.6.17-5_powerpc.deb: package says priority is extra, override says optional. linux-image-2.6-powerpc-miboot_2.6.17-5_powerpc.deb: package says section is admin, override says base. linux-image-2.6-powerpc-smp_2.6.17-5_powerpc.deb: package says section is admin, override says base. linux-image-2.6-powerpc64_2.6.17-5_powerpc.deb: package says section is admin, override says base. linux-image-2.6-powerpc_2.6.17-5_powerpc.deb: package says section is admin, override says base. linux-image-2.6-vserver-powerpc64_2.6.17-5_powerpc.deb: package says section is admin, override says base. linux-image-2.6-vserver-powerpc_2.6.17-5_powerpc.deb: package says section is admin, override says base. linux-image-2.6.17-1-powerpc-miboot_2.6.17-5_powerpc.deb: package says section is admin, override says base. linux-image-2.6.17-1-powerpc-smp_2.6.17-5_powerpc.deb: package says section is admin, override says base. linux-image-2.6.17-1-powerpc64_2.6.17-5_powerpc.deb: package says section is admin, override says base. linux-image-2.6.17-1-powerpc_2.6.17-5_powerpc.deb: package says section is admin, override says base. linux-image-2.6.17-1-vserver-powerpc64_2.6.17-5_powerpc.deb: package says section is admin, override says base. linux-image-2.6.17-1-vserver-powerpc_2.6.17-5_powerpc.deb: package says section is admin, override says base. linux-image-powerpc-miboot_2.6.17-5_powerpc.deb: package says section is admin, override says base. linux-image-powerpc-smp_2.6.17-5_powerpc.deb: package says section is admin, override says base. linux-image-powerpc64_2.6.17-5_powerpc.deb: package says section is admin, override says base. linux-image-powerpc_2.6.17-5_powerpc.deb: package says section is admin, override says base. linux-image-vserver-powerpc64_2.6.17-5_powerpc.deb: package says section is admin, override says base. linux-image-vserver-powerpc_2.6.17-5_powerpc.deb: package says section is admin, override says base. Either the package or the override file is incorrect. If you think the override is correct and the package wrong please fix the package so that this disparity is fixed in the next upload. If you feel the override is incorrect then please reply to this mail and explain why. [NB: this is an automatically generated mail; if you replied to one like it before and have not received a response yet, please ignore this mail. Your reply needs to be processed by a human and will be in due course, but until then the installer will send these automated mails; sorry.] -- Debian distribution maintenance soft
Processed: Re: nxtvepg: Acquisition and provider scan fails
Processing commands for [EMAIL PROTECTED]: > severity 376097 important Bug#376097: nxtvepg: Acquisition and provider scan fails Severity set to `important' from `normal' > reassign 376097 nxtvepg,linux-source-2.6.16,linux-source-2.6.17 Bug#376097: nxtvepg: Acquisition and provider scan fails Bug reassigned from package `nxtvepg' to `nxtvepg,linux-source-2.6.16,linux-source-2.6.17'. > reassign 362153 nxtvepg,linux-source-2.6.16,linux-source-2.6.17 Bug#362153: vbi interface in bttv broken Bug reassigned from package `linux-source-2.6.16' to `nxtvepg,linux-source-2.6.16,linux-source-2.6.17'. > merge 376097 362153 Bug#362153: vbi interface in bttv broken Bug#376097: nxtvepg: Acquisition and provider scan fails Merged 362153 376097. > stop Stopping processing here. Please contact me if you need assistance. Debian bug tracking system administrator (administrator, Debian Bugs database) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#380292: linux-image-2.6.16-2-k7-smp: upgrade re-ran lilo
reassign 380292 initramfs-tools thanks hello ross, On Fri, Jul 28, 2006 at 06:56:29PM -0700, Ross Boylan wrote: > > I upgraded this image and the installation process re-ran lilo. This > had the unfortunate effect of taking control of the boot back from > grub, and of making my system unbootable. blaeh > I've reinstalled grub (i.e., I'm OK), but I thought lilo was no longer > getting run by default. I was so sure, I didn't even check before > reboot :(. try to install grub _and_ removing lilo as workaround. > If this misbehavior belongs to some other package (e.g., initramfs) > please reassign as appropriate. yes it seems to be an initramfs-tools trouble. lilo is only run if there is no /sbin/grub or no /boot/grub/menu.lst but a /etc/lilo.conf and lilo -t runs successfully > Here's the relevant part of my log: > -- > Preparing to replace linux-image-2.6.16-2-k7-smp 2.6.16-15 (using > .../linux-image-2.6.16-2-k7-smp_2.6.16-17_i386.deb) ... > The directory /lib/modules/2.6.16-2-k7-smp still exists. Continuing as > directed. > Configuring linux-image-2.6.16-2-k7-smp > --- > > The kernel version running is the same as the one being installed > > You are attempting to install a kernel version that is the same as the > version you are currently running (version > 2.6.16-2-k7-smp). The modules list is quite likely to have been changed, and > the modules dependency file > /lib/modules/2.6.16-2-k7-smp/modules.dep needs to be re-built. It can not be > built correctly right now, since the module > list for the running kernel are likely to be different from the kernel > installed. I am creating a new modules.dep file, but > that may not be correct. It shall be regenerated correctly at next reboot. > > I repeat: you have to reboot in order for the modules file to be created > correctly. Until you reboot, it may be impossible > to load some modules. Reboot as soon as this install is finished (Do not > reboot right now, since you may not be able to > boot back up until installation is over, but boot immediately after). I can > not stress that too much. You need to reboot > soon. > > Done. > Unpacking replacement linux-image-2.6.16-2-k7-smp ... > > > # and later > > Setting up linux-image-2.6.16-2-k7-smp (2.6.16-17) ... > > Hmm. The package shipped with a symbolic link > /lib/modules/2.6.16-2-k7-smp/source > However, I can not read the target: No such file or directory > Therefore, I am deleting /lib/modules/2.6.16-2-k7-smp/source > > Running depmod. > Finding valid ramdisk creators. > Using mkinitramfs-kpkg to build the ramdisk. > Other valid candidates: mkinitramfs-kpkg mkinitrd.yaird > Not updating initrd symbolic links since we are being updated/reinstalled > (2.6.16-15 was configured last, according to dpkg) > Not updating image symbolic links since we are being updated/reinstalled > (2.6.16-15 was configured last, according to dpkg) > You already have a LILO configuration in /etc/lilo.conf > Testing lilo.conf ... > Testing successful. > Installing the partition boot sector... > Running /sbin/lilo ... > Installation successful. > - > > My system has both grub and lilo on it. Originally I used lilo, but I > switched to grub. please post output dpkg -l grub ( [ -x /sbin/grub ] || [ -e /boot/grub/menu.lst ] ) || echo "no grub" does any of those file exist. > P.S. reportbug gave me a bunch of messages about checksum mismatches > with various files. I suspect it took the checksum with the old > kernel's files, and isn't happy now that the new ones are there. those you can safely ignore. regards -- maks -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Processed: tagging 380089
Processing commands for [EMAIL PROTECTED]: > # Automatically generated email from bts, devscripts version 2.9.20 > tags 380089 pending Bug#380089: lvm/mdadm take care of partial upgrades from sarge There were no tags set. Tags added: pending > End of message, stopping processing here. Please contact me if you need assistance. Debian bug tracking system administrator (administrator, Debian Bugs database) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Processed: retitle 380089 to lvm/mdadm take care of partial upgrades from sarge
Processing commands for [EMAIL PROTECTED]: > # Automatically generated email from bts, devscripts version 2.9.20 > retitle 380089 lvm/mdadm take care of partial upgrades from sarge Bug#380089: missing conflict against mdadm (<< 2.5-1) Changed Bug title. > End of message, stopping processing here. Please contact me if you need assistance. Debian bug tracking system administrator (administrator, Debian Bugs database) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Processed: severity of 380089 is serious
Processing commands for [EMAIL PROTECTED]: > # Automatically generated email from bts, devscripts version 2.9.20 > severity 380089 serious Bug#380089: missing conflict against mdadm (<< 2.5-1) Severity set to `serious' from `critical' > End of message, stopping processing here. Please contact me if you need assistance. Debian bug tracking system administrator (administrator, Debian Bugs database) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
