Bug#355218: marked as done (debchange: Default is now --increment ?!?)

Your message dated Sat, 4 Mar 2006 08:26:37 +0100 with message-id <[EMAIL PROTECTED]> and subject line This bug has never been reported. You haven't seen this bug. has caused the attached Bug report to be marked as done. This means that you claim that the problem has been dealt with. If this is no

Bug#351090: marked as done (gkrellm: no longer able to show sensors output since lm-sensors upgrade)

Your message dated Sat, 4 Mar 2006 07:53:53 +0100 with message-id <[EMAIL PROTECTED]> and subject line Recent upgrade fixed it. has caused the attached Bug report to be 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 responsibi

Bug#353311: marked as done (mrename: FTBFS: can't parse dependency)

Your message dated Sat, 4 Mar 2006 07:34:35 +0100 with message-id <[EMAIL PROTECTED]> and subject line wrong bug reopened has caused the attached Bug report to be 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#347050: marked as done (xlockmore: FTBFS: build-depends on removed xlibs-dev)

Your message dated Fri, 03 Mar 2006 19:17:18 -0800 with message-id <[EMAIL PROTECTED]> and subject line Bug#347050: fixed in xlockmore 1:5.21-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#63021: marked as done (xlockmore is missing the vtlock option)

Your message dated Fri, 03 Mar 2006 19:17:18 -0800 with message-id <[EMAIL PROTECTED]> and subject line Bug#63021: fixed in xlockmore 1:5.21-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#337467: marked as done (xlockmore: FTBFS: Unsatisfiable Build-Depends on xlibmesa-dev)

Your message dated Fri, 03 Mar 2006 19:17:18 -0800 with message-id <[EMAIL PROTECTED]> and subject line Bug#337467: fixed in xlockmore 1:5.21-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#323445: marked as done (xlockmore: New upstream version available)

Your message dated Fri, 03 Mar 2006 19:17:18 -0800 with message-id <[EMAIL PROTECTED]> and subject line Bug#323445: fixed in xlockmore 1:5.21-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#310598: marked as done (bash:[completion] renders "set" unusable)

Your message dated Sat, 4 Mar 2006 04:01:06 +0100 with message-id <[EMAIL PROTECTED]> and subject line bash:[completion] renders "set" unusable has caused the attached Bug report to be 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#307223: marked as done (xlockmore: manpage of xlock mentions vtlock option which is not supported)

Your message dated Fri, 03 Mar 2006 19:17:17 -0800 with message-id <[EMAIL PROTECTED]> and subject line Bug#307223: fixed in xlockmore 1:5.21-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#271558: marked as done ("echokeys" default changed, should be reverted)

Your message dated Fri, 03 Mar 2006 19:17:17 -0800 with message-id <[EMAIL PROTECTED]> and subject line Bug#271558: fixed in xlockmore 1:5.21-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#241925: marked as done (xlockmore-gl: xlock(1x) manpage unclear about `-vtlock' argument meanings)

Your message dated Fri, 03 Mar 2006 19:17:17 -0800 with message-id <[EMAIL PROTECTED]> and subject line Bug#241925: fixed in xlockmore 1:5.21-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#355209: marked as done (Installation Report for D-I beta 2 (Korean))

Your message dated Sat, 04 Mar 2006 03:53:31 +0100 with message-id <[EMAIL PROTECTED]> and subject line Bug#355209: Installation Report for D-I beta 2 (Korean) has caused the 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#355098: marked as done (debian-installer - FTBFS: Tries to use apt with key checks)

Your message dated Fri, 03 Mar 2006 18:34:09 -0800 with message-id <[EMAIL PROTECTED]> and subject line Bug#355098: fixed in debian-installer 20060304 has caused the attached Bug report 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#354451: marked as done (bash: Window size is wrong until the first command has run)

Your message dated Sat, 4 Mar 2006 03:48:09 +0100 with message-id <[EMAIL PROTECTED]> and subject line Window size is wrong until the first command has run has caused the attached Bug report to be marked as done. This means that you claim that the problem has been dealt with. If this is not the ca

Bug#352760: marked as done (bash: Error messages on completion after scp)

Your message dated Sat, 4 Mar 2006 03:40:25 +0100 with message-id <[EMAIL PROTECTED]> and subject line bash: Error messages on completion after scp has caused the attached Bug report 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#347695: marked as done (bash: segfault in "while read" loop)

Your message dated Sat, 4 Mar 2006 03:32:22 +0100 with message-id <[EMAIL PROTECTED]> and subject line bash: segfault in "while read" loop has caused the attached Bug report to be 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#345649: marked as done (bash: package includes /bin/sh)

Your message dated Sat, 4 Mar 2006 03:43:19 +0100 with message-id <[EMAIL PROTECTED]> and subject line bash: package includes /bin/sh has caused the attached Bug report to be 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#348111: marked as done (Xterm: no wrap long lines)

Your message dated Sat, 4 Mar 2006 03:37:13 +0100 with message-id <[EMAIL PROTECTED]> and subject line fixed in bash-3.1-3 has caused the attached Bug report to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility

Bug#343471: marked as done (bash: In the command line, problem when the line reaches the last column of the terminal)

Your message dated Sat, 4 Mar 2006 03:37:13 +0100 with message-id <[EMAIL PROTECTED]> and subject line fixed in bash-3.1-3 has caused the attached Bug report to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility

Bug#322489: marked as done (xlock: sh: fortune: command not found)

Your message dated Fri, 03 Mar 2006 21:43:21 -0500 with message-id <[EMAIL PROTECTED]> and subject line xlock fortune not found has caused the attached Bug report to be 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 responsibi

Bug#283624: marked as done (in marquee mode, xlockmore depends on fortune present)

Your message dated Fri, 03 Mar 2006 21:43:21 -0500 with message-id <[EMAIL PROTECTED]> and subject line xlock fortune not found has caused the attached Bug report to be 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 responsibi

Bug#349851: marked as done (gpe-contacts - FTBFS: Build-depends against not available package libcontactsdb-dev)

Your message dated Sat, 04 Mar 2006 02:12:58 + with message-id <[EMAIL PROTECTED]> and subject line Bug#349851: gpe-contacts - FTBFS: Build-depends against not available package libcontactsdb-dev has caused the attached Bug report to be marked as done. This means that you claim that the probl

Bug#333535: marked as done (didiwiki: strikethrough too eager and impossible to disable)

Your message dated Sat, 4 Mar 2006 01:53:48 + with message-id <[EMAIL PROTECTED]> and subject line you can disable strikethrough with exclamation mark has caused the attached Bug report to be marked as done. This means that you claim that the problem has been dealt with. If this is not the cas

Bug#351848: marked as done (Add uppercase MID for timidity in bash_completion)

Your message dated Fri, 03 Mar 2006 17:32:13 -0800 with message-id <[EMAIL PROTECTED]> and subject line Bug#351848: fixed in bash 3.1-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 re

Bug#345861: marked as done ([parameter expansion] Array member length expansion fails with nested index expression)

Your message dated Fri, 03 Mar 2006 17:32:13 -0800 with message-id <[EMAIL PROTECTED]> and subject line Bug#345861: fixed in bash 3.1-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 re

Bug#343628: marked as done (bash: command completion for 'scp' fails with 'unterminated s command')

Your message dated Fri, 03 Mar 2006 17:32:13 -0800 with message-id <[EMAIL PROTECTED]> and subject line Bug#343312: fixed in bash 3.1-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 re

Bug#348313: marked as done (bash: Bash completion with ssh doesn't work)

Your message dated Fri, 03 Mar 2006 17:32:13 -0800 with message-id <[EMAIL PROTECTED]> and subject line Bug#343312: fixed in bash 3.1-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 re

Bug#325056: marked as done (bash: [COMPLETION] misinformation in /etc/bash_completion)

Your message dated Fri, 03 Mar 2006 17:32:13 -0800 with message-id <[EMAIL PROTECTED]> and subject line Bug#325056: fixed in bash 3.1-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 re

Bug#344066: marked as done (bash: [COMPLETION] scp completion spews sed error instead)

Your message dated Fri, 03 Mar 2006 17:32:13 -0800 with message-id <[EMAIL PROTECTED]> and subject line Bug#343312: fixed in bash 3.1-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 re

Bug#343312: marked as done (bash_completion and new ssh settings cause sed parsing error)

Your message dated Fri, 03 Mar 2006 17:32:13 -0800 with message-id <[EMAIL PROTECTED]> and subject line Bug#343312: fixed in bash 3.1-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 re

Bug#343866: marked as done (error in /etc/bash_completion script)

Your message dated Fri, 03 Mar 2006 17:32:13 -0800 with message-id <[EMAIL PROTECTED]> and subject line Bug#343312: fixed in bash 3.1-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 re

Bug#342868: marked as done (bash: [COMPLETION] syntax error on sed call at _known_hosts())

Your message dated Fri, 03 Mar 2006 17:32:13 -0800 with message-id <[EMAIL PROTECTED]> and subject line Bug#343312: fixed in bash 3.1-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 re

Bug#340452: marked as done (completion support for mplayer *.mka and *.flac|*.mka for -audiofile)

Your message dated Fri, 03 Mar 2006 17:32:13 -0800 with message-id <[EMAIL PROTECTED]> and subject line Bug#340452: fixed in bash 3.1-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 re

Bug#327414: marked as done (bash: no completion for invoke-rc.d)

Your message dated Fri, 03 Mar 2006 17:32:13 -0800 with message-id <[EMAIL PROTECTED]> and subject line Bug#327414: fixed in bash 3.1-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 re

Bug#324169: marked as done (bash: [completion] Mercurical revision control bash completions available)

Your message dated Fri, 03 Mar 2006 17:32:13 -0800 with message-id <[EMAIL PROTECTED]> and subject line Bug#324169: fixed in bash 3.1-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 re

Bug#323824: marked as done (include attached /etc/bash_completion.d/dpkg-source file)

Your message dated Fri, 03 Mar 2006 17:32:13 -0800 with message-id <[EMAIL PROTECTED]> and subject line Bug#323824: fixed in bash 3.1-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 re

Bug#224543: marked as done (bash: monitor mode causes emacs as $EDITOR to hang on kernel 2.6)

Your message dated Fri, 03 Mar 2006 17:32:13 -0800 with message-id <[EMAIL PROTECTED]> and subject line Bug#224543: fixed in bash 3.1-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 re

Bug#354942: marked as done (bcm43xx-fwcutter: package does not configure with confusing error message)

Your message dated Fri, 03 Mar 2006 16:47:05 -0800 with message-id <[EMAIL PROTECTED]> and subject line Bug#354942: fixed in bcm43xx-fwcutter 20060108-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

Bug#352159: marked as done (bcron: group membership is not set up properly)

Your message dated Fri, 03 Mar 2006 16:47:07 -0800 with message-id <[EMAIL PROTECTED]> and subject line Bug#352159: fixed in bcron 0.09-4 has caused the attached Bug report to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your

Bug#333285: marked as done (xrestop: would be nice to be able to quit with 'q')

Your message dated Fri, 03 Mar 2006 17:02:15 -0800 with message-id <[EMAIL PROTECTED]> and subject line Bug#333285: fixed in xrestop 0.4-1 has caused the attached Bug report to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your

Bug#354630: marked as done (libgpevtype: implicit-pointer-conversion)

Your message dated Fri, 03 Mar 2006 16:32:13 -0800 with message-id <[EMAIL PROTECTED]> and subject line Bug#354630: fixed in libgpevtype 0.16-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#354458: marked as done (Kernel panic after upgrading initramfs-tools/klibc-utils/libklibc)

Your message dated Sat, 4 Mar 2006 00:56:58 +0100 with message-id <[EMAIL PROTECTED]> and subject line Bug#354458: Kernel panic after upgrading initramfs-tools/klibc-utils/libklibc has caused the attached Bug report to be marked as done. This means that you claim that the problem has been dealt w

Bug#355193: marked as done (Missing dependency libneon24 in sid)

Your message dated Sat, 4 Mar 2006 00:33:59 +0100 with message-id <[EMAIL PROTECTED]> and subject line Bug#355193: Missing dependency libneon24 in sid has caused the attached Bug report 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#354342: marked as done (FTBFS: can't find res_mkquery )

Your message dated Fri, 03 Mar 2006 15:32:11 -0800 with message-id <[EMAIL PROTECTED]> and subject line Bug#354342: fixed in mtr 0.69-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 re

Bug#305728: marked as done (mtr: -s and -p should be interchanged on manpage)

Your message dated Fri, 03 Mar 2006 15:32:11 -0800 with message-id <[EMAIL PROTECTED]> and subject line Bug#305728: fixed in mtr 0.69-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 re

Bug#257981: marked as done (FTBFS: broken Build-Depends automaken)

Your message dated Fri, 03 Mar 2006 15:32:11 -0800 with message-id <[EMAIL PROTECTED]> and subject line Bug#257981: fixed in mtr 0.69-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 re

Bug#166613: marked as done (mtr_0.51-1 (unstable): fails to build)

Your message dated Fri, 03 Mar 2006 15:32:11 -0800 with message-id <[EMAIL PROTECTED]> and subject line Bug#254089: fixed in mtr 0.69-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 re

Bug#320609: marked as done (Conformance with menu policy)

Your message dated Fri, 03 Mar 2006 15:32:11 -0800 with message-id <[EMAIL PROTECTED]> and subject line Bug#320609: fixed in mtr 0.69-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 re

Bug#301346: marked as done (mtr: does not resolve IP adresses if no nameserver specified in /etc/resolv.conf)

Your message dated Fri, 03 Mar 2006 15:32:11 -0800 with message-id <[EMAIL PROTECTED]> and subject line Bug#301346: fixed in mtr 0.69-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 re

Bug#254089: marked as done (FTBFS: test for res_mkquery is broken)

Your message dated Fri, 03 Mar 2006 15:32:11 -0800 with message-id <[EMAIL PROTECTED]> and subject line Bug#254089: fixed in mtr 0.69-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 re

Bug#166613: marked as done (mtr_0.51-1 (unstable): fails to build)

Your message dated Fri, 03 Mar 2006 15:32:11 -0800 with message-id <[EMAIL PROTECTED]> and subject line Bug#166613: fixed in mtr 0.69-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 re

Bug#254089: marked as done (FTBFS: test for res_mkquery is broken)

Your message dated Fri, 03 Mar 2006 15:32:11 -0800 with message-id <[EMAIL PROTECTED]> and subject line Bug#166613: fixed in mtr 0.69-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 re

Bug#354563: marked as done (git: new upstream version)

Your message dated Fri, 03 Mar 2006 14:47:08 -0800 with message-id <[EMAIL PROTECTED]> and subject line Bug#354563: fixed in git-core 1.2.4-1 has caused the attached Bug report to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now y

Bug#355170: marked as done (zlib: Please build-depend on libc6-dev-i386 on amd64.)

Your message dated Fri, 03 Mar 2006 13:47:38 -0800 with message-id <[EMAIL PROTECTED]> and subject line Bug#355170: fixed in zlib 1:1.2.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 yo

Bug#354310: marked as done (zlib1g-dev: doc gzclose versus gzerror)

Your message dated Fri, 03 Mar 2006 13:47:38 -0800 with message-id <[EMAIL PROTECTED]> and subject line Bug#354310: fixed in zlib 1:1.2.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 yo

Bug#302936: marked as done (cccd: Improper copyright file)

Your message dated Fri, 03 Mar 2006 13:47:12 -0800 with message-id <[EMAIL PROTECTED]> and subject line Bug#302936: fixed in cccd 0.3beta4-6 has caused the attached Bug report to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now yo

Bug#337992: marked as done (acidlab: sarge to sid upgrade mess with conffiles)

Your message dated Fri, 03 Mar 2006 13:47:09 -0800 with message-id <[EMAIL PROTECTED]> and subject line Bug#337992: fixed in acidlab 0.9.6b20-15 has caused the attached Bug report to 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#353407: marked as done (zlib1g-dev: Please document type of memory returned by gzerror())

Your message dated Fri, 03 Mar 2006 13:47:38 -0800 with message-id <[EMAIL PROTECTED]> and subject line Bug#353407: fixed in zlib 1:1.2.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 yo

Bug#341131: marked as done (acidlab: Can't delete alerts)

Your message dated Fri, 03 Mar 2006 13:47:09 -0800 with message-id <[EMAIL PROTECTED]> and subject line Bug#341131: fixed in acidlab 0.9.6b20-15 has caused the attached Bug report to 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#170548: marked as done (libsdl1.2debian-all: [aalib frontend] keyboard arrows do not work)

Your message dated Fri, 03 Mar 2006 13:47:23 -0800 with message-id <[EMAIL PROTECTED]> and subject line Bug#170548: fixed in libsdl1.2 1.2.9-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

Processed: Re: Bug#307833: Processed: Re: apt-file: broken. curl is needed

Processing commands for [EMAIL PROTECTED]: > reassign 307833 apt-file Bug#307833: apt-file: broken. curl is needed Bug#311329: apt-file depends IMHO on curl Bug#323970: apt-file should depend on curl Bug#324153: apt-file depends on curl which is not mentioned Bug#325102: apt-file should depend on

Processed: pyca

Processing commands for [EMAIL PROTECTED]: > package pyca Ignoring bugs not assigned to: pyca > tag 355177 +wontfix Bug#355177: /etc/pyca underdocumented There were no tags set. Tags added: wontfix > close 355177 Bug#355177: /etc/pyca underdocumented 'close' is deprecated; see http://www.debian.

Bug#349476: marked as done (mono: tomboy fails to start (segfault))

Your message dated Fri, 3 Mar 2006 22:04:21 +0200 with message-id <[EMAIL PROTECTED]> and subject line was mono: tomboy fails to start (segfault) has caused the attached Bug report to 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#354798: marked as done (tomboy: Tomboy won't start)

Your message dated Fri, 3 Mar 2006 11:47:15 -0800 with message-id <[EMAIL PROTECTED]> and subject line Bug#354798: tomboy: Tomboy won't start has caused the attached Bug report to be 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#336497: marked as done (libsdl-sge: new upstream available)

Your message dated Fri, 03 Mar 2006 11:02:08 -0800 with message-id <[EMAIL PROTECTED]> and subject line Bug#336497: fixed in libsdl-sge 030809-1 has caused the attached Bug report to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is no

Bug#318973: marked as done (libsdl-sge-dev: examples do not compile)

Your message dated Fri, 03 Mar 2006 11:02:08 -0800 with message-id <[EMAIL PROTECTED]> and subject line Bug#318973: fixed in libsdl-sge 030809-1 has caused the attached Bug report to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is no

Bug#332833: marked as done (libsdl-sge: Please recompile with g++-4.0 for C++ 'c2' transition)

Your message dated Fri, 03 Mar 2006 11:02:08 -0800 with message-id <[EMAIL PROTECTED]> and subject line Bug#332833: fixed in libsdl-sge 030809-1 has caused the attached Bug report to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is no

Processed: closing 322415

Processing commands for [EMAIL PROTECTED]: > # Automatically generated email from bts, devscripts version 2.9.15 > close 322415 1.2.9-0.0 Bug#322415: libsdl1.2debian: IYUV blitting does not work 'close' is deprecated; see http://www.debian.org/Bugs/Developer#closing. Bug marked as fixed in version

Bug#355154: marked as done (libgnat-3.4: insatisfiable depends in unstable)

Your message dated Fri, 3 Mar 2006 18:38:58 +0100 with message-id <[EMAIL PROTECTED]> and subject line Bug#355154: libgnat-3.4: insatisfiable depends 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

Bug#355137: marked as done (sysfs_write_attribute() is broken)

Your message dated Fri, 3 Mar 2006 18:41:08 +0100 with message-id <[EMAIL PROTECTED]> and subject line Bug#355137: sysfs_write_attribute() is broken has caused the attached Bug report 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#351080: marked as done (asterisk-prompt-it: Updated prompts for italian language available)

Your message dated Fri, 03 Mar 2006 09:32:09 -0800 with message-id <[EMAIL PROTECTED]> and subject line Bug#351080: fixed in asterisk-prompt-it 20060120-1 has caused the attached Bug report to be marked as done. This means that you claim that the problem has been dealt with. If this is not the cas

Bug#353965: marked as done (imapfilter uses an extraordinary amount of CPU while performing cross server mail moving)

Your message dated Fri, 03 Mar 2006 08:32:39 -0800 with message-id <[EMAIL PROTECTED]> and subject line Bug#353965: fixed in imapfilter 1:1.2-1 has caused the attached Bug report to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now

Bug#346023: marked as done (libjpeg-progs: -maxmemory / JPEGMEM appears not to work)

Your message dated Fri, 03 Mar 2006 07:17:08 -0800 with message-id <[EMAIL PROTECTED]> and subject line Bug#346023: fixed in libjpeg6b 6b-12 has caused the attached Bug report to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now yo

Bug#355007: marked as done (podracer: Please package new version 1.4)

Your message dated Fri, 03 Mar 2006 06:47:19 -0800 with message-id <[EMAIL PROTECTED]> and subject line Bug#355007: fixed in podracer 1.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 you

Bug#353036: marked as done (podracer: Fails to follow redirects to RSS feeds)

Your message dated Fri, 03 Mar 2006 06:47:19 -0800 with message-id <[EMAIL PROTECTED]> and subject line Bug#353036: fixed in podracer 1.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 you

Bug#350699: marked as done (podracer: unescaped shell metacharacter)

Your message dated Fri, 03 Mar 2006 06:47:19 -0800 with message-id <[EMAIL PROTECTED]> and subject line Bug#350699: fixed in podracer 1.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 you

Bug#349012: marked as done (podracer: Cryptic curl error if subscriptions file contains blank lines.)

Your message dated Fri, 03 Mar 2006 06:47:19 -0800 with message-id <[EMAIL PROTECTED]> and subject line Bug#349012: fixed in podracer 1.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 you

Bug#333284: marked as done (podracer: cannot open file `{print $1}' for reading (No such file or directory))

Your message dated Fri, 03 Mar 2006 06:47:19 -0800 with message-id <[EMAIL PROTECTED]> and subject line Bug#333284: fixed in podracer 1.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 you

Bug#355113: marked as done (libxul-dev: header file missing)

Your message dated Fri, 3 Mar 2006 13:44:06 +0100 with message-id <[EMAIL PROTECTED]> and subject line Bug#355113: libxul-dev: header file missing has caused the attached Bug report to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is

Bug#238997: marked as done (nvidia-modules-i386: not available for 2.6 kernel)

Your message dated Fri, 03 Mar 2006 07:29:08 -0500 with message-id <[EMAIL PROTECTED]> and subject line Done has caused the attached Bug report to be 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#354992: marked as done (lists.debian.org: Persistent spew from @amgi.it lists)

Your message dated Fri, 3 Mar 2006 05:50:35 -0600 with message-id <[EMAIL PROTECTED]> and subject line Bug#354992: lists.debian.org: Persistent spew from @amgi.it lists has 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#355022: marked as done (meld: New upstream version (1.1.3), fixes svn diff issue)

Your message dated Fri, 03 Mar 2006 03:17:06 -0800 with message-id <[EMAIL PROTECTED]> and subject line Bug#355022: fixed in meld 1.1.3-1 has caused the attached Bug report to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your

Bug#354941: marked as done (zope3-sandbox: package is uninstallable)

Your message dated Fri, 03 Mar 2006 12:03:05 +0100 with message-id <[EMAIL PROTECTED]> and subject line [Pkg-zope-developers] Bug#354941: zope3-sandbox: package is uninstallable has caused the attached Bug report to be marked as done. This means that you claim that the problem has been dealt with

Bug#353592: marked as done (asterisk: stereorize in wrong directory)

Your message dated Fri, 03 Mar 2006 10:51:07 +0100 with message-id <[EMAIL PROTECTED]> and subject line Bug#353592: asterisk: stereorize in wrong directory has caused the attached Bug report to be marked as done. This means that you claim that the problem has been dealt with. If this is not the ca

Bug#355083: marked as done (avahi-daemon: links against non-existent library)

Your message dated Fri, 3 Mar 2006 09:02:32 +0100 with message-id <[EMAIL PROTECTED]> and subject line Bug#355083: avahi-daemon: links against non-existent library has caused the attached Bug report to be marked as done. This means that you claim that the problem has been dealt with. If this is no

Bug#351953: marked as done (GNU/kFreeBSD port)

Your message dated Fri, 03 Mar 2006 00:17:19 -0800 with message-id <[EMAIL PROTECTED]> and subject line Bug#351953: fixed in wine 0.9.8-1 has caused the attached Bug report to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your