Bug#454417: marked as done (maildrop does not list all the necessary dependencies)

Your message dated Fri, 04 Jan 2008 20:32:06 + with message-id [EMAIL PROTECTED] and subject line Bug#395529: fixed in maildrop 2.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

Bug#396540: marked as done (maildrop: Mention duplicate filtering and logging in package description)

Your message dated Fri, 04 Jan 2008 20:32:06 + with message-id [EMAIL PROTECTED] and subject line Bug#396540: fixed in maildrop 2.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

Bug#459030: marked as done (mailsync: FTBFS: unmet b-dep libc-client-dev)

Your message dated Fri, 4 Jan 2008 22:43:25 +0100 with message-id [EMAIL PROTECTED] and subject line Bug#459026: libmail-cclient-perl: FTBFS: unmet b-dep libc-client-dev 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#450004: marked as done (ulex: debian/watch fails to report upstream's version)

Your message dated Fri, 04 Jan 2008 21:32:10 + with message-id [EMAIL PROTECTED] and subject line Bug#450004: fixed in ulex 1.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 your

Bug#459035: marked as done (aolserver4-nsimap: FTBFS: unmet dep libc-client-dev)

Your message dated Fri, 4 Jan 2008 22:43:25 +0100 with message-id [EMAIL PROTECTED] and subject line Bug#459026: libmail-cclient-perl: FTBFS: unmet b-dep libc-client-dev 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#459036: marked as done (archmbox: FTBFS: unmet dep libc-client2006j2)

Your message dated Fri, 4 Jan 2008 22:43:25 +0100 with message-id [EMAIL PROTECTED] and subject line Bug#459026: libmail-cclient-perl: FTBFS: unmet b-dep libc-client-dev 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#411525: marked as done (items in the Debian menu appear a second time in the open with dialog)

Your message dated Fri, 04 Jan 2008 22:33:17 +0100 with message-id [EMAIL PROTECTED] and subject line Fixed by the menu cleanup has caused the attached Bug report to be 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#436561: marked as done (fortunes-de: [INTL:pt] Portuguese translation for debconf messages)

Your message dated Fri, 04 Jan 2008 20:47:02 + with message-id [EMAIL PROTECTED] and subject line Bug#436561: fixed in fortunes-de 0.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 is now

Bug#459192: marked as done (fortunes-de: package content changes when built with dash as /bin/sh)

Your message dated Fri, 04 Jan 2008 20:47:02 + with message-id [EMAIL PROTECTED] and subject line Bug#459192: fixed in fortunes-de 0.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 is now

Bug#451700: marked as done (apt-cacher won't connect to IPv6 hosts)

Your message dated Fri, 04 Jan 2008 21:17:02 + with message-id [EMAIL PROTECTED] and subject line Bug#451700: fixed in apt-cacher 1.6.0 has caused the attached Bug report to be 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#369433: marked as done (GPG errors only when using apt-cacher)

Your message dated Fri, 04 Jan 2008 21:17:02 + with message-id [EMAIL PROTECTED] and subject line Bug#369433: fixed in apt-cacher 1.6.0 has caused the attached Bug report to be 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#457314: marked as done (smb2www: [INTL:vi] Vietnamese debconf templates translation update)

Your message dated Fri, 04 Jan 2008 21:32:09 + with message-id [EMAIL PROTECTED] and subject line Bug#457314: fixed in smb2www 980804-33 has caused the attached Bug report to be 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#447033: marked as done (apt-cacher: fails to fetch files when use_proxy is in effect)

Your message dated Fri, 04 Jan 2008 21:17:02 + with message-id [EMAIL PROTECTED] and subject line Bug#447033: fixed in apt-cacher 1.6.0 has caused the attached Bug report to be 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#459038: marked as done (postman: FTBFS: unmet dep libc-client-dev)

Your message dated Fri, 4 Jan 2008 22:43:25 +0100 with message-id [EMAIL PROTECTED] and subject line Bug#459026: libmail-cclient-perl: FTBFS: unmet b-dep libc-client-dev 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#456148: marked as done (CVE-2007-6306: Multiple cross-site scripting vulnerabilities)

Your message dated Fri, 04 Jan 2008 21:17:06 + with message-id [EMAIL PROTECTED] and subject line Bug#456148: fixed in libjfreechart-java 1.0.9-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#455080: marked as done (bashdb: should be arch all)

Your message dated Fri, 04 Jan 2008 22:02:02 + with message-id [EMAIL PROTECTED] and subject line Bug#455080: fixed in bashdb 3.1.0.8-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

Bug#427695: marked as done (apt-cacher: should update the Packages file)

Your message dated Fri, 04 Jan 2008 21:17:02 + with message-id [EMAIL PROTECTED] and subject line Bug#427695: fixed in apt-cacher 1.6.0 has caused the attached Bug report to be 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#459026: marked as done (libmail-cclient-perl: FTBFS: unmet b-dep libc-client-dev)

Your message dated Fri, 4 Jan 2008 22:43:25 +0100 with message-id [EMAIL PROTECTED] and subject line Bug#459026: libmail-cclient-perl: FTBFS: unmet b-dep libc-client-dev 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#456583: marked as done (nb translation for debconf eel2)

Your message dated Fri, 04 Jan 2008 22:32:02 + with message-id [EMAIL PROTECTED] and subject line Bug#456583: fixed in eel2 2.20.0-3 has caused the attached Bug report to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your

Bug#325290: marked as done (/usr/bin/routef: No manual entry for routef)

Your message dated Fri, 04 Jan 2008 22:17:08 + with message-id [EMAIL PROTECTED] and subject line Bug#325290: fixed in iproute 20071016-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

Bug#458578: marked as done (uses pseudo-hashes, fails with perl 5.10)

Your message dated Fri, 04 Jan 2008 22:32:05 + with message-id [EMAIL PROTECTED] and subject line Bug#458578: fixed in libxml-encoding-perl 2.01-1 has caused the attached Bug report to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case

Bug#453381: marked as done (eel2: [INTL:vi] Vietnamese program translation)

Your message dated Fri, 04 Jan 2008 22:32:02 + with message-id [EMAIL PROTECTED] and subject line Bug#453381: fixed in eel2 2.20.0-3 has caused the attached Bug report to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your

Bug#451740: marked as done (dfxvideo error -- BadMatch (invalid parameter attributes))

Your message dated Fri, 04 Jan 2008 23:02:02 + with message-id [EMAIL PROTECTED] and subject line Bug#451740: fixed in pcsx-df 1:1.816-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#458877: marked as done (asterisk: FTBFS: E: Couldn't find package libc-client2006j2-dev)

Your message dated Fri, 04 Jan 2008 22:47:06 + with message-id [EMAIL PROTECTED] and subject line Bug#458877: fixed in asterisk 1:1.4.17~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

Bug#456932: marked as done (eel2: Finnish translation of the patches.pot)

Your message dated Fri, 04 Jan 2008 22:32:02 + with message-id [EMAIL PROTECTED] and subject line Bug#456932: fixed in eel2 2.20.0-3 has caused the attached Bug report to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your

Bug#456580: marked as done (eel2: [INTL:de] initial German po file translation)

Your message dated Fri, 04 Jan 2008 22:32:02 + with message-id [EMAIL PROTECTED] and subject line Bug#456580: fixed in eel2 2.20.0-3 has caused the attached Bug report to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your

Bug#433507: marked as done (iproute: 'ip rule help' lists unnecessary pref/prio duplicate)

Your message dated Fri, 04 Jan 2008 22:17:08 + with message-id [EMAIL PROTECTED] and subject line Bug#433507: fixed in iproute 20071016-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

Bug#456616: marked as done (eel2: [INTL:pt] Portuguese translation for eel2)

Your message dated Fri, 04 Jan 2008 22:32:02 + with message-id [EMAIL PROTECTED] and subject line Bug#456616: fixed in eel2 2.20.0-3 has caused the attached Bug report to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your

Bug#435022: marked as done (nautilus: Invoke gnome-app-install when no application known for file)

Your message dated Fri, 04 Jan 2008 22:32:02 + with message-id [EMAIL PROTECTED] and subject line Bug#435022: fixed in eel2 2.20.0-3 has caused the attached Bug report to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your

Bug#458539: marked as done (tc flowid unknown)

Your message dated Fri, 04 Jan 2008 22:17:08 + with message-id [EMAIL PROTECTED] and subject line Bug#458539: fixed in iproute 20071016-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

Bug#457438: marked as done (picalib: Bashism in debian/rules)

Your message dated Fri, 04 Jan 2008 22:17:10 + with message-id [EMAIL PROTECTED] and subject line Bug#457438: fixed in picalib 0.1.5-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

Bug#414086: marked as done (iproute: become the new default)

Your message dated Fri, 04 Jan 2008 22:17:08 + with message-id [EMAIL PROTECTED] and subject line Bug#414086: fixed in iproute 20071016-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

Bug#410942: marked as done (scripts should be executable)

Your message dated Fri, 04 Jan 2008 22:32:05 + with message-id [EMAIL PROTECTED] and subject line Bug#410942: fixed in libxml-encoding-perl 2.01-1 has caused the attached Bug report to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case

Bug#457689: marked as done (eel2: [INTL:it] Italian translation)

Your message dated Fri, 04 Jan 2008 22:32:02 + with message-id [EMAIL PROTECTED] and subject line Bug#457689: fixed in eel2 2.20.0-3 has caused the attached Bug report to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your

Bug#453282: marked as done (eel2: [INTL:Eu] BAsque translation)

Your message dated Fri, 04 Jan 2008 22:32:02 + with message-id [EMAIL PROTECTED] and subject line Bug#453282: fixed in eel2 2.20.0-3 has caused the attached Bug report to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your

Bug#456937: marked as done (FTBFS: gcc fails to compile pcsx without optimizations)

Your message dated Fri, 04 Jan 2008 23:02:02 + with message-id [EMAIL PROTECTED] and subject line Bug#456937: fixed in pcsx-df 1:1.816-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#452017: marked as done (pcsx-df: get_state_filename() implicitly converted to pointer)

Your message dated Fri, 04 Jan 2008 23:02:02 + with message-id [EMAIL PROTECTED] and subject line Bug#452017: fixed in pcsx-df 1:1.816-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#452079: marked as done (hellanzb: screen is updated incorrectly with a server with multiple hosts)

Your message dated Fri, 04 Jan 2008 23:17:04 + with message-id [EMAIL PROTECTED] and subject line Bug#452079: fixed in hellanzb 0.13-3 has caused the attached Bug report to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now

Bug#456434: marked as done (qa.debian.org/developer.php shows comanintained packages even on comaint=no)

Your message dated Sat, 5 Jan 2008 00:27:21 +0100 with message-id [EMAIL PROTECTED] and subject line Seems to be working again has caused the attached Bug report to be 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#456920: marked as done (etckeeper: French debconf templates translation)

Your message dated Sat, 05 Jan 2008 00:02:17 + with message-id [EMAIL PROTECTED] and subject line Bug#456920: fixed in etckeeper 0.7 has caused the attached Bug report to be 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#455967: marked as done ([INTL:fi] Finnish translation of the debconf templates)

Your message dated Sat, 05 Jan 2008 00:02:17 + with message-id [EMAIL PROTECTED] and subject line Bug#455967: fixed in etckeeper 0.7 has caused the attached Bug report to be 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#457678: marked as done ([l10n] Czech translation of etckeeper debconf messages)

Your message dated Sat, 05 Jan 2008 00:02:17 + with message-id [EMAIL PROTECTED] and subject line Bug#457678: fixed in etckeeper 0.7 has caused the attached Bug report to be 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#459191: marked as done (gimp-help: package content changes when built with dash as /bin/sh)

Your message dated Sat, 05 Jan 2008 00:32:13 + with message-id [EMAIL PROTECTED] and subject line Bug#459191: fixed in gimp-help 2.4.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

Bug#454774: marked as done (etckeeper: [debconf_rewrite] Debconf templates and debian/control review)

Your message dated Sat, 05 Jan 2008 00:02:17 + with message-id [EMAIL PROTECTED] and subject line Bug#454774: fixed in etckeeper 0.7 has caused the attached Bug report to be 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#457806: marked as done ([INTL:nl] Dutch po-debconf translation)

Your message dated Sat, 05 Jan 2008 00:02:18 + with message-id [EMAIL PROTECTED] and subject line Bug#457806: fixed in etckeeper 0.7 has caused the attached Bug report to be 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#440902: marked as done (window placement of scan dialog)

Your message dated Sat, 05 Jan 2008 00:02:24 + with message-id [EMAIL PROTECTED] and subject line Bug#440902: fixed in gscan2pdf 0.9.19-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#456509: marked as done (etckeeper: [INTL:it] Italian debconf templates translation)

Your message dated Sat, 05 Jan 2008 00:02:17 + with message-id [EMAIL PROTECTED] and subject line Bug#456509: fixed in etckeeper 0.7 has caused the attached Bug report to be 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#457307: marked as done (etckeeper: [INTL:vi] Vietnamese debconf templates translation)

Your message dated Sat, 05 Jan 2008 00:02:17 + with message-id [EMAIL PROTECTED] and subject line Bug#457307: fixed in etckeeper 0.7 has caused the attached Bug report to be 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#456543: marked as done (etckeeper: [INTL:pt] Updated Portuguese translation for debconf messages)

Your message dated Sat, 05 Jan 2008 00:02:17 + with message-id [EMAIL PROTECTED] and subject line Bug#456543: fixed in etckeeper 0.7 has caused the attached Bug report to be 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#457830: marked as done ([INTL:eu] Basque debconf templates translation for etckeeper)

Your message dated Sat, 05 Jan 2008 00:02:18 + with message-id [EMAIL PROTECTED] and subject line Bug#457830: fixed in etckeeper 0.7 has caused the attached Bug report to be 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#457871: marked as done (etckeeper: [INTL:ru] Russian debconf templates translation)

Your message dated Sat, 05 Jan 2008 00:02:18 + with message-id [EMAIL PROTECTED] and subject line Bug#457871: fixed in etckeeper 0.7 has caused the attached Bug report to be 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#455790: marked as done ([INTL:gl] Galician debconf template translation for etckeeper)

Your message dated Sat, 05 Jan 2008 00:02:17 + with message-id [EMAIL PROTECTED] and subject line Bug#455790: fixed in etckeeper 0.7 has caused the attached Bug report to be 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#459031: marked as done (fldigi: FTBFS: /usr/include/c++/4.2/bits/locale_facets.tcc:118: error: 'dynamic_cast' not permitted with -fno-rtti)

Your message dated Sat, 05 Jan 2008 00:32:05 + with message-id [EMAIL PROTECTED] and subject line Bug#459031: fixed in fldigi 2.07-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#456617: marked as done (ITP: uvcvideo -- Source for the USB Video Class (uvcvideo) webcam driver)

Your message dated Fri, 4 Jan 2008 19:59:27 -0500 with message-id [EMAIL PROTECTED] and subject line (no subject) has caused the attached Bug report to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to

Bug#429080: marked as done (RM: libapache-mod-trigger -- RoQA; obsolete)

Your message dated Sat, 05 Jan 2008 00:58:46 + with message-id [EMAIL PROTECTED] and subject line Bug#429080: 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

Bug#429093: marked as done (RM: libapache-mod-ldap -- RoQA; obsolete)

Your message dated Sat, 05 Jan 2008 00:59:59 + with message-id [EMAIL PROTECTED] and subject line Bug#429093: 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

Bug#429131: marked as done (RM: libapache-mod-rpaf -- RoQA; obsolete)

Your message dated Sat, 05 Jan 2008 01:00:29 + with message-id [EMAIL PROTECTED] and subject line Bug#429131: 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

Bug#429102: marked as done (RM: libapache-mod-auth-useragent -- RoQA; obsolete)

Your message dated Sat, 05 Jan 2008 00:59:33 + with message-id [EMAIL PROTECTED] and subject line Bug#429102: 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

Bug#458109: marked as done (ftp.debian.org: Please change section override of shorewall-doc)

Your message dated Sat, 05 Jan 2008 00:53:26 + with message-id [EMAIL PROTECTED] and subject line Bug#458109: 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

Bug#429081: marked as done (RM: libapache-mod-text2html -- RoQA; obsolete)

Your message dated Sat, 05 Jan 2008 00:59:19 + with message-id [EMAIL PROTECTED] and subject line Bug#429081: 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

Bug#429124: marked as done (RM: libapache-mod-index-rss -- RoQA; obsolete)

Your message dated Sat, 05 Jan 2008 00:57:28 + with message-id [EMAIL PROTECTED] and subject line Bug#429124: 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

Bug#429127: marked as done (RM: libapache-mod-mp3 -- RoQA; obsolete)

Your message dated Sat, 05 Jan 2008 00:58:33 + with message-id [EMAIL PROTECTED] and subject line Bug#429127: 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

Bug#429098: marked as done (RM: libapache-mod-choke -- RoQA; obsolete)

Your message dated Sat, 05 Jan 2008 00:58:09 + with message-id [EMAIL PROTECTED] and subject line Bug#429098: 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

Bug#458885: marked as done (RM: libopensync-plugin-gpe/unstable -- RoM; errornous upload, FTBFS)

Your message dated Sat, 05 Jan 2008 01:00:45 + with message-id [EMAIL PROTECTED] and subject line Bug#458885: 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

Bug#429123: marked as done (RM: libapache-mod-iptos -- RoM; obsolete; apache1 only)

Your message dated Sat, 05 Jan 2008 01:01:01 + with message-id [EMAIL PROTECTED] and subject line Bug#429123: 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

Bug#429096: marked as done (RM: libapache-mod-filter -- RoQA; obsolete)

Your message dated Sat, 05 Jan 2008 00:57:48 + with message-id [EMAIL PROTECTED] and subject line Bug#429096: 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

Bug#429083: marked as done (RM: libapache-mod-relocate -- RoQA; obsolete)

Your message dated Sat, 05 Jan 2008 00:59:46 + with message-id [EMAIL PROTECTED] and subject line Bug#429083: 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

Bug#458982: marked as done (RM: parmetis [arm hppa mips mipsel s390] -- RoRM; build-depends on package not available on some archs)

Your message dated Sat, 05 Jan 2008 01:02:50 + with message-id [EMAIL PROTECTED] and subject line Bug#458982: 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

Bug#459148: marked as done (apt-get source does not fetch the source for the current security release)

Your message dated Fri, 4 Jan 2008 20:37:45 -0500 with message-id [EMAIL PROTECTED] and subject line Bug#459148: apt-get source does not fetch the source for the current security release has caused the attached Bug report to be marked as done. This means that you claim that the problem has been

Bug#421189: marked as done (Remove/merge redundant dvorak file)

Your message dated Sat, 5 Jan 2008 02:44:40 +0100 with message-id [EMAIL PROTECTED] and subject line Bug#421189: Remove/merge redundant dvorak file has caused the attached Bug report 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#449070: marked as done (Nautilus crashes)

Your message dated Sat, 05 Jan 2008 02:55:20 +0100 with message-id [EMAIL PROTECTED] and subject line [Fwd: Accepted gtk+2.0 2.12.1-2 (source all amd64)] has caused the attached 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#416951: marked as done (File is lost during tagging)

Your message dated Sat, 05 Jan 2008 01:47:08 + with message-id [EMAIL PROTECTED] and subject line Bug#416951: fixed in picard 0.9.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 now your

Bug#431466: marked as done (picard: critical failed asserts)

Your message dated Sat, 05 Jan 2008 01:47:08 + with message-id [EMAIL PROTECTED] and subject line Bug#431466: fixed in picard 0.9.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 now your

Bug#458912: marked as done (The watch file isn't working correctly)

Your message dated Sat, 05 Jan 2008 01:47:08 + with message-id [EMAIL PROTECTED] and subject line Bug#458912: fixed in picard 0.9.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 now your

Bug#457327: marked as done (New upstream version 1.0 available)

Your message dated Sat, 05 Jan 2008 01:47:04 + with message-id [EMAIL PROTECTED] and subject line Bug#457327: fixed in alpine 1.0+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 is now

Bug#457241: marked as done (picard: New (stable) upstream release)

Your message dated Sat, 05 Jan 2008 01:47:08 + with message-id [EMAIL PROTECTED] and subject line Bug#457241: fixed in picard 0.9.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 now your

Bug#458147: marked as done (nautilus: crash when tries to get information of a directory)

Your message dated Sat, 05 Jan 2008 03:34:32 +0100 with message-id [EMAIL PROTECTED] and subject line Bug#458147: nautilus: crash when tries to get information of a directory has caused the attached Bug report to be marked as done. This means that you claim that the problem has been dealt with.

Bug#458853: marked as done (lib32bz2-1.0: installs files in /usr/lib32)

Your message dated Sat, 05 Jan 2008 02:47:03 + with message-id [EMAIL PROTECTED] and subject line Bug#458853: fixed in bzip2 1.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 your

Bug#418532: marked as done (bzexe refers wrongly to /usr/bin/bzip2)

Your message dated Sat, 05 Jan 2008 02:47:03 + with message-id [EMAIL PROTECTED] and subject line Bug#418532: fixed in bzip2 1.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 your

Bug#381230: marked as done (bzip2 doesn't have a copyright file in the source)

Your message dated Sat, 05 Jan 2008 02:47:03 + with message-id [EMAIL PROTECTED] and subject line Bug#381230: fixed in bzip2 1.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 your

Bug#458971: marked as done (darkstat initscript error if START_DARKSTAT variable undefined)

Your message dated Sat, 05 Jan 2008 03:47:03 + with message-id [EMAIL PROTECTED] and subject line Bug#458971: fixed in darkstat 3.0.707-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#439897: marked as done (ffmpeg: Patent holders on mpeg2 encoder)

Your message dated Sat, 05 Jan 2008 06:49:41 +0100 with message-id [EMAIL PROTECTED] and subject line ffmpeg: Patent holders on mpeg2 encoder has caused the attached Bug report to be 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#443911: marked as done (Please package more recent snapshot)

Your message dated Sat, 05 Jan 2008 06:52:14 +0100 with message-id [EMAIL PROTECTED] and subject line Please package more recent snapshot has caused the attached Bug report to be 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#458733: marked as done (FTBFS on architectures where char is unsigned by default)

Your message dated Sat, 05 Jan 2008 05:47:24 + with message-id [EMAIL PROTECTED] and subject line Bug#458733: fixed in warzone2100 2.1.0~0.svn3330-1 has caused the attached Bug report to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case

Bug#458671: marked as done (gshare: FTBFS: error CS0123: A method or delegate `System.EventHandler(object, System.EventArgs)' parameters do not match delegate `System.Threading.ThreadStart()' paramet

Your message dated Sat, 05 Jan 2008 06:32:03 + with message-id [EMAIL PROTECTED] and subject line Bug#458671: fixed in gshare 0.94-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#449942: marked as done (gshare: debian/watch fails to report upstream's version)

Your message dated Sat, 05 Jan 2008 06:32:03 + with message-id [EMAIL PROTECTED] and subject line Bug#449942: fixed in gshare 0.94-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#424380: marked as done (gshare: FTBFS if built twice in a row)

Your message dated Sat, 05 Jan 2008 06:32:03 + with message-id [EMAIL PROTECTED] and subject line Bug#424380: fixed in gshare 0.94-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#456936: marked as done (libgtop2: FTBFS on GNU/kFreeBSD)

Your message dated Sat, 05 Jan 2008 06:32:04 + with message-id [EMAIL PROTECTED] and subject line Bug#456936: fixed in libgtop2 2.20.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

Bug#458387: marked as done (ikiwiki: table plugin with file= does not update when the data file changes)

Your message dated Sat, 05 Jan 2008 07:32:30 + with message-id [EMAIL PROTECTED] and subject line Bug#458387: fixed in ikiwiki 2.18 has caused the attached Bug report to be 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#450242: marked as done (mrt: debian/watch fails to report upstream's version)

Your message dated Sat, 05 Jan 2008 07:32:31 + with message-id [EMAIL PROTECTED] and subject line Bug#450242: fixed in mrt 2.2.2a-8 has caused the attached Bug report to be 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

<    1   2