Bug#779612: [pkg-cryptsetup-devel] Bug#779612: systemd-sysv,cryptsetup: systemd-sysv, cryptsetup should recommend plymouth; without plymouth cryptsetup prompts are unusable
On 03/25/2015 10:24 AM, Michael Biebl wrote: Gordon, can you try systemd v219 from experimental? It has some tricks to suppress output from other jobs while a password prompt is running. I dunno how well that works, though so having someone with such a setup test this would be appreciated. Hi Michael, 219-5 is MUCH MUCH better. If I type the wrong password it's a bit glitchy (prints multiple prompts and starts a service to dispatch password prompts but then holds after a spurious prompt or two). I didn't wait to see if there was a hidden timeout. I got the system booted in one try which is a first. If v219 works reasonably well (without plymouth), we might consider backporting those patches (depending on how invasive they are). So far so good here. Best, -Gordon M. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#779612: [pkg-cryptsetup-devel] Bug#779612: systemd-sysv,cryptsetup: systemd-sysv, cryptsetup should recommend plymouth; without plymouth cryptsetup prompts are unusable
On 03/25/2015 09:29 AM, Jonas Meurer wrote: [snip] > Seems like there's some more discussion needed in order to fix the reported bug: a) do we want cryptsetup to recommend plymouth? this way at least for manual installation of cryptsetup, plymouth would be pulled in, fixing destroyed nasty boot-password-prompts introduced that were introduced by the switch to systemd. b) do we want plymouth to be installed per default on new installs? to my knowledge it's not _required_ for systemd to work, but as soon as an initscript with user interaction is invoked, apparently plymouth is required. This *is* an argument for installing plymouth by default. c) do we want any of the above to be fixed/changed in time for jessie? I'm Just A User(tm) but I really think this should be fixed in time for jessie, because it looks really, really terrible. Yes, there's a "fix" - if you can get your system booted, which takes me on average 3-5 tries with only two interactive password prompts. If I were a sysadmin and ran into this after installing jessie, I'd think strongly about uninstalling it and going with something else. "It can't even boot right?!" is the first question that came to mind after my first install of jessie - really unacceptable UX for a release soon to be marked "stable" and a distribution which people have relied upon for stability for well over a decade, including myself. I'll drop it after this, but I urge release maintainers to take the above into consideration and fix this in time for jessie. Thanks for all your hard work. Best, -Gordon M. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#779612: [pkg-cryptsetup-devel] Bug#779612: systemd-sysv,cryptsetup: systemd-sysv, cryptsetup should recommend plymouth; without plymouth cryptsetup prompts are unusable
On 03/19/2015 06:58 PM, Michael Biebl wrote: > As pointed out, a recommends does not really help for new installs, > since they have no effect when installing the base system. A recommends at least provides users a pointer towards fixing a really nasty problem (which they shouldn't even have, but, they currently will). > Also, what Julien said. > > Therefor, I wonder if this bug report is useful in this form and if > there's a point, keeping it open. Perhaps you could open a more appropriate bug to fix the problem for new installs? I'm not familiar enough with Debian to do so. Leaving this bug completely untouched is not a good idea. It makes Debian look cartoonishly bad when it bites. Best, -Gordon M. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#779612: [pkg-cryptsetup-devel] Bug#779612: systemd-sysv,cryptsetup: systemd-sysv, cryptsetup should recommend plymouth; without plymouth cryptsetup prompts are unusable
On Sun, 08 Mar 2015 12:45:28 +0100, Jonas Meurer wrote: > Hi Gordon, > > thanks for the bugreport. I escalate this bugreport to the > debian-release team, asking for advice: would you accept another > cryptsetup upload targeted to jessie in order to add 'plymouth' to the > list of recommended packages? Thank you! > I agree that plymouth should be pulled in per default on jessie > installations with systemd and cryptsetup. While I don't know nothing > about systemd without plymouth, when cryptsetup comes into play, > plymouth is critical for the interactive password prompt at boot. > > Therefore I agree with the bug submitter, that cryptsetup in jessie > should recommend plymouth. > > I could upload cryptsetup packages with the added recommends immediately > after the pre-approval of the jessie release team. There are some differing opinions starting at about [1] on Bug#768314. I will attempt to direct them here. 1. https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=768314#160 Best, -Gordon M. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#779612: recommends, suggest, and which packages
Hi folks, My mention of creating Bug#779612 was intended to steer discussion of a packaging-related "fix" for jessie into that bug and out of this bug. ;) It's currently being discussed there[1] and has been escalated to the Debian release list. 1. https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=779612 Best, -Gordon M. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#771623: submitter reachable
Please use gor...@morehouse.me. I don't use the gmail, I'll see about setting up a forward. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#768314: proposed 'recommend' as suggested on debian-qa
On Wed, 04 Mar 2015 17:56:52 +0100, Michael Biebl wrote: > A recommends in systemd-sysv doesn't help on new installations, since > during debootstrap, recommends are not considered. I personally believe it should be a dependency, but I spoke with some people who are more involved in Debian than myself and got a suggestion to file a bug suggesting a recommendation. I don't like that for the exact reason you mentioned - they're still going to end up doing a web search and then finding something that they then have to fix. I am unsure of any problems that might be raised by adding a dependency on plymouth. Best, -Gordon M. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#768314: proposed 'recommend' as suggested on debian-qa
I've created Bug#779612 [1] to propose that 'systemd-sysv' and 'cryptsetup' recommend 'plymouth' in Jessie. There is related discussion in debian-qa[2]. 1. https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=779612 2. https://lists.debian.org/debian-qa/2015/02/msg00051.html -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#779612: systemd-sysv,cryptsetup: systemd-sysv, cryptsetup should recommend plymouth; without plymouth cryptsetup prompts are unusable
Package: systemd-sysv,cryptsetup Severity: important Dear Maintainer, Booting in jessie is currently nearly impossible with multiple cryptsetup volumes which are mounted at boot time. systemd spews messages over the prompt and there's a 90-second timeout while typing blind. Please see the bug report[1] and discussion on debian-qa[2]. The bug appears to be "fixed" by installing plymouth, so it's proposed that systemd-sysv and cryptsetup should at least recommend plymouth. This is a major usability problem for users with multiple required cryptsetup volumes, e.g. on /var and /usr. I do not believe jessie should ship as "stable" with it unresolved. 1. https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=768314 2. https://lists.debian.org/debian-qa/2015/02/msg00051.html -- System Information: Debian Release: 8.0 APT prefers testing APT policy: (900, 'testing') Architecture: amd64 (x86_64) Kernel: Linux 3.16-2-amd64 (SMP w/1 CPU core) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#768314: systemd: encrypted disk passphrase prompt nearly unusable
Package: systemd Version: 215-11 Followup-For: Bug #768314 Dear Maintainer, This renders systems with needed partitions (e.g. /var, /usr) on encrypted volumes near-totally unusable, especially if there are multiple partitions. I updated recently and the UI changed again. If anything, it's WORSE than it was when I first added information to this bug. I've uploaded a video to demonstrate it. I had to reboot twice before deciding to make the video, and twice more afterwards in order to actually boot my system so as to run 'reportbug' as I am doing now. Please see http://dai.ly/x2hmowq for video. In my opinion this is a major usability problem that should ABSOLUTELY NOT ship in anything called 'stable'. There are a lot of people with multiple encrypted partitions in the world, and this renders booting such machines a total crapshoot - and potentially near-impossible with enough encrypted partitions. -- Package-specific info: -- System Information: Debian Release: 8.0 APT prefers testing APT policy: (900, 'testing') Architecture: amd64 (x86_64) Kernel: Linux 3.16-2-amd64 (SMP w/1 CPU core) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages systemd depends on: ii acl 2.2.52-2 ii adduser 3.113+nmu3 ii initscripts 2.88dsf-58 ii libacl1 2.2.52-2 ii libaudit1 1:2.4-1+b1 ii libblkid1 2.25.2-5 ii libc6 2.19-13 ii libcap2 1:2.24-6 ii libcap2-bin 1:2.24-6 ii libcryptsetup4 2:1.6.6-5 ii libgcrypt20 1.6.2-4+b1 ii libkmod218-3 ii liblzma55.1.1alpha+20120614-2+b3 ii libpam0g1.1.8-3.1 ii libselinux1 2.3-2 ii libsystemd0 215-11 ii mount 2.25.2-5 ii sysv-rc 2.88dsf-58 ii udev215-11 ii util-linux 2.25.2-5 Versions of packages systemd recommends: ii dbus1.8.12-3 pn libpam-systemd Versions of packages systemd suggests: pn systemd-ui -- no debconf information -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#768314: cryptsetup: Passphrase prompt rolls by without stopping
Corrections on my above update, apologies: On Fri, 23 Jan 2015 16:35:09 -0800, Gordon Morehouse wrote: > What I expect to happen: > > 1. The system should STOP and WAIT for a password for any encrypted volume > which is marked as critical to boot (I had debconf ask me which of my md > devices were critical to boot during my last upgrade; since debconf didn't > tell me how to enter them ['md1'? 'md1_crypt'? how should I know?]) I forgot to add I told debconf 'all' here. > 3. The system should NOT have a countdown timer for encrypted filesystems > which are not critical. This should say "which ARE critical." Thanks, -Gordon M. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#776101: aptitude: hangs forever on 'setting up console-setup (1.116)'
Package: aptitude Version: 0.6.11-1+b1 Severity: important Dear Maintainer, running 'aptitude upgrade' followed by 'aptitude update' on a Debian testing system hangs after similar output from aptitude: Installing new version of config file /etc/console-setup/compose.ISO-8859-3.inc ... Installing new version of config file /etc/console-setup/compose.ISO-8859-4.inc ... Installing new version of config file /etc/console-setup/compose.ISO-8859-7.inc ... Installing new version of config file /etc/console-setup/compose.ISO-8859-9.inc ... Setting up console-setup (1.116) ... 'top' shows aptitude taking about 3-4% CPU but it is stuck. Ctrl-C is not effective. Kill with SIGTERM does stop the process while breaking terminal echo. It leaves the aptitude /var lockfile dirty. Running 'sudo dpkg --configure -a' has a couple errors about /var/cache/debconf/config.dat being locked as well. -- Package-specific info: Terminal: xterm $DISPLAY not set. which aptitude: /usr/bin/aptitude aptitude version information: aptitude 0.6.11 compiled at Nov 8 2014 13:34:39 Compiler: g++ 4.9.1 Compiled against: apt version 4.12.0 NCurses version 5.9 libsigc++ version: 2.4.0 Gtk+ support disabled. Qt support disabled. Current library versions: NCurses version: ncurses 5.9.20140913 cwidget version: 0.5.17 Apt version: 4.12.0 aptitude linkage: linux-vdso.so.1 (0x7fff45bfc000) libapt-pkg.so.4.12 => /usr/lib/x86_64-linux-gnu/libapt-pkg.so.4.12 (0x7fa67abcb000) libncursesw.so.5 => /lib/x86_64-linux-gnu/libncursesw.so.5 (0x7fa67a995000) libtinfo.so.5 => /lib/x86_64-linux-gnu/libtinfo.so.5 (0x7fa67a76a000) libsigc-2.0.so.0 => /usr/lib/x86_64-linux-gnu/libsigc-2.0.so.0 (0x7fa67a564000) libcwidget.so.3 => /usr/lib/x86_64-linux-gnu/libcwidget.so.3 (0x7fa67a24e000) libsqlite3.so.0 => /usr/lib/x86_64-linux-gnu/libsqlite3.so.0 (0x7fa679f85000) libboost_iostreams.so.1.55.0 => /usr/lib/x86_64-linux-gnu/libboost_iostreams.so.1.55.0 (0x7fa679d6d000) libxapian.so.22 => /usr/lib/libxapian.so.22 (0x7fa67995c000) libpthread.so.0 => /lib/x86_64-linux-gnu/libpthread.so.0 (0x7fa67973e000) libstdc++.so.6 => /usr/lib/x86_64-linux-gnu/libstdc++.so.6 (0x7fa679433000) libm.so.6 => /lib/x86_64-linux-gnu/libm.so.6 (0x7fa679132000) libgcc_s.so.1 => /lib/x86_64-linux-gnu/libgcc_s.so.1 (0x7fa678f1b000) libc.so.6 => /lib/x86_64-linux-gnu/libc.so.6 (0x7fa678b72000) libutil.so.1 => /lib/x86_64-linux-gnu/libutil.so.1 (0x7fa67896f000) libdl.so.2 => /lib/x86_64-linux-gnu/libdl.so.2 (0x7fa67876a000) libz.so.1 => /lib/x86_64-linux-gnu/libz.so.1 (0x7fa67854f000) libbz2.so.1.0 => /lib/x86_64-linux-gnu/libbz2.so.1.0 (0x7fa67833f000) liblzma.so.5 => /lib/x86_64-linux-gnu/liblzma.so.5 (0x7fa67811b000) librt.so.1 => /lib/x86_64-linux-gnu/librt.so.1 (0x7fa677f13000) libuuid.so.1 => /lib/x86_64-linux-gnu/libuuid.so.1 (0x7fa677d0d000) /lib64/ld-linux-x86-64.so.2 (0x7fa67b595000) -- System Information: Debian Release: 8.0 APT prefers testing APT policy: (900, 'testing') Architecture: amd64 (x86_64) Kernel: Linux 3.16-2-amd64 (SMP w/1 CPU core) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages aptitude depends on: ii aptitude-common 0.6.11-1 ii libapt-pkg4.121.0.9.6 ii libboost-iostreams1.55.0 1.55.0+dfsg-3 ii libc6 2.19-13 ii libcwidget3 0.5.17-2 ii libgcc1 1:4.9.1-19 ii libncursesw5 5.9+20140913-1+b1 ii libsigc++-2.0-0c2a2.4.0-1 ii libsqlite3-0 3.8.7.1-1 ii libstdc++64.9.1-19 ii libtinfo5 5.9+20140913-1+b1 ii libxapian22 1.2.19-1 Versions of packages aptitude recommends: ii aptitude-doc-en [aptitude-doc] 0.6.11-1 ii libparse-debianchangelog-perl 1.2.0-1.1 ii sensible-utils 0.0.9 Versions of packages aptitude suggests: pn apt-xapian-index pn debtags ii tasksel 3.29 -- no debconf information -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#771623: installation-reports: expert installer 'targeted' initrd does not contain modules for USB keyboard on intended system
Package: installation-reports Severity: normal Tags: d-i Dear Maintainer, Please ignore the system information, this is an attempt to install jessie beta 2 from netinst. I used 'expert mode' to install for various reasons, and when presented with the choice between generic and targeted initrd images, I chose targeted, since I was fairly comfortable that the hardware in this system will not change til EOL. I also set up an encrypted / and a cleartext /boot. Upon booting, I am asked: "Please unlock disk sdg5_crypt:" However, my USB keyboard is unusable despite working fine during most of the rest of the boot process. There is an excellent description of the problem at [1]. It appears that more USB / USBHID modules should be included in the 'targeted' initrd - having USB keyboard support broken on the system for which the initrd was targeted is not good, as you can't unlock your system without a PS/2 keyboard. 1. http://www.kasploosh.com/weblog/14000/14016-debian_jessie_usb_keyboard.html -- System Information: Debian Release: 7.6 Architecture: armhf (armv6l) Kernel: Linux 3.12.28+ (PREEMPT) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#771617:
This has happened to me again. It appears to happen any time the installer, in 'expert mode' (haven't tried normal mode), gets to "Starting up the partitioner" after making certain kinds of changes to encrypted volumes. I don't know what the set of those changes is, though. Again the same couple mke2fs statements in the log, followed by the same segfault with different ip and sp.
Bug#771617: installer beta 2: jessie parted_server segfault on AMD Athlon64
Package: installation-reports Severity: important Tags: d-i Dear Maintainer, Please ignore the system information, this is being submitted from a different system. I am attempting to install jessie on an Athlon64 3000+. This is the jessie DI netinst beta 2 amd64 iso installer. I was in the partitioner, had a RAID 6 of five disks and a RAID 5 of three disks configured as encrypted volumes (aes128 with ext4). I also had a microSD card configured originally as a cleartext btrfs volume and changed my mind and decided to encrypt it (or try) as well, after setting up the encrypted RAID volumes. The microSD would contain / and is at /dev/sdc - all physical drives are at /dev/sd[abd-j]. When I chose to set up encrypted filesystems from the installer to set up encryption on /, I noted that the installer already had some btrfs-related options (including mount point) in the encryption menu, as if setting up an encryption for an already-partitioned disk retains some of the settings made before. So I selected aes128, erase data no, and proceeded. I believe I was asked for a password but I can't remember as I also typed it elsewhere. Anyway, the installer hung at "Starting up the partitioner" - 81% - "Detecting file systems..." afterward - I was expecting the parman installer menu to be next again, or an error if I'd done something wrong. Alt-F4 shows me that parted_server segfaulted. Here are 4 lines, which I'm typing from my other screen. I am not sure what the mke2fs lines were about - perhaps remaking my two ext4 filesystems on other volumes? - but I'm putting them there for context. Dec 1 01:20:41 partman: mke2fs 1.42.12 (29-Aug-2014) Dec 1 01:20:54 partman: mke2fs 1.42.12 (29-Aug-2014) Dec 1 01:21:32 partman-crypto: kernel entropy_avail: 1357 bits Dev 1 01:22:37 kernel: [ 1778.893717] parted_server[22481]: segfault at 8 ip 0040b485 sp 7fff9ddb8e50 error 4 in parted_server[40+12000] To summarize, this happened after I'd set up file systems, set up encrypted volumes on top of software RAID, then changed my mind and gone back in to set up an encrypted volume for / on a microSD card in a USB adapter. This system has (to the best of my knowledge during earlier installations today) successfully booted from MicroSD using Wheezy. So, probably an edge case, but it hangs the installer. -- System Information: Debian Release: 7.6 Architecture: armhf (armv6l) Kernel: Linux 3.12.28+ (PREEMPT) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#770873: bugs.debian.org: http://bugs-search.debian.org/cgi-bin/search.cgi completely broken (HTTP 500)
Package: bugs.debian.org Severity: grave Justification: renders package unusable Dear Maintainer, The "HyperEstraier based search engine" for bugs does not work. Steps to reproduce: 1. Visit http://bugs-search.debian.org/cgi-bin/search.cgi 2. Enter some text and search 3. Receive HTTP 500 -- System Information: Debian Release: 7.6 Architecture: armhf (armv6l) Kernel: Linux 3.12.28+ (PREEMPT) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#770870: cdimage.debian.org: Untrustworthy key used to sign SHA512SUMS: DF9B 9C49 EAA9 2984 3258 9D76 DA87 E80D 6294 BE9B
Package: cdimage.debian.org Severity: important Dear Maintainer, Debian 7.7 SHA512SUMS are signed with a key that doesn't appear to be signed by anyone on the Debian keyring, leaving SHA512SUMS unverifiable by any easy means. Please note that I have the debian keyring installed in GPG on the machine on which the following operation was performed. $ gpg --verify SHA512SUMS.sign gpg: Signature made Sun Oct 19 19:45:39 2014 PDT using RSA key ID 6294BE9B gpg: Good signature from "Debian CD signing key " gpg: WARNING: This key is not certified with a trusted signature! gpg: There is no indication that the signature belongs to the owner. Primary key fingerprint: DF9B 9C49 EAA9 2984 3258 9D76 DA87 E80D 6294 BE9B Meanwhile, it appears this has been noted as a problem since 2011 on the Debian forums: http://forums.debian.net/viewtopic.php?f=17&t=62272&p=561324 I shouldn't need to remind anyone that we are living in an age of known MitM attacks versus FOSS software downloads. Verifying Debian ISOs NEEDS TO BE EASY. I can pretty much guarantee you I'm the 1 in 100 users who wouldn't have given up reporting this when: * I got an HTTP 500 from the "HyperEstraier based search engine" for Debian bugs at http://bugs-search.debian.org/cgi-bin/search.cgi when I looked to see if it had already been reported * I came up against the 11-printed-pages wall of text at https://www.debian.org/Bugs/Reporting * I found through the wall of text that there was no web interface for bug reporting, in this, the Year of Our Lord 2014 * I had to install 'reportbug' on a random Raspberry Pi just to get you this message. I know that producing Debian is hard work and that Debian is an accretion of decades of hard work, but peeps. Snowden. NSA. This is not 1998. Verifying downloaded software needs to be EASY TO DO, and you might want bug reporting to be easy to do, too, even though it involves dealing with lots of dupes from noobs - if your system is byzantine and/or broken enough to put off actual software developers, it's ungood. -- System Information: Debian Release: 7.6 Architecture: armhf (armv6l) Kernel: Linux 3.12.28+ (PREEMPT) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
