Bug#512764: procps: Misleading comment in /etc/sysctl.conf.
Package: procps Version: 1:3.2.7-11 Severity: minor Version 1:3.2.7-10 adds the following comment to /etc/sysctl.conf: # This disables TCP Window Scaling (http://lkml.org/lkml/2008/2/5/167), # and is not recommended. This comment is misleading, as can easily be determined by reading the rest of the linked thread. Quoting Alan Cox: Syncookies only get used at the point where the alternative is failure. No SACK beats a DoS situation most days See also http://lwn.net/Articles/277146/ for more information about why syncookies are still useful. -- System Information: Debian Release: 5.0 APT prefers testing APT policy: (500, 'testing'), (500, 'stable') Architecture: i386 (i686) Kernel: Linux 2.6.26-1-686 (SMP w/2 CPU cores) Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/bash Versions of packages procps depends on: ii libc6 2.7-18 GNU C Library: Shared libraries ii libncurses5 5.7+20081213-1 shared libraries for terminal hand ii lsb-base 3.2-20 Linux Standard Base 3.2 init scrip Versions of packages procps recommends: ii psmisc22.6-1 Utilities that use the proc filesy procps suggests no packages. -- 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#475669: Suggest informing the user
Thanks Shaun, The last time I had Azureus working was also with Sun's VM. I didn't use it for several months, and it looks like the default java VM was switched to GIJ by an upgrade in the meantime. So unfortunately I cannot confirm whether it worked previously. I just tested with gij 4.1 and gij 4.2, and they both exhibit the same behaviour as gij 4.3, ie. they fail to establish any peer connections. Thanks, Adam On Thursday 01 May 2008 22:17:26 Shaun Jackman wrote: Hi Adam, My preference would be to fix the bug, of course! But with the bug being 180 days old now, it might be time to look at a workaround like this. Do you know, does Azureus work with any other versions of GIJ? I know that it works with Sun's VM. Cheers, Shaun On Thu, May 1, 2008 at 1:45 PM, Adam Rice [EMAIL PROTECTED] wrote: The problem is that it comes so close to working with gij-4.3 that it's hard to notice that anything is actually wrong. How about putting a temporary hack in the /usr/bin/azureus script to check if /usr/bin/java is gij-4.3 and popup an xmessage saying something like You are running azureus with gij-4.3. There are known problems with this combination. See http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=475669 for details. If your torrents fail to download, please consider selecting a different java interpreter using the update-alternatives program. ? I guess that would add a dependency on the xll-utils package, which is not so nice. But printing a message to the console is not much use for people who start azureus from iceweasel like I usually do. -- /-/ Adam Rice / [EMAIL PROTECTED] / Tokyo, Japan /-/ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#475669: Suggest informing the user
The problem is that it comes so close to working with gij-4.3 that it's hard to notice that anything is actually wrong. How about putting a temporary hack in the /usr/bin/azureus script to check if /usr/bin/java is gij-4.3 and popup an xmessage saying something like You are running azureus with gij-4.3. There are known problems with this combination. See http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=475669 for details. If your torrents fail to download, please consider selecting a different java interpreter using the update-alternatives program. ? I guess that would add a dependency on the xll-utils package, which is not so nice. But printing a message to the console is not much use for people who start azureus from iceweasel like I usually do. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#467522: googleearth-package: /usr/lib/googleearth/linux/README-mailto.txt
Package: googleearth-package Version: 0.5.3 Severity: minor The file /usr/lib/googleearth/linux/README-mailto.txt in the generated package should be moved to /usr/share/doc/googleearth. googleearth version is 4.2.205.5730. -- System Information: Debian Release: 4.0 APT prefers stable APT policy: (500, 'stable') Architecture: i386 (i686) Shell: /bin/sh linked to /bin/bash Kernel: Linux 2.6.18-6-686 Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8) Versions of packages googleearth-package depends on: ii bzip21.0.3-6 high-quality block-sorting file co ii dpkg-dev 1.13.25 package building tools for Debian ii fakeroot 1.5.10 Gives a fake root environment ii file 4.17-5etch3 Determines file type using magic ii wget 1.10.2-2retrieves files from the web ii x11-common 1:7.1.0-19 X Window System (X.Org) infrastruc googleearth-package recommends no packages. -- no debconf information
Bug#462352: doc-linux-text: The X Window User HOWTO contains misleading font comment
Package: doc-linux-text Version: 2007.02-1 Severity: minor XWindow-User-HOWTO.gz contains the statement: Terminal emulators like xterm require a monospaced font. So forget about TrueType or Type 1 fonts. This is wrong on two counts: firstly monospaced TrueType fonts exist, and secondly xterm supports them. xterm -fa Courier New works very nicely on my system, thankyou (I have the msttcorefonts package installed). -- System Information: Debian Release: 4.0 APT prefers stable APT policy: (500, 'stable') Architecture: i386 (i686) Shell: /bin/sh linked to /bin/bash Kernel: Linux 2.6.18-5-686 Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8) -- no debconf information -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#404565: shaper stop spews errors when network interfaces containing capital letters are present
Package: shaper
Version: 2.2.12-0.7.3-2.1
Severity: normal
Tags: patch
When the system has network interfaces with capital letters in their
names, many errors are displayed at shutdown time. For example:
Cannot find device 2:
RTNETLINK answers: No such file or directory
Cannot find device BROADCAST,MULT
Cannot find device mtu
Cannot find device 576
Cannot find device qdisc
Cannot find device pfifo_fast
Cannot find device qlen
Cannot find device 1000
Cannot find device 3:
The cause is that the part of the script which parser the output of ip
link show does not allow for network interface names containing
capital letters. I have attached a patch which explicitly allows capital
letters in the interface name. It might be worth making the parsing even
more forgiving, since the failure mode is so ugly.
-- System Information:
Debian Release: 4.0
APT prefers testing
APT policy: (500, 'testing')
Architecture: i386 (i686)
Shell: /bin/sh linked to /bin/bash
Kernel: Linux 2.6.18-3-k7
Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8)
Versions of packages shaper depends on:
ii debconf [debconf-2.0] 1.5.8 Debian configuration management sy
ii iproute 20061002-3 Professional tools to control the
shaper recommends no packages.
-- debconf information:
* shaper/kernel-modules:
--- shaper.bak 2006-12-26 11:43:24.0 +
+++ shaper 2006-12-26 11:44:10.0 +
@@ -516,7 +516,7 @@
### Get list of network devices
cbq_device_list () {
ip link show| sed -n /^[0-9]/ \
- { s/^[0-9]\+: \([a-z0-9._]\+\)[:@].*/\1/; p; }
+ { s/^[0-9]\+: \([a-zA-Z0-9._]\+\)[:@].*/\1/; p; }
} # cbq_device_list
Bug#368464: python-minimal: Package description is blatantly deceptive
Package: python-minimal Version: 2.3.5-5 Severity: normal A minimal subset of the Python language This package pulls in the entirity of Python, and unless you want to alienate Python upstream, it always will. This package contains the interpreter and some essential modules. True if you consider some essential modules to mean all of them, as upstream apparently does. It's used in the boot process for some basic tasks. Blatantly untrue. See /usr/share/doc/python-minimal/README.Debian for a list of the modules contained in this package. There is no such list in that file. -- System Information: Debian Release: testing/unstable APT prefers testing APT policy: (500, 'testing') Architecture: i386 (i686) Shell: /bin/sh linked to /bin/bash Kernel: Linux 2.6.12-1-k7 Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8) Versions of packages python-minimal depends on: ii python2.3 2.3.5-9.1 An interactive high-level object-o python-minimal recommends no packages. -- no debconf information -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#368462: alsa-utils depends on dummy package python-minimal
Package: alsa-utils Version: 1.0.11-2 Severity: minor python-minimal is a dummy package which appears to exist only in a misguided attempt to be compatible with Ubuntu. Since it pulls in the whole of Python anyway (python upstream strongly disproves of incomplete installations), there's no benefit in depending on it. In fact, to avoid perpetuating this error it is better to ignore it completely. Please go back to depending on python so I can uninstall python-minimal and have my 24 kilobytes back. -- System Information: Debian Release: testing/unstable APT prefers testing APT policy: (500, 'testing') Architecture: i386 (i686) Shell: /bin/sh linked to /bin/bash Kernel: Linux 2.6.12-1-k7 Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8) Versions of packages alsa-utils depends on: ii dialog1.0-20060221-1 Displays user-friendly dialog boxe ii libasound21.0.11-3 ALSA library ii libc6 2.3.6-7GNU C Library: Shared libraries ii libncurses5 5.5-1.1Shared libraries for terminal hand ii linux-sound-base 1.0.11-1 base package for ALSA and OSS soun ii lsb-base 3.1-5 Linux Standard Base 3.1 init scrip ii module-init-tools 3.2.2-2tools for managing Linux kernel mo ii modutils 2.4.27.0-5 Linux module utilities ii pciutils 1:2.1.11-16Linux PCI Utilities ii python-minimal2.3.5-5A minimal subset of the Python lan ii whiptail 0.51.6-31 Displays user-friendly dialog boxe Versions of packages alsa-utils recommends: ii alsa-base 1.0.11-1 ALSA driver configuration files -- no debconf information -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#356501: python2.4-minimal: This package should not exist
Package: python2.4-minimal Version: 2.4.2-2 Severity: normal python-minimal only exists in Ubuntu so that users can uninstall python without breaking the base system. Ubuntu has an agreement with the python developers that a user will only get a system with python-minimal but without the full python base packages if they specifically request it. Debian is not Ubuntu. Debian has no such agreement, and the only way Debian could have such an agreement was if python was in the base system, which it is not. The only purpose python-minimal can serve in Debian is to force the inclusion of python into the base system. Since there is neither a technical need for this nor a consensus supporting it, I ask that python-minimal be removed. -- System Information: Debian Release: testing/unstable APT prefers testing APT policy: (500, 'testing') Architecture: i386 (i686) Shell: /bin/sh linked to /bin/bash Kernel: Linux 2.6.12-1-k7 Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8) Versions of packages python2.4-minimal depends on: ii libc6 2.3.5-13 GNU C Library: Shared libraries an ii zlib1g1:1.2.3-9 compression library - runtime python2.4-minimal recommends no packages. -- no debconf information -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#340717: libc-client2002edebian: cram-md5.pwd format ridiculously finicky
Jonas Smedegaard wrote: On Fri, 25 Nov 2005 11:12:52 + Adam Rice [EMAIL PROTECTED] wrote: The format of /etc/cram-md5.pwd is usertabpassword. This is particularly troublesome for those of us with 7-character usernames, as the tabs become indistinguishable from spaces. Naturally if you get it wrong, no error is reported. Annoyance - but how is it a bug? If one user can log in, and another can't, and there's no visible difference between the configuration of the two, I'd call that a bug. Frankly I think uw-imapd should come with free beer. Or is this the bug? That's more of a feature request. Adam -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#340717: libc-client2002edebian: cram-md5.pwd format ridiculously finicky
Package: libc-client2002edebian Version: 7:2002edebian1-12 Severity: normal The format of /etc/cram-md5.pwd is usertabpassword. This is particularly troublesome for those of us with 7-character usernames, as the tabs become indistinguishable from spaces. Naturally if you get it wrong, no error is reported. Frankly I think uw-imapd should come with free beer. -- System Information: Debian Release: testing/unstable APT prefers testing APT policy: (500, 'testing') Architecture: i386 (i686) Shell: /bin/sh linked to /bin/bash Kernel: Linux 2.4.27 Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8) Versions of packages libc-client2002edebian depends on: ii debconf1.4.59Debian configuration management sy ii libc6 2.3.5-8 GNU C Library: Shared libraries an ii libcomerr2 1.38-2common error description library ii libkrb53 1.3.6-5 MIT Kerberos runtime libraries ii libpam-modules 0.79-3Pluggable Authentication Modules f ii libpam0g 0.79-3Pluggable Authentication Modules l ii libssl0.9.80.9.8a-3 SSL shared libraries ii mlock 7:2002edebian1-12 Mailbox locking program from UW libc-client2002edebian recommends no packages. -- debconf information: * libc-client/plaintext: yes * libc-client/no_maildir_warning: true -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#295921: caudium: Caudium takes over from Apache
Marek Habersack wrote: So my guess is that for some weird reason the above pulls caudium-php4 and, in consequence, caudium. I'm also wondering whether caudium asked you about the port it should listen on - it should have done that precisely to avoid clash with any installed webserver. In my case, the upgrade was done with cron-apt, so I guess the question was suppressed. If I had done the apt-get dist-upgrade manually, I probably would have noticed something weird was afoot. Now that I'm thinking, maybe it's a bug in apt not in php4. Either way, I'll try to look closer into the issue and see where to assign the bug, Possibly the new version of the caudium-php4 package arrived in testing before libapache-mod-php4, and so apt took the rather drastic step of installing caudium to resolve the dependency. I don't know how I'd confirm that theory though. If it's true, I can prevent it happening again by uninstalling the php4 package. Otherwise I might find myself with an unscheduled upgrade to Apache 2 next time :-) Adam -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#295921: caudium: Caudium takes over from Apache
This just happened to me too. I don't know why Caudium was installed, but the result was major suckage. This may not actually be a bug in Caudium, but in the depends for another package. But I was able to uninstall Caudium without difficultly, so frankly, I'm confused. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#295642: minor English changes for cupsys.postinst
Package: cupsys Version: 1.1.23-4 Severity: wishlist Tags: patch I changed the wording of some sentences in cupsys.postinst to make them more readable. Please consider applying this patch. --- cupsys.postinst.old 2005-02-17 05:05:53.0 + +++ cupsys.postinst 2005-02-17 05:29:25.0 + @@ -29,10 +29,10 @@ configure) # Check cupsys is really stopped... stupid if [ -n `ps aux | grep /usr/sbin/cupsd | grep -v grep` ]; then - echo Hmm, cupsys won't stop... I wait 5 seconds... + echo Cupsys is still running... waiting 5 seconds... sleep 5 if [ -n `ps aux | grep /usr/sbin/cupsd | grep -v grep` ]; then - echo Retrying to stop... + echo Killing cupsys... kill -9 `pidof /usr/sbin/cupsd` || true fi fi @@ -151,7 +151,7 @@ EOT else -echo Your /etc/cups/cupsd.conf seems be edited by your hand. cupsys.postinst doesn't touch this. +echo Your /etc/cups/cupsd.conf appears to have been manually edited. cupsys.postinst won't touch it. fi fi ;; -- System Information: Debian Release: 3.1 APT prefers testing APT policy: (500, 'testing') Architecture: i386 (i686) Kernel: Linux 2.4.27 Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8) Versions of packages cupsys depends on: ii adduser 3.59 Add and remove users and groups ii debconf 1.4.30.11Debian configuration management sy ii libc6 2.3.2.ds1-20 GNU C Library: Shared libraries an ii libcupsimage2 1.1.23-4 Common UNIX Printing System(tm) - ii libcupsys2-gnutls10 1.1.23-4 Common UNIX Printing System(tm) - ii libgnutls11 1.0.16-9 GNU TLS library - runtime library ii libpam0g0.76-22 Pluggable Authentication Modules l ii libpaper1 1.1.14-3 Library for handling paper charact ii libslp1 1.0.11a-1OpenSLP libraries ii patch 2.5.9-2 Apply a diff file to an original ii perl-modules5.8.4-6 Core Perl modules ii xpdf-utils 3.00-12 Portable Document Format (PDF) sui ii zlib1g 1:1.2.2-3compression library - runtime -- debconf information: cupsys/raw-print: true * cupsys/backend: ipp, lpd, parallel, socket, usb -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
