Bug#919419: marked as done (yatex: hangs while installing along xemacs21)

2019-02-23 Thread Debian Bug Tracking System
Your message dated Sun, 24 Feb 2019 07:35:13 + with message-id and subject line Bug#919419: fixed in yatex 1.81-2 has caused the Debian Bug report #919419, regarding yatex: hangs while installing along xemacs21 to be marked as done. This means that you claim that the problem has been dealt wi

Bug#917685: marked as done (ruby-rack: FTBFS: ERROR: Test "ruby2.5" failed.)

2019-02-23 Thread Debian Bug Tracking System
Your message dated Sun, 24 Feb 2019 15:45:50 +0900 with message-id <8736odr8f5.wl-uwab...@gfd-dennou.org> and subject line has caused the Debian Bug report #917685, regarding ruby-rack: FTBFS: ERROR: Test "ruby2.5" failed. to be marked as done. This means that you claim that the problem has been

Bug#875135: marked as done ([qgis] Future Qt4 removal from Buster)

2019-02-23 Thread Debian Bug Tracking System
Your message dated Sun, 24 Feb 2019 07:21:46 +0100 with message-id <84ff6a78-78d9-eea0-12cd-78391a454...@xs4all.nl> and subject line Re: Bug#875135: qgis: Qt5 version available has caused the Debian Bug report #875135, regarding [qgis] Future Qt4 removal from Buster to be marked as done. This mean

Bug#902482: marked as done (rifiuti FTCBFS: uses the build architecture compiler)

2019-02-23 Thread Debian Bug Tracking System
Your message dated Sun, 24 Feb 2019 02:40:57 + with message-id and subject line Bug#902482: fixed in rifiuti 20040505-3 has caused the Debian Bug report #902482, regarding rifiuti FTCBFS: uses the build architecture compiler to be marked as done. This means that you claim that the problem has

Processed: control

2019-02-23 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > close 919550 Bug #919550 [wnpp] O: farmhash -- FarmHash, a family of hash functions Marked Bug as done > close 919551 Bug #919551 [wnpp] O: gemmlowp -- small self-contained low-precision GEMM library Marked Bug as done > close 919553 Bug #919553

Bug#670805: marked as done (dpkg: patch apply problem: line after --- isn't as expected in diff)

2019-02-23 Thread Debian Bug Tracking System
Your message dated Sun, 24 Feb 2019 02:28:39 +0100 with message-id <20190224012839.ga8...@gaara.hadrons.org> and subject line Re: Bug#485330: Non-unified patches and dpkg source format ‘3.0 (quilt)’. has caused the Debian Bug report #485330, regarding dpkg: patch apply problem: line after --- isn'

Bug#485330: marked as done (Allow context diff in debian/patches/ in 3.0 (quilt) format)

2019-02-23 Thread Debian Bug Tracking System
Your message dated Sun, 24 Feb 2019 02:28:39 +0100 with message-id <20190224012839.ga8...@gaara.hadrons.org> and subject line Re: Bug#485330: Non-unified patches and dpkg source format ‘3.0 (quilt)’. has caused the Debian Bug report #485330, regarding Allow context diff in debian/patches/ in 3.0 (

Bug#360643: marked as done (Support build configuration flags (a la FreeBSD/Gentoo))

2019-02-23 Thread Debian Bug Tracking System
Your message dated Sun, 24 Feb 2019 02:15:27 +0100 with message-id <20190224011527.ga8...@gaara.hadrons.org> and subject line Re: Bug#360643: APT configure flags has caused the Debian Bug report #360643, regarding Support build configuration flags (a la FreeBSD/Gentoo) to be marked as done. This m

Bug#241768: marked as done (dpkg: low mem systems - do not load available packages into memory)

2019-02-23 Thread Debian Bug Tracking System
Your message dated Sun, 24 Feb 2019 02:11:44 +0100 with message-id <20190224011144.ga8...@gaara.hadrons.org> and subject line Re: Bug#241768: dpkg: low mem systems - do not load available packages into memory has caused the Debian Bug report #241768, regarding dpkg: low mem systems - do not load a

Bug#916367: marked as done (braa FTCBFS: hard codes the build architecture compiler)

2019-02-23 Thread Debian Bug Tracking System
Your message dated Sun, 24 Feb 2019 01:03:57 + with message-id and subject line Bug#916367: fixed in braa 0.82-4 has caused the Debian Bug report #916367, regarding braa FTCBFS: hard codes the build architecture compiler to be marked as done. This means that you claim that the problem has bee

Bug#898263: marked as done (braa: version mismatch in -h output)

2019-02-23 Thread Debian Bug Tracking System
Your message dated Sun, 24 Feb 2019 01:03:57 + with message-id and subject line Bug#898263: fixed in braa 0.82-4 has caused the Debian Bug report #898263, regarding braa: version mismatch in -h output to be marked as done. This means that you claim that the problem has been dealt with. If thi

Bug#487108: marked as done (dpkg-divert: does not support --root)

2019-02-23 Thread Debian Bug Tracking System
Your message dated Sun, 24 Feb 2019 01:59:08 +0100 with message-id <20190224005908.ga8...@gaara.hadrons.org> and subject line Re: Bug#487108: /usr/sbin/dpkg-divert: Does not support --root has caused the Debian Bug report #487108, regarding dpkg-divert: does not support --root to be marked as done.

Bug#853795: marked as done (dpkg: Unable to disable .buildinfo generation)

2019-02-23 Thread Debian Bug Tracking System
Your message dated Sun, 24 Feb 2019 01:56:02 +0100 with message-id <20190224005602.ga8...@gaara.hadrons.org> and subject line Re: Bug#853795: dpkg: Unable to disable .buildinfo generation has caused the Debian Bug report #853795, regarding dpkg: Unable to disable .buildinfo generation to be marked

Bug#880086: marked as done (snoopy: root parent name is extracted incorrectly, causing test suite fails (FTBFS) when building from tmux)

2019-02-23 Thread Debian Bug Tracking System
Your message dated Sun, 24 Feb 2019 00:49:10 + with message-id and subject line Bug#880086: fixed in snoopy 2.4.6-5 has caused the Debian Bug report #880086, regarding snoopy: root parent name is extracted incorrectly, causing test suite fails (FTBFS) when building from tmux to be marked as d

Bug#921637: marked as done (ronn 0.8.0-1 breaks man pages with numbered lists)

2019-02-23 Thread Debian Bug Tracking System
Your message dated Sun, 24 Feb 2019 00:34:14 + with message-id and subject line Bug#921637: fixed in ruby-ronn 0.8.0-2 has caused the Debian Bug report #921637, regarding ronn 0.8.0-1 breaks man pages with numbered lists to be marked as done. This means that you claim that the problem has bee

Processed: Bug#911533: gandi-cli: missing dependencies

2019-02-23 Thread Debian Bug Tracking System
Processing control commands: > clone -1 -2 Bug #911533 [gandi-cli] gandi-cli: missing dependencies for python3 setuptools and ipy Bug 911533 cloned as bug 923084 > retitle -1 gandi-cli: Python dependencies not declared Bug #911533 [gandi-cli] gandi-cli: missing dependencies for python3 setuptools

Processed: Bug#911533: gandi-cli: missing dependencies

2019-02-23 Thread Debian Bug Tracking System
Processing control commands: > clone -1 -2 Bug #911533 {Done: Ben Finney } [gandi-cli] gandi-cli: Python dependencies not declared Bug 911533 cloned as bug 923085 > retitle -1 gandi-cli: Python dependencies not declared Bug #911533 {Done: Ben Finney } [gandi-cli] gandi-cli: Python dependencies n

Bug#859784: marked as done (validns: Please migrate to openssl1.1 in Buster)

2019-02-23 Thread Debian Bug Tracking System
Your message dated Sat, 23 Feb 2019 23:49:18 + with message-id and subject line Bug#859784: fixed in validns 0.8+git20160720-3.1 has caused the Debian Bug report #859784, regarding validns: Please migrate to openssl1.1 in Buster to be marked as done. This means that you claim that the problem

Bug#897882: marked as done (validns: ftbfs with GCC-8)

2019-02-23 Thread Debian Bug Tracking System
Your message dated Sat, 23 Feb 2019 23:49:18 + with message-id and subject line Bug#897882: fixed in validns 0.8+git20160720-3.1 has caused the Debian Bug report #897882, regarding validns: ftbfs with GCC-8 to be marked as done. This means that you claim that the problem has been dealt with.

Bug#912183: marked as done (python-cookies FTBFS with python 3.7 as supported version)

2019-02-23 Thread Debian Bug Tracking System
Your message dated Sat, 23 Feb 2019 23:35:15 + with message-id and subject line Bug#912183: fixed in python-cookies 2.2.1-2 has caused the Debian Bug report #912183, regarding python-cookies FTBFS with python 3.7 as supported version to be marked as done. This means that you claim that the pr

Processed: RFS: pymacs/0.25-2 [ITA]

2019-02-23 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > close 923019 Bug #923019 {Done: Bart Martens } [sponsorship-requests] RFS: pymacs/0.25-2 [ITA] Bug 923019 is already marked as done; not doing anything. > stop Stopping processing here. Please contact me if you need assistance. -- 923019: https

Processed: RFS: pymacs/0.25-2 [ITA]

2019-02-23 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > close 923019 Bug #923019 [sponsorship-requests] RFS: pymacs/0.25-2 [ITA] Marked Bug as done > stop Stopping processing here. Please contact me if you need assistance. -- 923019: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=923019 Debian Bug

Bug#922805: marked as done (strophejs: FTBFS (ERROR: module path does not exist: /usr/lib/nodejs/node-almond/almond.js))

2019-02-23 Thread Debian Bug Tracking System
Your message dated Sat, 23 Feb 2019 22:35:16 + with message-id and subject line Bug#922805: fixed in strophejs 1.2.14+dfsg-4 has caused the Debian Bug report #922805, regarding strophejs: FTBFS (ERROR: module path does not exist: /usr/lib/nodejs/node-almond/almond.js) to be marked as done. T

Bug#923079: marked as done (tcl8.6-dev: tcl.pc pkgconfig file not packaged)

2019-02-23 Thread Debian Bug Tracking System
Your message dated Sat, 23 Feb 2019 22:35:51 + with message-id and subject line Bug#923079: fixed in tcl8.6 8.6.9+dfsg-2 has caused the Debian Bug report #923079, regarding tcl8.6-dev: tcl.pc pkgconfig file not packaged to be marked as done. This means that you claim that the problem has been

Bug#919516: marked as done (ruby2.5 ftbfs in testing/unstable: certificate verify failed (certificate has expired))

2019-02-23 Thread Debian Bug Tracking System
Your message dated Sat, 23 Feb 2019 21:34:57 + with message-id and subject line Bug#919516: fixed in ruby2.5 2.5.3-4 has caused the Debian Bug report #919516, regarding ruby2.5 ftbfs in testing/unstable: certificate verify failed (certificate has expired) to be marked as done. This means tha

Bug#923008: marked as done (CVE-2018-16886)

2019-02-23 Thread Debian Bug Tracking System
Your message dated Sat, 23 Feb 2019 21:34:12 + with message-id and subject line Bug#923008: fixed in etcd 3.2.26+dfsg-1 has caused the Debian Bug report #923008, regarding CVE-2018-16886 to be marked as done. This means that you claim that the problem has been dealt with. If this is not the c

Bug#922636: marked as done (dpkg-genchanges: Please do not exclude packages from the Binary field)

2019-02-23 Thread Debian Bug Tracking System
Your message dated Sat, 23 Feb 2019 22:34:27 +0100 with message-id <20190223213426.ga21...@gaara.hadrons.org> and subject line Re: Bug#922636: dpkg-genchanges: Please do not exclude packages from the Binary field has caused the Debian Bug report #922636, regarding dpkg-genchanges: Please do not ex

Bug#922261: marked as done (python-sunlight: FTBFS (Could not import extension sphinx.ext.pngmath))

2019-02-23 Thread Debian Bug Tracking System
Your message dated Sat, 23 Feb 2019 20:57:30 + with message-id and subject line Bug#922261: fixed in python-sunlight 1.1.5-2 has caused the Debian Bug report #922261, regarding python-sunlight: FTBFS (Could not import extension sphinx.ext.pngmath) to be marked as done. This means that you cla

Bug#907537: marked as done (mblaze: please make the build reproducible)

2019-02-23 Thread Debian Bug Tracking System
Your message dated Sat, 23 Feb 2019 20:50:45 + with message-id and subject line Bug#907537: fixed in mblaze 0.5-1 has caused the Debian Bug report #907537, regarding mblaze: please make the build reproducible to be marked as done. This means that you claim that the problem has been dealt with

Bug#921891: marked as done (mblaze: new upstream version available)

2019-02-23 Thread Debian Bug Tracking System
Your message dated Sat, 23 Feb 2019 20:50:45 + with message-id and subject line Bug#921891: fixed in mblaze 0.5-1 has caused the Debian Bug report #921891, regarding mblaze: new upstream version available to be marked as done. This means that you claim that the problem has been dealt with. If

Bug#887988: marked as done (mblaze: File conflict at /usr/bin/msort, /usr/bin/mprev)

2019-02-23 Thread Debian Bug Tracking System
Your message dated Sat, 23 Feb 2019 20:50:45 + with message-id and subject line Bug#887988: fixed in mblaze 0.5-1 has caused the Debian Bug report #887988, regarding mblaze: File conflict at /usr/bin/msort, /usr/bin/mprev to be marked as done. This means that you claim that the problem has be

Bug#915208: marked as done (easybind FTBFS: error: package javafx.beans does not exist)

2019-02-23 Thread Debian Bug Tracking System
Your message dated Sat, 23 Feb 2019 20:43:41 + with message-id and subject line Bug#915208: fixed in easybind 1.0.3-2 has caused the Debian Bug report #915208, regarding easybind FTBFS: error: package javafx.beans does not exist to be marked as done. This means that you claim that the problem

Bug#709478: marked as done (Merge init skeleton with dh-make)

2019-02-23 Thread Debian Bug Tracking System
Your message dated Sat, 23 Feb 2019 20:07:46 + with message-id and subject line Re: Related bugs has caused the Debian Bug report #709478, regarding Merge init skeleton with dh-make to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case i

Bug#718347: marked as done (bootlogd keeps on running after boot)

2019-02-23 Thread Debian Bug Tracking System
Your message dated Sat, 23 Feb 2019 20:07:44 + with message-id and subject line Re: bootlogd keeps on running after boot has caused the Debian Bug report #718347, regarding bootlogd keeps on running after boot to be marked as done. This means that you claim that the problem has been dealt wit

Bug#570756: marked as done (repeated "insserv: warning: current stop runlevel(s) ...")

2019-02-23 Thread Debian Bug Tracking System
Your message dated Sat, 23 Feb 2019 20:07:40 + with message-id and subject line Re: [Pkg-sysvinit-devel] Bug#570756: repeated "insserv: warning: current stop runlevel(s) ..." has caused the Debian Bug report #570756, regarding repeated "insserv: warning: current stop runlevel(s) ..." to be ma

Bug#920027: marked as done (python3-persistent: ships headers in /usr/include/python3.7/)

2019-02-23 Thread Debian Bug Tracking System
Your message dated Sat, 23 Feb 2019 18:35:36 + with message-id and subject line Bug#920027: fixed in python-persistent 4.2.2-2 has caused the Debian Bug report #920027, regarding python3-persistent: ships headers in /usr/include/python3.7/ to be marked as done. This means that you claim that

Bug#898204: marked as done (hwinfo: suggesting minor packaging improvements)

2019-02-23 Thread Debian Bug Tracking System
Your message dated Sat, 23 Feb 2019 18:34:59 + with message-id and subject line Bug#898204: fixed in hwinfo 21.63-3 has caused the Debian Bug report #898204, regarding hwinfo: suggesting minor packaging improvements to be marked as done. This means that you claim that the problem has been dea

Bug#922799: marked as done ([dpkg-maintscript-helper] bug in finish_dir_to_symlink)

2019-02-23 Thread Debian Bug Tracking System
Your message dated Sat, 23 Feb 2019 17:49:14 + with message-id and subject line Bug#922799: fixed in dpkg 1.19.5 has caused the Debian Bug report #922799, regarding [dpkg-maintscript-helper] bug in finish_dir_to_symlink to be marked as done. This means that you claim that the problem has been

Bug#922407: marked as done ([PATCH] man page elucidation plus missing unknown state)

2019-02-23 Thread Debian Bug Tracking System
Your message dated Sat, 23 Feb 2019 17:49:13 + with message-id and subject line Bug#922407: fixed in dpkg 1.19.5 has caused the Debian Bug report #922407, regarding [PATCH] man page elucidation plus missing unknown state to be marked as done. This means that you claim that the problem has bee

Bug#922410: marked as done (Forgot to --forget-old-unavail on state "unknown")

2019-02-23 Thread Debian Bug Tracking System
Your message dated Sat, 23 Feb 2019 17:49:14 + with message-id and subject line Bug#922410: fixed in dpkg 1.19.5 has caused the Debian Bug report #922410, regarding Forgot to --forget-old-unavail on state "unknown" to be marked as done. This means that you claim that the problem has been deal

Bug#922039: marked as done (dpkg-buildpackage: error: short OpenPGP key IDs are broken; please use key fingerprints instead)

2019-02-23 Thread Debian Bug Tracking System
Your message dated Sat, 23 Feb 2019 17:49:13 + with message-id and subject line Bug#922039: fixed in dpkg 1.19.5 has caused the Debian Bug report #922039, regarding dpkg-buildpackage: error: short OpenPGP key IDs are broken; please use key fingerprints instead to be marked as done. This mean

Bug#922043: marked as done (dpkg-buildpackage: error: short OpenPGP key IDs are broken; please use key fingerprints instead)

2019-02-23 Thread Debian Bug Tracking System
Your message dated Sat, 23 Feb 2019 17:49:13 + with message-id and subject line Bug#922039: fixed in dpkg 1.19.5 has caused the Debian Bug report #922039, regarding dpkg-buildpackage: error: short OpenPGP key IDs are broken; please use key fingerprints instead to be marked as done. This mean

Bug#922212: marked as done (dpkg: lib/dpkg/pager.c uses memset on line 100 and doesn't include )

2019-02-23 Thread Debian Bug Tracking System
Your message dated Sat, 23 Feb 2019 17:49:13 + with message-id and subject line Bug#922212: fixed in dpkg 1.19.5 has caused the Debian Bug report #922212, regarding dpkg: lib/dpkg/pager.c uses memset on line 100 and doesn't include to be marked as done. This means that you claim that the pr

Bug#921557: marked as done (start-stop-daemon: behavior change on "matching only on non-root pidfile /run/exim4/exim.pid is insecure" not fully documented)

2019-02-23 Thread Debian Bug Tracking System
Your message dated Sat, 23 Feb 2019 17:49:13 + with message-id and subject line Bug#921557: fixed in dpkg 1.19.5 has caused the Debian Bug report #921557, regarding start-stop-daemon: behavior change on "matching only on non-root pidfile /run/exim4/exim.pid is insecure" not fully documented t

Bug#920974: marked as done (dpkg 1.19.4 FTBFS with t-file test failure)

2019-02-23 Thread Debian Bug Tracking System
Your message dated Sat, 23 Feb 2019 17:49:13 + with message-id and subject line Bug#920974: fixed in dpkg 1.19.5 has caused the Debian Bug report #920974, regarding dpkg 1.19.4 FTBFS with t-file test failure to be marked as done. This means that you claim that the problem has been dealt with.

Bug#921942: marked as done (dpkg: [INTL:nl] Dutch po file for the dpkg package)

2019-02-23 Thread Debian Bug Tracking System
Your message dated Sat, 23 Feb 2019 17:49:13 + with message-id and subject line Bug#921942: fixed in dpkg 1.19.5 has caused the Debian Bug report #921942, regarding dpkg: [INTL:nl] Dutch po file for the dpkg package to be marked as done. This means that you claim that the problem has been dea

Bug#883700: marked as done (dpkg: error: unable to access dpkg status area: No such file or directory" when changing admin dir)

2019-02-23 Thread Debian Bug Tracking System
Your message dated Sat, 23 Feb 2019 17:49:13 + with message-id and subject line Bug#883700: fixed in dpkg 1.19.5 has caused the Debian Bug report #883700, regarding dpkg: error: unable to access dpkg status area: No such file or directory" when changing admin dir to be marked as done. This m

Bug#666147: marked as done (set UCF_FORCE_CONFFMISS when force-confmiss option is set)

2019-02-23 Thread Debian Bug Tracking System
Your message dated Sat, 23 Feb 2019 17:49:13 + with message-id and subject line Bug#666147: fixed in dpkg 1.19.5 has caused the Debian Bug report #666147, regarding set UCF_FORCE_CONFFMISS when force-confmiss option is set to be marked as done. This means that you claim that the problem has b

Bug#922693: marked as done (dgit: autopkgtests regressed since the upload of dpkg 1.19.3)

2019-02-23 Thread Debian Bug Tracking System
Your message dated Sat, 23 Feb 2019 17:49:13 + with message-id and subject line Bug#921031: fixed in dpkg 1.19.5 has caused the Debian Bug report #921031, regarding dgit: autopkgtests regressed since the upload of dpkg 1.19.3 to be marked as done. This means that you claim that the problem ha

Bug#921031: marked as done (Dpkg::Source::Package missing use of ::Format)

2019-02-23 Thread Debian Bug Tracking System
Your message dated Sat, 23 Feb 2019 17:49:13 + with message-id and subject line Bug#921031: fixed in dpkg 1.19.5 has caused the Debian Bug report #921031, regarding Dpkg::Source::Package missing use of ::Format to be marked as done. This means that you claim that the problem has been dealt wi

Bug#920880: marked as done (recover from unknown user in statoverride)

2019-02-23 Thread Debian Bug Tracking System
Your message dated Sat, 23 Feb 2019 17:49:13 + with message-id and subject line Bug#920880: fixed in dpkg 1.19.5 has caused the Debian Bug report #920880, regarding recover from unknown user in statoverride to be marked as done. This means that you claim that the problem has been dealt with.

Bug#921189: marked as done (postsrsd FTBFS on 64bit big endian: AllTests (Failed))

2019-02-23 Thread Debian Bug Tracking System
Your message dated Sat, 23 Feb 2019 17:38:32 + with message-id and subject line Bug#921189: fixed in postsrsd 1.5-2 has caused the Debian Bug report #921189, regarding postsrsd FTBFS on 64bit big endian: AllTests (Failed) to be marked as done. This means that you claim that the problem has be

Bug#918122: marked as done (gsettings schema files contain translations, causes summary and description shown in Chinese)

2019-02-23 Thread Debian Bug Tracking System
Your message dated Sat, 23 Feb 2019 17:38:53 + with message-id and subject line Bug#918122: fixed in tracker-miners 2.1.6-1 has caused the Debian Bug report #918122, regarding gsettings schema files contain translations, causes summary and description shown in Chinese to be marked as done. T

Processed: fix wrong close version.

2019-02-23 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > notfixed 921745 0.11.1-2 Bug #921745 {Done: Yaroslav Halchenko } [src:datalad] src:datalad: Build-depends/Recommends uninstallable packages The source 'datalad' and version '0.11.1-2' do not appear to match any binary packages No longer marked a

Processed: Re: Invalid upstream-signing-key

2019-02-23 Thread Debian Bug Tracking System
Processing control commands: > close -1 1.6.1-1 Bug #876065 [yubico-piv-tool] Invalid upstream-signing-key Marked as fixed in versions yubico-piv-tool/1.6.1-1. Bug #876065 [yubico-piv-tool] Invalid upstream-signing-key Marked Bug as done -- 876065: https://bugs.debian.org/cgi-bin/bugreport.cgi?b

Bug#922957: marked as done (python-igraph's tests fail with Python 3.7 on Windows10 (version python-igraph/0.7.1.post6-6))

2019-02-23 Thread Debian Bug Tracking System
Your message dated Sat, 23 Feb 2019 22:08:32 +0500 with message-id <20190223170832.ga4...@belkar.wrar.name> and subject line Re: Bug#922957: python-igraph's tests fail with Python 3.7 on Windows10 (version python-igraph/0.7.1.post6-6) has caused the Debian Bug report #922957, regarding python-igra

Bug#921166: marked as done (movim: [INTL:ru] Russian translation of debconf template)

2019-02-23 Thread Debian Bug Tracking System
Your message dated Sat, 23 Feb 2019 17:22:09 +0100 with message-id <20190223162209.gb24...@portux.naturalnet.de> and subject line Fixed has caused the Debian Bug report #921166, regarding movim: [INTL:ru] Russian translation of debconf template to be marked as done. This means that you claim that

Bug#893287: marked as done (libjogl2-java FTBFS with openjdk-9)

2019-02-23 Thread Debian Bug Tracking System
Your message dated Sat, 23 Feb 2019 16:04:22 + with message-id and subject line Bug#893287: fixed in libjogl2-java 2.3.2+dfsg-8 has caused the Debian Bug report #893287, regarding libjogl2-java FTBFS with openjdk-9 to be marked as done. This means that you claim that the problem has been deal

Processed: RFS: pk2/1.2.1-1 [ITP] -- 2D Oldschool platform game where you control a rooster

2019-02-23 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > close 915074 Bug #915074 [sponsorship-requests] RFS: pk2/1.2.1-1 [ITP] -- 2D Oldschool platform game where you control a rooster Marked Bug as done > stop Stopping processing here. Please contact me if you need assistance. -- 915074: https://bu

Bug#921898: marked as done (pilkit: FTBFS (AssertionError: '.apng' != '.png'))

2019-02-23 Thread Debian Bug Tracking System
Your message dated Sat, 23 Feb 2019 15:49:56 + with message-id and subject line Bug#921898: fixed in pilkit 2.0-2 has caused the Debian Bug report #921898, regarding pilkit: FTBFS (AssertionError: '.apng' != '.png') to be marked as done. This means that you claim that the problem has been dea

Processed: dup

2019-02-23 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > block 920406 by 923019 Bug #920406 [wnpp] ITA: pymacs -- interface between Emacs Lisp and Python 920406 was blocked by: 921586 920406 was not blocking any bugs. Added blocking bug(s) of 920406: 923019 > close 921586 Bug #921586 [sponsorship-reques

Bug#921759: marked as done (sdaps: FTBFS (Error running "pdflatex" to compile the LaTeX file))

2019-02-23 Thread Debian Bug Tracking System
Your message dated Sat, 23 Feb 2019 15:34:36 + with message-id and subject line Bug#921759: fixed in sdaps 1.2.1-2 has caused the Debian Bug report #921759, regarding sdaps: FTBFS (Error running "pdflatex" to compile the LaTeX file) to be marked as done. This means that you claim that the pro

Bug#919303: marked as done (movim: [INTL:nl] Dutch translation of debconf messages)

2019-02-23 Thread Debian Bug Tracking System
Your message dated Sat, 23 Feb 2019 15:34:12 + with message-id and subject line Bug#919303: fixed in movim 0.14.1-2 has caused the Debian Bug report #919303, regarding movim: [INTL:nl] Dutch translation of debconf messages to be marked as done. This means that you claim that the problem has b

Bug#923040: marked as done (Topal's mime-tool is broken (Makefile error))

2019-02-23 Thread Debian Bug Tracking System
Your message dated Sat, 23 Feb 2019 15:34:45 + with message-id and subject line Bug#923040: fixed in topal 80-1 has caused the Debian Bug report #923040, regarding Topal's mime-tool is broken (Makefile error) to be marked as done. This means that you claim that the problem has been dealt with

Bug#922166: marked as done (linux-image-4.19.0-0.bpo.2-amd64-unsigned: [regression] Touchpad doesn't work unless set to 'Basic' from BIOS)

2019-02-23 Thread Debian Bug Tracking System
Your message dated Sat, 23 Feb 2019 15:34:12 + with message-id and subject line Bug#922166: fixed in movim 0.14.1-2 has caused the Debian Bug report #922166, regarding linux-image-4.19.0-0.bpo.2-amd64-unsigned: [regression] Touchpad doesn't work unless set to 'Basic' from BIOS to be marked as

Bug#922267: marked as done (dh_missing reports missing files, though installed)

2019-02-23 Thread Debian Bug Tracking System
Your message dated Sat, 23 Feb 2019 14:49:01 + with message-id and subject line Bug#922267: fixed in debhelper 12.1.1 has caused the Debian Bug report #922267, regarding dh_missing reports missing files, though installed to be marked as done. This means that you claim that the problem has bee

Bug#922990: marked as done (dh_installinitramfs: causes script-not-executable in lintian)

2019-02-23 Thread Debian Bug Tracking System
Your message dated Sat, 23 Feb 2019 14:49:01 + with message-id and subject line Bug#922990: fixed in debhelper 12.1.1 has caused the Debian Bug report #922990, regarding dh_installinitramfs: causes script-not-executable in lintian to be marked as done. This means that you claim that the probl

Bug#507020: marked as done (xen-utils-3.2-1: Pygrub says "Error: Boot loader didn't return any data!")

2019-02-23 Thread Debian Bug Tracking System
Your message dated Sat, 23 Feb 2019 14:18:12 +0100 with message-id <2fbea6c1-cfd3-2006-4905-85a97ad17...@vandervlis.nl> and subject line Re: xen-utils-3.2-1: Pygrub says "Error: Boot loader didn't return any data!" has caused the Debian Bug report #507020, regarding xen-utils-3.2-1: Pygrub says "E

Bug#892295: marked as done (jemalloc: Please add support for new architecture "riscv64" (RISC-V 64 bits little-endian))

2019-02-23 Thread Debian Bug Tracking System
Your message dated Sat, 23 Feb 2019 12:49:03 + with message-id and subject line Bug#892295: fixed in jemalloc 5.1.0-3 has caused the Debian Bug report #892295, regarding jemalloc: Please add support for new architecture "riscv64" (RISC-V 64 bits little-endian) to be marked as done. This mean

Bug#920030: marked as done (python3-pygame: ships headers in /usr/include/python3.7/)

2019-02-23 Thread Debian Bug Tracking System
Your message dated Sat, 23 Feb 2019 12:04:56 + with message-id and subject line Bug#920030: fixed in pygame 1.9.4.post1+dfsg-3 has caused the Debian Bug report #920030, regarding python3-pygame: ships headers in /usr/include/python3.7/ to be marked as done. This means that you claim that the

Bug#366545: marked as done (pidentd: [security] use /bin/nologin instead of /bin/false in /etc/passwd)

2019-02-23 Thread Debian Bug Tracking System
Your message dated Sat, 23 Feb 2019 11:35:17 + with message-id and subject line Bug#922997: Removed package(s) from unstable has caused the Debian Bug report #366545, regarding pidentd: [security] use /bin/nologin instead of /bin/false in /etc/passwd to be marked as done. This means that you

Bug#859553: marked as done (pidentd: Please migrate to openssl1.1 in buster)

2019-02-23 Thread Debian Bug Tracking System
Your message dated Sat, 23 Feb 2019 11:35:17 + with message-id and subject line Bug#922997: Removed package(s) from unstable has caused the Debian Bug report #859553, regarding pidentd: Please migrate to openssl1.1 in buster to be marked as done. This means that you claim that the problem has

Bug#490636: marked as done (pidentd: add --quiet option)

2019-02-23 Thread Debian Bug Tracking System
Your message dated Sat, 23 Feb 2019 11:35:17 + with message-id and subject line Bug#922997: Removed package(s) from unstable has caused the Debian Bug report #490636, regarding pidentd: add --quiet option to be marked as done. This means that you claim that the problem has been dealt with. If

Bug#411072: marked as done (pidentd: sets groupship to :nogroup)

2019-02-23 Thread Debian Bug Tracking System
Your message dated Sat, 23 Feb 2019 11:35:17 + with message-id and subject line Bug#922997: Removed package(s) from unstable has caused the Debian Bug report #411072, regarding pidentd: sets groupship to :nogroup to be marked as done. This means that you claim that the problem has been dealt

Bug#425536: marked as done (pidentd does not suggest nor recomends idecrypt)

2019-02-23 Thread Debian Bug Tracking System
Your message dated Sat, 23 Feb 2019 11:35:17 + with message-id and subject line Bug#922997: Removed package(s) from unstable has caused the Debian Bug report #425536, regarding pidentd does not suggest nor recomends idecrypt to be marked as done. This means that you claim that the problem has

Bug#341908: marked as done (pidentd: needs to be more careful about when to update inetd)

2019-02-23 Thread Debian Bug Tracking System
Your message dated Sat, 23 Feb 2019 11:35:17 + with message-id and subject line Bug#922997: Removed package(s) from unstable has caused the Debian Bug report #341908, regarding pidentd: needs to be more careful about when to update inetd to be marked as done. This means that you claim that th

Bug#922997: marked as done (RM: pidentd -- RoQA; unmaintained, RC-buggy, alternatives exist)

2019-02-23 Thread Debian Bug Tracking System
Your message dated Sat, 23 Feb 2019 11:35:08 + with message-id and subject line Bug#922997: Removed package(s) from unstable has caused the Debian Bug report #922997, regarding RM: pidentd -- RoQA; unmaintained, RC-buggy, alternatives exist to be marked as done. This means that you claim that

Bug#337774: marked as done (linux-2.6: Identd service currently broken by default)

2019-02-23 Thread Debian Bug Tracking System
Your message dated Sat, 23 Feb 2019 11:35:17 + with message-id and subject line Bug#922997: Removed package(s) from unstable has caused the Debian Bug report #337774, regarding linux-2.6: Identd service currently broken by default to be marked as done. This means that you claim that the probl

Bug#361420: marked as done (pidentd: tcp_diag CONFIG_INET_DIAG was CONFIG_IP_TCPDIAG as mentioned in #305926)

2019-02-23 Thread Debian Bug Tracking System
Your message dated Sat, 23 Feb 2019 11:35:17 + with message-id and subject line Bug#922997: Removed package(s) from unstable has caused the Debian Bug report #339317, regarding pidentd: tcp_diag CONFIG_INET_DIAG was CONFIG_IP_TCPDIAG as mentioned in #305926 to be marked as done. This means t

Bug#374524: marked as done (pidentd: ERROR : UNKNOWN-ERROR)

2019-02-23 Thread Debian Bug Tracking System
Your message dated Sat, 23 Feb 2019 11:35:17 + with message-id and subject line Bug#922997: Removed package(s) from unstable has caused the Debian Bug report #339317, regarding pidentd: ERROR : UNKNOWN-ERROR to be marked as done. This means that you claim that the problem has been dealt with.

Bug#192538: marked as done (pidentd: Please add IPv6 support)

2019-02-23 Thread Debian Bug Tracking System
Your message dated Sat, 23 Feb 2019 11:35:17 + with message-id and subject line Bug#922997: Removed package(s) from unstable has caused the Debian Bug report #192538, regarding pidentd: Please add IPv6 support to be marked as done. This means that you claim that the problem has been dealt wit

Bug#832240: marked as done (libjs-sinon: Section should not be “ruby”)

2019-02-23 Thread Debian Bug Tracking System
Your message dated Sat, 23 Feb 2019 11:33:37 + with message-id and subject line Bug#922872: Removed package(s) from unstable has caused the Debian Bug report #832240, regarding libjs-sinon: Section should not be “ruby” to be marked as done. This means that you claim that the problem has been

Bug#320133: marked as done (pidentd denies queries on semi-closed connections)

2019-02-23 Thread Debian Bug Tracking System
Your message dated Sat, 23 Feb 2019 11:35:17 + with message-id and subject line Bug#922997: Removed package(s) from unstable has caused the Debian Bug report #320133, regarding pidentd denies queries on semi-closed connections to be marked as done. This means that you claim that the problem h

Bug#922920: marked as done (RM: imdbpy -- python-imdbpy package removed)

2019-02-23 Thread Debian Bug Tracking System
Your message dated Sat, 23 Feb 2019 11:34:21 + with message-id and subject line Bug#922920: Removed package(s) from unstable has caused the Debian Bug report #922920, regarding RM: imdbpy -- python-imdbpy package removed to be marked as done. This means that you claim that the problem has bee

Bug#339317: marked as done (pidentd: set kernel option CONFIG_INET_TCP_DIAG or CONFIG_INET_DIAG and load module tcp_diag)

2019-02-23 Thread Debian Bug Tracking System
Your message dated Sat, 23 Feb 2019 11:35:17 + with message-id and subject line Bug#922997: Removed package(s) from unstable has caused the Debian Bug report #339317, regarding pidentd: set kernel option CONFIG_INET_TCP_DIAG or CONFIG_INET_DIAG and load module tcp_diag to be marked as done.

Bug#884745: marked as done (libjs-sinon: new upstream version “4.1.3”)

2019-02-23 Thread Debian Bug Tracking System
Your message dated Sat, 23 Feb 2019 11:33:37 + with message-id and subject line Bug#922872: Removed package(s) from unstable has caused the Debian Bug report #884745, regarding libjs-sinon: new upstream version “4.1.3” to be marked as done. This means that you claim that the problem has been

Bug#922872: marked as done (RM: ruby-sinon-rails -- ROM; no longer required, no reverse dependencies)

2019-02-23 Thread Debian Bug Tracking System
Your message dated Sat, 23 Feb 2019 11:33:31 + with message-id and subject line Bug#922872: Removed package(s) from unstable has caused the Debian Bug report #922872, regarding RM: ruby-sinon-rails -- ROM; no longer required, no reverse dependencies to be marked as done. This means that you

Bug#745145: marked as done (libjs-sinon: Section should be web instead of ruby)

2019-02-23 Thread Debian Bug Tracking System
Your message dated Sat, 23 Feb 2019 11:33:37 + with message-id and subject line Bug#922872: Removed package(s) from unstable has caused the Debian Bug report #745145, regarding libjs-sinon: Section should be web instead of ruby to be marked as done. This means that you claim that the problem

Bug#835509: marked as done (ruby-sinon-rails: should depend on libjs-sinon)

2019-02-23 Thread Debian Bug Tracking System
Your message dated Sat, 23 Feb 2019 11:33:37 + with message-id and subject line Bug#922872: Removed package(s) from unstable has caused the Debian Bug report #835509, regarding ruby-sinon-rails: should depend on libjs-sinon to be marked as done. This means that you claim that the problem has

Bug#912142: marked as done (ruby-capybara-screenshot FTBFS: test failure)

2019-02-23 Thread Debian Bug Tracking System
Your message dated Sat, 23 Feb 2019 11:32:05 + with message-id and subject line Bug#922843: Removed package(s) from unstable has caused the Debian Bug report #912142, regarding ruby-capybara-screenshot FTBFS: test failure to be marked as done. This means that you claim that the problem has be

Bug#922868: marked as done (RM: ruby-protected-attributes -- ROM; obsolete with rails 5, no reverse dependencies)

2019-02-23 Thread Debian Bug Tracking System
Your message dated Sat, 23 Feb 2019 11:32:33 + with message-id and subject line Bug#922868: Removed package(s) from unstable has caused the Debian Bug report #922868, regarding RM: ruby-protected-attributes -- ROM; obsolete with rails 5, no reverse dependencies to be marked as done. This mea

Bug#918403: marked as done (ruby-rack-pjax FTBFS with ruby-rack 2.0.6-2)

2019-02-23 Thread Debian Bug Tracking System
Your message dated Sat, 23 Feb 2019 11:31:39 + with message-id and subject line Bug#922837: Removed package(s) from unstable has caused the Debian Bug report #918403, regarding ruby-rack-pjax FTBFS with ruby-rack 2.0.6-2 to be marked as done. This means that you claim that the problem has bee

Bug#918260: marked as done (ruby-protected-attributes: Depends: ruby-activemodel (< 2:5.0) but 2:5.2.0+dfsg-2 is to be installed)

2019-02-23 Thread Debian Bug Tracking System
Your message dated Sat, 23 Feb 2019 11:32:37 + with message-id and subject line Bug#922868: Removed package(s) from unstable has caused the Debian Bug report #918260, regarding ruby-protected-attributes: Depends: ruby-activemodel (< 2:5.0) but 2:5.2.0+dfsg-2 is to be installed to be marked as

Bug#922837: marked as done (RM: ruby-rack-pjax -- ROM; not required, rc buggy, only reverse dependency can also be removed)

2019-02-23 Thread Debian Bug Tracking System
Your message dated Sat, 23 Feb 2019 11:31:35 + with message-id and subject line Bug#922837: Removed package(s) from unstable has caused the Debian Bug report #922837, regarding RM: ruby-rack-pjax -- ROM; not required, rc buggy, only reverse dependency can also be removed to be marked as done.

Bug#922843: marked as done (RM: ruby-capybara-screenshot -- ROM; no longer used,no reverse dependencies, rc buggy)

2019-02-23 Thread Debian Bug Tracking System
Your message dated Sat, 23 Feb 2019 11:32:01 + with message-id and subject line Bug#922843: Removed package(s) from unstable has caused the Debian Bug report #922843, regarding RM: ruby-capybara-screenshot -- ROM; no longer used,no reverse dependencies, rc buggy to be marked as done. This me

Bug#861459: marked as done (ruby-protected-attributes: FTBFS randomly (failing tests))

2019-02-23 Thread Debian Bug Tracking System
Your message dated Sat, 23 Feb 2019 11:32:37 + with message-id and subject line Bug#922868: Removed package(s) from unstable has caused the Debian Bug report #861459, regarding ruby-protected-attributes: FTBFS randomly (failing tests) to be marked as done. This means that you claim that the p

Bug#922514: marked as done (RM: capstone4 -- ROM; taken over by src:capstone)

2019-02-23 Thread Debian Bug Tracking System
Your message dated Sat, 23 Feb 2019 11:30:31 + with message-id and subject line Bug#922514: Removed package(s) from unstable has caused the Debian Bug report #922514, regarding RM: capstone4 -- ROM; taken over by src:capstone to be marked as done. This means that you claim that the problem ha

Bug#903855: marked as done (CVE-2016-10522)

2019-02-23 Thread Debian Bug Tracking System
Your message dated Sat, 23 Feb 2019 11:31:10 + with message-id and subject line Bug#922836: Removed package(s) from unstable has caused the Debian Bug report #903855, regarding CVE-2016-10522 to be marked as done. This means that you claim that the problem has been dealt with. If this is not

Bug#922836: marked as done (RM: ruby-rails-admin -- ROM; not required, no reverse dependencies, rc buggy)

2019-02-23 Thread Debian Bug Tracking System
Your message dated Sat, 23 Feb 2019 11:31:05 + with message-id and subject line Bug#922836: Removed package(s) from unstable has caused the Debian Bug report #922836, regarding RM: ruby-rails-admin -- ROM; not required, no reverse dependencies, rc buggy to be marked as done. This means that

Bug#900178: marked as done (ruby-rails-admin: CVE-2017-12098)

2019-02-23 Thread Debian Bug Tracking System
Your message dated Sat, 23 Feb 2019 11:31:10 + with message-id and subject line Bug#922836: Removed package(s) from unstable has caused the Debian Bug report #900178, regarding ruby-rails-admin: CVE-2017-12098 to be marked as done. This means that you claim that the problem has been dealt wit

  1   2   >