Your message dated Sat, 15 Oct 2005 22:12:08 -0700
with message-id <[EMAIL PROTECTED]>
and subject line gtkdiskfree: insecure temporary file creation
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, 15 Oct 2005 22:02:05 -0700
with message-id <[EMAIL PROTECTED]>
and subject line Bug#332987: fixed in gnomebaker 0.5.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 Sun, 16 Oct 2005 14:58:28 +1000
with message-id <[EMAIL PROTECTED]>
and subject line Bug#334023: perl: possible LKM Trojan infection
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 i
Your message dated Sat, 15 Oct 2005 21:02:09 -0700
with message-id <[EMAIL PROTECTED]>
and subject line Bug#332973: fixed in mercurial 0.7-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 yo
Your message dated Sat, 15 Oct 2005 19:47:06 -0700
with message-id <[EMAIL PROTECTED]>
and subject line Bug#331696: fixed in dar 2.2.3-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 r
Your message dated Sat, 15 Oct 2005 19:32:07 -0700
with message-id <[EMAIL PROTECTED]>
and subject line Bug#307884: fixed in speex 1.1.10-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 Sat, 15 Oct 2005 19:32:07 -0700
with message-id <[EMAIL PROTECTED]>
and subject line Bug#306159: fixed in speex 1.1.10-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 Sat, 15 Oct 2005 19:32:07 -0700
with message-id <[EMAIL PROTECTED]>
and subject line Bug#300968: fixed in speex 1.1.10-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 Sat, 15 Oct 2005 19:02:07 -0700
with message-id <[EMAIL PROTECTED]>
and subject line Bug#334033: fixed in kbear 2.1.1-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 case it is now you
Your message dated Sat, 15 Oct 2005 18:32:53 -0700
with message-id <[EMAIL PROTECTED]>
and subject line Bug#334163: fixed in mftrace 1.1.17-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 y
Your message dated Sat, 15 Oct 2005 17:16:31 -0700
with message-id <[EMAIL PROTECTED]>
and subject line Fixed in 0.3.5.1-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 responsibility
Your message dated Sat, 15 Oct 2005 17:16:31 -0700
with message-id <[EMAIL PROTECTED]>
and subject line Fixed in 0.3.5.1-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 responsibility
Your message dated Sat, 15 Oct 2005 17:16:31 -0700
with message-id <[EMAIL PROTECTED]>
and subject line Fixed in 0.3.5.1-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 responsibility
Your message dated Sat, 15 Oct 2005 17:16:31 -0700
with message-id <[EMAIL PROTECTED]>
and subject line Fixed in 0.3.5.1-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 responsibility
Your message dated Sat, 15 Oct 2005 17:16:31 -0700
with message-id <[EMAIL PROTECTED]>
and subject line Fixed in 0.3.5.1-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 responsibility
Your message dated Sat, 15 Oct 2005 17:16:31 -0700
with message-id <[EMAIL PROTECTED]>
and subject line Fixed in 0.3.5.1-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 responsibility
Your message dated Sat, 15 Oct 2005 17:16:31 -0700
with message-id <[EMAIL PROTECTED]>
and subject line Fixed in 0.3.5.1-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 responsibility
Your message dated Sat, 15 Oct 2005 17:16:31 -0700
with message-id <[EMAIL PROTECTED]>
and subject line Fixed in 0.3.5.1-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 responsibility
Your message dated Sat, 15 Oct 2005 17:16:31 -0700
with message-id <[EMAIL PROTECTED]>
and subject line Fixed in 0.3.5.1-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 responsibility
Your message dated Sat, 15 Oct 2005 17:16:31 -0700
with message-id <[EMAIL PROTECTED]>
and subject line Fixed in 0.3.5.1-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 responsibility
Your message dated Sat, 15 Oct 2005 17:16:31 -0700
with message-id <[EMAIL PROTECTED]>
and subject line Fixed in 0.3.5.1-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 responsibility
Your message dated Sat, 15 Oct 2005 17:16:31 -0700
with message-id <[EMAIL PROTECTED]>
and subject line Fixed in 0.3.5.1-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 responsibility
Your message dated Sat, 15 Oct 2005 17:16:31 -0700
with message-id <[EMAIL PROTECTED]>
and subject line Fixed in 0.3.5.1-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 responsibility
Your message dated Sat, 15 Oct 2005 17:16:31 -0700
with message-id <[EMAIL PROTECTED]>
and subject line Fixed in 0.3.5.1-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 responsibility
Your message dated Sat, 15 Oct 2005 16:43:54 -0700
with message-id <[EMAIL PROTECTED]>
and subject line Bug#333971: fixed in vdk2 2.4.0-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
t kit)
Closes: 322624 326875 329893 331216 333137
Changes:
gcc-3.4 (3.4.4-9) unstable; urgency=low
.
* Updated to gcc-3.4 CVS 20051015.
* Update hurd-changes.dpatch (Michael Banck). Closes: #322624.
* Add support for the ppc64 architecture (Andreas Jochens).
Closes: #326875.
* Fix
tion for the GNU Fortran compiler (g77)
gcc-3.4- The GNU C compiler
gcc-3.4-base - The GNU Compiler Collection (base package)
gcc-3.4-doc - Documentation for the GNU compilers (gcc, gobjc, g++)
gnat-3.4 - The GNU Ada compiler
gnat-3.4-doc - Documentation for the GNU Ada compiler (gnat)
Your message dated Sat, 15 Oct 2005 16:39:34 -0700
with message-id <[EMAIL PROTECTED]>
and subject line Bug#333949: fixed in orpheus 1.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
64bit)
libg2c0- Runtime library for GNU Fortran 77 applications
libg2c0-dev - GNU Fortran 77 library development
libgnat-3.4 - Runtime library for GNU Ada applications
libstdc++6-dbg - The GNU Standard C++ Library v3 (debugging files)
libstdc++6-dev - The GNU Standard C++ Library v3 (development
piler
gpc-2.1-3.4 - The GNU Pascal compiler
gpc-2.1-3.4-doc - Documentation for the GNU Pascal compiler (gpc)
lib64g2c0 - Runtime library for GNU Fortran 77 applications (64bit)
libg2c0- Runtime library for GNU Fortran 77 applications
libg2c0-dev - GNU Fortran 77 library developm
libstdc++6-pic - The GNU Standard C++ Library v3 (shared library subset kit)
Closes: 322624 326875 329893 331216 333137
Changes:
gcc-3.4 (3.4.4-9) unstable; urgency=low
.
* Updated to gcc-3.4 CVS 20051015.
* Update hurd-changes.dpatch (Michael Banck). Closes: #322624.
* Add support for t
Your message dated Sat, 15 Oct 2005 16:43:54 -0700
with message-id <[EMAIL PROTECTED]>
and subject line Bug#294437: fixed in vdk2 2.4.0-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
Your message dated Sat, 15 Oct 2005 16:42:26 -0700
with message-id <[EMAIL PROTECTED]>
and subject line Bug#272295: fixed in lucene 1.4.3-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 you
Your message dated Sat, 15 Oct 2005 16:43:54 -0700
with message-id <[EMAIL PROTECTED]>
and subject line Bug#262091: fixed in vdk2 2.4.0-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
Your message dated Sat, 15 Oct 2005 16:05:06 -0700
with message-id <[EMAIL PROTECTED]>
and subject line Bug#333152: fixed in ruby-v4l 0.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 y
Your message dated Sat, 15 Oct 2005 15:41:06 -0700
with message-id <[EMAIL PROTECTED]>
and subject line Bug#333230: fixed in bsdtar 1.02.034-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, 15 Oct 2005 15:38:54 -0700
with message-id <[EMAIL PROTECTED]>
and subject line Bug#333222: fixed in libarchive 1.02.034-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, 15 Oct 2005 15:27:25 -0700
with message-id <[EMAIL PROTECTED]>
and subject line Bug#331636: fixed in score-reading-trainer 0.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 cas
Your message dated Sat, 15 Oct 2005 15:17:10 -0700
with message-id <[EMAIL PROTECTED]>
and subject line Bug#332961: fixed in nvram-wakeup 0.97-9
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, 15 Oct 2005 15:17:10 -0700
with message-id <[EMAIL PROTECTED]>
and subject line Bug#332354: fixed in nvram-wakeup 0.97-9
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, 15 Oct 2005 15:17:10 -0700
with message-id <[EMAIL PROTECTED]>
and subject line Bug#318191: fixed in nvram-wakeup 0.97-9
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, 15 Oct 2005 15:06:15 -0700
with message-id <[EMAIL PROTECTED]>
and subject line Bug#332641: fixed in gspot 0.1-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 r
Your message dated Sat, 15 Oct 2005 14:59:03 -0700
with message-id <[EMAIL PROTECTED]>
and subject line Bug#317047: fixed in gnome-python-extras 2.10.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
Your message dated Sat, 15 Oct 2005 14:59:03 -0700
with message-id <[EMAIL PROTECTED]>
and subject line Bug#327420: fixed in gnome-python-extras 2.10.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
Your message dated Sat, 15 Oct 2005 14:56:24 -0700
with message-id <[EMAIL PROTECTED]>
and subject line Bug#332623: fixed in aylet 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 now your r
Your message dated Sat, 15 Oct 2005 14:59:03 -0700
with message-id <[EMAIL PROTECTED]>
and subject line Bug#327420: fixed in gnome-python-extras 2.10.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
Your message dated Sat, 15 Oct 2005 14:47:08 -0700
with message-id <[EMAIL PROTECTED]>
and subject line Bug#323499: fixed in gaim 1:1.5.0+1.5.1cvs20051015-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, 15 Oct 2005 14:47:08 -0700
with message-id <[EMAIL PROTECTED]>
and subject line Bug#267180: fixed in gaim 1:1.5.0+1.5.1cvs20051015-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, 15 Oct 2005 23:41:39 +0200
with message-id <[EMAIL PROTECTED]>
and subject line fixed in 0.3.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 responsibility to r
Your message dated Sat, 15 Oct 2005 14:32:10 -0700
with message-id <[EMAIL PROTECTED]>
and subject line Bug#328659: fixed in mondo 2.04-7
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, 15 Oct 2005 14:32:10 -0700
with message-id <[EMAIL PROTECTED]>
and subject line Bug#328640: fixed in mondo 2.04-7
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, 15 Oct 2005 14:30:34 -0700
with message-id <[EMAIL PROTECTED]>
and subject line Bug#324808: fixed in scim-pinyin 0.5.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 no
Your message dated Sat, 15 Oct 2005 14:31:51 -0700
with message-id <[EMAIL PROTECTED]>
and subject line Bug#330010: fixed in libjson-perl 1.00-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, 15 Oct 2005 14:32:08 -0700
with message-id <[EMAIL PROTECTED]>
and subject line Bug#323809: fixed in keynote 2.3-11
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, 15 Oct 2005 14:30:34 -0700
with message-id <[EMAIL PROTECTED]>
and subject line Bug#324268: fixed in scim-pinyin 0.5.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 no
Your message dated Sat, 15 Oct 2005 14:30:34 -0700
with message-id <[EMAIL PROTECTED]>
and subject line Bug#324268: fixed in scim-pinyin 0.5.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 no
Your message dated Sat, 15 Oct 2005 14:30:34 -0700
with message-id <[EMAIL PROTECTED]>
and subject line Bug#297975: fixed in scim-pinyin 0.5.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 no
Your message dated Sat, 15 Oct 2005 14:17:11 -0700
with message-id <[EMAIL PROTECTED]>
and subject line Bug#329246: fixed in mindi 1.04-7
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, 15 Oct 2005 14:17:13 -0700
with message-id <[EMAIL PROTECTED]>
and subject line Bug#332025: fixed in mindi-partimagehack 0.6.2-7
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, 15 Oct 2005 14:17:11 -0700
with message-id <[EMAIL PROTECTED]>
and subject line Bug#324302: fixed in mindi 1.04-7
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
Processing commands for [EMAIL PROTECTED]:
> close 315451
Bug#315451: laptop-mode-tools: ext3,ext2 not recognized as ext3
'close' is deprecated; see http://www.debian.org/Bugs/Developer#closing.
Bug closed, send any further explanations to Dan Christensen <[EMAIL PROTECTED]>
> thanks
Stopping pro
Your message dated Sat, 15 Oct 2005 13:32:14 -0700
with message-id <[EMAIL PROTECTED]>
and subject line Bug#331430: fixed in emacs-goodies-el 25.1-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
Your message dated Sat, 15 Oct 2005 13:32:14 -0700
with message-id <[EMAIL PROTECTED]>
and subject line Bug#331421: fixed in emacs-goodies-el 25.1-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
Your message dated Sat, 15 Oct 2005 13:32:14 -0700
with message-id <[EMAIL PROTECTED]>
and subject line Bug#331234: fixed in emacs-goodies-el 25.1-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
Your message dated Sat, 15 Oct 2005 13:32:14 -0700
with message-id <[EMAIL PROTECTED]>
and subject line Bug#331114: fixed in emacs-goodies-el 25.1-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
Your message dated Sat, 15 Oct 2005 13:32:14 -0700
with message-id <[EMAIL PROTECTED]>
and subject line Bug#329883: fixed in emacs-goodies-el 25.1-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
Your message dated Sat, 15 Oct 2005 13:32:14 -0700
with message-id <[EMAIL PROTECTED]>
and subject line Bug#326772: fixed in emacs-goodies-el 25.1-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
Your message dated Sat, 15 Oct 2005 13:32:14 -0700
with message-id <[EMAIL PROTECTED]>
and subject line Bug#317566: fixed in emacs-goodies-el 25.1-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
Your message dated Sat, 15 Oct 2005 13:32:14 -0700
with message-id <[EMAIL PROTECTED]>
and subject line Bug#309790: fixed in emacs-goodies-el 25.1-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
Your message dated Sat, 15 Oct 2005 13:32:14 -0700
with message-id <[EMAIL PROTECTED]>
and subject line Bug#301293: fixed in emacs-goodies-el 25.1-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
Your message dated Sat, 15 Oct 2005 13:32:13 -0700
with message-id <[EMAIL PROTECTED]>
and subject line Bug#293732: fixed in emacs-goodies-el 25.1-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
Your message dated Sat, 15 Oct 2005 13:32:14 -0700
with message-id <[EMAIL PROTECTED]>
and subject line Bug#297828: fixed in emacs-goodies-el 25.1-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
Your message dated Sat, 15 Oct 2005 13:32:13 -0700
with message-id <[EMAIL PROTECTED]>
and subject line Bug#280415: fixed in emacs-goodies-el 25.1-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
Your message dated Sat, 15 Oct 2005 13:32:13 -0700
with message-id <[EMAIL PROTECTED]>
and subject line Bug#260705: fixed in emacs-goodies-el 25.1-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
Your message dated Sat, 15 Oct 2005 13:32:13 -0700
with message-id <[EMAIL PROTECTED]>
and subject line Bug#246379: fixed in emacs-goodies-el 25.1-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
Your message dated Sat, 15 Oct 2005 13:32:13 -0700
with message-id <[EMAIL PROTECTED]>
and subject line Bug#237341: fixed in emacs-goodies-el 25.1-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
Your message dated Sat, 15 Oct 2005 20:52:03 +0100
with message-id <[EMAIL PROTECTED]>
and subject line Bug#327797: bins: contains paths from the build process
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 th
Your message dated Sat, 15 Oct 2005 15:34:45 -0400
with message-id <[EMAIL PROTECTED]>
and subject line Bug#334118: HPPA B180L 2005-10-15 netboot install successful
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, 15 Oct 2005 11:32:07 -0700
with message-id <[EMAIL PROTECTED]>
and subject line Bug#271799: fixed in fbpager 0.1.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 yo
Your message dated Sat, 15 Oct 2005 11:17:08 -0700
with message-id <[EMAIL PROTECTED]>
and subject line Bug#334043: fixed in rss2email 1:2.55-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 message dated Sat, 15 Oct 2005 11:02:14 -0700
with message-id <[EMAIL PROTECTED]>
and subject line Bug#332312: fixed in gnome-libs 1.4.2-25
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, 15 Oct 2005 18:27:18 +0200
with message-id <[EMAIL PROTECTED]>
and subject line Fixed in upload of libgnomeprint 2.12.1-2 to experimental
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, 15 Oct 2005 09:32:05 -0700
with message-id <[EMAIL PROTECTED]>
and subject line Bug#316889: fixed in libpam-radius-auth 1.3.16-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
Your message dated Sat, 15 Oct 2005 09:32:06 -0700
with message-id <[EMAIL PROTECTED]>
and subject line Bug#332003: fixed in libpam-radius-auth 1.3.16-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
Your message dated Sat, 15 Oct 2005 09:32:06 -0700
with message-id <[EMAIL PROTECTED]>
and subject line Bug#333145: fixed in libpam-radius-auth 1.3.16-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
Your message dated Sat, 15 Oct 2005 09:32:05 -0700
with message-id <[EMAIL PROTECTED]>
and subject line Bug#312442: fixed in libpam-radius-auth 1.3.16-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
Your message dated Sat, 15 Oct 2005 18:58:50 +0200
with message-id <[EMAIL PROTECTED]>
and subject line bug closed
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 reope
Your message dated Sat, 15 Oct 2005 12:30:17 -0400
with message-id <[EMAIL PROTECTED]>
and subject line Bug#311555: wine: Missing build depend for docbook
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 cas
Your message dated Sat, 15 Oct 2005 18:58:50 +0200
with message-id <[EMAIL PROTECTED]>
and subject line bug closed
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 reope
Your message dated Sat, 15 Oct 2005 18:58:50 +0200
with message-id <[EMAIL PROTECTED]>
and subject line bug closed
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 reope
Your message dated Sat, 15 Oct 2005 18:58:50 +0200
with message-id <[EMAIL PROTECTED]>
and subject line bug closed
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 reope
Your message dated Sat, 15 Oct 2005 18:58:50 +0200
with message-id <[EMAIL PROTECTED]>
and subject line bug closed
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 reope
Your message dated Sat, 15 Oct 2005 12:18:05 -0400
with message-id <[EMAIL PROTECTED]>
and subject line Bug#295137: wine: icons toolbar missing
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, 15 Oct 2005 12:34:37 -0400
with message-id <[EMAIL PROTECTED]>
and subject line Bug#226201: missing Build-Depends?
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
Processing commands for [EMAIL PROTECTED]:
> # Automatically generated email from bts, devscripts version 2.9.7
> close 241744 0.50-2-4
Bug#241744: aspell-pt is not instalable
'close' is deprecated; see http://www.debian.org/Bugs/Developer#closing.
Bug marked as fixed in version 0.50-2-4, send any
Your message dated Sat, 15 Oct 2005 17:55:51 +0200
with message-id <[EMAIL PROTECTED]>
and subject line Backlog has been processed and most of the consultants have
been pinged
has caused the attached Bug report to be marked as done.
This means that you claim that the problem has been dealt with.
Your message dated Sat, 15 Oct 2005 08:47:10 -0700
with message-id <[EMAIL PROTECTED]>
and subject line Bug#331275: fixed in gif2png 2.5.1-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, 15 Oct 2005 08:47:10 -0700
with message-id <[EMAIL PROTECTED]>
and subject line Bug#328336: fixed in gif2png 2.5.1-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, 15 Oct 2005 08:47:10 -0700
with message-id <[EMAIL PROTECTED]>
and subject line Bug#285329: fixed in gif2png 2.5.1-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, 15 Oct 2005 08:17:11 -0700
with message-id <[EMAIL PROTECTED]>
and subject line Bug#332694: fixed in zope-testcase 0.9.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
1 - 100 of 145 matches
Mail list logo