Your message dated Sat, 23 Apr 2005 08:17:41 +0200
with message-id [EMAIL PROTECTED]
and subject line privoxy: Images broken on allofmp3.com
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 message dated Sat, 23 Apr 2005 08:47:45 +0200
with message-id [EMAIL PROTECTED]
and subject line 0.20 available
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 responsibility to
Your message dated Sat, 23 Apr 2005 15:47:21 +0900
with message-id [EMAIL PROTECTED]
and subject line Bug#303832: scmail: can't fulfill the build dependencies in
sarge
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
Your message dated Sat, 23 Apr 2005 03:29:46 -0400
with message-id [EMAIL PROTECTED]
and subject line Close: Bug#305963: Acknowledgement ('man lspci' typo:
unrealiable)
has caused the attached Bug report to be marked as done.
This means that you claim that the problem has been dealt with.
If
Your message dated Sat, 23 Apr 2005 09:32:26 +0200
with message-id [EMAIL PROTECTED]
and subject line Bug#305941: ppp broken on Sarge
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
Your message dated Sat, 23 Apr 2005 03:33:22 -0400
with message-id [EMAIL PROTECTED]
and subject line Bug#305955: fixed in ratpoison 1.3.0-6
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 message dated Sat, 23 Apr 2005 10:11:45 +0200
with message-id [EMAIL PROTECTED]
and subject line Bug#305908: courier: FTBFS on sarge: Can't satisfy build
dependency on libsasl-dev
has caused the attached Bug report to be marked as done.
This means that you claim that the problem has been
Your message dated Sat, 23 Apr 2005 11:18:57 +0200
with message-id [EMAIL PROTECTED]
and subject line Bug#305784: rsync-option: fails
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
Your message dated Sat, 23 Apr 2005 05:47:05 -0400
with message-id [EMAIL PROTECTED]
and subject line Bug#293234: fixed in dhttpd 1.02a-14
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 message dated Sat, 23 Apr 2005 12:30:57 +0200
with message-id [EMAIL PROTECTED]
and subject line Bug#305972: Acknowledgement (@monthly executes every day)
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
Your message dated Sat, 23 Apr 2005 13:06:21 +0200
with message-id [EMAIL PROTECTED]
and subject line Bug#305931: base-installer: need noapic on K7S41-GX
motherboards
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
Your message dated Sat, 23 Apr 2005 07:46:38 -0400
with message-id [EMAIL PROTECTED]
and subject line Bug#305979: /bin/ls: ls with * does not find correct files
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
Your message dated Sat, 23 Apr 2005 08:17:18 -0400
with message-id [EMAIL PROTECTED]
and subject line Bug#291356: fixed in gnustep-back 0.9.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
Your message dated Sat, 23 Apr 2005 15:03:58 +0200
with message-id [EMAIL PROTECTED]
and subject line Fixed in wwwconfig-common.
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
Your message dated Sat, 23 Apr 2005 15:02:40 +0200
with message-id [EMAIL PROTECTED]
and subject line php4 issue and a long time ago.
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
Your message dated Sat, 23 Apr 2005 15:07:31 +0200
with message-id [EMAIL PROTECTED]
and subject line Very old horde2
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 responsibility to
Your message dated Sat, 23 Apr 2005 14:29:28 +0100
with message-id [EMAIL PROTECTED]
and subject line Closing Polipo crash bug report
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
Your message dated Sat, 23 Apr 2005 09:17:32 -0400
with message-id [EMAIL PROTECTED]
and subject line Bug#305436: fixed in horde2 2.2.8-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
Your message dated Sat, 23 Apr 2005 10:02:30 -0400
with message-id [EMAIL PROTECTED]
and subject line Bug#298321: fixed in sn 0.3.8-4
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
Your message dated Sat, 23 Apr 2005 16:15:22 +0200
with message-id [EMAIL PROTECTED]
and subject line Bug#305948: Allow pmount to name device using hal's description
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
Your message dated Sat, 23 Apr 2005 17:21:54 +0200
with message-id [EMAIL PROTECTED]
and subject line (no subject)
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 responsibility to
Your message dated Sat, 23 Apr 2005 17:27:01 +0200
with message-id [EMAIL PROTECTED]
and subject line (no subject)
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 responsibility to
Your message dated Sat, 23 Apr 2005 17:35:26 +0200
with message-id [EMAIL PROTECTED]
and subject line (no subject)
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 responsibility to
Your message dated Sat, 23 Apr 2005 17:30:09 +0200
with message-id [EMAIL PROTECTED]
and subject line (no subject)
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 responsibility to
Your message dated Sat, 23 Apr 2005 17:32:40 +0200
with message-id [EMAIL PROTECTED]
and subject line (no subject)
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 responsibility to
Your message dated Sat, 23 Apr 2005 17:34:28 +0200
with message-id [EMAIL PROTECTED]
and subject line (no subject)
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 responsibility to
Your message dated Sat, 23 Apr 2005 11:32:33 -0400
with message-id [EMAIL PROTECTED]
and subject line Bug#290436: fixed in pspresent 1.2-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 message dated Sat, 23 Apr 2005 11:32:18 -0400
with message-id [EMAIL PROTECTED]
and subject line Bug#291222: fixed in bluefish 1.0-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
Your message dated Sat, 23 Apr 2005 11:32:20 -0400
with message-id [EMAIL PROTECTED]
and subject line Bug#299633: fixed in fakeroot 1.2.10
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 message dated Sat, 23 Apr 2005 16:57:17 +0100
with message-id [EMAIL PROTECTED]
and subject line Removed from Debian
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 responsibility
Your message dated Sat, 23 Apr 2005 16:57:17 +0100
with message-id [EMAIL PROTECTED]
and subject line Removed from Debian
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 responsibility
Your message dated Sat, 23 Apr 2005 16:57:17 +0100
with message-id [EMAIL PROTECTED]
and subject line Removed from Debian
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 responsibility
Your message dated Sat, 23 Apr 2005 17:46:06 +0200
with message-id [EMAIL PROTECTED]
and subject line This was a known php4 bug.
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
Your message dated Sat, 23 Apr 2005 16:57:17 +0100
with message-id [EMAIL PROTECTED]
and subject line Removed from Debian
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 responsibility
Your message dated Sat, 23 Apr 2005 16:53:04 +0100
with message-id [EMAIL PROTECTED]
and subject line removed
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 responsibility to reopen
Your message dated Sat, 23 Apr 2005 16:57:17 +0100
with message-id [EMAIL PROTECTED]
and subject line Removed from Debian
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 responsibility
Your message dated Sat, 23 Apr 2005 16:57:17 +0100
with message-id [EMAIL PROTECTED]
and subject line Removed from Debian
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 responsibility
Your message dated Sat, 23 Apr 2005 16:57:17 +0100
with message-id [EMAIL PROTECTED]
and subject line Removed from Debian
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 responsibility
Your message dated Sat, 23 Apr 2005 16:57:17 +0100
with message-id [EMAIL PROTECTED]
and subject line Removed from Debian
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 responsibility
Your message dated Sat, 23 Apr 2005 17:49:47 +0200
with message-id [EMAIL PROTECTED]
and subject line Filed against a old version of horde2.
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 message dated Sat, 23 Apr 2005 16:57:17 +0100
with message-id [EMAIL PROTECTED]
and subject line Removed from Debian
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 responsibility
Your message dated Sat, 23 Apr 2005 17:52:21 +0200
with message-id [EMAIL PROTECTED]
and subject line This must have been fixed.
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
Your message dated Sat, 23 Apr 2005 16:57:17 +0100
with message-id [EMAIL PROTECTED]
and subject line Removed from Debian
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 responsibility
Your message dated Sat, 23 Apr 2005 16:57:17 +0100
with message-id [EMAIL PROTECTED]
and subject line Removed from Debian
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 responsibility
Your message dated Sat, 23 Apr 2005 17:46:06 +0200
with message-id [EMAIL PROTECTED]
and subject line This was a known php4 bug.
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
Your message dated Sat, 23 Apr 2005 16:57:17 +0100
with message-id [EMAIL PROTECTED]
and subject line Removed from Debian
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 responsibility
Your message dated Sat, 23 Apr 2005 16:57:17 +0100
with message-id [EMAIL PROTECTED]
and subject line Removed from Debian
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 responsibility
Your message dated Sat, 23 Apr 2005 16:57:17 +0100
with message-id [EMAIL PROTECTED]
and subject line Removed from Debian
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 responsibility
Your message dated Sat, 23 Apr 2005 18:01:49 +0200
with message-id [EMAIL PROTECTED]
and subject line merge
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 responsibility to reopen the
Your message dated Sat, 23 Apr 2005 18:00:08 +0200
with message-id [EMAIL PROTECTED]
and subject line Bug#305923: rsnapshot does not handle new rsync '--timeout'
option
has caused the attached Bug report to be marked as done.
This means that you claim that the problem has been dealt with.
If
Your message dated Sat, 23 Apr 2005 18:01:49 +0200
with message-id [EMAIL PROTECTED]
and subject line merge
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 responsibility to reopen the
Your message dated Sat, 23 Apr 2005 12:17:19 -0400
with message-id [EMAIL PROTECTED]
and subject line Bug#305782: fixed in randomize-lines 0.2.4
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
Your message dated Sat, 23 Apr 2005 11:30:08 -0500
with message-id [EMAIL PROTECTED]
and subject line Bug#306004: cron: CAN-2005-1038
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
Your message dated Sat, 23 Apr 2005 21:22:17 +0400
with message-id [EMAIL PROTECTED]
and subject line 2.6.3 is there
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 responsibility to
Your message dated Sat, 23 Apr 2005 19:18:02 +0200
with message-id [EMAIL PROTECTED]
and subject line Pear log problem fixed.
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
Your message dated Sat, 23 Apr 2005 19:22:21 +0200
with message-id [EMAIL PROTECTED]
and subject line php-cgi problem.
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 responsibility to
Your message dated Sat, 23 Apr 2005 20:11:22 +0200
with message-id [EMAIL PROTECTED]
and subject line (no subject)
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 responsibility to
Your message dated Sat, 23 Apr 2005 20:12:12 +0200
with message-id [EMAIL PROTECTED]
and subject line (no subject)
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 responsibility to
Your message dated Sat, 23 Apr 2005 20:08:21 +0200
with message-id [EMAIL PROTECTED]
and subject line (no subject)
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 responsibility to
Your message dated Sat, 23 Apr 2005 14:17:08 -0400
with message-id [EMAIL PROTECTED]
and subject line Bug#302915: fixed in auctex 11.55-2
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
Your message dated Sat, 23 Apr 2005 14:17:33 -0400
with message-id [EMAIL PROTECTED]
and subject line Bug#298399: fixed in flyspray 0.9.7-2
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 message dated Sat, 23 Apr 2005 14:17:33 -0400
with message-id [EMAIL PROTECTED]
and subject line Bug#297704: fixed in flyspray 0.9.7-2
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 message dated Sat, 23 Apr 2005 20:13:57 +0200
with message-id [EMAIL PROTECTED]
and subject line (no subject)
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 responsibility to
Your message dated Sat, 23 Apr 2005 14:17:33 -0400
with message-id [EMAIL PROTECTED]
and subject line Bug#297704: fixed in flyspray 0.9.7-2
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 message dated Sat, 23 Apr 2005 14:17:08 -0400
with message-id [EMAIL PROTECTED]
and subject line Bug#293139: fixed in auctex 11.55-2
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
Your message dated Sat, 23 Apr 2005 14:17:33 -0400
with message-id [EMAIL PROTECTED]
and subject line Bug#300608: fixed in flyspray 0.9.7-2
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 message dated Sat, 23 Apr 2005 14:17:08 -0400
with message-id [EMAIL PROTECTED]
and subject line Bug#302916: fixed in auctex 11.55-2
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
Your message dated Sat, 23 Apr 2005 14:47:07 -0400
with message-id [EMAIL PROTECTED]
and subject line Bug#302578: fixed in dict-jargon 4.4.4-6
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 message dated Sat, 23 Apr 2005 14:47:07 -0400
with message-id [EMAIL PROTECTED]
and subject line Bug#296957: fixed in dict-jargon 4.4.4-6
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 message dated Sat, 23 Apr 2005 14:47:07 -0400
with message-id [EMAIL PROTECTED]
and subject line Bug#274689: fixed in dict-jargon 4.4.4-6
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 message dated Sat, 23 Apr 2005 14:47:12 -0400
with message-id [EMAIL PROTECTED]
and subject line Bug#278293: fixed in pdumpfs 1.3-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
Your message dated Sat, 23 Apr 2005 22:02:22 +0200
with message-id [EMAIL PROTECTED]
and subject line Fixed in vnc4
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 responsibility to
Your message dated Sat, 23 Apr 2005 15:56:54 -0400
with message-id [EMAIL PROTECTED]
and subject line Bug#305946: fixed
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 responsibility to
Your message dated Sat, 23 Apr 2005 13:24:51 -0700
with message-id [EMAIL PROTECTED]
and subject line Bug#306010: php error when trying to restart apache
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
Your message dated Sat, 23 Apr 2005 16:17:05 -0400
with message-id [EMAIL PROTECTED]
and subject line Bug#288442: fixed in rpy 0.4.1-4
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
Your message dated Sat, 23 Apr 2005 22:22:16 +0200
with message-id [EMAIL PROTECTED]
and subject line owsadm.exe is not a part of this package.
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
Your message dated Sat, 23 Apr 2005 22:38:50 +0200
with message-id [EMAIL PROTECTED]
and subject line Use the recommended package.
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
Your message dated Sat, 23 Apr 2005 17:02:14 -0400
with message-id [EMAIL PROTECTED]
and subject line Bug#304897: fixed in mysql-dfsg-4.1 4.1.11-2
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
Your message dated Sat, 23 Apr 2005 17:02:14 -0400
with message-id [EMAIL PROTECTED]
and subject line Bug#301741: fixed in mysql-dfsg-4.1 4.1.11-2
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
Your message dated Sat, 23 Apr 2005 07:51:30 +0800
with message-id [EMAIL PROTECTED]
and subject line html2text: just reads in the file and poops out
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
Your message dated Sat, 23 Apr 2005 18:17:49 -0400
with message-id [EMAIL PROTECTED]
and subject line old bugs already fixed
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
Your message dated Sat, 23 Apr 2005 18:17:49 -0400
with message-id [EMAIL PROTECTED]
and subject line old bugs already fixed
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
Your message dated Sat, 23 Apr 2005 18:17:49 -0400
with message-id [EMAIL PROTECTED]
and subject line old bugs already fixed
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
Your message dated Sat, 23 Apr 2005 18:17:49 -0400
with message-id [EMAIL PROTECTED]
and subject line old bugs already fixed
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
Your message dated Sat, 23 Apr 2005 18:17:49 -0400
with message-id [EMAIL PROTECTED]
and subject line old bugs already fixed
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
Your message dated Sat, 23 Apr 2005 16:22:45 -0700
with message-id [EMAIL PROTECTED]
and subject line default x-terminal-emulator options no longer contain -sb
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
Your message dated Sun, 24 Apr 2005 02:42:11 +0300
with message-id [EMAIL PROTECTED]
and subject line Old bug
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 responsibility to reopen
Your message dated Sat, 23 Apr 2005 20:18:24 -0400
with message-id [EMAIL PROTECTED]
and subject line Bug#305999: fixed in mysql-query-browser 1.1.6-2
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
Your message dated Sat, 23 Apr 2005 20:18:25 -0400
with message-id [EMAIL PROTECTED]
and subject line Bug#305048: fixed in oinkmaster 1.2-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 message dated Sat, 23 Apr 2005 20:06:37 -0400
with message-id [EMAIL PROTECTED]
and subject line Bug#164391: fixed in djvulibre 3.5.14-4
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 message dated Sat, 23 Apr 2005 20:17:51 -0400
with message-id [EMAIL PROTECTED]
and subject line Bug#294331: fixed in kdenetwork 4:3.3.2-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
Processing commands for [EMAIL PROTECTED]:
close 305753
Bug#305753: general: 38 packages still use Origin: debian
'close' is deprecated; see http://www.debian.org/Bugs/Developer#closing.
Bug closed, send any further explanations to Dan Jacobson [EMAIL PROTECTED]
End of message, stopping
Your message dated Sat, 23 Apr 2005 20:17:51 -0400
with message-id [EMAIL PROTECTED]
and subject line Bug#305942: fixed in kdenetwork 4:3.3.2-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
Your message dated Sat, 23 Apr 2005 22:58:35 -0300
with message-id [EMAIL PROTECTED]
and subject line Closing old bug
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 responsibility to
Your message dated Sat, 23 Apr 2005 22:47:42 -0400
with message-id [EMAIL PROTECTED]
and subject line Bug#305896: fixed in pyblosxom 1.2-2
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 message dated Sun, 24 Apr 2005 00:02:23 -0400
with message-id [EMAIL PROTECTED]
and subject line Bug#302785: fixed in discover1-data 1.2005.04.23
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
Your message dated Sun, 24 Apr 2005 00:02:23 -0400
with message-id [EMAIL PROTECTED]
and subject line Bug#274039: fixed in discover1-data 1.2005.04.23
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
Your message dated Sun, 24 Apr 2005 00:02:23 -0400
with message-id [EMAIL PROTECTED]
and subject line Bug#299824: fixed in discover1-data 1.2005.04.23
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
Your message dated Sun, 24 Apr 2005 00:02:23 -0400
with message-id [EMAIL PROTECTED]
and subject line Bug#299824: fixed in discover1-data 1.2005.04.23
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
Your message dated Sun, 24 Apr 2005 00:02:23 -0400
with message-id [EMAIL PROTECTED]
and subject line Bug#283399: fixed in discover1-data 1.2005.04.23
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
100 matches
Mail list logo