Bug#407507: icedove: Purge doesn't remove all config files
Package: icedove Version: 1.5.0.9.dfsg1-1 Severity: normal Running "aptitude purge icedove" doesn't remove /etc/icedove/auto-config.js -- System Information: Debian Release: 4.0 APT prefers testing APT policy: (990, 'testing') Architecture: i386 (i686) Shell: /bin/sh linked to /bin/bash Kernel: Linux 2.6.18-3-686 Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#376380: -x does not work as expected [PATCH]
Here's a patch that will cause spamc to return the failure code when -x is specified, regardless of the -e flag: --- spamassassin-3.1.7/spamc/spamc.c2006-09-29 06:06:44.0 -0700 +++ spamassassin-3.1.7-new/spamc/spamc.c2007-01-11 18:59:32.594271748 -0800 @@ -819,6 +819,9 @@ } free(username); +if (ret != EX_OK && (flags & SPAMC_SAFE_FALLBACK) == 0) + goto finish; + /* FAIL: */ get_output_fd(&out_fd); Now, one COULD just use a line like this in master.cf: spamassassin unix - n n - - pipe flags=q user=nobody argv=/usr/local/bin/spamc -x -u $(recipient) -e /usr/sbin/sendmail -oi -f $(sender) $(recipient) HOWEVER, this will cause mail to bounce if your spamd is unavailable. This is because spamc can return any one of several error codes. Postfix will only queue mail if the return code is specifically EX_TEMPFAIL. I prefer all mail to queue up if spamd is down for some reason. So, I wrote a script that does that: /usr/local/bin/spam_filter: #!/bin/bash RECIPIENT=$1 SENDER=$2 EX_OK=0 EX_TEMPFAIL=75 if /usr/local/bin/spamc -x -u "$RECIPIENT" -e /usr/sbin/sendmail -oi -f "$SENDER" "$RECIPIENT"; then exit $EX_OK; else exit $EX_TEMPFAIL; fi Then I use a line like this in master.cf: spamassassin unix - n n - - pipe flags=q user=nobody argv=/usr/local/bin/spam_filter $(recipient) $(sender) Hope this helps! -- Kevin
Bug#737811: icedove: Missing /usr/lib/icedove/components/components.manifest
Package: icedove Version: 24.2.0-1 Severity: normal Dear Maintainer, My installation of Icedove wouldn't open links in a browser, it would keep asking me to select what program to use to open the link. It turns out the root cause is a missing file, /usr/lib/icedove/components/components.manifest. I grabbed the latest tarball from upstream, and copied the file, and now clicking on links works again. -- System Information: Debian Release: jessie/sid APT prefers unstable APT policy: (500, 'unstable') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.12-1-amd64 (SMP w/8 CPU cores) Locale: LANG=en_US.utf8, LC_CTYPE=en_US.utf8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages icedove depends on: ii debianutils 4.4 ii fontconfig2.11.0-2 ii libasound21.0.27.2-3 ii libatk1.0-0 2.10.0-2 ii libc6 2.17-97 ii libcairo2 1.12.16-2 ii libdbus-1-3 1.8.0-1 ii libdbus-glib-1-2 0.100.2-1 ii libevent-2.0-52.0.21-stable-1 ii libffi6 3.0.13-12 ii libfontconfig12.11.0-2 ii libfreetype6 2.5.2-1 ii libgcc1 1:4.8.2-14 ii libgdk-pixbuf2.0-02.28.2-1+b1 ii libglib2.0-0 2.36.4-1 ii libgtk2.0-0 2.24.22-1 ii libhunspell-1.3-0 1.3.2-6 ii libnspr4 2:4.10.2-1 ii libnss3 2:3.15.4-2 ii libpango-1.0-01.36.0-1+b1 ii libpixman-1-0 0.32.4-1 ii libsqlite3-0 3.8.2-1 ii libstartup-notification0 0.12-3 ii libstdc++64.8.2-14 ii libvpx1 1.3.0-2 ii libx11-6 2:1.6.2-1 ii libxext6 2:1.3.2-1 ii libxrender1 1:0.9.8-1 ii libxt61:1.1.4-1 ii psmisc22.20-1 ii zlib1g1:1.2.8.dfsg-1 Versions of packages icedove recommends: ii hunspell-en-us [hunspell-dictionary] 20070829-6 Versions of packages icedove suggests: pn fonts-lyx ii libglib2.0-0 2.36.4-1 ii libgssapi-krb5-2 1.12+dfsg-2 -- no debconf information -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#666980: zoneminder: hash authentication broken in update
On 07/18/2012 09:25 PM, Marcelo Jorge Vieira wrote: Hi Kevin, On Sun, 2012-04-15 at 15:12 -0700, Kevin Ross wrote: I'm having the same problem, but unfortunately for me, your workaround isn't working for me. Looking at my apache access.log, I can see it is passing the user name, but it isn't passing the password. So for now, I have completely turned off authentication. Obviously this is not a great solution, but it gets me back up and running while waiting for a fix. you can try turn on authentication and set AUTH_RELAY to 'none'. Cheers, Thanks, that worked! -- Kevin -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#656314: Debian Bug report logs - #656314,logcheck.logfiles * pattern does not work
I believe this is fixed in 1.3.14. Hope this helps! -- Kevin -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#632754: (no subject)
I also use the PPA for Wine in Wheezy. When I added the PPA, I did it
manually, but I was curious to see if it could be automated.
In /usr/lib/python2.6/dist-packages/softwareproperties/ppa.py
change:
sourceslistd = apt_pkg.Config.find_dir("Dir::Etc::sourceparts")
to this:
sourceslistd = apt_pkg.config.find_dir("Dir::Etc::sourceparts")
(Config should be lowercase)
Now, when you run apt-add-repository ppa:ubuntu-wine/ppa, it properly
adds the signing key, and creates a new file called
/etc/apt/sources.list.d/ubuntu-wine-ppa-wheezy.list, the contents of
which are:
deb http://ppa.launchpad.net/ubuntu-wine/ppa/ubuntu wheezy main
deb-src http://ppa.launchpad.net/ubuntu-wine/ppa/ubuntu wheezy main
It should be obvious that there aren't any "wheezy" releases on
Launchpad, so you'll have to change that to something more appropriate,
such as lucid for Squeeze systems, or maverick or natty for Wheezy or
Sid systems.
Hope this helps!
-- Kevin
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#666980: zoneminder: hash authentication broken in update
I'm having the same problem, but unfortunately for me, your workaround isn't working for me. Looking at my apache access.log, I can see it is passing the user name, but it isn't passing the password. So for now, I have completely turned off authentication. Obviously this is not a great solution, but it gets me back up and running while waiting for a fix. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#746737: (no subject)
I think this is a duplicate of #430684. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
