Bug#328602: marked as done (RFA: redir -- Redirect TCP connections)

Your message dated Fri, 21 Oct 2005 22:32:06 -0700 with message-id <[EMAIL PROTECTED]> and subject line Bug#328602: fixed in redir 2.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 your

Bug#139197: marked as done (Bandwidth throttling for redir'd connections [patch])

Your message dated Fri, 21 Oct 2005 22:32:06 -0700 with message-id <[EMAIL PROTECTED]> and subject line Bug#139197: fixed in redir 2.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 your

Bug#147061: marked as done (redir: new version available)

Your message dated Fri, 21 Oct 2005 22:32:06 -0700 with message-id <[EMAIL PROTECTED]> and subject line Bug#147061: fixed in redir 2.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 your

Bug#324935: marked as done (base64-decode fails on valid data without error status)

Your message dated Fri, 21 Oct 2005 23:28:02 -0500 with message-id <[EMAIL PROTECTED]> and subject line Apparently, VM's implementation follows RFC 2045 has caused the attached Bug 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#215733: marked as done (Oficial imlib11 .deb crashes Enlightenment with illegal instruction on k6)

Your message dated Fri, 21 Oct 2005 21:29:53 -0700 with message-id <[EMAIL PROTECTED]> and subject line fixit has caused the attached Bug report to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the

Bug#296011: marked as done (kernel hardware autodetection fails to detect the SupraExpress 56i Sp Intl )

Your message dated Sat, 22 Oct 2005 04:43:37 +0200 with message-id <[EMAIL PROTECTED]> and subject line kernel hardware autodetection fails to detect the SupraExpress 56i Sp Intl has caused the attached Bug report to be marked as done. This means that you claim that the problem has been dealt wit

Bug#334244: marked as done (ITA: bibcursed -- An interactive program to edit BibTeX bibliographies)

Your message dated Fri, 21 Oct 2005 18:39:11 -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

Processed: Re: Bug#335107: konqueror: omit

Processing commands for [EMAIL PROTECTED]: > close 335106 Bug#335106: konqueror: cannot copynpaste for smb target home subfolders 'close' is deprecated; see http://www.debian.org/Bugs/Developer#closing. Bug closed, send any further explanations to - <[EMAIL PROTECTED]> > close 335107 Bug#335107:

Bug#335100: marked as done (freeradius missing /etc/init.d/freeradius)

Your message dated Fri, 21 Oct 2005 16:21:42 -0700 with message-id <[EMAIL PROTECTED]> and subject line Bug#335100: freeradius missing /etc/init.d/freeradius has caused the attached 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#231095: marked as done (valgrind-calltree: calltree terminates with SIGSEV on call to calloc.)

Your message dated Sat, 22 Oct 2005 00:36:47 +0200 with message-id <[EMAIL PROTECTED]> and subject line [EMAIL PROTECTED]: Bug#231095: valgrind-calltree: calltree terminates with SIGSEV on call to calloc.] has caused the attached Bug report to be marked as done. This means that you claim that the

Bug#334234: marked as done (clisp: configure gets rerun gratuitiously)

Your message dated Fri, 21 Oct 2005 15:32:07 -0700 with message-id <[EMAIL PROTECTED]> and subject line Bug#334234: fixed in clisp 1:2.35-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 you

Bug#330052: marked as done (INTL [l10n:pt_PT] Portuguese translation for apticron)

Your message dated Fri, 21 Oct 2005 15:17:09 -0700 with message-id <[EMAIL PROTECTED]> and subject line Bug#330052: fixed in apticron 1.1.13 has caused the attached Bug report to be 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#323723: marked as done (apticron: Sort list of packages to be updated)

Your message dated Fri, 21 Oct 2005 15:17:09 -0700 with message-id <[EMAIL PROTECTED]> and subject line Bug#323723: fixed in apticron 1.1.13 has caused the attached Bug report to be 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#328989: marked as done (apticron: should not stop if apt-get update fails)

Your message dated Fri, 21 Oct 2005 15:17:09 -0700 with message-id <[EMAIL PROTECTED]> and subject line Bug#328989: fixed in apticron 1.1.13 has caused the attached Bug report to be 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#316416: marked as done (apticron: depending on Essential packages)

Your message dated Fri, 21 Oct 2005 15:17:09 -0700 with message-id <[EMAIL PROTECTED]> and subject line Bug#316416: fixed in apticron 1.1.13 has caused the attached Bug report to be 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#331479: marked as done (gnus: [INTL:sv] Swedish debconf templates translation)

Your message dated Fri, 21 Oct 2005 14:32:10 -0700 with message-id <[EMAIL PROTECTED]> and subject line Bug#331479: fixed in gnus 5.10.6-1.NO.20051020-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

Bug#335092: marked as done (orpheus: Package description shoudl mention "CD only" - not general play utility)

Your message dated Fri, 21 Oct 2005 23:21:47 +0200 with message-id <[EMAIL PROTECTED]> and subject line Bug#335092: orpheus: Package description shoudl mention "CD only" - not general play utility has caused the attached Bug report to be marked as done. This means that you claim that the problem

Bug#334761: marked as done (belocs-locale-data: Please add a locale for Khmer/Cambodia)

Your message dated Fri, 21 Oct 2005 22:43:11 +0200 with message-id <[EMAIL PROTECTED]> and subject line Bug#334761: belocs-locale-data: Please add a locale for Khmer/Cambodia 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#335089: marked as done (tpctl: apmiser shouldn't be automatically installed)

Your message dated Fri, 21 Oct 2005 22:56:14 +0200 with message-id <[EMAIL PROTECTED]> and subject line Bug#335089: tpctl: apmiser shouldn't be automatically installed has caused the attached Bug report to be marked as done. This means that you claim that the problem has been dealt with. If this i

Bug#334975: marked as done (rhdb-explain: FTBFS: Missing Build-Depends on 'cdbs')

Your message dated Fri, 21 Oct 2005 13:32:28 -0700 with message-id <[EMAIL PROTECTED]> and subject line Bug#334975: fixed in rhdb-explain 2.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

Processed: close-bug

Processing commands for [EMAIL PROTECTED]: > package qterm Ignoring bugs not assigned to: qterm > close 323713 0.4.0pre2.ds.3-2 Bug#323713: qterm should depend on libqt3-mt not libqt3c102-mt now 'close' is deprecated; see http://www.debian.org/Bugs/Developer#closing. Bug marked as fixed in versio

Bug#334999: marked as done (FTBFS on arm/hppa/m68k: please use g++-3.4)

Your message dated Fri, 21 Oct 2005 11:47:13 -0700 with message-id <[EMAIL PROTECTED]> and subject line Bug#334999: fixed in monotone 0.23-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#332794: marked as done (lprof: FTBFS on 64 bit arches: cast from 'void*' to 'int' loses precision)

Your message dated Fri, 21 Oct 2005 11:59:58 -0600 with message-id <[EMAIL PROTECTED]> and subject line close #332794 has caused the attached Bug report to be 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#335030: marked as done (aptitude: resolution bug (not in apt-get))

Your message dated Fri, 21 Oct 2005 10:41:40 -0700 with message-id <[EMAIL PROTECTED]> and subject line Bug#335030: aptitude: resolution bug (not in apt-get) has caused the attached 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#269586: marked as done (segfault in samba)

Your message dated Fri, 21 Oct 2005 17:59:21 +0200 with message-id <[EMAIL PROTECTED]> and subject line Bug#269586: Debian samba bugs triggered by a samba panic action has caused the attached Bug report to be marked as done. This means that you claim that the problem has been dealt with. If this i

Bug#334584: marked as done (udev-udeb: /lib/hotplug/*.agent not executable)

Your message dated Fri, 21 Oct 2005 10:02:12 -0700 with message-id <[EMAIL PROTECTED]> and subject line Bug#334584: fixed in udev 0.071-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#334439: marked as done (udev: /dev/fuse node is created with wrong group owner)

Your message dated Fri, 21 Oct 2005 10:02:12 -0700 with message-id <[EMAIL PROTECTED]> and subject line Bug#334439: fixed in udev 0.071-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#334232: marked as done (udev: wrong hint about CONFIG_ISAPNP)

Your message dated Fri, 21 Oct 2005 10:02:12 -0700 with message-id <[EMAIL PROTECTED]> and subject line Bug#334232: fixed in udev 0.071-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#334179: marked as done (udev 0.070-1 breaks dvb when /bin/sh != bash)

Your message dated Fri, 21 Oct 2005 10:02:12 -0700 with message-id <[EMAIL PROTECTED]> and subject line Bug#334179: fixed in udev 0.071-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#324505: marked as done (kde-icons-nuovext: Includes text files under /usr/share/icons)

Your message dated Fri, 21 Oct 2005 18:54:08 +0200 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 reop

Bug#304055: marked as done (smail: cron.daily script invokes checkerr, which must be run as root, via su mail)

Your message dated Fri, 21 Oct 2005 18:47:55 +0200 with message-id <[EMAIL PROTECTED]> and subject line Closing already fixed 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 responsi

Bug#329423: marked as done (hibernate: X status report doesn't kill xmessage)

Your message dated Sat, 22 Oct 2005 00:04:01 +0800 with message-id <[EMAIL PROTECTED]> and subject line Bug#329423: hibernate: X status report doesn't kill xmessage has caused 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#334085: marked as done (: should change dependency on passwd)

Your message dated Fri, 21 Oct 2005 12:10:07 -0400 with message-id <[EMAIL PROTECTED]> and subject line oops has caused the attached Bug report to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the

Bug#269053: marked as done (bubblefishymon: misbehaviour on Linux 2.6)

Your message dated Fri, 21 Oct 2005 14:05:21 -0200 with message-id <[EMAIL PROTECTED]> and subject line bubblefishymon: misbehaviour on Linux 2.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 n

Bug#301428: marked as done (smail: security: heap overflow.)

Your message dated Fri, 21 Oct 2005 18:10:56 +0200 with message-id <[EMAIL PROTECTED]> and subject line has caused the attached Bug report to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug

Bug#334406: marked as done (reduce priority of common-lisp-control's asdf repository)

Your message dated Fri, 21 Oct 2005 08:47:08 -0700 with message-id <[EMAIL PROTECTED]> and subject line Bug#334406: fixed in common-lisp-controller 4.21 has caused the attached Bug report to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case

Bug#334976: marked as done (cl-cil: FTBFS: Missing Build-Depends on 'dh-lisp')

Your message dated Fri, 21 Oct 2005 08:47:05 -0700 with message-id <[EMAIL PROTECTED]> and subject line Bug#334976: fixed in cl-cil 1:20050701-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 no

Bug#334550: marked as done (common-lisp-controller: Spanish debconf translation)

Your message dated Fri, 21 Oct 2005 08:47:08 -0700 with message-id <[EMAIL PROTECTED]> and subject line Bug#334550: fixed in common-lisp-controller 4.21 has caused the attached Bug report to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case

Bug#334167: marked as done (Incomplete CXX transition)

Your message dated Fri, 21 Oct 2005 08:32:12 -0700 with message-id <[EMAIL PROTECTED]> and subject line Bug#334167: fixed in pinball 0.3.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#334189: marked as done (common-lisp-controller: [INTL:sv] Swedish debconf templates translation)

Your message dated Fri, 21 Oct 2005 08:47:08 -0700 with message-id <[EMAIL PROTECTED]> and subject line Bug#334189: fixed in common-lisp-controller 4.21 has caused the attached Bug report to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case

Bug#335014: marked as done (zsh: please update xmllint completions (for options))

Your message dated Fri, 21 Oct 2005 08:32:17 -0700 with message-id <[EMAIL PROTECTED]> and subject line Bug#335014: fixed in zsh 4.2.5-21 has caused the attached Bug report to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your

Bug#335010: marked as done (simulpic bug in sublw)

Your message dated Fri, 21 Oct 2005 07:32:09 -0700 with message-id <[EMAIL PROTECTED]> and subject line Bug#335010: fixed in simulpic 1:2005-1-28-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

Bug#40148: marked as done (m4: Should set exit-code to non-zero on error.)

Your message dated Fri, 21 Oct 2005 07:32:07 -0700 with message-id <[EMAIL PROTECTED]> and subject line Bug#46403: fixed in m4 1.4.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 res

Bug#46403: marked as done (m4 exits 0 on error)

Your message dated Fri, 21 Oct 2005 07:32:07 -0700 with message-id <[EMAIL PROTECTED]> and subject line Bug#46403: fixed in m4 1.4.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 res

Bug#46403: marked as done (m4 exits 0 on error)

Your message dated Fri, 21 Oct 2005 07:32:07 -0700 with message-id <[EMAIL PROTECTED]> and subject line Bug#40148: fixed in m4 1.4.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 res

Bug#40148: marked as done (m4: Should set exit-code to non-zero on error.)

Your message dated Fri, 21 Oct 2005 07:32:07 -0700 with message-id <[EMAIL PROTECTED]> and subject line Bug#40148: fixed in m4 1.4.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 res

Bug#335003: marked as done (/var/log/syslog is at VT4)

Your message dated Fri, 21 Oct 2005 15:37:17 +0200 with message-id <[EMAIL PROTECTED]> and subject line Bug#335003: /var/log/syslog is at VT4 has caused the attached Bug report to be 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#295478: marked as done (openoffice.org: lock files put in wrong place)

Your message dated Fri, 21 Oct 2005 15:41:17 +0200 with message-id <[EMAIL PROTECTED]> and subject line openoffice.org: lock files put in wrong place has caused the attached Bug report 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#285350: marked as done (symbol "lightning-bolt" not explained in partman's-helppage)

Your message dated Fri, 21 Oct 2005 06:47:09 -0700 with message-id <[EMAIL PROTECTED]> and subject line Bug#285350: fixed in partman-base 73 has caused the attached Bug report to be 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#269418: marked as done (kopete: Pressing read on bubble does not give focus to new window)

Your message dated Fri, 21 Oct 2005 15:35:58 +0200 with message-id <[EMAIL PROTECTED]> and subject line kopete: Pressing read on bubble does not give focus to new window has caused the attached Bug report to be marked as done. This means that you claim that the problem has been dealt with. If thi

Bug#162908: marked as done (Better ways to do /etc/init.d/firebird stop [database shutdown])

Your message dated Fri, 21 Oct 2005 16:05:29 +0300 with message-id <[EMAIL PROTECTED]> and subject line Better ways to do /etc/init.d/firebird stop [database shutdown] has caused the attached Bug report to be marked as done. This means that you claim that the problem has been dealt with. If this i

Processed: Re: [Pkg-firebird-general] Bug#299983: marked as done (firebird2-super-server: package description typo(s) and the like)

Processing commands for [EMAIL PROTECTED]: > found 283911 Bug#283911: firebird2: FTBFS with kerberos4kth-dev 1.2.2-11: undefined reference to `strunvis' Bug reopened. > found 329330 Bug#329330: libfbclient1: long description lacks everything Bug reopened. > found 322199 Bug#322199: firebird2-cl

Processed: Re: [Pkg-firebird-general] Bug#299983: marked as done (firebird2-super-server: package description typo(s) and the like)

Processing commands for [EMAIL PROTECTED]: > found 299983 Bug#299983: firebird2-super-server: package description typo(s) and the like Bug reopened. > close 299983 1.5.2-9 Bug#299983: firebird2-super-server: package description typo(s) and the like 'close' is deprecated; see http://www.debian.org

Bug#330074: marked as done (firebird2-classic-server: installation not correct if inetd is installed and xinetd was removed earlier)

Your message dated Fri, 21 Oct 2005 15:41:07 +0300 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#299983: marked as done (firebird2-super-server: package description typo(s) and the like)

Your message dated Fri, 21 Oct 2005 15:01:08 +0300 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#262343: marked as done (irc: nickname conflation)

Your message dated Fri, 21 Oct 2005 13:51:09 +0200 with message-id <[EMAIL PROTECTED]> and subject line irc: nickname conflation has caused the attached Bug report to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsib

Bug#259702: marked as done (kopete: AIM error message are broken, doesn't ask for a password)

Your message dated Fri, 21 Oct 2005 13:32:47 +0200 with message-id <[EMAIL PROTECTED]> and subject line kopete: AIM error message are broken, doesn't ask for a password has 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#329488: marked as done (clustalw-mpi: needs rebuild for lam transition)

Your message dated Fri, 21 Oct 2005 03:47:04 -0700 with message-id <[EMAIL PROTECTED]> and subject line Bug#329488: fixed in clustalw-mpi 0.13-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 no

Bug#194101: marked as done (phpwiki: Automatic login from $_SERVER["PHP_AUTH_USER"] would be nice)

Your message dated Fri, 21 Oct 2005 23:33:15 +1300 with message-id <[EMAIL PROTECTED]> and subject line Functionality supported upstream now has caused the attached Bug report to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now yo

Bug#251604: marked as done (kopete: does not remeber passwords)

Your message dated Fri, 21 Oct 2005 12:30:17 +0200 with message-id <[EMAIL PROTECTED]> and subject line kopete: does not remeber passwords has caused the attached Bug report to be 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#227641: marked as done (nettoe: doesn't know about reuseaddr)

Your message dated Fri, 21 Oct 2005 03:17:14 -0700 with message-id <[EMAIL PROTECTED]> and subject line Bug#227641: fixed in nettoe 1.1.0-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#334980: marked as done (dhcp3-server: goes into infinite loop and fill syslog if started with this bad configuration file)

Your message dated Fri, 21 Oct 2005 19:27:41 +1000 with message-id <[EMAIL PROTECTED]> and subject line Bug#334980: dhcp3-server: goes into infinite loop and fill syslog if started with this bad configuration file has caused the attached Bug report to be marked as done. This means that you claim

Bug#334814: marked as done (ieee80211-source: Does not build)

Your message dated Fri, 21 Oct 2005 02:02:08 -0700 with message-id <[EMAIL PROTECTED]> and subject line Bug#334814: fixed in ieee80211 1.1.5-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

Bug#313933: marked as done (pavuk: [INTL:de] German PO file corrections)

Your message dated Fri, 21 Oct 2005 01:47:08 -0700 with message-id <[EMAIL PROTECTED]> and subject line Bug#313933: fixed in pavuk 0.9.33-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#264684: marked as done (DSA-527-1 not fixed in unstable)

Your message dated Fri, 21 Oct 2005 01:47:08 -0700 with message-id <[EMAIL PROTECTED]> and subject line Bug#264684: fixed in pavuk 0.9.33-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#276104: marked as done (kopete: Doesn't keep toolbar settings.)

Your message dated Fri, 21 Oct 2005 10:23:26 +0200 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#248524: marked as done (please upgrade to newer BDB)

Your message dated Fri, 21 Oct 2005 01:47:08 -0700 with message-id <[EMAIL PROTECTED]> and subject line Bug#248524: fixed in pavuk 0.9.33-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#334919: marked as done (ant 1.6.5 fails on custom task, where ant 1.6.2 succeeded.)

Your message dated Fri, 21 Oct 2005 09:54:21 +0200 (MEST) with message-id <[EMAIL PROTECTED]> and subject line Bug#334919: ant 1.6.5 fails on custom task, where ant 1.6.2 succeeded. has caused the attached Bug report to be marked as done. This means that you claim that the problem has been de

Bug#309005: marked as done (bugs in cmd line params and documentation)

Your message dated Fri, 21 Oct 2005 07:58:38 + with message-id <[EMAIL PROTECTED]> and subject line fixed in bincimap 1.2.14beta2-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 re

Bug#318413: marked as done (xlibs: Backslash Key is broken on Japanese Keyboards)

Your message dated Fri, 21 Oct 2005 16:42:54 +0900 with message-id <[EMAIL PROTECTED]> and subject line Bug#318413: xlibs: Backslash Key is broken on Japanese Keyboards has 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#322199: marked as done (firebird2-classic-server: Missing sql for functions of ib_udf and fbudf)

Your message dated Fri, 21 Oct 2005 10:21:06 +0300 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#329330: marked as done (libfbclient1: long description lacks everything)

Your message dated Fri, 21 Oct 2005 10:21:06 +0300 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#283911: marked as done (firebird2: FTBFS with kerberos4kth-dev 1.2.2-11: undefined reference to `strunvis')

Your message dated Fri, 21 Oct 2005 10:21:06 +0300 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#328341: marked as done (gnotepad+: please rebuild against latest libpng)

Your message dated Fri, 21 Oct 2005 00:26:04 -0700 with message-id <[EMAIL PROTECTED]> and subject line gnotepad+: please rebuild against latest libpng has caused the attached Bug 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

Bug#299292: marked as done (samba: FTBFS (ppc64): cannot compute sizeof (int), 77)

Your message dated Fri, 21 Oct 2005 09:58:45 +0200 with message-id <[EMAIL PROTECTED]> and subject line samba: #299292 has been fixed has caused the attached Bug report to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your resp

Bug#322628: marked as done (yy_init_globals in header file)

Your message dated Thu, 20 Oct 2005 23:47:11 -0700 with message-id <[EMAIL PROTECTED]> and subject line Bug#322628: fixed in flex 2.5.31-35 has caused the attached Bug report to be 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#318347: marked as done (Please provide flex++ symlink)

Your message dated Thu, 20 Oct 2005 23:47:11 -0700 with message-id <[EMAIL PROTECTED]> and subject line Bug#318347: fixed in flex 2.5.31-35 has caused the attached Bug report to be 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#333321: marked as done (flex: [INTL:sv] Swedish debconf templates translation)

Your message dated Thu, 20 Oct 2005 23:47:11 -0700 with message-id <[EMAIL PROTECTED]> and subject line Bug#21: fixed in flex 2.5.31-35 has caused the attached Bug report to be 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