Bug#249335: marked as done (silo: needs versioned build-dep for e2fslibs-dev ( >= 1.28 ))

Your message dated Fri, 16 Jun 2006 23:36:52 -0700 (PDT) with message-id <[EMAIL PROTECTED]> and subject line silo: needs versioned build-dep for e2fslibs-dev ( >= 1.28 ) 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#236578: marked as done (gnome-terminal: does not render character upon [Compose, D/d, -] sequence)

Your message dated Sat, 17 Jun 2006 16:41:35 +1000 with message-id <[EMAIL PROTECTED]> and subject line compose sequences work has caused the attached Bug report to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibil

Bug#252056: marked as done (gnome-terminal: some keys on the numpad dos not work)

Your message dated Sat, 17 Jun 2006 16:46:03 +1000 with message-id <[EMAIL PROTECTED]> and subject line closing due to lack of submitter response has caused the attached Bug report to 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#202904: marked as done (irssi-text: Some key bindings doesn't work)

Your message dated Sat, 17 Jun 2006 15:59:04 +1000 with message-id <[EMAIL PROTECTED]> and subject line gnome-terminal differentiates left and Alt+Left has caused the attached Bug 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#374073: marked as done (whizzytex: Configuration is a mess)

Your message dated Fri, 16 Jun 2006 22:32:09 -0700 with message-id <[EMAIL PROTECTED]> and subject line Bug#374073: fixed in whizzytex 1.3.0-4 has caused the attached Bug report to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now

Bug#374071: marked as done ("-ini: command not found" on every run)

Your message dated Fri, 16 Jun 2006 22:32:09 -0700 with message-id <[EMAIL PROTECTED]> and subject line Bug#374071: fixed in whizzytex 1.3.0-4 has caused the attached Bug report to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now

Bug#228912: marked as done (gv does not work with whizzytex, whizzytex seems to be broken)

Your message dated Fri, 16 Jun 2006 22:32:09 -0700 with message-id <[EMAIL PROTECTED]> and subject line Bug#228912: fixed in whizzytex 1.3.0-4 has caused the attached Bug report to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now

Bug#374054: marked as done (ddskk: FTBFS when /bin/sh is dash)

Your message dated Fri, 16 Jun 2006 20:17:02 -0700 with message-id <[EMAIL PROTECTED]> and subject line Bug#374054: fixed in ddskk 13.0.90.cvs20060531-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

Bug#374055: marked as done (ddskk: problematic emacsen-startup)

Your message dated Fri, 16 Jun 2006 20:17:03 -0700 with message-id <[EMAIL PROTECTED]> and subject line Bug#374055: fixed in ddskk 13.0.90.cvs20060531-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

Bug#374057: marked as done (ddskk: emacsen-install: please use -no-site-file)

Your message dated Fri, 16 Jun 2006 20:17:03 -0700 with message-id <[EMAIL PROTECTED]> and subject line Bug#374057: fixed in ddskk 13.0.90.cvs20060531-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

Bug#373434: marked as done (Python policy transition)

Your message dated Fri, 16 Jun 2006 18:47:07 -0700 with message-id <[EMAIL PROTECTED]> and subject line Bug#373434: fixed in genetic 0.1.1b-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 y

Bug#373679: marked as done (rbconfig returns invalid LDFLAGS)

Your message dated Fri, 16 Jun 2006 18:47:12 -0700 with message-id <[EMAIL PROTECTED]> and subject line Bug#373679: fixed in ruby1.8 1.8.4-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#373302: marked as done (Python policy transition)

Your message dated Fri, 16 Jun 2006 18:17:03 -0700 with message-id <[EMAIL PROTECTED]> and subject line Bug#373302: fixed in cerealizer 0.4-2 has caused the attached Bug report to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now y

Bug#297734: marked as done (rhythmbox loops forever displaying error dialog)

Your message dated Sat, 17 Jun 2006 03:24:51 +0200 with message-id <[EMAIL PROTECTED]> and subject line Close 297734 has caused the attached Bug report to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reo

Bug#373418: marked as done (Python policy transition)

Your message dated Fri, 16 Jun 2006 17:47:04 -0700 with message-id <[EMAIL PROTECTED]> and subject line Bug#373418: fixed in editobj 0.5.7-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#373384: marked as done (Python policy transition)

Your message dated Fri, 16 Jun 2006 17:47:13 -0700 with message-id <[EMAIL PROTECTED]> and subject line Bug#373384: fixed in slides 1.0.1-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#72271: marked as done (ntp does not handle ARCRON clock)

Your message dated Sat, 17 Jun 2006 02:33:15 +0200 with message-id <[EMAIL PROTECTED]> and subject line Bug#72271: ntp does not handle ARCRON clock has caused the attached Bug report to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is

Processed: closing 307842

Processing commands for [EMAIL PROTECTED]: > # Automatically generated email from bts, devscripts version 2.9.20 > close 307842 Bug#307842: ntpd (-simple) gets SIGSEGV on startup [[SOLVED]] 'close' is deprecated; see http://www.debian.org/Bugs/Developer#closing. Bug closed, send any further explan

Bug#373358: marked as done (Python policy transition)

Your message dated Fri, 16 Jun 2006 17:32:11 -0700 with message-id <[EMAIL PROTECTED]> and subject line Bug#373358: fixed in python-stats 0.6-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

Bug#373432: marked as done (Python policy transition)

Your message dated Fri, 16 Jun 2006 17:32:09 -0700 with message-id <[EMAIL PROTECTED]> and subject line Bug#373432: fixed in gadfly 1.0.0-9 has caused the attached Bug report to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now you

Bug#373879: marked as done (bugs.deian.org: forcemerge documentation should clarify the meaning of "settings")

Your message dated Fri, 16 Jun 2006 17:26:18 -0700 with message-id <[EMAIL PROTECTED]> and subject line bugs.deian.org: forcemerge documentation should clarify the meaning of "settings" has caused the attached Bug report to be marked as done. This means that you claim that the problem has been de

Bug#372936: marked as done (bugs.d.o reports wrongly pending bugs)

Your message dated Fri, 16 Jun 2006 16:54:05 -0700 with message-id <[EMAIL PROTECTED]> and subject line Bug#372936: bugs.d.o reports wrongly pending bugs has caused the attached Bug 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#328098: marked as done (fonttools: do not work during summer)

Your message dated Fri, 16 Jun 2006 16:47:07 -0700 with message-id <[EMAIL PROTECTED]> and subject line Bug#328098: fixed in fonttools 1.99+2.0b1+cvs20060225-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 th

Bug#373438: marked as done (Python policy transition)

Your message dated Fri, 16 Jun 2006 16:32:07 -0700 with message-id <[EMAIL PROTECTED]> and subject line Bug#373438: fixed in gnupginterface 0.3.2-9 has caused the attached Bug report to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is

Bug#373504: marked as done (Python policy transition)

Your message dated Fri, 16 Jun 2006 16:02:06 -0700 with message-id <[EMAIL PROTECTED]> and subject line Bug#373504: fixed in pyspf 1.6-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 r

Bug#357923: marked as done (twisted-names: Please switch build-depends to twisted-core, too)

Your message dated Fri, 16 Jun 2006 16:02:09 -0700 with message-id <[EMAIL PROTECTED]> and subject line Bug#357923: fixed in twisted-news 0.2.0-1 has caused the attached Bug report to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is n

Bug#373399: marked as done (Python policy transition)

Your message dated Fri, 16 Jun 2006 16:02:13 -0700 with message-id <[EMAIL PROTECTED]> and subject line Bug#373399: fixed in twisted-web 0.6.0-1 has caused the attached Bug report to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is no

Bug#357925: marked as done (twisted-names: Please switch build-depends to twisted-core, too)

Your message dated Fri, 16 Jun 2006 16:02:18 -0700 with message-id <[EMAIL PROTECTED]> and subject line Bug#357925: fixed in twisted-words 0.4.0-1 has caused the attached Bug report to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is

Bug#373401: marked as done (Python policy transition)

Your message dated Fri, 16 Jun 2006 16:02:18 -0700 with message-id <[EMAIL PROTECTED]> and subject line Bug#373401: fixed in twisted-words 0.4.0-1 has caused the attached Bug report to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is

Bug#373400: marked as done (Python policy transition)

Your message dated Fri, 16 Jun 2006 16:02:15 -0700 with message-id <[EMAIL PROTECTED]> and subject line Bug#373400: fixed in twisted-web2 0.2.0-1 has caused the attached Bug report to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is n

Bug#357921: marked as done (twisted-names: Please switch build-depends to twisted-core, too)

Your message dated Fri, 16 Jun 2006 16:02:13 -0700 with message-id <[EMAIL PROTECTED]> and subject line Bug#357921: fixed in twisted-web 0.6.0-1 has caused the attached Bug report to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is no

Bug#373398: marked as done (Python policy transition)

Your message dated Fri, 16 Jun 2006 16:02:11 -0700 with message-id <[EMAIL PROTECTED]> and subject line Bug#373398: fixed in twisted-runner 0.2.0-1 has caused the attached Bug report to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is

Bug#373397: marked as done (Python policy transition)

Your message dated Fri, 16 Jun 2006 16:02:09 -0700 with message-id <[EMAIL PROTECTED]> and subject line Bug#373397: fixed in twisted-news 0.2.0-1 has caused the attached Bug report to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is n

Bug#357924: marked as done (twisted-names: Please switch build-depends to twisted-core, too)

Your message dated Fri, 16 Jun 2006 16:02:11 -0700 with message-id <[EMAIL PROTECTED]> and subject line Bug#357924: fixed in twisted-runner 0.2.0-1 has caused the attached Bug report to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is

Bug#362918: marked as done (twisted-runner: Build depends on itself.)

Your message dated Fri, 16 Jun 2006 16:02:11 -0700 with message-id <[EMAIL PROTECTED]> and subject line Bug#362918: fixed in twisted-runner 0.2.0-1 has caused the attached Bug report to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is

Bug#373396: marked as done (Python policy transition)

Your message dated Fri, 16 Jun 2006 16:02:08 -0700 with message-id <[EMAIL PROTECTED]> and subject line Bug#373396: fixed in twisted-names 0.3.0-1 has caused the attached Bug report to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is

Bug#357916: marked as done (twisted-names: Please switch build-depends to twisted-core, too)

Your message dated Fri, 16 Jun 2006 16:02:08 -0700 with message-id <[EMAIL PROTECTED]> and subject line Bug#357916: fixed in twisted-names 0.3.0-1 has caused the attached Bug report to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is

Bug#373394: marked as done (Python policy transition)

Your message dated Fri, 16 Jun 2006 15:47:22 -0700 with message-id <[EMAIL PROTECTED]> and subject line Bug#373394: fixed in twisted-lore 0.2.0-1 has caused the attached Bug report to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is n

Bug#304621: marked as done (plucker: Include GTK viewer)

Your message dated Fri, 16 Jun 2006 15:47:15 -0700 with message-id <[EMAIL PROTECTED]> and subject line Bug#304621: fixed in plucker 1.8-14 has caused the attached Bug report to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now you

Bug#357922: marked as done (twisted-names: Please switch build-depends to twisted-core, too)

Your message dated Fri, 16 Jun 2006 15:47:22 -0700 with message-id <[EMAIL PROTECTED]> and subject line Bug#357922: fixed in twisted-lore 0.2.0-1 has caused the attached Bug report to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is n

Bug#366515: marked as done (libnm_glib_nm_state_cb: dbus returned an error)

Your message dated Sat, 17 Jun 2006 00:46:07 +0200 with message-id <[EMAIL PROTECTED]> and subject line Solved by clearing ~/.evolution and ~/.gconf/apps/evolution has caused 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#351209: marked as done (package depends on transitional python2.3-twisted)

Your message dated Fri, 16 Jun 2006 15:47:25 -0700 with message-id <[EMAIL PROTECTED]> and subject line Bug#351209: fixed in twisted-mail 0.3.0-1 has caused the attached Bug report to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is n

Bug#355747: marked as done (python2.3-twisted-conch: file conflict with python2.3-twisted)

Your message dated Fri, 16 Jun 2006 15:47:20 -0700 with message-id <[EMAIL PROTECTED]> and subject line Bug#355747: fixed in twisted-conch 1:0.7.0-1 has caused the attached Bug report to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it i

Bug#323551: marked as done (python-twisted: im.1 is a dangling symlink:)

Your message dated Fri, 16 Jun 2006 15:47:25 -0700 with message-id <[EMAIL PROTECTED]> and subject line Bug#323551: fixed in twisted-mail 0.3.0-1 has caused the attached Bug report to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is n

Bug#373393: marked as done (Python policy transition)

Your message dated Fri, 16 Jun 2006 15:47:20 -0700 with message-id <[EMAIL PROTECTED]> and subject line Bug#373393: fixed in twisted-conch 1:0.7.0-1 has caused the attached Bug report to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it i

Bug#372830: marked as done (evolution: depends on libgnomevfs2 v2.14.1-2, should depend on libgnomevfs2 v2.14.2-1)

Your message dated Sat, 17 Jun 2006 00:44:18 +0200 with message-id <[EMAIL PROTECTED]> and subject line [2006-06-14] gnome-vfs2 2.14.2-1 MIGRATED to testing has caused the attached Bug report to be marked as done. This means that you claim that the problem has been dealt with. If this is not the c

Bug#326021: marked as done (python-twisted: a lot of dangling manpage symlinks)

Your message dated Fri, 16 Jun 2006 15:47:25 -0700 with message-id <[EMAIL PROTECTED]> and subject line Bug#326021: fixed in twisted-mail 0.3.0-1 has caused the attached Bug report to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is n

Bug#314508: marked as done (/usr/share/man/man1/mktap.1 is a dangling symlink)

Your message dated Fri, 16 Jun 2006 15:47:25 -0700 with message-id <[EMAIL PROTECTED]> and subject line Bug#314508: fixed in twisted-mail 0.3.0-1 has caused the attached Bug report to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is n

Bug#313313: marked as done (/usr/share/doc/python-twisted symlink wrong)

Your message dated Fri, 16 Jun 2006 15:47:25 -0700 with message-id <[EMAIL PROTECTED]> and subject line Bug#313313: fixed in twisted-mail 0.3.0-1 has caused the attached Bug report to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is n

Bug#373395: marked as done (Python policy transition)

Your message dated Fri, 16 Jun 2006 15:47:25 -0700 with message-id <[EMAIL PROTECTED]> and subject line Bug#373395: fixed in twisted-mail 0.3.0-1 has caused the attached Bug report to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is n

Bug#366456: marked as done (polgen-doc: missing /usr/share/polgen/src fobids polgen-doc from being installed)

Your message dated Fri, 16 Jun 2006 15:47:17 -0700 with message-id <[EMAIL PROTECTED]> and subject line Bug#366456: fixed in polgen-doc-non-dfsg 1.3-2 has caused the attached Bug report to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it

Bug#317290: marked as done (Missing dependency on python-soappy)

Your message dated Fri, 16 Jun 2006 15:47:25 -0700 with message-id <[EMAIL PROTECTED]> and subject line Bug#317290: fixed in twisted-mail 0.3.0-1 has caused the attached Bug report to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is n

Bug#373351: marked as done (Python policy transition)

Your message dated Fri, 16 Jun 2006 15:32:28 -0700 with message-id <[EMAIL PROTECTED]> and subject line Bug#373351: fixed in python-scientific 2.4.9-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

Bug#315307: marked as done (python-twisted: man twistd is a dangling symlink)

Your message dated Fri, 16 Jun 2006 15:47:25 -0700 with message-id <[EMAIL PROTECTED]> and subject line Bug#315307: fixed in twisted-mail 0.3.0-1 has caused the attached Bug report to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is n

Bug#319384: marked as done (python-scientific: Please make Scientific available for different versions of python)

Your message dated Fri, 16 Jun 2006 15:32:28 -0700 with message-id <[EMAIL PROTECTED]> and subject line Bug#319384: fixed in python-scientific 2.4.9-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

Bug#318167: marked as done (twisted-doc fails to install due to a broken doc-base file)

Your message dated Fri, 16 Jun 2006 15:47:25 -0700 with message-id <[EMAIL PROTECTED]> and subject line Bug#318167: fixed in twisted-mail 0.3.0-1 has caused the attached Bug report to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is n

Bug#374016: marked as done (libssl-dev: libssl.pc's Libs shouldn't include -ldl -lz)

Your message dated Fri, 16 Jun 2006 23:27:03 +0200 with message-id <[EMAIL PROTECTED]> and subject line [Pkg-openssl-devel] Bug#374016: libssl-dev: libssl.pc's Libs shouldn't include -ldl -lz has caused the attached Bug report to be marked as done. This means that you claim that the problem has b

Bug#339063: marked as done (plucker-desktop: unable to open SysZLib.prc)

Your message dated Fri, 16 Jun 2006 23:54:17 +0200 with message-id <[EMAIL PROTECTED]> and subject line plucker-desktop: unable to open SysZLib.prc has caused the attached Bug report to 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#373350: marked as done (Python policy transition)

Your message dated Fri, 16 Jun 2006 14:47:05 -0700 with message-id <[EMAIL PROTECTED]> and subject line Bug#373350: fixed in python-reportlab 1.20debian-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 cas

Bug#367296: marked as done (browsing downloaded .php's later from disk)

Your message dated Sun, 11 Jun 2006 07:21:15 +0800 with message-id <[EMAIL PROTECTED]> and subject line Bug#367296: browsing downloaded .php's later from disk has caused the attached 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#367048: marked as done (synfig: floating point exception on alpha)

Your message dated Fri, 16 Jun 2006 15:02:14 -0700 with message-id <[EMAIL PROTECTED]> and subject line Bug#367048: fixed in synfig 0.61.05-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 y

Bug#371074: marked as done (mailman: web interface gives internal server error)

Your message dated Fri, 16 Jun 2006 23:23:51 +0200 with message-id <[EMAIL PROTECTED]> and subject line Bug#371074: mailman: web interface gives internal server error has caused the attached Bug report to be marked as done. This means that you claim that the problem has been dealt with. If this is

Bug#352924: marked as done (kernel-wedge: de4x5 listed in nic-extra-modules, but not needed in 2.6?)

Your message dated Fri, 16 Jun 2006 14:32:59 -0700 with message-id <[EMAIL PROTECTED]> and subject line Bug#352924: fixed in kernel-wedge 2.23 has caused the attached Bug report to be 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#364633: marked as done (please backport func_odbc)

Your message dated Fri, 16 Jun 2006 14:32:38 -0700 with message-id <[EMAIL PROTECTED]> and subject line Bug#364633: fixed in asterisk 1:1.2.9.1.dfsg-1 has caused the attached Bug report to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it

Bug#373545: marked as done (Python policy transition)

Your message dated Fri, 16 Jun 2006 14:33:39 -0700 with message-id <[EMAIL PROTECTED]> and subject line Bug#373545: fixed in python-happydoc 2.1-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#368539: marked as done (kernel-package: localversion* files not supported?)

Your message dated Fri, 16 Jun 2006 14:32:57 -0700 with message-id <[EMAIL PROTECTED]> and subject line Bug#368539: fixed in kernel-package 10.049 has caused the attached Bug report to 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#373525: marked as done (Python policy transition)

Your message dated Fri, 16 Jun 2006 14:33:31 -0700 with message-id <[EMAIL PROTECTED]> and subject line Bug#373525: fixed in python-davlib 1.8-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 no

Bug#373338: marked as done (Python policy transition)

Your message dated Fri, 16 Jun 2006 14:33:41 -0700 with message-id <[EMAIL PROTECTED]> and subject line Bug#373338: fixed in python-pmw 1.2-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 y

Bug#216728: marked as done (python-pmw: support multiple python versions)

Your message dated Fri, 16 Jun 2006 14:33:41 -0700 with message-id <[EMAIL PROTECTED]> and subject line Bug#216728: fixed in python-pmw 1.2-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 y

Bug#369239: marked as done (pygresql: Insecure quote escaping [CVE-2006-2314])

Your message dated Fri, 16 Jun 2006 14:33:22 -0700 with message-id <[EMAIL PROTECTED]> and subject line Bug#369239: fixed in pygresql 1:3.8.1-1 has caused the attached Bug report to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now

Bug#372233: marked as done (kernel-package: arch/powerpc/include/asm symlink is not included in the *-headers package)

Your message dated Fri, 16 Jun 2006 14:32:57 -0700 with message-id <[EMAIL PROTECTED]> and subject line Bug#372233: fixed in kernel-package 10.049 has caused the attached Bug report to 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#373996: marked as done (ocaml - FTBFS: cannot open "/usr/share/sgml/docbook/dtd/xml/4.3/docbookx.dtd" (No such file or directory))

ing ID 'bytecode-native' > make[1]: *** [html] Error 8 > make[1]: Leaving directory `/build/buildd/ocaml-3.09.2/debian/policy' > make: *** [build-arch-stamp] Error 2 > ** > Build finished at 20060616-1441 > FAILED [dpkg-buildpackage died

Bug#373965: marked as done (error: `LOADPATH' undefined)

Your message dated Fri, 16 Jun 2006 23:24:50 +0200 with message-id <[EMAIL PROTECTED]> and subject line Bug#373965: [Pkg-octave-devel] Bug#373965: error: `LOADPATH' undefined 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#373774: marked as done (no longer supports images with the same name on 2 arches)

Your message dated Fri, 16 Jun 2006 14:32:57 -0700 with message-id <[EMAIL PROTECTED]> and subject line Bug#373774: fixed in kernel-package 10.049 has caused the attached Bug report to 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#373542: marked as done (Python policy transition)

Your message dated Fri, 16 Jun 2006 14:33:36 -0700 with message-id <[EMAIL PROTECTED]> and subject line Bug#373542: fixed in python-gnuplot 1.7-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#373531: marked as done (Python policy transition)

Your message dated Fri, 16 Jun 2006 14:33:33 -0700 with message-id <[EMAIL PROTECTED]> and subject line Bug#373531: fixed in python-extclass 1.2.0zope-2.5.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

Bug#373202: marked as done (pyparallel: FTBFS: Missing Build-Depends on 'python-dev')

Your message dated Fri, 16 Jun 2006 14:33:26 -0700 with message-id <[EMAIL PROTECTED]> and subject line Bug#373202: fixed in pyparallel 0.2-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 y

Bug#372783: marked as done (linux-image-2.6.16-2-amd64-k8: initrd symlink management sucks)

Your message dated Fri, 16 Jun 2006 14:32:57 -0700 with message-id <[EMAIL PROTECTED]> and subject line Bug#372783: fixed in kernel-package 10.049 has caused the attached Bug report to 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#373494: marked as done (Python policy transition)

Your message dated Fri, 16 Jun 2006 14:33:23 -0700 with message-id <[EMAIL PROTECTED]> and subject line Bug#373494: fixed in pygresql 1:3.8.1-1 has caused the attached Bug report to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now

Bug#373460: marked as done (Python policy transition)

Your message dated Fri, 16 Jun 2006 14:33:07 -0700 with message-id <[EMAIL PROTECTED]> and subject line Bug#373460: fixed in lxml 1.0.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#359908: marked as done (python-gnuplot: only python2.3 is supported)

Your message dated Fri, 16 Jun 2006 23:07:36 +0200 with message-id <[EMAIL PROTECTED]> and subject line python-gnuplot: only python2.3 is supported has caused the attached Bug report to 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#374013: marked as done (cdbs: $(cdbs_python_current_version) should always be set)

Your message dated Fri, 16 Jun 2006 23:01:27 +0200 with message-id <[EMAIL PROTECTED]> and subject line Bug#374013: cdbs: $(cdbs_python_current_version) should always be set has caused the attached Bug report to be marked as done. This means that you claim that the problem has been dealt with. If

Bug#370228: marked as done (subversion - FTBFS: Please use gcj)

Your message dated Fri, 16 Jun 2006 14:58:20 -0500 with message-id <[EMAIL PROTECTED]> and subject line Bug#370228: subversion - FTBFS: Please use gcj has caused the attached Bug report 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#312542: marked as done (python2.3-pygresql: Upstream 3.6.2 released)

Your message dated Fri, 16 Jun 2006 21:42:45 +0200 with message-id <[EMAIL PROTECTED]> and subject line pygresql-3.8 is in testing/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 you

Bug#270646: marked as done (ntp-server: FLAGS variable not used in /etc/init.d/ntp-server)

Your message dated Fri, 16 Jun 2006 21:59:55 +0200 with message-id <[EMAIL PROTECTED]> and subject line Bug#270646: ntp-server: FLAGS variable not used in /etc/init.d/ntp-server has caused the attached Bug report to be marked as done. This means that you claim that the problem has been dealt with

Bug#264569: marked as done (please document format of NTPSERVERS option)

Your message dated Fri, 16 Jun 2006 21:20:23 +0200 with message-id <[EMAIL PROTECTED]> and subject line #264569 please document format of NTPSERVERS option has caused the attached 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#357964: marked as done (FTBFS with G++ 4.1: extra qualification)

Your message dated Fri, 16 Jun 2006 11:47:09 -0700 with message-id <[EMAIL PROTECTED]> and subject line Bug#357964: fixed in pysvn 1.4.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 your

Processed: Re: Bug#374002: kdm: [CVE-2006-2449] KDM symlink attack vulnerability

Processing commands for [EMAIL PROTECTED]: > found 374002 4:3.5.2-2 Bug#374002: kdm: [CVE-2006-2449] KDM symlink attack vulnerability Bug marked as found in version 4:3.5.2-2. > close 374002 4:3.5.3-2 Bug#374002: kdm: [CVE-2006-2449] KDM symlink attack vulnerability 'close' is deprecated; see htt

Bug#373521: marked as done (Python policy transition)

Your message dated Fri, 16 Jun 2006 11:32:09 -0700 with message-id <[EMAIL PROTECTED]> and subject line Bug#373521: fixed in python-cjkcodecs 1.1.1-2 has caused the attached Bug report to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it

Bug#351107: marked as done (Please stop building the modules for python2.1/python2.2)

Your message dated Fri, 16 Jun 2006 11:32:09 -0700 with message-id <[EMAIL PROTECTED]> and subject line Bug#351107: fixed in python-cjkcodecs 1.1.1-2 has caused the attached Bug report to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it

Processed: Re: Bug#374003: CVE-2006-2916: artswrapper setuid() return value checking vulnerability

Processing commands for [EMAIL PROTECTED]: > found 374003 1.5.3-1 Bug#374003: CVE-2006-2916: artswrapper setuid() return value checking vulnerability Bug marked as found in version 1.5.3-1. > close 374003 1.5.3-2 Bug#374003: CVE-2006-2916: artswrapper setuid() return value checking vulnerabilit

Bug#354587: marked as done (pysvn: Incompatible with subversion 1.3 from experimental)

Your message dated Fri, 16 Jun 2006 20:42:35 +0200 with message-id <[EMAIL PROTECTED]> and subject line pysvn: Incompatible with subversion 1.3 from experimental has caused the 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#373954: marked as done (kernel-package: cross-compiling selects wrong compiler)

Your message dated Fri, 16 Jun 2006 13:28:47 -0500 with message-id <[EMAIL PROTECTED]> and subject line Bug#373954: kernel-package: cross-compiling selects wrong compiler has caused the attached Bug report to be marked as done. This means that you claim that the problem has been dealt with. If th

Bug#373507: marked as done (Python policy transition)

Your message dated Fri, 16 Jun 2006 11:47:09 -0700 with message-id <[EMAIL PROTECTED]> and subject line Bug#373507: fixed in pysvn 1.4.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 your

Bug#370667: marked as done (I2O modules for 64bit platforms)

Your message dated Fri, 16 Jun 2006 14:54:18 -0400 with message-id <[EMAIL PROTECTED]> and subject line Bug#370667: I2O modules for 64bit platforms has caused the attached Bug report to 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#372303: marked as done (ucf takes not enough care using readlink -f)

Your message dated Fri, 16 Jun 2006 11:17:09 -0700 with message-id <[EMAIL PROTECTED]> and subject line Bug#372303: fixed in ucf 2.0012 has caused the attached Bug report to be 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#373678: marked as done (python-distutils.mk DEB_PYTHON_INSTALL_ARGS variable should be DEB_PYTHON_INSTALL_ARGS_ALL)

Your message dated Fri, 16 Jun 2006 11:17:03 -0700 with message-id <[EMAIL PROTECTED]> and subject line Bug#373678: fixed in cdbs 0.4.42 has caused the attached Bug report to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your r

Bug#373997: marked as done (python-distutils.mk: ignores information about minor supported python version)

Your message dated Fri, 16 Jun 2006 11:17:03 -0700 with message-id <[EMAIL PROTECTED]> and subject line Bug#373997: fixed in cdbs 0.4.42 has caused the attached Bug report to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your r

Bug#373653: marked as done (cdbs: Some details to fix in the new python-distutils.mk)

Your message dated Fri, 16 Jun 2006 11:17:03 -0700 with message-id <[EMAIL PROTECTED]> and subject line Bug#373653: fixed in cdbs 0.4.42 has caused the attached Bug report to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your r

Bug#373873: marked as done (misleading python-distutils.mk error message)

Your message dated Fri, 16 Jun 2006 11:17:03 -0700 with message-id <[EMAIL PROTECTED]> and subject line Bug#373873: fixed in cdbs 0.4.42 has caused the attached Bug report to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your r

  1   2   >