Bug#954314: marked as done (neomutt: diff for NMU version 20191207+dfsg.1-1.1)

2020-03-24 Thread Debian Bug Tracking System
Your message dated Wed, 25 Mar 2020 02:12:38 + with message-id <20200325021145.fj567btokazud...@satie.tumbleweed.org.za> and subject line Bug#954314: fixed in neomutt 20191207+dfsg.1-1.1 has caused the Debian Bug report #954314, regarding neomutt: diff for NMU version 20191207+dfsg.1-1.1 to be

Bug#950559: marked as done (apertium-mk-bg FTBFS with apertium 3.6.1)

2020-03-24 Thread Debian Bug Tracking System
Your message dated Wed, 25 Mar 2020 04:49:10 + with message-id and subject line Bug#950559: fixed in apertium-mk-bg 0.2.0~r49489-3 has caused the Debian Bug report #950559, regarding apertium-mk-bg FTBFS with apertium 3.6.1 to be marked as done. This means that you claim that the problem has

Bug#954638: marked as done (golang-github-mattn-go-runewidth: FTBFS: dh_auto_test: error: cd _build && go test -vet=off -v -p 4 github.com/mattn/go-runewidth returned exit code 1)

2020-03-24 Thread Debian Bug Tracking System
Your message dated Wed, 25 Mar 2020 04:49:18 + with message-id and subject line Bug#954638: fixed in golang-github-mattn-go-runewidth 0.0.9-1 has caused the Debian Bug report #954638, regarding golang-github-mattn-go-runewidth: FTBFS: dh_auto_test: error: cd _build && go test -vet=off -v -p

Bug#953969: marked as done (onioncircuits: autopkgtest failure with Python 3.8 as default)

2020-03-24 Thread Debian Bug Tracking System
Your message dated Wed, 25 Mar 2020 00:15:41 -0400 with message-id <2562204.EoEBX4H4JI@l5580> and subject line Re: Bug#953969: onioncircuits: autopkgtest failure with Python 3.8 as default has caused the Debian Bug report #953969, regarding onioncircuits: autopkgtest failure with Python 3.8 as

Bug#915829: marked as done (ITP: arcp -- (Archive and Package) URI parser and generator)

2020-03-24 Thread Debian Bug Tracking System
Your message dated Wed, 25 Mar 2020 02:11:56 + with message-id and subject line Bug#915829: fixed in arcp 0.2.1-1 has caused the Debian Bug report #915829, regarding ITP: arcp -- (Archive and Package) URI parser and generator to be marked as done. This means that you claim that the problem

Bug#942132: marked as done (ITP: python-nest-asyncio -- Patch asyncio to allow nested event loops)

2020-03-24 Thread Debian Bug Tracking System
Your message dated Wed, 25 Mar 2020 02:11:58 + with message-id and subject line Bug#942132: fixed in python-nest-asyncio 1.2.3-1 has caused the Debian Bug report #942132, regarding ITP: python-nest-asyncio -- Patch asyncio to allow nested event loops to be marked as done. This means that you

Bug#951235: marked as done (ITP: pyscrypt -- pure-python scrypt password-based key derivation function)

2020-03-24 Thread Debian Bug Tracking System
Your message dated Wed, 25 Mar 2020 02:12:02 + with message-id and subject line Bug#951235: fixed in python-pyscrypt 1.6.2-1 has caused the Debian Bug report #951235, regarding ITP: pyscrypt -- pure-python scrypt password-based key derivation function to be marked as done. This means that

Bug#953863: marked as done (python3-stem: "RuntimeError: dictionary keys changed during iteration" with python 3.8)

2020-03-24 Thread Debian Bug Tracking System
Your message dated Wed, 25 Mar 2020 03:05:22 + with message-id and subject line Bug#953863: fixed in python-stem 1.7.1-1.2 has caused the Debian Bug report #953863, regarding python3-stem: "RuntimeError: dictionary keys changed during iteration" with python 3.8 to be marked as done. This

Processed: Re: Bug#954010: improvements to mbox viewer

2020-03-24 Thread Debian Bug Tracking System
Processing control commands: > close -1 Bug #954010 [nm.debian.org] improvements to mbox viewer Marked Bug as done -- 954010: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=954010 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems

Bug#939656: marked as done (dh_strip should strip sections with LTO information from .a and .o files / lintian should warn about these)

2020-03-24 Thread Debian Bug Tracking System
Your message dated Tue, 24 Mar 2020 18:19:09 + with message-id and subject line Bug#939656: fixed in debhelper 12.10 has caused the Debian Bug report #939656, regarding dh_strip should strip sections with LTO information from .a and .o files / lintian should warn about these to be marked as

Bug#954726: marked as done (mftrace: FTBFS: dh_auto_test: error: make -j4 test VERBOSE=1 returned exit code 2)

2020-03-24 Thread Debian Bug Tracking System
Your message dated Tue, 24 Mar 2020 18:19:44 + with message-id and subject line Bug#954726: fixed in mftrace 1.2.20+git20191022.3b4bc2e-2 has caused the Debian Bug report #954726, regarding mftrace: FTBFS: dh_auto_test: error: make -j4 test VERBOSE=1 returned exit code 2 to be marked as

Bug#950723: marked as done (dh_installsystemd: NOOP promise is unsafe)

2020-03-24 Thread Debian Bug Tracking System
Your message dated Tue, 24 Mar 2020 18:19:09 + with message-id and subject line Bug#950723: fixed in debhelper 12.10 has caused the Debian Bug report #950723, regarding dh_installsystemd: NOOP promise is unsafe to be marked as done. This means that you claim that the problem has been dealt

Bug#940442: marked as done (RFA: golang-go.uber-zap)

2020-03-24 Thread Debian Bug Tracking System
Your message dated Wed, 25 Mar 2020 01:32:02 +0530 with message-id and subject line Re: RFA: golang-go.uber-zap has caused the Debian Bug report #940442, regarding RFA: golang-go.uber-zap to be marked as done. This means that you claim that the problem has been dealt with. If this is not the

Bug#917892: marked as done (ptex2tex: /usr/bin/pygmentize moved to python3-pygments package)

2020-03-24 Thread Debian Bug Tracking System
Your message dated Tue, 24 Mar 2020 21:35:00 + with message-id and subject line Bug#954877: Removed package(s) from unstable has caused the Debian Bug report #917892, regarding ptex2tex: /usr/bin/pygmentize moved to python3-pygments package to be marked as done. This means that you claim

Bug#954832: marked as done (RM: node-run-sequence -- ROM; Deprecated since node-gulp 4)

2020-03-24 Thread Debian Bug Tracking System
Your message dated Tue, 24 Mar 2020 21:36:27 + with message-id and subject line Bug#954832: Removed package(s) from unstable has caused the Debian Bug report #954832, regarding RM: node-run-sequence -- ROM; Deprecated since node-gulp 4 to be marked as done. This means that you claim that the

Bug#937333: marked as done (ptex2tex: Python2 removal in sid/bullseye)

2020-03-24 Thread Debian Bug Tracking System
Your message dated Tue, 24 Mar 2020 21:35:00 + with message-id and subject line Bug#954877: Removed package(s) from unstable has caused the Debian Bug report #937333, regarding ptex2tex: Python2 removal in sid/bullseye to be marked as done. This means that you claim that the problem has been

Bug#937903: marked as done (python-macaron: Python2 removal in sid/bullseye)

2020-03-24 Thread Debian Bug Tracking System
Your message dated Tue, 24 Mar 2020 21:35:31 + with message-id and subject line Bug#954880: Removed package(s) from unstable has caused the Debian Bug report #937903, regarding python-macaron: Python2 removal in sid/bullseye to be marked as done. This means that you claim that the problem

Bug#954877: marked as done (RM: ptex2tex -- RoQA; Depends on Python 2)

2020-03-24 Thread Debian Bug Tracking System
Your message dated Tue, 24 Mar 2020 21:34:57 + with message-id and subject line Bug#954877: Removed package(s) from unstable has caused the Debian Bug report #954877, regarding RM: ptex2tex -- RoQA; Depends on Python 2 to be marked as done. This means that you claim that the problem has been

Bug#954880: marked as done (RM: python-macaron -- RoQA; Depends on Python 2, unmaintained)

2020-03-24 Thread Debian Bug Tracking System
Your message dated Tue, 24 Mar 2020 21:35:28 + with message-id and subject line Bug#954880: Removed package(s) from unstable has caused the Debian Bug report #954880, regarding RM: python-macaron -- RoQA; Depends on Python 2, unmaintained to be marked as done. This means that you claim that

Bug#953486: marked as done (xow: binaries for non-free not auto-built)

2020-03-24 Thread Debian Bug Tracking System
Your message dated Tue, 24 Mar 2020 21:34:13 + with message-id and subject line Bug#954876: Removed package(s) from unstable has caused the Debian Bug report #953486, regarding xow: binaries for non-free not auto-built to be marked as done. This means that you claim that the problem has been

Bug#954557: marked as done (node-run-sequence: FTBFS: dh_auto_test: error: /bin/sh -e debian/tests/pkg-js/test returned exit code 1)

2020-03-24 Thread Debian Bug Tracking System
Your message dated Tue, 24 Mar 2020 21:36:30 + with message-id and subject line Bug#954832: Removed package(s) from unstable has caused the Debian Bug report #954557, regarding node-run-sequence: FTBFS: dh_auto_test: error: /bin/sh -e debian/tests/pkg-js/test returned exit code 1 to be

Bug#954876: marked as done (RM: xow -- ROM; licensing issue)

2020-03-24 Thread Debian Bug Tracking System
Your message dated Tue, 24 Mar 2020 21:34:09 + with message-id and subject line Bug#954876: Removed package(s) from unstable has caused the Debian Bug report #954876, regarding RM: xow -- ROM; licensing issue to be marked as done. This means that you claim that the problem has been dealt

Bug#954881: marked as done (RM: meshlab [armel armhf] -- RoQA; obsolete binaries)

2020-03-24 Thread Debian Bug Tracking System
Your message dated Tue, 24 Mar 2020 21:35:54 + with message-id and subject line Bug#954881: Removed package(s) from unstable has caused the Debian Bug report #954881, regarding RM: meshlab [armel armhf] -- RoQA; obsolete binaries to be marked as done. This means that you claim that the

Bug#934479: marked as done (false negative: linux-image-4.19.0.5-powerpc64le)

2020-03-24 Thread Debian Bug Tracking System
Your message dated Tue, 24 Mar 2020 09:56:37 +0100 with message-id and subject line Re: Bug#934479: fails to detect linux update on arm64 (Re: false negative: linux-image-4.19.0.5-powerpc64le) has caused the Debian Bug report #934479, regarding false negative: linux-image-4.19.0.5-powerpc64le to

Bug#948867: marked as done (gst-plugins-base1.0 FTBFS: dpkg-gensymbols: error: some symbols or patterns disappeared in the symbols file)

2020-03-24 Thread Debian Bug Tracking System
Your message dated Tue, 24 Mar 2020 10:04:50 + with message-id and subject line Bug#948867: fixed in gst-plugins-base1.0 1.16.2-4 has caused the Debian Bug report #948867, regarding gst-plugins-base1.0 FTBFS: dpkg-gensymbols: error: some symbols or patterns disappeared in the symbols file to

Bug#948143: marked as done (libgstreamer-plugins-base1.0-dev: Should depend on libx11-xcb-dev)

2020-03-24 Thread Debian Bug Tracking System
Your message dated Tue, 24 Mar 2020 10:04:50 + with message-id and subject line Bug#948143: fixed in gst-plugins-base1.0 1.16.2-4 has caused the Debian Bug report #948143, regarding libgstreamer-plugins-base1.0-dev: Should depend on libx11-xcb-dev to be marked as done. This means that you

Bug#954829: marked as done (nmu: php-apcu_5.1.18+4.0.11-1+0~20191219.13+debian10~1.gbpa99079)

2020-03-24 Thread Debian Bug Tracking System
Your message dated Tue, 24 Mar 2020 11:07:39 +0100 with message-id and subject line Re: Bug#954829: nmu: php-apcu_5.1.18+4.0.11-1+0~20191219.13+debian10~1.gbpa99079 has caused the Debian Bug report #954829, regarding nmu: php-apcu_5.1.18+4.0.11-1+0~20191219.13+debian10~1.gbpa99079 to be marked

Bug#949249: marked as done (libslurm-dev: missing Breaks+Replaces: libslurmdb-dev (unversioned))

2020-03-24 Thread Debian Bug Tracking System
Your message dated Tue, 24 Mar 2020 11:21:40 + with message-id and subject line Bug#949249: fixed in slurm-llnl 19.05.5-2 has caused the Debian Bug report #949249, regarding libslurm-dev: missing Breaks+Replaces: libslurmdb-dev (unversioned) to be marked as done. This means that you claim

Bug#604453: marked as done (reproducible way to crash the system with kernel.function("*@*/*.c"))

2020-03-24 Thread Debian Bug Tracking System
Your message dated Tue, 24 Mar 2020 12:44:31 +0100 with message-id <20200324114431.GA13762@ariel> and subject line Re: #604453 reproducible way to crash the system with kernel.function("*@*/*.c") has caused the Debian Bug report #604453, regarding reproducible way to crash the system with

Bug#936670: marked as done (gst-python1.0: Python2 removal in sid/bullseye)

2020-03-24 Thread Debian Bug Tracking System
Your message dated Tue, 24 Mar 2020 10:19:48 + with message-id and subject line Bug#936670: fixed in gst-python1.0 1.16.2-2 has caused the Debian Bug report #936670, regarding gst-python1.0: Python2 removal in sid/bullseye to be marked as done. This means that you claim that the problem has

Bug#952149: marked as done (node-react: FTBFS: unsatisfiable build-dependencies: node-rollup-plugin-alias, node-rollup-plugin-replace)

2020-03-24 Thread Debian Bug Tracking System
Your message dated Tue, 24 Mar 2020 11:26:06 +0100 with message-id <9bc8bab4-172b-4230-acd5-16c8b244f...@debian.org> and subject line Fixed by node-rollup-plugins* updates has caused the Debian Bug report #952149, regarding node-react: FTBFS: unsatisfiable build-dependencies:

Bug#953527: marked as done ([apt] colour highlighted error/warn labels)

2020-03-24 Thread Debian Bug Tracking System
Your message dated Tue, 24 Mar 2020 11:19:24 + with message-id and subject line Bug#953527: fixed in apt 2.0.1 has caused the Debian Bug report #953527, regarding [apt] colour highlighted error/warn labels to be marked as done. This means that you claim that the problem has been dealt with.

Bug#924325: marked as done (gcc-8-cross: FTBFS for unknown reasons)

2020-03-24 Thread Debian Bug Tracking System
Your message dated Tue, 24 Mar 2020 12:07:34 + with message-id and subject line Bug#954831: Removed package(s) from unstable has caused the Debian Bug report #924325, regarding gcc-8-cross: FTBFS for unknown reasons to be marked as done. This means that you claim that the problem has been

Bug#954515: marked as done (gcc-8-cross: FTBFS: x86_64-linux-gnu-ld: /lib/x86_64-linux-gnu/libpthread.so.0: undefined reference to `__twalk_r@GLIBC_PRIVATE')

2020-03-24 Thread Debian Bug Tracking System
Your message dated Tue, 24 Mar 2020 12:07:34 + with message-id and subject line Bug#954831: Removed package(s) from unstable has caused the Debian Bug report #954515, regarding gcc-8-cross: FTBFS: x86_64-linux-gnu-ld: /lib/x86_64-linux-gnu/libpthread.so.0: undefined reference to

Bug#928424: marked as done (gcc-8-cross: Does not honor parallel=n properly in DEB_BUILD_OPTIONS)

2020-03-24 Thread Debian Bug Tracking System
Your message dated Tue, 24 Mar 2020 12:07:34 + with message-id and subject line Bug#954831: Removed package(s) from unstable has caused the Debian Bug report #928424, regarding gcc-8-cross: Does not honor parallel=n properly in DEB_BUILD_OPTIONS to be marked as done. This means that you

Bug#954831: marked as done (RM: gcc-8, superseded by gcc-9)

2020-03-24 Thread Debian Bug Tracking System
Your message dated Tue, 24 Mar 2020 12:07:22 + with message-id and subject line Bug#954831: Removed package(s) from unstable has caused the Debian Bug report #954831, regarding RM: gcc-8, superseded by gcc-9 to be marked as done. This means that you claim that the problem has been dealt

Bug#919141: marked as done (gcc-8-cross: please support binnmu)

2020-03-24 Thread Debian Bug Tracking System
Your message dated Tue, 24 Mar 2020 12:07:34 + with message-id and subject line Bug#954831: Removed package(s) from unstable has caused the Debian Bug report #919141, regarding gcc-8-cross: please support binnmu to be marked as done. This means that you claim that the problem has been dealt

Bug#952025: marked as done (ruby-grape: FTBFS: ERROR: Test "ruby2.7" failed: Failure/Error: spec = parsers(**options)[api_format])

2020-03-24 Thread Debian Bug Tracking System
Your message dated Tue, 24 Mar 2020 11:21:24 + with message-id and subject line Bug#952025: fixed in ruby-grape 1.3.1+git20200320.c8fd21b-1 has caused the Debian Bug report #952025, regarding ruby-grape: FTBFS: ERROR: Test "ruby2.7" failed: Failure/Error: spec =

Bug#867027: marked as done (test failure: Grape::Validations::CoerceValidator coerce multiple types for primitive collections when updating ruby-hashie)

2020-03-24 Thread Debian Bug Tracking System
Your message dated Tue, 24 Mar 2020 11:21:24 + with message-id and subject line Bug#867027: fixed in ruby-grape 1.3.1+git20200320.c8fd21b-1 has caused the Debian Bug report #867027, regarding test failure: Grape::Validations::CoerceValidator coerce multiple types for primitive collections

Bug#950383: marked as done (apertium-isl-eng FTBFS with apertium 3.6.1)

2020-03-24 Thread Debian Bug Tracking System
Your message dated Tue, 24 Mar 2020 09:04:21 + with message-id and subject line Bug#950383: fixed in apertium-isl-eng 0.1.0~r66083-3 has caused the Debian Bug report #950383, regarding apertium-isl-eng FTBFS with apertium 3.6.1 to be marked as done. This means that you claim that the problem

Bug#948714: marked as done (gst-plugins-good1.0 FTBFS: gst/gl/x11/gstgldisplay_x11.h:26:10: fatal error: X11/Xlib-xcb.h: No such file or directory)

2020-03-24 Thread Debian Bug Tracking System
Your message dated Tue, 24 Mar 2020 11:05:05 + with message-id and subject line Bug#948714: fixed in gst-plugins-good1.0 1.16.2-3 has caused the Debian Bug report #948714, regarding gst-plugins-good1.0 FTBFS: gst/gl/x11/gstgldisplay_x11.h:26:10: fatal error: X11/Xlib-xcb.h: No such file or

Bug#954659: marked as done (FTBFS: gjs:JS / Gio unit test crashes after 5th TAP test)

2020-03-24 Thread Debian Bug Tracking System
Your message dated Tue, 24 Mar 2020 11:04:37 + with message-id and subject line Bug#954659: fixed in gjs 1.64.0-1 has caused the Debian Bug report #954659, regarding FTBFS: gjs:JS / Gio unit test crashes after 5th TAP test to be marked as done. This means that you claim that the problem has

Bug#899088: marked as done (gcc-8-cross-ports: provide riscv32 cross compiler)

2020-03-24 Thread Debian Bug Tracking System
Your message dated Tue, 24 Mar 2020 12:09:06 + with message-id and subject line Bug#954831: Removed package(s) from unstable has caused the Debian Bug report #899088, regarding gcc-8-cross-ports: provide riscv32 cross compiler to be marked as done. This means that you claim that the problem

Bug#954139: marked as done (metview fail to start after clean install on sid)

2020-03-24 Thread Debian Bug Tracking System
Your message dated Tue, 24 Mar 2020 09:34:28 + with message-id and subject line Bug#954139: fixed in metview 5.8.1-2 has caused the Debian Bug report #954139, regarding metview fail to start after clean install on sid to be marked as done. This means that you claim that the problem has been

Bug#837697: marked as done (systemtap: Arguments of user probes are always (incorrectly) zero)

2020-03-24 Thread Debian Bug Tracking System
Your message dated Tue, 24 Mar 2020 11:23:47 +0100 with message-id <20200324102347.GA6020@ariel> and subject line Re: Bug#837697: systemtap: Arguments of user probes are always (incorrectly) zero has caused the Debian Bug report #837697, regarding systemtap: Arguments of user probes are always

Bug#935199: marked as done (network-manager-openconnect: New upstream release 1.2.6 support protocol selector (newest Palo Alto and Juniper devices))

2020-03-24 Thread Debian Bug Tracking System
Your message dated Tue, 24 Mar 2020 11:36:06 + with message-id and subject line Bug#935199: fixed in network-manager-openconnect 1.2.6-1 has caused the Debian Bug report #935199, regarding network-manager-openconnect: New upstream release 1.2.6 support protocol selector (newest Palo Alto and

Bug#953752: marked as done (Add Palo Alto Global Protect support to the GUI)

2020-03-24 Thread Debian Bug Tracking System
Your message dated Tue, 24 Mar 2020 11:36:06 + with message-id and subject line Bug#953752: fixed in network-manager-openconnect 1.2.6-1 has caused the Debian Bug report #953752, regarding Add Palo Alto Global Protect support to the GUI to be marked as done. This means that you claim that

Bug#953057: marked as done (subversion: FTBFS against swig 4)

2020-03-24 Thread Debian Bug Tracking System
Your message dated Tue, 24 Mar 2020 12:52:28 + with message-id and subject line Bug#951893: fixed in subversion 1.13.0-3 has caused the Debian Bug report #951893, regarding subversion: FTBFS against swig 4 to be marked as done. This means that you claim that the problem has been dealt with.

Bug#951893: marked as done (subversion FTBFS with swig 4.0.1)

2020-03-24 Thread Debian Bug Tracking System
Your message dated Tue, 24 Mar 2020 12:52:28 + with message-id and subject line Bug#951893: fixed in subversion 1.13.0-3 has caused the Debian Bug report #951893, regarding subversion FTBFS with swig 4.0.1 to be marked as done. This means that you claim that the problem has been dealt with.

Bug#954438: marked as done (libgccjit0: GCCJIT leads to linking error)

2020-03-24 Thread Debian Bug Tracking System
Your message dated Tue, 24 Mar 2020 13:06:09 + with message-id and subject line Bug#954438: fixed in gcc-10 10-20200324-1 has caused the Debian Bug report #954438, regarding libgccjit0: GCCJIT leads to linking error to be marked as done. This means that you claim that the problem has been

Bug#954617: marked as done (golang-github-mendersoftware-log: FTBFS: dh_auto_test: error: cd obj-x86_64-linux-gnu && go test -vet=off -v -p 4 github.com/mendersoftware/log returned exit code 2)

2020-03-24 Thread Debian Bug Tracking System
Your message dated Tue, 24 Mar 2020 12:49:33 + with message-id and subject line Bug#954617: fixed in golang-github-mendersoftware-log 0.0~git20191210.25ea5b7-1 has caused the Debian Bug report #954617, regarding golang-github-mendersoftware-log: FTBFS: dh_auto_test: error: cd

Bug#952199: marked as done (golang-github-boltdb-bolt: FTBFS: dh_auto_test: error: cd obj-x86_64-linux-gnu && go test -vet=off -v -p 4 -short github.com/boltdb/bolt github.com/boltdb/bolt/cmd/bolt ret

2020-03-24 Thread Debian Bug Tracking System
Your message dated Tue, 24 Mar 2020 12:49:18 + with message-id and subject line Bug#952199: fixed in golang-github-boltdb-bolt 1.3.1-7 has caused the Debian Bug report #952199, regarding golang-github-boltdb-bolt: FTBFS: dh_auto_test: error: cd obj-x86_64-linux-gnu && go test -vet=off -v -p

Bug#954751: marked as done (libgcc-10-dev: Missing include/sanitizer/)

2020-03-24 Thread Debian Bug Tracking System
Your message dated Tue, 24 Mar 2020 13:06:10 + with message-id and subject line Bug#954751: fixed in gcc-10 10-20200324-1 has caused the Debian Bug report #954751, regarding libgcc-10-dev: Missing include/sanitizer/ to be marked as done. This means that you claim that the problem has been

Bug#952321: marked as done (golang-github-akrennmair-gopcap: FTBFS: dh_auto_build: error: cd obj-x86_64-linux-gnu && go install -trimpath -v -p 1 github.com/akrennmair/gopcap returned exit code 2)

2020-03-24 Thread Debian Bug Tracking System
Your message dated Tue, 24 Mar 2020 12:19:51 + with message-id and subject line Bug#952321: fixed in golang-github-akrennmair-gopcap 0.0~git20150728.0.00e1103-3 has caused the Debian Bug report #952321, regarding golang-github-akrennmair-gopcap: FTBFS: dh_auto_build: error: cd

Bug#950654: marked as done (node-eslint-plugin-html seems unusable without eslint)

2020-03-24 Thread Debian Bug Tracking System
Your message dated Tue, 24 Mar 2020 13:34:24 + with message-id and subject line Bug#950654: fixed in node-eslint-plugin-html 3.2.1-2 has caused the Debian Bug report #950654, regarding node-eslint-plugin-html seems unusable without eslint to be marked as done. This means that you claim that

Bug#934805: marked as done (lintian: probably shouldn't emit package-supports-alternative-init-but-no-init.d-script for instanced systemd services (foo@.service))

2020-03-24 Thread Debian Bug Tracking System
Your message dated Tue, 24 Mar 2020 13:41:44 + with message-id <0473ec0e-2b45-4944-a1ea-1803fceb8f02@sloti26t01> and subject line Re: lintian: probably shouldn't emit package-supports-alternative-init-but-no-init.d-script for instanced systemd services (foo@.service) has caused the Debian

Bug#952335: marked as done (uglify-js: FTBFS: ERROR: `m` is not a supported option)

2020-03-24 Thread Debian Bug Tracking System
Your message dated Tue, 24 Mar 2020 14:45:11 + with message-id and subject line Bug#952335: fixed in node-commander 4.0.1+really2.20.0-1 has caused the Debian Bug report #952335, regarding uglify-js: FTBFS: ERROR: `m` is not a supported option to be marked as done. This means that you claim

Bug#937009: marked as done (mercurial: Python2 removal in sid/bullseye)

2020-03-24 Thread Debian Bug Tracking System
Your message dated Tue, 24 Mar 2020 14:44:51 + with message-id and subject line Bug#937009: fixed in mercurial 5.3.1-1+exp1 has caused the Debian Bug report #937009, regarding mercurial: Python2 removal in sid/bullseye to be marked as done. This means that you claim that the problem has been

Bug#952206: marked as done (golang-go.uber-zap: FTBFS: dh_auto_test: error: cd obj-x86_64-linux-gnu && go test -vet=off -v -p 4 go.uber.org/zap go.uber.org/zap/buffer go.uber.org/zap/internal/bufferpo

2020-03-24 Thread Debian Bug Tracking System
Your message dated Tue, 24 Mar 2020 14:43:24 + with message-id and subject line Bug#952206: fixed in golang-go.uber-zap 1.14.1-1 has caused the Debian Bug report #952206, regarding golang-go.uber-zap: FTBFS: dh_auto_test: error: cd obj-x86_64-linux-gnu && go test -vet=off -v -p 4

Bug#943193: marked as done (neurodebian: Python2 removal in sid/bullseye)

2020-03-24 Thread Debian Bug Tracking System
Your message dated Tue, 24 Mar 2020 11:19:55 -0400 with message-id <20200324151955.gv5...@lena.dartmouth.edu> and subject line Re: Processed: found 943193 in 0.38.3 has caused the Debian Bug report #943193, regarding neurodebian: Python2 removal in sid/bullseye to be marked as done. This means

Bug#715205: marked as done ([lighttpd]: Running lighttpd as another user)

2020-03-24 Thread Debian Bug Tracking System
Your message dated Tue, 24 Mar 2020 11:31:49 -0400 with message-id <20200324153149.GB860795@xps13> and subject line 715205-done has caused the Debian Bug report #715205, regarding [lighttpd]: Running lighttpd as another user to be marked as done. This means that you claim that the problem has

Bug#928059: marked as done (lighttpd: setenv missing from conf-available)

2020-03-24 Thread Debian Bug Tracking System
Your message dated Tue, 24 Mar 2020 11:44:00 -0400 with message-id <20200324154400.GA861240@xps13> and subject line 928059-done has caused the Debian Bug report #928059, regarding lighttpd: setenv missing from conf-available to be marked as done. This means that you claim that the problem has

Bug#954550: marked as done (libprelude: FTBFS: Prelude.cxx:1263:85: error: call of overloaded ‘rb_define_virtual_variable(const char [21], VALUE (&)(...), NULL)’ is ambiguous)

2020-03-24 Thread Debian Bug Tracking System
Your message dated Tue, 24 Mar 2020 16:11:07 + with message-id and subject line Bug#954550: fixed in libprelude 5.1.1-5 has caused the Debian Bug report #954550, regarding libprelude: FTBFS: Prelude.cxx:1263:85: error: call of overloaded ‘rb_define_virtual_variable(const char [21], VALUE

Bug#954785: marked as done (libprelude FTBFS against ruby 2.7)

2020-03-24 Thread Debian Bug Tracking System
Your message dated Tue, 24 Mar 2020 16:11:07 + with message-id and subject line Bug#954785: fixed in libprelude 5.1.1-5 has caused the Debian Bug report #954785, regarding libprelude FTBFS against ruby 2.7 to be marked as done. This means that you claim that the problem has been dealt with.

Bug#954669: marked as done (Please update shared-mime-info to 1.15, and update the watch file)

2020-03-24 Thread Debian Bug Tracking System
Your message dated Tue, 24 Mar 2020 16:45:50 + with message-id and subject line Bug#954669: fixed in shared-mime-info 1.15-1 has caused the Debian Bug report #954669, regarding Please update shared-mime-info to 1.15, and update the watch file to be marked as done. This means that you claim

Bug#788187: marked as done (Missing option for icinga2 on configure backend)

2020-03-24 Thread Debian Bug Tracking System
Your message dated Tue, 24 Mar 2020 17:11:59 + with message-id and subject line Bug#788187: fixed in nagvis 1:1.9.18-1 has caused the Debian Bug report #788187, regarding Missing option for icinga2 on configure backend to be marked as done. This means that you claim that the problem has been

Bug#949387: marked as done (nagivs: New upstream release 1.19.17)

2020-03-24 Thread Debian Bug Tracking System
Your message dated Tue, 24 Mar 2020 17:11:59 + with message-id and subject line Bug#949387: fixed in nagvis 1:1.9.18-1 has caused the Debian Bug report #949387, regarding nagivs: New upstream release 1.19.17 to be marked as done. This means that you claim that the problem has been dealt

Processed: Re: Bug#925816: marked as done (qxw: ftbfs with GCC-9)

2020-03-24 Thread Debian Bug Tracking System
Processing control commands: > reopen 925816 Bug #925816 [src:qxw] qxw: ftbfs with GCC-9 Bug 925816 is not marked as done; doing nothing. > close 925826 15+1533136590.3beb971-8 Bug #925826 {Done: Steve McIntyre } [src:shim] shim: ftbfs with GCC-9 The source 'shim' and version

Processed: Re: Bug#925816: marked as done (qxw: ftbfs with GCC-9)

2020-03-24 Thread Debian Bug Tracking System
Processing control commands: > reopen 925816 Bug #925816 {Done: Steve McIntyre <93...@debian.org>} [src:qxw] qxw: ftbfs with GCC-9 'reopen' may be inappropriate when a bug has been closed with a version; all fixed versions will be cleared, and you may need to re-add them. Bug reopened No longer

Bug#884431: marked as done (gcc-7: miscompile pthread_barrier.c from glibc with -mcpu=ultrasparc)

2020-03-24 Thread Debian Bug Tracking System
Your message dated Tue, 24 Mar 2020 21:39:38 + with message-id and subject line Bug#923982: Removed package(s) from unstable has caused the Debian Bug report #884431, regarding gcc-7: miscompile pthread_barrier.c from glibc with -mcpu=ultrasparc to be marked as done. This means that you

Bug#881288: marked as done (gcc-7 fails to patch when old distribution detected)

2020-03-24 Thread Debian Bug Tracking System
Your message dated Tue, 24 Mar 2020 21:39:38 + with message-id and subject line Bug#923982: Removed package(s) from unstable has caused the Debian Bug report #881288, regarding gcc-7 fails to patch when old distribution detected to be marked as done. This means that you claim that the

Bug#879703: marked as done (gcc-7: static development libraries miss debug information)

2020-03-24 Thread Debian Bug Tracking System
Your message dated Tue, 24 Mar 2020 21:39:38 + with message-id and subject line Bug#923982: Removed package(s) from unstable has caused the Debian Bug report #879703, regarding gcc-7: static development libraries miss debug information to be marked as done. This means that you claim that the

Bug#901836: marked as done (-mieee-fp broken on i386)

2020-03-24 Thread Debian Bug Tracking System
Your message dated Tue, 24 Mar 2020 21:39:38 + with message-id and subject line Bug#923982: Removed package(s) from unstable has caused the Debian Bug report #901836, regarding -mieee-fp broken on i386 to be marked as done. This means that you claim that the problem has been dealt with. If

Bug#894302: marked as done (g++-7: Compiler generates wrong code with warning options)

2020-03-24 Thread Debian Bug Tracking System
Your message dated Tue, 24 Mar 2020 21:39:38 + with message-id and subject line Bug#923982: Removed package(s) from unstable has caused the Debian Bug report #894302, regarding g++-7: Compiler generates wrong code with warning options to be marked as done. This means that you claim that the

Bug#954830: marked as done (RM: gcc-7 -- ROM; old version not used anymore)

2020-03-24 Thread Debian Bug Tracking System
Your message dated Tue, 24 Mar 2020 21:39:38 + with message-id and subject line Bug#923982: Removed package(s) from unstable has caused the Debian Bug report #954830, regarding RM: gcc-7 -- ROM; old version not used anymore to be marked as done. This means that you claim that the problem has

Bug#882490: marked as done (gcc: Tune default --param ggc-min-expand for 32-bit arches)

2020-03-24 Thread Debian Bug Tracking System
Your message dated Tue, 24 Mar 2020 21:39:38 + with message-id and subject line Bug#923982: Removed package(s) from unstable has caused the Debian Bug report #882490, regarding gcc: Tune default --param ggc-min-expand for 32-bit arches to be marked as done. This means that you claim that the

Bug#888394: marked as done (GCC bootstrap comparison failure build the D frontend on alpha)

2020-03-24 Thread Debian Bug Tracking System
Your message dated Tue, 24 Mar 2020 21:39:38 + with message-id and subject line Bug#923982: Removed package(s) from unstable has caused the Debian Bug report #888394, regarding GCC bootstrap comparison failure build the D frontend on alpha to be marked as done. This means that you claim that

Bug#895452: marked as done (gcc-7: libquadmath is disabled for gcc 7.3.0 on powerpc64-linux-gnu)

2020-03-24 Thread Debian Bug Tracking System
Your message dated Tue, 24 Mar 2020 21:39:38 + with message-id and subject line Bug#923982: Removed package(s) from unstable has caused the Debian Bug report #895452, regarding gcc-7: libquadmath is disabled for gcc 7.3.0 on powerpc64-linux-gnu to be marked as done. This means that you claim

Bug#887453: marked as done (libunwind: please disable lzma on ia64)

2020-03-24 Thread Debian Bug Tracking System
Your message dated Tue, 24 Mar 2020 21:39:38 + with message-id and subject line Bug#923982: Removed package(s) from unstable has caused the Debian Bug report #887453, regarding libunwind: please disable lzma on ia64 to be marked as done. This means that you claim that the problem has been

Bug#923982: marked as done (RM: gcc-7 -- old version not used anymore)

2020-03-24 Thread Debian Bug Tracking System
Your message dated Tue, 24 Mar 2020 21:39:17 + with message-id and subject line Bug#923982: Removed package(s) from unstable has caused the Debian Bug report #923982, regarding RM: gcc-7 -- old version not used anymore to be marked as done. This means that you claim that the problem has been

Bug#881939: marked as done (gcc: disable D when cross build native GCC)

2020-03-24 Thread Debian Bug Tracking System
Your message dated Tue, 24 Mar 2020 21:39:38 + with message-id and subject line Bug#923982: Removed package(s) from unstable has caused the Debian Bug report #881939, regarding gcc: disable D when cross build native GCC to be marked as done. This means that you claim that the problem has

Bug#870375: marked as done (gcc-7: Native gdc cross-builds fail)

2020-03-24 Thread Debian Bug Tracking System
Your message dated Tue, 24 Mar 2020 21:39:38 + with message-id and subject line Bug#923982: Removed package(s) from unstable has caused the Debian Bug report #870375, regarding gcc-7: Native gdc cross-builds fail to be marked as done. This means that you claim that the problem has been dealt

Bug#866369: marked as done (gdc unittest fails to build on ARM32)

2020-03-24 Thread Debian Bug Tracking System
Your message dated Tue, 24 Mar 2020 21:39:38 + with message-id and subject line Bug#923982: Removed package(s) from unstable has caused the Debian Bug report #866369, regarding gdc unittest fails to build on ARM32 to be marked as done. This means that you claim that the problem has been

Bug#886099: marked as done (gcc-7: backport PR target/82981)

2020-03-24 Thread Debian Bug Tracking System
Your message dated Tue, 24 Mar 2020 21:39:38 + with message-id and subject line Bug#923982: Removed package(s) from unstable has caused the Debian Bug report #886099, regarding gcc-7: backport PR target/82981 to be marked as done. This means that you claim that the problem has been dealt

Processed: Re: ERROR: Signature extraction failed + WARNING: Unable to extract video title

2020-03-24 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > close 945405 2020.01.24-0.1 Bug #945405 [youtube-dl] ERROR: Signature extraction failed + WARNING: Unable to extract video title Marked as fixed in versions youtube-dl/2020.01.24-0.1. Bug #945405 [youtube-dl] ERROR: Signature extraction failed +

Bug#954642: marked as done (fonttools: FTBFS: dh_auto_test: error: pybuild --test --test-pytest -i python{version} -p "3.7 3.8" returned exit code 13)

2020-03-24 Thread Debian Bug Tracking System
Your message dated Tue, 24 Mar 2020 19:19:39 + with message-id and subject line Bug#954642: fixed in fonttools 4.5.0-1 has caused the Debian Bug report #954642, regarding fonttools: FTBFS: dh_auto_test: error: pybuild --test --test-pytest -i python{version} -p "3.7 3.8" returned exit code 13

Bug#919387: marked as done (autopkgtest: missing build dependency on sysvinit-utils)

2020-03-24 Thread Debian Bug Tracking System
Your message dated Tue, 24 Mar 2020 20:18:41 +0100 with message-id and subject line Re: Bug#919387: autopkgtest: missing build dependency on sysvinit-utils has caused the Debian Bug report #919387, regarding autopkgtest: missing build dependency on sysvinit-utils to be marked as done. This

Bug#940359: marked as done (RFA: golang-github-glycerine-go-unsnap-stream)

2020-03-24 Thread Debian Bug Tracking System
Your message dated Tue, 24 Mar 2020 20:45:38 + with message-id and subject line Bug#940359: fixed in golang-github-glycerine-go-unsnap-stream 0.0~git20190901.81cf024-1 has caused the Debian Bug report #940359, regarding RFA: golang-github-glycerine-go-unsnap-stream to be marked as done.

Bug#940369: marked as done (RFA: golang-github-influxdata-influxql)

2020-03-24 Thread Debian Bug Tracking System
Your message dated Tue, 24 Mar 2020 20:45:46 + with message-id and subject line Bug#940369: fixed in golang-github-influxdata-influxql 1.1.0-1 has caused the Debian Bug report #940369, regarding RFA: golang-github-influxdata-influxql to be marked as done. This means that you claim that the

Bug#954750: marked as done (libgcc-9-dev: Missing include/sanitizer/)

2020-03-24 Thread Debian Bug Tracking System
) unstable; urgency=medium . * Update to git 20200324 from the gcc-9 branch. - Fix PR tree-optimization/94125, PR target/90763 (PPC). * libgcc-N-dev: Include sanitizer headers again. Closes: #954750. * gm2: Define lang_register_spec_functions for jit. Addresses: #954438.

Bug#392396: marked as done (xstarfish: starfish-1.1/unix/.AppleDouble/zut-1.5.tar.gz corrupted)

2020-03-24 Thread Debian Bug Tracking System
Your message dated Tue, 24 Mar 2020 21:06:15 + with message-id and subject line Bug#392396: fixed in xstarfish 1.1+ds-1 has caused the Debian Bug report #392396, regarding xstarfish: starfish-1.1/unix/.AppleDouble/zut-1.5.tar.gz corrupted to be marked as done. This means that you claim that

Bug#810078: marked as done (xstarfish: diff for NMU version 1.1-11.1)

2020-03-24 Thread Debian Bug Tracking System
Your message dated Tue, 24 Mar 2020 21:06:15 + with message-id and subject line Bug#810078: fixed in xstarfish 1.1+ds-1 has caused the Debian Bug report #810078, regarding xstarfish: diff for NMU version 1.1-11.1 to be marked as done. This means that you claim that the problem has been dealt

Bug#954887: marked as done (Returning UPnP response with 200 items out of 246 total matches)

2020-03-24 Thread Debian Bug Tracking System
Your message dated Tue, 24 Mar 2020 22:03:54 +0100 with message-id and subject line Re: Bug#954887: Acknowledgement (Returning UPnP response with 200 items out of 246 total matches) has caused the Debian Bug report #954887, regarding Returning UPnP response with 200 items out of 246 total

Bug#885953: marked as done (xstarfish: \r in filename in .orig tarball)

2020-03-24 Thread Debian Bug Tracking System
Your message dated Tue, 24 Mar 2020 21:06:15 + with message-id and subject line Bug#885953: fixed in xstarfish 1.1+ds-1 has caused the Debian Bug report #885953, regarding xstarfish: \r in filename in .orig tarball to be marked as done. This means that you claim that the problem has been

Bug#951819: marked as done (debhelper: dh_installsystemduser can't install parameterized services)

2020-03-24 Thread Debian Bug Tracking System
Your message dated Tue, 24 Mar 2020 18:19:09 + with message-id and subject line Bug#951819: fixed in debhelper 12.10 has caused the Debian Bug report #951819, regarding debhelper: dh_installsystemduser can't install parameterized services to be marked as done. This means that you claim that

Bug#925816: marked as done (qxw: ftbfs with GCC-9)

2020-03-24 Thread Debian Bug Tracking System
Your message dated Tue, 24 Mar 2020 18:19:58 + with message-id and subject line Bug#925816: fixed in shim 15+1533136590.3beb971-8 has caused the Debian Bug report #925816, regarding qxw: ftbfs with GCC-9 to be marked as done. This means that you claim that the problem has been dealt with. If

Processed: bts

2020-03-24 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > close 946439 2020.01.24-0.1 Bug #946439 [youtube-dl] youtube-dl needs python3.8 for dailymotion.com Marked as fixed in versions youtube-dl/2020.01.24-0.1. Bug #946439 [youtube-dl] youtube-dl needs python3.8 for dailymotion.com Marked Bug as done

Bug#940374: marked as done (RFA: golang-github-jackpal-gateway)

2020-03-24 Thread Debian Bug Tracking System
Your message dated Tue, 24 Mar 2020 19:34:58 + with message-id and subject line Bug#940374: fixed in golang-github-jackpal-gateway 1.0.4-5 has caused the Debian Bug report #940374, regarding RFA: golang-github-jackpal-gateway to be marked as done. This means that you claim that the problem

Bug#951186: marked as done (Please reconsider usage of perl-Array-IntSpan in licensecheck)

2020-03-24 Thread Debian Bug Tracking System
Your message dated Tue, 24 Mar 2020 22:21:26 +0100 with message-id <158508488673.3704239.17642803147167183...@auryn.jones.dk> and subject line Re: Bug#951186: Please reconsider usage of perl-Array-IntSpan in licensecheck has caused the Debian Bug report #951186, regarding Please reconsider usage

Bug#853709: marked as done (xbubble: ftbfs with GCC-7)

2020-03-24 Thread Debian Bug Tracking System
Your message dated Tue, 24 Mar 2020 21:39:38 + with message-id and subject line Bug#923982: Removed package(s) from unstable has caused the Debian Bug report #853709, regarding xbubble: ftbfs with GCC-7 to be marked as done. This means that you claim that the problem has been dealt with. If

  1   2   >