Bug#434067: marked as done (libodbc-ruby1.8: Query execution generates random values in queries for SMALLINT values on MySQL)

Your message dated Fri, 24 Aug 2007 23:53:10 -0700 with message-id <[EMAIL PROTECTED]> and subject line Processed: reassign 434067 to libmyodbc has caused the attached Bug report to be 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#421838: marked as done ([INTL:nl] Dutch po-debconf translation)

Your message dated Sat, 25 Aug 2007 06:47:05 + with message-id <[EMAIL PROTECTED]> and subject line Bug#421838: fixed in up-imapproxy 1.2.4-10.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 i

Bug#402118: marked as done (debiandoc-sgml: Must specifiy explicit TeXLive dependencies)

Your message dated Sat, 25 Aug 2007 06:47:02 + with message-id <[EMAIL PROTECTED]> and subject line Bug#402118: fixed in debiandoc-sgml 1.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 n

Bug#436314: marked as done (up-imapproxy: FTBFS: unmet b-dep libwrap-dev)

Your message dated Sat, 25 Aug 2007 06:47:05 + with message-id <[EMAIL PROTECTED]> and subject line Bug#436314: fixed in up-imapproxy 1.2.4-10.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 i

Bug#422534: marked as done (diald : [INTL:pt] Portuguese translation for debconf messages)

Your message dated Sat, 25 Aug 2007 06:47:04 + with message-id <[EMAIL PROTECTED]> and subject line Bug#422534: fixed in diald 0.99.4-7.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 y

Bug#415355: marked as done (diald: [INTL:de] updated German debconf translation)

Your message dated Sat, 25 Aug 2007 06:47:03 + with message-id <[EMAIL PROTECTED]> and subject line Bug#415355: fixed in diald 0.99.4-7.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 y

Bug#436307: marked as done (diald: FTBFS: unmet b-dep libwrap-dev)

Your message dated Sat, 25 Aug 2007 06:47:04 + with message-id <[EMAIL PROTECTED]> and subject line Bug#436307: fixed in diald 0.99.4-7.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 y

Bug#424782: marked as done (axyl: affected by php4-removal)

Your message dated Sat, 25 Aug 2007 06:02:03 + with message-id <[EMAIL PROTECTED]> and subject line Bug#424782: fixed in axyl 2.1.14 has caused the attached Bug report to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your r

Bug#425764: marked as done (axyl: Minor error in Debconf template)

Your message dated Sat, 25 Aug 2007 06:02:03 + with message-id <[EMAIL PROTECTED]> and subject line Bug#425764: fixed in axyl 2.1.14 has caused the attached Bug report to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your r

Bug#438612: marked as done (zim: internal links don't work)

Your message dated Sat, 25 Aug 2007 05:47:05 + with message-id <[EMAIL PROTECTED]> and subject line Bug#438612: fixed in zim 0.20-1 has caused the attached Bug report to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your re

Bug#212960: marked as done (gauche: Japanese Info documents are not filled)

Your message dated Sat, 25 Aug 2007 05:17:08 + with message-id <[EMAIL PROTECTED]> and subject line Bug#212960: fixed in gauche 0.8.11-1 has caused the attached Bug report to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now yo

Bug#436510: marked as done (#title tag and lisp code evaluation order)

Your message dated Sat, 25 Aug 2007 05:17:35 + with message-id <[EMAIL PROTECTED]> and subject line Bug#436510: fixed in muse-el 3.11-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#439411: marked as done (kdelibs4c2a: kstartupconfig missing)

Your message dated Sat, 25 Aug 2007 05:03:28 + with message-id <[EMAIL PROTECTED]> and subject line Bug#439411: fixed in kdelibs 4:3.5.7.dfsg.1-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

Bug#438715: marked as done (docbookwiki: [INTL:pt] Portuguese translation for debconf messages)

Your message dated Sat, 25 Aug 2007 04:17:02 + with message-id <[EMAIL PROTECTED]> and subject line Bug#438715: fixed in docbookwiki 0.9.1cvs-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#439401: marked as done (docbookwiki: [INTL:de] initial German debconf translation)

Your message dated Sat, 25 Aug 2007 04:17:03 + with message-id <[EMAIL PROTECTED]> and subject line Bug#439401: fixed in docbookwiki 0.9.1cvs-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#439438: marked as done (xserver-xorg has inappropriate Recommends)

Your message dated Sat, 25 Aug 2007 05:52:54 +0200 with message-id <[EMAIL PROTECTED]> and subject line Bug#439438: xserver-xorg has inappropriate Recommends has caused the attached 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#415149: marked as done (rdist: FTBFS on GNU/kFreeBSD: missing OS detection)

Your message dated Sat, 25 Aug 2007 03:47:04 + with message-id <[EMAIL PROTECTED]> and subject line Bug#415149: fixed in rdist 6.1.5-13 has caused the attached Bug report to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now you

Bug#360976: marked as done (Please build the graphviz-tcl plugins and language module)

Your message dated Sat, 25 Aug 2007 05:25:12 +0200 with message-id <[EMAIL PROTECTED]> and subject line Closing bugreports... has caused the attached Bug report to be 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 responsibili

Bug#360979: marked as done (Please build the graphviz-php plugins and language module)

Your message dated Sat, 25 Aug 2007 05:23:10 +0200 with message-id <[EMAIL PROTECTED]> and subject line Duplicate of #360973, closing. has caused the attached Bug report to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your res

Bug#360972: marked as done (Please build the graphviz-perl plugins and language module)

Your message dated Sat, 25 Aug 2007 05:25:12 +0200 with message-id <[EMAIL PROTECTED]> and subject line Closing bugreports... has caused the attached Bug report to be 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 responsibili

Bug#423932: marked as done (/usr/share/man/man3/Mail::Address.3pm.gz: Typo: Limitted)

Your message dated Sat, 25 Aug 2007 02:02:02 + with message-id <[EMAIL PROTECTED]> and subject line Bug#423932: fixed in libmailtools-perl 1.77-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#374047: marked as done (Mail::Header: atg)

Your message dated Sat, 25 Aug 2007 02:02:02 + with message-id <[EMAIL PROTECTED]> and subject line Bug#374047: fixed in libmailtools-perl 1.77-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#439274: marked as done ([l10n] Updated Czech translation of sitebar debconf messages)

Your message dated Sat, 25 Aug 2007 01:32:02 + with message-id <[EMAIL PROTECTED]> and subject line Bug#439274: fixed in sitebar 3.3.8-11 has caused the attached Bug report to be 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#169943: marked as done (Fails to upgrade)

Your message dated Fri, 24 Aug 2007 21:23:35 -0400 with message-id <[EMAIL PROTECTED]> and subject line Fails to upgrade has caused the attached Bug report to be 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#439395: marked as done (libzzip-dev: Broken pkgconfig files)

Your message dated Sat, 25 Aug 2007 01:17:05 + with message-id <[EMAIL PROTECTED]> and subject line Bug#439395: fixed in zziplib 0.13.49-2 has caused the attached Bug report to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now

Bug#430894: marked as done (please turn gaim-librvp into a transition package for pidgin-librvp)

Your message dated Sat, 25 Aug 2007 01:17:04 + with message-id <[EMAIL PROTECTED]> and subject line Bug#430894: fixed in gaim-librvp 0.9.5-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

Bug#430892: marked as done (please turn gaim-encryption into a transition package to pidgin-encryption)

Your message dated Sat, 25 Aug 2007 01:17:03 + with message-id <[EMAIL PROTECTED]> and subject line Bug#430892: fixed in gaim-encryption 3.0~beta7-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 cas

Bug#272539: marked as done (wish: --quiet option for lockfile-create)

Your message dated Sat, 25 Aug 2007 00:47:03 + with message-id <[EMAIL PROTECTED]> and subject line Bug#272539: fixed in lockfile-progs 0.1.11 has caused the attached Bug report to 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#161685: marked as done (lockfile-progs: --retry option misleading)

Your message dated Sat, 25 Aug 2007 00:47:03 + with message-id <[EMAIL PROTECTED]> and subject line Bug#161685: fixed in lockfile-progs 0.1.11 has caused the attached Bug report to 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#244314: marked as done (lockfile-progs: lockfile-create(3) wrong about --retry)

Your message dated Sat, 25 Aug 2007 00:47:03 + with message-id <[EMAIL PROTECTED]> and subject line Bug#244314: fixed in lockfile-progs 0.1.11 has caused the attached Bug report to 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#416355: marked as done (inconsistent behaviour regarding .lock extension)

Your message dated Sat, 25 Aug 2007 00:47:03 + with message-id <[EMAIL PROTECTED]> and subject line Bug#416355: fixed in lockfile-progs 0.1.11 has caused the attached Bug report to 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#398421: marked as done (segfaults on startup (amd64))

Your message dated Sat, 25 Aug 2007 10:50:18 +1000 with message-id <[EMAIL PROTECTED]> and subject line Bug#398421: IRC has caused the attached Bug report to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to

Bug#360474: marked as done (lockfile-progs: man page is wrong)

Your message dated Sat, 25 Aug 2007 00:47:03 + with message-id <[EMAIL PROTECTED]> and subject line Bug#360474: fixed in lockfile-progs 0.1.11 has caused the attached Bug report to 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#437491: marked as done (lockfile-progs: not handling nostrip build option (policy 10.1))

Your message dated Sat, 25 Aug 2007 00:47:03 + with message-id <[EMAIL PROTECTED]> and subject line Bug#437491: fixed in lockfile-progs 0.1.11 has caused the attached Bug report to 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#382730: marked as done (Duplicate binaries in lockfile-progs)

Your message dated Sat, 25 Aug 2007 00:47:03 + with message-id <[EMAIL PROTECTED]> and subject line Bug#382730: fixed in lockfile-progs 0.1.11 has caused the attached Bug report to 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: Fix up OOo gdk bug versions with epoch

Processing commands for [EMAIL PROTECTED]: > close 423636 1:2.3.0~oog680m2-1 Bug#423636: oowriter: spits repeated glib/gdk assertion errors 'close' is deprecated; see http://www.debian.org/Bugs/Developer#closing. Bug marked as fixed in version 1:2.3.0~oog680m2-1, send any further explanations to

Bug#434666: marked as done (FTBFS: "bin/mpif90[f77] you provided with --with-mpi-dir=/usr does not work")

Your message dated Fri, 24 Aug 2007 23:17:05 + with message-id <[EMAIL PROTECTED]> and subject line Bug#434666: fixed in petsc 2.3.3-2 has caused the attached Bug report to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your

Bug#438449: marked as done (tzdata: Failed to preconfigure)

Your message dated Fri, 24 Aug 2007 23:17:06 + with message-id <[EMAIL PROTECTED]> and subject line Bug#438449: fixed in tzdata 2007f-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#423636: marked as done (oowriter: spits repeated glib/gdk assertion errors)

Your message dated Sat, 25 Aug 2007 00:14:44 +0100 with message-id <[EMAIL PROTECTED]> and subject line Bug#423636: Fixed in latest openoffice.org has caused the attached Bug report to 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#439421: marked as done (speedbar: "Recursive `require' for feature `sb-info'" with emacs22)

Your message dated Fri, 24 Aug 2007 18:42:28 -0400 with message-id <[EMAIL PROTECTED]> and subject line Bug#439421: speedbar: "Recursive `require' for feature `sb-info'" with emacs22 has caused the attached Bug report to be marked as done. This means that you claim that the problem has been dealt

Bug#439035: marked as done (missing builddep: liblocale-gettext-perl)

Your message dated Fri, 24 Aug 2007 22:32:02 + with message-id <[EMAIL PROTECTED]> and subject line Bug#439035: fixed in ikiwiki 2.6 has caused the attached Bug report to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your r

Bug#437181: marked as done (ikiwiki: French translation update)

Your message dated Fri, 24 Aug 2007 22:32:02 + with message-id <[EMAIL PROTECTED]> and subject line Bug#437181: fixed in ikiwiki 2.6 has caused the attached Bug report to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your r

Bug#438900: marked as done (ikiwiki: Would be nice if the postsparkline plugin took a color parameter)

Your message dated Fri, 24 Aug 2007 22:32:02 + with message-id <[EMAIL PROTECTED]> and subject line Bug#438900: fixed in ikiwiki 2.6 has caused the attached Bug report to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your r

Bug#436310: marked as done (atftp: FTBFS: unmet build dep libwrap-dev)

Your message dated Fri, 24 Aug 2007 22:02:02 + with message-id <[EMAIL PROTECTED]> and subject line Bug#436310: fixed in atftp 0.7.dfsg-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 y

Bug#439366: marked as done (atftp: FTBFS: unmet b-dep libwrap-dev)

Your message dated Fri, 24 Aug 2007 22:02:02 + with message-id <[EMAIL PROTECTED]> and subject line Bug#436310: fixed in atftp 0.7.dfsg-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 y

Bug#411456: marked as done (atftpd does not check exit code from select)

Your message dated Fri, 24 Aug 2007 22:02:02 + with message-id <[EMAIL PROTECTED]> and subject line Bug#411456: fixed in atftp 0.7.dfsg-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 y

Bug#378501: marked as done (epiphany-browser: epiphany unstable lately)

Your message dated Fri, 24 Aug 2007 23:42:13 +0200 with message-id <[EMAIL PROTECTED]> and subject line epiphany-browser: epiphany unstable lately has caused the attached Bug report to 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#432680: marked as done (gnome-power-manager: X session is not restored on wake up)

Your message dated Fri, 24 Aug 2007 23:40:38 +0200 with message-id <[EMAIL PROTECTED]> and subject line Bug#432680: gnome-power-manager: X session is not restored on wake up 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#438539: marked as done (oowriter hangs with experimental libgtk2.0-0)

Your message dated Fri, 24 Aug 2007 22:24:21 +0100 with message-id <[EMAIL PROTECTED]> and subject line Bug#438539: Fixed by openoffice.org 2.2.8-1 and 2.3.0~oog680m2-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

Bug#423631: marked as done (gdb: FTBFS on ia64: timeout)

Your message dated Fri, 24 Aug 2007 21:02:04 + with message-id <[EMAIL PROTECTED]> and subject line Bug#423631: fixed in gdb 6.6.dfsg-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 you

Bug#439215: marked as done (schroot: FTBFS because of boost change)

Your message dated Fri, 24 Aug 2007 21:02:08 + with message-id <[EMAIL PROTECTED]> and subject line Bug#439215: fixed in schroot 1.1.5-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#434604: marked as done (depends on non-essential package ucf in postrm)

Your message dated Fri, 24 Aug 2007 20:48:10 + with message-id <[EMAIL PROTECTED]> and subject line Bug#434604: fixed in monotone 0.36-1 has caused the attached Bug report to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now yo

Processed: not a "bug" in any version, but addressed in 0.3.1 anyway

Processing commands for [EMAIL PROTECTED]: > close 439292 Bug#439292: bashism 'close' is deprecated; see http://www.debian.org/Bugs/Developer#closing. Bug closed, send any further explanations to Joey Hess <[EMAIL PROTECTED]> > thanks Stopping processing here. Please contact me if you need assis

Bug#294279: marked as done ("quits unexpectedly" on Alpha)

Your message dated Fri, 24 Aug 2007 20:37:01 +0200 with message-id <[EMAIL PROTECTED]> and subject line Fixed has caused the attached Bug report to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the

Bug#420606: marked as done (ITP: python-cjson -- very fast JSON encoder/decoder for Python)

Your message dated Fri, 24 Aug 2007 18:36:04 + with message-id <[EMAIL PROTECTED]> and subject line Bug#420606: fixed in python-cjson 1.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 n

Bug#433926: marked as done (ITP: libwww-mechanize-formfiller-perl -- framework to automate HTML forms)

Your message dated Fri, 24 Aug 2007 18:38:39 + with message-id <[EMAIL PROTECTED]> and subject line Bug#433926: fixed in libwww-mechanize-formfiller-perl 0.06-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 n

Bug#437822: marked as done (vlock: permission denied with options -s and -n)

Your message dated Fri, 24 Aug 2007 18:32:54 + with message-id <[EMAIL PROTECTED]> and subject line Bug#437822: fixed in vlock 2.0-2 has caused the attached Bug report to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your r

Bug#436369: marked as done (ITP: python-pcs -- Packet Construction Set for Python)

Your message dated Fri, 24 Aug 2007 18:24:09 + with message-id <[EMAIL PROTECTED]> and subject line Bug#436369: fixed in python-pcs 0.5+debian-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#435884: marked as done (ITP: rsyslog -- enhanced multi-threaded syslogd)

Your message dated Fri, 24 Aug 2007 18:15:12 + with message-id <[EMAIL PROTECTED]> and subject line Bug#435884: fixed in rsyslog 1.18.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 y

Bug#439363: marked as done (youtube-dl: Does not work any longer -- has youtube.com changed their system?)

Your message dated Fri, 24 Aug 2007 18:02:03 + with message-id <[EMAIL PROTECTED]> and subject line Bug#439363: fixed in youtube-dl 2007.08.24-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#384125: marked as done (RFP: truetypeviewer -- viewer for TrueType and OpenType fonts)

Your message dated Fri, 24 Aug 2007 12:00:06 -0600 with message-id <[EMAIL PROTECTED]> and subject line WNPP bug closing has caused the attached Bug report to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to

Bug#383645: marked as done (ITP: nta -- network traffic analyzer, generate static html reports from /proc/net/dev)

Your message dated Fri, 24 Aug 2007 11:59:51 -0600 with message-id <[EMAIL PROTECTED]> and subject line WNPP bug closing has caused the attached Bug report to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to

Bug#323913: marked as done (ITP: tstat -- TCP STatistic and Analysis Tool)

Your message dated Fri, 24 Aug 2007 11:59:51 -0600 with message-id <[EMAIL PROTECTED]> and subject line WNPP bug closing has caused the attached Bug report to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to

Bug#211659: marked as done (RFP: dotproject -- Web-based project management tool)

Your message dated Fri, 24 Aug 2007 12:00:02 -0600 with message-id <[EMAIL PROTECTED]> and subject line WNPP bug closing has caused the attached Bug report to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to

Bug#384298: marked as done (RFP: cca -- CIL - Infrastructure for C Program Analysis and Transformation)

Your message dated Fri, 24 Aug 2007 12:00:06 -0600 with message-id <[EMAIL PROTECTED]> and subject line WNPP bug closing has caused the attached Bug report to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to

Bug#379855: marked as done (ITP: miboot -- Linux bootloader for OldWorld PowerMac computers)

Your message dated Fri, 24 Aug 2007 11:59:51 -0600 with message-id <[EMAIL PROTECTED]> and subject line WNPP bug closing has caused the attached Bug report to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to

Bug#344991: marked as done (RFP: dotproject -- Web-based project management tool)

Your message dated Fri, 24 Aug 2007 12:00:02 -0600 with message-id <[EMAIL PROTECTED]> and subject line WNPP bug closing has caused the attached Bug report to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to

Bug#266004: marked as done (RFP: libpam-smb -- Pluggable Authentication Module allowing Samba interface)

Your message dated Fri, 24 Aug 2007 12:00:02 -0600 with message-id <[EMAIL PROTECTED]> and subject line WNPP bug closing has caused the attached Bug report to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to

Bug#361797: marked as done (RFP: clewn -- A program to implement full gdb support in the vim editor.)

Your message dated Fri, 24 Aug 2007 12:00:06 -0600 with message-id <[EMAIL PROTECTED]> and subject line WNPP bug closing has caused the attached Bug report to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to

Bug#379399: marked as done (ITP: typo -- a lean weblogging engine powered by Ruby On Rails)

Your message dated Fri, 24 Aug 2007 11:59:51 -0600 with message-id <[EMAIL PROTECTED]> and subject line WNPP bug closing has caused the attached Bug report to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to

Bug#383398: marked as done (ITP: tptest3 -- A suite for testing bandwidth)

Your message dated Fri, 24 Aug 2007 11:59:51 -0600 with message-id <[EMAIL PROTECTED]> and subject line WNPP bug closing has caused the attached Bug report to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to

Bug#195519: marked as done (RFP: kernel-patch-l7-filter -- Application Layer Packet Classifier for Linux)

Your message dated Fri, 24 Aug 2007 12:00:01 -0600 with message-id <[EMAIL PROTECTED]> and subject line WNPP bug closing has caused the attached Bug report to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to

Bug#439376: marked as done (xserver-xorg: The resolution configured in the file "xorg.conf" is not used)

Your message dated Fri, 24 Aug 2007 19:48:35 +0200 with message-id <[EMAIL PROTECTED]> and subject line Bug#439376: xserver-xorg: The resolution configured in the file "xorg.conf" is not used has caused the attached Bug report to be marked as done. This means that you claim that the problem has b

Bug#436247: marked as done (wireshark-dev: Some header files are still missing from the package.)

Your message dated Fri, 24 Aug 2007 16:47:10 + with message-id <[EMAIL PROTECTED]> and subject line Bug#436247: fixed in wireshark 0.99.6rel-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

Bug#438732: marked as done (Starting firestarter firewall failed on boot)

Your message dated Fri, 24 Aug 2007 16:47:04 + with message-id <[EMAIL PROTECTED]> and subject line Bug#438732: fixed in firestarter 1.0.3-6 has caused the attached Bug report to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is no

Bug#439379: marked as done (CVE-2007-4436: permission problem)

Your message dated Fri, 24 Aug 2007 18:38:59 +0200 with message-id <[EMAIL PROTECTED]> and subject line Bug#439379: CVE-2007-4436: permission problem has caused the attached Bug report 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#439317: marked as done (Missing dependency on libssh2-0-dev)

Your message dated Fri, 24 Aug 2007 16:32:02 + with message-id <[EMAIL PROTECTED]> and subject line Bug#439317: fixed in curl 7.16.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 your

Bug#439326: marked as done (libcurl4-gnutls-dev: Must depends on libssh2-0-dev)

Your message dated Fri, 24 Aug 2007 16:32:03 + with message-id <[EMAIL PROTECTED]> and subject line Bug#439326: fixed in curl 7.16.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 your

Bug#439176: marked as done (libcurl3-gnutls: cannot depend on libssh2-0, which depends on libssl0.9.8)

Your message dated Fri, 24 Aug 2007 16:17:03 + with message-id <[EMAIL PROTECTED]> and subject line Bug#439176: fixed in curl 7.16.4-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#439270: marked as done (postgresql-8.1-plr: needs R_HOME which is a known constant for Debian)

Your message dated Fri, 24 Aug 2007 16:02:04 + with message-id <[EMAIL PROTECTED]> and subject line Bug#439270: fixed in plr 1:8.2.0.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 is now yo

Bug#436987: marked as done (ITP: blitz -- kde/qt image filter library)

Your message dated Fri, 24 Aug 2007 15:49:25 + with message-id <[EMAIL PROTECTED]> and subject line Bug#436987: fixed in blitz 0.0.3+svn699563-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#267934: marked as done (run level of firestarter script should be lower (not S45))

Your message dated Fri, 24 Aug 2007 16:44:22 +0100 with message-id <[EMAIL PROTECTED]> and subject line run level of firestarter script should be lower (not S45) has caused the 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#301763: marked as done (firestarter: Firewall not working for kernel > 2.6.10)

Your message dated Fri, 24 Aug 2007 16:37:20 +0100 with message-id <[EMAIL PROTECTED]> and subject line firestarter: Firewall not working for kernel > 2.6.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

Bug#401800: marked as done (ITP: ecryptfs-utils -- Linux eCryptfs utilities)

Your message dated Fri, 24 Aug 2007 15:34:40 + with message-id <[EMAIL PROTECTED]> and subject line Bug#401800: fixed in ecryptfs-utils 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 no

Bug#430729: marked as done (ITP: abraca -- gtk2 client for xmms2)

Your message dated Fri, 24 Aug 2007 15:29:36 + with message-id <[EMAIL PROTECTED]> and subject line Bug#430729: fixed in abraca 0.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#437350: marked as done (ITP: hunspell-ar -- Arabic dictionary for hunspell)

Your message dated Fri, 24 Aug 2007 15:22:26 + with message-id <[EMAIL PROTECTED]> and subject line Bug#437350: fixed in ayaspell-dic 0.0.0~beta1-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 i

Bug#437179: marked as done (ITP: libsoundgen -- Simple sound generator library for GPE)

Your message dated Fri, 24 Aug 2007 15:14:49 + with message-id <[EMAIL PROTECTED]> and subject line Bug#437179: fixed in libsoundgen 0.6-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#435279: marked as done (bacula: Please consider uploading to backports.org)

Your message dated Fri, 24 Aug 2007 09:46:58 -0500 with message-id <[EMAIL PROTECTED]> and subject line Closing has caused the attached Bug report to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen t

Bug#371890: marked as done (bacula: lower priority for mtx)

Your message dated Fri, 24 Aug 2007 09:50:59 -0500 with message-id <[EMAIL PROTECTED]> and subject line Closing has caused the attached Bug report to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen t

Bug#435633: marked as done (bacula-server: leaves .conf-files in /etc/bacula after purge)

Your message dated Fri, 24 Aug 2007 09:41:33 -0500 with message-id <[EMAIL PROTECTED]> and subject line Not a bug has caused the attached Bug report to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen

Bug#439343: marked as done (python-brlapi: Wrong permissions of brlapi.so)

Your message dated Fri, 24 Aug 2007 14:32:02 + with message-id <[EMAIL PROTECTED]> and subject line Bug#439343: fixed in brltty 3.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 now your

Bug#400109: marked as done (lucene: FTBFS: random, different build failures)

Your message dated Fri, 24 Aug 2007 14:32:04 + with message-id <[EMAIL PROTECTED]> and subject line Bug#400109: fixed in lucene 1.4.3.dfsg-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 no

Bug#424471: marked as done (lucene - FTBFS: Cannot use Kaffe rmic, as it is not available)

Your message dated Fri, 24 Aug 2007 14:32:04 + with message-id <[EMAIL PROTECTED]> and subject line Bug#424471: fixed in lucene 1.4.3.dfsg-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 no

Bug#439353: marked as done (custom HAL mount options ignored)

Your message dated Fri, 24 Aug 2007 15:18:51 +0200 with message-id <[EMAIL PROTECTED]> and subject line Bug#439353: custom HAL mount options ignored has caused the attached Bug report 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#428785: marked as done (wpasupplicant: losing WiFi connectivity "Connection to wpa_supplicant lost - trying to reconnect")

Your message dated Fri, 24 Aug 2007 21:05:27 +1000 with message-id <[EMAIL PROTECTED]> and subject line Marking as closed has caused the attached Bug report to be 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#432609: marked as done (xsane: Saving files is too slow)

Your message dated Fri, 24 Aug 2007 11:02:04 + with message-id <[EMAIL PROTECTED]> and subject line Bug#432609: fixed in xsane 0.99+0.991-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#409684: marked as done (xsane: please avoid redisplaying eula with every failed startup)

Your message dated Fri, 24 Aug 2007 12:27:04 +0200 with message-id <[EMAIL PROTECTED]> and subject line Bug#409684: xsane: please avoid redisplaying eula with every failed startup has caused the attached Bug report to be marked as done. This means that you claim that the problem has been dealt wi

Bug#428688: marked as done (xsane: No images are saved in multipage projects when the )

Your message dated Fri, 24 Aug 2007 12:30:58 +0200 with message-id <[EMAIL PROTECTED]> and subject line Bug#428688: xsane: No images are saved in multipage projects when the 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#404860: marked as done (Gimp 2.2 cannot load xsane plugin)

Your message dated Fri, 24 Aug 2007 12:27:40 +0200 with message-id <[EMAIL PROTECTED]> and subject line Bug#404860: Gimp 2.2 cannot load xsane plugin has caused the attached Bug report 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#437829: marked as done (libmtp5: add ID for Samsung YP-U3JQW)

Your message dated Fri, 24 Aug 2007 10:17:03 + with message-id <[EMAIL PROTECTED]> and subject line Bug#437829: fixed in libmtp 0.2.1-1 has caused the attached Bug report to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now you

  1   2   >