Bug#510524: whohas: searching for short strings triggers strange opensuse output

2009-01-24 Thread jhasler
Christoph writes: > Same thing for other short strings like abc and qwertz. I guess it's > some fuzzy search in these cases. It's fine for longer strings like > supertuxkart or automake. Try 'whohas pppconfig' and look what it returns for Suse. Looks like any substring in any source file will do

Bug#474294: RFH: Chrony goes into endless loop on x86_64

2008-04-22 Thread jhasler
From: John Hasler <[EMAIL PROTECTED]> Subject: RFH: Chrony goes into endless loop on x86_64 To: [EMAIL PROTECTED] Date: Tue, 22 Apr 2008 13:50:43 -0500 Organization: Dancing Horse Hill See bug #474294. If you have an x86_64 system you can help by a) installing chrony-1.21 from Stable or Unstab

Bug#474294: Uploaded chrony-1.23 to Experimental

2008-04-19 Thread jhasler
I've uploaded 1.23 to Experimental. Please test it and let me know if 474294 is fixed. Upstream has made changes affecting 64-bit operation. I have applied my Debian patches but have not yet addressed most bugs: I will when I upload to Unstable after 474294 is fixed. -- John Hasler -- To UN

Bug#267879: mailagent: particular emails causing a sigpipe

2007-11-24 Thread jhasler
When I send myself a message that contains only a line of test, a '.', and another line of text I get this in the agentlog: 07/11/25 02:15:12 mailagent[188286]: ERROR Search pattern not terminated at (eval 213) line 1. 07/11/25 02:15:12 mailagent[188286]: ERROR Search pattern not terminated at (

Bug#267879: mailagent: particular emails causing a sigpipe

2007-11-23 Thread jhasler
I'm seeing this too. The common factor in the messages that trigger the bug is a line containing only a '.'. I see such lines in Matt's examples as well. I am using Mailagent version 3.73-26 but I have seen this in earlier versions. -- John Hasler -- To UNSUBSCRIBE, email to [EMAIL PROTECTE

Bug#438233: units: not handling nostrip build option (policy 10.1)

2007-08-24 Thread jhasler
Install is being called with '-s'. This will be fixed in the next upload. -- John Hasler -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Bug#429156: dc: segfaults when generating primes

2007-08-22 Thread jhasler
Your script crashes 1.0.6-20 reliably on this i686 running Sid but I have not been able to get it to crash the upcoming upstream release on the same machine. -- John Hasler -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Bug#221781: dc: precision >= 1000000000 does not work

2007-08-22 Thread jhasler
Fixed in the upcoming upstream release. -- John Hasler -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Bug#221781: dc: precision >= 1000000000 does not work

2007-08-22 Thread jhasler
This is fixed in the upcoming upstream release. -- John Hasler -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Bug#296232: 'dc directory' should print an error

2007-08-22 Thread jhasler
Fixed in the next upstream release. -- John Hasler -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Bug#389345: dc: man page formatting bug

2007-08-22 Thread jhasler
I cannot reproduce this in 1.06-20. -- John Hasler -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Bug#370224: [units] crochet is spelled crotchet

2007-02-27 Thread jhasler
Fixed upstream. -- John Hasler -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Bug#375255: (no subject)

2007-02-27 Thread jhasler
From: Adrian Mariano <[EMAIL PROTECTED]> Subject: Re: Units suggestion To: [EMAIL PROTECTED], [EMAIL PROTECTED] Date: Tue, 27 Feb 2007 07:20:07 -0500 Resent-From: [EMAIL PROTECTED] On Mon, Feb 26, 2007 at 11:41:23AM -0600, [EMAIL PROTECTED] wrote: > I'm not sure I ever actually got around to forwa

Bug#294030: chronyd makes the whole system briefly (< 1 second) freeze

2007-02-03 Thread jhasler
Bill Unruh is working on a patch that may solve this problem (among others). -- John Hasler -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Bug#407466: Chrony won't access hardware clock but prevents hwclock from doing so either

2007-02-03 Thread jhasler
Bill Unruh has a patch which may fix this. If it works out I will include it in my next upload. -- John Hasler -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Bug#386994: time zone hassles between chrony/woody and chrony/etch

2006-09-14 Thread jhasler
> This is exactly two hours difference. > There is no /etc/default/rcS on the Etch machine Chrony reads /etc/default/rcS to find out if the machine is on UTC or local time. It defaults to local time. That is what is happening to you. Why is there no /etc/default/rcS? -- John Hasler -- To

Bug#381559: French man translation update

2006-08-13 Thread jhasler
I don't understand what I am to do with this file. -- John Hasler -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Bug#353509: logcheck-database: Ignore chronyd messages, please

2006-03-18 Thread jhasler
>From /etc/chrony/chrony.conf: # Comment this line out to turn off logging. log tracking measurements statistics -- John Hasler -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Bug#346009: pppconfig: Exits when Modeminit choosen.

2006-01-06 Thread jhasler
On line 580 of the ru.po you sent me for pppconfig is a '--' which »ÕÔÞÒáÚØå ½ØÚÞÛÐÙ ²ÐÛÕàìÕÒØç <[EMAIL PROTECTED]> tells me should be a '-' (the '--' somehow causes the program to exit). Does this make sense to you? -- John Hasler -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject

Bug#287210: bc: Interrupt should reset the input line

2005-01-16 Thread jhasler
> That would be fine with me, but I wonder: can the current behaviour > really be considered a feature? Is there any reason to believe it would > create problems to implement the change? I can't think of any reason the change would break anything, but people use these old command-line programs in