Bug#391194: marked as done (evince: Wrong or missing Debian menu icon)

Your message dated Wed, 17 Jan 2007 08:26:46 +0100 with message-id <[EMAIL PROTECTED]> and subject line evince: Wrong or missing Debian menu icon has caused the attached Bug report 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

Bug#380679: marked as done (rar: Depending on libstd++6 instead of libstd++5)

Your message dated Wed, 17 Jan 2007 07:17:03 + with message-id <[EMAIL PROTECTED]> and subject line Bug#380679: fixed in rar 1:3.6.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

Bug#337940: marked as done (rar: new upstream release 3.51)

Your message dated Wed, 17 Jan 2007 07:17:03 + with message-id <[EMAIL PROTECTED]> and subject line Bug#280595: fixed in rar 1:3.6.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

Bug#280595: marked as done (rar: New upstream version)

Your message dated Wed, 17 Jan 2007 07:17:03 + with message-id <[EMAIL PROTECTED]> and subject line Bug#280595: fixed in rar 1:3.6.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

Bug#309184: marked as done (rar: Does not report error type when extracting files)

Your message dated Wed, 17 Jan 2007 07:17:03 + with message-id <[EMAIL PROTECTED]> and subject line Bug#309184: fixed in rar 1:3.6.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

Bug#404818: marked as done (SA23528: cacti: "cmd.php" Command Execution and SQL Injection)

Your message dated Wed, 17 Jan 2007 06:47:02 + with message-id <[EMAIL PROTECTED]> and subject line Bug#404818: fixed in cacti 0.8.6i-3 has caused the attached Bug report to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now you

Bug#348428: marked as done (kate: Regression: Document selector always opens, even when Kate was closed with it closed)

Your message dated Tue, 16 Jan 2007 22:58:03 -0600 with message-id <[EMAIL PROTECTED]> and subject line Closing has caused the attached Bug report 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 t

Bug#216554: marked as done (thttpd: malicious user may start stopped daemon exploiting logrotate)

Your message dated Tue, 16 Jan 2007 19:59:31 -0800 with message-id <[EMAIL PROTECTED]> and subject line thttpd: malicious user may start stopped daemon exploiting logrotate has caused the attached Bug report to be marked as done. This means that you claim that the problem has been dealt with. If

Bug#406813: marked as done (installation-report: Installation mostly went well. Mostly.)

Your message dated Wed, 17 Jan 2007 02:33:42 +0100 with message-id <[EMAIL PROTECTED]> and subject line Bug#406813: installation-report: Installation mostly went well. Mostly. has caused the attached Bug report to be marked as done. This means that you claim that the problem has been dealt with.

Bug#406770: marked as done (Installation Report on Acer Aspire 2003 WLMI)

Your message dated Wed, 17 Jan 2007 02:46:57 +0100 with message-id <[EMAIL PROTECTED]> and subject line Bug#406770: Installation Report on Acer Aspire 2003 WLMI has caused the attached Bug report to be marked as done. This means that you claim that the problem has been dealt with. If this is not t

Bug#407202: marked as done (CVE-2007-0248: squid: Denial of Service Vulnerabilities)

Your message dated Wed, 17 Jan 2007 01:02:03 + with message-id <[EMAIL PROTECTED]> and subject line Bug#407202: fixed in squid 2.6.5-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

Bug#407222: marked as done (Install problem)

Your message dated Wed, 17 Jan 2007 02:14:33 +0100 with message-id <[EMAIL PROTECTED]> and subject line Bug#407222: Install 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 respon

Bug#403351: marked as done (NMU to drop build-dependency on python2.3)

Your message dated Wed, 17 Jan 2007 00:47:03 + with message-id <[EMAIL PROTECTED]> and subject line Bug#403351: fixed in gnucash 2.0.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 now yo

Bug#406378: marked as done (gnucash: GnuCash crashes when I open an account register)

Your message dated Wed, 17 Jan 2007 00:47:03 + with message-id <[EMAIL PROTECTED]> and subject line Bug#406378: fixed in gnucash 2.0.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 now yo

Bug#296338: marked as done (dpkg-reconfigure -plow xserver-xfree86 report this error)

Your message dated Wed, 17 Jan 2007 01:33:02 +0100 with message-id <[EMAIL PROTECTED]> and subject line Undelivered Mail Returned to Sender has caused the attached Bug report 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

Processed: your mail

Processing commands for [EMAIL PROTECTED]: > close 406844 Bug#406844: Tiny ERP Version 4.0 is released 'close' is deprecated; see http://www.debian.org/Bugs/Developer#closing. Bug closed, send any further explanations to Robert Derochette <[EMAIL PROTECTED]> > thanks Stopping processing here. P

Bug#293160: marked as done (resolution config problem)

Your message dated Wed, 17 Jan 2007 01:06:16 +0100 with message-id <[EMAIL PROTECTED]> and subject line Bug#293160: resolution config 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 y

Bug#251968: marked as done (supertux conifguration issues)

Your message dated Wed, 17 Jan 2007 00:48:19 +0100 with message-id <[EMAIL PROTECTED]> and subject line Fixed: supertux configuration issues has caused the attached Bug report to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now yo

Bug#397497: marked as done (debian/utils/mldonkey_users is incompatible with multiuser-style users.ini)

Your message dated Tue, 16 Jan 2007 23:32:04 + with message-id <[EMAIL PROTECTED]> and subject line Bug#397497: fixed in mldonkey 2.8.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 y

Bug#402093: marked as done (mldonkey-server: Option "users2" in users.ini triggers an fatal error)

Your message dated Tue, 16 Jan 2007 23:32:04 + with message-id <[EMAIL PROTECTED]> and subject line Bug#397497: fixed in mldonkey 2.8.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 y

Bug#405173: marked as done (runs as group root)

Your message dated Tue, 16 Jan 2007 23:32:04 + with message-id <[EMAIL PROTECTED]> and subject line Bug#405173: fixed in mldonkey 2.8.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 y

Bug#401170: marked as done (mldonkey-server: Fails to configure.)

Your message dated Tue, 16 Jan 2007 23:32:04 + with message-id <[EMAIL PROTECTED]> and subject line Bug#397497: fixed in mldonkey 2.8.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 y

Bug#259108: marked as done (supertux: Mr. Iceblock gets stuck when released into a block)

Your message dated Wed, 17 Jan 2007 00:42:54 +0100 with message-id <[EMAIL PROTECTED]> and subject line Fixed: Mr. Iceblock gets really stuck when released into a block has caused the attached Bug report to be marked as done. This means that you claim that the problem has been dealt with. If this

Bug#406247: marked as done (Urgent patch to solve upload problem)

Your message dated Tue, 16 Jan 2007 23:32:04 + with message-id <[EMAIL PROTECTED]> and subject line Bug#406247: fixed in mldonkey 2.8.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 y

Bug#259091: marked as done (supertux: 1up sound playing inconsistent with 99 lives)

Your message dated Wed, 17 Jan 2007 00:36:17 +0100 with message-id <[EMAIL PROTECTED]> and subject line Fixed: supertux: 1up sound playing inconsistent with 99 lives has caused the attached Bug report to be marked as done. This means that you claim that the problem has been dealt with. If this is

Bug#401273: marked as done (mldonkey-server: error on post-install on upgrade)

Your message dated Tue, 16 Jan 2007 23:32:04 + with message-id <[EMAIL PROTECTED]> and subject line Bug#397497: fixed in mldonkey 2.8.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 y

Bug#290650: marked as done (xserver-xfree86: [ati/atimisc] server won't start on Mach64 LN rev 100 [monitor sync ranges misconfigured])

Your message dated Wed, 17 Jan 2007 00:18:21 +0100 with message-id <[EMAIL PROTECTED]> and subject line Undelivered Mail Returned to Sender has caused the attached Bug report to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now you

Bug#192365: marked as done (xserver-xfree86: [s3] accelerated solid Bresenham line drawing buggy on Trio32/64 rev 84)

Your message dated Wed, 17 Jan 2007 00:21:02 +0100 with message-id <[EMAIL PROTECTED]> and subject line Bug#192365: xserver-xfree86: [s3] accelerated solid Bresenham line drawing buggy on Trio32/64 rev 84 has caused the attached Bug report to be marked as done. This means that you claim that the

Bug#290797: marked as done (xserver-xfree86: commenting out resolutions with dpkg-reconfigure doesn't work)

Your message dated Wed, 17 Jan 2007 00:19:04 +0100 with message-id <[EMAIL PROTECTED]> and subject line Undelivered Mail Returned to Sender has caused the attached Bug report to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now you

Bug#324693: marked as done (supertux: Bad guys get stuck in the floor)

Your message dated Wed, 17 Jan 2007 00:02:21 +0100 with message-id <[EMAIL PROTECTED]> and subject line Fixed: supertux: Bad guys get stuck in the floor has caused the attached Bug report to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case

Bug#299784: marked as done (ocaml-doc: Mistake in Printf docs)

Your message dated Tue, 16 Jan 2007 23:32:22 +0100 with message-id <[EMAIL PROTECTED]> and subject line Bug#299784: ocaml-doc: Mistake in Printf docs has caused the attached Bug report to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it

Bug#406718: marked as done (Version 1.4 is available since 18-Nov-2006)

Your message dated Tue, 16 Jan 2007 22:40:45 +0100 with message-id <[EMAIL PROTECTED]> and subject line Re: Fwd: Re: foremost-1.4 (fwd) has caused the attached Bug report 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

Bug#378201: marked as done (supertux: FTBFS: bashisms)

Your message dated Tue, 16 Jan 2007 23:45:48 +0100 with message-id <[EMAIL PROTECTED]> and subject line supertux bashisms: should be 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

Bug#404676: marked as done (New upstream release: 0.3.0)

Your message dated Tue, 16 Jan 2007 22:17:04 + with message-id <[EMAIL PROTECTED]> and subject line Bug#404676: fixed in supertux 0.3.0~dfsg-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

Bug#394222: marked as done (supertux: No icon in gnome applications menu.)

Your message dated Tue, 16 Jan 2007 22:17:04 + with message-id <[EMAIL PROTECTED]> and subject line Bug#394222: fixed in supertux 0.3.0~dfsg-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

Bug#341432: marked as done (Desktopfile for supertux package)

Your message dated Tue, 16 Jan 2007 22:17:04 + with message-id <[EMAIL PROTECTED]> and subject line Bug#341432: fixed in supertux 0.3.0~dfsg-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

Bug#251686: marked as done (X server crash)

Your message dated Tue, 16 Jan 2007 22:54:07 +0100 with message-id <[EMAIL PROTECTED]> and subject line Undelivered Mail Returned to Sender has caused the attached Bug report to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now you

Bug#254119: marked as done (xserver-xfree86: [keyboard] Option "AutoRepeat" in XF86Config-4 has no effect (but xset r rate works))

Your message dated Tue, 16 Jan 2007 22:54:03 +0100 with message-id <[EMAIL PROTECTED]> and subject line Undelivered Mail Returned to Sender has caused the attached Bug report to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now you

Bug#396791: marked as done (torrentflux: Charset iso-8859-1 not recognized by browsers)

Your message dated Tue, 16 Jan 2007 13:36:55 -0800 with message-id <[EMAIL PROTECTED]> and subject line Bug#396791: torrentflux: Charset iso-8859-1 not recognized by browsers has caused the attached Bug report to be marked as done. This means that you claim that the problem has been dealt with. I

Bug#403288: marked as done (libipod: ipod_memory_alloc return implicitly converted to int)

Your message dated Tue, 16 Jan 2007 21:32:02 + with message-id <[EMAIL PROTECTED]> and subject line Bug#403288: fixed in libipod 0.1.2-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

Bug#404995: marked as done (pnputils: ..conflict w pnpbios-tools on `/sbin/lspnp'...)

Your message dated Tue, 16 Jan 2007 21:17:07 + with message-id <[EMAIL PROTECTED]> and subject line Bug#404995: fixed in pnputils 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

Bug#406583: marked as done (libswt-mozilla-gtk-3.2-jni: Conflicts with libswt3.2-gtk-jni)

Your message dated Tue, 16 Jan 2007 20:32:04 + with message-id <[EMAIL PROTECTED]> and subject line Bug#406583: fixed in swt-gtk 3.2.1-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

Bug#273993: marked as done (xserver-xfree86: [nv] SIGFPE in nv10CalcArbitration() on on NV35 [GeForce FX 5900] rev 161)

Your message dated Tue, 16 Jan 2007 21:42:39 +0100 with message-id <[EMAIL PROTECTED]> and subject line Bug#273993: xserver-xfree86: [nv] SIGFPE in nv10CalcArbitration() on on NV35 [GeForce FX 5900] rev 161 has caused the attached Bug report to be marked as done. This means that you claim that th

Bug#401570: marked as done (libswt-gtk-3.2-jni: Conflicts with libswt3.2-gtk-jni)

Your message dated Tue, 16 Jan 2007 20:32:04 + with message-id <[EMAIL PROTECTED]> and subject line Bug#401570: fixed in swt-gtk 3.2.1-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

Bug#357596: marked as done (tenshi: Please do not abuse debconf)

Your message dated Tue, 16 Jan 2007 20:32:05 + with message-id <[EMAIL PROTECTED]> and subject line Bug#357596: fixed in tenshi 0.4-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 you

Bug#407191: marked as done (debianutils: armel and crosscompilation problems)

Your message dated Tue, 16 Jan 2007 20:32:01 + with message-id <[EMAIL PROTECTED]> and subject line Bug#407191: fixed in debianutils 2.17.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

Bug#407113: marked as done (missing dependency)

Your message dated Tue, 16 Jan 2007 20:47:02 + with message-id <[EMAIL PROTECTED]> and subject line Bug#407113: fixed in libnxml 0.16-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

Bug#383807: marked as done (Missing PCI IDs in the sata_via driver)

Your message dated Tue, 16 Jan 2007 13:36:10 -0700 with message-id <[EMAIL PROTECTED]> and subject line closing has caused the attached Bug report 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 t

Bug#360284: marked as done ([l10n] Czech translation of tenshi debconf messages)

Your message dated Tue, 16 Jan 2007 20:32:05 + with message-id <[EMAIL PROTECTED]> and subject line Bug#360284: fixed in tenshi 0.4-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 you

Bug#243081: marked as done (xserver-xfree86: [ati/atimisc] DPMS power off misbehaves on 3D Rage Pro rev 92)

Your message dated Tue, 16 Jan 2007 20:57:57 +0100 with message-id <[EMAIL PROTECTED]> and subject line Undelivered Mail Returned to Sender has caused the attached Bug report to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now you

Bug#248866: marked as done (xserver-xfree86: [nv] XAA screen-to-screen copies malfunction on NV15 [GeForce2 - nForce GPU] rev 177)

Your message dated Tue, 16 Jan 2007 20:59:14 +0100 with message-id <[EMAIL PROTECTED]> and subject line Returned mail has caused the attached Bug report 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 re

Bug#186738: marked as done (cadaver: SSL not enabled.)

Your message dated Tue, 16 Jan 2007 19:32:02 + with message-id <[EMAIL PROTECTED]> and subject line Bug#186738: fixed in cadaver 0.22.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 y

Bug#163583: marked as done (If you adopt this package, please port it to GNU TLS)

Your message dated Tue, 16 Jan 2007 19:32:02 + with message-id <[EMAIL PROTECTED]> and subject line Bug#186738: fixed in cadaver 0.22.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 y

Bug#397735: marked as done (cadaver: please document .netrc support)

Your message dated Tue, 16 Jan 2007 19:32:02 + with message-id <[EMAIL PROTECTED]> and subject line Bug#397735: fixed in cadaver 0.22.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 y

Bug#247374: marked as done (Cadaver missing SSL support)

Your message dated Tue, 16 Jan 2007 19:32:02 + with message-id <[EMAIL PROTECTED]> and subject line Bug#247374: fixed in cadaver 0.22.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 y

Bug#407105: marked as done (tenshi: Package is non functional when rebuilt from sources)

Your message dated Tue, 16 Jan 2007 20:56:17 +0100 with message-id <[EMAIL PROTECTED]> and subject line Closing this 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

Bug#163583: marked as done (If you adopt this package, please port it to GNU TLS)

Your message dated Tue, 16 Jan 2007 19:32:02 + with message-id <[EMAIL PROTECTED]> and subject line Bug#163583: fixed in cadaver 0.22.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 y

Bug#186738: marked as done (cadaver: SSL not enabled.)

Your message dated Tue, 16 Jan 2007 19:32:02 + with message-id <[EMAIL PROTECTED]> and subject line Bug#163583: fixed in cadaver 0.22.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 y

Processed: Fixed

Processing commands for [EMAIL PROTECTED]: > close 383669 Bug#383669: slrn: Exit with sigseg 'close' is deprecated; see http://www.debian.org/Bugs/Developer#closing. Bug#383670: slrn: Dies due to a double free Bug closed, send any further explanations to Jörg Sommer <[EMAIL PROTECTED]> Removed pe

Bug#407169: marked as done (installation-reports)

Your message dated Tue, 16 Jan 2007 19:20:45 +0100 with message-id <[EMAIL PROTECTED]> and subject line Bug#407169: installation-reports has caused the attached Bug report 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

Bug#407117: marked as done (coq-doc-html: index.html requires a multi-file manual, while the refman is a single html file.)

Your message dated Tue, 16 Jan 2007 18:02:03 + with message-id <[EMAIL PROTECTED]> and subject line Bug#407117: fixed in coq-doc 8.1~gamma-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

Bug#406911: marked as done (user-setup: last set of bugfixes stops passwd/make-user=false from working)

Your message dated Tue, 16 Jan 2007 18:55:05 +0100 with message-id <[EMAIL PROTECTED]> and subject line Bug#406911: user-setup: last set of bugfixes stops passwd/make-user=false from working has caused the attached Bug report to be marked as done. This means that you claim that the problem has be

Bug#369574: marked as done (Suggestion: Add support for gcj to libpg-java)

Your message dated Tue, 16 Jan 2007 19:19:27 +0100 with message-id <[EMAIL PROTECTED]> and subject line Bug#369574: Suggestion: Add support for gcj to libpg-java has caused the attached Bug report to be marked as done. This means that you claim that the problem has been dealt with. If this is not

Bug#379918: marked as done (gpr: [INTL:fr] French program translation update)

Your message dated Tue, 16 Jan 2007 17:02:02 + with message-id <[EMAIL PROTECTED]> and subject line Bug#379918: fixed in gpr 0.11deb.etch1 has caused the attached Bug report 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#370098: marked as done (epiphany isn't installed by the default installation)

Your message dated Tue, 16 Jan 2007 16:32:03 + with message-id <[EMAIL PROTECTED]> and subject line Bug#370098: fixed in tasksel 2.64 has caused the attached Bug report 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#407017: marked as done (installation-report: SUN Ultra 10)

Your message dated Tue, 16 Jan 2007 17:08:35 +0100 with message-id <[EMAIL PROTECTED]> and subject line Bug#407017: installation-report: SUN Ultra 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

Bug#407164: marked as done (Logical volume name is wrong when the hostname contains the dash character)

Your message dated Tue, 16 Jan 2007 17:29:58 +0100 with message-id <[EMAIL PROTECTED]> and subject line Bug#407164: Logical volume name is wrong when the hostname contains the dash character has caused the attached Bug report to be marked as done. This means that you claim that the problem has be

Bug#407156: marked as done (jamvm: FTBFS on kfreebsd-amd64)

Your message dated Tue, 16 Jan 2007 16:02:02 + with message-id <[EMAIL PROTECTED]> and subject line Bug#407156: fixed in jamvm 1.4.4-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

Bug#403475: marked as done (linux-image-2.6.18-3-k7 lacks grub as dependancy)

Your message dated Tue, 16 Jan 2007 16:06:07 +0100 with message-id <[EMAIL PROTECTED]> and subject line Bug#403475: linux-image-2.6.18-3-k7 lacks grub as dependancy has caused 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

Bug#407141: marked as done (xen-utils-3.0.3-1: please provide 32bit domU kernels on amd64 arch)

Your message dated Tue, 16 Jan 2007 15:51:21 +0100 with message-id <[EMAIL PROTECTED]> and subject line [Pkg-xen-devel] Bug#407141: xen-utils-3.0.3-1: please provide 32bit domU kernels on amd64 arch has caused the attached Bug report to be marked as done. This means that you claim that the proble

Bug#350021: marked as done (Alt-I should insert \item before the current character)

Your message dated Tue, 16 Jan 2007 15:02:16 + with message-id <[EMAIL PROTECTED]> and subject line Bug#350021: fixed in vim-latexsuite 20060325-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

Bug#378294: marked as done (vim-latexsuite: dependencies on tetex-bin)

Your message dated Tue, 16 Jan 2007 15:02:16 + with message-id <[EMAIL PROTECTED]> and subject line Bug#378294: fixed in vim-latexsuite 20060325-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

Bug#395810: marked as done (vim-latexsuite: missing binary-arch and binary-indep targets in debian/rules (Policy 4.9))

Your message dated Tue, 16 Jan 2007 15:02:16 + with message-id <[EMAIL PROTECTED]> and subject line Bug#395810: fixed in vim-latexsuite 20060325-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

Bug#377992: marked as done (linux-kernel: boot kernle overlaps lilo config)

Your message dated Tue, 16 Jan 2007 16:05:12 +0100 with message-id <[EMAIL PROTECTED]> and subject line linux-kernel: boot kernle overlaps lilo config has caused the attached Bug report to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it

Bug#365152: marked as done (vim-latexsuite: doesn't work)

Your message dated Tue, 16 Jan 2007 15:02:16 + with message-id <[EMAIL PROTECTED]> and subject line Bug#365152: fixed in vim-latexsuite 20060325-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

Bug#382200: marked as done (linux-image-2.6.16-2-vserver-686: grub is beeing deinstalled using bpo)

Your message dated Tue, 16 Jan 2007 15:34:27 +0100 with message-id <[EMAIL PROTECTED]> and subject line Bug#382200: linux-image-2.6.16-2-vserver-686: grub is beeing deinstalled using bpo has caused the attached Bug report to be marked as done. This means that you claim that the problem has been d

Bug#262885: marked as done (RFH: parted -- Searching co-maintainer for the parted package.)

Your message dated Tue, 16 Jan 2007 14:52:32 +0100 with message-id <[EMAIL PROTECTED]> and subject line Help for parted debian 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 res

Bug#398140: marked as done (linux-image-2.6.18-2-486: ..fancy new post-rm script oughtta mention grub or "exit 0" instead of bombing out a lilo style 128 error.)

Your message dated Tue, 16 Jan 2007 15:30:15 +0100 with message-id <[EMAIL PROTECTED]> and subject line Bug#398140: linux-image-2.6.18-2-486: ..fancy new post-rm script oughtta mention grub or "exit 0" instead of bombing out a lilo style 128 error. has caused the attached Bug report to be marked

Processed: closing 319429

Processing commands for [EMAIL PROTECTED]: > # Automatically generated email from bts, devscripts version 2.9.26 > close 319429 Bug#319429: linux-image-2.6.12-1-686: installation, when used with grub and a separate /boot partition results in boot failure 'close' is deprecated; see http://www.debi

Bug#406912: marked as done (tasksel-data: Should add numlockx to desktop)

Your message dated Mon, 15 Jan 2007 23:19:03 -0500 with message-id <[EMAIL PROTECTED]> and subject line Bug#406912: tasksel-data: Should add numlockx to desktop has caused the attached Bug report to be marked as done. This means that you claim that the problem has been dealt with. If this is not t

Bug#406847: marked as done (DDPO: link to p-u-new is stale)

Your message dated Tue, 16 Jan 2007 15:31:14 +0100 with message-id <[EMAIL PROTECTED]> and subject line DDPO: link to p-u-new is stale has caused the attached Bug report to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your res

Bug#380588: marked as done (INTL:vi)

Your message dated Tue, 16 Jan 2007 13:55:03 + with message-id <[EMAIL PROTECTED]> and subject line Bug#380588: fixed in installation-guide 20070115 has caused the attached Bug report to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case

Bug#342076: marked as done (installation-guide: should give the right path to TFTP root directory)

Your message dated Tue, 16 Jan 2007 13:55:03 + with message-id <[EMAIL PROTECTED]> and subject line Bug#342076: fixed in installation-guide 20070115 has caused the attached Bug report to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case

Bug#305977: marked as done (debian-installer-manual support for amd64.)

Your message dated Tue, 16 Jan 2007 13:55:03 + with message-id <[EMAIL PROTECTED]> and subject line Bug#305977: fixed in installation-guide 20070115 has caused the attached Bug report to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case

Bug#402492: marked as done (installation-guide: file does not exist)

Your message dated Tue, 16 Jan 2007 13:55:04 + with message-id <[EMAIL PROTECTED]> and subject line Bug#402492: fixed in installation-guide 20070115 has caused the attached Bug report to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case

Bug#397923: marked as done (debian-installer-manual: Bad english in preseed.po)

Your message dated Tue, 16 Jan 2007 13:55:04 + with message-id <[EMAIL PROTECTED]> and subject line Bug#397923: fixed in installation-guide 20070115 has caused the attached Bug report to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case

Bug#378651: marked as done (Manual section 7.2.1 needs update for loop-AES)

Your message dated Tue, 16 Jan 2007 13:55:03 + with message-id <[EMAIL PROTECTED]> and subject line Bug#378651: fixed in installation-guide 20070115 has caused the attached Bug report to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case

Bug#248067: marked as done (Installation manual says Ctrl-Alt-Del will shut down PPC system)

Your message dated Tue, 16 Jan 2007 13:55:03 + with message-id <[EMAIL PROTECTED]> and subject line Bug#248067: fixed in installation-guide 20070115 has caused the attached Bug report to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case

Bug#370425: marked as done (installation-guide)

Your message dated Tue, 16 Jan 2007 13:55:03 + with message-id <[EMAIL PROTECTED]> and subject line Bug#370425: fixed in installation-guide 20070115 has caused the attached Bug report to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case

Bug#402437: marked as done (installation-guide: /post-install/reactivating-win.xml seems obsolete)

Your message dated Tue, 16 Jan 2007 13:55:04 + with message-id <[EMAIL PROTECTED]> and subject line Bug#402437: fixed in installation-guide 20070115 has caused the attached Bug report to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case

Bug#400750: marked as done (linux-modules-extra-2.6: remove spca5xx)

Your message dated Tue, 16 Jan 2007 14:01:04 + with message-id <[EMAIL PROTECTED]> and subject line Bug#400750: fixed in linux-modules-extra-2.6 2.6.18-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

Bug#332772: marked as done (debian-installer: FTBFS on amd64: Error: unknown architecture 'amd64')

Your message dated Tue, 16 Jan 2007 13:55:03 + with message-id <[EMAIL PROTECTED]> and subject line Bug#305977: fixed in installation-guide 20070115 has caused the attached Bug report to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case

Bug#381657: marked as done (installation-guide: Korean PDF build patch)

Your message dated Tue, 16 Jan 2007 13:55:03 + with message-id <[EMAIL PROTECTED]> and subject line Bug#381657: fixed in installation-guide 20070115 has caused the attached Bug report to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case

Bug#397790: marked as done (installation-guide: Typos in boot-installer.po)

Your message dated Tue, 16 Jan 2007 13:55:03 + with message-id <[EMAIL PROTECTED]> and subject line Bug#397790: fixed in installation-guide 20070115 has caused the attached Bug report to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case

Bug#386591: marked as done (Typo in Alpha d-i documentation)

Your message dated Tue, 16 Jan 2007 13:55:03 + with message-id <[EMAIL PROTECTED]> and subject line Bug#386591: fixed in installation-guide 20070115 has caused the attached Bug report to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case

Bug#400751: marked as done (linux-modules-extra-2.6: include gspca)

Your message dated Tue, 16 Jan 2007 14:01:04 + with message-id <[EMAIL PROTECTED]> and subject line Bug#400751: fixed in linux-modules-extra-2.6 2.6.18-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

Bug#394471: marked as done (installation guide)

Your message dated Tue, 16 Jan 2007 13:55:03 + with message-id <[EMAIL PROTECTED]> and subject line Bug#394471: fixed in installation-guide 20070115 has caused the attached Bug report to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case

Bug#394929: marked as done ([Etch] installation-guide-i386 - several steps are misleading or cannot be finished)

Your message dated Tue, 16 Jan 2007 13:55:03 + with message-id <[EMAIL PROTECTED]> and subject line Bug#394929: fixed in installation-guide 20070115 has caused the attached Bug report to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case

Bug#381787: marked as done (mkvmlinuz should bail if it can't find addnote)

Your message dated Tue, 16 Jan 2007 13:47:01 + with message-id <[EMAIL PROTECTED]> and subject line Bug#381787: fixed in mkvmlinuz 30 has caused the attached Bug report 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#384321: marked as done (installation-guide: with amd64 we have now 12 supported architectures)

Your message dated Tue, 16 Jan 2007 13:55:03 + with message-id <[EMAIL PROTECTED]> and subject line Bug#384321: fixed in installation-guide 20070115 has caused the attached Bug report to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case

  1   2   >