Bug#959040: marked as done (Mcedit does not check spell)

Your message dated Sat, 02 May 2020 15:14:12 +1000 with message-id <1797189.oc1MUlxYgm@deblab> and subject line Re: Bug#959040: Mcedit does not check spell has caused the Debian Bug report #959040, regarding Mcedit does not check spell to be marked as done. This means that you claim that the

Bug#958778: marked as done (node-babel: Package fail to build with node-gulp-babel 8.8.0)

Your message dated Sat, 02 May 2020 10:31:49 +0530 with message-id <1zto9q.jbyuuzz0a...@onenetbeyond.org> and subject line fixed in 6.26.0+repack-4 bu embedding gulp-babel 6.1.2 has caused the Debian Bug report #958778, regarding node-babel: Package fail to build with node-gulp-babel 8.8.0 to be

Bug#959391: marked as done (wordpress: CVE-2020-11025 CVE-2020-11026 CVE-2020-11027 CVE-2020-11028 CVE-2020-11029 CVE-2020-11030)

Your message dated Sat, 02 May 2020 04:48:44 + with message-id and subject line Bug#959391: fixed in wordpress 5.4.1+dfsg1-1 has caused the Debian Bug report #959391, regarding wordpress: CVE-2020-11025 CVE-2020-11026 CVE-2020-11027 CVE-2020-11028 CVE-2020-11029 CVE-2020-11030 to be marked

Bug#308940: marked as done (eject failed as a normal user)

Your message dated Sat, 2 May 2020 10:06:03 +0800 with message-id and subject line bugreport is too old has caused the Debian Bug report #308940, regarding eject failed as a normal user to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case

Bug#591358: marked as done (When I try to eject a CD the door opens then closes immediately)

Your message dated Sat, 2 May 2020 10:06:03 +0800 with message-id and subject line bugreport is too old has caused the Debian Bug report #591358, regarding When I try to eject a CD the door opens then closes immediately to be marked as done. This means that you claim that the problem has been

Bug#521880: marked as done (cannot eject from sd card reader)

Your message dated Sat, 2 May 2020 10:06:03 +0800 with message-id and subject line bugreport is too old has caused the Debian Bug report #521880, regarding cannot eject from sd card reader to be marked as done. This means that you claim that the problem has been dealt with. If this is not the

Bug#276479: marked as done (can eject cdrom0, but not cdrom1 and cdrom2)

Your message dated Sat, 2 May 2020 10:06:03 +0800 with message-id and subject line bugreport is too old has caused the Debian Bug report #276479, regarding can eject cdrom0, but not cdrom1 and cdrom2 to be marked as done. This means that you claim that the problem has been dealt with. If this is

Bug#387392: marked as done (Problem ejecting USB drives)

Your message dated Sat, 2 May 2020 10:06:03 +0800 with message-id and subject line bugreport is too old has caused the Debian Bug report #387392, regarding Problem ejecting USB drives to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it

Bug#400523: marked as done ("eject -t" + "ipod 5g" = "unknown partition table")

Your message dated Sat, 2 May 2020 10:06:03 +0800 with message-id and subject line bugreport is too old has caused the Debian Bug report #400523, regarding "eject -t" + "ipod 5g" = "unknown partition table" to be marked as done. This means that you claim that the problem has been dealt with. If

Bug#259364: marked as done (eject: causes auto-open on exit)

Your message dated Sat, 2 May 2020 09:57:41 +0800 with message-id <9cfc31c8-b977-a178-8cc1-faa56e52d...@sina.com> and subject line bugreport is too old has caused the Debian Bug report #259364, regarding eject: causes auto-open on exit to be marked as done. This means that you claim that the

Bug#307485: marked as done (eject: Possible data loss (?) with dvd-RAM/packet writing)

Your message dated Sat, 2 May 2020 09:53:15 +0800 with message-id <84d0e361-b100-0e91-cd93-495393e50...@sina.com> and subject line bugreport is too old has caused the Debian Bug report #307485, regarding eject: Possible data loss (?) with dvd-RAM/packet writing to be marked as done. This means

Bug#753821: marked as done (eject fails on CD/DVD drive and reports wrong error)

Your message dated Sat, 2 May 2020 09:43:33 +0800 with message-id <9500528e-db80-3276-ed3e-1fdfad2a3...@sina.com> and subject line bugreport is too old has caused the Debian Bug report #753821, regarding eject fails on CD/DVD drive and reports wrong error to be marked as done. This means that you

Bug#774670: marked as done (cdrom will not eject)

Your message dated Sat, 2 May 2020 09:41:02 +0800 with message-id <869bc4d4-1374-2724-6fdf-6776091b0...@sina.com> and subject line bugreport is too old has caused the Debian Bug report #774670, regarding cdrom will not eject to be marked as done. This means that you claim that the problem has

Bug#946077: marked as done (little problem with tag and tags commands description in bug system documentation)

Your message dated Fri, 01 May 2020 22:01:37 + with message-id <5eac9c4133be9_3902ab4bbc0e5b442...@godard.mail> and subject line Bug#946077 fixed in www.debian.org has caused the Debian Bug report #946077, regarding little problem with tag and tags commands description in bug system

Bug#955721: marked as done (radcli: New upstream version 1.2.11 available)

Your message dated Fri, 01 May 2020 21:38:44 + with message-id and subject line Bug#955721: fixed in radcli 1.2.11-1 has caused the Debian Bug report #955721, regarding radcli: New upstream version 1.2.11 available to be marked as done. This means that you claim that the problem has been

Bug#953470: marked as done (Updating the radcli Uploaders list)

Your message dated Fri, 01 May 2020 21:38:43 + with message-id and subject line Bug#953470: fixed in radcli 1.2.11-1 has caused the Debian Bug report #953470, regarding Updating the radcli Uploaders list to be marked as done. This means that you claim that the problem has been dealt with. If

Bug#924247: marked as done (/Bugs/server-request.wml: very tiny typo i guess)

Your message dated Fri, 01 May 2020 21:34:35 + with message-id <5eac95eb885fb_3902ab4bbc0e5b442...@godard.mail> and subject line Bug#924247 fixed in www.debian.org has caused the Debian Bug report #924247, regarding /Bugs/server-request.wml: very tiny typo i guess to be marked as done. This

Bug#940226: marked as done (broken link to source from policy manual)

Your message dated Fri, 1 May 2020 23:26:45 +0200 with message-id <20200501232645.c4d108cab18960e52cccb...@mailbox.org> and subject line Re: [Bug#940226] broken link to source from policy manual has caused the Debian Bug report #940226, regarding broken link to source from policy manual to be

Bug#957696: marked as done (poa: ftbfs with GCC-10)

Your message dated Fri, 01 May 2020 20:37:32 + with message-id and subject line Bug#957696: fixed in poa 2.0+20060928-8 has caused the Debian Bug report #957696, regarding poa: ftbfs with GCC-10 to be marked as done. This means that you claim that the problem has been dealt with. If this is

Bug#924146: marked as done (www.debian.org: possible leftover: norwegian/Bugs/pseudo-packages.inc)

Your message dated Fri, 01 May 2020 20:00:22 + with message-id <5eac7fd6e1cb4_3902ab4bbc0e5b442...@godard.mail> and subject line Bug#924146 fixed in www.debian.org has caused the Debian Bug report #924146, regarding www.debian.org: possible leftover: norwegian/Bugs/pseudo-packages.inc to be

Bug#900749: marked as done ([www.debian.org] webwml build takes too long)

Your message dated Fri, 1 May 2020 21:47:47 +0200 with message-id <20200501214747.bfefc2871a208c141ed35...@mailbox.org> and subject line Re: Bug #900749: [www.debian.org] webwml build takes too long has caused the Debian Bug report #900749, regarding [www.debian.org] webwml build takes too long to

Bug#946572: marked as done (abcm2ps FTCBFS: builds for the build architecture)

Your message dated Fri, 01 May 2020 19:33:22 + with message-id and subject line Bug#946572: fixed in abcm2ps 8.14.7-0.2 has caused the Debian Bug report #946572, regarding abcm2ps FTCBFS: builds for the build architecture to be marked as done. This means that you claim that the problem has

Bug#871659: marked as done (www.debian.org: scripts: Debian GNU/Linux FAQ should not be typesetted on webserver but webserver should use faq .deb (was: Re: [...] Debian Documentation BoF @ DebConf17 [

Your message dated Fri, 1 May 2020 21:26:09 +0200 with message-id <20200501212609.f8798a9b51c1dd02a99c5...@mailbox.org> and subject line Re: Bug#871659: www.debian.org: scripts: Debian GNU/Linux FAQ should not be typesetted on webserver but webserver should use faq .deb has caused the Debian Bug

Bug#959034: marked as done (scilab: Updating Buster (notification) => scilab 6.0.1 dead. Illegal reflective operation. java --version : => openjdk 11.0.7)

Your message dated Fri, 01 May 2020 19:17:07 + with message-id and subject line Bug#959034: fixed in scilab 6.0.1-10+deb10u1 has caused the Debian Bug report #959034, regarding scilab: Updating Buster (notification) => scilab 6.0.1 dead. Illegal reflective operation. java --version : =>

Bug#915281: marked as done (libtag1v5: possible corruption of ogg files)

Your message dated Fri, 01 May 2020 19:17:08 + with message-id and subject line Bug#915281: fixed in taglib 1.11.1+dfsg.1-0.3+deb10u1 has caused the Debian Bug report #915281, regarding libtag1v5: possible corruption of ogg files to be marked as done. This means that you claim that the

Bug#945344: marked as done (libuim-data: registers unusable "tutcode" module)

Your message dated Fri, 01 May 2020 19:17:08 + with message-id and subject line Bug#945344: fixed in uim 1:1.8.8-4+deb10u3 has caused the Debian Bug report #945344, regarding libuim-data: registers unusable "tutcode" module to be marked as done. This means that you claim that the problem has

Bug#954278: marked as done (rust-cookie-factory: autopkgtest failure.)

Your message dated Fri, 1 May 2020 19:06:49 + with message-id <20200501190649.GZ29437@localhost> and subject line Close #954278 has caused the Debian Bug report #954278, regarding rust-cookie-factory: autopkgtest failure. to be marked as done. This means that you claim that the problem has

Bug#839028: marked as done (iodine should depend on ipcalc)

Your message dated Fri, 1 May 2020 21:06:32 +0200 with message-id <20200501190632.ga2...@jadzia.comodo.priv.at> and subject line Re: Bug#839028: iodine should depend on ipcalc has caused the Debian Bug report #839028, regarding iodine should depend on ipcalc to be marked as done. This means that

Processed: src:php-imagick: fails to migrate to testing for too long: FTBFS on armel

Processing control commands: > close -1 3.4.4-4 Bug #959386 [src:php-imagick] src:php-imagick: fails to migrate to testing for too long: FTBFS on armel Marked as fixed in versions php-imagick/3.4.4-4. Bug #959386 [src:php-imagick] src:php-imagick: fails to migrate to testing for too long: FTBFS

Bug#951412: marked as done (proftpd-basic: segfault when logging in through sftp)

Your message dated Fri, 01 May 2020 18:32:11 + with message-id and subject line Bug#951412: fixed in proftpd-dfsg 1.3.6-4+deb10u5 has caused the Debian Bug report #951412, regarding proftpd-basic: segfault when logging in through sftp to be marked as done. This means that you claim that the

Bug#928282: marked as done (filezilla: CVE-2019-5429)

Your message dated Fri, 01 May 2020 18:32:08 + with message-id and subject line Bug#928282: fixed in filezilla 3.39.0-2+deb10u1 has caused the Debian Bug report #928282, regarding filezilla: CVE-2019-5429 to be marked as done. This means that you claim that the problem has been dealt with.

Bug#943612: marked as done (python3-ownet: Python2-only code shipped in Python3 module)

Your message dated Fri, 01 May 2020 18:32:11 + with message-id and subject line Bug#943612: fixed in owfs 3.2p3+dfsg1-2+deb10u1 has caused the Debian Bug report #943612, regarding python3-ownet: Python2-only code shipped in Python3 module to be marked as done. This means that you claim that

Bug#956308: marked as done (libssh: CVE-2020-1730: Client/server denial of service when handling AES-CTR ciphers)

Your message dated Fri, 01 May 2020 18:32:09 + with message-id and subject line Bug#956308: fixed in libssh 0.8.7-1+deb10u1 has caused the Debian Bug report #956308, regarding libssh: CVE-2020-1730: Client/server denial of service when handling AES-CTR ciphers to be marked as done. This

Bug#959157: marked as done (fix for CVE-2020-1749 in linux-image-4.19.0-9 breaks wireguard)

Your message dated Fri, 01 May 2020 17:52:02 + with message-id and subject line Bug#959157: fixed in wireguard-linux-compat 1.0.20200429-2 has caused the Debian Bug report #959157, regarding fix for CVE-2020-1749 in linux-image-4.19.0-9 breaks wireguard to be marked as done. This means that

Bug#956869: marked as done (wireguard-dkms missing dependency on bc)

Your message dated Fri, 01 May 2020 17:52:02 + with message-id and subject line Bug#956869: fixed in wireguard-linux-compat 1.0.20200429-2 has caused the Debian Bug report #956869, regarding wireguard-dkms missing dependency on bc to be marked as done. This means that you claim that the

Bug#954305: marked as done (python-udatetime: shared library is not properly linked with libm)

Your message dated Fri, 01 May 2020 17:50:02 + with message-id and subject line Bug#954305: fixed in python-udatetime 0.0.16-3 has caused the Debian Bug report #954305, regarding python-udatetime: shared library is not properly linked with libm to be marked as done. This means that you claim

Bug#953539: marked as done (test fails in current unstable during the build)

Your message dated Fri, 01 May 2020 17:50:02 + with message-id and subject line Bug#953539: fixed in python-udatetime 0.0.16-3 has caused the Debian Bug report #953539, regarding test fails in current unstable during the build to be marked as done. This means that you claim that the problem

Bug#720991: marked as done (libgtkgl2.0-dev: should Depend: libgl-dev and libglu-dev)

Your message dated Fri, 01 May 2020 17:33:31 + with message-id and subject line Bug#720991: fixed in gtkgl2 2.1.0-0.1 has caused the Debian Bug report #720991, regarding libgtkgl2.0-dev: should Depend: libgl-dev and libglu-dev to be marked as done. This means that you claim that the problem

Bug#814351: marked as done (gtkgl2: various packaging updates)

Your message dated Fri, 01 May 2020 17:33:31 + with message-id and subject line Bug#814351: fixed in gtkgl2 2.1.0-0.1 has caused the Debian Bug report #814351, regarding gtkgl2: various packaging updates to be marked as done. This means that you claim that the problem has been dealt with. If

Bug#895052: marked as done (gtkgl2 FTCBFS: configures for the build architecture)

Your message dated Fri, 01 May 2020 17:33:31 + with message-id and subject line Bug#895052: fixed in gtkgl2 2.1.0-0.1 has caused the Debian Bug report #895052, regarding gtkgl2 FTCBFS: configures for the build architecture to be marked as done. This means that you claim that the problem has

Processed: ITP: php-horde-core -- Core Horde Framework library

Processing commands for cont...@bugs.debian.org: > close 959289 Bug #959289 [wnpp] ITP: php-horde-core -- Core Horde Framework library Marked Bug as done > stop Stopping processing here. Please contact me if you need assistance. -- 959289:

Bug#958586: marked as done (fake-hwclock: Build-Depends on deprecated dh-systemd which is going away)

Your message dated Fri, 01 May 2020 16:19:55 + with message-id and subject line Bug#958586: fixed in fake-hwclock 0.12 has caused the Debian Bug report #958586, regarding fake-hwclock: Build-Depends on deprecated dh-systemd which is going away to be marked as done. This means that you claim

Bug#695504: marked as done (eject: Avoid setuid to root for dmcrypt-get-device)

Your message dated Fri, 1 May 2020 23:56:03 +0800 with message-id <8e9fbf21-92be-ea09-c223-d6418b2b6...@sina.com> and subject line close has caused the Debian Bug report #695504, regarding eject: Avoid setuid to root for dmcrypt-get-device to be marked as done. This means that you claim that the

Bug#929801: marked as done (debian-policy: Broken link in section 3.6 Virtual packages)

Your message dated Fri, 01 May 2020 15:01:11 + with message-id <5eac39b7f29cf_3902ab4bbc0e5b442...@godard.mail> and subject line Bug#929389 fixed in www.debian.org has caused the Debian Bug report #929389, regarding debian-policy: Broken link in section 3.6 Virtual packages to be marked as

Bug#929389: marked as done (missed virtual-package-names-list.yaml page)

Your message dated Fri, 01 May 2020 15:01:11 + with message-id <5eac39b7f29cf_3902ab4bbc0e5b442...@godard.mail> and subject line Bug#929389 fixed in www.debian.org has caused the Debian Bug report #929389, regarding missed virtual-package-names-list.yaml page to be marked as done. This means

Bug#959231: marked as done (security-tracker: Proxy Error on CVE-2020-11565 tracker page)

Your message dated Fri, 1 May 2020 16:46:21 +0200 with message-id <20200501144621.GA19818@eldamar.local> and subject line Re: Bug#959231: security-tracker: Proxy Error on CVE-2020-11565 tracker page has caused the Debian Bug report #929228, regarding security-tracker: Proxy Error on

Bug#925747: marked as done (libkibi: ftbfs with GCC-9)

Your message dated Fri, 01 May 2020 14:49:25 + with message-id and subject line Bug#925747: fixed in libkibi 0.1.1-2.1 has caused the Debian Bug report #925747, regarding libkibi: ftbfs with GCC-9 to be marked as done. This means that you claim that the problem has been dealt with. If this

Bug#929228: marked as done (security-tracker: MITRE descriptions containing non-ascii characters might cause issues on accessing CVE page)

Your message dated Fri, 1 May 2020 16:46:21 +0200 with message-id <20200501144621.GA19818@eldamar.local> and subject line Re: Bug#959231: security-tracker: Proxy Error on CVE-2020-11565 tracker page has caused the Debian Bug report #929228, regarding security-tracker: MITRE descriptions

Bug#959110: marked as done (node-babel7 is missing @babel/runtime/helpers)

Your message dated Fri, 01 May 2020 14:38:09 + with message-id and subject line Bug#959110: fixed in node-babel7 7.4.5-4 has caused the Debian Bug report #959110, regarding node-babel7 is missing @babel/runtime/helpers to be marked as done. This means that you claim that the problem has been

Bug#958868: marked as done (charcodes component in node-babel7 ftbfs in buster-backports)

Your message dated Fri, 01 May 2020 14:38:09 + with message-id and subject line Bug#958868: fixed in node-babel7 7.4.5-4 has caused the Debian Bug report #958868, regarding charcodes component in node-babel7 ftbfs in buster-backports to be marked as done. This means that you claim that the

Bug#955443: marked as done (RFS: libkibi/0.1.1-2.1 [NMU, RC] -- library for byte prefixes)

Your message dated Fri, 01 May 2020 10:36:05 -0400 with message-id <0f3ade0b0f089894238f54c7282aa70af527bd9e.ca...@debian.org> and subject line Re: RFS: libkibi/0.1.1-2.1 [NMU, RC] -- library for byte prefixes has caused the Debian Bug report #955443, regarding RFS: libkibi/0.1.1-2.1 [NMU, RC] --

Bug#952334: marked as done (gcl: FTBFS: Unrecoverable error: Segmentation violation..)

Your message dated Fri, 01 May 2020 13:33:34 + with message-id and subject line Bug#952334: fixed in gcl 2.6.12-95 has caused the Debian Bug report #952334, regarding gcl: FTBFS: Unrecoverable error: Segmentation violation.. to be marked as done. This means that you claim that the problem

Bug#954586: marked as done (evolution-data-server: FTBFS: CheckFunctionExists.c:17: undefined reference to `res_query')

Your message dated Fri, 1 May 2020 06:59:02 -0400 with message-id and subject line Re: evolution-data-server: FTBFS: CheckFunctionExists.c:17: undefined reference to `res_query' has caused the Debian Bug report #954586, regarding evolution-data-server: FTBFS: CheckFunctionExists.c:17: undefined

Bug#959222: marked as done (qemu-user-static: does not register binary formats)

Your message dated Fri, 01 May 2020 10:50:38 + with message-id and subject line Bug#959222: fixed in qemu 1:5.0-4 has caused the Debian Bug report #959222, regarding qemu-user-static: does not register binary formats to be marked as done. This means that you claim that the problem has been

Processed: closing 872960

Processing commands for cont...@bugs.debian.org: > close 872960 Bug #872960 [synapse] synapse: Fails to start under wayland with segmentation fault. Marked Bug as done > thanks Stopping processing here. Please contact me if you need assistance. -- 872960:

Bug#959077: marked as done (saods9: autopkgtest fails on arm64)

Your message dated Fri, 01 May 2020 10:07:29 + with message-id and subject line Bug#959077: fixed in saods9 8.1+repack-2 has caused the Debian Bug report #959077, regarding saods9: autopkgtest fails on arm64 to be marked as done. This means that you claim that the problem has been dealt

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

Your message dated Fri, 01 May 2020 10:06:49 + with message-id and subject line Bug#937251: fixed in pax-utils 1.2.6-2 has caused the Debian Bug report #937251, regarding pax-utils: Python2 removal in sid/bullseye to be marked as done. This means that you claim that the problem has been

Processed: closing 907524

Processing commands for cont...@bugs.debian.org: > close 907524 Bug #907524 [src:python-guess-language] Support for python 2.7 Marked Bug as done > thanks Stopping processing here. Please contact me if you need assistance. -- 907524: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=907524

Bug#956152: marked as done (rabbitmq-server: fails to install reliably on arm64)

Your message dated Fri, 1 May 2020 11:56:34 +0200 with message-id <9a1464e5-a231-8aad-cc84-83e11cb53...@debian.org> and subject line Re: rabbitmq-server: fails to install reliably on arm64 has caused the Debian Bug report #956152, regarding rabbitmq-server: fails to install reliably on arm64 to be

Bug#957238: marked as done (fs-uae: ftbfs with GCC-10)

Your message dated Fri, 01 May 2020 09:19:13 + with message-id and subject line Bug#957238: fixed in fs-uae 3.0.5+dfsg-1 has caused the Debian Bug report #957238, regarding fs-uae: ftbfs with GCC-10 to be marked as done. This means that you claim that the problem has been dealt with. If this

Processed: closing 814339

Processing commands for cont...@bugs.debian.org: > close 814339 Bug #814339 [nghttp2] nghttp2: missing build-dependency on python-sphinxcontrib.rubydomain Marked Bug as done > thanks Stopping processing here. Please contact me if you need assistance. -- 814339:

Bug#957303: marked as done (gravit: ftbfs with GCC-10)

Your message dated Fri, 01 May 2020 09:04:51 + with message-id and subject line Bug#957303: fixed in gravit 0.5.1+dfsg-5 has caused the Debian Bug report #957303, regarding gravit: ftbfs with GCC-10 to be marked as done. This means that you claim that the problem has been dealt with. If this

Processed: closing 957537

Processing commands for cont...@bugs.debian.org: > close 957537 Bug #957537 [src:mg] mg: ftbfs with GCC-10 Marked Bug as done > thanks Stopping processing here. Please contact me if you need assistance. -- 957537: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=957537 Debian Bug Tracking

Processed: closing 913461

Processing commands for cont...@bugs.debian.org: > close 913461 Bug #913461 [src:libstrophe] libstrophe: please provide a package for stretch-backports Marked Bug as done > thanks Stopping processing here. Please contact me if you need assistance. -- 913461:

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

Your message dated Fri, 01 May 2020 08:34:16 + with message-id and subject line Bug#938061: fixed in python-pyelftools 0.26-2 has caused the Debian Bug report #938061, regarding python-pyelftools: Python2 removal in sid/bullseye to be marked as done. This means that you claim that the

Bug#955981: marked as done (libreoffice-gtk3: Bottom of the LibreOffice Writer print dialog window appears off-screen making it unusable.)

Your message dated Fri, 01 May 2020 07:04:47 + with message-id and subject line Bug#955981: fixed in libreoffice 1:6.4.4~rc1-1 has caused the Debian Bug report #955981, regarding libreoffice-gtk3: Bottom of the LibreOffice Writer print dialog window appears off-screen making it unusable. to

Bug#955637: marked as done (ITS: font-manager)

Your message dated Fri, 01 May 2020 06:03:25 + with message-id and subject line Bug#955637: fixed in font-manager 0.7.7-1 has caused the Debian Bug report #955637, regarding ITS: font-manager to be marked as done. This means that you claim that the problem has been dealt with. If this is not