Bug#896192: marked as done (cloudcompare FTBFS on architectures where char is unsigned)

Your message dated Mon, 28 Jan 2019 08:15:29 +0100 with message-id <71d53c25888f65e4aafd9209766d6...@phys.ethz.ch> and subject line cloudcompare FTBFS on architectures where char is unsigned has caused the Debian Bug report #896192, regarding cloudcompare FTBFS on architectures where char is

Bug#912627: marked as done (asymptote: Asymptote crashes on attempt to create pdf file)

Your message dated Mon, 28 Jan 2019 06:04:15 + with message-id and subject line Bug#912627: fixed in asymptote 2.47-2 has caused the Debian Bug report #912627, regarding asymptote: Asymptote crashes on attempt to create pdf file to be marked as done. This means that you claim that the

Bug#635619: marked as done (ipe: Segfaults on JPG import)

Your message dated Sun, 27 Jan 2019 22:51:10 -0600 with message-id <21525102.7Na66R36Bd@riemann> and subject line Re: ipe: Segfaults on JPG import has caused the Debian Bug report #635619, regarding ipe: Segfaults on JPG import to be marked as done. This means that you claim that the problem has

Bug#728479: marked as done (ipe: buffer overflow! I cannot complete snapping examples 2, 3, and 6)

Your message dated Sun, 27 Jan 2019 22:41:34 -0600 with message-id <5283578.GYRp15vA60@riemann> and subject line Re: ipe: buffer overflow! I cannot complete snapping examples 2, 3, and 6 has caused the Debian Bug report #728479, regarding ipe: buffer overflow! I cannot complete snapping examples

Bug#808957: marked as done (/usr/bin/ipetoipe: ipetoipe does not export in the EPS format any more)

Your message dated Sun, 27 Jan 2019 22:43:30 -0600 with message-id <2588569.XG2dRNVXPi@riemann> and subject line Re: Bug#808957: /usr/bin/ipetoipe: ipetoipe does not export in the EPS format any more has caused the Debian Bug report #808957, regarding /usr/bin/ipetoipe: ipetoipe does not export

Bug#920597: marked as done (docker.io: Unable to start daemon: "containerd" executable file not found in PATH)

Your message dated Mon, 28 Jan 2019 03:20:43 + with message-id and subject line Bug#920597: fixed in docker.io 18.09.1+dfsg1-4 has caused the Debian Bug report #920597, regarding docker.io: Unable to start daemon: "containerd" executable file not found in PATH to be marked as done. This

Bug#920661: marked as done (docker.io: failed to start shim: exec: "containerd-shim": executable file not found in $PATH: unknown)

Your message dated Mon, 28 Jan 2019 13:53:15 +1100 with message-id <2177541.J6sLav8ZAG@deblab> and subject line Re: Bug#920661: docker.io: failed to start shim: exec: "containerd-shim": executable file not found in $PATH: unknown has caused the Debian Bug report #920661, regarding docker.io:

Bug#882729: marked as done (signing-party: spelling fixes)

Your message dated Mon, 28 Jan 2019 02:49:15 + with message-id and subject line Bug#882729: fixed in signing-party 2.8-1 has caused the Debian Bug report #882729, regarding signing-party: spelling fixes to be marked as done. This means that you claim that the problem has been dealt with. If

Bug#872529: marked as done (caff: should put the TTY in a sane state before prompts)

Your message dated Mon, 28 Jan 2019 02:49:15 + with message-id and subject line Bug#872529: fixed in signing-party 2.8-1 has caused the Debian Bug report #872529, regarding caff: should put the TTY in a sane state before prompts to be marked as done. This means that you claim that the

Bug#917595: marked as done (umoci: FTBFS (cannot find package "github.com/fatih/color"))

Your message dated Mon, 28 Jan 2019 02:49:28 + with message-id and subject line Bug#917595: fixed in umoci 0.4.3+dfsg-1 has caused the Debian Bug report #917595, regarding umoci: FTBFS (cannot find package "github.com/fatih/color") to be marked as done. This means that you claim that the

Bug#917406: marked as done (ITA: elinks -- advanced text-mode WWW browser)

Your message dated Mon, 28 Jan 2019 02:46:06 + with message-id and subject line Bug#917406: fixed in elinks 0.13~20190125-1 has caused the Debian Bug report #917406, regarding ITA: elinks -- advanced text-mode WWW browser to be marked as done. This means that you claim that the problem has

Bug#797934: marked as done (elinks: Support for SSL authentication using client certs)

Your message dated Mon, 28 Jan 2019 02:46:06 + with message-id and subject line Bug#797934: fixed in elinks 0.13~20190125-1 has caused the Debian Bug report #797934, regarding elinks: Support for SSL authentication using client certs to be marked as done. This means that you claim that the

Bug#919473: marked as done (zapping: Settings schema 'net.sf.Zapping.plugins.teletext' does not contain a key named 'method')

Your message dated Mon, 28 Jan 2019 02:49:50 + with message-id and subject line Bug#919473: fixed in zapping 0.10~cvs6-16 has caused the Debian Bug report #919473, regarding zapping: Settings schema 'net.sf.Zapping.plugins.teletext' does not contain a key named 'method' to be marked as done.

Bug#905097: marked as done (signing-party: gpglist crashes for (some?) signature revocations)

Your message dated Mon, 28 Jan 2019 02:49:15 + with message-id and subject line Bug#905097: fixed in signing-party 2.8-1 has caused the Debian Bug report #905097, regarding signing-party: gpglist crashes for (some?) signature revocations to be marked as done. This means that you claim that

Bug#866015: marked as done (elinks: SSL error with some websites)

Your message dated Mon, 28 Jan 2019 02:46:06 + with message-id and subject line Bug#866015: fixed in elinks 0.13~20190125-1 has caused the Debian Bug report #866015, regarding elinks: SSL error with some websites to be marked as done. This means that you claim that the problem has been dealt

Bug#891575: marked as done (elinks: CVE-2012-6709)

Your message dated Mon, 28 Jan 2019 02:46:06 + with message-id and subject line Bug#891575: fixed in elinks 0.13~20190125-1 has caused the Debian Bug report #891575, regarding elinks: CVE-2012-6709 to be marked as done. This means that you claim that the problem has been dealt with. If this

Bug#919820: marked as done (mysql-connector-python: CVE-2019-2435)

Your message dated Mon, 28 Jan 2019 02:48:06 + with message-id and subject line Bug#919820: fixed in mysql-connector-python 8.0.14-1 has caused the Debian Bug report #919820, regarding mysql-connector-python: CVE-2019-2435 to be marked as done. This means that you claim that the problem has

Bug#797931: marked as done (elinks: Does not support SSL rehandshakes)

Your message dated Mon, 28 Jan 2019 02:46:06 + with message-id and subject line Bug#797931: fixed in elinks 0.13~20190125-1 has caused the Debian Bug report #797931, regarding elinks: Does not support SSL rehandshakes to be marked as done. This means that you claim that the problem has been

Bug#797968: marked as done (elinks: Please add support for TLS SNI)

Your message dated Mon, 28 Jan 2019 02:46:06 + with message-id and subject line Bug#797968: fixed in elinks 0.13~20190125-1 has caused the Debian Bug report #797968, regarding elinks: Please add support for TLS SNI to be marked as done. This means that you claim that the problem has been

Bug#757631: marked as done (elinks: HTML5 source element display missing)

Your message dated Mon, 28 Jan 2019 02:46:06 + with message-id and subject line Bug#757631: fixed in elinks 0.13~20190125-1 has caused the Debian Bug report #757631, regarding elinks: HTML5 source element display missing to be marked as done. This means that you claim that the problem has

Bug#856852: marked as done (cert_verify is disabled by default)

Your message dated Mon, 28 Jan 2019 02:46:06 + with message-id and subject line Bug#856852: fixed in elinks 0.13~20190125-1 has caused the Debian Bug report #856852, regarding cert_verify is disabled by default to be marked as done. This means that you claim that the problem has been dealt

Bug#740981: marked as done (elinks: doesn't check if hostname matches certificate's CN/SAN (CWE-297))

Your message dated Mon, 28 Jan 2019 02:46:06 + with message-id and subject line Bug#740981: fixed in elinks 0.13~20190125-1 has caused the Debian Bug report #740981, regarding elinks: doesn't check if hostname matches certificate's CN/SAN (CWE-297) to be marked as done. This means that you

Bug#913548: marked as done (spamassassin: running /etc/cron.daily/spamassassin gives: Unescaped left brace in regex is deprecated here)

Your message dated Mon, 28 Jan 2019 15:33:30 +1300 with message-id <87bm41se85@silverfish.pri> and subject line Re: Bug#913548: spamassassin: running /etc/cron.daily/spamassassin gives: Unescaped left brace in regex is deprecated here has caused the Debian Bug report #913548, regarding

Bug#919637: marked as done (RFS: elinks/0.13~20190125-1 [ITA])

Your message dated Mon, 28 Jan 2019 03:05:51 +0100 with message-id <20190128020551.4vuxh33trtc72...@angband.pl> and subject line Re: Bug#919637: RFS: elinks/0.13~20190114-1 [ITA] has caused the Debian Bug report #919637, regarding RFS: elinks/0.13~20190125-1 [ITA] to be marked as done. This means

Bug#919950: marked as done (Please drop compatibility hack for liblzma.so.2 (last present in squeeze))

Your message dated Mon, 28 Jan 2019 01:52:05 + with message-id and subject line Bug#919950: fixed in xz-utils 5.2.4-1 has caused the Debian Bug report #919950, regarding Please drop compatibility hack for liblzma.so.2 (last present in squeeze) to be marked as done. This means that you claim

Bug#920444: marked as done (RFS: zapping/0.10~cvs6-16 [QA] [RC])

Your message dated Mon, 28 Jan 2019 02:51:30 +0100 with message-id <20190128015130.4niqierq6uqgp...@angband.pl> and subject line Re: Bug#920444: RFS: zapping/0.10~cvs6-16 [QA] [RC] has caused the Debian Bug report #920444, regarding RFS: zapping/0.10~cvs6-16 [QA] [RC] to be marked as done. This

Bug#685203: marked as done (xz-utils is "Priority: required" but not pseudo-essential)

Your message dated Mon, 28 Jan 2019 01:52:05 + with message-id and subject line Bug#685203: fixed in xz-utils 5.2.4-1 has caused the Debian Bug report #685203, regarding xz-utils is "Priority: required" but not pseudo-essential to be marked as done. This means that you claim that the problem

Bug#826382: marked as done (xz-utils: git packaging repo not updated)

Your message dated Mon, 28 Jan 2019 01:52:05 + with message-id and subject line Bug#826382: fixed in xz-utils 5.2.4-1 has caused the Debian Bug report #826382, regarding xz-utils: git packaging repo not updated to be marked as done. This means that you claim that the problem has been dealt

Bug#851615: marked as done (xz-utils: please upgrade to 5.2.3)

Your message dated Mon, 28 Jan 2019 01:52:05 + with message-id and subject line Bug#851615: fixed in xz-utils 5.2.4-1 has caused the Debian Bug report #851615, regarding xz-utils: please upgrade to 5.2.3 to be marked as done. This means that you claim that the problem has been dealt with. If

Bug#920487: marked as done (RFS: wxmaxima/19.01.2-1)

Your message dated Mon, 28 Jan 2019 02:45:17 +0100 with message-id <20190128014517.fhgwpoasyhcbg...@angband.pl> and subject line Re: Bug#920487: RFS: wxmaxima/19.01.2-1 has caused the Debian Bug report #920487, regarding RFS: wxmaxima/19.01.2-1 to be marked as done. This means that you claim that

Bug#631768: marked as done (gnomint saved window size after using the quit button is out of range)

Your message dated Mon, 28 Jan 2019 01:34:17 + with message-id and subject line Bug#631768: fixed in gnomint 1.3.0-1 has caused the Debian Bug report #631768, regarding gnomint saved window size after using the quit button is out of range to be marked as done. This means that you claim that

Bug#920654: marked as done (RFS: liboauth/1.0.3-3 [QA])

Your message dated Mon, 28 Jan 2019 02:34:20 +0100 with message-id <20190128013420.qtfths24y3qlf...@angband.pl> and subject line Re: Bug#920654: RFS: liboauth/1.0.3-3 [QA] has caused the Debian Bug report #920654, regarding RFS: liboauth/1.0.3-3 [QA] to be marked as done. This means that you

Bug#885817: marked as done (gnomint: Depends on gconf)

Your message dated Mon, 28 Jan 2019 01:34:17 + with message-id and subject line Bug#885817: fixed in gnomint 1.3.0-1 has caused the Debian Bug report #885817, regarding gnomint: Depends on gconf to be marked as done. This means that you claim that the problem has been dealt with. If this is

Bug#855200: marked as done (gnomint: segfault when exporting private keys)

Your message dated Mon, 28 Jan 2019 01:34:17 + with message-id and subject line Bug#855200: fixed in gnomint 1.3.0-1 has caused the Debian Bug report #855200, regarding gnomint: segfault when exporting private keys to be marked as done. This means that you claim that the problem has been

Bug#920660: marked as done (RFS: rmlint/2.8.0-3)

Your message dated Mon, 28 Jan 2019 02:31:08 +0100 with message-id <20190128013108.zhmohvfsmekzt...@angband.pl> and subject line Re: Bug#920660: RFS: rmlint/2.8.0-3 has caused the Debian Bug report #920660, regarding RFS: rmlint/2.8.0-3 to be marked as done. This means that you claim that the

Bug#907826: marked as done (RFS: gnomint/1.3.0-1 [QA])

Your message dated Mon, 28 Jan 2019 02:12:44 +0100 with message-id <20190128011244.5qtqna6qn4teb...@angband.pl> and subject line Re: Bug#907826: RFS: gnomint/1.3.0-1 [QA] has caused the Debian Bug report #907826, regarding RFS: gnomint/1.3.0-1 [QA] to be marked as done. This means that you claim

Bug#920471: marked as done (RFS: fathom/1.0+git.20190120.0439ca-1)

Your message dated Mon, 28 Jan 2019 01:59:20 +0100 with message-id <20190128005920.lcrfx23b3yosk...@angband.pl> and subject line Re: Bug#920471: RFS: fathom/1.0+git.20190120.0439ca-1 has caused the Debian Bug report #920471, regarding RFS: fathom/1.0+git.20190120.0439ca-1 to be marked as done.

Bug#845624: marked as done (lxqt: Touchpad features)

Your message dated Mon, 28 Jan 2019 00:20:56 + with message-id and subject line Bug#845624: fixed in lxqt-config 0.14.0-1 has caused the Debian Bug report #845624, regarding lxqt: Touchpad features to be marked as done. This means that you claim that the problem has been dealt with. If this

Bug#900421: marked as done (improve "wiki account creation delayed" message)

Your message dated Mon, 28 Jan 2019 00:10:24 + with message-id <20190128001024.z5cafmajiptgv...@tack.einval.com> and subject line Re: Bug#900421: improve "wiki account creation delayed" message has caused the Debian Bug report #900421, regarding improve "wiki account creation delayed" message

Bug#762918: marked as done (Please convert all scripts to not use bash)

Your message dated Sun, 27 Jan 2019 15:46:15 -0800 with message-id <20190127234615.ga103...@google.com> and subject line Re: Please convert all scripts to not use bash has caused the Debian Bug report #762918, regarding Please convert all scripts to not use bash to be marked as done. This means

Bug#919971: marked as done (node-rollup-pluginutils: autopkgtestsuite failure)

Your message dated Sun, 27 Jan 2019 22:53:50 + with message-id and subject line Bug#919971: fixed in node-rollup-pluginutils 2.3.3-4 has caused the Debian Bug report #919971, regarding node-rollup-pluginutils: autopkgtestsuite failure to be marked as done. This means that you claim that the

Bug#835377: marked as done (godoc requires explicit GOROOT)

Your message dated Sun, 27 Jan 2019 22:06:27 + with message-id <4f86cdb9-76f7-202d-e2ea-45027a110...@debian.org> and subject line Closing bug after 2 years has caused the Debian Bug report #835377, regarding godoc requires explicit GOROOT to be marked as done. This means that you claim that

Bug#228112: marked as done (indent: Adjustment of '*' in function declaration)

Your message dated Sun, 27 Jan 2019 22:04:21 + with message-id and subject line Bug#228112: fixed in indent 2.2.12-1 has caused the Debian Bug report #228112, regarding indent: Adjustment of '*' in function declaration to be marked as done. This means that you claim that the problem has been

Bug#507173: marked as done (indent: adds extra const keywords to C++ programs)

Your message dated Sun, 27 Jan 2019 22:04:21 + with message-id and subject line Bug#349065: fixed in indent 2.2.12-1 has caused the Debian Bug report #349065, regarding indent: adds extra const keywords to C++ programs to be marked as done. This means that you claim that the problem has been

Bug#349065: marked as done ([Bug+Patch] double const after C++ Function declaration)

Your message dated Sun, 27 Jan 2019 22:04:21 + with message-id and subject line Bug#349065: fixed in indent 2.2.12-1 has caused the Debian Bug report #349065, regarding [Bug+Patch] double const after C++ Function declaration to be marked as done. This means that you claim that the problem

Bug#657461: marked as done (add --fix-nested-comments option)

Your message dated Sun, 27 Jan 2019 22:04:21 + with message-id and subject line Bug#657461: fixed in indent 2.2.12-1 has caused the Debian Bug report #657461, regarding add --fix-nested-comments option to be marked as done. This means that you claim that the problem has been dealt with. If

Bug#726105: marked as done (indent: Incorrectly changes `!!` to `! !` when run with `-linux`)

Your message dated Sun, 27 Jan 2019 22:04:21 + with message-id and subject line Bug#726105: fixed in indent 2.2.12-1 has caused the Debian Bug report #726105, regarding indent: Incorrectly changes `!!` to `! !` when run with `-linux` to be marked as done. This means that you claim that the

Bug#865677: marked as done (indent FTCBFS: compiles build tool texinfo2man with the host architecture compiler)

Your message dated Sun, 27 Jan 2019 22:04:21 + with message-id and subject line Bug#865677: fixed in indent 2.2.12-1 has caused the Debian Bug report #865677, regarding indent FTCBFS: compiles build tool texinfo2man with the host architecture compiler to be marked as done. This means that

Bug#916199: marked as done (indent: Please package indent 2.2.12)

Your message dated Sun, 27 Jan 2019 22:04:21 + with message-id and subject line Bug#916199: fixed in indent 2.2.12-1 has caused the Debian Bug report #916199, regarding indent: Please package indent 2.2.12 to be marked as done. This means that you claim that the problem has been dealt with.

Bug#487517: marked as done (indent: [rfe] better support for gettext macros)

Your message dated Sun, 27 Jan 2019 22:04:21 + with message-id and subject line Bug#487517: fixed in indent 2.2.12-1 has caused the Debian Bug report #487517, regarding indent: [rfe] better support for gettext macros to be marked as done. This means that you claim that the problem has been

Bug#920606: marked as done (transifex-client: Depends: python3-six (= 1.11.0) but 1.12.0-1 is to be installed)

Your message dated Sun, 27 Jan 2019 21:35:18 + with message-id and subject line Bug#920606: fixed in transifex-client 0.13.5-2 has caused the Debian Bug report #920606, regarding transifex-client: Depends: python3-six (= 1.11.0) but 1.12.0-1 is to be installed to be marked as done. This

Bug#759173: marked as done (ocamlgraph: [INTL:pt] Updated Portuguese translation of manpage)

Your message dated Sun, 27 Jan 2019 21:20:13 + with message-id and subject line Bug#759173: fixed in ocamlgraph 1.8.8-1.1 has caused the Debian Bug report #759173, regarding ocamlgraph: [INTL:pt] Updated Portuguese translation of manpage to be marked as done. This means that you claim that

Bug#866145: marked as done (ocamlgraph: [INTL:de] Initial German po4a translation)

Your message dated Sun, 27 Jan 2019 21:20:13 + with message-id and subject line Bug#866145: fixed in ocamlgraph 1.8.8-1.1 has caused the Debian Bug report #866145, regarding ocamlgraph: [INTL:de] Initial German po4a translation to be marked as done. This means that you claim that the problem

Bug#492932: marked as done (Clarify contents in description)

Your message dated Sun, 27 Jan 2019 21:19:09 + with message-id and subject line Bug#492932: fixed in context-nonfree 2007.03.22-1.1 has caused the Debian Bug report #492932, regarding Clarify contents in description to be marked as done. This means that you claim that the problem has been

Bug#778384: marked as done (fookebox: [INTL:it] Italian translation of debconf messages)

Your message dated Sun, 27 Jan 2019 21:04:08 + with message-id and subject line Bug#778384: fixed in fookebox 0.7.2-3 has caused the Debian Bug report #778384, regarding fookebox: [INTL:it] Italian translation of debconf messages to be marked as done. This means that you claim that the

Bug#866436: marked as done (keysync: depends on obsolete python-imaging (replace with python3-pil or python-pil))

Your message dated Sun, 27 Jan 2019 20:43:32 + with message-id and subject line Bug#866436: fixed in keysync 0.2.2-2 has caused the Debian Bug report #866436, regarding keysync: depends on obsolete python-imaging (replace with python3-pil or python-pil) to be marked as done. This means that

Bug#820370: marked as done (keysync: Section should not be “python”)

Your message dated Sun, 27 Jan 2019 20:43:32 + with message-id and subject line Bug#820370: fixed in keysync 0.2.2-2 has caused the Debian Bug report #820370, regarding keysync: Section should not be “python” to be marked as done. This means that you claim that the problem has been dealt

Processed (with 2 errors): Second attempt to merge bugs

Processing commands for cont...@bugs.debian.org: > unblock 807848 by 818115 Failed to set blocking bugs of 807848: Not altering archived bugs; see unarchive. > close 818115 Bug #818115 [src:sphinx] turn python-sphinx into an arch:any package Marked Bug as done > merge 818115 915856 Bug #818115

Processed: closing 919324

Processing commands for cont...@bugs.debian.org: > close 919324 1.2.0.9000-1 Bug #919324 [r-cran-readxl] CVE-2018-20450 CVE-2018-20452 Marked as fixed in versions r-cran-readxl/1.2.0.9000-1. Bug #919324 [r-cran-readxl] CVE-2018-20450 CVE-2018-20452 Marked Bug as done > thanks Stopping processing

Processed (with 1 error): Re: Bug#915856: sphinx: Failed cross building with Build-Depends on python3-sphinx

Processing control commands: > reassign 818115 src:sphinx 1.4.9-2 Bug #818115 [python-sphinx] turn python-sphinx into an arch:any package Bug reassigned from package 'python-sphinx' to 'src:sphinx'. No longer marked as found in versions sphinx/1.3.6-2. Ignoring request to alter fixed versions of

Bug#752938: marked as done (swig2.0: drop the unused default-jdk build dependency)

Your message dated Sun, 27 Jan 2019 19:51:14 + with message-id and subject line Bug#752938: fixed in swig 3.0.12-2 has caused the Debian Bug report #752938, regarding swig2.0: drop the unused default-jdk build dependency to be marked as done. This means that you claim that the problem has

Bug#795694: marked as done (git-dpm: Lots of warnings about GREP_OPTIONS)

Your message dated Sun, 27 Jan 2019 19:49:28 + with message-id and subject line Bug#795694: fixed in git-dpm 0.9.2-1 has caused the Debian Bug report #795694, regarding git-dpm: Lots of warnings about GREP_OPTIONS to be marked as done. This means that you claim that the problem has been

Bug#920548: marked as done (golang-1.12: CVE-2019-6486)

Your message dated Sun, 27 Jan 2019 19:50:07 + with message-id and subject line Bug#920548: fixed in golang-1.12 1.12~beta2-2 has caused the Debian Bug report #920548, regarding golang-1.12: CVE-2019-6486 to be marked as done. This means that you claim that the problem has been dealt with.

Bug#920636: marked as done (dialogues illegible on HIDPI display)

Your message dated Sun, 27 Jan 2019 19:11:29 + with message-id <20190127191128.ga9...@laptop-t.office.oeko.net> and subject line Re: Bug#920636: Acknowledgement (dialogues illegible on HIDPI display) has caused the Debian Bug report #920636, regarding dialogues illegible on HIDPI display to

Bug#920409: marked as done (splitpatch: please make the build reproducible)

Your message dated Sun, 27 Jan 2019 19:19:41 + with message-id and subject line Bug#920409: fixed in splitpatch 1.0+20170926+git322ebca-2 has caused the Debian Bug report #920409, regarding splitpatch: please make the build reproducible to be marked as done. This means that you claim that

Bug#911867: marked as done (RFS: frr/6.0.2-1 [ITP])

Your message dated Sun, 27 Jan 2019 20:04:18 +0100 with message-id <20190127190418.gl881...@eidolon.nox.tf> and subject line close / upload sponsored has caused the Debian Bug report #911867, regarding RFS: frr/6.0.2-1 [ITP] to be marked as done. This means that you claim that the problem has

Bug#891722: marked as done (sqwebmail-de FTBFS: applying patches fails)

Your message dated Sun, 27 Jan 2019 18:51:15 + with message-id and subject line Bug#891722: fixed in sqwebmail-de 6.0.0-1 has caused the Debian Bug report #891722, regarding sqwebmail-de FTBFS: applying patches fails to be marked as done. This means that you claim that the problem has been

Bug#920400: marked as done (linssid FTCBFS: upstream linssid-app.pro hard codes build architecture compiler)

Your message dated Sun, 27 Jan 2019 18:05:36 + with message-id and subject line Bug#920400: fixed in linssid 3.6-3 has caused the Debian Bug report #920400, regarding linssid FTCBFS: upstream linssid-app.pro hard codes build architecture compiler to be marked as done. This means that you

Bug#920244: marked as done (cdimage.debian.org: Please add LXQt and Standard builds for live Buster images)

Your message dated Sun, 27 Jan 2019 18:05:26 + with message-id <20190127180514.7j5f7yhudp4pn...@tack.einval.com> and subject line Re: Bug#920244: cdimage.debian.org: Please add LXQt and Standard builds for live Buster images has caused the Debian Bug report #920244, regarding

Bug#920512: marked as done (syslog-ng: FTBFS with dpkg-buildpackage -A)

Your message dated Sun, 27 Jan 2019 18:06:21 + with message-id and subject line Bug#920512: fixed in syslog-ng 3.19.1-2 has caused the Debian Bug report #920512, regarding syslog-ng: FTBFS with dpkg-buildpackage -A to be marked as done. This means that you claim that the problem has been

Bug#919775: marked as done (apparmor: AppArmor denies new mesa-related paths)

Your message dated Sun, 27 Jan 2019 18:04:28 + with message-id and subject line Bug#919775: fixed in apparmor 2.13.2-4 has caused the Debian Bug report #919775, regarding apparmor: AppArmor denies new mesa-related paths to be marked as done. This means that you claim that the problem has

Bug#919705: marked as done (move libapparmor.so to /lib/)

Your message dated Sun, 27 Jan 2019 18:04:28 + with message-id and subject line Bug#919705: fixed in apparmor 2.13.2-4 has caused the Debian Bug report #919705, regarding move libapparmor.so to /lib/ to be marked as done. This means that you claim that the problem has been dealt with. If

Bug#920026: marked as done (python-greenlet-dev: ships header in /usr/include/python3.7/)

Your message dated Sun, 27 Jan 2019 17:17:32 + with message-id and subject line Bug#920026: fixed in python-greenlet 0.4.15-2 has caused the Debian Bug report #920026, regarding python-greenlet-dev: ships header in /usr/include/python3.7/ to be marked as done. This means that you claim that

Bug#908890: marked as done (developers-reference: As alioth is gone, replace references to Salsa)

Your message dated Sun, 27 Jan 2019 16:51:48 + with message-id and subject line Bug#908890: fixed in developers-reference 3.4.22 has caused the Debian Bug report #908890, regarding developers-reference: As alioth is gone, replace references to Salsa to be marked as done. This means that you

Bug#907915: marked as done (developers-reference: language in manual)

Your message dated Sun, 27 Jan 2019 16:51:48 + with message-id and subject line Bug#907915: fixed in developers-reference 3.4.22 has caused the Debian Bug report #907915, regarding developers-reference: language in manual to be marked as done. This means that you claim that the problem has

Bug#818850: marked as done (developers-reference: two chapters regarding the 'default' field)

Your message dated Sun, 27 Jan 2019 16:51:48 + with message-id and subject line Bug#818850: fixed in developers-reference 3.4.22 has caused the Debian Bug report #818850, regarding developers-reference: two chapters regarding the 'default' field to be marked as done. This means that you

Bug#908291: marked as done (developers-reference, section 5.11.4: Add a note on versioning scheme when reverting an NMU)

Your message dated Sun, 27 Jan 2019 16:51:48 + with message-id and subject line Bug#908291: fixed in developers-reference 3.4.22 has caused the Debian Bug report #908291, regarding developers-reference, section 5.11.4: Add a note on versioning scheme when reverting an NMU to be marked as

Bug#690750: marked as done (developers-reference: no link to English manual)

Your message dated Sun, 27 Jan 2019 16:51:48 + with message-id and subject line Bug#690750: fixed in developers-reference 3.4.22 has caused the Debian Bug report #690750, regarding developers-reference: no link to English manual to be marked as done. This means that you claim that the

Bug#915310: marked as done (developer-reference: broken link to anonscm.debian.org)

Your message dated Sun, 27 Jan 2019 16:51:49 + with message-id and subject line Bug#915310: fixed in developers-reference 3.4.22 has caused the Debian Bug report #915310, regarding developer-reference: broken link to anonscm.debian.org to be marked as done. This means that you claim that the

Bug#907665: marked as done (developers-reference: Section 6.7.9 about dbg packages outdated)

Your message dated Sun, 27 Jan 2019 16:51:48 + with message-id and subject line Bug#907665: fixed in developers-reference 3.4.22 has caused the Debian Bug report #907665, regarding developers-reference: Section 6.7.9 about dbg packages outdated to be marked as done. This means that you claim

Bug#905930: marked as done (www.debian.org: Duplication of text in webpage https://www.debian.org/doc/manuals/developers-reference/ch04.en.html 4.6.5 "Debian 10, will be called buster and Debian 10 wi

Your message dated Sun, 27 Jan 2019 16:51:48 + with message-id and subject line Bug#905930: fixed in developers-reference 3.4.22 has caused the Debian Bug report #905930, regarding www.debian.org: Duplication of text in webpage

Bug#912724: marked as done (www.debian.org: wrong links to translations of "Debian Developer's Reference")

Your message dated Sun, 27 Jan 2019 16:51:49 + with message-id and subject line Bug#912724: fixed in developers-reference 3.4.22 has caused the Debian Bug report #912724, regarding www.debian.org: wrong links to translations of "Debian Developer's Reference" to be marked as done. This means

Bug#841289: marked as done ([drm/i915] GPU HANG: ecode 9:0:0xfffffffe, in Xorg [2507], reason: Engine(s) hung, action: reset)

Your message dated Sun, 27 Jan 2019 17:21:24 +0100 with message-id and subject line Re: Bug#841289: [drm/i915] GPU HANG: ecode 9:0:0xfffe, in Xorg [2507], reason: Engine(s) hung, action: reset has caused the Debian Bug report #841289, regarding [drm/i915] GPU HANG: ecode 9:0:0xfffe, in

Bug#912587: marked as done (firejail AppArmor profile blocks Chromium's usage of ptrace => large amounts of denial logged)

Your message dated Sun, 27 Jan 2019 16:40:23 + with message-id and subject line Bug#912587: fixed in firejail 0.9.58-1 has caused the Debian Bug report #912587, regarding firejail AppArmor profile blocks Chromium's usage of ptrace => large amounts of denial logged to be marked as done. This

Bug#916920: marked as done (firejail: Firejail allows regular users to bypass root system settings)

Your message dated Sun, 27 Jan 2019 16:40:23 + with message-id and subject line Bug#916920: fixed in firejail 0.9.58-1 has caused the Debian Bug report #916920, regarding firejail: Firejail allows regular users to bypass root system settings to be marked as done. This means that you claim

Bug#920617: marked as done (gnome-settings-daemon: Please upgrade gnome-settings-daemon-common too.)

Your message dated Sun, 27 Jan 2019 11:07:41 -0500 with message-id and subject line Re: Bug#920617: gnome-settings-daemon: Please upgrade gnome-settings-daemon-common too. has caused the Debian Bug report #920617, regarding gnome-settings-daemon: Please upgrade gnome-settings-daemon-common

Bug#919736: marked as done (tj3: FTBFS (failing tests))

Your message dated Sun, 27 Jan 2019 16:08:14 + with message-id and subject line Bug#919736: fixed in tj3 3.6.0-6 has caused the Debian Bug report #919736, regarding tj3: FTBFS (failing tests) to be marked as done. This means that you claim that the problem has been dealt with. If this is not

Bug#875954: marked as done (courier-mta: /usr/sbin/sendmail has wrong permissions)

Your message dated Sun, 27 Jan 2019 16:40:09 +0100 with message-id and subject line Re: courier-mta: /usr/sbin/sendmail has wrong permissions has caused the Debian Bug report #875954, regarding courier-mta: /usr/sbin/sendmail has wrong permissions to be marked as done. This means that you claim

Processed: is in NEW

Processing commands for cont...@bugs.debian.org: > close 917561 Bug #917561 [sponsorship-requests] RFS: opencpn/4.8.8+dfsg.1-1 [ITP] -- Chartplotter and Marine Navigation software Marked Bug as done > End of message, stopping processing here. Please contact me if you need assistance. --

Bug#867681: marked as done (software-properties-gtk: trusted.gpg file created by this package produces gpg error for 'apt-get update')

Your message dated Sun, 27 Jan 2019 15:35:35 + with message-id and subject line Bug#867681: fixed in software-properties 0.96.24.32.7-1 has caused the Debian Bug report #867681, regarding software-properties-gtk: trusted.gpg file created by this package produces gpg error for 'apt-get

Bug#898881: marked as done (conntrack-tools FTCBFS: does not pass --host to ./configure)

Your message dated Sun, 27 Jan 2019 15:34:11 + with message-id and subject line Bug#898881: fixed in conntrack-tools 1:1.4.5-2 has caused the Debian Bug report #898881, regarding conntrack-tools FTCBFS: does not pass --host to ./configure to be marked as done. This means that you claim that

Bug#916138: marked as done (conntrackd: State Accept/Ignore isn't working, always get symbol '}': syntax error. Even "SYNC EXAMPLE 2" from manpage fails.)

Your message dated Sun, 27 Jan 2019 15:34:11 + with message-id and subject line Bug#916138: fixed in conntrack-tools 1:1.4.5-2 has caused the Debian Bug report #916138, regarding conntrackd: State Accept/Ignore isn't working, always get symbol '}': syntax error. Even "SYNC EXAMPLE 2" from

Bug#920558: marked as done (RFS: liboauth/1.0.3-2 [QA])

Your message dated Sun, 27 Jan 2019 15:28:58 + with message-id <20190127152858.a7lbb2cj7iv47...@master.debian.org> and subject line removed from mentors has caused the Debian Bug report #920558, regarding RFS: liboauth/1.0.3-2 [QA] to be marked as done. This means that you claim that the

Bug#890190: marked as done ([compiz-plugins-default] Plugin "wall" doesn't honor edge-delay)

Your message dated Sun, 27 Jan 2019 15:06:19 + with message-id and subject line Bug#890190: fixed in compiz 2:0.8.16.1-6 has caused the Debian Bug report #890190, regarding [compiz-plugins-default] Plugin "wall" doesn't honor edge-delay to be marked as done. This means that you claim that

Bug#914804: marked as done (pycuda: FTBFS with boost1.67: /usr/bin/ld: cannot find -lcuda)

Your message dated Sun, 27 Jan 2019 13:52:33 + with message-id and subject line Bug#914804: fixed in pycuda 2018.1.1-3 has caused the Debian Bug report #914804, regarding pycuda: FTBFS with boost1.67: /usr/bin/ld: cannot find -lcuda to be marked as done. This means that you claim that the

Bug#920597: marked as done (docker.io: Unable to start daemon: "containerd" executable file not found in PATH)

Your message dated Sun, 27 Jan 2019 13:51:00 + with message-id and subject line Bug#920597: fixed in docker.io 18.09.1+dfsg1-3 has caused the Debian Bug report #920597, regarding docker.io: Unable to start daemon: "containerd" executable file not found in PATH to be marked as done. This

Bug#916256: marked as done (gitlab-runner fails when it tries to pull docker image gitlab-runner-helper:11.2.0)

Your message dated Sun, 27 Jan 2019 23:55:54 +1100 with message-id <4197763.WzzgV0LaB0@deblab> and subject line Re: [pkg-go] Bug#916256: Bug#916256: Bug#916256: gitlab-runner fails when it tries to pull docker image gitlab-runner-helper:11.2.0 has caused the Debian Bug report #916256, regarding

Bug#919918: marked as done (scikit-learn FTBFS on armel/armhf/arm64/ppc64el/s390x: test failures)

Your message dated Sun, 27 Jan 2019 12:50:32 + with message-id and subject line Bug#919918: fixed in scikit-learn 0.20.2+dfsg-2 has caused the Debian Bug report #919918, regarding scikit-learn FTBFS on armel/armhf/arm64/ppc64el/s390x: test failures to be marked as done. This means that you

Processed: Re: stretch-backports: needs newer python3-urllib3

Processing commands for cont...@bugs.debian.org: > close 920160 Bug #920160 [netdata] stretch-backports: needs newer python3-urllib3 Marked Bug as done > thanks Stopping processing here. Please contact me if you need assistance. -- 920160:

Bug#919535: marked as done (surf: AppArmor profile forbids access to publicsuffix data)

Your message dated Sun, 27 Jan 2019 12:21:46 + with message-id and subject line Bug#919535: fixed in surf 2.0+git20181009-4 has caused the Debian Bug report #919535, regarding surf: AppArmor profile forbids access to publicsuffix data to be marked as done. This means that you claim that the

  1   2   >