Bug#842417: TAG: Nightingale -- media player and library

Package: wnpp Severity: RFP Some information about the package https://getnightingale.com/ https://getnightingale.com/all-versions.php https://github.com/nightingale-media-player http://wiki.getnightingale.com/doku.php?id=licensing GNU General Public License version 2.0

Bug#842415: TAG: fre:ac-- free audio converter and CD ripper

Package: wnpp Severity: RFP Some information about the package https://www.freac.org/ https://sourceforge.net/projects/bonkenc/ GNU General Public License version 2.0 (GPLv2)

Bug#842413: TAG: Quick Hash GUI -- Hashing GUI Tool

Package: wnpp Severity: RFP Some information about the package https://sourceforge.net/projects/quickhash/ https://github.com/tedsmith/quickhash/releases GNU General Public License version 2.0 (GPLv2)

Bug#842412: TAG: Money Manager Ex -- Is an easy to use, money management application

Package: wnpp Severity: RFP Some information about the package https://github.com/moneymanagerex/moneymanagerex/releases https://github.com/moneymanagerex https://sourceforge.net/projects/moneymanagerex/ http://www.moneymanagerex.org/

Bug#823418: Info received (Bug#823418: exim4: Since the last update, it seems like some messages are rejected after DATA)

very much, David Hill -Original Message- From: Marc Haber Sent: Friday, May 6, 2016 4:10 PM To: David Hill Cc: 823...@bugs.debian.org Subject: Re: Bug#823418: Info received (Bug#823418: exim4: Since the last update, it seems like some messages are rejected after DATA) retitle #823418 add

Bug#823418: Info received (Bug#823418: exim4: Since the last update, it seems like some messages are rejected after DATA)

Hello Marc, This solved this issue ... Now, why is this enforced ? This is a new behavior and a lot of smtp servers are not enforcing this limitation like hotmail and some banks. Thank you very much, David Hill On 05/05/2016 04:13 PM, Marc Haber wrote: On Thu, May 05, 2016 at 01:15

Bug#823418: exim4: Since the last update, it seems like some messages are rejected after DATA

Hello sir, If I send you the templates in a secure location would it help you ? Thank you very much, David Hill -Original Message- From: Andreas Metzler Sent: Wednesday, May 4, 2016 12:56 PM To: David Hill ; 823...@bugs.debian.org Subject: Re: Bug#823418: exim4: Since the last

Bug#823418: exim4: Since the last update, it seems like some messages are rejected after DATA

) [127.0.0.1] F=<spamt...@hotmail.com> rejected after DATA Thank you very much, David Hill On 05/04/2016 05:54 PM, David Hill wrote: Hello sir, If I send you the templates in a secure location would it help you ? Thank you very much, David Hill -Original Message- From: Andreas M

Bug#823418: Acknowledgement (exim4: Since the last update, it seems like some messages are rejected after DATA)

False alarm... it didn't fix anything. On 05/04/2016 12:19 PM, David Hill wrote: Setting DISABLE_DKIM_VERIFY='true' solved my problem. On 05/04/2016 11:58 AM, David Hill wrote: One sample of the dropped message that seems to have started on Apr 18. T To: spamt...@binarystorm.net R Reply

Bug#823418: Acknowledgement (exim4: Since the last update, it seems like some messages are rejected after DATA)

Setting DISABLE_DKIM_VERIFY='true' solved my problem. On 05/04/2016 11:58 AM, David Hill wrote: One sample of the dropped message that seems to have started on Apr 18. T To: spamt...@binarystorm.net R Reply-To: carrie...@workopolis.com F From: "Workopolis Alerte aux Emploi&quo

Bug#823418: Acknowledgement (exim4: Since the last update, it seems like some messages are rejected after DATA)

One sample of the dropped message that seems to have started on Apr 18. T To: spamt...@binarystorm.net R Reply-To: carrie...@workopolis.com F From: "Workopolis Alerte aux Emploi" 2016-04-29 03:36:36 1aw2ya-0004Lo-0P H=localhost (binarystorm.net) [127.0.0.1]

Bug#823418: exim4: Since the last update, it seems like some messages are rejected after DATA

Package: exim4 Version: 4.87-2 Severity: important Dear Maintainer, *** Reporter, please consider answering these questions, where appropriate *** * What led up to the situation? I updated * What exactly did you do (or not do) that was effective (or ineffective)? I updated

Bug#730839: mirror submission for mirror.as24220.net

: mirror.aarnet.edu.au CDImage-upstream: mirror.aarnet.edu.au Updates: four Maintainer: David Hill mirr...@as24220.net Country: AU Australia Location: Melbourne, Australia Sponsor: Hostcentral http://www.hostcentral.net.au/ Comment: Mirror connected at 1Gbit/s -- To UNSUBSCRIBE, email to debian

Bug#653671: mrtg: MRTG stopped working with ipv6 turned on

Package: mrtg Version: 2.17.3-2 Severity: important Dear Maintainer, When mrtg is running, I now have these messages: wolfe:/etc/cron.d# env LANG=C /usr/bin/mrtg /etc/mrtg.cfg 21 Subroutine SNMP_Session::pack_sockaddr_in6 redefined at /usr/share/perl/5.14/Exporter.pm line 67. at

Bug#649835: mailscanner: Since perl update MailScanner seems to fork another parent with children (fork bomb?)

Package: mailscanner Version: 4.79.11-2.2 Severity: important Dear Maintainer, * Updating perl (and or spamassassin) seems to have trigered this issue * I did nothing, still trying to figure out why it does this... * I was expecting MailScanner to be not affected by any of these

Bug#649835: Acknowledgement (mailscanner: Since perl update MailScanner seems to fork another parent with children (fork bomb?))

...@bugs.debian.org Sent: Thursday, November 24, 2011 2:03 AM To: David Hill report...@binarystorm.net Subject: Bug#649835: Acknowledgement (mailscanner: Since perl update MailScanner seems to fork another parent with children (fork bomb?)) Thank you for filing a new Bug report with Debian

Bug#649835: Acknowledgement (mailscanner: Since perl update MailScanner seems to fork another parent with children (fork bomb?))

To: David Hill report...@binarystorm.net Subject: Bug#649835: Acknowledgement (mailscanner: Since perl update MailScanner seems to fork another parent with children (fork bomb?)) Thank you for filing a new Bug report with Debian. This is an automatically generated reply to let you know your

Bug#628237: Info received (slapd refuses to start ... just to let you know ;))

Recompiling the package solves my problem. BTW, I have cyrus and cyrus updated sasl and then slapd broke at restart... :S On 2011-06-02, at 1:39 AM, Debian Bug Tracking System wrote: Thank you for the additional information you have supplied regarding this Bug report. This is an

Bug#628919: /usr/sbin/chronyd: Starting with kernel v3.0, chronyd will refuse to start

Package: chrony Version: 1.24-3+b1 Severity: important File: /usr/sbin/chronyd wolfe:/etc/init.d# chronyd -d sys_linux.c:688:(get_version_specific_details)[02-12:36:37] Initial txc.tick=1 txc.freq=0 (0.) txc.offset=0 = hz=100 shift_hz=7

Bug#628237: slapd refuses to start ... just to let you know ;)

-- This message has been scanned for viruses and dangerous content by MailScanner, and is believed to be clean. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Bug#620958: I have the same issue...

I manually edited /var/lib/dpkg/status to add architecture to the packages where it was missing. Everything's working fine now! :) Thank you for the bug report! -- This message has been scanned for viruses and dangerous content by MailScanner, and is believed to be clean. -- To

Bug#627143: Dependency problem while updating to cyrus-common-2.4 - 2.4.8

Package: cyrus-common-2.4 Version: 2.4.8-6 Severity: important Unless I --force-all, I can't update to the newest package ... (Reading database ... 101660 files and directories currently installed.) Preparing to replace cyrus-imapd-2.4 2.4.8-2 (using .../cyrus-imapd-2.4_2.4.8-6_i386.deb) ...

Bug#620320: cyrus-imapd-2.4: fetching user_deny.db entry for users is appearing millions of times in log files

I think removing debug from syslog-ng isn't a solution Why? You can only remove logging of the mail.debug, or even use match() or message() functionality to filter out unwanted cyrus-imapd messages. Sure we can do this, but wouldn't it be better to simply remove it? Is it useful to anbody?

Bug#620320: cyrus-imapd-2.4: fetching user_deny.db entry for users is appearing millions of times in log files

Package: cyrus-imapd-2.4 Version: 2.4.7-3 Severity: normal Tags: experimental I think removing debug from syslog-ng isn't a solution and since we can't turn off debugging in cyrus-imapd, commenting out this line seems a quick fix. Here is the patch: ---

Bug#620321: cyrus-imapd-2.4: When upgrading to cyrus 2.2/2.4, it shouldn't try to restart it

Package: cyrus-imapd-2.4 Version: 2.4.7-3 Severity: critical Tags: experimental Justification: breaks the whole system When upgrading to cyrus 2.2/2.4, it cannot start with the following messages: Mar 31 20:14:27 wolfe cyrus/lmtpunix[21633]: incorrect version of Berkeley db: compiled against

Bug#620325: cyrus-imapd-2.4: /usr/lib/cyrus/bin/squatter is missing in deb package

Package: cyrus-imapd-2.4 Version: 2.4.7-3 Severity: important Tags: experimental When using squatter or cyrus squatter, it says ERROR: squatter: Unknown command or command not installed When compiling cyrus-imapd-2.4-2.4.7, the file is present but not packaged... -- System Information: Debian

Bug#612373: With kernel 2.6.38-rc3, syslog-ng refuses to start.

Package: syslog-ng Version: 3.1.3-3 Severity: important Hi guys, Starting with kernel v2.6.38-rc3, syslog-ng will break ... it's not able to open /proc/kmsg ! I've found the following forum thread explaining why:

Bug#612373: Acknowledgement (With kernel 2.6.38-rc3, syslog-ng refuses to start.)

/syslog-ng/syslog-ng.pid +PIDFILE=/var/run/syslog-ng/syslog-ng.pid SYSLOGNG=/sbin/syslog-ng NAME=syslog-ng - Original Message - From: Debian Bug Tracking System ow...@bugs.debian.org To: David Hill report...@binarystorm.net Sent: Monday, February 07, 2011 9:27 PM Subject: Bug#612373

Bug#610439: Since last exim4 update, all messages are frozen in a queueonly demon.

Package: exim4 Version: 4.72-3 Severity: important Since last exim4 (4.72-3 and 4.73-rc1) updates, all messages are frozen in a queueonly demon. cat /var/spool/exim4.out/msglog/1PfDVi-0001xs-Bk 2011-01-18 10:30:34 u...@montcalm.dyndns.org www-d...@montcalm.dyndns.org R=local_user

Bug#610439: Since last exim4 update, all messages are frozen in a queueonly demon.

...@downhill.at.eu.org To: David Hill report...@binarystorm.net; 610...@bugs.debian.org Sent: Tuesday, January 18, 2011 12:55 PM Subject: Re: Bug#610439: Since last exim4 update, all messages are frozen in a queueonly demon. On 2011-01-18 David Hill report...@binarystorm.net wrote: Package: exim4 Version: 4.72

Bug#610367: {Spam?}

Subject: Since last exim4 update, all messages are frozen in a queueonly demon. Package: exim4 Version: 4.72-3 Severity: important -- Package-specific info: Exim version 4.72 #1 built 29-Dec-2010 19:22:37 Copyright (c) University of Cambridge, 1995 - 2007 Berkeley DB: Berkeley DB 4.8.30:

Bug#610367: Acknowledgement ({Spam?})

Rollbacking to 4.69 (not 4.72-2) solves the issue. - Original Message - From: Debian Bug Tracking System ow...@bugs.debian.org To: David Hill report...@binarystorm.net Sent: Monday, January 17, 2011 7:45 PM Subject: Bug#610367: Acknowledgement ({Spam?}) Thank you for filing a new

Bug#610367: Acknowledgement ({Spam?})

4.73-rc1 has the same issue ... lmtp deliveries to cyrus are broken procmail has the same -1 return code... - Original Message - From: Debian Bug Tracking System ow...@bugs.debian.org To: David Hill report...@binarystorm.net Sent: Monday, January 17, 2011 7:45 PM Subject: Bug#610367

Bug#564322: {Spam?} with kernel 2.6.33-rc2, udev wrongfuly whines about signalfd and inotify_user not being compiled in the kernel

Package: udev Version: 149-2 Severity: critical Justification: breaks the whole system What: - inotify(2) (CONFIG_INOTIFY_USER) - signalfd(2) (CONFIG_SIGNALFD) It is present: $ zcat config.gz | egrep -i inotify|signalfd

Bug#563104: nfs: With kernel 2.6.33-rc2, nfsd seems to be broken.

Package: nfs-kernel-server Version: 1:1.2.1-1 Severity: normal File: nfs wolfe:/etc/init.d# ps -ef | grep nfs root 276 2 0 02:55 ?00:00:00 [nfsiod] root 22198 2 0 15:50 ?00:00:00 [nfsd4] root 22200 2 0 15:50 ?00:00:00 [nfsd]

Bug#547614: ircd-irc2: Fatal Error: No working P-line in ircd.conf

Package: ircd-irc2 Version: 2.11.2p1+dfsg-1 Severity: grave Justification: renders package unusable When I try to start ircd, I get this error message: opening stream socket irc.localhost:Address family not supported by protocol Fatal Error: No working P-line in ircd.conf According to my

Bug#547613: ircd-irc2: Fatal Error: No working P-line in ircd.conf

Package: ircd-irc2 Version: 2.11.2p1+dfsg-1 Severity: normal ircd-irc2 wont start ... Here is my config file. The P-line is there ... Even with % instead of : it doesn't start. # This is ircd's config-file. Look at # /usr/share/doc/ircd-irc2/ircd.conf.example.gz and # and

Bug#529712: mailscanner: Problem with file checker.

Package: mailscanner Version: 4.74.16-1 Severity: important May 20 15:54:42 wolfe MailScanner[12034]: File checker failed with real error: Insecure dependency in exec while running with -T switch at /usr/share/MailScanner//MailScanner/SweepOther.pm line 374. I guess since perl 5.10.0-22 I get

Bug#327097: Problem fixed

It used to work with the initial configuration, but something happened in the latest upgrade that broke it. I fixed it but maybe IPV6 should not be enabled by default, it is not compiled in thy kernel :) (if it's the problem) Today I tried to connect remotely to Wolfe and Colborne xdm servers

Bug#327097: xdm: Can't connect remotely to the XDM server since last upgrade.

Package: xdm Version: 6.8.2.dfsg.1-6 Severity: grave Justification: renders package unusable What I found in /var/log/xdm.log: Wed Sep 7 11:58:34 2005 xdm info (pid 11335): not sourcing /usr/X11R6/lib/X11/xdm/Xsetup (No such file or directory) Wed Sep 7 11:59:36 2005 xdm info (pid 11326):

Bug#327121: xdm: Can't remotely connect to this computer using XDMCP protocol.

Package: xdm Version: 6.8.2.dfsg.1-6 Severity: grave Justification: renders package unusable It previously worked but doesn't anymore. It does the samethign on two computers running unstable. I tried to run gdb on it, but didn't find anything. I found that in /var/log/xdm.log Mon Aug 22

Bug#327097: Debugging code for XDM

DisplayManager.errorLogFile/DisplayManager.ErrorLogFile value /var/log/xdm.log DisplayManager.daemonMode/DisplayManager.DaemonMode value true DisplayManager.pidFile/DisplayManager.PidFile value /var/run/xdm.pid DisplayManager.lockPidFile/DisplayManager.LockPidFile value true

Bug#325277: Kmerlin: kmerlin is broken (javascript?)

Package: Kmerlin Version: 1.4.2-3 Severity: grave Justification: renders package unusable Well, it seems it just can't work! It should be removed or fixed. If it's not fixed, remove it... if it's fixed, keep it. But it's been a month or so and still no answer from the maintainer. Well, it is

Bug#325092: kmail: Kmail segfault with libqt3c102-mt but works fine with libqt3-mt, but this situation isn't a livable one.

Package: kmail Version: 4:3.3.2-3 Severity: grave Justification: renders package unusable GDB= Received signal SIGSEGV, Segmentation fault. [Switching to Thread -1244882720 (LWP 29713)] 0xb758e95b in QString::QString () from /usr/lib/libqt-mt.so.3 quite simple from this point of vue! dpkg