Bug#55648: marked as done (date outputs wrong things about unknown timezones)

2007-04-10 Thread Debian Bug Tracking System
Your message dated Wed, 11 Apr 2007 02:47:04 + with message-id [EMAIL PROTECTED] and subject line Bug#119540: fixed in glibc 2.5-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 is now your

Bug#55648: marked as done (date outputs wrong things about unknown timezones)

2007-04-10 Thread Debian Bug Tracking System
Your message dated Wed, 11 Apr 2007 02:47:04 + with message-id [EMAIL PROTECTED] and subject line Bug#55648: fixed in glibc 2.5-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 is now your

Bug#55648: marked as done (date outputs wrong things about unknown timezones)

2007-04-10 Thread Debian Bug Tracking System
Your message dated Wed, 11 Apr 2007 02:47:04 + with message-id [EMAIL PROTECTED] and subject line Bug#269238: fixed in glibc 2.5-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 is now your

Bug#55648: marked as done (date outputs wrong things about unknown timezones)

2007-02-19 Thread Debian Bug Tracking System
Your message dated Mon, 19 Feb 2007 21:02:10 + with message-id [EMAIL PROTECTED] and subject line Bug#119540: fixed in glibc 2.5-0exp6 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

Bug#55648: marked as done (date outputs wrong things about unknown timezones)

2007-02-19 Thread Debian Bug Tracking System
Your message dated Mon, 19 Feb 2007 21:02:10 + with message-id [EMAIL PROTECTED] and subject line Bug#269238: fixed in glibc 2.5-0exp6 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

Bug#55648: marked as done (date outputs wrong things about unknown timezones)

2007-02-19 Thread Debian Bug Tracking System
Your message dated Mon, 19 Feb 2007 21:02:10 + with message-id [EMAIL PROTECTED] and subject line Bug#55648: fixed in glibc 2.5-0exp6 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

Bug#55648: marked as done (date outputs wrong things about unknown timezones)

2007-02-12 Thread Debian Bug Tracking System
Your message dated Mon, 12 Feb 2007 20:32:07 + with message-id [EMAIL PROTECTED] and subject line Bug#269238: fixed in glibc 2.5-0exp5 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

Bug#55648: marked as done (date outputs wrong things about unknown timezones)

2007-02-12 Thread Debian Bug Tracking System
Your message dated Mon, 12 Feb 2007 20:32:08 + with message-id [EMAIL PROTECTED] and subject line Bug#55648: fixed in glibc 2.5-0exp5 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

Bug#55648: marked as done (date outputs wrong things about unknown timezones)

2007-02-12 Thread Debian Bug Tracking System
Your message dated Mon, 12 Feb 2007 20:32:07 + with message-id [EMAIL PROTECTED] and subject line Bug#119540: fixed in glibc 2.5-0exp5 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

Bug#55648: marked as done (date outputs wrong things about unknown timezones)

2005-02-21 Thread Debian Bug Tracking System
Your message dated Mon, 21 Feb 2005 06:47:18 -0500 with message-id [EMAIL PROTECTED] and subject line Bug#269238: fixed in autofs 4.1.3+4.1.4beta2-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