Processing of bfm_0.6.3-3_i386.changes

bfm_0.6.3-3_i386.changes uploaded successfully to localhost along with the files: bfm_0.6.3-3.dsc bfm_0.6.3-3.diff.gz bubblefishymon_0.6.3-3_i386.deb gkrellm-bfm_0.6.3-3_i386.deb Greetings, Your Debian queue daemon -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of

bfm_0.6.3-3_i386.changes ACCEPTED

Accepted: bfm_0.6.3-3.diff.gz to pool/main/b/bfm/bfm_0.6.3-3.diff.gz bfm_0.6.3-3.dsc to pool/main/b/bfm/bfm_0.6.3-3.dsc bubblefishymon_0.6.3-3_i386.deb to pool/main/b/bfm/bubblefishymon_0.6.3-3_i386.deb gkrellm-bfm_0.6.3-3_i386.deb to pool/main/b/bfm/gkrellm-bfm_0.6.3-3_i386.deb Announcing

Processed: Fixed in NMU of mailliststat 1.3-3

Processing commands for [EMAIL PROTECTED]: > tag 300272 + fixed Bug#300272: mailliststat: FTBFS (amd64/gcc-4.0): array type has incomplete element type Tags were: patch Tags added: fixed > quit Stopping processing here. Please contact me if you need assistance. Debian bug tracking system admin

Bug#320698: Debian-specific binary deps patch

Package: libtool Version: 1.5.6-6 Severity: important Hi, It seems that Debian's libtool has a patch which will reduce dependencies in binaries it produces. It would be nice to bring this patch upstream, as the upstream maintainers not running Debian are libtoolizing without this spe

Bug#320714: twin: undefined symbol in tty driver

Package: twin Version: 0.4.0-7 Severity: important -- System Information: Debian Release: testing/unstable APT prefers unstable APT policy: (990, 'unstable') Architecture: i386 (i686) Shell: /bin/sh linked to /bin/bash Kernel: Linux 2.6.11-1-k7 Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8

Bug#95428: marked as done (suggestion: EZMLM report addresses that are bounce-unsubscribed)

Your message dated Sun, 31 Jul 2005 23:33:20 +0100 with message-id <[EMAIL PROTECTED]> and subject line Removed from Debian - unmaintained has caused the attached Bug report to be 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#67612: marked as done (jitterbug: you install the Package_name cgi as copy not lin)

Your message dated Sun, 31 Jul 2005 23:34:21 +0100 with message-id <[EMAIL PROTECTED]> and subject line Removed from Debian - unmaintained has caused the attached Bug report to be 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#67384: marked as done (fields are too large when looking at individual records)

Your message dated Sun, 31 Jul 2005 23:32:33 +0100 with message-id <[EMAIL PROTECTED]> and subject line Removed from Debian - unmaintained has caused the attached Bug report to be 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#55507: marked as done (problem with setuid/setgid of /usr/cgi-bin/jitterbug)

Your message dated Sun, 31 Jul 2005 23:34:21 +0100 with message-id <[EMAIL PROTECTED]> and subject line Removed from Debian - unmaintained has caused the attached Bug report to be 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#40978: marked as done (ftape-module-2.0.35: File /etc/modutils/ftape-util configuration fails)

Your message dated Sun, 31 Jul 2005 23:34:00 +0100 with message-id <[EMAIL PROTECTED]> and subject line Removed from Debian - unmaintained has caused the attached Bug report to be 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#317782: marked as done (INTL:vi Vietnamese translation for rio500)

Your message dated Sun, 31 Jul 2005 23:35:08 +0100 with message-id <[EMAIL PROTECTED]> and subject line Removed from Debian - unmaintained has caused the attached Bug report to be 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#313171: marked as done (INTL:vi)

Your message dated Sun, 31 Jul 2005 23:32:47 +0100 with message-id <[EMAIL PROTECTED]> and subject line Removed from Debian - unmaintained has caused the attached Bug report to be 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#312756: marked as done (ftape-util: Typo in debconf-template)

Your message dated Sun, 31 Jul 2005 23:34:00 +0100 with message-id <[EMAIL PROTECTED]> and subject line Removed from Debian - unmaintained has caused the attached Bug report to be 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#303700: marked as done (Please build-depend on libpng12-dev)

Your message dated Sun, 31 Jul 2005 23:34:48 +0100 with message-id <[EMAIL PROTECTED]> and subject line Removed from Debian - unmaintained has caused the attached Bug report to be 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#66602: marked as done (ftape-util: Cannot format tapes with current driver in kernel)

Your message dated Sun, 31 Jul 2005 23:34:00 +0100 with message-id <[EMAIL PROTECTED]> and subject line Removed from Debian - unmaintained has caused the attached Bug report to be 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#311569: marked as done (wordinspect: Constant core dump with multiwords (** WARNING **: dict exited abnormally))

Your message dated Sun, 31 Jul 2005 23:35:51 +0100 with message-id <[EMAIL PROTECTED]> and subject line Removed from Debian - unmaintained has caused the attached Bug report to be 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#44460: marked as done (Fails to comply with the proposed Java Policy)

Your message dated Sun, 31 Jul 2005 23:32:41 +0100 with message-id <[EMAIL PROTECTED]> and subject line Removed from Debian - unmaintained has caused the attached Bug report to be 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#318278: marked as done ([l10n] Initial Czech translation of mifluz debconf messagesd)

Your message dated Sun, 31 Jul 2005 23:34:53 +0100 with message-id <[EMAIL PROTECTED]> and subject line Removed from Debian - unmaintained has caused the attached Bug report to be 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#314113: marked as done (ftape-tools: [INTL:de] German PO file corrections)

Your message dated Sun, 31 Jul 2005 23:34:00 +0100 with message-id <[EMAIL PROTECTED]> and subject line Removed from Debian - unmaintained has caused the attached Bug report to be 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#297950: marked as done (ttfprint: FTBFS (amd64/gcc-4.0): invalid lvalue in assignment)

Your message dated Sun, 31 Jul 2005 23:35:42 +0100 with message-id <[EMAIL PROTECTED]> and subject line Removed from Debian - unmaintained has caused the attached Bug report to be 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#28957: marked as done (ipautofw cleanup (PATCH))

Your message dated Sun, 31 Jul 2005 23:34:14 +0100 with message-id <[EMAIL PROTECTED]> and subject line Removed from Debian - unmaintained has caused the attached Bug report to be 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#288773: marked as done (wordinspect: wrong behavior for non english languages)

Your message dated Sun, 31 Jul 2005 23:35:51 +0100 with message-id <[EMAIL PROTECTED]> and subject line Removed from Debian - unmaintained has caused the attached Bug report to be 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#282585: marked as done (gpppkill: black screen under heavy load)

Your message dated Sun, 31 Jul 2005 23:34:09 +0100 with message-id <[EMAIL PROTECTED]> and subject line Removed from Debian - unmaintained has caused the attached Bug report to be 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#281341: marked as done (Tries to use version 2 bind which is disabled by default)

Your message dated Sun, 31 Jul 2005 23:34:29 +0100 with message-id <[EMAIL PROTECTED]> and subject line Removed from Debian - unmaintained has caused the attached Bug report to be 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#269420: marked as done (libapache-auth-ldap: apache-modconf should be used instead)

Your message dated Sun, 31 Jul 2005 23:34:29 +0100 with message-id <[EMAIL PROTECTED]> and subject line Removed from Debian - unmaintained has caused the attached Bug report to be 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#268503: marked as done (epic4-script-thirdeye: Incorrect use of "it's" in package description)

Your message dated Sun, 31 Jul 2005 23:33:10 +0100 with message-id <[EMAIL PROTECTED]> and subject line Removed from Debian - unmaintained has caused the attached Bug report to be 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#264172: marked as done (xwave: FTBFS: *orig.tar.gz sets 2755 permissions)

Your message dated Sun, 31 Jul 2005 23:36:05 +0100 with message-id <[EMAIL PROTECTED]> and subject line Removed from Debian - unmaintained has caused the attached Bug report to be 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#261525: marked as done (zircon: under TK 8.4 some menus are not functioning)

Your message dated Sun, 31 Jul 2005 23:36:16 +0100 with message-id <[EMAIL PROTECTED]> and subject line Removed from Debian - unmaintained has caused the attached Bug report to be 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#259415: marked as done (ezmlm-src: Does undocumented reject Precedence: bulk mails as well)

Your message dated Sun, 31 Jul 2005 23:33:20 +0100 with message-id <[EMAIL PROTECTED]> and subject line Removed from Debian - unmaintained has caused the attached Bug report to be 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#265288: marked as done (add support for iso-8859-1)

Your message dated Sun, 31 Jul 2005 23:32:47 +0100 with message-id <[EMAIL PROTECTED]> and subject line Removed from Debian - unmaintained has caused the attached Bug report to be 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#257686: marked as done (bibview: Major loss of data -- no save on exit)

Your message dated Sun, 31 Jul 2005 23:32:33 +0100 with message-id <[EMAIL PROTECTED]> and subject line Removed from Debian - unmaintained has caused the attached Bug report to be 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#248463: marked as done (zircon: will not quit on menu option)

Your message dated Sun, 31 Jul 2005 23:36:16 +0100 with message-id <[EMAIL PROTECTED]> and subject line Removed from Debian - unmaintained has caused the attached Bug report to be 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#246343: marked as done (bibview: Confusing informational message)

Your message dated Sun, 31 Jul 2005 23:32:33 +0100 with message-id <[EMAIL PROTECTED]> and subject line Removed from Debian - unmaintained has caused the attached Bug report to be 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#232800: marked as done (Half-broken dependency on emacs20)

Your message dated Sun, 31 Jul 2005 23:35:57 +0100 with message-id <[EMAIL PROTECTED]> and subject line Removed from Debian - unmaintained has caused the attached Bug report to be 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#228569: marked as done (jitterbug: Please update Dependencies to exim4)

Your message dated Sun, 31 Jul 2005 23:34:21 +0100 with message-id <[EMAIL PROTECTED]> and subject line Removed from Debian - unmaintained has caused the attached Bug report to be 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#201554: marked as done (ftape-source: ftape fails to build against 2.6[-test])

Your message dated Sun, 31 Jul 2005 23:34:00 +0100 with message-id <[EMAIL PROTECTED]> and subject line Removed from Debian - unmaintained has caused the attached Bug report to be 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#200476: marked as done (rtf2latex generates invalid LaTeX files (\` in math mode))

Your message dated Sun, 31 Jul 2005 23:35:15 +0100 with message-id <[EMAIL PROTECTED]> and subject line Removed from Debian - unmaintained has caused the attached Bug report to be 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#225003: marked as done (libtest-unit-perl: Can't locate Error.pm)

Your message dated Sun, 31 Jul 2005 23:34:36 +0100 with message-id <[EMAIL PROTECTED]> and subject line Removed from Debian - unmaintained has caused the attached Bug report to be 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#182638: marked as done (xae: please make `xae-mode' interactive )

Your message dated Sun, 31 Jul 2005 23:35:57 +0100 with message-id <[EMAIL PROTECTED]> and subject line Removed from Debian - unmaintained has caused the attached Bug report to be 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#206757: marked as done (rtf2latex: LaTeX Error: Command \guillemotleft unavailable in encoding OT1.)

Your message dated Sun, 31 Jul 2005 23:35:15 +0100 with message-id <[EMAIL PROTECTED]> and subject line Removed from Debian - unmaintained has caused the attached Bug report to be 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#197127: marked as done (causes screen to garble xterm titles)

Your message dated Sun, 31 Jul 2005 23:33:10 +0100 with message-id <[EMAIL PROTECTED]> and subject line Removed from Debian - unmaintained has caused the attached Bug report to be 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#154236: marked as done (bock: Warning: .stabn: description field '10001' too big)

Your message dated Sun, 31 Jul 2005 23:32:41 +0100 with message-id <[EMAIL PROTECTED]> and subject line Removed from Debian - unmaintained has caused the attached Bug report to be 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#196597: marked as done (race: New upstream version available)

Your message dated Sun, 31 Jul 2005 23:35:02 +0100 with message-id <[EMAIL PROTECTED]> and subject line Removed from Debian - unmaintained has caused the attached Bug report to be 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#193354: marked as done (rio500: 128M smartmedia problem)

Your message dated Sun, 31 Jul 2005 23:35:08 +0100 with message-id <[EMAIL PROTECTED]> and subject line Removed from Debian - unmaintained has caused the attached Bug report to be 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#186130: marked as done (jitterbug: Jitterbug should substitute ALL instances of %PRNUM% in autoreply.txt)

Your message dated Sun, 31 Jul 2005 23:34:21 +0100 with message-id <[EMAIL PROTECTED]> and subject line Removed from Debian - unmaintained has caused the attached Bug report to be 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#184828: marked as done (bibview: man page for bibview)

Your message dated Sun, 31 Jul 2005 23:32:33 +0100 with message-id <[EMAIL PROTECTED]> and subject line Removed from Debian - unmaintained has caused the attached Bug report to be 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#178766: marked as done (w3mir: should decode content-encoding: gzip)

Your message dated Sun, 31 Jul 2005 23:35:46 +0100 with message-id <[EMAIL PROTECTED]> and subject line Removed from Debian - unmaintained has caused the attached Bug report to be 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#177982: marked as done (yencode: Ydecode can't decode multiple files from a single file)

Your message dated Sun, 31 Jul 2005 23:36:10 +0100 with message-id <[EMAIL PROTECTED]> and subject line Removed from Debian - unmaintained has caused the attached Bug report to be 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#122917: marked as done (thirdeye: does not get an active channel with multi-channel joins)

Your message dated Sun, 31 Jul 2005 23:33:10 +0100 with message-id <[EMAIL PROTECTED]> and subject line Removed from Debian - unmaintained has caused the attached Bug report to be 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#168546: marked as done (xae: Error "External entity not found" when there is no DTD)

Your message dated Sun, 31 Jul 2005 23:35:57 +0100 with message-id <[EMAIL PROTECTED]> and subject line Removed from Debian - unmaintained has caused the attached Bug report to be 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#160816: marked as done (epic4-script-thirdeye: Since the upgrade of epic4 on 10 Sep, 2002, the alt- bindings no longer work.)

Your message dated Sun, 31 Jul 2005 23:33:10 +0100 with message-id <[EMAIL PROTECTED]> and subject line Removed from Debian - unmaintained has caused the attached Bug report to be 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#114319: marked as done (ftape-doc: Please Recommend ftape-util)

Your message dated Sun, 31 Jul 2005 23:34:00 +0100 with message-id <[EMAIL PROTECTED]> and subject line Removed from Debian - unmaintained has caused the attached Bug report to be 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#146965: marked as done (ezmlm-src: ezmlm-cron has incorrect location of qmail-inject binary)

Your message dated Sun, 31 Jul 2005 23:33:20 +0100 with message-id <[EMAIL PROTECTED]> and subject line Removed from Debian - unmaintained has caused the attached Bug report to be 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#139349: marked as done (color-errors in epic4-script-thirdeye)

Your message dated Sun, 31 Jul 2005 23:33:10 +0100 with message-id <[EMAIL PROTECTED]> and subject line Removed from Debian - unmaintained has caused the attached Bug report to be 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#114321: marked as done (ftape-doc: docs are confusing and self-contradictory; lack Debian info)

Your message dated Sun, 31 Jul 2005 23:34:00 +0100 with message-id <[EMAIL PROTECTED]> and subject line Removed from Debian - unmaintained has caused the attached Bug report to be 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#43257: marked as done (Add translation of mailing list messages)

Your message dated Sun, 31 Jul 2005 23:33:20 +0100 with message-id <[EMAIL PROTECTED]> and subject line Removed from Debian - unmaintained has caused the attached Bug report to be 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#31379: marked as done (netbase: No manpage for ipautofw)

Your message dated Sun, 31 Jul 2005 23:34:14 +0100 with message-id <[EMAIL PROTECTED]> and subject line Removed from Debian - unmaintained has caused the attached Bug report to be 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#273451: marked as done (race: Debian menu icon missing)

Your message dated Sun, 31 Jul 2005 23:35:02 +0100 with message-id <[EMAIL PROTECTED]> and subject line Removed from Debian - unmaintained has caused the attached Bug report to be 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#249678: marked as done (libtest-unit-perl: Three bugs in assert_deep_equals)

Your message dated Sun, 31 Jul 2005 23:34:36 +0100 with message-id <[EMAIL PROTECTED]> and subject line Removed from Debian - unmaintained has caused the attached Bug report to be 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#247081: marked as done (no man page for bg5ps, ttf2psm, etc.)

Your message dated Sun, 31 Jul 2005 23:32:20 +0100 with message-id <[EMAIL PROTECTED]> and subject line Removed from Debian - unmaintained has caused the attached Bug report to be 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#165192: marked as done (rio500 usbfs support and cleanups)

Your message dated Sun, 31 Jul 2005 23:35:08 +0100 with message-id <[EMAIL PROTECTED]> and subject line Removed from Debian - unmaintained has caused the attached Bug report to be 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#144640: marked as done (yencode: Doesn't work if locale != C)

Your message dated Sun, 31 Jul 2005 23:36:10 +0100 with message-id <[EMAIL PROTECTED]> and subject line Removed from Debian - unmaintained has caused the attached Bug report to be 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#144013: marked as done (xae: does not install with XEmacs without Emacs )

Your message dated Sun, 31 Jul 2005 23:35:57 +0100 with message-id <[EMAIL PROTECTED]> and subject line Removed from Debian - unmaintained has caused the attached Bug report to be 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#143670: marked as done (fda: Upstream location is bogus)

Your message dated Sun, 31 Jul 2005 23:33:28 +0100 with message-id <[EMAIL PROTECTED]> and subject line Removed from Debian - unmaintained has caused the attached Bug report to be 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#129211: marked as done (xwave: temporary files are not correctly removed)

Your message dated Sun, 31 Jul 2005 23:36:05 +0100 with message-id <[EMAIL PROTECTED]> and subject line Removed from Debian - unmaintained has caused the attached Bug report to be 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#120185: marked as done (ftape-source: Maintainer, please look at latests NMU before resuming your work)

Your message dated Sun, 31 Jul 2005 23:34:00 +0100 with message-id <[EMAIL PROTECTED]> and subject line Removed from Debian - unmaintained has caused the attached Bug report to be 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#320721: capi4hylafax: c2faxrecv segfaults when an incoming faxtransmission enters

Package: capi4hylafax Version: 1:01.02.03-10 Severity: grave Justification: renders package unusable c2faxrecv segfaults when a fax transmission comes in. I use a AVM B1 PCI V4.0-Card. Here are the interesting error messages: luggage:/var/log# dmesg|grep B1 b1pci: PCI BIOS reports AVM-B1 V4 at i/

Bug#120186: marked as done (ftape-util: Maintainer, please look at latests NMU before resuming your work)

Your message dated Sun, 31 Jul 2005 23:34:00 +0100 with message-id <[EMAIL PROTECTED]> and subject line Removed from Debian - unmaintained has caused the attached Bug report to be 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#120187: marked as done (ftape-doc: Maintainer, please look at latests NMU before resuming your work)

Your message dated Sun, 31 Jul 2005 23:34:00 +0100 with message-id <[EMAIL PROTECTED]> and subject line Removed from Debian - unmaintained has caused the attached Bug report to be 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#138909: marked as done (xae; patch to allow use of perl rather than java)

Your message dated Sun, 31 Jul 2005 23:35:57 +0100 with message-id <[EMAIL PROTECTED]> and subject line Removed from Debian - unmaintained has caused the attached Bug report to be 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#148850: marked as done (zircon: zircon loops. 85%+ cpu)

Your message dated Sun, 31 Jul 2005 23:36:16 +0100 with message-id <[EMAIL PROTECTED]> and subject line Removed from Debian - unmaintained has caused the attached Bug report to be 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#161128: marked as done (bg5ps: no way to turn off trailer)

Your message dated Sun, 31 Jul 2005 23:32:20 +0100 with message-id <[EMAIL PROTECTED]> and subject line Removed from Debian - unmaintained has caused the attached Bug report to be 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#161974: marked as done (yencode: Not compiled for large-file support)

Your message dated Sun, 31 Jul 2005 23:36:10 +0100 with message-id <[EMAIL PROTECTED]> and subject line Removed from Debian - unmaintained has caused the attached Bug report to be 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#169471: marked as done (xae: Exception java.lang.NoClassDefFoundError: xae/XMLToolServer)

Your message dated Sun, 31 Jul 2005 23:35:57 +0100 with message-id <[EMAIL PROTECTED]> and subject line Removed from Debian - unmaintained has caused the attached Bug report to be 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#195792: marked as done (libapache-auth-ldap: auth_ldap will not authenticate against 2.1.x slapd server)

Your message dated Sun, 31 Jul 2005 23:34:29 +0100 with message-id <[EMAIL PROTECTED]> and subject line Removed from Debian - unmaintained has caused the attached Bug report to be 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#197445: marked as done (libtest-unit-perl: Missing dependencies for libtest-unit-perl 0.24)

Your message dated Sun, 31 Jul 2005 23:34:36 +0100 with message-id <[EMAIL PROTECTED]> and subject line Removed from Debian - unmaintained has caused the attached Bug report to be 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#214632: marked as done (removing xae should remove site-start.d init file)

Your message dated Sun, 31 Jul 2005 23:35:57 +0100 with message-id <[EMAIL PROTECTED]> and subject line Removed from Debian - unmaintained has caused the attached Bug report to be 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#228760: marked as done (libapache-auth-ldap: mistakenly prohibits SSL (ldaps://) connections)

Your message dated Sun, 31 Jul 2005 23:34:29 +0100 with message-id <[EMAIL PROTECTED]> and subject line Removed from Debian - unmaintained has caused the attached Bug report to be 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#251797: marked as done (splitdigest.1.gz: config file location wrong)

Your message dated Sun, 31 Jul 2005 23:35:20 +0100 with message-id <[EMAIL PROTECTED]> and subject line Removed from Debian - unmaintained has caused the attached Bug report to be 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#261103: marked as done (bibview: Closing a leaf window shuts down the whole application)

Your message dated Sun, 31 Jul 2005 23:32:33 +0100 with message-id <[EMAIL PROTECTED]> and subject line Removed from Debian - unmaintained has caused the attached Bug report to be 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#277210: marked as done (package description typo(s) and the like)

Your message dated Sun, 31 Jul 2005 23:33:10 +0100 with message-id <[EMAIL PROTECTED]> and subject line Removed from Debian - unmaintained has caused the attached Bug report to be 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#287493: marked as done (lpkg: FTBFS (amd64/gcc-4.0): invalid lvalue in assignment)

Your message dated Sun, 31 Jul 2005 23:34:43 +0100 with message-id <[EMAIL PROTECTED]> and subject line Removed from Debian - unmaintained has caused the attached Bug report to be 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#299963: marked as done (cl-odcl: package description typo(s) and the like)

Your message dated Sun, 31 Jul 2005 23:33:04 +0100 with message-id <[EMAIL PROTECTED]> and subject line Removed from Debian - unmaintained has caused the attached Bug report to be 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#318533: marked as done (ftape-tools: FTBFS: Syntax error before '__FUNCTION__')

Your message dated Sun, 31 Jul 2005 23:34:00 +0100 with message-id <[EMAIL PROTECTED]> and subject line Removed from Debian - unmaintained has caused the attached Bug report to be 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#38990: marked as done (splitdigest can't split stdin)

Your message dated Sun, 31 Jul 2005 23:35:20 +0100 with message-id <[EMAIL PROTECTED]> and subject line Removed from Debian - unmaintained has caused the attached Bug report to be 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#47894: marked as done (images/back.gif does not exist)

Your message dated Sun, 31 Jul 2005 23:34:21 +0100 with message-id <[EMAIL PROTECTED]> and subject line Removed from Debian - unmaintained has caused the attached Bug report to be 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#88964: marked as done (LaTeX Error: Command \textquotedbl unavailable in encoding OT1.)

Your message dated Sun, 31 Jul 2005 23:35:15 +0100 with message-id <[EMAIL PROTECTED]> and subject line Removed from Debian - unmaintained has caused the attached Bug report to be 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