Your message dated Sat, 09 Jun 2007 07:02:03 +
with message-id <[EMAIL PROTECTED]>
and subject line Bug#427809: fixed in shntool 3.0.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 yo
Your message dated Sat, 09 Jun 2007 10:10:46 +0200
with message-id <[EMAIL PROTECTED]>
and subject line Fixed in dmz-cursor-theme
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 responsi
Your message dated Sat, 09 Jun 2007 10:10:46 +0200
with message-id <[EMAIL PROTECTED]>
and subject line Fixed in dmz-cursor-theme
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 responsi
Your message dated Sat, 09 Jun 2007 08:47:23 +
with message-id <[EMAIL PROTECTED]>
and subject line Bug#416190: fixed in iceweasel 2.0.0.4-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 no
Your message dated Sat, 09 Jun 2007 08:47:23 +
with message-id <[EMAIL PROTECTED]>
and subject line Bug#420051: fixed in iceweasel 2.0.0.4-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 no
Your message dated Sat, 09 Jun 2007 08:47:23 +
with message-id <[EMAIL PROTECTED]>
and subject line Bug#409074: fixed in iceweasel 2.0.0.4-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 no
Your message dated Sat, 09 Jun 2007 08:47:23 +
with message-id <[EMAIL PROTECTED]>
and subject line Bug#427785: fixed in iceweasel 2.0.0.4-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 no
Your message dated Sat, 09 Jun 2007 09:32:05 +
with message-id <[EMAIL PROTECTED]>
and subject line Bug#395268: fixed in libmail-mboxparser-perl 0.55-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 ca
Your message dated Sat, 09 Jun 2007 11:17:03 +
with message-id <[EMAIL PROTECTED]>
and subject line Bug#415752: fixed in nagios2 2.9-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, 09 Jun 2007 11:17:03 +
with message-id <[EMAIL PROTECTED]>
and subject line Bug#423639: fixed in nagios2 2.9-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, 09 Jun 2007 11:17:03 +
with message-id <[EMAIL PROTECTED]>
and subject line Bug#414762: fixed in nagios2 2.9-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, 09 Jun 2007 11:17:03 +
with message-id <[EMAIL PROTECTED]>
and subject line Bug#413122: fixed in nagios2 2.9-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, 09 Jun 2007 11:17:03 +
with message-id <[EMAIL PROTECTED]>
and subject line Bug#416763: fixed in nagios2 2.9-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, 09 Jun 2007 11:17:03 +
with message-id <[EMAIL PROTECTED]>
and subject line Bug#414050: fixed in nagios2 2.9-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, 09 Jun 2007 11:17:03 +
with message-id <[EMAIL PROTECTED]>
and subject line Bug#414652: fixed in nagios2 2.9-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, 09 Jun 2007 11:17:03 +
with message-id <[EMAIL PROTECTED]>
and subject line Bug#412980: fixed in nagios2 2.9-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, 09 Jun 2007 11:17:03 +
with message-id <[EMAIL PROTECTED]>
and subject line Bug#414647: fixed in nagios2 2.9-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, 09 Jun 2007 11:17:03 +
with message-id <[EMAIL PROTECTED]>
and subject line Bug#397289: fixed in nagios2 2.9-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, 09 Jun 2007 11:47:02 +
with message-id <[EMAIL PROTECTED]>
and subject line Bug#386976: fixed in dropbear 0.49-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 yo
Your message dated Sat, 09 Jun 2007 12:02:02 +
with message-id <[EMAIL PROTECTED]>
and subject line Bug#428096: fixed in liquidsoap 0.3.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 now
Your message dated Sat, 9 Jun 2007 14:24: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 reop
Your message dated Sat, 09 Jun 2007 12:47:10 +
with message-id <[EMAIL PROTECTED]>
and subject line Bug#427594: fixed in wmwave 0.4-8
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, 09 Jun 2007 12:47:03 +
with message-id <[EMAIL PROTECTED]>
and subject line Bug#427405: fixed in fetchmail 6.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 message dated Sat, 09 Jun 2007 12:47:10 +
with message-id <[EMAIL PROTECTED]>
and subject line Bug#406947: fixed in wmwave 0.4-8
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, 09 Jun 2007 12:47:10 +
with message-id <[EMAIL PROTECTED]>
and subject line Bug#421405: fixed in wmwave 0.4-8
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, 09 Jun 2007 12:47:10 +
with message-id <[EMAIL PROTECTED]>
and subject line Bug#225279: fixed in wmwave 0.4-8
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, 9 Jun 2007 11:09:14 -0300
with message-id <[EMAIL PROTECTED]>
and subject line Please refer to http://linux-ata.org/shutdown.html
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, 09 Jun 2007 15:03:18 +
with message-id <[EMAIL PROTECTED]>
and subject line Bug#426874: fixed in libept 0.5
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 re
Your message dated Sat, 09 Jun 2007 15:17:21 +
with message-id <[EMAIL PROTECTED]>
and subject line Bug#427899: fixed in update-manager 0.42.2ubuntu22-12
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, 9 Jun 2007 17:24:44 +0200
with message-id <[EMAIL PROTECTED]>
and subject line grub-splashimages: breaks/fails when /boot is on a separate
partition
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, 9 Jun 2007 17:24:44 +0200
with message-id <[EMAIL PROTECTED]>
and subject line grub-splashimages: breaks/fails when /boot is on a separate
partition
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, 9 Jun 2007 17:36:04 +0200
with message-id <[EMAIL PROTECTED]>
and subject line Bug#427882: Suggests nonexistent xmorph-example
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, 9 Jun 2007 17:57:15 +0200
with message-id <[EMAIL PROTECTED]>
and subject line Etch is released
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, 09 Jun 2007 16:17:02 +
with message-id <[EMAIL PROTECTED]>
and subject line Bug#419231: fixed in svn-buildpackage 0.6.21
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
Your message dated Sat, 09 Jun 2007 16:32:02 +
with message-id <[EMAIL PROTECTED]>
and subject line Bug#285321: fixed in grub-splashimages 1.2.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 is not the case it i
Your message dated Sat, 9 Jun 2007 22:04:04 +0530
with message-id <[EMAIL PROTECTED]>
and subject line Compiling IT++ with GCC 4.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 your respons
Your message dated Sat, 9 Jun 2007 18:33:52 +0200
with message-id <[EMAIL PROTECTED]>
and subject line Bug#428139: [amd64][etch][4.0r0] success: Sun X2200 server
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, 9 Jun 2007 19:08:23 +0200
with message-id <[EMAIL PROTECTED]>
and subject line Bug#428171: Broken dependencies / wrong versions in stable
repository
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, 9 Jun 2007 19:30:51 +0200
with message-id <[EMAIL PROTECTED]>
and subject line 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 reopen the
Your message dated Sat, 9 Jun 2007 19:49:49 +0200
with message-id <[EMAIL PROTECTED]>
and subject line Bug#428184: libgphoto2-2:
/etc/udev/rules.d/025_libgphoto2.rules is not recreated upon reinstallation
has caused the attached Bug report to be marked as done.
This means that you claim that the
Your message dated Sat, 09 Jun 2007 17:47:03 +
with message-id <[EMAIL PROTECTED]>
and subject line Bug#426444: fixed in talloc 1.0.1-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 you
Your message dated Sat, 09 Jun 2007 18:17:15 +
with message-id <[EMAIL PROTECTED]>
and subject line Bug#393897: fixed in gcc-4.2 4.2-20070609-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 c
Your message dated Sat, 09 Jun 2007 18:17:15 +
with message-id <[EMAIL PROTECTED]>
and subject line Bug#426905: fixed in gcc-4.2 4.2-20070609-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 c
Your message dated Sat, 09 Jun 2007 18:17:15 +
with message-id <[EMAIL PROTECTED]>
and subject line Bug#424855: fixed in gcc-4.2 4.2-20070609-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 c
Your message dated Sat, 09 Jun 2007 18:17:15 +
with message-id <[EMAIL PROTECTED]>
and subject line Bug#424693: fixed in gcc-4.2 4.2-20070609-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 c
Your message dated Sat, 09 Jun 2007 18:17:15 +
with message-id <[EMAIL PROTECTED]>
and subject line Bug#419511: fixed in gcc-4.2 4.2-20070609-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 c
Your message dated Sat, 09 Jun 2007 19:17:02 +
with message-id <[EMAIL PROTECTED]>
and subject line Bug#422513: fixed in alsa-lib 1.0.14-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, 09 Jun 2007 19:17:02 +
with message-id <[EMAIL PROTECTED]>
and subject line Bug#424310: fixed in alsa-lib 1.0.14-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, 09 Jun 2007 19:17:02 +
with message-id <[EMAIL PROTECTED]>
and subject line Bug#408766: fixed in alsa-lib 1.0.14-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, 09 Jun 2007 19:17:02 +
with message-id <[EMAIL PROTECTED]>
and subject line Bug#420999: fixed in alsa-lib 1.0.14-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, 09 Jun 2007 19:32:02 +
with message-id <[EMAIL PROTECTED]>
and subject line Bug#408770: fixed in alsa-oss 1.0.14-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, 09 Jun 2007 19:32:02 +
with message-id <[EMAIL PROTECTED]>
and subject line Bug#419099: fixed in alsa-oss 1.0.14-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, 09 Jun 2007 19:32:02 +
with message-id <[EMAIL PROTECTED]>
and subject line Bug#364730: fixed in alsa-oss 1.0.14-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, 09 Jun 2007 19:47:02 +
with message-id <[EMAIL PROTECTED]>
and subject line Bug#425430: fixed in alsa-utils 1.0.14-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 no
Your message dated Sat, 09 Jun 2007 19:47:02 +
with message-id <[EMAIL PROTECTED]>
and subject line Bug#408773: fixed in alsa-utils 1.0.14-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 no
Your message dated Sat, 09 Jun 2007 19:52:17 +
with message-id <[EMAIL PROTECTED]>
and subject line Bug#426077: fixed in mpop 1.0.5-1etch1
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, 09 Jun 2007 19:52:20 +
with message-id <[EMAIL PROTECTED]>
and subject line Bug#418850: fixed in cdrom-detect 1.20etch1
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, 09 Jun 2007 19:52:22 +
with message-id <[EMAIL PROTECTED]>
and subject line Bug#356671: fixed in lifelines 3.0.50-2etch1
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
Your message dated Sat, 09 Jun 2007 19:52:22 +
with message-id <[EMAIL PROTECTED]>
and subject line Bug#405500: fixed in lifelines 3.0.50-2etch1
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
Your message dated Sat, 09 Jun 2007 19:52:15 +
with message-id <[EMAIL PROTECTED]>
and subject line Bug#422442: fixed in apt-setup 1:0.20etch1
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, 09 Jun 2007 19:52:22 +
with message-id <[EMAIL PROTECTED]>
and subject line Bug#356671: fixed in lifelines 3.0.50-2etch1
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
Your message dated Sat, 09 Jun 2007 19:52:22 +
with message-id <[EMAIL PROTECTED]>
and subject line Bug#418347: fixed in lifelines 3.0.50-2etch1
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
Your message dated Sat, 09 Jun 2007 19:52:21 +
with message-id <[EMAIL PROTECTED]>
and subject line Bug#421323: fixed in user-setup 1.11etch1
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 n
Your message dated Sat, 9 Jun 2007 21:09:56 +0100
with message-id <[EMAIL PROTECTED]>
and subject line This should have been fixed for quite a while
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
Your message dated Sat, 9 Jun 2007 21:32:49 +0100
with message-id <[EMAIL PROTECTED]>
and subject line Debtags uses the tags from the apt packages file by default
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, 09 Jun 2007 20:32:02 +
with message-id <[EMAIL PROTECTED]>
and subject line Bug#407428: fixed in alsa-plugins 1.0.14-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, 09 Jun 2007 20:32:03 +
with message-id <[EMAIL PROTECTED]>
and subject line Bug#422773: fixed in alsa-tools 1.0.14-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 no
Your message dated Sat, 09 Jun 2007 20:32:02 +
with message-id <[EMAIL PROTECTED]>
and subject line Bug#408771: fixed in alsa-plugins 1.0.14-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, 09 Jun 2007 20:32:03 +
with message-id <[EMAIL PROTECTED]>
and subject line Bug#408772: fixed in alsa-tools 1.0.14-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 no
Your message dated Sat, 9 Jun 2007 22:15:00 +0100
with message-id <[EMAIL PROTECTED]>
and subject line Seems to be fixed now
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 responsibilit
Your message dated Sat, 9 Jun 2007 22:22:25 +0100
with message-id <[EMAIL PROTECTED]>
and subject line I have forgotten to close the bug when I uploaded to unstable
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 n
Your message dated Sat, 09 Jun 2007 21:32:07 +
with message-id <[EMAIL PROTECTED]>
and subject line Bug#428101: fixed in qemu-launcher 1.7.4-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, 09 Jun 2007 21:32:04 +
with message-id <[EMAIL PROTECTED]>
and subject line Bug#417673: fixed in dosfstools 2.11-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 no
Your message dated Sat, 09 Jun 2007 21:32:07 +
with message-id <[EMAIL PROTECTED]>
and subject line Bug#399521: fixed in qemu-launcher 1.7.4-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, 09 Jun 2007 21:32:08 +
with message-id <[EMAIL PROTECTED]>
and subject line Bug#424028: fixed in sqlobject 0.9.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 message dated Sat, 9 Jun 2007 23:17:11 +0200
with message-id <[EMAIL PROTECTED]>
and subject line also fixed in current version
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 respo
Your message dated Sat, 09 Jun 2007 21:47:04 +
with message-id <[EMAIL PROTECTED]>
and subject line Bug#422443: fixed in sfront 0.91-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, 09 Jun 2007 22:02:03 +
with message-id <[EMAIL PROTECTED]>
and subject line Bug#395469: fixed in syslog-ocaml 1.3-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, 09 Jun 2007 23:02:03 +
with message-id <[EMAIL PROTECTED]>
and subject line Bug#421071: fixed in freefem 3.5.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 yo
Your message dated Sat, 9 Jun 2007 19:18:57 -0400
with message-id <[EMAIL PROTECTED]>
and subject line not a 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, 9 Jun 2007 19:24:22 -0400
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 reop
Your message dated Sat, 09 Jun 2007 23:32:03 +
with message-id <[EMAIL PROTECTED]>
and subject line Bug#417153: fixed in debtags 1.7.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 is not the case it is now your
Your message dated Sat, 09 Jun 2007 23:32:03 +
with message-id <[EMAIL PROTECTED]>
and subject line Bug#402852: fixed in debtags 1.7.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 is not the case it is now your
Your message dated Sat, 09 Jun 2007 23:32:03 +
with message-id <[EMAIL PROTECTED]>
and subject line Bug#402853: fixed in debtags 1.7.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 is not the case it is now your
Your message dated Sat, 09 Jun 2007 23:32:07 +
with message-id <[EMAIL PROTECTED]>
and subject line Bug#324443: fixed in python-xlib 0.13-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, 09 Jun 2007 23:32:03 +
with message-id <[EMAIL PROTECTED]>
and subject line Bug#423376: fixed in debtags 1.7.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 is not the case it is now your
Your message dated Sat, 09 Jun 2007 23:32:07 +
with message-id <[EMAIL PROTECTED]>
and subject line Bug#357507: fixed in python-xlib 0.13-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, 09 Jun 2007 23:32:04 +
with message-id <[EMAIL PROTECTED]>
and subject line Bug#417154: fixed in debtags-edit 1.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 y
Your message dated Sat, 09 Jun 2007 23:32:03 +
with message-id <[EMAIL PROTECTED]>
and subject line Bug#423377: fixed in debtags 1.7.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 is not the case it is now your
Your message dated Sat, 09 Jun 2007 23:32:03 +
with message-id <[EMAIL PROTECTED]>
and subject line Bug#397516: fixed in debtags 1.7.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 is not the case it is now your
Your message dated Sat, 09 Jun 2007 23:32:07 +
with message-id <[EMAIL PROTECTED]>
and subject line Bug#421594: fixed in python-xlib 0.13-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, 09 Jun 2007 23:32:03 +
with message-id <[EMAIL PROTECTED]>
and subject line Bug#423370: fixed in debtags 1.7.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 is not the case it is now your
Your message dated Sat, 09 Jun 2007 23:32:07 +
with message-id <[EMAIL PROTECTED]>
and subject line Bug#420774: fixed in python-xlib 0.13-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, 09 Jun 2007 23:32:03 +
with message-id <[EMAIL PROTECTED]>
and subject line Bug#399102: fixed in debtags 1.7.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 is not the case it is now your
Your message dated Sat, 09 Jun 2007 16:47:33 -0700
with message-id <[EMAIL PROTECTED]>
and subject line Icedove 2.0 now packaged
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 responsib
Your message dated Sat, 09 Jun 2007 16:47:33 -0700
with message-id <[EMAIL PROTECTED]>
and subject line Icedove 2.0 now packaged
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 responsib
Your message dated Sun, 10 Jun 2007 02:02:02 +
with message-id <[EMAIL PROTECTED]>
and subject line Bug#424012: fixed in scim-hangul 0.2.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 no
Your message dated Sun, 10 Jun 2007 03:47:02 +
with message-id <[EMAIL PROTECTED]>
and subject line Bug#428172: fixed in cpufrequtils 002-5
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, 10 Jun 2007 05:32:05 +
with message-id <[EMAIL PROTECTED]>
and subject line Bug#423280: fixed in dx 1:4.4.0-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 you
Your message dated Sun, 10 Jun 2007 05:32:05 +
with message-id <[EMAIL PROTECTED]>
and subject line Bug#423280: fixed in dx 1:4.4.0-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 you
1 - 100 of 112 matches
Mail list logo