Bug#127933: marked as done (microwindows: microwindows source is organized wrong)

Your message dated Thu, 21 Mar 2002 01:26:03 -0500 with message-id <[EMAIL PROTECTED]> and subject line Bug#127933: fixed in microwindows 0.89pre8-1 has caused the attached Bug report to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it i

Bug#121459: marked as done (microwindows doesn't build from source on powerpc (at least))

Your message dated Thu, 21 Mar 2002 01:26:03 -0500 with message-id <[EMAIL PROTECTED]> and subject line Bug#121459: fixed in microwindows 0.89pre8-1 has caused the attached Bug report to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it i

Bug#139238: patch for bugs - please apply

--- sgDb.c.orig Thu Mar 21 16:11:11 2002 +++ sgDb.c Thu Mar 21 16:15:09 2002 @@ -143,7 +143,8 @@ if(dbfile == NULL){ sgLogError("error update dbfile %s.db. file does not exists, use -C to create",file); } else { -update = (char *) sgMalloc(strlen(file) + 5); +

Bug#133881: please close bug - this corrected in release 1.2.0-0

subj 8-) -- Three o'clock in the afternoon is always just a little too late or a little too early for anything you want to do. -- Jean-Paul Sartre

Bug#108049: marked as done (Host should include 'nslookup' somewhere in it's package description)

Your message dated Thu, 21 Mar 2002 10:02:07 -0500 with message-id <[EMAIL PROTECTED]> and subject line Bug#108049: fixed in host 2331-3 has caused the attached Bug report to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now yo

Bug#109912: marked as done (host dumps core)

Your message dated Thu, 21 Mar 2002 10:02:08 -0500 with message-id <[EMAIL PROTECTED]> and subject line Bug#109912: fixed in host 2331-3 has caused the attached Bug report to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now yo

Bug#122126: marked as done (host: host -l museum. core dumps)

Your message dated Thu, 21 Mar 2002 10:02:08 -0500 with message-id <[EMAIL PROTECTED]> and subject line Bug#122126: fixed in host 2331-3 has caused the attached Bug report to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now yo

Bug#108438: marked as done (host -C broken)

Your message dated Thu, 21 Mar 2002 10:02:07 -0500 with message-id <[EMAIL PROTECTED]> and subject line Bug#108438: fixed in host 2331-3 has caused the attached Bug report to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now yo

Bug#130434: marked as done (host: Please explain which links it installs and the purpose of this tool)

Your message dated Thu, 21 Mar 2002 10:02:08 -0500 with message-id <[EMAIL PROTECTED]> and subject line Bug#130434: fixed in host 2331-3 has caused the attached Bug report to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now yo

Bug#97340: marked as done (host -l akamaitech.com gets segfault)

Your message dated Thu, 21 Mar 2002 10:02:08 -0500 with message-id <[EMAIL PROTECTED]> and subject line Bug#97340: fixed in host 2331-3 has caused the attached Bug report to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now you

Bug#88928: marked as done (host -H segfaults if nameserver doesn't allow AXFR)

Your message dated Thu, 21 Mar 2002 10:02:08 -0500 with message-id <[EMAIL PROTECTED]> and subject line Bug#88928: fixed in host 2331-3 has caused the attached Bug report to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now you

Bug#90174: marked as done (host segfaulted after a seemingly non-fatal error)

Your message dated Thu, 21 Mar 2002 10:02:08 -0500 with message-id <[EMAIL PROTECTED]> and subject line Bug#88928: fixed in host 2331-3 has caused the attached Bug report to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now you

Bug#95108: marked as done (Bad parsing of resolv.conf)

Your message dated Thu, 21 Mar 2002 16:44:36 +0100 with message-id <[EMAIL PROTECTED]> and subject line host: Parsing /etc/resolv.conf has caused the attached Bug report to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your res

Bug#95110: marked as done ([addendum]error in parsing /etc/resolv.conf or wrong manpage)

Your message dated Thu, 21 Mar 2002 16:44:36 +0100 with message-id <[EMAIL PROTECTED]> and subject line host: Parsing /etc/resolv.conf has caused the attached Bug report to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your res

Bug#133881: marked as done (squidguard: configuration.html in squidgauard incomplete download from site)

Your message dated Thu, 21 Mar 2002 11:56:59 -0600 with message-id <[EMAIL PROTECTED]> and subject line Bug#133881: please close bug - this corrected in release 1.2.0-0 has caused the attached Bug report to be marked as done. This means that you claim that the problem has been dealt with. If this