Bug#778750: marked as done (php-horde: themes should be managed via /etc)

Your message dated Tue, 30 Jun 2020 05:48:32 + with message-id and subject line Bug#778750: fixed in php-horde 5.2.23+debian0-1 has caused the Debian Bug report #778750, regarding php-horde: themes should be managed via /etc to be marked as done. This means that you claim that the problem has

Bug#725001: marked as done (/usr/share/horde/.htaccess should be a symlink and point to e.g. /etc/horde/site_htaccess)

Your message dated Tue, 30 Jun 2020 05:48:32 + with message-id and subject line Bug#725001: fixed in php-horde 5.2.23+debian0-1 has caused the Debian Bug report #725001, regarding /usr/share/horde/.htaccess should be a symlink and point to e.g. /etc/horde/site_htaccess to be marked as done.

Bug#942905: marked as done (alsa-utils: Python2 removal in sid/bullseye)

Your message dated Tue, 30 Jun 2020 05:48:24 + with message-id and subject line Bug#942905: fixed in alsa-utils 1.2.2-2 has caused the Debian Bug report #942905, regarding alsa-utils: Python2 removal in sid/bullseye to be marked as done. This means that you claim that the problem has been dea

Bug#962073: marked as done (alsa-info is calling home without asking)

Your message dated Tue, 30 Jun 2020 05:48:24 + with message-id and subject line Bug#962073: fixed in alsa-utils 1.2.2-2 has caused the Debian Bug report #962073, regarding alsa-info is calling home without asking to be marked as done. This means that you claim that the problem has been dealt

Bug#953489: marked as done (php-horde-text-filter-jsmin: binaries for non-free not auto-built)

Your message dated Tue, 30 Jun 2020 05:48:37 + with message-id and subject line Bug#953489: fixed in php-horde-text-filter-jsmin 1.0.2-8 has caused the Debian Bug report #953489, regarding php-horde-text-filter-jsmin: binaries for non-free not auto-built to be marked as done. This means that

Bug#963809: marked as done (php-horde: CVE-2020-8035)

Your message dated Tue, 30 Jun 2020 05:48:32 + with message-id and subject line Bug#963809: fixed in php-horde 5.2.23+debian0-1 has caused the Debian Bug report #963809, regarding php-horde: CVE-2020-8035 to be marked as done. This means that you claim that the problem has been dealt with. If

Bug#924187: marked as done (kdiff3-doc: broken symlinks: /usr/share/doc/kdiff3-doc/html/*.png -> ../../kde/HTML/en/kdiff3/*.png)

Your message dated Tue, 30 Jun 2020 05:33:28 + with message-id and subject line Bug#924187: fixed in kdiff3 1.8.01-2 has caused the Debian Bug report #924187, regarding kdiff3-doc: broken symlinks: /usr/share/doc/kdiff3-doc/html/*.png -> ../../kde/HTML/en/kdiff3/*.png to be marked as done. T

Bug#932887: marked as done (kdiff3: Missing translations)

Your message dated Tue, 30 Jun 2020 05:33:28 + with message-id and subject line Bug#932887: fixed in kdiff3 1.8.01-2 has caused the Debian Bug report #932887, regarding kdiff3: Missing translations to be marked as done. This means that you claim that the problem has been dealt with. If this i

Processed: your mail

Processing commands for cont...@bugs.debian.org: > forcemerge 963035 963080 963601 963894 963963 Bug #963035 {Done: Michael Gilbert } [src:chromium] ffmpeg: 4.3 breaks chromium Bug #963894 {Done: Michael Gilbert } [src:chromium] Chromium: Error "Aw, Snap! Something went wrong while displaying th

Processed: your mail

Processing commands for cont...@bugs.debian.org: > reassign 963894 src:chromium Bug #963894 [chromium] Chromium: Error "Aw, Snap! Something went wrong while displaying this webpage. Error code 256." Bug reassigned from package 'chromium' to 'src:chromium'. No longer marked as found in versions ch

Bug#952041: marked as done (ruby-hoe: FTBFS: ERROR: Test "ruby2.7" failed.)

Your message dated Mon, 29 Jun 2020 22:49:50 + with message-id and subject line Bug#952041: fixed in ruby-hoe 3.22.1+dfsg1-2 has caused the Debian Bug report #952041, regarding ruby-hoe: FTBFS: ERROR: Test "ruby2.7" failed. to be marked as done. This means that you claim that the problem has

Bug#934374: marked as done (de4dot: FTBFS in sid (failing tests))

Your message dated Mon, 29 Jun 2020 21:33:32 + with message-id and subject line Bug#934374: fixed in de4dot 3.1.41592.3405-2 has caused the Debian Bug report #934374, regarding de4dot: FTBFS in sid (failing tests) to be marked as done. This means that you claim that the problem has been dealt

Bug#962995: marked as done (testssl.sh: missing dependencies)

Your message dated Mon, 29 Jun 2020 21:20:51 + with message-id and subject line Bug#962995: fixed in testssl.sh 3.0.2+dfsg1-2 has caused the Debian Bug report #962995, regarding testssl.sh: missing dependencies to be marked as done. This means that you claim that the problem has been dealt wi

Bug#957619: marked as done (nx-libs: ftbfs with GCC-10)

Your message dated Mon, 29 Jun 2020 21:05:21 + with message-id and subject line Bug#957619: fixed in nx-libs 2:3.5.99.24-1 has caused the Debian Bug report #957619, regarding nx-libs: ftbfs with GCC-10 to be marked as done. This means that you claim that the problem has been dealt with. If th

Bug#913662: marked as done (Switch default backend to nftables)

Your message dated Mon, 29 Jun 2020 23:03:09 +0200 with message-id and subject line Re: Switch default backend to nftables has caused the Debian Bug report #913662, regarding Switch default backend to nftables to be marked as done. This means that you claim that the problem has been dealt with. I

Bug#963983: marked as done (python3-pyside2.qtsvg: segfault on import)

Your message dated Mon, 29 Jun 2020 22:47:16 +0200 with message-id <06b2b72f-daee-0815-789c-6f89fc2e6...@debian.org> and subject line Re: python3-pyside2.qtsvg: segfault on import has caused the Debian Bug report #963983, regarding python3-pyside2.qtsvg: segfault on import to be marked as done. Th

Bug#963726: marked as done (projectm-data needs Breaks+Replaces: libprojectm2v5)

Your message dated Mon, 29 Jun 2020 20:49:48 + with message-id and subject line Bug#963726: fixed in projectm 3.1.3-2 has caused the Debian Bug report #963726, regarding projectm-data needs Breaks+Replaces: libprojectm2v5 to be marked as done. This means that you claim that the problem has be

Bug#961443: marked as done (buster-pu: package perl/5.28.3)

Your message dated Mon, 29 Jun 2020 21:34:07 +0100 with message-id <20200629203407.ootmlksceql6a...@urchin.earth.li> and subject line Re: Bug#961443: buster-pu: package perl/5.28.2 has caused the Debian Bug report #961443, regarding buster-pu: package perl/5.28.3 to be marked as done. This means t

Bug#961827: marked as done (please add openssl-rsync script for use of encrypted rsync over TLS)

Your message dated Mon, 29 Jun 2020 20:19:12 +0100 with message-id and subject line please add openssl-rsync script for use of encrypted rsync over TLS has caused the Debian Bug report #961827, regarding please add openssl-rsync script for use of encrypted rsync over TLS to be marked as done. T

Bug#957878: marked as done (tightvnc: ftbfs with GCC-10)

Your message dated Mon, 29 Jun 2020 19:03:32 + with message-id and subject line Bug#957878: fixed in tightvnc 1:1.3.9-10 has caused the Debian Bug report #957878, regarding tightvnc: ftbfs with GCC-10 to be marked as done. This means that you claim that the problem has been dealt with. If thi

Bug#853117: marked as done (tightvnc FTBFS on mips*: PIE / stipmips.s problem)

Your message dated Mon, 29 Jun 2020 19:03:32 + with message-id and subject line Bug#853117: fixed in tightvnc 1:1.3.9-10 has caused the Debian Bug report #853117, regarding tightvnc FTBFS on mips*: PIE / stipmips.s problem to be marked as done. This means that you claim that the problem has b

Bug#586413: marked as done (ITA: tightvnc -- virtual network computing server)

Your message dated Mon, 29 Jun 2020 19:03:32 + with message-id and subject line Bug#586413: fixed in tightvnc 1:1.3.9-10 has caused the Debian Bug report #586413, regarding ITA: tightvnc -- virtual network computing server to be marked as done. This means that you claim that the problem has b

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

Your message dated Mon, 29 Jun 2020 18:48:47 + with message-id and subject line Bug#938992: fixed in glewlwyd 2.3.1-2 has caused the Debian Bug report #938992, regarding glewlwyd: [INTL:pt_BR] Brazilian Portuguese debconf templates translation to be marked as done. This means that you claim

Bug#963717: marked as done (aerc embeds build path and can't find config files)

Your message dated Mon, 29 Jun 2020 18:48:36 + with message-id and subject line Bug#963717: fixed in aerc 0.3.0-2 has caused the Debian Bug report #963717, regarding aerc embeds build path and can't find config files to be marked as done. This means that you claim that the problem has been de

Bug#957274: marked as done (glewlwyd: ftbfs with GCC-10)

Your message dated Mon, 29 Jun 2020 18:48:47 + with message-id and subject line Bug#957274: fixed in glewlwyd 2.3.1-2 has caused the Debian Bug report #957274, regarding glewlwyd: ftbfs with GCC-10 to be marked as done. This means that you claim that the problem has been dealt with. If this i

Bug#956700: marked as done (kvirc: Please witch to enchant-2 instead of enchant(1))

Your message dated Mon, 29 Jun 2020 18:18:39 + with message-id and subject line Bug#956700: fixed in kvirc 4:5.0.0+dfsg-3 has caused the Debian Bug report #956700, regarding kvirc: Please witch to enchant-2 instead of enchant(1) to be marked as done. This means that you claim that the proble

Bug#960985: marked as done (kvirc: Defunct homepage)

Your message dated Mon, 29 Jun 2020 18:18:39 + with message-id and subject line Bug#960985: fixed in kvirc 4:5.0.0+dfsg-3 has caused the Debian Bug report #960985, regarding kvirc: Defunct homepage to be marked as done. This means that you claim that the problem has been dealt with. If this i

Bug#963678: marked as done (hedgewars: FTBFS with ghc 8.8)

Your message dated Mon, 29 Jun 2020 17:33:50 + with message-id and subject line Bug#963678: fixed in hedgewars 1.0.0-6 has caused the Debian Bug report #963678, regarding hedgewars: FTBFS with ghc 8.8 to be marked as done. This means that you claim that the problem has been dealt with. If thi

Bug#963369: marked as done (python-testfixtures: FTBFS: dh_auto_test: error: pybuild --test -i python{version} -p 3.8 returned exit code 13)

Your message dated Mon, 29 Jun 2020 16:36:08 + with message-id and subject line Bug#963369: fixed in python-testfixtures 6.14.1-1 has caused the Debian Bug report #963369, regarding python-testfixtures: FTBFS: dh_auto_test: error: pybuild --test -i python{version} -p 3.8 returned exit code 13

Processed: forcibly merging 963107 963970

Processing commands for cont...@bugs.debian.org: > forcemerge 963107 963970 Bug #963107 {Done: Antonio Radici } [mutt] "Encrypted connection unavailable" when using pre-authenticated connection Bug #963970 [mutt] mutt: DSA-4707-1 regression: setting tunnel option results in error "Encrypted conn

Bug#944750: marked as done (neomutt: Build with autocrypt support)

Your message dated Mon, 29 Jun 2020 15:35:35 + with message-id and subject line Bug#944750: fixed in neomutt 20200626+dfsg.1-1 has caused the Debian Bug report #944750, regarding neomutt: Build with autocrypt support to be marked as done. This means that you claim that the problem has been de

Bug#698267: marked as done (mutt: [PATCH] To/CC/Bc fields are stripped during editing (RFC 2822))

Your message dated Mon, 29 Jun 2020 15:35:29 + with message-id and subject line Bug#698267: fixed in mutt 1.14.5-1 has caused the Debian Bug report #698267, regarding mutt: [PATCH] To/CC/Bc fields are stripped during editing (RFC 2822) to be marked as done. This means that you claim that the

Bug#932698: marked as done (Please switch to libidn2)

Your message dated Mon, 29 Jun 2020 15:35:29 + with message-id and subject line Bug#932698: fixed in mutt 1.14.5-1 has caused the Debian Bug report #932698, regarding Please switch to libidn2 to be marked as done. This means that you claim that the problem has been dealt with. If this is not

Bug#963972: marked as done (error: cannot import key in /debian/upstream/signing-key.asc since GnuPG is not installed)

Your message dated Mon, 29 Jun 2020 23:59:24 +0900 with message-id <20200629235924.6be8486e34a4608d31853...@iijmio-mail.jp> and subject line has caused the Debian Bug report #963972, regarding error: cannot import key in /debian/upstream/signing-key.asc since GnuPG is not installed to be marked a

Bug#962676: marked as done (libzstd FTBFS for alpha: libc doesn't #define st_mtime)

Your message dated Mon, 29 Jun 2020 15:07:04 + with message-id and subject line Bug#962676: fixed in libzstd 1.4.5+dfsg-3 has caused the Debian Bug report #962676, regarding libzstd FTBFS for alpha: libc doesn't #define st_mtime to be marked as done. This means that you claim that the problem

Processed: closing 890586

Processing commands for cont...@bugs.debian.org: > close 890586 0.12-1 Bug #890586 [src:rtkit] rtkit: Homepage URL is dead Marked as fixed in versions rtkit/0.12-1. Bug #890586 [src:rtkit] rtkit: Homepage URL is dead Marked Bug as done > thanks Stopping processing here. Please contact me if you n

Processed: RFS: keras/2.3.1+dfsg-2 [RC] -- deep learning framework running on Theano or TensorFlow

Processing commands for cont...@bugs.debian.org: > close 963621 Bug #963621 [sponsorship-requests] RFS: keras/2.3.1+dfsg-2 [RC] -- deep learning framework running on Theano or TensorFlow Marked Bug as done > stop Stopping processing here. Please contact me if you need assistance. -- 963621: htt

Bug#894766: marked as done (Make a build without kwallet support)

Your message dated Mon, 29 Jun 2020 14:35:58 + with message-id and subject line Bug#894766: fixed in falkon 3.1.0+dfsg1-7 has caused the Debian Bug report #894766, regarding Make a build without kwallet support to be marked as done. This means that you claim that the problem has been dealt wi

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

Your message dated Mon, 29 Jun 2020 14:37:59 + with message-id and subject line Bug#963426: fixed in keras 2.3.1+dfsg-2 has caused the Debian Bug report #963426, regarding keras: FTBFS: dh_auto_test: error: pybuild --test --test-pytest -i python{version} -p 3.8 returned exit code 13 to be mar

Bug#963869: marked as done (falkon: FTBFS: 'QFile' was not declared in this scope)

Your message dated Mon, 29 Jun 2020 14:35:58 + with message-id and subject line Bug#963869: fixed in falkon 3.1.0+dfsg1-7 has caused the Debian Bug report #963869, regarding falkon: FTBFS: 'QFile' was not declared in this scope to be marked as done. This means that you claim that the problem

Bug#940463: marked as done (falkon: Falkon crashes and even freezes entire desktop.)

Your message dated Mon, 29 Jun 2020 14:35:58 + with message-id and subject line Bug#940463: fixed in falkon 3.1.0+dfsg1-7 has caused the Debian Bug report #940463, regarding falkon: Falkon crashes and even freezes entire desktop. to be marked as done. This means that you claim that the proble

Bug#903809: marked as done (Add qtwebengine5-dev-tools to suggests)

Your message dated Mon, 29 Jun 2020 14:35:58 + with message-id and subject line Bug#903809: fixed in falkon 3.1.0+dfsg1-7 has caused the Debian Bug report #903809, regarding Add qtwebengine5-dev-tools to suggests to be marked as done. This means that you claim that the problem has been dealt

Bug#963709: marked as done (pyside2: FTBFS on arm64: web_engine_initialize test fails with "Could not initialize GLX")

Your message dated Mon, 29 Jun 2020 12:49:10 + with message-id and subject line Bug#963709: fixed in pyside2 5.15.0-2 has caused the Debian Bug report #963709, regarding pyside2: FTBFS on arm64: web_engine_initialize test fails with "Could not initialize GLX" to be marked as done. This means

Bug#963903: marked as done ('ftpnew-blends' importer crashing. disabled.)

Your message dated Mon, 29 Jun 2020 14:10:45 +0200 with message-id <20200629121045.ga6...@xanadu.blop.info> and subject line Re: Bug#963903: 'ftpnew-blends' importer crashing. disabled. has caused the Debian Bug report #963903, regarding 'ftpnew-blends' importer crashing. disabled. to be marked as

Processed: RFS: shotdetect/1.0.86-5.1 [NMU] -- scene change detector

Processing commands for cont...@bugs.debian.org: > close 962751 Bug #962751 [sponsorship-requests] RFS: shotdetect/1.0.86-5.1 [NMU] -- scene change detector Marked Bug as done > stop Stopping processing here. Please contact me if you need assistance. -- 962751: https://bugs.debian.org/cgi-bin/b

Bug#963774: marked as done (mcl breaks roary autopkgtest: Cannot find the mcxdeblast executable, please ensure its in your PATH)

Your message dated Mon, 29 Jun 2020 11:35:51 + with message-id and subject line Bug#963774: fixed in mcl 1:14-137+ds-8 has caused the Debian Bug report #963774, regarding mcl breaks roary autopkgtest: Cannot find the mcxdeblast executable, please ensure its in your PATH to be marked as done.

Bug#962127: marked as done (shotdetect: FTBFS without dh-autoreconf)

Your message dated Mon, 29 Jun 2020 11:36:02 + with message-id and subject line Bug#962127: fixed in shotdetect 1.0.86-5.1 has caused the Debian Bug report #962127, regarding shotdetect: FTBFS without dh-autoreconf to be marked as done. This means that you claim that the problem has been deal

Bug#948871: marked as done (shotdetect: FTBFS with libxslt 1.1.34 (uses xslt-config))

Your message dated Mon, 29 Jun 2020 11:36:02 + with message-id and subject line Bug#948871: fixed in shotdetect 1.0.86-5.1 has caused the Debian Bug report #948871, regarding shotdetect: FTBFS with libxslt 1.1.34 (uses xslt-config) to be marked as done. This means that you claim that the prob

Bug#949496: marked as done (shotdetect: FTBFS with libxml2 not shipping xml2-config)

Your message dated Mon, 29 Jun 2020 11:36:02 + with message-id and subject line Bug#949496: fixed in shotdetect 1.0.86-5.1 has caused the Debian Bug report #949496, regarding shotdetect: FTBFS with libxml2 not shipping xml2-config to be marked as done. This means that you claim that the probl

Bug#795281: marked as done (autofs: Please provide a mechanism to make automount root mount points shared)

Your message dated Mon, 29 Jun 2020 11:33:39 + with message-id and subject line Bug#795281: fixed in autofs 5.1.6-3 has caused the Debian Bug report #795281, regarding autofs: Please provide a mechanism to make automount root mount points shared to be marked as done. This means that you clai

Bug#963839: marked as done (dpkg-dev: gpg tries to write in $HOME when verifying signatures)

Your message dated Mon, 29 Jun 2020 11:04:11 + with message-id and subject line Bug#963839: fixed in dpkg 1.20.3 has caused the Debian Bug report #963839, regarding dpkg-dev: gpg tries to write in $HOME when verifying signatures to be marked as done. This means that you claim that the problem

Bug#963035: marked as done (ffmpeg: 4.3 breaks chromium)

Your message dated Mon, 29 Jun 2020 11:04:01 + with message-id and subject line Bug#963035: fixed in chromium 83.0.4103.116-2 has caused the Debian Bug report #963035, regarding ffmpeg: 4.3 breaks chromium to be marked as done. This means that you claim that the problem has been dealt with. I

Bug#963844: marked as done (libdpkg-perl: unclear deprecation warning from get_build_env_whitelist())

Your message dated Mon, 29 Jun 2020 11:04:11 + with message-id and subject line Bug#963844: fixed in dpkg 1.20.3 has caused the Debian Bug report #963844, regarding libdpkg-perl: unclear deprecation warning from get_build_env_whitelist() to be marked as done. This means that you claim that t

Bug#963944: marked as done (libdpkg-perl: dpkg-source cannot build packages with keys anymore)

Your message dated Mon, 29 Jun 2020 11:04:11 + with message-id and subject line Bug#963944: fixed in dpkg 1.20.3 has caused the Debian Bug report #963944, regarding libdpkg-perl: dpkg-source cannot build packages with keys anymore to be marked as done. This means that you claim that the probl

Bug#963313: marked as done (vg: FTBFS: configure: error: Could not find a version of the library!)

Your message dated Mon, 29 Jun 2020 11:53:53 +0200 with message-id and subject line has caused the Debian Bug report #963313, regarding vg: FTBFS: configure: error: Could not find a version of the library! to be marked as done. This means that you claim that the problem has been dealt with. If

Bug#963487: marked as done (mitmproxy: New updated mitmproxy does not work as per #963067)

Your message dated Mon, 29 Jun 2020 09:34:13 + with message-id and subject line Bug#963487: fixed in mitmproxy 5.1.1-2 has caused the Debian Bug report #963487, regarding mitmproxy: New updated mitmproxy does not work as per #963067 to be marked as done. This means that you claim that the pro

Bug#957446: marked as done (libkiwix: ftbfs with GCC-10)

Your message dated Mon, 29 Jun 2020 01:58:08 -0700 with message-id and subject line Re: Bug#957446: libkiwix: ftbfs with GCC-10 has caused the Debian Bug report #957446, regarding libkiwix: ftbfs with GCC-10 to be marked as done. This means that you claim that the problem has been dealt with. If

Bug#963817: marked as done (numpy breaks pandas autopkgtest: TypeError: Cannot interpret 'CategoricalDtype(categories=None, ordered=None)' as a data type)

Your message dated Mon, 29 Jun 2020 08:28:47 + with message-id and subject line Bug#963817: fixed in pandas 0.25.3+dfsg2-3 has caused the Debian Bug report #963817, regarding numpy breaks pandas autopkgtest: TypeError: Cannot interpret 'CategoricalDtype(categories=None, ordered=None)' as a da

Bug#963752: marked as done (exfat-fuse should not provide /sbin/mount.exfat)

Your message dated Mon, 29 Jun 2020 08:24:50 + with message-id and subject line Bug#963752: fixed in fuse-exfat 1.3.0-2 has caused the Debian Bug report #963752, regarding exfat-fuse should not provide /sbin/mount.exfat to be marked as done. This means that you claim that the problem has been

Bug#960033: marked as done (patroni: Unit file option 'RuntimeDirectory' has invalid value for Debian 9)

Your message dated Mon, 29 Jun 2020 10:01:56 +0200 with message-id and subject line Re: Bug#960033: patroni: Unit file option 'RuntimeDirectory' has invalid value for Debian 9 has caused the Debian Bug report #960033, regarding patroni: Unit file option 'RuntimeDirectory' has invalid value for D

Bug#951059: marked as done (mariadb-server-10.3: lc_messages=fr_FR leads to upgrade crash with apt)

Your message dated Mon, 29 Jun 2020 07:19:41 + with message-id and subject line Bug#951059: fixed in mariadb-10.4 1:10.4.13-1~exp1 has caused the Debian Bug report #951059, regarding mariadb-server-10.3: lc_messages=fr_FR leads to upgrade crash with apt to be marked as done. This means that y

Bug#962541: marked as done (mariadb: Incorrect license information for the embedded mariadb-connector-c library)

Your message dated Mon, 29 Jun 2020 07:19:41 + with message-id and subject line Bug#962541: fixed in mariadb-10.4 1:10.4.13-1~exp1 has caused the Debian Bug report #962541, regarding mariadb: Incorrect license information for the embedded mariadb-connector-c library to be marked as done. Thi

Bug#962994: marked as done (pcp: cron jobs launch pcp in cron's cgroup)

Your message dated Mon, 29 Jun 2020 07:05:41 + with message-id and subject line Bug#962994: fixed in pcp 5.1.2-1 has caused the Debian Bug report #962994, regarding pcp: cron jobs launch pcp in cron's cgroup to be marked as done. This means that you claim that the problem has been dealt with.