Bug#342104: marked as done (strange mysql bug, possibly thread related)

Your message dated Mon, 05 Dec 2005 22:02:07 -0800 with message-id <[EMAIL PROTECTED]> and subject line Bug#342104: fixed in kfreebsd-5 5.4-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 now y

Bug#320558: marked as done ('man xloadimage' typos: "copywritten" x 2, "preceeded" x 2, "preceed" x 2, "noticable", and "noticably")

Your message dated Mon, 05 Dec 2005 20:17:05 -0800 with message-id <[EMAIL PROTECTED]> and subject line Bug#320558: fixed in xloadimage 4.1-16 has caused the attached Bug report to 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#330200: marked as done (zsh: xloadimage completion doesn't know about png support)

Your message dated Mon, 05 Dec 2005 20:17:05 -0800 with message-id <[EMAIL PROTECTED]> and subject line Bug#330200: fixed in xloadimage 4.1-16 has caused the attached Bug report to 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#326519: marked as done (Typo in the xloadimage.1x man page)

Your message dated Mon, 05 Dec 2005 20:17:05 -0800 with message-id <[EMAIL PROTECTED]> and subject line Bug#326519: fixed in xloadimage 4.1-16 has caused the attached Bug report to 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#320556: marked as done ('man uufilter' typo: "editting")

Your message dated Mon, 05 Dec 2005 20:17:05 -0800 with message-id <[EMAIL PROTECTED]> and subject line Bug#320556: fixed in xloadimage 4.1-16 has caused the attached Bug report to 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#297433: marked as done (ITA: mailliststat -- Displays statistics about mbox files)

Your message dated Mon, 05 Dec 2005 19:47:06 -0800 with message-id <[EMAIL PROTECTED]> and subject line Bug#297433: fixed in mailliststat 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

Bug#281816: marked as done (mailliststat case insensitive option?)

Your message dated Mon, 05 Dec 2005 19:47:06 -0800 with message-id <[EMAIL PROTECTED]> and subject line Bug#281816: fixed in mailliststat 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

Bug#341417: marked as done (bamboo: staticcopy script does not work)

Your message dated Mon, 05 Dec 2005 19:17:08 -0800 with message-id <[EMAIL PROTECTED]> and subject line Bug#341417: fixed in bamboo 1.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

Bug#342189: marked as done (wxwidgets2.6: Please update to latest stable version 2.6.2)

Your message dated Tue, 6 Dec 2005 13:33:41 +1030 with message-id <[EMAIL PROTECTED]> and subject line Bug#342189: wxwidgets2.6: Please update to latest stable version 2.6.2 has caused the attached Bug report to be marked as done. This means that you claim that the problem has been dealt with. If

Bug#341750: marked as done (genext2fs_1.3-9(hppa/unstable): FTBFS: missing build-depends)

Your message dated Mon, 05 Dec 2005 19:02:06 -0800 with message-id <[EMAIL PROTECTED]> and subject line Bug#341750: fixed in genext2fs 1.3-10 has caused the attached Bug report to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now y

Bug#319806: marked as done (Cannot import new folders (f-spot crashes))

Your message dated Tue, 6 Dec 2005 15:24:45 +1300 with message-id <[EMAIL PROTECTED]> and subject line Cannot import new folders (f-spot crashes) has caused the attached Bug report to 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#327182: marked as done (f-spot: fails to import)

Your message dated Tue, 6 Dec 2005 14:49:47 +1300 with message-id <[EMAIL PROTECTED]> and subject line f-spot: slideshow causes unhandled exception has caused the attached Bug report to 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#327182: marked as done (f-spot: fails to import)

Your message dated Tue, 6 Dec 2005 14:57:58 +1300 with message-id <[EMAIL PROTECTED]> and subject line f-spot: fails to import has caused the attached Bug report to 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 responsibil

Bug#316020: marked as done (f-spot: slideshow causes unhandled exception)

Your message dated Tue, 6 Dec 2005 14:49:47 +1300 with message-id <[EMAIL PROTECTED]> and subject line f-spot: slideshow causes unhandled exception has caused the attached Bug report to 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#342185: marked as done (vm: ftbfs [sparc] dpkg-genchanges: failure: cannot read files list file)

Your message dated Mon, 05 Dec 2005 19:40:53 -0600 with message-id <[EMAIL PROTECTED]> and subject line Bug#342185: vm: ftbfs [sparc] dpkg-genchanges: failure: cannot read files list file has caused the attached Bug report to be marked as done. This means that you claim that the problem has been

Bug#341920: marked as done (postinst fails and 'make-kpkg clean' doesn't remove debian )

Your message dated Mon, 05 Dec 2005 19:39:07 -0600 with message-id <[EMAIL PROTECTED]> and subject line Bug#341920: postinst fails and 'make-kpkg clean' doesn't remove debian 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#312839: marked as done (ITA: august -- Tcl/Tk HTML editor.)

Your message dated Mon, 05 Dec 2005 17:02:04 -0800 with message-id <[EMAIL PROTECTED]> and subject line Bug#312839: fixed in august 0.63-beta1-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 no

Bug#342147: marked as done (pbuilder: pdebuild fails if EXTRAPACKAGES is nonzero)

Your message dated Tue, 06 Dec 2005 09:23:48 +0900 with message-id <[EMAIL PROTECTED]> and subject line [Pbuilder-maint] Bug#342147: pbuilder: pdebuild fails if EXTRAPACKAGES is nonzero has caused the attached Bug report to be marked as done. This means that you claim that the problem has b

Bug#342139: marked as done (disable chan_zap building (in channels makefile) against old libmfcr2)

Your message dated Mon, 05 Dec 2005 16:32:24 -0800 with message-id <[EMAIL PROTECTED]> and subject line Bug#342139: fixed in asterisk 1:1.2.0.dfsg-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 i

Bug#341395: marked as done (seperate api docs and configuration samples)

Your message dated Mon, 05 Dec 2005 16:32:24 -0800 with message-id <[EMAIL PROTECTED]> and subject line Bug#341395: fixed in asterisk 1:1.2.0.dfsg-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 i

Bug#341363: marked as done (asterisk: Should build-depend on libcurl3-dev)

Your message dated Mon, 05 Dec 2005 16:32:24 -0800 with message-id <[EMAIL PROTECTED]> and subject line Bug#341363: fixed in asterisk 1:1.2.0.dfsg-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 i

Bug#341362: marked as done (asterisk: Missing build-dependency on doxygen)

Your message dated Mon, 05 Dec 2005 16:32:24 -0800 with message-id <[EMAIL PROTECTED]> and subject line Bug#341362: fixed in asterisk 1:1.2.0.dfsg-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 i

Bug#340574: marked as done (asterisk: SIP error 400 on outgoing calls)

Your message dated Mon, 05 Dec 2005 16:32:24 -0800 with message-id <[EMAIL PROTECTED]> and subject line Bug#340574: fixed in asterisk 1:1.2.0.dfsg-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 i

Bug#272566: marked as done (chronyc input does not terminate)

Your message dated Mon, 05 Dec 2005 18:37:20 -0600 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 reo

Bug#326198: marked as done (asterisk: debian configuration hickup. needs dependency.)

Your message dated Tue, 06 Dec 2005 00:05:06 + with message-id <[EMAIL PROTECTED]> and subject line Fixed in 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 not the case it is now your responsibility t

Bug#325268: marked as done (asterisk: Please package version 1.2 betas)

Your message dated Tue, 06 Dec 2005 00:05:06 + with message-id <[EMAIL PROTECTED]> and subject line Fixed in 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 not the case it is now your responsibility t

Bug#342169: marked as done (modprobe.8.gz: Add SEE ALSO insmod(8))

Your message dated Tue, 6 Dec 2005 00:19:47 +0100 with message-id <[EMAIL PROTECTED]> and subject line Bug#342169: modprobe.8.gz: Add SEE ALSO insmod(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

Bug#336279: marked as done (FTBFS: Unsatisfiable build-dependency on dvips)

Your message dated Mon, 05 Dec 2005 14:47:11 -0800 with message-id <[EMAIL PROTECTED]> and subject line Bug#336279: fixed in magicfilter 1.2-59 has caused the attached Bug report to 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#342143: marked as done (kernel-package: Error setting debconf flags in generated linux image)

Your message dated Mon, 05 Dec 2005 14:32:21 -0800 with message-id <[EMAIL PROTECTED]> and subject line Bug#342143: fixed in kernel-package 10.015 has caused the attached Bug report to 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#342033: marked as done (debhelper: dh_installdocs ignores -X for doc-base files)

Your message dated Mon, 05 Dec 2005 14:32:11 -0800 with message-id <[EMAIL PROTECTED]> and subject line Bug#342033: fixed in debhelper 5.0.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 yo

Bug#341289: marked as done (typos in debhelper.pot: compatability)

Your message dated Mon, 05 Dec 2005 14:32:11 -0800 with message-id <[EMAIL PROTECTED]> and subject line Bug#341289: fixed in debhelper 5.0.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 yo

Bug#5212: marked as done (xdm: allows login without valid shell)

Your message dated Mon, 5 Dec 2005 17:21:04 -0500 with message-id <[EMAIL PROTECTED]> and subject line conclusions regarding login without valid shell has caused the attached Bug report 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#248064: marked as done ([i386] [beta4] [netinst] success)

Your message dated Mon, 5 Dec 2005 23:25:52 +0100 with message-id <[EMAIL PROTECTED]> and subject line Bug#248064: Problems 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 responsi

Bug#103007: marked as done (mkdir -v bug)

Your message dated Mon, 5 Dec 2005 23:06:29 +0100 (CET) with message-id <[EMAIL PROTECTED]> and subject line closing wishlist that is implemented in current coreutils has caused 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#342151: marked as done (kernel-package: make-kpkg use "--exec" for find in templates)

Your message dated Mon, 05 Dec 2005 15:55:35 -0600 with message-id <[EMAIL PROTECTED]> and subject line Bug#342151: kernel-package: make-kpkg use "--exec" for find in templates has caused the attached Bug report to be marked as done. This means that you claim that the problem has been dealt with.

Bug#342146: marked as done (binutils: Fails compiling Linux 2.6.9/i386)

Your message dated Mon, 05 Dec 2005 21:37:38 + with message-id <[EMAIL PROTECTED]> and subject line Bug#342146: binutils: Fails compiling Linux 2.6.9/i386 has caused the attached 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#95766: marked as done (Please add --gigabytes)

Your message dated Mon, 5 Dec 2005 22:24:12 +0100 (CET) with message-id <[EMAIL PROTECTED]> and subject line closing wishlist that is implemented in current coreutils has caused 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#136195: marked as done (fileutils: du manpage patch)

Your message dated Mon, 5 Dec 2005 22:45:59 +0100 (CET) with message-id <[EMAIL PROTECTED]> and subject line closing wishlist that is implemented in current coreutils has caused the attached Bug report to be marked as done. This means that you claim that the problem has been dealt with. If this is

Processed: close antique fixed bug

Processing commands for [EMAIL PROTECTED]: > close 92389 Bug#92389: libstdc++2.10-dev build dependency 'close' is deprecated; see http://www.debian.org/Bugs/Developer#closing. Bug closed, send any further explanations to [EMAIL PROTECTED] (Bdale Garbee) > thanks Stopping processing here. Please

Bug#314542: marked as done (clisp: clobbers terminal state on ^C)

Your message dated Mon, 5 Dec 2005 21:57:32 +0100 with message-id <[EMAIL PROTECTED]> and subject line very old bugreport, 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 respons

Bug#278285: marked as done (clisp-dev needs to depend on -dev versions of clisp's dependencies)

Your message dated Mon, 5 Dec 2005 21:57:32 +0100 with message-id <[EMAIL PROTECTED]> and subject line very old bugreport, 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 respons

Bug#235243: marked as done (postinst script hangs when common-lisp-controller is run inside a chroot)

Your message dated Mon, 5 Dec 2005 21:57:32 +0100 with message-id <[EMAIL PROTECTED]> and subject line very old bugreport, 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 respons

Processed: close bug for removed package

Processing commands for [EMAIL PROTECTED]: > close 322642 Bug#322642: FTBFS: toc/tests/cpp/gcc_2_95_typename_problem.cpp fails 'close' is deprecated; see http://www.debian.org/Bugs/Developer#closing. Bug closed, send any further explanations to Matt Kraai <[EMAIL PROTECTED]> > thanks Stopping pro

Bug#341667: marked as done (apt: FTBFS on s390)

Your message dated Mon, 5 Dec 2005 14:53:41 -0500 with message-id <[EMAIL PROTECTED]> and subject line apparently built has caused the attached Bug report to 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#342081: marked as done (/usr/share/doc/phpbb2/NEWS.Debian.gz refers to non existant file)

Your message dated Mon, 05 Dec 2005 11:32:10 -0800 with message-id <[EMAIL PROTECTED]> and subject line Bug#342081: fixed in phpbb2 2.0.18-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

Bug#341991: marked as done (phpbb2-conf-mysql: Gziped SQL schemas are expected, but they're not gziped)

Your message dated Mon, 05 Dec 2005 11:32:10 -0800 with message-id <[EMAIL PROTECTED]> and subject line Bug#341991: fixed in phpbb2 2.0.18-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

Bug#341943: marked as done (xaos(GNU/k*BSD): FTBFS: out of date config.sub/config.guess)

Your message dated Mon, 05 Dec 2005 11:32:13 -0800 with message-id <[EMAIL PROTECTED]> and subject line Bug#341943: fixed in xaos 3.1r-14 has caused the attached Bug report to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your

Bug#336623: marked as done (phpbb2-languages: Russian translations fixes)

Your message dated Mon, 05 Dec 2005 11:32:10 -0800 with message-id <[EMAIL PROTECTED]> and subject line Bug#336623: fixed in phpbb2 2.0.18-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

Bug#328191: marked as done (gnomemeeting: uninstallable (unstable). conflicts libopenh323-1.15.3c2)

Your message dated Mon, 05 Dec 2005 11:17:09 -0800 with message-id <[EMAIL PROTECTED]> and subject line Bug#328191: fixed in gnomemeeting 1.2.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 n

Bug#321513: marked as done (gnomemeeting: Huge memory leaks)

Your message dated Mon, 05 Dec 2005 11:17:09 -0800 with message-id <[EMAIL PROTECTED]> and subject line Bug#321513: fixed in gnomemeeting 1.2.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 n

Bug#303727: marked as done (gnomemeeting: Can't find installed BookFactory that handles protocol 'file'.)

Your message dated Mon, 05 Dec 2005 11:17:09 -0800 with message-id <[EMAIL PROTECTED]> and subject line Bug#303727: fixed in gnomemeeting 1.2.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 n

Bug#340114: marked as done (debhelper: dh_installman character convert feature request)

Your message dated Mon, 5 Dec 2005 14:16:25 -0500 with message-id <[EMAIL PROTECTED]> and subject line Bug#340114: debhelper: dh_installman character convert feature request 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#341608: marked as done (krb5: FTBFS on hurd-i386: Does not link with -lpthread)

Your message dated Mon, 05 Dec 2005 10:47:49 -0800 with message-id <[EMAIL PROTECTED]> and subject line Bug#341608: fixed in krb5 1.4.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

Bug#330925: marked as done ([l10n:de] German debconf translation)

Your message dated Mon, 05 Dec 2005 10:47:49 -0800 with message-id <[EMAIL PROTECTED]> and subject line Bug#330925: fixed in krb5 1.4.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

Bug#333161: marked as done (krb5-admin-server: doesn't remove config file)

Your message dated Mon, 05 Dec 2005 10:47:49 -0800 with message-id <[EMAIL PROTECTED]> and subject line Bug#333161: fixed in krb5 1.4.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

Bug#261712: marked as done (krb5: FTBFS on GNU/kFreeBSD)

Your message dated Mon, 05 Dec 2005 10:47:49 -0800 with message-id <[EMAIL PROTECTED]> and subject line Bug#261712: fixed in krb5 1.4.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

Bug#250966: marked as done (/usr/sbin/klogind: Authorization behavior not fully documented)

Your message dated Mon, 05 Dec 2005 10:47:49 -0800 with message-id <[EMAIL PROTECTED]> and subject line Bug#250966: fixed in krb5 1.4.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

Bug#232431: marked as done (krb5-user: kinit: -a described in manpage but not supported by client)

Your message dated Mon, 05 Dec 2005 10:47:49 -0800 with message-id <[EMAIL PROTECTED]> and subject line Bug#232431: fixed in krb5 1.4.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

Bug#339521: marked as done (libpdf-api2-perl: Please package 0.51, it fixes an ugly import bug)

Your message dated Mon, 05 Dec 2005 10:32:21 -0800 with message-id <[EMAIL PROTECTED]> and subject line Bug#339521: fixed in libpdf-api2-perl 0.51-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

Bug#337551: marked as done (kshutdown: [INTL:sv] Swedish PO-template translation)

Your message dated Mon, 05 Dec 2005 10:32:17 -0800 with message-id <[EMAIL PROTECTED]> and subject line Bug#337551: fixed in kshutdown 0.8-1 has caused the attached Bug report to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now yo

Bug#342012: marked as done (opendb: New upstream version available)

Your message dated Mon, 05 Dec 2005 10:17:22 -0800 with message-id <[EMAIL PROTECTED]> and subject line Bug#342012: fixed in opendb 0.81p13-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#319738: marked as done ([l10n] Czech translation for opendb)

Your message dated Mon, 05 Dec 2005 10:17:22 -0800 with message-id <[EMAIL PROTECTED]> and subject line Bug#319738: fixed in opendb 0.81p13-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#316717: marked as done ([intl:fr] opendb debconf templates translation)

Your message dated Mon, 05 Dec 2005 10:17:22 -0800 with message-id <[EMAIL PROTECTED]> and subject line Bug#316717: fixed in opendb 0.81p13-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#316600: marked as done (INTL:vi)

Your message dated Mon, 05 Dec 2005 10:17:22 -0800 with message-id <[EMAIL PROTECTED]> and subject line Bug#316600: fixed in opendb 0.81p13-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#334981: marked as done (gimp: displays menus in black on black)

Your message dated Mon, 05 Dec 2005 12:47:36 -0500 with message-id <[EMAIL PROTECTED]> and subject line gimp displays menus in black on black has caused the attached Bug report to 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#341783: marked as done (bitlbee has a useless Build-Depends: on debconf-2.0)

Your message dated Mon, 05 Dec 2005 09:17:06 -0800 with message-id <[EMAIL PROTECTED]> and subject line Bug#341783: fixed in bitlbee 1.0-1 has caused the attached Bug report to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your

Bug#290835: marked as done (screem crash w/ remote location open)

Your message dated Mon, 5 Dec 2005 16:45:55 + with message-id <[EMAIL PROTECTED]> and subject line Closing: No response from submitter has caused the attached Bug report to 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#342118: marked as done (sarge tries to install libsigc++-1.2-5c102, but libsigc++-1.2-5c2 is in the archive)

Your message dated Mon, 5 Dec 2005 17:31:04 +0100 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

Bug#341515: marked as done (Cannot install synaptic, even after the "binNMU" fix)

Your message dated Mon, 05 Dec 2005 11:14:51 -0500 with message-id <[EMAIL PROTECTED]> and subject line Invalid has caused the attached Bug report to 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#341138: marked as done (ttf-gentium: re-released by upstream under a free license)

Your message dated Mon, 05 Dec 2005 08:17:12 -0800 with message-id <[EMAIL PROTECTED]> and subject line Bug#341138: fixed in ttf-gentium 1.02-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#340827: marked as done (mairix --version gives old version number)

Your message dated Mon, 05 Dec 2005 08:17:08 -0800 with message-id <[EMAIL PROTECTED]> and subject line Bug#340827: fixed in mairix 0.17-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#307432: marked as done (mairix: would be nice to handle compressed mbox)

Your message dated Mon, 05 Dec 2005 08:17:08 -0800 with message-id <[EMAIL PROTECTED]> and subject line Bug#307432: fixed in mairix 0.17-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#341488: marked as done (Synaptic 0.57.6 in unstable depends on experimental packages)

Your message dated Mon, 05 Dec 2005 11:09:29 -0500 with message-id <[EMAIL PROTECTED]> and subject line Duplicate has caused the attached Bug report to 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

Bug#341187: marked as done (most: RegExp support not compiled in)

Your message dated Mon, 05 Dec 2005 08:02:09 -0800 with message-id <[EMAIL PROTECTED]> and subject line Bug#341187: fixed in most 4.10.2-2 has caused the attached Bug report to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your

Bug#338129: marked as done (most: Wrong option +c in manpage (should be -c))

Your message dated Mon, 05 Dec 2005 08:02:09 -0800 with message-id <[EMAIL PROTECTED]> and subject line Bug#338129: fixed in most 4.10.2-2 has caused the attached Bug report to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your

Bug#335329: marked as done ('man most' typos: "confiuration" and "hexidecimal")

Your message dated Mon, 05 Dec 2005 08:02:09 -0800 with message-id <[EMAIL PROTECTED]> and subject line Bug#335329: fixed in most 4.10.2-2 has caused the attached Bug report to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your

Bug#330033: marked as done (phpwiki: debconf-updatepo has not been launched)

Your message dated Mon, 5 Dec 2005 17:05:26 +0100 with message-id <[EMAIL PROTECTED]> and subject line Closing 330033 has caused the attached Bug report to 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#307841: marked as done (most: lineno option documentation misformatted)

Your message dated Mon, 05 Dec 2005 08:02:09 -0800 with message-id <[EMAIL PROTECTED]> and subject line Bug#307841: fixed in most 4.10.2-2 has caused the attached Bug report to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your

Bug#260388: marked as done (most: should drop a file into /usr/lib/mime/packages)

Your message dated Mon, 05 Dec 2005 08:02:09 -0800 with message-id <[EMAIL PROTECTED]> and subject line Bug#260388: fixed in most 4.10.2-2 has caused the attached Bug report to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your

Bug#307930: marked as done (most: Cannot process properly UTF-8 input)

Your message dated Mon, 05 Dec 2005 08:02:09 -0800 with message-id <[EMAIL PROTECTED]> and subject line Bug#211217: fixed in most 4.10.2-2 has caused the attached Bug report to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your

Bug#211217: marked as done (most: Doesn't understand UTF-8)

Your message dated Mon, 05 Dec 2005 08:02:09 -0800 with message-id <[EMAIL PROTECTED]> and subject line Bug#211217: fixed in most 4.10.2-2 has caused the attached Bug report to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your

Bug#340829: marked as done (Security-Issue in Cacti)

Your message dated Mon, 5 Dec 2005 10:21:37 -0500 with message-id <[EMAIL PROTECTED]> and subject line closing 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 reope

Bug#336049: marked as done (Typo in man page for dict: "implemenation" -> "implementation")

Your message dated Mon, 05 Dec 2005 07:17:10 -0800 with message-id <[EMAIL PROTECTED]> and subject line Bug#336049: fixed in dictd 1.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 it is now you

Bug#340369: marked as done (libextractor(GNU/k*BSD): FTBFS: out of date libtool scripts)

Your message dated Mon, 05 Dec 2005 07:17:17 -0800 with message-id <[EMAIL PROTECTED]> and subject line Bug#340369: fixed in libextractor 0.5.7-2 has caused the attached Bug report to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is n

Bug#339792: marked as done (dictd: new upstream release available (1.10.2, 2005-09-06))

Your message dated Mon, 05 Dec 2005 07:17:10 -0800 with message-id <[EMAIL PROTECTED]> and subject line Bug#339792: fixed in dictd 1.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 it is now you

Bug#330934: marked as done (FTBFS: ICE on m68k, arm and hppa)

Your message dated Mon, 05 Dec 2005 07:32:06 -0800 with message-id <[EMAIL PROTECTED]> and subject line Bug#330934: fixed in kdesdk 4:3.4.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 y

Bug#311138: marked as done (dictd: package description /usr/doc)

Your message dated Mon, 05 Dec 2005 07:17:10 -0800 with message-id <[EMAIL PROTECTED]> and subject line Bug#311138: fixed in dictd 1.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 it is now you

Bug#314325: marked as done (dictd: fales to use utf-8 muller dictionary)

Your message dated Mon, 05 Dec 2005 07:17:10 -0800 with message-id <[EMAIL PROTECTED]> and subject line Bug#314325: fixed in dictd 1.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 it is now you

Bug#292068: marked as done (dictd: dictd doesn't need the same locale as dictfmt)

Your message dated Mon, 05 Dec 2005 07:17:10 -0800 with message-id <[EMAIL PROTECTED]> and subject line Bug#292068: fixed in dictd 1.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 it is now you

Bug#310349: marked as done ('man dict' typo: "implemenation")

Your message dated Mon, 05 Dec 2005 07:17:10 -0800 with message-id <[EMAIL PROTECTED]> and subject line Bug#310349: fixed in dictd 1.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 it is now you

Bug#297616: marked as done (dictd silently fails to start)

Your message dated Mon, 05 Dec 2005 07:17:10 -0800 with message-id <[EMAIL PROTECTED]> and subject line Bug#297616: fixed in dictd 1.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 it is now you

Bug#237113: marked as done (kopete doesn't auto-scroll my chat windows down with a new message)

Your message dated Mon, 05 Dec 2005 16:22:30 +0100 with message-id <[EMAIL PROTECTED]> and subject line kopete doesn't auto-scroll my chat windows down with a new message has caused the attached Bug report to be marked as done. This means that you claim that the problem has been dealt with. If th

Bug#232227: marked as done (dictd should not require a UTF-8 locale on the server)

Your message dated Mon, 05 Dec 2005 07:17:10 -0800 with message-id <[EMAIL PROTECTED]> and subject line Bug#232227: fixed in dictd 1.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 it is now you

Processed: closing old bug

Processing commands for [EMAIL PROTECTED]: > close 323876 Bug#323876: nagios-plugins: check_mysql does coredump on AMD64 architecture 'close' is deprecated; see http://www.debian.org/Bugs/Developer#closing. Bug closed, send any further explanations to Florian Fuessl <[EMAIL PROTECTED]> > thanks S

Bug#341199: marked as done (w3m: Mouse-in-xterm doesn't stay disabled)

Your message dated Mon, 5 Dec 2005 07:52:27 -0700 with message-id <[EMAIL PROTECTED]> and subject line Bug#341199: w3m: Mouse-in-xterm doesn't stay disabled has caused the attached 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

Bug#336081: marked as done (pbuilder: pdebuild creates incorrect diff.gz files)

Your message dated Mon, 05 Dec 2005 23:44:17 +0900 with message-id <[EMAIL PROTECTED]> and subject line [Pbuilder-maint] Bug#336081: Clean pbuilder environment has caused the 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

Bug#342099: marked as done (url bar does not respond to enter key or go button)

Your message dated Mon, 5 Dec 2005 15:25:00 +0100 with message-id <[EMAIL PROTECTED]> and subject line Bug#342099: url bar does not respond to enter key or go button has caused 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#338638: marked as done (tetex-base: dies when /usr/local/ read-only)

Your message dated Mon, 05 Dec 2005 06:02:23 -0800 with message-id <[EMAIL PROTECTED]> and subject line Bug#338638: fixed in tetex-base 2.0.2c-8sarge1 has caused the attached Bug report to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it

Processed: your mail

Processing commands for [EMAIL PROTECTED]: > close 315734 Bug#315734: frozen order drives line totals crazy 'close' is deprecated; see http://www.debian.org/Bugs/Developer#closing. Bug closed, send any further explanations to Max Alekseyev <[EMAIL PROTECTED]> > thanks Stopping processing here. P

Bug#339891: marked as done (evms: corrupts RAID-5 volumes when running in degraded mode)

Your message dated Mon, 5 Dec 2005 14:04:58 +0100 with message-id <[EMAIL PROTECTED]> and subject line Processed: Fixed in NMU of evms 2.5.2-1.testing1 has caused the attached Bug 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

  1   2   >