Bug#614931: vim-puppet: addon should be enabled by default
Package: vim-puppet Version: 2.6.4-2 Having to manually complete the installation feels suboptimal and not really in keeping with the Debian experience. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#574697: please test proposed fix
Michael Biebl bi...@debian.org writes: Could you all, who experienced this crashes with 1.2.22 in dbus-daemon, try the packages from [1] and report back if they fix your problems. I can no longer reproduce the problem with these packages installed. Regards, -- Paul Collins Wellington, New Zealand Dag vijandelijk luchtschip de huismeester is dood -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#574697: dbus-x11: dbus segfaults when closing ppp connections using network-manager
,
revents = 0}, {fd = 35, events = 1, revents = 0}, {fd = 38, events
= 1, revents = 1}, {fd = -341383259, events = 32590, revents = 0}, {
fd = 67108864, events = 0, revents = 0}, {fd = -350361200, events =
32590, revents = 0}, {fd = 0, events = 0, revents = 0} repeats 16 times, {
fd = -341524480, events = 32590, revents = 0}, {fd = 57, events =
0, revents = 0}, {fd = -341232933, events = 32590, revents = 0}, {
fd = -341383259, events = 32590, revents = 0}, {fd = -341284272,
events = 15, revents = 0}, {fd = 0, events = 0, revents = 0}, {fd = 0,
events = 0, revents = 0}, {fd = 0, events = 0, revents = 0}, {fd =
0, events = 0, revents = 0}, {fd = 0, events = 0, revents = 0}, {fd = 0,
events = 0, revents = 0}}
n_fds = 34
watches_for_fds = 0x7f4eedcb4cb0
stack_watches_for_fds = {0x7f4eedc328a0, 0x7f4eedc2f190,
0x7f4eedc20090, 0x7f4eedc1d190, 0x7f4eedc22e60, 0x7f4eedc28130, 0x7f4eedc3a3a0,
0x7f4eedc3d9e0, 0x7f4eedc47c60, 0x7f4eedc47380, 0x7f4eedc457a0,
0x7f4eedc44600, 0x7f4eedc4eda0, 0x7f4eedc5c670, 0x7f4eedc5f370, 0x7f4eedc625a0,
0x7f4eedc65c20, 0x7f4eedc68590, 0x7f4eedc6ab60, 0x7f4eedc6d130,
0x7f4eedc6ef10, 0x7f4eedc6f800, 0x7f4eedc71010, 0x7f4eedc8d310, 0x7f4eedc905b0,
0x7f4eedc90f60, 0x7f4eedc923c0, 0x7f4eedc97460, 0x7f4eedc94180,
0x7f4eedc8fce0, 0x7f4eedcab970, 0x7f4eedcad920, 0x7f4eedcab470, 0x7f4eedcad920,
0x0,
0x7fff367bff80, 0x0, 0x7f4eeba31630, 0x7fff367c00d0, 0x8, 0x3,
0x7f4eeb83a07d, 0x6, 0x7fff367c00e8, 0x7f4eeb1d0a78, 0x0, 0x7fff367bff80,
0x7f4eeb1d0e10, 0x0, 0x7f4eeba316b8, 0x7f4eeba32000, 0x7f4eeba50e7c,
0x7f4eeb1d2b68, 0x7f4eeba50140, 0x1, 0x10053, 0x,
0x7f4eeba4c358, 0x7fff367c0120, 0x7f4eeba316b8, 0x0, 0x7fff367c0148,
0xf375846, 0x7f4eeb83a3b9}
i = 34
link = 0x0
n_ready = 1
initial_serial = 113
timeout = -1
oom_watch_pending = 0
orig_depth = 1
#11 0x7f4eeba9079c in _dbus_loop_run (loop=0x7f4eedc1c1a0) at
dbus-mainloop.c:874
our_exit_depth = 0
#12 0x7f4eeba6f4c0 in main (argc=2, argv=0x7fff367c0508) at main.c:476
error = {name = 0x0, message = 0x0, dummy1 = 1, dummy2 = 0, dummy3 = 0,
dummy4 = 0, dummy5 = 0, padding1 = 0x7f4eeba9d0c0}
config_file = {dummy1 = 0x7f4eedc1c070, dummy2 = 23, dummy3 = 31,
dummy4 = 2147483639, dummy5 = 0, dummy6 = 0, dummy7 = 1, dummy8 = 0}
addr_fd = {dummy1 = 0x7f4eedc1c030, dummy2 = 0, dummy3 = 8, dummy4 =
2147483639, dummy5 = 0, dummy6 = 0, dummy7 = 1, dummy8 = 0}
pid_fd = {dummy1 = 0x7f4eedc1c050, dummy2 = 0, dummy3 = 8, dummy4 =
2147483639, dummy5 = 0, dummy6 = 0, dummy7 = 1, dummy8 = 0}
prev_arg = 0x7fff367c0ce0 --system
print_addr_pipe = {fd_or_handle = -1}
print_pid_pipe = {fd_or_handle = -1}
i = 2
print_address = 0
print_pid = 0
force_fork = 0
Regards,
--
Paul Collins
Wellington, New Zealand
Dag vijandelijk luchtschip de huismeester is dood
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#574697: [Pkg-utopia-maintainers] Bug#574697: dbus-x11: dbus segfaults when closing ppp connections using network-manager
Michael Biebl bi...@debian.org writes: Am 21.03.2010 05:29, schrieb Paul Collins: Since upgrading from dbus 1.2.20-2 to 1.2.22-1 I've also had problems with the system dbus-daemon crashing. In my case I can trigger it easily by toggling Bluetooth on and off with the Bluetooth applet's menu. Here's the backtrace I gathered: Thanks for the bt. Do you by chance, also have a 64bit (amd64) system? Yes, I do. -- Paul Collins Wellington, New Zealand Dag vijandelijk luchtschip de huismeester is dood -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#574422: pmud: CRITICAL_VOLT is an order of magnitude too high
Package: pmud Version: 0.10-11 Tags: patch Following an upgrade to squeeze, my PowerBook G4 began suspending every time I unplugged the AC. I believe this is because CRITICAL_VOLT defaults to 100,000 millivolts (100V) instead of 10,000 millivolts (10V). I'm using the patch below and pmud now behaves as I expect. diff --git a/pmud.h b/pmud.h index d6a96a7..9739da1 100644 --- a/pmud.h +++ b/pmud.h @@ -83,7 +83,7 @@ /* take immediate action once voltage drops this low */ -#define CRITICAL_VOLT 10 +#define CRITICAL_VOLT 1 #define BEEP_TIME 150 #define BEEP_OK 1000 -- Paul Collins Wellington, New Zealand Dag vijandelijk luchtschip de huismeester is dood -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#564176: QLScrobbler is cruising for a bruising
Package: quodlibet-plugins
Version: 20100104-1
I have not enabled QLScrobbler, and I do not plan to enable it.
Nevertheless, every time I start quodlibet or refresh the plugins,
it insists on asking me to configure it. I fixed it like so,
Conan-style, but perhaps this is not the best way to do it.
--- events/qlscrobbler.py 2010-01-05 09:23:37.0 +1300
+++ /usr/share/pyshared/quodlibet/plugins/events/qlscrobbler.py 2010-01-08
20:08:22.0 +1300
@@ -149,6 +149,8 @@
return 0
def check_config(self):
+if not self.__enabled:
+return
user = config_get('username')
passw = md5(config_get('password')).hexdigest()
url = config_get_url()
--
Paul Collins
Wellington, New Zealand
Dag vijandelijk luchtschip de huismeester is dood
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#546833: libgc-dev: pkg-config file missing
Rebuilding with the following applied does the trick. diff --git a/debian/libgc-dev.install b/debian/libgc-dev.install index 0daebed..8287a36 100644 --- a/debian/libgc-dev.install +++ b/debian/libgc-dev.install @@ -2,6 +2,7 @@ usr/include usr/lib/libgc*.so usr/lib/libgc*.a usr/lib/libgc*.la +usr/lib/pkgconfig/bdw-gc.pc usr/share/doc/gc/*.html usr/share/doc/libgc1c2 usr/share/doc/gc/barrett_diagram usr/share/doc/libgc1c2 usr/share/doc/gc/README usr/share/doc/libgc1c2 -- Paul Collins Wellington, New Zealand Dag vijandelijk luchtschip de huismeester is dood -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#555551: swfdec0.8: utc-offset property's range is too limited
Package: libswfdec-0.8-0 Version: 0.8.4-1 I just noticed the following: (epiphany-browser:21566): GLib-GObject-WARNING **: value 780 of type `gint' is invalid or out of range for property `utc-offset' of type `gint' After some spelunking I discovered this in swfdec0.8: g_object_class_install_property (object_class, PROP_UTC_OFFSET, g_param_spec_int (utc-offset, utc offset, Difference between UTC and local timezone in minutes, -12 * 60, 12 * 60, 0, G_PARAM_READWRITE | G_PARAM_CONSTRUCT)); which limits the values of the property to plus or minus 12 hours. However, there are places on Earth whose offset from UTC can exceed 12 hours; here in New Zealand, which is in UTC+12, daylight saving time means that the current offset from UTC is 13 hours, which results in the above message. Per http://en.wikipedia.org/wiki/List_of_time_zones#UTC.2B12.2C_M the allowable range should probably be -12 to +14 hours. -- Paul Collins Wellington, New Zealand Dag vijandelijk luchtschip de huismeester is dood -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#548390: python-mpd: upgrade fails due to pycentral pkgremove python-gammu in preinst
Package: python-mpd Version: 0.2.1-2 (Reading database ... 97 files and directories currently installed.) Preparing to replace python-mpd 0.2.1-1 (using .../python-mpd_0.2.1-2_all.deb) ... pycentral: pycentral pkgremove: package python-gammu is not installed pycentral pkgremove: package python-gammu is not installed dpkg: error processing /var/cache/apt/archives/python-mpd_0.2.1-2_all.deb (--unpack): subprocess new pre-installation script returned error exit status 1 Errors were encountered while processing: /var/cache/apt/archives/python-mpd_0.2.1-2_all.deb E: Sub-process /usr/bin/dpkg returned an error code (1) -- Paul Collins Wellington, New Zealand Dag vijandelijk luchtschip de huismeester is dood -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#534765: udev: vol_id does not recognize ext4 volumes that have no journal
Package: udev Version: 0.141-1 vol_id does not recognize ext4 volumes that have no journal, which means that such volumes are not added to /dev/disk/by-uuid and /dev/disk/by-label when presented to the system. # mke2fs -T ext4 -L ext4journalled /dev/sdb1 mke2fs 1.41.6 (30-May-2009) Filesystem label=ext4journalled OS type: Linux Block size=4096 (log=2) Fragment size=4096 (log=2) 244800 inodes, 977329 blocks 48866 blocks (5.00%) reserved for the super user First data block=0 Maximum filesystem blocks=1002438656 30 block groups 32768 blocks per group, 32768 fragments per group 8160 inodes per group Superblock backups stored on blocks: 32768, 98304, 163840, 229376, 294912, 819200, 884736 Writing inode tables: done Creating journal (16384 blocks): done Writing superblocks and filesystem accounting information: done This filesystem will be automatically checked every 35 mounts or 180 days, whichever comes first. Use tune2fs -c or -i to override. # vol_id /dev/sdb1 ID_FS_USAGE=filesystem ID_FS_TYPE=ext4 ID_FS_VERSION=1.0 ID_FS_UUID=0372d93a-762f-41b5-8500-aa2f23598e4c ID_FS_UUID_ENC=0372d93a-762f-41b5-8500-aa2f23598e4c ID_FS_LABEL=ext4journalled ID_FS_LABEL_ENC=ext4journalled # mke2fs -T ext4 -L ext4notjournalled -O ^has_journal /dev/sdb1 mke2fs 1.41.6 (30-May-2009) Filesystem label=ext4notjournalled OS type: Linux Block size=4096 (log=2) Fragment size=4096 (log=2) 244800 inodes, 977329 blocks 48866 blocks (5.00%) reserved for the super user First data block=0 Maximum filesystem blocks=1002438656 30 block groups 32768 blocks per group, 32768 fragments per group 8160 inodes per group Superblock backups stored on blocks: 32768, 98304, 163840, 229376, 294912, 819200, 884736 Writing inode tables: done Writing superblocks and filesystem accounting information: done This filesystem will be automatically checked every 21 mounts or 180 days, whichever comes first. Use tune2fs -c or -i to override. # vol_id /dev/sdb1 unknown or non-unique volume type (--probe-all lists possibly conflicting types) -- Paul Collins Wellington, New Zealand Dag vijandelijk luchtschip de huismeester is dood -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#534649: irssi: some signals are no longer available in Perl environment
Package: irssi Version: 0.8.13-2 The following four signals are no longer available in irssi's Perl environment: $ grep '$' docs/signals.txt gui exit setup changed irssi init read settings beep They are not present in src/perl/perl-signals-list.h, which is generated by src/perl/get-signals.pl from docs/signals.txt. A quick review of get-signals.pl reveals that this script does not account for the possibility of signals having no arguments. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#529282: [Pkg-libvirt-maintainers] Bug#529282: Bug#529282: libvirt: questionable build-dep on open-iscsi
Guido Günther a...@sigxcpu.org writes: On Tue, May 19, 2009 at 08:48:00AM +1200, Paul Collins wrote: It checks for it to get the binary paths. I'm sorry, but that's really silly. Why doesn't it build-dep on kvm, for example, to make sure it still lives in /usr/bin/kvm? It checks for several (iscsiadm, parted, ...) but not all of the needed binaries. That should probably be fixed. Debian packages put binaries in one of a very few standard locations and they do not change often. Adding checks is a waste of your time and will needlessly bloat your build-deps. -- Paul Collins Wellington, New Zealand Dag vijandelijk luchtschip de huismeester is dood -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#529408: libvirtd does not work with kvm-85
Package: libvirt-bin Version: 0.6.3-2 libvirtd no longer works with kvm as of version 85 (now available in Debian experimental), apparently due to the increased length of the kvm -help output. I have tested the patch below and it fixes the problem. http://article.gmane.org/gmane.comp.emulators.libvirt/13498/raw -- Paul Collins Wellington, New Zealand Dag vijandelijk luchtschip de huismeester is dood -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#525588: bridged network stop working with kvm 84
Daniel Dehennin daniel.dehen...@baby-gnu.org writes: Le 5717 Septembre 1993, Paul Collins a envoyé: I noticed this problem cropped up when I upgraded from Linux 2.6.29 to Linux 2.6.29.1, so bisecting the kernel may be worth a try. One one host system I use a bridge and on the other a private network with NAT, so it seems to be a more general problem. Switching my VMs to use emulated hardware NICs instead of virtio worked around the problem. I test with 2.6.28.1: - on both host and guest - only on host, - only on guest With kvm 72-dfsg-5 it's ok, with kvm-84 it does not work. It works fine again here with kvm-85. -- Paul Collins Wellington, New Zealand Dag vijandelijk luchtschip de huismeester is dood -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#529410: kvm-85: booting from virtio under libvirt no longer works due to help text change
Package: kvm
Version: 85+dfsg-1
As of version 85, kvm -help no longer reports the availability of the
boot={on,off} option, which causes libvirt to assume it is not
available. This in turn causes booting from virtio block devices to
fail. This patch, taken from the qemu-kvm git tree's commit
d7580e4dc3d10161fbcd591105af99d1cac2e370, fixes the problem for me.
From d7580e4dc3d10161fbcd591105af99d1cac2e370 Mon Sep 17 00:00:00 2001
From: Pauline Middelink middel...@polyware.nl
Date: Mon, 27 Apr 2009 09:57:42 +0200
Subject: [PATCH] Re-add -drive boot= parameter help text
Small regression. libvirt determines the use of the boot= flag by looking
at the helptext. This flag is required for booting off virtio-blk devices.
The description was lost in the last upstream merge; this patch re-adds it.
Signed-off-by: Pauline Middelink middel...@polyware.nl
Signed-off-by: Avi Kivity a...@redhat.com
---
qemu-options.hx |1 +
1 files changed, 1 insertions(+), 0 deletions(-)
diff --git a/qemu-options.hx b/qemu-options.hx
index d5e0b85..a11ead9 100644
--- a/qemu-options.hx
+++ b/qemu-options.hx
@@ -92,6 +92,7 @@ DEF(drive, HAS_ARG, QEMU_OPTION_drive,
-drive [file=file][,if=type][,bus=n][,unit=m][,media=d][,index=i]\n
[,cyls=c,heads=h,secs=s[,trans=t]][,snapshot=on|off]\n
[,cache=writethrough|writeback|none][,format=f][,serial=s]\n
+ [,boot=on|off]\n
use 'file' as a drive image\n)
STEXI
@item -drive @var{option}[,@var{option}[,@var{option}[,...]]]
--
1.6.3.1
--
Paul Collins
Wellington, New Zealand
Dag vijandelijk luchtschip de huismeester is dood
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#529280: open-iscsi is uninstallable
Package: open-iscsi Version: 2.0.870~rc3-0.4 Severity: grave Having never used this package before, a fresh install yields Setting up open-iscsi (2.0.870~rc3-0.4) ... Starting iSCSI initiator service: iscsid failed! Setting up iSCSI targets: iscsiadm: No records found! . Mounting network filesystems:. invoke-rc.d: initscript open-iscsi, action start failed. dpkg: error processing open-iscsi (--configure): subprocess post-installation script returned error exit status 1 Errors were encountered while processing: open-iscsi E: Sub-process /usr/bin/dpkg returned an error code (1) which is rather useless. I have no intention of using this thing; I just want to rebuild libvirt, which states this package is a build-dependency. -- Paul Collins Wellington, New Zealand Dag vijandelijk luchtschip de huismeester is dood -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#529282: libvirt: questionable build-dep on open-iscsi
Package: libvirt Version: 0.6.3-2 This package checks for iscsiadm at build-time, but makes no attempt to ensure it is available at runtime. This seems backwards to me, and with open-iscsi being currently uninstallable on vanilla systems (#529280) right now it is challenging to rebuild libvirt oneself. Please consider removing open-iscsi from the build-dependencies, modifying the configure script to skip the check for iscsiadm, and adding Suggests: open-iscsi on the libvirt-bin package. -- Paul Collins Wellington, New Zealand Dag vijandelijk luchtschip de huismeester is dood -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#529280: [Pkg-libvirt-maintainers] Bug#529282: libvirt: questionable build-dep on open-iscsi
It checks for it to get the binary paths. I'm sorry, but that's really silly. Why doesn't it build-dep on kvm, for example, to make sure it still lives in /usr/bin/kvm? A package not being installable is a bad excuse to remove the build-dep. It's not so much an excuse to remove the build-dep as an explanation of why I noticed it in the first place. -- Paul Collins Wellington, New Zealand Dag vijandelijk luchtschip de huismeester is dood -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#529282: [Pkg-libvirt-maintainers] Bug#529282: libvirt: questionable build-dep on open-iscsi
It checks for it to get the binary paths. I'm sorry, but that's really silly. Why doesn't it build-dep on kvm, for example, to make sure it still lives in /usr/bin/kvm? A package not being installable is a bad excuse to remove the build-dep. It's not so much an excuse to remove the build-dep as an explanation of why I noticed it in the first place. -- Paul Collins Wellington, New Zealand Dag vijandelijk luchtschip de huismeester is dood -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#528514: krb5 - rpc.gssd from nfs-common segfaults after upgrade
Sam Hartman hartm...@debian.org writes: Paul, letting us know that it works against a lenny server but not a sid server is very interesting. That probably means that the etype negotiation support introduced in 1.7 is not quite doing the right thing. Things to check: [I'm not saying you should check these; this is mostly for Kerberos people including myself to look at. In particular I may not be giving enough detail here for someone not familiar with Kerberos and NFS internals. It will be a few days before I can go through this myself] * Confirm that both the lenny and sid kernels only support DES. * If sid kernel supports more than DES, it may be a config issue on the server side. I should point my sid box is not running a kernel from sid but rather my own builds. I've observed the problem with 2.6.29.2 and 2.6.30-rc5+. I gave the current sid 2.6.29 a shot but alas it doesn't support my goofy Apple keyboard, so I can't type in my LUKS passphrase, and I don't have any normal keyboards to hand. I think I've seen 2.6.30-pre builds from the Debian kernel team linked somewhere, so I'll track those down and try one in case the problem has something to do with how my kernel is configured. * Confirm that the client is setting the allowed gss enctypes * walk through that code path and see what breaks. -- Paul Collins Wellington, New Zealand Dag vijandelijk luchtschip de huismeester is dood -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#528514: krb5 - rpc.gssd from nfs-common segfaults after upgrade
Rebuilding my main NFSv4 client sadly coincided with this bug cropping up, so it's hard for me to be 100% certain I didn't mess something up. However, my NFSv4 client can mount an NFSv4 krb5 mount from a lenny server, but it cannot mount NFSv4 krb5 from the sid server, even with version 1.7dfsg~beta2-2 of the krb5 packages installed. Instead, the same error Mr. Litzenberger reports is logged: May 15 21:37:28 burly kernel: gss_kerberos_mech: unsupported algorithm 1 -- Paul Collins Wellington, New Zealand Dag vijandelijk luchtschip de huismeester is dood -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#481483: lastfmsubmitd: Doesn't know how to use a network proxy
lastfmsubmitd uses python's urllib, which will honour $http_proxy. I
have hacked my installation as follows:
$ cat /etc/default/lastfmsubmitd
http_proxy=http://proxy.example.com:3128/
$ diff -u /etc/init.d/lastfmsubmitd{~,}
--- /etc/init.d/lastfmsubmitd~ 2009-04-12 05:52:37.0 +1200
+++ /etc/init.d/lastfmsubmitd 2009-05-07 11:52:45.0 +1200
@@ -17,6 +17,13 @@
USER=lastfm
GROUP=lastfm
+if [ -r /etc/default/$NAME ]; then
+. /etc/default/$NAME
+if [ -n $http_proxy ]; then
+export http_proxy
+fi
+fi
+
if ! [ -x $DAEMON ]; then
exit 0
fi
and it's working nicely.
--
Paul Collins
Wellington, New Zealand
Dag vijandelijk luchtschip de huismeester is dood
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#526910: icicles: bad autoload in /etc/emacs/site-start.d/50icicles.el
Package: icicles Version: 22.0+20090409-2 The second autoload in /etc/emacs/site-start.d/50icicles.el should be for icicle-mode, not icicles-mode; the latter does not exist. -- Paul Collins Wellington, New Zealand Dag vijandelijk luchtschip de huismeester is dood -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#525588: bridged network stop working with kvm 84
Guido Günther a...@sigxcpu.org writes: On Mon, Apr 27, 2009 at 10:50:09AM +1200, Paul Collins wrote: I noticed this problem cropped up when I upgraded from Linux 2.6.29 to Linux 2.6.29.1, so bisecting the kernel may be worth a try. But you do use the kvm-84 modules or are you using the in kernel kvm modules? I use the kernel's kvm modules. -- Paul Collins Wellington, New Zealand Dag vijandelijk luchtschip de huismeester is dood -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#525588: bridged network stop working with kvm 84
I noticed this problem cropped up when I upgraded from Linux 2.6.29 to Linux 2.6.29.1, so bisecting the kernel may be worth a try. One one host system I use a bridge and on the other a private network with NAT, so it seems to be a more general problem. Switching my VMs to use emulated hardware NICs instead of virtio worked around the problem. -- Paul Collins Wellington, New Zealand Dag vijandelijk luchtschip de huismeester is dood -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#520677: linux-2.6: [x86] VMI does not correctly release PGD pages
Package: linux-2.6 Version: 2.6.26-13 A bug in Linux's VMI implementation that can cause hangs and reboots was fixed by commit 55a8ba4b7f76bebd7e8ce3f74c04b140627a1bad (which in turn requires commit eba0045ff87bab465d3c80c289f3bf709c1800f5) and has been incorporated into the 2.6.28 stable series. Please consider including it in Debian's 2.6.26. I have had a couple of Debian guests running 2.6.26-13 plus these two patches on one of our ESX clusters for a few days and the symptom I was observing (massively excessive hypervisor memory usage as reported in the Memory Overhead field) is no longer present. Note that commit eba0045ff87bab465d3c80c289f3bf709c1800f5 will cause an ABI bump as it alters pv_mmu_ops. -- Paul Collins Wellington, New Zealand Dag vijandelijk luchtschip de huismeester is dood -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#510392: [PATCH] ncmpc: status line clock display is not configurable
Package: ncmpc
Version: 0.12-1
Tags: patch
I already have a clock, and I don't need ncmpc showing me another one.
This patch adds command line options and a config file item to allow the
user to flexibly enable or disable the clock.
diff --git a/src/conf.c b/src/conf.c
index 5b3ebb3..b43078c 100644
--- a/src/conf.c
+++ b/src/conf.c
@@ -71,6 +71,7 @@
#define CONF_SCROLL_SEP scroll-sep
#define CONF_VISIBLE_BITRATE visible-bitrate
#define CONF_WELCOME_SCREEN_LIST welcome-screen-list
+#define CONF_DISPLAY_TIME display-time
typedef enum {
KEY_PARSER_UNKNOWN,
@@ -534,7 +535,9 @@ read_rc_file(char *filename)
else if (!strcasecmp(CONF_SCROLL_SEP, name)) {
g_free(options.scroll_sep);
options.scroll_sep = get_format(value);
- } else
+ } else if (!strcasecmp(CONF_DISPLAY_TIME, name))
+ options.display_time = str2bool(value);
+ else
match_found = 0;
if (!match_found)
diff --git a/src/options.c b/src/options.c
index b6a49e3..9d8ce93 100644
--- a/src/options.c
+++ b/src/options.c
@@ -77,6 +77,8 @@ static const arg_opt_t option_table[] = {
{ 'f', config, FILE, Read configuration from file },
{ 'k', key-file,FILE, Read configuration from file },
{ 'S', no-splash, NULL, Don't show the splash screen },
+ { 't', display-time, NULL, Display the time when idle },
+ { 'T', no-display-time, NULL, Do not display the time when idle },
#ifndef NDEBUG
{ 'K', dump-keys, NULL, Dump key bindings to stdout },
#endif
@@ -232,6 +234,12 @@ handle_option(int c, const char *arg)
case 'S': /* --key-file */
/* the splash screen was removed */
break;
+ case 't': /* --display-time */
+ options.display_time = 1;
+ break;
+ case 'T': /* --no-display-time */
+ options.display_time = 0;
+ break;
#ifndef NDEBUG
case 'K': /* --dump-keys */
read_configuration();
@@ -358,4 +366,5 @@ options_init(void)
#ifndef NCMPC_MINI
options.scroll_sep = g_strdup(DEFAULT_SCROLL_SEP);
#endif
+ options.display_time = 1;
}
diff --git a/src/options.h b/src/options.h
index 98ad315..cce36a5 100644
--- a/src/options.h
+++ b/src/options.h
@@ -51,6 +51,7 @@ typedef struct {
bool visible_bitrate;
bool welcome_screen_list;
#endif
+ int display_time;
} options_t;
extern options_t options;
diff --git a/src/screen.c b/src/screen.c
index 1a68b41..05d1e83 100644
--- a/src/screen.c
+++ b/src/screen.c
@@ -331,10 +331,12 @@ paint_status_window(mpdclient_t *c)
}
#ifndef NCMPC_MINI
} else {
- time_t timep;
+ if (options.display_time) {
+ time_t timep;
- time(timep);
- strftime(screen.buf, screen.buf_size, %X ,localtime(timep));
+ time(timep);
+ strftime(screen.buf, screen.buf_size, %X
,localtime(timep));
+ }
#endif
}
--
Paul Collins
Wellington, New Zealand
Dag vijandelijk luchtschip de huismeester is dood
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#505969: spurious warning due to newly empty config file
Package: fontconfig-config Version: 2.6.0-2 Since I upgraded to this version, my applications spew the following: Fontconfig error: /etc/fonts/conf.d/70-yes-bitmaps.conf, line 1: no element found Removing the file above (a symlink) gets rid of the warning. -- Paul Collins Wellington, New Zealand Dag vijandelijk luchtschip de huismeester is dood -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#505970: old answer to debconf question ignored
Package: fontconfig-config Version: 2.6.0-2 A while back I told fontconfig-config to enable bitmaps. On upgrading to this version, I have had to do it again. This is annoying. -- Paul Collins Wellington, New Zealand Dag vijandelijk luchtschip de huismeester is dood -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#505969: spurious warning due to newly empty config file
Something like the following seems to serve as an empty config file while also shutting fontconfig up: ?xml version=1.0? !DOCTYPE fontconfig SYSTEM fonts.dtd fontconfig/ -- Paul Collins Wellington, New Zealand Dag vijandelijk luchtschip de huismeester is dood -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#497919: libwine-ldap: links to nonexistent library, causing wine to fail
Package: libwine-ldap Version: 1.0.0-1 wine is failing for me as follows: err:module:load_builtin_dll failed to load .so lib for builtin LWLDAP32.dll: liblber.so.2: cannot open shared object file: No such file or directory There does not appear to be any library named liblber.so.2 in sid currently. There is one in etch, though, although it seems like liblber-2.4.so.2 probably replaces it, which IS linked by this library. $ ldd /usr/lib/wine/wldap32.dll.so linux-gate.so.1 = (0xf7f9d000) libldap_r-2.4.so.2 = /usr/lib32/libldap_r-2.4.so.2 (0xf7ef5000) liblber.so.2 = not found libwine.so.1 = /usr/lib/libwine.so.1 (0xf7dbf000) libm.so.6 = /lib32/libm.so.6 (0xf7d9b000) libc.so.6 = /lib32/libc.so.6 (0xf7c48000) liblber-2.4.so.2 = /usr/lib32/liblber-2.4.so.2 (0xf7c3b000) libresolv.so.2 = /lib32/libresolv.so.2 (0xf7c28000) libsasl2.so.2 = /usr/lib32/libsasl2.so.2 (0xf7c11000) libgnutls.so.26 = /usr/lib32/libgnutls.so.26 (0xf7b74000) libpthread.so.0 = /lib32/libpthread.so.0 (0xf7b5d000) libdl.so.2 = /lib32/libdl.so.2 (0xf7b58000) /lib/ld-linux.so.2 (0xf7f9e000) libtasn1.so.3 = /usr/lib32/libtasn1.so.3 (0xf7b48000) libgpg-error.so.0 = /usr/lib32/libgpg-error.so.0 (0xf7b44000) libz.so.1 = /usr/lib32/libz.so.1 (0xf7b2f000) libgcrypt.so.11 = /usr/lib32/libgcrypt.so.11 (0xf7ac7000) -- Paul Collins Wellington, New Zealand Dag vijandelijk luchtschip de huismeester is dood -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#495647: iceweasel: home page defaults to Gran Paradiso home page
Package: iceweasel Version: 3.0.1-1 Severity: minor http://www.mozilla.org/projects/granparadiso/ is the default home page for newly created profiles. This appears to be because 'browser.startup.homepage' is set to 'resource:/browserconfig.properties', which I guess refers to one of the following files /usr/lib/iceweasel/browserconfig.properties /usr/share/iceweasel/browserconfig.properties both of which contain browser.startup.homepage=http://www.mozilla.org/projects/granparadiso/ a page that, in an Iceweasel 3.0 context, is either strange, annoying or terrifying, depending on one's disposition. -- Paul Collins Wellington, New Zealand Dag vijandelijk luchtschip de huismeester is dood -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#459494: nvclock: Console version depends on libqt3-mt.
Additionally, there's the following: Tag: hardware::video, uitoolkit::gtk ^^ -- Paul Collins Wellington, New Zealand Dag vijandelijk luchtschip de huismeester is dood -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#493217: libnfsidmap-0.21 is available
Kevin Coffman [EMAIL PROTECTED] writes: Getting back to this. I'm curious if there is a specific reason why the *.so symlink was not there? Adding the .0 shouldn't be necessary. But there may be a reason for not including the .so symlink that I am not aware of. My default install in /usr/local/lib shows: lrwxrwxrwx 1 root root29 2008-07-30 16:59 /usr/local/lib/libnfsidmap_nsswitch.so - libnfsidmap_nsswitch.so.0.0.0 lrwxrwxrwx 1 root root29 2008-07-30 16:59 /usr/local/lib/libnfsidmap_nsswitch.so.0 - libnfsidmap_nsswitch.so.0.0.0 -rwxr-xr-x 1 root root 17141 2008-07-30 16:59 /usr/local/lib/libnfsidmap_nsswitch.so.0.0.0 This looks like a reasonable result from make install in a regular autotooled source distribution. The libfoo.so link is used by the linker to find the library based on the -lfoo switch. The object resulting from the link will refer to libfoo.so.X and then that will be a symlink to libfoo.so.X.Y.Z. So far, so good. With typical libraries on Debian, libfoo.so will be provided, along with the required headers, by libfoo-dev (or perhaps libfooX-dev, depending on how it has been packaged). libfoo.so.X and libfoo.so.X.Y.Z will be in the libfooX package (or perhaps libfoo, if X has never changed), and applications linked to libfoo will depend on that package, as will libfoo-dev. Of course, the shared objects we're talking about are not regular libraries and so should be handled specially. This could mean altering the dlopen calls as per my suggestion, or overriding the autotools stuff and installing them as libnfsidmap_foo.so somewhere or other. -- Paul Collins Wellington, New Zealand Dag vijandelijk luchtschip de huismeester is dood -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#492970: (was: nfs-utils-1.1.3 released)
Chuck Lever [EMAIL PROTECTED] writes: On Aug 3, 2008, at 11:10 AM, J. Bruce Fields wrote: On Mon, Aug 04, 2008 at 12:37:19AM +1200, Paul Collins wrote: J. Bruce Fields [EMAIL PROTECTED] writes: On Fri, Aug 01, 2008 at 11:15:33PM +1000, Aníbal Monsalve Salazar wrote: On Mon, Jul 28, 2008 at 03:13:19AM -0400, Steve Dickson wrote: I just cut the 1.1.3 nfs-utils release. Unfortunately I'm having issues accessing my kernel.org account so for the moment the tar ball is only available on SourceForge: http://sourceforge.net/projects/nfs [...] 1.1.3 clients don't work with a 1.0.10 server anymore. Very weird--it might make sense if upgrading nfs-utils broke the mount itself, but here it seems the mount is succeeding and subsequent file access (which I'd expect to only involve the in-kernel client code) is failing. Maybe there's some difference in the mount options? What does /proc/self/mounts say? I assume these are all v2 or v3 mounts? I discovered today that I was no longer able to write to the v3 mount on my 1.1.2 server. I checked /proc/mounts and noticed sec=null on the mount. Either adding sec=sys to the client's mount options or downgrading to nfs-common 1.1.2 on the client fixes the problem. That would do it! So it sounds like there's a bug that causes mount.nfs to get the default mount options wrong? I'm not sure I'm following this. I can't think of a user-space mount.nfs change in 1.1.3 that would affect the sec= option. Paul, which kernel are you running on your clients? Either 2.6.26 or 2.6.27-rc1+. I'll double-check. Whichever one it was, the problem was present with 1.1.3 installed, and not present with 1.1.2 installed. -- Paul Collins Wellington, New Zealand Dag vijandelijk luchtschip de huismeester is dood -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#492970: (was: nfs-utils-1.1.3 released)
J. Bruce Fields [EMAIL PROTECTED] writes: On Fri, Aug 01, 2008 at 11:15:33PM +1000, Aníbal Monsalve Salazar wrote: On Mon, Jul 28, 2008 at 03:13:19AM -0400, Steve Dickson wrote: I just cut the 1.1.3 nfs-utils release. Unfortunately I'm having issues accessing my kernel.org account so for the moment the tar ball is only available on SourceForge: http://sourceforge.net/projects/nfs [...] 1.1.3 clients don't work with a 1.0.10 server anymore. Very weird--it might make sense if upgrading nfs-utils broke the mount itself, but here it seems the mount is succeeding and subsequent file access (which I'd expect to only involve the in-kernel client code) is failing. Maybe there's some difference in the mount options? What does /proc/self/mounts say? I assume these are all v2 or v3 mounts? I discovered today that I was no longer able to write to the v3 mount on my 1.1.2 server. I checked /proc/mounts and noticed sec=null on the mount. Either adding sec=sys to the client's mount options or downgrading to nfs-common 1.1.2 on the client fixes the problem. -- Paul Collins Wellington, New Zealand Dag vijandelijk luchtschip de huismeester is dood -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#493217: libnfsidmap2: rpc.idmapd broken
Package: libnfsidmap2 Version: 0.21-1 Severity: grave Upgrading from 0.20-1 to 0.21-1 breaks rpc.idmapd: $ sudo rpc.idmapd -f -v rpc.idmapd: libnfsidmap: using domain: wgtn.ondioline.org rpc.idmapd: libnfsidmap: processing 'Method' list rpc.idmapd: libnfsidmap: Unable to load plugin: libnfsidmap_nsswitch.so: cannot open shared object file: No such file or directory rpc.idmapd: libnfsidmap: requested translation method, 'nsswitch', is not available rpc.idmapd: Unable to create name to user id mappings. $ dpkg -L libnfsidmap2 | grep nsswitch /usr/lib/libnfsidmap_nsswitch.so.0.0.0 /usr/lib/libnfsidmap_nsswitch.so.0 Since these newly separated plugins are not general-purpose shared libraries, perhaps they should be shipped as /usr/lib/libnfsidmap2/nsswitch.so and so forth, or something along those lines. -- Paul Collins Wellington, New Zealand Dag vijandelijk luchtschip de huismeester is dood -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#493217: libnfsidmap-0.21 is available
Kevin Coffman [EMAIL PROTECTED] writes:
Did you run ldconfig? I was trying to find the right thing to force
that, but from what I saw, when you install in /usr/local/lib, libtool
knows better. If anyone has the answer on that, let me know.
The convention on Debian seems to be to install plugins as
/usr/lib/${packagename}/${plugin}.so and dlopen them with an absolute path.
--
Paul Collins
Wellington, New Zealand
Dag vijandelijk luchtschip de huismeester is dood
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#493217: libnfsidmap-0.21 is available
Kevin Coffman [EMAIL PROTECTED] writes:
On Fri, Aug 1, 2008 at 9:41 AM, Paul Collins [EMAIL PROTECTED] wrote:
Kevin Coffman [EMAIL PROTECTED] writes:
Did you run ldconfig? I was trying to find the right thing to force
that, but from what I saw, when you install in /usr/local/lib, libtool
knows better. If anyone has the answer on that, let me know.
The convention on Debian seems to be to install plugins as
/usr/lib/${packagename}/${plugin}.so and dlopen them with an absolute path.
OK, I'll update the code and put out a -0.22 ASAP, but it might not be
for a few days.
Having had some sleep, I realized a quicker fix is to just change the
dlopen calls to do e.g. dlopen(libfoo.so.0, ...). This would avoid
any tussling with libtool and the autogar, which is always a plus.
I've tried that out here and it works nicely. Patch below.
BTW, this is the kind of comments I was looking for since putting the
beta out in April, but received none. I guess I was asking in the
wrong places. :-/
You may have to just be bold and trick people into testing your betas by
calling them releases. I'm happy to complain about anything that ends
up in Debian unstable, but I tend not to grab stuff from upstream much.
--- libnfsidmap-0.21/libnfsidmap.c~ 2008-08-02 10:52:00.289845221 +1200
+++ libnfsidmap-0.21/libnfsidmap.c 2008-08-02 10:47:50.647889312 +1200
@@ -101,7 +101,7 @@
char plgname[128];
int ret = 0;
- snprintf(plgname, sizeof(plgname), %s%s.so, PLUGIN_PREFIX, method);
+ snprintf(plgname, sizeof(plgname), %s%s.so.0, PLUGIN_PREFIX, method);
dl = dlopen(plgname, RTLD_NOW | RTLD_LOCAL);
if (dl == NULL) {
--
Paul Collins
Wellington, New Zealand
Dag vijandelijk luchtschip de huismeester is dood
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#465498: virt-manager: Need to ask twice to open dialogs or windows
I just encountered a problem using virt-manager with evilwm that I think may be a variant of this problem. When I tried to create a new VM, the dialog window appeared at the top left of the screen without a border and was visible on all workspaces. Checking it out with xwininfo and xprop, I noticed the following: $ xprop WM_STATE # click on window WM_STATE(WM_STATE): window state: Withdrawn icon window: 0x0 When I cancel the dialog and invoke the New command again, the window appears with a border and WM_STATE is correct: $ xprop WM_STATE # click on window WM_STATE(WM_STATE): window state: Normal icon window: 0x0 -- Paul Collins Wellington, New Zealand Dag vijandelijk luchtschip de huismeester is dood -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#489372: tritium: does not honour $DISPLAY or -display
Package: tritium Version: 0.3.8-1 $ DISPLAY=:1 tritium /usr/bin/tritium: Screen 0 already managed by some other window manager /usr/bin/tritium: Another window manager already running? $ tritium -display :1 Traceback (most recent call last): File /usr/bin/tritium, line 172, in module usage() NameError: name 'usage' is not defined $ _ -- Paul Collins Wellington, New Zealand Dag vijandelijk luchtschip de huismeester is dood -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#487830: mplayer: crashes with MPlayer interrupted by signal 11 in module: demux_open on FLV files
Package: mplayer Version: 1.0~rc2-14 View FLV files with this version of mplayer results in MPlayer interrupted by signal 11 in module: demux_open Version 1.0~rc2-12 works fine. -- Paul Collins Wellington, New Zealand Dag vijandelijk luchtschip de huismeester is dood -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#484205: filters: please include hovercar
Package: filters Version: 2.44 Please consider including the hovercar text filter, available at http://www.finnie.org/software/hovercar/ -- Paul Collins Wellington, New Zealand Dag vijandelijk luchtschip de huismeester is dood -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#481989: kvm: new upstream version available
Package: kvm Version: 66+dfsg-1 Version 69 of kvm has been released upstream. Please consider updating the version in Debian. Thanks, -- Paul Collins Wellington, New Zealand Dag vijandelijk luchtschip de huismeester is dood -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#480310: [ixp4xx] armel NSLU2 fails to boot with 2.6.25
Kevin Price [EMAIL PROTECTED] writes: Martin Michlmayr schrieb: This has been fixed in version 2.6.25-3 of linux-image-2.6.25-2-ixp4xx which is now in unstable. Would be great if you (Paul, Kevin) could confirm it works. Yes, confirmed. It works nicely for me. Works great here too. Thanks, folks! -- Paul Collins Wellington, New Zealand Dag vijandelijk luchtschip de huismeester is dood -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#480310: [ixp4xx] armel NSLU2 fails to boot with 2.6.25
Martin Michlmayr [EMAIL PROTECTED] writes: * Paul Collins [EMAIL PROTECTED] [2008-05-12 09:15]: Nothing, I'm afraid; all 2.6.24. There was no disk activity when I restarted after installing 2.6.25. Judging by /usr/share/doc/nslu2-utils/README.Debian it didn't even get as far as starting the initramfs. Do you know how to go back to 2.6.24 for now? Yep, no worries there. I backed up the flash beforehand and upslugged my way home. -- Paul Collins Wellington, New Zealand Dag vijandelijk luchtschip de huismeester is dood -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#480310: [ixp4xx] armel NSLU2 fails to boot with 2.6.25
Martin Michlmayr [EMAIL PROTECTED] writes: Paul, can you check in /var/log on your hard drive to see if there's anything useful? Nothing, I'm afraid; all 2.6.24. There was no disk activity when I restarted after installing 2.6.25. Judging by /usr/share/doc/nslu2-utils/README.Debian it didn't even get as far as starting the initramfs. -- Paul Collins Wellington, New Zealand Dag vijandelijk luchtschip de huismeester is dood -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#469435: lastmp: only handles a single mpd
I've started using my second mpd again, so here are the changes I've
made to lastmp 0.37-2 to accommodate it.
The main change is adding the --config option to lastmp. The value passed
determines which section to consult in /etc/lastmp.conf, defaulting to mpd.
The config value is appended to the name passed to lastfm.client.Daemon
so that each lastmp instance gets a unique pid file. The init script is
adjusted to reflect this.
With these changes, adding a new instance consists of adding a new
section to /etc/lastmp.conf, copying /etc/init.d/lastmp and adjusting
$LASTMP_CONFIG and finally creating startup links and whatnot.
diff --git a/debian/lastmp.init.d b/debian/lastmp.init.d
index ac01562..61c995d 100644
--- a/debian/lastmp.init.d
+++ b/debian/lastmp.init.d
@@ -17,6 +17,11 @@ RUNDIR=/var/run/lastfm
USER=lastfm
GROUP=lastfm
+LASTMP_CONFIG=mpd
+DAEMON_OPTS=--config $LASTMP_CONFIG
+
+PIDFILE=$RUNDIR/${NAME}_${LASTMP_CONFIG}.pid
+
if ! [ -x $DAEMON ]; then
exit 0
fi
@@ -25,23 +30,23 @@ case $1 in
start)
echo -n Starting $DESC:
start-stop-daemon --quiet --start -c $USER:$GROUP \
---pidfile $RUNDIR/$NAME.pid --exec $DAEMON -- $DAEMON_OPTS
-echo $NAME.
+--pidfile $PIDFILE --exec $DAEMON -- $DAEMON_OPTS
+echo $NAME ($LASTMP_CONFIG).
;;
stop)
echo -n Stopping $DESC:
start-stop-daemon --quiet --oknodo --stop -u $USER \
---pidfile $RUNDIR/$NAME.pid
-echo $NAME.
+--pidfile $PIDFILE
+echo $NAME ($LASTMP_CONFIG).
;;
restart|force-reload)
echo -n Restarting $DESC:
start-stop-daemon --quiet --oknodo --stop -u $USER \
---pidfile $RUNDIR/$NAME.pid
+--pidfile $PIDFILE
sleep 1
start-stop-daemon --quiet --start -c $USER:$GROUP \
---pidfile $RUNDIR/$NAME.pid --exec $DAEMON -- $DAEMON_OPTS
-echo $NAME.
+--pidfile $PIDFILE --exec $DAEMON -- $DAEMON_OPTS
+echo $NAME ($LASTMP_CONFIG).
;;
*)
N=/etc/init.d/$NAME
diff --git a/lastmp b/lastmp
index 7223fca..a714716 100755
--- a/lastmp
+++ b/lastmp
@@ -13,7 +13,7 @@ import lastfm.config
import lastfm.marshaller
DAEMON_NAME = 'lastmp'
-USAGE = 'usage: %s [--debug] [--no-daemon] [--help]' % DAEMON_NAME
+USAGE = 'usage: %s [--config CONFIG] [--debug] [--no-daemon] [--help]' %
DAEMON_NAME
# If the system load is high, we may not wake again until slightly
# longer than we slept. This should really be like 0.1, but
@@ -173,11 +173,11 @@ class MPDMonitor:
self.cli.log.error(Can't write sub: %s % e)
class LmpConfig(lastfm.config.Config):
-def __init__(self):
+def __init__(self, config):
lastfm.config.Config.__init__(self, search=DAEMON_NAME)
-self.host = self.cp.get('mpd', 'host', None)
-self.port = int(self.cp.get('mpd', 'port', 6600))
-self.password = self.cp.get('mpd', 'password', None)
+self.host = self.cp.get(config, 'host', None)
+self.port = int(self.cp.get(config, 'port', 6600))
+self.password = self.cp.get(config, 'password', None)
if not self.host:
raise NoHostError
@@ -196,8 +196,8 @@ def daemon(cli):
mo.observe()
if __name__ == '__main__':
-shortopts = 'dnh'
-longopts = ['debug', 'no-daemon', 'help']
+shortopts = 'c:dnh'
+longopts = ['config=', 'debug', 'no-daemon', 'help']
try:
opts, args = getopt.getopt(sys.argv[1:], shortopts, longopts)
@@ -206,12 +206,15 @@ if __name__ == '__main__':
print sys.stderr, USAGE
sys.exit(1)
+config = 'mpd'
debug = False
fork = True
stderr = False
for opt, arg in opts:
-if opt in ('--debug', '-d'):
+if opt in ('--config', '-c'):
+config = arg
+elif opt in ('--debug', '-d'):
debug = True
elif opt in ('--no-daemon', '-n'):
fork = False
@@ -221,14 +224,14 @@ if __name__ == '__main__':
sys.exit(0)
try:
-conf = LmpConfig()
+conf = LmpConfig(config)
except NoHostError:
print sys.stderr, '%s: no MPD host specified' % DAEMON_NAME
sys.exit(1)
if conf.debug:
debug = True
-cli = lastfm.client.Daemon(DAEMON_NAME, conf)
+cli = lastfm.client.Daemon(DAEMON_NAME + _ + config, conf)
cli.daemonize(fork)
cli.open_log(debug, stderr)
--
Paul Collins
Wellington, New Zealand
Dag vijandelijk luchtschip de huismeester is dood
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#480310: [ixp4xx] armel NSLU2 fails to boot with 2.6.25
Package: linux-image-2.6.25-1-ixp4xx Version: 2.6.25-1 After the usual initial lightshow, the NSLU2 sits there with only the Ethernet LED illuminated. I have initramfs-tools 0.92a and the initrd is 1.4MB, so I think that should be mustard. I'm running armel. I have no serial console, so I guess I can't be much help with debugging. -- Paul Collins Wellington, New Zealand Dag vijandelijk luchtschip de huismeester is dood -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#471062: ixp4xx: stalls and I/O errors when reading and writing via NFS
Hi Gordon, Gordon Farquharson [EMAIL PROTECTED] writes: I added a patch to the Debian kernel subversion repository for sid. Snapshots of the kernel are not built for arm, so I uploaded the binary here [1]. Martin Michlmayr tested this version and reported that he could not reproduce the problem. If possible, it would be great if you could test the new kernel. The following link wil show you the patch that was applied. I'm happy to test. However, the image you linked below is for arm, and my system is armel. [1] http://fradharc.com/files/linux-image-2.6.24-1-ixp4xx_2.6.24-5_arm.deb md5sum: c16ad247db142be3e5b6c1e45a81 linux-image-2.6.24-1-ixp4xx_2.6.24-5_arm.deb -- Paul Collins Wellington, New Zealand Dag vijandelijk luchtschip de huismeester is dood -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#471292: please build-depend on libncurses5-dev so that -curses will be enabled
Package: kvm Version: 63+dfsg-1 Please add a build dependency on libncurses5-dev so that support for -curses will be enabled and built. I have rebuilt the package locally with libncurses5-dev installed and no further changes were required; 'kvm -curses' works great with a FreeBSD 7 VM I have here. Thanks! -- Paul Collins Wellington, New Zealand Dag vijandelijk luchtschip de huismeester is dood -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#471062: ixp4xx: stalls and I/O errors when reading and writing via NFS
Package: linux-image-2.6.24-1-ixp4xx Version: 2.6.24-4 I recently upgraded my NSLU2 from etch/arm to lenny/armel. I had no problems throwing any amount of NFS traffic at it when I was on arm (kernel linux-image-2.6.18-6-ixp4xx version 2.6.18.dfsg.1-18etch1), but now that I'm on armel I get a lot of messages from nfsd in dmesg. When reading: nfsd: recvfrom returned errno 14 When writing: nfsd: non-standard errno: -14 The read problem manifests as mplayer stalling every minute or so when playing a movie from the NFS mount. The write problem manifests as cp or mv reporting an I/O error for one or more files when I copy 40 or 50MB worth to the NFS mount. Bug #404447 sounded similar and with the tcp_wmem sysctl setting suggested therein applied mplayer behaves itself. However, the recvfrom messages are still logged and writes still throw an I/O error now and then. The network setup is the NSLU2 and the client connected by wired Ethernet to a Linksys WRT54GL. -- Paul Collins Wellington, New Zealand Dag vijandelijk luchtschip de huismeester is dood -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#469435: lastmp: only handles a single mpd
Package: lastmp Version: 0.37-2 Severity: wishlist I have a bunch of mpds installed around the place (two on this machine alone), and it would be nice if a single lastmp could talk to all of them, whether by direct support or by starting one per mpd. last.fm's spam protection would probably trigger if I played music with more than one mpd at a time, but that would be my problem. -- Paul Collins Wellington, New Zealand Dag vijandelijk luchtschip de huismeester is dood -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#469435: lastmp: only handles a single mpd
Decklin Foster [EMAIL PROTECTED] writes: Paul Collins writes: I have a bunch of mpds installed around the place (two on this machine alone), and it would be nice if a single lastmp could talk to all of them, whether by direct support or by starting one per mpd. It should be possible for any number of lastmp processes (this would have to be one per MPD) write to the same lastfmsubmitd spool. Would a --config option make this easier? Not sure what your setup looks like. Yes, I think a --config option would be enough for my situation. -- Paul Collins Wellington, New Zealand Dag vijandelijk luchtschip de huismeester is dood -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#462182: init script: start-stop-daemon --stop retry interval is much too long
Package: dbus Version: 1.1.2-1 Recently I noticed on three separate machines running current unstable that dbus has started taking an age to shut down. I had a look and it seems that although dbus-daemon exits immediately, start-stop-daemon is waiting a full minute before checking, due to the --retry argument passed to it. Please consider reducing this timeout. I've run 'invoke-rc.d dbus restart' in a loop here with --retry altered to 2 and it seems solid. (The scripts in my /etc/init.d seem to use a value of 3 or 5, so if this is partly due to a recent change in start-stop-daemon, that may be why it is only apparent with dbus.) -- Paul Collins Wellington, New Zealand Dag vijandelijk luchtschip de huismeester is dood -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#462182: [Pkg-utopia-maintainers] Bug#462182: init script: start-stop-daemon --stop retry interval is much too long
Michael Biebl [EMAIL PROTECTED] writes: That's a bug in dpkg [1], which has already been fixed in 1.14.16.3. So with this fixed dpkg version this issue becomes moot. Whoops. I had a look through the dpkg bugs, but I didn't spot this. Btw. did you also test under high load and lot of I/O? If we change it, then most likely to 5 secs. I think the system was probably lightly loaded at the time. Thank you for responding so quickly. -- Paul Collins Wellington, New Zealand Dag vijandelijk luchtschip de huismeester is dood -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#461828: FTBFS: missing build-dependency
Package: rrootage Version: 0.23a-6 Please add libboost-dev to this package's build-dependencies. http://buildd.debian.org/fetch.cgi?pkg=rrootagever=0.23a-6arch=amd64stamp=1190915624file=log Regards, -- Paul Collins Wellington, New Zealand Dag vijandelijk luchtschip de huismeester is dood -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#461019: pointer hidden during typing is not quite (hidden)
Package: xterm
Version: 231-1
Tags: patch
The cursor xterm uses for the hidden mouse pointer has a non-empty mask,
so when I start typing, the I-bar is replaced with a black dot, which I
find quite distracting. With this patch, the pointer's cursor has a
blank image and mask and so when it is used nothing is visible.
--- ../xterm-231/misc.c 2008-01-01 10:11:20.0 +1300
+++ misc.c 2008-01-16 21:35:37.0 +1300
@@ -418,7 +418,7 @@
static XColor dummy;
if (fn != 0) {
- c = XCreateGlyphCursor(dpy, fn, fn, 'X', '.', dummy, dummy);
+ c = XCreateGlyphCursor(dpy, fn, fn, ' ', ' ', dummy, dummy);
} else {
c = 0;
}
--
Paul Collins
Wellington, New Zealand
Dag vijandelijk luchtschip de huismeester is dood
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#454692: upgrade fails: elscreen-wl.el:27:1:Error: Cannot open load file: wl
Package: elscreen Version: 1.4.5-2 It looks like elscreen-wl.el is expecting wanderlust to be installed. However, I do not have it installed. Transcript: Setting up elscreen (1.4.5-2) ... install/apel: Byte-compiling for emacs-snapshot ... skipped. (already compiled) install/apel: Byte-compiling for emacs22 ... skipped. (already compiled) install/elscreen: Handling install for emacsen flavor emacs-snapshot Loading 00debian-vars... Loading /etc/emacs/site-start.d/20apel.el (source)... Loading /etc/emacs/site-start.d/50autoconf.el (source)... Loading /etc/emacs/site-start.d/50cedet-common.el (source)... Loading /etc/emacs/site-start.d/50dictionaries-common.el (source)... Skipping dictionaries-common setup for emacs-snapshot Loading /etc/emacs/site-start.d/50eieio.el (source)... Loading /etc/emacs/site-start.d/50elscreen.el (source)... Loading /etc/emacs/site-start.d/50emacs-goodies-el.el (source)... Loading /etc/emacs/site-start.d/50erlang-mode.el (source)... Loading /etc/emacs/site-start.d/50psvn.el (source)... Loading /etc/emacs/site-start.d/50slime.el (source)... Loading /usr/share/emacs-snapshot/site-lisp/slime/slime-autoloads... Source file `/usr/share/emacs-snapshot/site-lisp/elscreen/elscreen.el' newer than byte-compiled file Wrote /usr/share/emacs-snapshot/site-lisp/elscreen/elscreen-color-theme.elc Wrote /usr/share/emacs-snapshot/site-lisp/elscreen/elscreen-dired.elc In toplevel form: elscreen-dnd.el:36:1:Warning: !! The file uses old-style backquotes !! This functionality has been obsolete for more than 10 years already and will be removed soon. See (elisp)Backquote in the manual. elscreen-dnd.el:54:1:Warning: !! The file uses old-style backquotes !! This functionality has been obsolete for more than 10 years already and will be removed soon. See (elisp)Backquote in the manual. Wrote /usr/share/emacs-snapshot/site-lisp/elscreen/elscreen-dnd.elc Wrote /usr/share/emacs-snapshot/site-lisp/elscreen/elscreen-gf.elc Wrote /usr/share/emacs-snapshot/site-lisp/elscreen/elscreen-goby.elc Wrote /usr/share/emacs-snapshot/site-lisp/elscreen/elscreen-howm.elc Wrote /usr/share/emacs-snapshot/site-lisp/elscreen/elscreen-server.elc Wrote /usr/share/emacs-snapshot/site-lisp/elscreen/elscreen-speedbar.elc Wrote /usr/share/emacs-snapshot/site-lisp/elscreen/elscreen-w3m.elc In toplevel form: elscreen-wl.el:27:1:Error: Cannot open load file: wl In toplevel form: elscreen.el:351:1:Warning: !! The file uses old-style backquotes !! This functionality has been obsolete for more than 10 years already and will be removed soon. See (elisp)Backquote in the manual. elscreen.el:515:1:Warning: !! The file uses old-style backquotes !! This functionality has been obsolete for more than 10 years already and will be removed soon. See (elisp)Backquote in the manual. elscreen.el:558:1:Warning: !! The file uses old-style backquotes !! This functionality has been obsolete for more than 10 years already and will be removed soon. See (elisp)Backquote in the manual. elscreen.el:623:1:Warning: !! The file uses old-style backquotes !! This functionality has been obsolete for more than 10 years already and will be removed soon. See (elisp)Backquote in the manual. Wrote /usr/share/emacs-snapshot/site-lisp/elscreen/elscreen.elc emacs-package-install: /usr/lib/emacsen-common/packages/install/elscreen emacs-snapshot emacs-snapshot emacs22 failed at /usr/lib/emacsen-common/emacs-package-install line 30, TSORT line 2. dpkg: error processing elscreen (--configure): subprocess post-installation script returned error exit status 1 Errors were encountered while processing: elscreen -- Paul Collins Wellington, New Zealand Dag vijandelijk luchtschip de huismeester is dood -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#452078: upgrade fails, attempts to overwrite /usr/share/perl5/Error.pm
Package: git-core Version: 1:1.5.3.6-1 Upgrading to this version fails as follows. Preparing to replace git-core 1:1.5.3.5-1 (using .../git-core_1%3a1.5.3.6-1_amd64.deb) ... Unpacking replacement git-core ... dpkg: error processing /var/cache/apt/archives/git-core_1%3a1.5.3.6-1_amd64.deb (--unpack): trying to overwrite `/usr/share/perl5/Error.pm', which is also in package liberror-perl Errors were encountered while processing: /var/cache/apt/archives/git-core_1%3a1.5.3.6-1_amd64.deb E: Sub-process /usr/bin/dpkg returned an error code (1) ii git-core 1:1.5.3.5-1fast, scalable, distributed revision control ii liberror-perl 0.15-8 Perl module for error/exception handling in -- Paul Collins Wellington, New Zealand Dag vijandelijk luchtschip de huismeester is dood -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#449307: cpufrequtils: init script does not configure all cores
Package: cpufrequtils Version: 002-5 On the Core 2 Duo machines I have installed cpufrequtils on, the init script says the following: CPUFreq Utilities: Setting ondemand CPUFreq governor...CPU0...CPU0...done. As a result, one core uses ondemand and the other uses performance, which is sub-optimal. [burly(~)] cpufreq-info cpufrequtils 002: cpufreq-info (C) Dominik Brodowski 2004-2006 Report errors and bugs to [EMAIL PROTECTED], please. analyzing CPU 0: driver: acpi-cpufreq CPUs which need to switch frequency at the same time: 0 hardware limits: 1000 MHz - 2.00 GHz available frequency steps: 2.00 GHz, 1.83 GHz, 1.67 GHz, 1.50 GHz, 1.33 GHz, 1000 MHz available cpufreq governors: ondemand, performance current policy: frequency should be within 1000 MHz and 2.00 GHz. The governor ondemand may decide which speed to use within this range. current CPU frequency is 1000 MHz. analyzing CPU 1: driver: acpi-cpufreq CPUs which need to switch frequency at the same time: 1 hardware limits: 1000 MHz - 2.00 GHz available frequency steps: 2.00 GHz, 1.83 GHz, 1.67 GHz, 1.50 GHz, 1.33 GHz, 1000 MHz available cpufreq governors: ondemand, performance current policy: frequency should be within 1000 MHz and 2.00 GHz. The governor performance may decide which speed to use within this range. current CPU frequency is 2.00 GHz. This is because the init script is using the 'processor' field in /proc/cpuinfo to locate the CPUs, which seems to enumerate packages or dies rather than cores. [burly(~)] grep '^processor' /proc/cpuinfo processor : 0 processor : 0 [burly(~)] grep '^physical id' /proc/cpuinfo physical id : 0 physical id : 0 Possible solutions: 1. Use the 'core id' field in /proc/cpuinfo. I don't know how backward-compatible to previous kernel versions this is. [burly(~)] grep '^core id' /proc/cpuinfo core id : 0 core id : 1 2. Enumerate the sysfs attributes directly. [burly(~)] grep ^ /sys/devices/system/cpu/cpu*/cpufreq/scaling_governor /sys/devices/system/cpu/cpu0/cpufreq/scaling_governor:ondemand /sys/devices/system/cpu/cpu1/cpufreq/scaling_governor:ondemand 3. Ask cpufreq-info. [burly(~)] cpufreq-info -o | grep ^CPU CPU 0 100 kHz ( 50 %) -200 kHz (100 %) - ondemand CPU 1 100 kHz ( 50 %) -200 kHz (100 %) - ondemand Regards, -- Paul Collins Wellington, New Zealand Dag vijandelijk luchtschip de huismeester is dood -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#436053: sftp at port 115 is not the secure file transfer protocol
Package: fail2ban Version: 0.8.0-4 The ssh and ssh-ddos sections in /etc/fail2ban/jail.conf have port = ssh,sftp. However, secure ftp runs over port 22 like regular ssh. (Instead of starting an interactive session after authentication, the sftp client requests the sftp module.) Port 115 is the Simple File Transfer Protocol[1], which is marked by the IETF as historic[2]. Please consider adjusting the default configuration to only specify port = ssh for these sections. [1] http://www.ietf.org/rfc/rfc913.txt [2] ftp://ftp.isi.edu/in-notes/rfc-index.txt -- Paul Collins Wellington, New Zealand Dag vijandelijk luchtschip de huismeester is dood -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#436053: sftp at port 115 is not the secure file transfer protocol
Yaroslav Halchenko [EMAIL PROTECTED] writes: Thank you for the information, but what harm really it does banning 'historic' sftp as well... I don't see any bug in this. I feel it is always best not to surprise the user. I was certainly surprised when I found fail2ban banning services unrelated to the services I had told it to ban. It is by no means a serious bug, so please feel free to tag it wontfix. Regards, -- Paul Collins Wellington, New Zealand Dag vijandelijk luchtschip de huismeester is dood -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#434585: Upgrade fails: file conflict with bsdgames (/usr/share/man/man6/worm.6.gz)
Package: xscreensaver Version: 5.03-1 I got the following error when I attempted to upgrade to 5.03-1: Preparing to replace xscreensaver 4.24-5 (using .../xscreensaver_5.03-1_powerpc.deb) ... Unpacking replacement xscreensaver ... dpkg: error processing /var/cache/apt/archives/xscreensaver_5.03-1_powerpc.deb (--unpack): trying to overwrite `/usr/share/man/man6/worm.6.gz', which is also in package bsdgames dpkg-deb: subprocess paste killed by signal (Broken pipe) Errors were encountered while processing: /var/cache/apt/archives/xscreensaver_5.03-1_powerpc.deb E: Sub-process /usr/bin/dpkg returned an error code (1) -- Paul Collins Wellington, New Zealand Dag vijandelijk luchtschip de huismeester is dood -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#431179: ^D accelerator for Select - Delete interacts badly with Emacs key theme
Package: postr Version: 0.7-1 I use the Emacs key theme with GTK+/GNOME apps, which binds ^D to delete-forward. When using postr I frequently find myself accidentally unintentionally pictures from the upload queue. Please consider using a different accelerator for this function. -- Paul Collins Wellington, New Zealand Dag vijandelijk luchtschip de huismeester is dood -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#409552: uninstallable: required libgcc1 version not available in unstable
Package: inkscape Version: 0.45~pre1-1 This package depends on libgcc1 1:4.2-20060728 or greater. But the version of libgcc1 in unstable is 1:4.1.1-21. -- Paul Collins Wellington, New Zealand Dag vijandelijk luchtschip de huismeester is dood -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#402255: no longer works as a module
Matt Kraai [EMAIL PROTECTED] writes: On Sat, Dec 09, 2006 at 03:56:42PM +1300, Paul Collins wrote: Package: markdown Version: 1.0.1-5 I recently upgraded from version 1.0.1-3, which seems to have broken the Markdown module. Using the example from markdown(3): [jenny(~)] perl -e 'use Markdown; $html=Markdown::Markdown(foo);' Undefined subroutine Markdown::Markdown called at -e line 1. The module was renamed to Text::Markdown, to be consistent with the version on CPAN. Does that work for you? Ah, I see. The .pm file needs to be installed as Text/Markdown.pm in Perl's search path in order for use Text::Markdown; to work. However, when I do that: [briny(~)] readlink /usr/share/perl5/Text/Markdown.pm ../../../bin/markdown [briny(~)] perl -e 'use Text::Markdown; $html=Text::Markdown::Markdown(foo);' it hangs, and when I type some stuff and hit ^D it processes it and spits out HTML, so it seems there is something elee amiss here. -- Paul Collins Wellington, New Zealand Dag vijandelijk luchtschip de huismeester is dood -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#402255: no longer works as a module
Package: markdown Version: 1.0.1-5 I recently upgraded from version 1.0.1-3, which seems to have broken the Markdown module. Using the example from markdown(3): [jenny(~)] perl -e 'use Markdown; $html=Markdown::Markdown(foo);' Undefined subroutine Markdown::Markdown called at -e line 1. -- Paul Collins Wellington, New Zealand Dag vijandelijk luchtschip de huismeester is dood -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#400507: Endianess problem whith compiz on PPC
Stephane Louise [EMAIL PROTECTED] writes: Package: compiz-core Version: 0.2.2-1 I tried compiz on my PPC mac-mini, but colours are wrongs. This sounds like bug #392453. With the updated packages installed, compiz now displays correctly on my PowerBook. -- Paul Collins Wellington, New Zealand Dag vijandelijk luchtschip de huismeester is dood -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#392453: compiz-gnome: BSOD on ppc/radeon
Benoît Dejean [EMAIL PROTECTED] writes: i've just install compiz-gnome on my G4 Ibook with radeon 9200 and it just corrupts the display : everything is blue or pink. Thanks. Similar here on a PowerBook G4 with Radeon 9600 (r300 driver). Everything's got a heavy blue tint, although the compiz effects seem to work, rotating cube and wobbly windows and such. Also I seem to have to hold down control for mouse clicks to be received by X clients -- otherwise they are handled by compiz. Probably unrelated. -- Paul Collins Wellington, New Zealand Dag vijandelijk luchtschip de huismeester is dood
Bug#391580: package description could be more informative
Package: dtach Version: 0.7-1 Severity: low In my search for a screen replacement, I did not consider dtach because the description does not mention that one can re-attach, and so I concluded that dtach is a nohup replacement. Please consider fleshing out the package description, perhaps incorporating this text from the project's Web site: dtach is a tiny program that emulates the detach feature of screen, allowing you to run a program in an environment that is protected from the controlling terminal and attach to it later. dtach does not keep track of the contents of the screen, and thus works best with programs that know how to redraw themselves. dtach does not, however, have the other features of screen, such as its support of multiple terminals or its terminal emulation support. This makes dtach extremely tiny compared to screen, making it more easily audited for bugs and security holes, and also allows it to fit in environments where space is limited, such as on rescue disks. -- Paul Collins Wellington, New Zealand Dag vijandelijk luchtschip de huismeester is dood -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#370600: reportbug 3.21 fails to configure (while failed != True: SyntaxError: invalid syntax)
Here is a (rather noisy) patch that lets the file compile.
1) Replaced leading pairs of tabs with eight spaces to produce correct
indentation.
2) Appended ':' at line 371 to produce well-formed if statement.
--- reportbug/usr/share/reportbug/reportbug_submit.py 2006-06-05
22:59:23.0 +1000
+++ /usr/share/reportbug/reportbug_submit.py2006-06-06 14:15:00.0
+1000
@@ -350,34 +350,34 @@
toaddrs = [x[1] for x in alist]
smtp_message = re.sub(r'(?m)^[.]', '..', message)
- # Modified by AP 2006-03-29
- while failed != True:
- ewrite(Connecting to %s via SMTP...\n, smtphost)
- try:
- conn = smtplib.SMTP(smtphost)
- if smtptls:
- conn.starttls()
- if smtpuser:
- if not smtppasswd:
- smtppasswd = ui.get_password(
- 'Enter SMTP password
for [EMAIL PROTECTED]: ' %
- (smtpuser, smtphost))
- conn.login(smtpuser, smtppasswd)
- conn.sendmail(fromaddr, toaddrs, smtp_message)
- conn.quit()
- except (socket.error, smtplib.SMTPException), x:
-
- # If wrong password, try again...
- if smtplib.SMTPResponseException.smtp_code ==
'535'
- ewrite('SMTP error: authentication
failed. Try again.')
- continue
-
- failed = True
- ewrite('SMTP send failure: %s\n', x)
- fh, msgname = TempFile(prefix=tfprefix)
- fh.write(message)
- fh.close()
- ewrite('Wrote bug report to %s\n', msgname)
+# Modified by AP 2006-03-29
+while failed != True:
+ ewrite(Connecting to %s via SMTP...\n, smtphost)
+ try:
+ conn = smtplib.SMTP(smtphost)
+ if smtptls:
+ conn.starttls()
+ if smtpuser:
+ if not smtppasswd:
+ smtppasswd = ui.get_password(
+ 'Enter SMTP password for [EMAIL
PROTECTED]: ' %
+ (smtpuser, smtphost))
+ conn.login(smtpuser, smtppasswd)
+ conn.sendmail(fromaddr, toaddrs, smtp_message)
+ conn.quit()
+ except (socket.error, smtplib.SMTPException), x:
+
+ # If wrong password, try again...
+ if smtplib.SMTPResponseException.smtp_code == '535':
+ ewrite('SMTP error: authentication failed. Try
again.')
+ continue
+
+ failed = True
+ ewrite('SMTP send failure: %s\n', x)
+ fh, msgname = TempFile(prefix=tfprefix)
+ fh.write(message)
+ fh.close()
+ ewrite('Wrote bug report to %s\n', msgname)
else:
try:
pipe.write(message)
--
Paul Collins
Melbourne, Australia
Dag vijandelijk luchtschip de huismeester is dood
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#368750: confusing debconf question
Package: sash Version: 3.7-7 Severity: minor When sash is installed, one is asked: Configuring sash Do you want to create a second root account with sash as its shell? The account name will be sashroot. Advantage: current root account is left untouched Disadvantage: you'd have two root accounts to keep track of Create sashroot account? Since saying no does not actually change root's shell, perhaps the advantage line should be deleted. -- Dag vijandelijk luchtschip de huismeester is dood -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#368415: fails to install - missing library?
Package: gauche Version: 0.8.7-1 Upgrade to this version is failing with the following: Setting up gauche (0.8.7-1) ... *** ERROR: Compile Error: Compile Error: can't find dlopen-able module gauche-collection-lib /usr/share/gauche/0.8.7/lib/gauche/uvector.scm:42:(define-module gauche.uvector (use g ... /usr/share/gauche/0.8.7/lib/slib.scm:8:(define-module slib (use srfi-0) (us ... Stack Trace: ___ dpkg: error processing gauche (--configure): subprocess post-installation script returned error exit status 1 Errors were encountered while processing: gauche E: Sub-process /usr/bin/dpkg returned an error code (1) [briny(~)] ls /usr/lib/gauche/0.8.7/powerpc-unknown-linux-gnu/*collection* ls: /usr/lib/gauche/0.8.7/powerpc-unknown-linux-gnu/*collection*: No such file or directory -- Dag vijandelijk luchtschip de huismeester is dood -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#367371: wikilist installed to wrong location
Package: ikiwiki Version: 1.1 Both the documentation and ikiwiki-mass-rebuild itself refer to /etc/ikiwiki/wikilist, but it is installed as /etc/wikilist. -- Dag vijandelijk luchtschip de huismeester is dood -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#366121: X fonts transition: alias file needs to be installed in new location
Russ Allbery [EMAIL PROTECTED] writes: Paul Collins [EMAIL PROTECTED] writes: Although postinst now calls update-fonts-dir and update-fonts-alias correctly for xorg 7 (following resolution of bug #362383), these tools look in /etc/X11/fonts/X11R7/$wossname for alias files when passed --x11r7-layout, not /etc/X11/fonts/$wossname. It looks like updated font packages are installing their alias file in both locations. It looks like this is being fixed in xfonts-utils by getting rid of the new X11R7 directory, so if I change it now, I'll have to change it back again. I'm therefore going to hold off until new versions of debhelper and xfonts-utils have been uploaded and then upload with the new dependencies. Having just upgraded to xfonts-utils 1.0.0-4, I tried reinstalling xfonts-jmk 3.0-10, and now the font aliases appear as expected. -- Dag vijandelijk luchtschip de huismeester is dood -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#366121: X fonts transition: alias file needs to be installed in new location
Package: xfonts-jmk Version: 3.0-10 Although postinst now calls update-fonts-dir and update-fonts-alias correctly for xorg 7 (following resolution of bug #362383), these tools look in /etc/X11/fonts/X11R7/$wossname for alias files when passed --x11r7-layout, not /etc/X11/fonts/$wossname. It looks like updated font packages are installing their alias file in both locations. -- Dag vijandelijk luchtschip de huismeester is dood -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#365855: tag editing: buttons disabled, most operations impossible
Package: quodlibet Version: 0.20-1 When I right-click an album in the album list and select Edit Tags, all of the buttons in the resulting window are disabled, making it difficult to do anything. exfalso shows a similar problem. Here is a screenshot with the artist tag changed: http://jenny.ondioline.org/~paul/ql-bug.png -- Dag vijandelijk luchtschip de huismeester is dood -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#356250: firefox -P, -CreateProfile, etc., don't work due to -a
* debian/firefox-runner, debian/firefox.1: Patch from Ian Jackson to
make -P, -CreateProfile and -ProfileManager options correctly work
again, and improve the manual page. (Closes: #356250)
It doesn't seem to quite fix this problem. I had to make the
following change for the -ProfileManager option to work, but I don't
know this if is the right way to do it.
--- firefox~2006-03-13 06:22:34.0 +
+++ firefox 2006-03-16 09:36:04.0 +
@@ -199,11 +199,13 @@
-g | -debug)
DEBUG=1
;;
--P | -ProfileManager | -CreateProfile | -no-remote)
+-P | -CreateProfile | -no-remote)
MOZ_NO_REMOTE=1
export MOZ_NO_REMOTE
;;
-ProfileManager)
+MOZ_NO_REMOTE=1
+export MOZ_NO_REMOTE
APPLICATION_ID=unique--`uname -n`--$$
set $@ ${arg}
;;
--
Dag vijandelijk luchtschip de huismeester is dood
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#356335: description does not mention cifs
Package: smbfs Version: 3.0.21b-1 Severity: wishlist Please consider mentioning in the package description that this package also includes support for mounting with the cifs filesystem in recent 2.6 kernels, to make it easier to find via apt-cache. -- Dag vijandelijk luchtschip de huismeester is dood -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#350901: crash on File - Open after or while playing a file
Package: totem-xine Version: 1.2.1-3 Playing a movie and then doing File - Open results in a crash. Here's a backtrace. Program received signal SIGSEGV, Segmentation fault. [Switching to Thread 805521088 (LWP 3160)] 0x0eabb54c in g_object_ref () from /usr/lib/libgobject-2.0.so.0 (gdb) bt #0 0x0eabb54c in g_object_ref () from /usr/lib/libgobject-2.0.so.0 #1 0x0f7cec34 in _gtk_file_chooser_default_get_type () from /usr/lib/libgtk-x11-2.0.so.0 #2 0x0f7bfdd4 in gtk_file_chooser_add_filter () from /usr/lib/libgtk-x11-2.0.so.0 #3 0x0f7bfdd4 in gtk_file_chooser_add_filter () from /usr/lib/libgtk-x11-2.0.so.0 #4 0x0f7bfdd4 in gtk_file_chooser_add_filter () from /usr/lib/libgtk-x11-2.0.so.0 #5 0x10029824 in totem_add_files () #6 0x10019610 in totem_action_open_dialog () #7 0x100196e8 in totem_action_open_dialog () #8 0x0eac7f14 in g_cclosure_marshal_VOID__VOID () from /usr/lib/libgobject-2.0.so.0 #9 0x0eab82b0 in g_closure_invoke () from /usr/lib/libgobject-2.0.so.0 #10 0x0eacc2e8 in g_signal_stop_emission () from /usr/lib/libgobject-2.0.so.0 #11 0x0eacd558 in g_signal_emit_valist () from /usr/lib/libgobject-2.0.so.0 #12 0x0eacd99c in g_signal_emit () from /usr/lib/libgobject-2.0.so.0 #13 0x0f959bf8 in gtk_widget_activate () from /usr/lib/libgtk-x11-2.0.so.0 #14 0x0f84c3e8 in gtk_menu_shell_activate_item () from /usr/lib/libgtk-x11-2.0.so.0 #15 0x0f84c7d8 in gtk_menu_shell_activate_item () from /usr/lib/libgtk-x11-2.0.so.0 #16 0x0f83fcac in gtk_menu_reorder_child () from /usr/lib/libgtk-x11-2.0.so.0 #17 0x0f8386dc in _gtk_marshal_BOOLEAN__BOXED () from /usr/lib/libgtk-x11-2.0.so.0 #18 0x0eab79cc in g_cclosure_new_swap () from /usr/lib/libgobject-2.0.so.0 #19 0x0eab82b0 in g_closure_invoke () from /usr/lib/libgobject-2.0.so.0 #20 0x0eacbef8 in g_signal_stop_emission () from /usr/lib/libgobject-2.0.so.0 #21 0x0eacd274 in g_signal_emit_valist () from /usr/lib/libgobject-2.0.so.0 #22 0x0eacd99c in g_signal_emit () from /usr/lib/libgobject-2.0.so.0 #23 0x0f959e84 in gtk_widget_activate () from /usr/lib/libgtk-x11-2.0.so.0 #24 0x0f836478 in gtk_propagate_event () from /usr/lib/libgtk-x11-2.0.so.0 #25 0x0f8369f8 in gtk_main_do_event () from /usr/lib/libgtk-x11-2.0.so.0 #26 0x0f64c80c in _gdk_events_queue () from /usr/lib/libgdk-x11-2.0.so.0 #27 0x0e850bb4 in g_main_context_dispatch () from /usr/lib/libglib-2.0.so.0 #28 0x0e854e6c in g_main_context_check () from /usr/lib/libglib-2.0.so.0 #29 0x0e8552c4 in g_main_loop_run () from /usr/lib/libglib-2.0.so.0 #30 0x0f8357d8 in gtk_main () from /usr/lib/libgtk-x11-2.0.so.0 #31 0x1001cbe8 in main () -- System Information: Debian Release: unstable APT prefers unstable APT policy: (500, 'unstable'), (499, 'experimental') Architecture: powerpc (ppc) Shell: /bin/sh linked to /bin/bash Kernel: Linux 2.6.14.3 Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968) Versions of packages totem-xine depends on: ii gconf2 2.12.1-8 GNOME configuration database syste ii libart-2.0-2 2.3.17-1 Library of functions for 2D graphi ii libatk1.0-01.10.3-1 The ATK accessibility toolkit ii libaudiofile0 0.2.6-6 Open-source version of SGI's audio ii libbonobo2-0 2.10.1-1 Bonobo CORBA interfaces library ii libbonoboui2-0 2.10.1-2 The Bonobo UI library ii libc6 2.3.5-12 GNU C Library: Shared libraries an ii libcairo2 1.0.2-3 The Cairo 2D vector graphics libra ii libdbus-1-20.60-5simple interprocess messaging syst ii libdbus-glib-1-2 0.60-5simple interprocess messaging syst ii libesd00.2.36-3 Enlightened Sound Daemon - Shared ii libexpat1 1.95.8-3 XML parsing C library - runtime li ii libfontconfig1 2.3.2-1.1 generic font configuration library ii libfreetype6 2.1.10-1 FreeType 2 font engine, shared lib ii libgconf2-42.12.1-8 GNOME configuration database syste ii libgcrypt111.2.2-1 LGPL Crypto library - runtime libr ii libglade2-01:2.5.1-2 library to load .glade files at ru ii libglib2.0-0 2.8.6-1 The GLib library of C routines ii libgnome-desktop-2 2.12.2-2 Utility library for loading .deskt ii libgnome-keyring0 0.4.6-2 GNOME keyring services library ii libgnome2-02.12.0.1-4The GNOME 2 library - runtime file ii libgnomecanvas2-0 2.12.0-2 A powerful object-oriented display ii libgnomeui-0 2.12.0-2 The GNOME 2 libraries (User Interf ii libgnomevfs2-0 2.12.2-5 GNOME virtual file-system (runtime ii libgnutls111.0.16-14 GNU TLS library - runtime library ii libgpg-error0
Bug#343879: mozilla-firefox-dom-inspector removed and not replaced on dist-upgrade
Package: firefox-dom-inspector Version: 1.5.dfsg-1 When dist-upgrading to this version of firefox, mozilla-firefox-dom-inspector is removed and the new firefox-dom-inspector package is left uninstalled. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#327675: lilypond: typo in package description
Package: lilypond Severity: minor Version: 2.4.5-2 seemless should read seamless. Regards, Paul -- Dag vijandelijk luchtschip de huismeester is dood -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#290891: does not supply /usr/lib/libhttp_fetcher.so
Package: libhttpfetcher-dev Version: 1.0.1-1.1 Severity: serious This package does not supply /usr/lib/libhttp_fetcher.so, violating Policy section 8.4. Since the .so symlink is not present, static linking is performed. Users building programs against this library end up with an binary containing potentially network-exploitable code that is not covered by normal security updates. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
