Bug#918328: marked as done (aptitude: symbol lookup error: aptitude: undefined symbol: _ZN6Xapian4MSetC1EOS0_)

2019-01-04 Thread Debian Bug Tracking System
Your message dated Sat, 05 Jan 2019 08:45:01 +0100 with message-id <874lanim4i@turtle.gmx.de> and subject line Re: Bug#918328: aptitude: symbol lookup error: aptitude: undefined symbol: _ZN6Xapian4MSetC1EOS0_ has caused the Debian Bug report #918328, regarding aptitude: symbol lookup error: ap

Bug#896786: marked as done (rss2email: missing build dependency on python3-distutils)

2019-01-04 Thread Debian Bug Tracking System
Your message dated Sat, 05 Jan 2019 07:35:00 + with message-id and subject line Bug#896786: fixed in rss2email 1:3.9-4.1 has caused the Debian Bug report #896786, regarding rss2email: missing build dependency on python3-distutils to be marked as done. This means that you claim that the proble

Bug#914657: marked as done (missing snmp.conf triggers flood of error messages)

2019-01-04 Thread Debian Bug Tracking System
Your message dated Sat, 05 Jan 2019 05:49:44 + with message-id and subject line Bug#914657: fixed in net-snmp 5.7.3+dfsg-5 has caused the Debian Bug report #914657, regarding missing snmp.conf triggers flood of error messages to be marked as done. This means that you claim that the problem ha

Processed: re-closing bug

2019-01-04 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > close 914607 20181214-2 Bug #914607 [dfwinreg] plaso depends on cruft package python-dfwinreg There is no source info for the package 'dfwinreg' at version '20181214-2' with architecture '' Unable to make a source version for version '20181214-2'

Bug#912685: marked as done (debian/rules is not binNMU safe)

2019-01-04 Thread Debian Bug Tracking System
Your message dated Sat, 05 Jan 2019 05:49:44 + with message-id and subject line Bug#912685: fixed in net-snmp 5.7.3+dfsg-5 has caused the Debian Bug report #912685, regarding debian/rules is not binNMU safe to be marked as done. This means that you claim that the problem has been dealt with.

Bug#918271: marked as done (Why does Debian start every process with low max priority in Linux)

2019-01-04 Thread Debian Bug Tracking System
Your message dated Sat, 05 Jan 2019 05:08:36 + with message-id <3b7782bd4738bcdbbd32fe6708e82a76dc0071da.ca...@decadent.org.uk> and subject line Re: Bug#918271: Why does Debian start every process with low max priority in Linux has caused the Debian Bug report #918271, regarding Why does Debia

Bug#914236: marked as done (ibus-chewing: Should we upgrade to v1.6.1?)

2019-01-04 Thread Debian Bug Tracking System
Your message dated Sat, 5 Jan 2019 11:47:01 +0800 with message-id <20190105034701.ga27...@gmail.com> and subject line Re: Bug#914236: ibus-chewing: Should we upgrade to v1.6.1? has caused the Debian Bug report #914236, regarding ibus-chewing: Should we upgrade to v1.6.1? to be marked as done. This

Bug#918177: marked as done (libcpuinfo0: Log-level specified compile-time is very annoing)

2019-01-04 Thread Debian Bug Tracking System
Your message dated Sat, 05 Jan 2019 02:40:22 + with message-id and subject line Bug#918177: fixed in cpuinfo 0.0~git20181219.a974884-2 has caused the Debian Bug report #918177, regarding libcpuinfo0: Log-level specified compile-time is very annoing to be marked as done. This means that you cl

Bug#914474: marked as done (sphinx-testing: Please update to v0.8.1 which is compatible with Sphinx 1.8)

2019-01-04 Thread Debian Bug Tracking System
Your message dated Sat, 05 Jan 2019 00:35:29 + with message-id and subject line Bug#914474: fixed in sphinx-testing 0.8.1-1 has caused the Debian Bug report #914474, regarding sphinx-testing: Please update to v0.8.1 which is compatible with Sphinx 1.8 to be marked as done. This means that yo

Bug#917895: marked as done (RFS: rmlint/2.8.0-1)

2019-01-04 Thread Debian Bug Tracking System
Your message dated Sat, 5 Jan 2019 01:29:41 +0100 with message-id <20190105002941.6oxjivwfrp5cl...@angband.pl> and subject line Re: Bug#917895: RFS: rmlint/2.8.0-1 has caused the Debian Bug report #917895, regarding RFS: rmlint/2.8.0-1 to be marked as done. This means that you claim that the probl

Bug#891059: marked as done (O: bfgminer -- multi-threaded multi-pool ASIC, FPGA and GPU bitcoin miner)

2019-01-04 Thread Debian Bug Tracking System
Your message dated Sat, 05 Jan 2019 00:19:34 + with message-id and subject line Bug#918313: Removed package(s) from unstable has caused the Debian Bug report #891059, regarding O: bfgminer -- multi-threaded multi-pool ASIC, FPGA and GPU bitcoin miner to be marked as done. This means that you

Bug#899449: marked as done (bfgminer: Invalid maintainer address pkg-bitcoin-de...@lists.alioth.debian.org)

2019-01-04 Thread Debian Bug Tracking System
Your message dated Sat, 05 Jan 2019 00:19:34 + with message-id and subject line Bug#918313: Removed package(s) from unstable has caused the Debian Bug report #899449, regarding bfgminer: Invalid maintainer address pkg-bitcoin-de...@lists.alioth.debian.org to be marked as done. This means tha

Bug#918313: marked as done (RM: bfgminer -- RoQA; RC-buggy, orphaned, not in stable)

2019-01-04 Thread Debian Bug Tracking System
Your message dated Sat, 05 Jan 2019 00:19:29 + with message-id and subject line Bug#918313: Removed package(s) from unstable has caused the Debian Bug report #918313, regarding RM: bfgminer -- RoQA; RC-buggy, orphaned, not in stable to be marked as done. This means that you claim that the pro

Bug#900930: marked as done (CVE-2018-10057 CVE-2018-10058)

2019-01-04 Thread Debian Bug Tracking System
Your message dated Sat, 05 Jan 2019 00:19:34 + with message-id and subject line Bug#918313: Removed package(s) from unstable has caused the Debian Bug report #900930, regarding CVE-2018-10057 CVE-2018-10058 to be marked as done. This means that you claim that the problem has been dealt with.

Bug#824117: marked as done (bfgminer: daemon mode)

2019-01-04 Thread Debian Bug Tracking System
Your message dated Sat, 05 Jan 2019 00:19:34 + with message-id and subject line Bug#918313: Removed package(s) from unstable has caused the Debian Bug report #824117, regarding bfgminer: daemon mode to be marked as done. This means that you claim that the problem has been dealt with. If this

Bug#918199: marked as done (RM: libxfcegui4 -- ROM; deprecated upstream, no reverse dependencies)

2019-01-04 Thread Debian Bug Tracking System
Your message dated Sat, 05 Jan 2019 00:19:02 + with message-id and subject line Bug#918199: Removed package(s) from unstable has caused the Debian Bug report #918199, regarding RM: libxfcegui4 -- ROM; deprecated upstream, no reverse dependencies to be marked as done. This means that you claim

Bug#917432: marked as done (bfgminer: Please switch Build-Depends to libsensors-dev from libsensors4-dev)

2019-01-04 Thread Debian Bug Tracking System
Your message dated Sat, 05 Jan 2019 00:19:34 + with message-id and subject line Bug#918313: Removed package(s) from unstable has caused the Debian Bug report #917432, regarding bfgminer: Please switch Build-Depends to libsensors-dev from libsensors4-dev to be marked as done. This means that

Bug#859351: marked as done (bfgminer shouldn't disable PIE)

2019-01-04 Thread Debian Bug Tracking System
Your message dated Sat, 05 Jan 2019 00:19:34 + with message-id and subject line Bug#918313: Removed package(s) from unstable has caused the Debian Bug report #859351, regarding bfgminer shouldn't disable PIE to be marked as done. This means that you claim that the problem has been dealt with.

Bug#899596: marked as done (libxfcegui4: Invalid maintainer address pkg-xfce-de...@lists.alioth.debian.org)

2019-01-04 Thread Debian Bug Tracking System
Your message dated Sat, 05 Jan 2019 00:19:06 + with message-id and subject line Bug#918199: Removed package(s) from unstable has caused the Debian Bug report #899596, regarding libxfcegui4: Invalid maintainer address pkg-xfce-de...@lists.alioth.debian.org to be marked as done. This means tha

Bug#876060: marked as done (vit's error messages makes its output blow up.)

2019-01-04 Thread Debian Bug Tracking System
Your message dated Fri, 04 Jan 2019 23:05:05 + with message-id and subject line Bug#876060: fixed in vit 1.3~beta1-1 has caused the Debian Bug report #876060, regarding vit's error messages makes its output blow up. to be marked as done. This means that you claim that the problem has been dea

Bug#910534: marked as done (adplug: CVE-2018-17825: several double-free vulnerabilities in the CEmuopl class in emuopl.cpp)

2019-01-04 Thread Debian Bug Tracking System
Your message dated Fri, 04 Jan 2019 22:49:16 + with message-id and subject line Bug#910534: fixed in adplug 2.2.1+dfsg3-1 has caused the Debian Bug report #910534, regarding adplug: CVE-2018-17825: several double-free vulnerabilities in the CEmuopl class in emuopl.cpp to be marked as done. T

Bug#895541: marked as done (doc-rfc autopkgtest broken, fixed by using Ghostscript's ps2txt instead of unmaintained pstotext)

2019-01-04 Thread Debian Bug Tracking System
Your message dated Fri, 04 Jan 2019 22:35:43 + with message-id and subject line Bug#895541: fixed in doc-rfc 20181229-2 has caused the Debian Bug report #895541, regarding doc-rfc autopkgtest broken, fixed by using Ghostscript's ps2txt instead of unmaintained pstotext to be marked as done. T

Bug#918249: marked as done (doc-rfc: please switch to ps2txt for testsuite)

2019-01-04 Thread Debian Bug Tracking System
Your message dated Fri, 04 Jan 2019 22:35:43 + with message-id and subject line Bug#918249: fixed in doc-rfc 20181229-2 has caused the Debian Bug report #918249, regarding doc-rfc: please switch to ps2txt for testsuite to be marked as done. This means that you claim that the problem has been

Bug#917116: marked as done (Buster: Salt Depends: python3-tornado (< 5) but 5.1.1-2 is to be installed)

2019-01-04 Thread Debian Bug Tracking System
Your message dated Sat, 5 Jan 2019 00:24:27 +0200 with message-id <20190104222427.GA25699@localhost> and subject line Re: Bug#917116: Buster: Salt Depends: python3-tornado (< 5) but 5.1.1-2 is to be installed has caused the Debian Bug report #917116, regarding Buster: Salt Depends: python3-tornado

Bug#918301: marked as done (libgdk-pixbuf2.0-dev: pkg-config reports version 2.10.14 when installed version is 2.36.5-2+deb9u2)

2019-01-04 Thread Debian Bug Tracking System
Your message dated Fri, 4 Jan 2019 17:20:59 -0500 with message-id and subject line Re: Bug#918301: libgdk-pixbuf2.0-dev: pkg-config reports version 2.10.14 when installed version is 2.36.5-2+deb9u2 has caused the Debian Bug report #918301, regarding libgdk-pixbuf2.0-dev: pkg-config reports versi

Bug#880534: marked as done (nbconvert: please add dependency “Suggests: python-nbconvert-doc”)

2019-01-04 Thread Debian Bug Tracking System
Your message dated Fri, 04 Jan 2019 21:50:42 + with message-id and subject line Bug#880534: fixed in nbconvert 5.4-1 has caused the Debian Bug report #880534, regarding nbconvert: please add dependency “Suggests: python-nbconvert-doc” to be marked as done. This means that you claim that the p

Bug#918247: marked as done (camlimages FTBFS on ocaml bytecode architectures)

2019-01-04 Thread Debian Bug Tracking System
Your message dated Fri, 04 Jan 2019 21:34:21 + with message-id and subject line Bug#918247: fixed in camlimages 1:4.2.6-2 has caused the Debian Bug report #918247, regarding camlimages FTBFS on ocaml bytecode architectures to be marked as done. This means that you claim that the problem has b

Bug#912790: marked as done (llvmlite: Please switch to llvm-toolchain-7)

2019-01-04 Thread Debian Bug Tracking System
Your message dated Fri, 04 Jan 2019 20:46:20 + with message-id and subject line Bug#912790: fixed in llvmlite 0.27.0-1 has caused the Debian Bug report #912790, regarding llvmlite: Please switch to llvm-toolchain-7 to be marked as done. This means that you claim that the problem has been deal

Bug#915502: marked as done (feedreader: Feedreader dies while updating feeds from a tt-rss instance)

2019-01-04 Thread Debian Bug Tracking System
Your message dated Fri, 04 Jan 2019 20:42:22 + with message-id and subject line Bug#915502: fixed in feedreader 2.6.1-1 has caused the Debian Bug report #915502, regarding feedreader: Feedreader dies while updating feeds from a tt-rss instance to be marked as done. This means that you claim

Bug#907057: marked as done (neverball: Constant fsync calls seriously degrade performance)

2019-01-04 Thread Debian Bug Tracking System
Your message dated Fri, 4 Jan 2019 21:32:28 +0100 with message-id <584be1fe-f40d-905a-83bf-29965b255...@debian.org> and subject line Re: neverball: Constant fsync calls seriously degrade performance has caused the Debian Bug report #907057, regarding neverball: Constant fsync calls seriously degra

Processed: ruby-actionpack-xml-parser: Depends: ruby-actionpack (< 2:5) but 2:5.2.0+dfsg-2 is to be installed

2019-01-04 Thread Debian Bug Tracking System
Processing control commands: > close -1 2.0.1-1 Bug #918265 [ruby-actionpack-xml-parser] ruby-actionpack-xml-parser: Depends: ruby-actionpack (< 2:5) but 2:5.2.0+dfsg-2 is to be installed Marked as fixed in versions ruby-actionpack-xml-parser/2.0.1-1. Bug #918265 [ruby-actionpack-xml-parser] ruby

Bug#704533: marked as done (claws-mail: force interrupting existing connections)

2019-01-04 Thread Debian Bug Tracking System
Your message dated Fri, 4 Jan 2019 21:03:46 +0100 with message-id <20190104210346.6d22098d@busgosu> and subject line Re: Bug#704533: claws-mail: force interrupting existing connections has caused the Debian Bug report #704533, regarding claws-mail: force interrupting existing connections to be mar

Bug#570006: marked as done (claws-mail: gtkcmctree.c:4556 Condition node != NULL failed)

2019-01-04 Thread Debian Bug Tracking System
Your message dated Fri, 4 Jan 2019 20:52:40 +0100 with message-id <20190104205240.766f4af4@busgosu> and subject line Re: Bug#570006: claws-mail: gtkcmctree.c:4556 Condition node != NULL failed has caused the Debian Bug report #570006, regarding claws-mail: gtkcmctree.c:4556 Condition node != NULL

Bug#908524: marked as done (pipewire: Section should not be “libs”)

2019-01-04 Thread Debian Bug Tracking System
Your message dated Fri, 04 Jan 2019 19:49:54 + with message-id and subject line Bug#908524: fixed in pipewire 0.2.5-1 has caused the Debian Bug report #908524, regarding pipewire: Section should not be “libs” to be marked as done. This means that you claim that the problem has been dealt with

Bug#505649: marked as done (claws-mail: setting messages marked skips messages)

2019-01-04 Thread Debian Bug Tracking System
Your message dated Fri, 4 Jan 2019 20:46:42 +0100 with message-id <20190104204642.7c17f523@busgosu> and subject line Re: Bug#505649: claws-mail: setting messages marked skips messages has caused the Debian Bug report #505649, regarding claws-mail: setting messages marked skips messages to be marke

Bug#917779: marked as done (groff FTCBFS: directory layout changed)

2019-01-04 Thread Debian Bug Tracking System
Your message dated Fri, 04 Jan 2019 19:35:00 + with message-id and subject line Bug#917779: fixed in groff 1.22.4-2 has caused the Debian Bug report #917779, regarding groff FTCBFS: directory layout changed to be marked as done. This means that you claim that the problem has been dealt with.

Bug#915278: marked as done (firetools FTCBFS: uses the wrong qmake)

2019-01-04 Thread Debian Bug Tracking System
Your message dated Fri, 04 Jan 2019 19:34:37 + with message-id and subject line Bug#915278: fixed in firetools 0.9.52-2 has caused the Debian Bug report #915278, regarding firetools FTCBFS: uses the wrong qmake to be marked as done. This means that you claim that the problem has been dealt wi

Processed: control

2019-01-04 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > unarchive 567934 Bug #567934 {Done: Debian FTP Masters } [emacs23] emacs23: segmentation fault in gtk libraries after closing emacsclient -c frame Unarchived Bug 567934 > reassign 604813 emacs23 Bug #604813 [emacs] Infrequent crashes with emacs

Bug#897604: marked as done (Broken AX_LIB_POSTGRESQL macro in sid?)

2019-01-04 Thread Debian Bug Tracking System
Your message dated Fri, 04 Jan 2019 18:34:09 + with message-id and subject line Bug#897604: fixed in autoconf-archive 20180313-1 has caused the Debian Bug report #897604, regarding Broken AX_LIB_POSTGRESQL macro in sid? to be marked as done. This means that you claim that the problem has been

Bug#905392: marked as done (openvpn: systemd generator ignores overrides in /etc/systemd/system)

2019-01-04 Thread Debian Bug Tracking System
Your message dated Fri, 4 Jan 2019 19:19:19 +0100 with message-id and subject line Fixed has caused the Debian Bug report #905392, regarding openvpn: systemd generator ignores overrides in /etc/systemd/system to be marked as done. This means that you claim that the problem has been dealt with. If

Bug#918230: marked as done (python-django: CVE-2019-3498: Content spoofing possibility in the default 404 page)

2019-01-04 Thread Debian Bug Tracking System
Your message dated Fri, 04 Jan 2019 18:06:43 + with message-id and subject line Bug#918230: fixed in python-django 2:2.1.5-1 has caused the Debian Bug report #918230, regarding python-django: CVE-2019-3498: Content spoofing possibility in the default 404 page to be marked as done. This means

Bug#918243: marked as done (icinga2.6: Deadlocks when icinga2 is reloaded)

2019-01-04 Thread Debian Bug Tracking System
Your message dated Fri, 4 Jan 2019 18:48:50 +0100 with message-id <65ada690-e605-71d7-1e37-dbc2c8195...@xs4all.nl> and subject line Re: [Pkg-nagios-devel] Bug#918243: icinga2.6: Deadlocks when icinga2 is reloaded has caused the Debian Bug report #918243, regarding icinga2.6: Deadlocks when icinga2

Bug#918230: marked as done (python-django: CVE-2019-3498: Content spoofing possibility in the default 404 page)

2019-01-04 Thread Debian Bug Tracking System
Your message dated Fri, 04 Jan 2019 17:35:51 + with message-id and subject line Bug#918230: fixed in python-django 1:1.11.18-1 has caused the Debian Bug report #918230, regarding python-django: CVE-2019-3498: Content spoofing possibility in the default 404 page to be marked as done. This mea

Bug#918240: marked as done (python3-django-hyperkitty: please backport to stretch)

2019-01-04 Thread Debian Bug Tracking System
Your message dated Fri, 4 Jan 2019 18:09:43 +0100 with message-id <1296b558-57ef-22c4-7cf5-cd3f329cc...@freesources.org> and subject line Re: [Pkg-mailman-hackers] Bug#918240: python3-django-hyperkitty: please backport to stretch has caused the Debian Bug report #918240, regarding python3-django-h

Bug#918121: marked as done (libgazebo9-dev: gazebo.pc has broken link flags)

2019-01-04 Thread Debian Bug Tracking System
Your message dated Fri, 04 Jan 2019 17:35:11 + with message-id and subject line Bug#918128: fixed in gazebo 9.6.0-1 has caused the Debian Bug report #918128, regarding libgazebo9-dev: gazebo.pc has broken link flags to be marked as done. This means that you claim that the problem has been dea

Bug#918128: marked as done (gazebo: autopkgtest fails due to invalid gazebo.pc)

2019-01-04 Thread Debian Bug Tracking System
Your message dated Fri, 04 Jan 2019 17:35:11 + with message-id and subject line Bug#918128: fixed in gazebo 9.6.0-1 has caused the Debian Bug report #918128, regarding gazebo: autopkgtest fails due to invalid gazebo.pc to be marked as done. This means that you claim that the problem has been

Bug#917959: marked as done (octave: segfault on complex dot product)

2019-01-04 Thread Debian Bug Tracking System
Your message dated Fri, 04 Jan 2019 18:21:17 +0100 with message-id <1546622477.3311.16.ca...@debian.org> and subject line Re: Bug#917959: octave: segfault on complex dot product has caused the Debian Bug report #917959, regarding octave: segfault on complex dot product to be marked as done. This m

Bug#909123: marked as done (ruby-active-model-serializers: /usr/bin/rubocop is already shipped by the rubocop package)

2019-01-04 Thread Debian Bug Tracking System
Your message dated Fri, 04 Jan 2019 17:20:54 + with message-id and subject line Bug#909123: fixed in ruby-active-model-serializers 0.10.8-1 has caused the Debian Bug report #909123, regarding ruby-active-model-serializers: /usr/bin/rubocop is already shipped by the rubocop package to be marke

Bug#802213: marked as done (node-postgres: FTBFS: error: expected class-name before '{' token)

2019-01-04 Thread Debian Bug Tracking System
Your message dated Fri, 04 Jan 2019 17:05:28 + with message-id and subject line Bug#802213: fixed in node-postgres 7.7.1-1 has caused the Debian Bug report #802213, regarding node-postgres: FTBFS: error: expected class-name before '{' token to be marked as done. This means that you claim that

Bug#884351: marked as done (UDD: outdated TODO about bpo uploads)

2019-01-04 Thread Debian Bug Tracking System
Your message dated Fri, 4 Jan 2019 17:24:01 +0100 with message-id <20190104162401.ccna3yjlme3wt...@xanadu.blop.info> and subject line Re: Bug#884351: UDD: outdated TODO about bpo uploads has caused the Debian Bug report #884351, regarding UDD: outdated TODO about bpo uploads to be marked as done.

Bug#824222: marked as done ([debian-refcard] change build mechanism to dblatex for ar, ml)

2019-01-04 Thread Debian Bug Tracking System
Your message dated Fri, 4 Jan 2019 17:33:28 +0100 with message-id <20190104173328.a4a54964c3269f82d7312...@mailbox.org> and subject line Re: Bug#824222: [debian-refcard] change build mechanism to dblatex for ar, hi, ml has caused the Debian Bug report #824222, regarding [debian-refcard] change bui

Bug#916282: marked as done (m_inmail: $INMAIL_DB is ignored)

2019-01-04 Thread Debian Bug Tracking System
Your message dated Fri, 04 Jan 2019 16:35:51 + with message-id and subject line Bug#916282: fixed in lbdb 0.48 has caused the Debian Bug report #916282, regarding m_inmail: $INMAIL_DB is ignored to be marked as done. This means that you claim that the problem has been dealt with. If this is n

Bug#897230: marked as done (qa.debian.org: the instructions for UDD development do not work)

2019-01-04 Thread Debian Bug Tracking System
Your message dated Fri, 4 Jan 2019 17:14:18 +0100 with message-id <20190104161418.taj2y4cr3wtb6...@xanadu.blop.info> and subject line Re: Bug#897230: qa.debian.org: the instructions for UDD development do not work has caused the Debian Bug report #897230, regarding qa.debian.org: the instructions

Processed: closing 886273

2019-01-04 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > close 886273 Bug #886273 [qa.debian.org] UDD: database table popcon_src no longer being updated Marked Bug as done > thanks Stopping processing here. Please contact me if you need assistance. -- 886273: https://bugs.debian.org/cgi-bin/bugreport

Bug#748879: marked as done (claws-mail: Not accepting cross-domain SSL certificates)

2019-01-04 Thread Debian Bug Tracking System
Your message dated Fri, 4 Jan 2019 17:11:27 +0100 with message-id <20190104171127.77982106@busgosu> and subject line Re: Bug#748879: claws-mail: Not accepting cross-domain SSL certificates has caused the Debian Bug report #748879, regarding claws-mail: Not accepting cross-domain SSL certificates t

Bug#918224: marked as done (ITP: ruby-mini-mime: A lightweight mime type implementation)

2019-01-04 Thread Debian Bug Tracking System
Your message dated Fri, 04 Jan 2019 16:00:09 + with message-id and subject line Bug#918224: fixed in ruby-mini-mime 1.0.1-1 has caused the Debian Bug report #918224, regarding ITP: ruby-mini-mime: A lightweight mime type implementation to be marked as done. This means that you claim that the

Bug#917469: marked as done (qa.debian.org: [UDD] Please import migration status and provide it as a(n optional) column in bugs cgi)

2019-01-04 Thread Debian Bug Tracking System
Your message dated Fri, 4 Jan 2019 16:45:15 +0100 with message-id <20190104154515.n7udm4utioa26...@xanadu.blop.info> and subject line Re: Bug#917469: qa.debian.org: Please import migration status and provide it as a(n optional) column in bugs cgi has caused the Debian Bug report #917469, regarding

Bug#702843: marked as done (claws-mail-bogofilter: Does not add X-Bogosity header when that option checked in preferences)

2019-01-04 Thread Debian Bug Tracking System
Your message dated Fri, 4 Jan 2019 16:59:09 +0100 with message-id <20190104165909.7060f22c@busgosu> and subject line Re: Bug#702843: claws-mail-bogofilter: Does not add X-Bogosity header when that option checked in preferences has caused the Debian Bug report #702843, regarding claws-mail-bogofil

Bug#918232: marked as done (Cloud-init not setting public key on Azure portal when creating a virtual machine instance)

2019-01-04 Thread Debian Bug Tracking System
Your message dated Fri, 4 Jan 2019 16:29:13 +0100 with message-id <20190104152913.5a7oan4ntg3hk...@shell.thinkmo.de> and subject line Re: Bug#918232: Cloud-init not setting public key on Azure portal when creating a virtual machine instance has caused the Debian Bug report #918232, regarding Cloud

Bug#877781: marked as done (backup-manager: Please ship user manual)

2019-01-04 Thread Debian Bug Tracking System
Your message dated Fri, 4 Jan 2019 12:17:40 -0300 with message-id <20190104151739.up3kv5hqwrkub...@neoptolemo.gnuservers.com.ar> and subject line Re: Bug#877781: backup-manager: Please ship user manual has caused the Debian Bug report #877781, regarding backup-manager: Please ship user manual to be

Bug#915150: marked as done (gzip FTBFS: ../../lib/fseeko.c:110:4: error: #error "Please port gnulib fseeko.c to your platform! Look at the code in fseeko.c, then report this to bug-gnulib.")

2019-01-04 Thread Debian Bug Tracking System
Your message dated Fri, 04 Jan 2019 15:04:47 + with message-id and subject line Bug#915150: fixed in gzip 1.9-2.2 has caused the Debian Bug report #915150, regarding gzip FTBFS: ../../lib/fseeko.c:110:4: error: #error "Please port gnulib fseeko.c to your platform! Look at the code in fseeko.c

Bug#888619: marked as done (gzip: please add Homepage field)

2019-01-04 Thread Debian Bug Tracking System
Your message dated Fri, 04 Jan 2019 15:04:47 + with message-id and subject line Bug#888619: fixed in gzip 1.9-2.2 has caused the Debian Bug report #888619, regarding gzip: please add Homepage field to be marked as done. This means that you claim that the problem has been dealt with. If this i

Bug#914907: marked as done (gzip: reproducible build (usrmerge): zgrep embeds path of grep found via PATH)

2019-01-04 Thread Debian Bug Tracking System
Your message dated Fri, 04 Jan 2019 15:04:47 + with message-id and subject line Bug#914907: fixed in gzip 1.9-2.2 has caused the Debian Bug report #914907, regarding gzip: reproducible build (usrmerge): zgrep embeds path of grep found via PATH to be marked as done. This means that you claim

Bug#917465: marked as done (aplpy: autopkgtest needs update for new version of python-numpy)

2019-01-04 Thread Debian Bug Tracking System
Your message dated Fri, 04 Jan 2019 14:46:27 + with message-id and subject line Bug#917465: fixed in aplpy 2.0~rc2-1 has caused the Debian Bug report #917465, regarding aplpy: autopkgtest needs update for new version of python-numpy to be marked as done. This means that you claim that the pro

Bug#916980: marked as done (flash-kernel: Please support Hardkernel's Odroid HC1/HC2 boards)

2019-01-04 Thread Debian Bug Tracking System
Your message dated Fri, 04 Jan 2019 14:47:11 + with message-id and subject line Bug#916980: fixed in flash-kernel 3.97 has caused the Debian Bug report #916980, regarding flash-kernel: Please support Hardkernel's Odroid HC1/HC2 boards to be marked as done. This means that you claim that the p

Bug#917798: marked as done (hashrat: FTBFS because of Makefile bug)

2019-01-04 Thread Debian Bug Tracking System
Your message dated Fri, 04 Jan 2019 14:48:02 + with message-id and subject line Bug#917798: fixed in hashrat 1.10.2-2 has caused the Debian Bug report #917798, regarding hashrat: FTBFS because of Makefile bug to be marked as done. This means that you claim that the problem has been dealt with

Bug#918193: marked as done (flash-kernel: add Seagate Blackarmor NAS220 to machine db)

2019-01-04 Thread Debian Bug Tracking System
Your message dated Fri, 04 Jan 2019 14:47:11 + with message-id and subject line Bug#918193: fixed in flash-kernel 3.97 has caused the Debian Bug report #918193, regarding flash-kernel: add Seagate Blackarmor NAS220 to machine db to be marked as done. This means that you claim that the problem

Processed: Merging bug

2019-01-04 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > reassign 918215 python3-skimage Bug #918215 [src:skimage] skimage: autopkgtest fails with python-numpy (1:1.16.0~rc1-3) Bug reassigned from package 'src:skimage' to 'python3-skimage'. No longer marked as found in versions skimage/0.14.1-2. Ignori

Bug#904240: marked as done (RFA: flycheck -- modern on-the-fly syntax checking for Emacs)

2019-01-04 Thread Debian Bug Tracking System
Your message dated Fri, 04 Jan 2019 13:49:23 + with message-id and subject line Bug#904240: fixed in flycheck 31-2 has caused the Debian Bug report #904240, regarding RFA: flycheck -- modern on-the-fly syntax checking for Emacs to be marked as done. This means that you claim that the problem

Bug#918133: marked as done (O: aalib -- ASCII art library)

2019-01-04 Thread Debian Bug Tracking System
Your message dated Fri, 04 Jan 2019 13:49:08 + with message-id and subject line Bug#918133: fixed in aalib 1.4p5-45 has caused the Debian Bug report #918133, regarding O: aalib -- ASCII art library to be marked as done. This means that you claim that the problem has been dealt with. If this i

Bug#917057: marked as done (libpolyclipping-dev: pkg-config file contains bogus includedir)

2019-01-04 Thread Debian Bug Tracking System
Your message dated Fri, 04 Jan 2019 13:39:14 + with message-id and subject line Bug#917057: fixed in libpolyclipping 6.4.2-6 has caused the Debian Bug report #917057, regarding libpolyclipping-dev: pkg-config file contains bogus includedir to be marked as done. This means that you claim that

Bug#917687: marked as done (cura-engine: FTBFS: ./obj-x86_64-linux-gnu/CMakeFiles/CMakeTmp/./obj-x86_64-linux-gnu/CMakeFiles/CMakeTmp/CheckSymbolExists.c:8: undefined reference to `pthread_create')

2019-01-04 Thread Debian Bug Tracking System
Your message dated Fri, 04 Jan 2019 13:39:14 + with message-id and subject line Bug#917057: fixed in libpolyclipping 6.4.2-6 has caused the Debian Bug report #917057, regarding cura-engine: FTBFS: ./obj-x86_64-linux-gnu/CMakeFiles/CMakeTmp/./obj-x86_64-linux-gnu/CMakeFiles/CMakeTmp/CheckSymbo

Bug#918203: marked as done (ccdproc: autopkgtest fails with python-numpy (1:1.16.0~rc1-3))

2019-01-04 Thread Debian Bug Tracking System
Your message dated Fri, 4 Jan 2019 13:59:57 +0100 with message-id and subject line Closing this bug has caused the Debian Bug report #917466, regarding ccdproc: autopkgtest fails with python-numpy (1:1.16.0~rc1-3) to be marked as done. This means that you claim that the problem has been dealt wit

Bug#918216: marked as done (sunpy: autopkgtest fails with python-numpy (1:1.16.0~rc1-3))

2019-01-04 Thread Debian Bug Tracking System
Your message dated Fri, 4 Jan 2019 13:59:57 +0100 with message-id and subject line Closing this bug has caused the Debian Bug report #917466, regarding sunpy: autopkgtest fails with python-numpy (1:1.16.0~rc1-3) to be marked as done. This means that you claim that the problem has been dealt with.

Bug#918200: marked as done (astropy: autopkgtest fails with python-numpy (1:1.16.0~rc1-3))

2019-01-04 Thread Debian Bug Tracking System
Your message dated Fri, 4 Jan 2019 13:59:57 +0100 with message-id and subject line Closing this bug has caused the Debian Bug report #917466, regarding astropy: autopkgtest fails with python-numpy (1:1.16.0~rc1-3) to be marked as done. This means that you claim that the problem has been dealt wit

Bug#918205: marked as done (hipspy: autopkgtest fails with python-numpy (1:1.16.0~rc1-3))

2019-01-04 Thread Debian Bug Tracking System
Your message dated Fri, 4 Jan 2019 13:59:57 +0100 with message-id and subject line Closing this bug has caused the Debian Bug report #917466, regarding hipspy: autopkgtest fails with python-numpy (1:1.16.0~rc1-3) to be marked as done. This means that you claim that the problem has been dealt with

Bug#917466: marked as done (python-numpy breaks astropy autopkgtest)

2019-01-04 Thread Debian Bug Tracking System
Your message dated Fri, 4 Jan 2019 13:59:57 +0100 with message-id and subject line Closing this bug has caused the Debian Bug report #917466, regarding python-numpy breaks astropy autopkgtest to be marked as done. This means that you claim that the problem has been dealt with. If this is not the

Processed: Merge duplicated bug reports

2019-01-04 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > reassign 917466 src:astropy Bug #917466 {Done: Ole Streicher } [src:python-numpy, src:astropy] python-numpy breaks astropy autopkgtest Bug reassigned from package 'src:python-numpy, src:astropy' to 'src:astropy'. No longer marked as found in vers

Bug#917983: marked as done (glib2.0: [experimental] FTBFS on arm64: tests/refcount/closures.c:298:main: assertion failed: (seen_thread2 != FALSE))

2019-01-04 Thread Debian Bug Tracking System
Your message dated Fri, 04 Jan 2019 12:04:21 + with message-id and subject line Bug#917983: fixed in glib2.0 2.58.2-3 has caused the Debian Bug report #917983, regarding glib2.0: [experimental] FTBFS on arm64: tests/refcount/closures.c:298:main: assertion failed: (seen_thread2 != FALSE) to be

Bug#908334: marked as done (glib2.0 FTCBFS: fatal error: testmarshal.h: No such file or directory)

2019-01-04 Thread Debian Bug Tracking System
Your message dated Fri, 04 Jan 2019 12:04:21 + with message-id and subject line Bug#908334: fixed in glib2.0 2.58.2-3 has caused the Debian Bug report #908334, regarding glib2.0 FTCBFS: fatal error: testmarshal.h: No such file or directory to be marked as done. This means that you claim that

Bug#775854: marked as done (glib2.0: Useless removal and regeneration of cached data)

2019-01-04 Thread Debian Bug Tracking System
Your message dated Fri, 04 Jan 2019 12:04:21 + with message-id and subject line Bug#775854: fixed in glib2.0 2.58.2-3 has caused the Debian Bug report #775854, regarding glib2.0: Useless removal and regeneration of cached data to be marked as done. This means that you claim that the problem h

Bug#917980: marked as done (glib2.0: [experimental] FTBFS on s390x: glib/gvariant-serialiser.c:174:g_variant_serialised_check: assertion failed (alignment & (gsize) serialised.data == 0): (4 == 0))

2019-01-04 Thread Debian Bug Tracking System
Your message dated Fri, 04 Jan 2019 12:04:21 + with message-id and subject line Bug#917980: fixed in glib2.0 2.58.2-3 has caused the Debian Bug report #917980, regarding glib2.0: [experimental] FTBFS on s390x: glib/gvariant-serialiser.c:174:g_variant_serialised_check: assertion failed (align

Bug#916847: marked as done (ITP: silkaj -- command-line client for Duniter)

2019-01-04 Thread Debian Bug Tracking System
Your message dated Fri, 04 Jan 2019 12:00:11 + with message-id and subject line Bug#916847: fixed in silkaj 0.6.1-1 has caused the Debian Bug report #916847, regarding ITP: silkaj -- command-line client for Duniter to be marked as done. This means that you claim that the problem has been deal

Bug#892561: marked as done (ruby-session: FTBFS and Debci failure with ruby 2.5)

2019-01-04 Thread Debian Bug Tracking System
Your message dated Fri, 04 Jan 2019 11:49:01 + with message-id and subject line Bug#892561: fixed in ruby-session 3.2.0-3 has caused the Debian Bug report #892561, regarding ruby-session: FTBFS and Debci failure with ruby 2.5 to be marked as done. This means that you claim that the problem ha

Bug#918219: marked as done (nagios3-cgi: postinst script fails if supplied apache config has been deleted previously)

2019-01-04 Thread Debian Bug Tracking System
Your message dated Fri, 4 Jan 2019 12:43:47 +0100 with message-id <593030f8-dcc9-8233-354a-7f2fc770e...@xs4all.nl> and subject line Re: [Pkg-nagios-devel] Bug#918219: nagios3-cgi: postinst script fails if supplied apache config has been deleted previously has caused the Debian Bug report #918219,

Bug#905470: marked as done (0ad: Alpha 23 Lobby lag and other multiplayer issues)

2019-01-04 Thread Debian Bug Tracking System
Your message dated Fri, 04 Jan 2019 11:19:47 + with message-id and subject line Bug#905470: fixed in 0ad 0.0.23.1-1 has caused the Debian Bug report #905470, regarding 0ad: Alpha 23 Lobby lag and other multiplayer issues to be marked as done. This means that you claim that the problem has bee

Bug#918050: marked as done (iv doesn't do anything)

2019-01-04 Thread Debian Bug Tracking System
Your message dated Fri, 04 Jan 2019 12:33:05 +0100 with message-id <87ftu864jy.fsf@localhost> and subject line Re: Bug#918050: iv doesn't do anything has caused the Debian Bug report #918050, regarding iv doesn't do anything to be marked as done. This means that you claim that the problem has been

Bug#898013: marked as done (lua-redis: Not compatible with lua5.3)

2019-01-04 Thread Debian Bug Tracking System
Your message dated Fri, 04 Jan 2019 11:25:00 + with message-id and subject line Bug#898013: fixed in lua-redis 2.0.5~git20141117.880dda9-2 has caused the Debian Bug report #898013, regarding lua-redis: Not compatible with lua5.3 to be marked as done. This means that you claim that the problem

Bug#898755: marked as done (node-miller-rabin: FTBFS and flaky autopkgtests)

2019-01-04 Thread Debian Bug Tracking System
Your message dated Fri, 04 Jan 2019 11:25:23 + with message-id and subject line Bug#898755: fixed in node-miller-rabin 4.0.1-2 has caused the Debian Bug report #898755, regarding node-miller-rabin: FTBFS and flaky autopkgtests to be marked as done. This means that you claim that the problem h

Bug#892658: marked as done (node-ip FTBFS with mocha 4.0.1-3)

2019-01-04 Thread Debian Bug Tracking System
Your message dated Fri, 04 Jan 2019 11:25:18 + with message-id and subject line Bug#892658: fixed in node-ip 1.1.5-2 has caused the Debian Bug report #892658, regarding node-ip FTBFS with mocha 4.0.1-3 to be marked as done. This means that you claim that the problem has been dealt with. If th

Bug#898755: marked as done (node-miller-rabin: FTBFS and flaky autopkgtests)

2019-01-04 Thread Debian Bug Tracking System
Your message dated Fri, 04 Jan 2019 11:25:29 + with message-id and subject line Bug#898755: fixed in node-miller-rabin 4.0.1-3 has caused the Debian Bug report #898755, regarding node-miller-rabin: FTBFS and flaky autopkgtests to be marked as done. This means that you claim that the problem h

Bug#888820: marked as done (ITP: nss-pem -- PEM file reader for Network Security Services (NSS))

2019-01-04 Thread Debian Bug Tracking System
Your message dated Fri, 04 Jan 2019 10:10:13 + with message-id and subject line Bug#20: fixed in nss-pem 1.0.4-1 has caused the Debian Bug report #20, regarding ITP: nss-pem -- PEM file reader for Network Security Services (NSS) to be marked as done. This means that you claim that the

Bug#917042: marked as done (dtfabric: Wrong name)

2019-01-04 Thread Debian Bug Tracking System
Your message dated Fri, 04 Jan 2019 10:10:11 + with message-id and subject line Bug#917042: fixed in dtfabric 20180808-1.1 has caused the Debian Bug report #917042, regarding dtfabric: Wrong name to be marked as done. This means that you claim that the problem has been dealt with. If this is

Bug#640303: marked as done (pdfminer: please provide a python3 version)

2019-01-04 Thread Debian Bug Tracking System
Your message dated Fri, 04 Jan 2019 10:10:13 + with message-id and subject line Bug#640303: fixed in pdfminer 20181108+dfsg-1~exp1 has caused the Debian Bug report #640303, regarding pdfminer: please provide a python3 version to be marked as done. This means that you claim that the problem ha

Bug#870469: marked as done (Should use a fork of pdfminer)

2019-01-04 Thread Debian Bug Tracking System
Your message dated Fri, 04 Jan 2019 10:10:13 + with message-id and subject line Bug#870469: fixed in pdfminer 20181108+dfsg-1~exp1 has caused the Debian Bug report #870469, regarding Should use a fork of pdfminer to be marked as done. This means that you claim that the problem has been dealt

Bug#912945: marked as done (ITP: egl-wayland -- Wayland EGL External Platform library)

2019-01-04 Thread Debian Bug Tracking System
Your message dated Fri, 04 Jan 2019 10:10:11 + with message-id and subject line Bug#912945: fixed in egl-wayland 1:1.1.1-1 has caused the Debian Bug report #912945, regarding ITP: egl-wayland -- Wayland EGL External Platform library to be marked as done. This means that you claim that the pro

Bug#913081: marked as done (liblouis FTCBFS: python* Build-Depends unsatisfiable)

2019-01-04 Thread Debian Bug Tracking System
Your message dated Fri, 04 Jan 2019 10:10:12 + with message-id and subject line Bug#913081: fixed in liblouis 3.8.0-1 has caused the Debian Bug report #913081, regarding liblouis FTCBFS: python* Build-Depends unsatisfiable to be marked as done. This means that you claim that the problem has b

Processed: closing 870282

2019-01-04 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > close 870282 Bug #870282 [firefox] Firefox: A11Y AT-SPI non standart event for caret-moved (not including detail1 caret offset) Marked Bug as done > thanks Stopping processing here. Please contact me if you need assistance. -- 870282: https://b

Bug#690412: marked as done (prosody: Reload TLS/SSL Certificates on SIGHUP)

2019-01-04 Thread Debian Bug Tracking System
Your message dated Fri, 4 Jan 2019 11:01:34 +0100 with message-id and subject line Re: prosody: Reload TLS/SSL Certificates on SIGHUP has caused the Debian Bug report #690412, regarding prosody: Reload TLS/SSL Certificates on SIGHUP to be marked as done. This means that you claim that the proble

Bug#916316: marked as done (please backport to stretch (for prosody))

2019-01-04 Thread Debian Bug Tracking System
Your message dated Fri, 4 Jan 2019 10:56:11 +0100 with message-id and subject line Re: please backport to stretch (for prosody) has caused the Debian Bug report #916316, regarding please backport to stretch (for prosody) to be marked as done. This means that you claim that the problem has been d

  1   2   >