Bug#875842: marked as done (im-config: Avoid using IBus through XIM)

Your message dated Thu, 21 Sep 2017 11:27:16 +0700 with message-id and subject line Closing bug has caused the Debian Bug report #875842, regarding im-config: Avoid using IBus through XIM to be marked as done. This means that

Bug#861634: marked as done (RFS: multimc/0.5.1-2 [ITP] -- A free, open source launcher for Minecraft)

Your message dated Thu, 21 Sep 2017 04:20:23 + with message-id and subject line closing RFS: multimc/0.5.1-2 [ITP] -- A free, open source launcher for Minecraft has caused the Debian Bug report #861634, regarding RFS: multimc/0.5.1-2 [ITP] -- A free, open

Bug#876317: marked as done (ruby-moneta: build-depends on default-mysql-server but relies on mariadb interfaces)

Your message dated Thu, 21 Sep 2017 04:04:30 + with message-id and subject line Bug#876317: fixed in ruby-moneta 1.0.0-2 has caused the Debian Bug report #876317, regarding ruby-moneta: build-depends on default-mysql-server but relies on mariadb

Bug#852590: marked as done (ltspfs: Update udevadm path)

Your message dated Thu, 21 Sep 2017 03:05:00 + with message-id and subject line Bug#852590: fixed in ltspfs 1.5-1 has caused the Debian Bug report #852590, regarding ltspfs: Update udevadm path to be marked as done. This means that you claim that the

Bug#873889: marked as done (elvish: FTBFS on ppc64(el): several tests fail)

Your message dated Thu, 21 Sep 2017 03:04:28 + with message-id and subject line Bug#873889: fixed in elvish 0.10.1-1 has caused the Debian Bug report #873889, regarding elvish: FTBFS on ppc64(el): several tests fail to be marked as done. This means that

Bug#539758: marked as done (wiki.debian.org: Wiki page not found by search.)

Your message dated Wed, 20 Sep 2017 21:41:58 -0400 with message-id and subject line (no subject) has caused the Debian Bug report #539758, regarding wiki.debian.org: Wiki page not found by search. to be marked as done. This means that you claim that

Bug#873894: marked as done (libsml: FTBFS on hurd-i386: O_NDELAY undeclared)

Your message dated Thu, 21 Sep 2017 01:07:53 + with message-id and subject line Bug#873894: fixed in libsml 0.1.1+git20170608-2 has caused the Debian Bug report #873894, regarding libsml: FTBFS on hurd-i386: O_NDELAY undeclared to be marked as done. This

Bug#873895: marked as done (libsml: FTBFS on non-Linux: libsml.a missing)

Your message dated Thu, 21 Sep 2017 01:07:53 + with message-id and subject line Bug#873895: fixed in libsml 0.1.1+git20170608-2 has caused the Debian Bug report #873895, regarding libsml: FTBFS on non-Linux: libsml.a missing to be marked as done. This

Bug#875949: marked as done (RFS: libsml/0.1.1+git20170608-2)

Your message dated Thu, 21 Sep 2017 02:41:17 +0200 with message-id <20170921004117.dmibvlpjhss53...@angband.pl> and subject line Re: Bug#875949: RFS: libsml/0.1.1+git20170608-2 has caused the Debian Bug report #875949, regarding RFS: libsml/0.1.1+git20170608-2 to be marked as done. This means

Bug#684707: marked as done (unattended-upgrades: Add a distro_release macro)

Your message dated Thu, 21 Sep 2017 02:30:36 +0200 with message-id <478b18c5-75e0-8b9e-4ba2-9afd8d01a...@canonical.com> and subject line Re: Bug#684707: Acknowledgement (unattended-upgrades: Add a distro_release macro) has caused the Debian Bug report #684707, regarding unattended-upgrades: Add a

Bug#506788: marked as done (man page basic fallacies )

Your message dated Thu, 21 Sep 2017 00:26:45 + with message-id and subject line Bug#506788: fixed in xml2 0.5-1 has caused the Debian Bug report #506788, regarding man page basic fallacies to be marked as done. This means that you claim that the problem

Bug#698072: marked as done (Hard coded ISO-8859-1)

Your message dated Thu, 21 Sep 2017 00:26:45 + with message-id and subject line Bug#698072: fixed in xml2 0.5-1 has caused the Debian Bug report #698072, regarding Hard coded ISO-8859-1 to be marked as done. This means that you claim that the problem has

Bug#754418: marked as done (xml2 version 0.5 available)

Your message dated Thu, 21 Sep 2017 00:26:45 + with message-id and subject line Bug#754418: fixed in xml2 0.5-1 has caused the Debian Bug report #754418, regarding xml2 version 0.5 available to be marked as done. This means that you claim that the problem

Bug#506805: marked as done (mangles UTF-8)

Your message dated Thu, 21 Sep 2017 00:26:45 + with message-id and subject line Bug#506805: fixed in xml2 0.5-1 has caused the Debian Bug report #506805, regarding mangles UTF-8 to be marked as done. This means that you claim that the problem has been

Bug#876286: marked as done (RFS: xml2/0.5-1 [QA,RC])

Your message dated Thu, 21 Sep 2017 02:07:37 +0200 with message-id <20170921000737.h7gk7jtafjsz3...@angband.pl> and subject line Re: Bug#876286: RFS: xml2/0.5-1 [QA,RC] has caused the Debian Bug report #876286, regarding RFS: xml2/0.5-1 [QA,RC] to be marked as done. This means that you claim that

Bug#745168: marked as done (gpm: Please use arch:linux-any)

Your message dated Wed, 20 Sep 2017 23:40:01 + with message-id and subject line Bug#745168: fixed in gpm 1.20.7-3 has caused the Debian Bug report #745168, regarding gpm: Please use arch:linux-any to be marked as done. This means that you claim that the

Bug#876249: marked as done (mark links{,2} Multi-Arch: foreign)

Your message dated Wed, 20 Sep 2017 23:40:54 + with message-id and subject line Bug#876249: fixed in links2 2.14-4 has caused the Debian Bug report #876249, regarding mark links{,2} Multi-Arch: foreign to be marked as done. This means that you claim that

Bug#496868: marked as done (Missing manpage for gpm-microtouch-setup(8))

Your message dated Wed, 20 Sep 2017 23:40:01 + with message-id and subject line Bug#496868: fixed in gpm 1.20.7-3 has caused the Debian Bug report #496868, regarding Missing manpage for gpm-microtouch-setup(8) to be marked as done. This means that you

Bug#875792: marked as done (doit: please make the build reproducible)

Your message dated Wed, 20 Sep 2017 23:37:13 + with message-id and subject line Bug#875792: fixed in doit 0.30.3-3 has caused the Debian Bug report #875792, regarding doit: please make the build reproducible to be marked as done. This means that you claim

Bug#869266: marked as done (commons-httpclient FTBFS: Plugin org.apache.maven.plugins:maven-surefire-plugin:2.19.1 or one of its dependencies could not be resolved)

Your message dated Thu, 21 Sep 2017 00:44:24 +0200 with message-id and subject line Re: commons-httpclient FTBFS: Plugin org.apache.maven.plugins:maven-surefire-plugin:2.19.1 or one of its dependencies could not be resolved has caused the Debian

Bug#610881: marked as done (gpm: Upstream contacts are broken)

Your message dated Thu, 21 Sep 2017 00:09:07 +0200 with message-id <20170920220906.ga5...@sym.noone.org> and subject line Re: Bug#610881: Homepage works now, sort of has caused the Debian Bug report #610881, regarding gpm: Upstream contacts are broken to be marked as done. This means that you

Bug#876235: marked as done (python-autobahn: missing B-D: openstack-pkg-tools)

Your message dated Wed, 20 Sep 2017 21:37:15 + with message-id and subject line Bug#876235: fixed in python-autobahn 17.7.1+dfsg1-2 has caused the Debian Bug report #876235, regarding python-autobahn: missing B-D: openstack-pkg-tools to be marked as done.

Bug#873568: marked as done (undefined symbol: Gpm_Wgetch)

Your message dated Wed, 20 Sep 2017 21:10:57 + with message-id and subject line Bug#873568: fixed in gpm 1.20.7-2 has caused the Debian Bug report #873568, regarding undefined symbol: Gpm_Wgetch to be marked as done. This means that you claim that the

Bug#782557: marked as done (glogic: Display not updated)

Your message dated Wed, 20 Sep 2017 21:10:19 + with message-id and subject line Bug#782557: fixed in glogic 2.6-3 has caused the Debian Bug report #782557, regarding glogic: Display not updated to be marked as done. This means that you claim that the

Bug#864582: marked as done (ITA: glogic -- graphical logic circuit simulator)

Your message dated Wed, 20 Sep 2017 21:10:19 + with message-id and subject line Bug#864582: fixed in glogic 2.6-3 has caused the Debian Bug report #864582, regarding ITA: glogic -- graphical logic circuit simulator to be marked as done. This means that

Bug#875973: marked as done (RFS: glogic/2.6-3 [ITA])

Your message dated Wed, 20 Sep 2017 22:21:13 +0200 with message-id <20170920202113.ldvaf2sfec2zh...@angband.pl> and subject line Re: Bug#875973: RFS: glogic/2.6-3 has caused the Debian Bug report #875973, regarding RFS: glogic/2.6-3 [ITA] to be marked as done. This means that you claim that the

Bug#876305: marked as done (polygen: FTBFS with ocaml 4.05.0)

Your message dated Wed, 20 Sep 2017 21:39:30 +0200 with message-id <20170920193930.deoutmc2tsdvn...@seneca.home.org> and subject line close has caused the Debian Bug report #876305, regarding polygen: FTBFS with ocaml 4.05.0 to be marked as done. This means that you claim that the problem has

Bug#851308: marked as done ([abi-dumper] New upstream release)

Your message dated Wed, 20 Sep 2017 19:04:34 + with message-id and subject line Bug#851308: fixed in abi-dumper 1.1-1 has caused the Debian Bug report #851308, regarding [abi-dumper] New upstream release to be marked as done. This means that you claim

Bug#855569: marked as done (dumpasn1: wrong output when reading from file)

Your message dated Wed, 20 Sep 2017 19:07:34 + with message-id and subject line Bug#855569: fixed in dumpasn1 20170309-1 has caused the Debian Bug report #855569, regarding dumpasn1: wrong output when reading from file to be marked as done. This means

Bug#869022: marked as done (guice: FTBFS: find: '/usr/share/maven-repo/org/codehaus/plexus/plexus-containers/*/*.jar': No such file or directory)

Your message dated Wed, 20 Sep 2017 19:15:31 +0100 with message-id <20170920181531.ga19...@alice.nomadium.lan> and subject line Re: guice: FTBFS: find: '/usr/share/maven-repo/org/codehaus/plexus/plexus-containers/*/*.jar': No such file or directory has caused the Debian Bug report #869022,

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

Your message dated Wed, 20 Sep 2017 18:04:48 + with message-id and subject line Bug#875814: fixed in ejabberd 17.08-2 has caused the Debian Bug report #875814, regarding ejabberd: [INTL:de] updated German debconf translation to be marked as done. This

Bug#869010: marked as done (cglib: FTBFS: find: '/usr/share/maven-repo/org/codehaus/plexus/plexus-containers/*/*.jar': No such file or directory)

Your message dated Wed, 20 Sep 2017 19:10:40 +0100 with message-id <20170920181040.ga19...@alice.nomadium.lan> and subject line Re: cglib: FTBFS: find: '/usr/share/maven-repo/org/codehaus/plexus/plexus-containers/*/*.jar': No such file or directory has caused the Debian Bug report #869010,

Bug#875540: marked as done (ejabberd: [INTL:pt_BR] Brazilian Portuguese debconf templates translation)

Your message dated Wed, 20 Sep 2017 18:04:48 + with message-id and subject line Bug#875540: fixed in ejabberd 17.08-2 has caused the Debian Bug report #875540, regarding ejabberd: [INTL:pt_BR] Brazilian Portuguese debconf templates translation to be

Bug#864102: marked as done (fis-gtm: Please stop Build-Depending on libgcrypt11-dev transition package)

Your message dated Wed, 20 Sep 2017 18:00:12 + with message-id and subject line Bug#864102: fixed in fis-gtm 6.3-002-1 has caused the Debian Bug report #864102, regarding fis-gtm: Please stop Build-Depending on libgcrypt11-dev transition package to be

Bug#742777: marked as done (grisbi: qif export - wrong amount format (french while should be english in all cases))

Your message dated Wed, 20 Sep 2017 17:49:30 + with message-id and subject line Bug#742777: fixed in grisbi 1.0.2-2 has caused the Debian Bug report #742777, regarding grisbi: qif export - wrong amount format (french while should be english in all cases)

Bug#874078: marked as done (lintian: improve binary-file-built-without-LFS-support info field)

Your message dated Wed, 20 Sep 2017 17:34:47 + with message-id and subject line Bug#874078: fixed in lintian 2.5.53 has caused the Debian Bug report #874078, regarding lintian: improve binary-file-built-without-LFS-support info field to be marked as done.

Bug#874381: marked as done (lintian: false-positive source-is-missing bug for css_browser_selector.js)

Your message dated Wed, 20 Sep 2017 17:34:47 + with message-id and subject line Bug#874381: fixed in lintian 2.5.53 has caused the Debian Bug report #874381, regarding lintian: false-positive source-is-missing bug for css_browser_selector.js to be marked

Bug#876003: marked as done (lintian: Wrong description of tag unknown-testsuite)

Your message dated Wed, 20 Sep 2017 17:34:48 + with message-id and subject line Bug#876003: fixed in lintian 2.5.53 has caused the Debian Bug report #876003, regarding lintian: Wrong description of tag unknown-testsuite to be marked as done. This means

Bug#875985: marked as done (lintian: Allow Testsuite: autopkgtest-pkg-octave)

Your message dated Wed, 20 Sep 2017 17:34:48 + with message-id and subject line Bug#875985: fixed in lintian 2.5.53 has caused the Debian Bug report #875985, regarding lintian: Allow Testsuite: autopkgtest-pkg-octave to be marked as done. This means that

Bug#872843: marked as done (lintian shouldn't check copyright_hints file for FIXME)

Your message dated Wed, 20 Sep 2017 17:34:47 + with message-id and subject line Bug#872843: fixed in lintian 2.5.53 has caused the Debian Bug report #872843, regarding lintian shouldn't check copyright_hints file for FIXME to be marked as done. This means

Bug#875933: marked as done (lintian: Please ignore debian/copyright_hints file from file-contains-fixme-placeholder tag checking)

Your message dated Wed, 20 Sep 2017 17:34:47 + with message-id and subject line Bug#872843: fixed in lintian 2.5.53 has caused the Debian Bug report #872843, regarding lintian: Please ignore debian/copyright_hints file from file-contains-fixme-placeholder

Bug#875509: marked as done (lintian: please upload a version that knows about Policy 4.1.0)

Your message dated Wed, 20 Sep 2017 17:34:48 + with message-id and subject line Bug#875509: fixed in lintian 2.5.53 has caused the Debian Bug report #875509, regarding lintian: please upload a version that knows about Policy 4.1.0 to be marked as done.

Bug#873702: marked as done (lintian: False positive: desktop-entry-lacks-keywords-entry)

Your message dated Wed, 20 Sep 2017 17:34:47 + with message-id and subject line Bug#873702: fixed in lintian 2.5.53 has caused the Debian Bug report #873702, regarding lintian: False positive: desktop-entry-lacks-keywords-entry to be marked as done. This

Bug#874121: marked as done (lintian: Please add more packagename to section mappings)

Your message dated Wed, 20 Sep 2017 17:34:47 + with message-id and subject line Bug#874121: fixed in lintian 2.5.53 has caused the Debian Bug report #874121, regarding lintian: Please add more packagename to section mappings to be marked as done. This

Bug#873434: marked as done (lintian: Please check for @import url(http://...) in /usr/share/doc)

Your message dated Wed, 20 Sep 2017 17:34:47 + with message-id and subject line Bug#873434: fixed in lintian 2.5.53 has caused the Debian Bug report #873434, regarding lintian: Please check for @import url(http://...) in /usr/share/doc to be marked as

Bug#873458: marked as done (lintian: Please add autopkgtest-pkg-elpa as a valid value for Testsuite)

Your message dated Wed, 20 Sep 2017 17:34:47 + with message-id and subject line Bug#873458: fixed in lintian 2.5.53 has caused the Debian Bug report #873458, regarding lintian: Please add autopkgtest-pkg-elpa as a valid value for Testsuite to be marked as

Bug#873096: marked as done (Warn about using deprecated /usr/bin/nodejs location)

Your message dated Wed, 20 Sep 2017 17:34:47 + with message-id and subject line Bug#873096: fixed in lintian 2.5.53 has caused the Debian Bug report #873096, regarding Warn about using deprecated /usr/bin/nodejs location to be marked as done. This means

Bug#873323: marked as done (lintian -- False positives on copyright-year-in-future)

Your message dated Wed, 20 Sep 2017 17:34:47 + with message-id and subject line Bug#873323: fixed in lintian 2.5.53 has caused the Debian Bug report #873323, regarding lintian -- False positives on copyright-year-in-future to be marked as done. This

Bug#873211: marked as done (Please warn about binary packages shipping .class files)

Your message dated Wed, 20 Sep 2017 17:34:47 + with message-id and subject line Bug#873211: fixed in lintian 2.5.53 has caused the Debian Bug report #873211, regarding Please warn about binary packages shipping .class files to be marked as done. This

Bug#873701: marked as done (lintian: False positive: apache2-unparsable-dependency)

Your message dated Wed, 20 Sep 2017 17:34:47 + with message-id and subject line Bug#873701: fixed in lintian 2.5.53 has caused the Debian Bug report #873701, regarding lintian: False positive: apache2-unparsable-dependency to be marked as done. This means

Bug#874659: marked as done (orig-tarball-missing-upstream-signature should not trigger on repacked tarballs)

Your message dated Wed, 20 Sep 2017 17:34:47 + with message-id and subject line Bug#871957: fixed in lintian 2.5.53 has caused the Debian Bug report #871957, regarding orig-tarball-missing-upstream-signature should not trigger on repacked tarballs to be

Bug#870822: marked as done (lintian: [checks/python] Check for applications using Python 2.x)

Your message dated Wed, 20 Sep 2017 17:34:47 + with message-id and subject line Bug#870822: fixed in lintian 2.5.53 has caused the Debian Bug report #870822, regarding lintian: [checks/python] Check for applications using Python 2.x to be marked as done.

Bug#872611: marked as done (lintian: Please warn on package using sensible-utils w/o relationship)

Your message dated Wed, 20 Sep 2017 17:34:47 + with message-id and subject line Bug#872611: fixed in lintian 2.5.53 has caused the Debian Bug report #872611, regarding lintian: Please warn on package using sensible-utils w/o relationship to be marked as

Bug#871957: marked as done ([lintian] orig-tarball-missing-upstream-signature should exclude repacks)

Your message dated Wed, 20 Sep 2017 17:34:47 + with message-id and subject line Bug#871957: fixed in lintian 2.5.53 has caused the Debian Bug report #871957, regarding [lintian] orig-tarball-missing-upstream-signature should exclude repacks to be marked

Bug#872076: marked as done (lintian: please warn about build-dependency on dh-systemd)

Your message dated Wed, 20 Sep 2017 17:34:47 + with message-id and subject line Bug#872076: fixed in lintian 2.5.53 has caused the Debian Bug report #872076, regarding lintian: please warn about build-dependency on dh-systemd to be marked as done. This

Bug#872042: marked as done (lintian: please check for missing calls to dpkg-maintscript-helper)

Your message dated Wed, 20 Sep 2017 17:34:47 + with message-id and subject line Bug#872042: fixed in lintian 2.5.53 has caused the Debian Bug report #872042, regarding lintian: please check for missing calls to dpkg-maintscript-helper to be marked as done.

Bug#871046: marked as done (ruby-json FTBFS: It seems your ruby installation is missing psych (for YAML output).)

Your message dated Wed, 20 Sep 2017 18:39:26 +0100 with message-id <20170920173926.ga19...@alice.nomadium.lan> and subject line Re: ruby-json FTBFS: It seems your ruby installation is missing psych (for YAML output). has caused the Debian Bug report #871046, regarding ruby-json FTBFS: It seems

Bug#870758: marked as done (lintian: [checks/python] Please check for packages build-depending on "python-sphinx | python3-sphinx")

Your message dated Wed, 20 Sep 2017 17:34:47 + with message-id and subject line Bug#870758: fixed in lintian 2.5.53 has caused the Debian Bug report #870758, regarding lintian: [checks/python] Please check for packages build-depending on "python-sphinx |

Bug#871767: marked as done (lintian: [checks/cruft] use substr instead of substring in example)

Your message dated Wed, 20 Sep 2017 17:34:47 + with message-id and subject line Bug#871767: fixed in lintian 2.5.53 has caused the Debian Bug report #871767, regarding lintian: [checks/cruft] use substr instead of substring in example to be marked as done.

Bug#871575: marked as done (lintian: maintainer-address-causes-mail-loops-or-bounces should be fixed to allow @packages.debian.org emails)

Your message dated Wed, 20 Sep 2017 17:34:47 + with message-id and subject line Bug#871575: fixed in lintian 2.5.53 has caused the Debian Bug report #871575, regarding lintian: maintainer-address-causes-mail-loops-or-bounces should be fixed to allow

Bug#870069: marked as done (orig-tarball-missing-upstream-signature error breaks rebuilding existing packages and more)

Your message dated Wed, 20 Sep 2017 17:34:47 + with message-id and subject line Bug#870069: fixed in lintian 2.5.53 has caused the Debian Bug report #870069, regarding orig-tarball-missing-upstream-signature error breaks rebuilding existing packages and

Bug#869788: marked as done (lintian: false positives in copyright-year-in-future)

Your message dated Wed, 20 Sep 2017 17:34:47 + with message-id and subject line Bug#869788: fixed in lintian 2.5.53 has caused the Debian Bug report #869788, regarding lintian: false positives in copyright-year-in-future to be marked as done. This means

Bug#870722: marked as done (lintian: orig-tarball-missing-upstream-signature has inflated severity)

Your message dated Wed, 20 Sep 2017 17:34:47 + with message-id and subject line Bug#870722: fixed in lintian 2.5.53 has caused the Debian Bug report #870722, regarding lintian: orig-tarball-missing-upstream-signature has inflated severity to be marked as

Bug#870730: marked as done (lintian: [checks/python] Please check for packages that Build-Depend on Python 2.x version of Sphinx)

Your message dated Wed, 20 Sep 2017 17:34:47 + with message-id and subject line Bug#870730: fixed in lintian 2.5.53 has caused the Debian Bug report #870730, regarding lintian: [checks/python] Please check for packages that Build-Depend on Python 2.x

Bug#870681: marked as done (lintian: [checks/python] Check for python-foo without python3-foo)

Your message dated Wed, 20 Sep 2017 17:34:47 + with message-id and subject line Bug#870681: fixed in lintian 2.5.53 has caused the Debian Bug report #870681, regarding lintian: [checks/python] Check for python-foo without python3-foo to be marked as done.

Bug#870272: marked as done (lintian: Should warn about python3-foo not in "Section: python")

Your message dated Wed, 20 Sep 2017 17:34:47 + with message-id and subject line Bug#870272: fixed in lintian 2.5.53 has caused the Debian Bug report #870272, regarding lintian: Should warn about python3-foo not in "Section: python" to be marked as done.

Bug#870649: marked as done (lintian: false positive codeless-jar with Clojure reader conditionals)

Your message dated Wed, 20 Sep 2017 17:34:47 + with message-id and subject line Bug#870649: fixed in lintian 2.5.53 has caused the Debian Bug report #870649, regarding lintian: false positive codeless-jar with Clojure reader conditionals to be marked as

Bug#870199: marked as done (lintian: file-contains-fixme-placeholder is "Certainty: certain" but has false positives)

Your message dated Wed, 20 Sep 2017 17:34:47 + with message-id and subject line Bug#870199: fixed in lintian 2.5.53 has caused the Debian Bug report #870199, regarding lintian: file-contains-fixme-placeholder is "Certainty: certain" but has false

Bug#869750: marked as done (lintian: fix for readelf parsing with binutils 2.29 on ppc64el)

Your message dated Wed, 20 Sep 2017 17:34:47 + with message-id and subject line Bug#869750: fixed in lintian 2.5.53 has caused the Debian Bug report #869750, regarding lintian: fix for readelf parsing with binutils 2.29 on ppc64el to be marked as done.

Bug#869587: marked as done (lintian: false positive for unconditional-use-of-dpkg-statoverride)

Your message dated Wed, 20 Sep 2017 17:34:47 + with message-id and subject line Bug#869587: fixed in lintian 2.5.53 has caused the Debian Bug report #869587, regarding lintian: false positive for unconditional-use-of-dpkg-statoverride to be marked as done.

Bug#868897: marked as done (en_US help uses British spelling)

Your message dated Wed, 20 Sep 2017 17:34:47 + with message-id and subject line Bug#868897: fixed in lintian 2.5.53 has caused the Debian Bug report #868897, regarding en_US help uses British spelling to be marked as done. This means that you claim that

Bug#869541: marked as done (lintian warns both with and without autotools-dev build-dep)

Your message dated Wed, 20 Sep 2017 17:34:47 + with message-id and subject line Bug#869541: fixed in lintian 2.5.53 has caused the Debian Bug report #869541, regarding lintian warns both with and without autotools-dev build-dep to be marked as done. This

Bug#762956: marked as done (lintian: add embedded-library libopenjpeg)

Your message dated Wed, 20 Sep 2017 17:34:46 + with message-id and subject line Bug#762956: fixed in lintian 2.5.53 has caused the Debian Bug report #762956, regarding lintian: add embedded-library libopenjpeg to be marked as done. This means that you

Bug#779675: marked as done (lintian: Add flag --list-tags that will list all tags Lintian knows about)

Your message dated Wed, 20 Sep 2017 17:34:46 + with message-id and subject line Bug#779675: fixed in lintian 2.5.53 has caused the Debian Bug report #779675, regarding lintian: Add flag --list-tags that will list all tags Lintian knows about to be marked

Bug#865570: marked as done (lintian: description of testsuite-autopkgtest-missing is unhelpful/incorrect)

Your message dated Wed, 20 Sep 2017 17:34:47 + with message-id and subject line Bug#865531: fixed in lintian 2.5.53 has caused the Debian Bug report #865531, regarding lintian: description of testsuite-autopkgtest-missing is unhelpful/incorrect to be

Bug#865531: marked as done (lintian: description of testsuite-autopkgtest-missing is unhelpful/incorrect)

Your message dated Wed, 20 Sep 2017 17:34:47 + with message-id and subject line Bug#865531: fixed in lintian 2.5.53 has caused the Debian Bug report #865531, regarding lintian: description of testsuite-autopkgtest-missing is unhelpful/incorrect to be

Bug#849622: marked as done (lintian: unexpected description-starts-with-leading-spaces)

Your message dated Wed, 20 Sep 2017 17:34:47 + with message-id and subject line Bug#849622: fixed in lintian 2.5.53 has caused the Debian Bug report #849622, regarding lintian: unexpected description-starts-with-leading-spaces to be marked as done. This

Bug#857123: marked as done (lintian: warning about missing classpath is confusing)

Your message dated Wed, 20 Sep 2017 17:34:47 + with message-id and subject line Bug#857123: fixed in lintian 2.5.53 has caused the Debian Bug report #857123, regarding lintian: warning about missing classpath is confusing to be marked as done. This means

Bug#835120: marked as done (lintian: false positive: virtual-package-depends-without-real-package-depends for bacula-director)

Your message dated Wed, 20 Sep 2017 17:34:46 + with message-id and subject line Bug#835120: fixed in lintian 2.5.53 has caused the Debian Bug report #835120, regarding lintian: false positive: virtual-package-depends-without-real-package-depends for

Bug#814599: marked as done (lintian: package-installs-into-obsolete-dir: mention filename requirements for /usr/share/bash-completion/completions/)

Your message dated Wed, 20 Sep 2017 17:34:46 + with message-id and subject line Bug#814599: fixed in lintian 2.5.53 has caused the Debian Bug report #814599, regarding lintian: package-installs-into-obsolete-dir: mention filename requirements for 

Bug#847144: marked as done (lintian: Please reword init.d-script-needs-depends-on-lsb-base, drop versioned dependency)

Your message dated Wed, 20 Sep 2017 17:34:47 + with message-id and subject line Bug#847144: fixed in lintian 2.5.53 has caused the Debian Bug report #847144, regarding lintian: Please reword init.d-script-needs-depends-on-lsb-base, drop versioned

Bug#690342: marked as done (corosync: cannot set lrm parameters)

Your message dated Wed, 20 Sep 2017 18:55:46 +0200 with message-id <87fubh48dp@lant.ki.iif.hu> and subject line Re: corosync: cannot set lrm parameters has caused the Debian Bug report #690342, regarding corosync: cannot set lrm parameters to be marked as done. This means that you claim that

Bug#681713: marked as done (lintian: Please add a test which checks Vcs-Browser headers for hardcoded revisions/commits)

Your message dated Wed, 20 Sep 2017 17:34:46 + with message-id and subject line Bug#681713: fixed in lintian 2.5.53 has caused the Debian Bug report #681713, regarding lintian: Please add a test which checks Vcs-Browser headers for hardcoded

Bug#876269: marked as done (ftbfs, building indep packages)

Your message dated Wed, 20 Sep 2017 18:30:37 +0100 with message-id <20170920173037.ga19...@alice.nomadium.lan> and subject line Re: ftbfs, building indep packages has caused the Debian Bug report #876269, regarding ftbfs, building indep packages to be marked as done. This means that you claim

Bug#871953: marked as done (apparmor: init script unconditionally uses systemd-detect-virt)

Your message dated Wed, 20 Sep 2017 16:34:13 + with message-id and subject line Bug#871953: fixed in apparmor 2.11.0-11 has caused the Debian Bug report #871953, regarding apparmor: init script unconditionally uses systemd-detect-virt to be marked as done.

Bug#865206: marked as done (apparmor: Should apparmor abstractions allow flatpak directories?)

Your message dated Wed, 20 Sep 2017 16:34:13 + with message-id and subject line Bug#865206: fixed in apparmor 2.11.0-11 has caused the Debian Bug report #865206, regarding apparmor: Should apparmor abstractions allow flatpak directories? to be marked as

Bug#872167: marked as done (dh-apparmor: Please a add "our $VERSION = ''" to dh_apparmor)

Your message dated Wed, 20 Sep 2017 16:34:13 + with message-id and subject line Bug#872167: fixed in apparmor 2.11.0-11 has caused the Debian Bug report #872167, regarding dh-apparmor: Please a add "our $VERSION = ''" to dh_apparmor to be marked as done.

Bug#860195: marked as done (graphite-web: new upstream version (1.0.0))

Your message dated Wed, 20 Sep 2017 15:54:43 + with message-id and subject line Bug#860195: fixed in graphite-web 1.0.2+debian-1 has caused the Debian Bug report #860195, regarding graphite-web: new upstream version (1.0.0) to be marked as done. This

Bug#862084: marked as done (graphite-web: Stupid version number testing as string)

Your message dated Wed, 20 Sep 2017 15:54:43 + with message-id and subject line Bug#862084: fixed in graphite-web 1.0.2+debian-1 has caused the Debian Bug report #862084, regarding graphite-web: Stupid version number testing as string to be marked as done.

Bug#876210: marked as done (pktanon: FTBFS on non-Linux: missing headers required for raw sockets)

Your message dated Wed, 20 Sep 2017 15:55:54 + with message-id and subject line Bug#876210: fixed in pktanon 2~git20160407.0.2bde4f2+dfsg-2 has caused the Debian Bug report #876210, regarding pktanon: FTBFS on non-Linux: missing headers required for raw

Bug#810428: marked as done (lcdproc: please switch to libusb 1.0)

Your message dated Wed, 20 Sep 2017 15:55:24 + with message-id and subject line Bug#810428: fixed in lcdproc 0.5.9-2 has caused the Debian Bug report #810428, regarding lcdproc: please switch to libusb 1.0 to be marked as done. This means that you claim

Bug#840516: marked as done (doesn't work with django 1.10)

Your message dated Wed, 20 Sep 2017 15:54:43 + with message-id and subject line Bug#840516: fixed in graphite-web 1.0.2+debian-1 has caused the Debian Bug report #840516, regarding doesn't work with django 1.10 to be marked as done. This means that you

Bug#849080: marked as done (graphite-web: race condition in /usr/bin/graphite-build-search-index)

Your message dated Wed, 20 Sep 2017 15:54:43 + with message-id and subject line Bug#849080: fixed in graphite-web 1.0.2+debian-1 has caused the Debian Bug report #849080, regarding graphite-web: race condition in /usr/bin/graphite-build-search-index to be

Bug#868073: marked as done (bioperl-run: FTBFS: t/Bowtie.t failure)

Your message dated Wed, 20 Sep 2017 15:49:53 + with message-id and subject line Bug#868073: fixed in bioperl-run 1.7.2-1 has caused the Debian Bug report #868073, regarding bioperl-run: FTBFS: t/Bowtie.t failure to be marked as done. This means that you

Bug#874972: marked as done ([klatexformula] Future Qt4 removal from Buster)

Your message dated Wed, 20 Sep 2017 17:11:41 +0200 with message-id <24690485.XSWhZ5zyHY@guymontag> and subject line Re: Bug#874972: [klatexformula] Future Qt4 removal from Buster has caused the Debian Bug report #874972, regarding [klatexformula] Future Qt4 removal from Buster to be marked as

Bug#874383: marked as done (torbrowser-launcher: AppArmor failures)

Your message dated Wed, 20 Sep 2017 15:26:20 + with message-id and subject line Bug#874383: fixed in torbrowser-launcher 0.2.8-2 has caused the Debian Bug report #874383, regarding torbrowser-launcher: AppArmor failures to be marked as done. This means

Bug#741616: marked as done (graphite-carbon: execute permission on whisper files)

Your message dated Wed, 20 Sep 2017 16:11:24 +0200 with message-id <20170920161124.7ee4e...@yelina.brachium-system.net> and subject line Re: graphite-carbon: execute permission on whisper files has caused the Debian Bug report #741616, regarding graphite-carbon: execute permission on whisper files

Bug#875605: marked as done (piuparts: esac missing in post_purge_exception script (develop branch) and yields error)

Your message dated Wed, 20 Sep 2017 15:20:07 +0200 with message-id <20170920132007.ga7...@layer-acht.org> and subject line fixed in git has caused the Debian Bug report #875605, regarding piuparts: esac missing in post_purge_exception script (develop branch) and yields error to be marked as

Bug#875664: marked as done (piuparts.debian.org: Syntax error in post_purge_exceptions)

Your message dated Wed, 20 Sep 2017 15:20:07 +0200 with message-id <20170920132007.ga7...@layer-acht.org> and subject line fixed in git has caused the Debian Bug report #875605, regarding piuparts.debian.org: Syntax error in post_purge_exceptions to be marked as done. This means that you claim

Bug#874408: marked as done (debian mirror mirror.yandex.ru issues)

Your message dated Wed, 20 Sep 2017 13:06:36 + with message-id <20170920130636.orts3y2vjbyir...@sarek.noreply.org> and subject line Re: Bug#874408: debian mirror mirror.yandex.ru issues has caused the Debian Bug report #874408, regarding debian mirror mirror.yandex.ru issues to be marked as

  1   2   >