Bug#412068: zaptel-source: doesn't compile with 2.6.18-4 kernel in sid
Is debugfs enabled by default in the current SID kernel? Looks to be: [EMAIL PROTECTED]:/usr/src/linux-headers-2.6.18-4-686# grep DEBUG_FS .config CONFIG_DEBUG_FS=y The patch for that is basically pretty simple (look in the code a bit above that line) but should also be included in zaptel 1.2.14 . Yeah, that does the job. Thanks, Richard. _ Get Hotmail, News, Sport and Entertainment from MSN on your mobile. http://www.msn.txt4content.com/ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#399174: libphp-adodb cannot be installed on unstable
Package: libphp-adodb Version: 4.72-0.1 Severity: grave Package cannot be installed. The following packages have unmet dependencies. libphp-adodb: Depends: phpapi-20050606 but it is not installable or phpapi-20051025 but it is not installable Richard. _ The new Windows Live Toolbar helps you guard against viruses http://toolbar.live.com/?mkt=en-gb -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#367081: sa-exim: not working with latest spamassassin package
From: Sander Smeenk [EMAIL PROTECTED] I don't really know what might cause this all. Did you change something in your spamassassin/local.cf? Or maybe made changes to sa-exim.conf? Nothing in the spamassassin file was changed, and no recent changes to sa-exim conf. Or with purging, did you also remove all the config files? Yep. I've got past the problem now, though I can't say I've figured out what was really wrong with it. With the new version of spamassassin (I assume) the spamd daemon became disabled, and reenabling it has fixed my problem. However the original problem can't have been that simple, because I originally saw no connection refused messages in syslog from spamc, but instead I saw a report of the spam status of each incoming message. Which was pretty confusing since it made everything look like it was working perfectly. Anyway, some combination of purging, reinstalling, and playing with config files has solved the problem. The only thing I would say is the unknown error message in SA could be a bit better, after looking at the code and turning up the debug I could see that unknown error meant more specifically that no X-Spam-Status header was in what came back from spamc. Also, it would be nice if spamc could give some feedback as to the problem it had, perhaps a header to indicate why it didn't actually do anything with the message, but that's obviously an issue for the developers of that, not you. You are welcome to close this bug, I haven't myself just incase you do want to use it improve the error messages to aid debugging. Richard. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#367081: sa-exim: not working with latest spamassassin package
I'm drowning in spam here, any more ideas on what I can check? I've tried purging the sa-exim and spam assassin packages and reinstalling, didn't help. Logs still show SA appears to be working fine, but sa-exim is still saying there was an unknown failure. Richard. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#367081: sa-exim: not working with latest spamassassin package
I sent this once already and it never made it onto the bug tracker, so trying again. Which means SA-Exim did work, but SpamAssassin itself failed for some reason. It would be great if you can search through your logs and see if you can find out why SpamAssassin isn't working. From syslog: May 14 14:29:41 localhost spamd[14765]: spamd: connection from localhost [127.0.0.1] at port 34030 May 14 14:29:41 localhost spamd[14765]: spamd: setuid to Debian-exim succeeded May 14 14:29:41 localhost spamd[14765]: spamd: processing message [EMAIL PROTECTED] for Debian-exim:102 May 14 14:29:41 localhost spamd[14765]: spamd: clean message (1.9/5.0) for Debian-exim:102 in 0.6 seconds, 994 bytes. May 14 14:29:41 localhost spamd[14765]: spamd: result: . 1 - AWL,DNS_FROM_RFC_ABUSE,DNS_FROM_RFC_POST,MSGID_FROM_MTA_HEADER scantime=0.6,size=994,user=Debian-exim,uid=102,required_score=5.0,rhost=localhost,raddr=127.0.0.1,rport=34030,mid=[EMAIL PROTECTED],autolearn=no May 14 14:29:41 localhost spamd[14764]: prefork: child states: II Looks to me like SA is happy at it's end. Please let me know what else to collect/try. Richard. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#365831: xserver-xorg: uninstallable on clean system, preinst exit status 10
Package: xserver-xorg Version: 1:7.0.15 Severity: grave xserver-xorg cannot be installed on a clean system. clean system was created using DFS cd to bootstrap unstable. Previously I would have installed xwindows-system-core gnome-desktop-environment to get my desktop. I wasn't totally sure what x-windows-system-core translated to with xorg, so I guessed at xserver-xorg-core. This installed fine, but gdm wouldn't start (no /etc/X11/X symlink), so I proceeded to try and install xserver-xorg (which thinking about it is probably the one that creates this symlink, as well as the xorg config file). xserver-xorg gives: subprocess pre-installation script returned error exit status 10 Rebuilding the package with -x in the preinst I can see that it's failing at the call to /use/share/debconf/frontend. Sticking a couple of prints in there I can see it's $confmodule-exitcode that's 10 on after the while ($confmodule-communicate) loop. I don't know anything about debconf, so I can't diagnose any further without some instruction. Please let me know what else I can do... Richard. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#365831: xserver-xorg: uninstallable on clean system, preinst exit status
This is fixed in version 1:7.0.16 of xserver-xorg in incoming. Confirmed fixed. Sorry for the dupe (I did check, but somehow missed it). Richard. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#362672: xserver-xorg: what happens if you delete /usr/X11R6/bin/X symlink...
Package: xserver-xorg Version: 1:7.0.11 Followup-For: Bug #362672 FYI: I figured that the X symlink was probably just a left over and not all that important, so I tried deleting it and doing a reconfigure of the x packages. This caused the /usr/X11R6/bin folder to be deleted and a new symlink to /usr/bin was created. When I next tried to start gdm it failed to find /usr/X11R6/bin/X. Following the chain of symlinks leads you to /bin/X, which doesn't exist. To fix this on my system I linked this to /etc/X11/X, which in turn points to your chosen X, so I assume this is the correct thing to do. Richard. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#347847: #347847 vlc: Not installable on powerpc unstable
retitle 347847 vlc: Not installable on unstable thanks It's not just powerpc, also x86. Richard. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#343042: [Yaird-devel] Bug#343042: #343042: linux-image-2.6.14-2-686: Boot aborts wit
From: Erik van Konijnenburg [EMAIL PROTECTED] On Wed, Dec 14, 2005 at 10:42:58AM +, Richard Antony Burton wrote: FYI the above workaround does not work for machines with SATA drives. I couldn't find a combination of modules that would get it to boot. To help debugging, could you post your version of /etc/yaird/Default.cfg, plus the output of yaird -v for the working version and the broken version? I can no longer recreate the problem. To give more background, which may explain why, this was a clean install on a new box with SATA, using Debian From Scratch 0.6.19. I was under the 2.6.11 kernel from the CD when I build the initrd in a chroot to my new install. /proc and /sys were both mounted, and yaird appeared to complete sucessfully. I have tried booting from the DFS CD again under the same kernel and still cannot recreate the problem. The bootstrapped version of sid from the CD contained quite a few backlevel packages, which have since been updated, so maybe this has some bearing on it? I don't have another box like this I can reinstall now to try again from scratch. Anyway, in my current system state I can build a working initrd from the latest yaird, and since there is no upgrade path to 2.6.14/yaird from Sarge (and so probably no official upgrade path from anything else either) this can probably be discounted as an odd one-off. Regards, Richard. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#332898: new udev package
I uploaded a new *untested* package at http://www.bofh.it/~md/debian/ , please let me know ASAP if it fixes the bugs you reported (mainly mousedev and evdev not being automatically loaded). Sorry, new package doesn't cause mousedev or psmouse to be loaded on my system, so without adding them to /etc/modules I still get no X. Richard. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
