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

2019-10-28 Thread Debian Bug Tracking System
Your message dated Tue, 29 Oct 2019 06:49:23 + with message-id and subject line Bug#937819: fixed in python-humanize 0.5.1-4 has caused the Debian Bug report #937819, regarding python-humanize: Python2 removal in sid/bullseye to be marked as done. This means that you claim that the problem ha

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

2019-10-28 Thread Debian Bug Tracking System
Your message dated Tue, 29 Oct 2019 04:49:46 + with message-id and subject line Bug#937836: fixed in python-intbitset 2.3.0-3.1 has caused the Debian Bug report #937836, regarding python-intbitset: Python2 removal in sid/bullseye to be marked as done. This means that you claim that the proble

Bug#943737: marked as done (RM: furiusisomount -- RoQA; dead upstream, depends on obsolete libs)

2019-10-28 Thread Debian Bug Tracking System
Your message dated Tue, 29 Oct 2019 04:43:51 + with message-id and subject line Bug#943737: Removed package(s) from unstable has caused the Debian Bug report #943737, regarding RM: furiusisomount -- RoQA; dead upstream, depends on obsolete libs to be marked as done. This means that you claim

Bug#943702: marked as done (RM: haskell-enumerator -- ROM; unused Haskell library)

2019-10-28 Thread Debian Bug Tracking System
Your message dated Tue, 29 Oct 2019 04:43:26 + with message-id and subject line Bug#943702: Removed package(s) from unstable has caused the Debian Bug report #943702, regarding RM: haskell-enumerator -- ROM; unused Haskell library to be marked as done. This means that you claim that the probl

Bug#861929: marked as done (furiusisomount: please demote the nautilus dependency)

2019-10-28 Thread Debian Bug Tracking System
Your message dated Tue, 29 Oct 2019 04:43:58 + with message-id and subject line Bug#943737: Removed package(s) from unstable has caused the Debian Bug report #861929, regarding furiusisomount: please demote the nautilus dependency to be marked as done. This means that you claim that the probl

Bug#910532: marked as done (src:haskell-enumerator: unlikely to be worth the maintenance burden)

2019-10-28 Thread Debian Bug Tracking System
Your message dated Tue, 29 Oct 2019 04:43:31 + with message-id and subject line Bug#943702: Removed package(s) from unstable has caused the Debian Bug report #910532, regarding src:haskell-enumerator: unlikely to be worth the maintenance burden to be marked as done. This means that you claim

Bug#943700: marked as done (RM: node-simple-fmt -- RoM; abandoned upstream)

2019-10-28 Thread Debian Bug Tracking System
Your message dated Tue, 29 Oct 2019 04:43:04 + with message-id and subject line Bug#943700: Removed package(s) from unstable has caused the Debian Bug report #943700, regarding RM: node-simple-fmt -- RoM; abandoned upstream to be marked as done. This means that you claim that the problem has

Bug#885281: marked as done (furiusisomount: Depends on unmaintained pygtk)

2019-10-28 Thread Debian Bug Tracking System
Your message dated Tue, 29 Oct 2019 04:43:58 + with message-id and subject line Bug#943737: Removed package(s) from unstable has caused the Debian Bug report #885281, regarding furiusisomount: Depends on unmaintained pygtk to be marked as done. This means that you claim that the problem has b

Bug#943698: marked as done (RM: node-es6-module-transpiler -- RoM; abandoned upstream)

2019-10-28 Thread Debian Bug Tracking System
Your message dated Tue, 29 Oct 2019 04:42:25 + with message-id and subject line Bug#943698: Removed package(s) from unstable has caused the Debian Bug report #943698, regarding RM: node-es6-module-transpiler -- RoM; abandoned upstream to be marked as done. This means that you claim that the

Bug#822270: marked as done ([furiusisomount] Typo in package description)

2019-10-28 Thread Debian Bug Tracking System
Your message dated Tue, 29 Oct 2019 04:43:58 + with message-id and subject line Bug#943737: Removed package(s) from unstable has caused the Debian Bug report #822270, regarding [furiusisomount] Typo in package description to be marked as done. This means that you claim that the problem has be

Bug#936571: marked as done (furiusisomount: Python2 removal in sid/bullseye)

2019-10-28 Thread Debian Bug Tracking System
Your message dated Tue, 29 Oct 2019 04:43:58 + with message-id and subject line Bug#943737: Removed package(s) from unstable has caused the Debian Bug report #936571, regarding furiusisomount: Python2 removal in sid/bullseye to be marked as done. This means that you claim that the problem has

Bug#686315: marked as done ([furiusisomount] Doesn't warn if user isn't in fuse group.)

2019-10-28 Thread Debian Bug Tracking System
Your message dated Tue, 29 Oct 2019 04:43:58 + with message-id and subject line Bug#943737: Removed package(s) from unstable has caused the Debian Bug report #686315, regarding [furiusisomount] Doesn't warn if user isn't in fuse group. to be marked as done. This means that you claim that the

Processed: oops

2019-10-28 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > close 943413 Bug #943413 [sudo] sudo 1.8.28p1-1 built with wrong libexecdir Marked Bug as done > reopen 943313 Bug #943313 {Done: Bdale Garbee } [src:liggghts] liggghts should not use MPI_C_COMPILER or MPI_CXX_COMPILER 'reopen' may be inappropria

Bug#846602: marked as done (lua-compat53: Install lua-compat53.h in /usr/include/lua*/)

2019-10-28 Thread Debian Bug Tracking System
Your message dated Tue, 29 Oct 2019 04:04:09 + with message-id and subject line Bug#846602: fixed in lua-compat53 0.7-2 has caused the Debian Bug report #846602, regarding lua-compat53: Install lua-compat53.h in /usr/include/lua*/ to be marked as done. This means that you claim that the probl

Bug#943745: marked as done (lintian: 'file-missing-in-md5sums' and 'md5sums-lists-nonexistent-file' are reversed)

2019-10-28 Thread Debian Bug Tracking System
Your message dated Mon, 28 Oct 2019 21:07:09 -0700 with message-id and subject line Fwd: Bug#943745: lintian: 'file-missing-in-md5sums' and 'md5sums-lists-nonexistent-file' are reversed has caused the Debian Bug report #943745, regarding lintian: 'file-missing-in-md5sums' and 'md5sums-lists-non

Bug#943313: marked as done (liggghts should not use MPI_C_COMPILER or MPI_CXX_COMPILER)

2019-10-28 Thread Debian Bug Tracking System
Your message dated Tue, 29 Oct 2019 02:53:11 + with message-id and subject line Bug#943313: fixed in sudo 1.8.29-1 has caused the Debian Bug report #943313, regarding liggghts should not use MPI_C_COMPILER or MPI_CXX_COMPILER to be marked as done. This means that you claim that the problem ha

Bug#943000: marked as done (doc-rfc: Python2 removal in sid/bullseye)

2019-10-28 Thread Debian Bug Tracking System
Your message dated Mon, 28 Oct 2019 22:26:53 + with message-id and subject line Bug#943000: fixed in doc-rfc 20191026-1 has caused the Debian Bug report #943000, regarding doc-rfc: Python2 removal in sid/bullseye to be marked as done. This means that you claim that the problem has been dealt

Bug#942634: marked as done (apt-cacher-ng: fails to work on debian/sid suite (too small BUFSIZEMAX))

2019-10-28 Thread Debian Bug Tracking System
Your message dated Mon, 28 Oct 2019 22:23:06 + with message-id and subject line Bug#942634: fixed in apt-cacher-ng 3.2-3 has caused the Debian Bug report #942634, regarding apt-cacher-ng: fails to work on debian/sid suite (too small BUFSIZEMAX) to be marked as done. This means that you claim

Bug#943102: marked as done (libzn-poly: Python2 removal in sid/bullseye)

2019-10-28 Thread Debian Bug Tracking System
Your message dated Mon, 28 Oct 2019 21:04:25 + with message-id and subject line Bug#943102: fixed in libzn-poly 0.9.1-2 has caused the Debian Bug report #943102, regarding libzn-poly: Python2 removal in sid/bullseye to be marked as done. This means that you claim that the problem has been dea

Bug#942770: marked as done (mat2: Please port to python3-nautlius)

2019-10-28 Thread Debian Bug Tracking System
Your message dated Mon, 28 Oct 2019 20:45:53 + with message-id and subject line Bug#942770: fixed in mat2 0.9.0-2 has caused the Debian Bug report #942770, regarding mat2: Please port to python3-nautlius to be marked as done. This means that you claim that the problem has been dealt with. If

Bug#934040: marked as done (tasksel: doesn't provide transitional package for task-print-server)

2019-10-28 Thread Debian Bug Tracking System
Your message dated Mon, 28 Oct 2019 21:35:37 +0100 with message-id <7671291f-57e6-edb1-db99-cd192c3a8...@gmail.com> and subject line 934040 fixed in 3.56 has caused the Debian Bug report #934040, regarding tasksel: doesn't provide transitional package for task-print-server to be marked as done. Th

Bug#943356: marked as done (no login in vm)

2019-10-28 Thread Debian Bug Tracking System
Your message dated Mon, 28 Oct 2019 19:37:24 + with message-id <5da715ce812ae111e3fa5a5d51b2bedfdd77d50d.ca...@gmail.com> and subject line Re: no login in vm has caused the Debian Bug report #943356, regarding no login in vm to be marked as done. This means that you claim that the problem has

Bug#926549: marked as done (libgps changed API of gps_read)

2019-10-28 Thread Debian Bug Tracking System
Your message dated Mon, 28 Oct 2019 19:19:02 + with message-id and subject line Bug#926549: fixed in direwolf 1.5+dfsg-3 has caused the Debian Bug report #926549, regarding libgps changed API of gps_read to be marked as done. This means that you claim that the problem has been dealt with. If

Bug#928361: marked as done (prometheus-bind-exporter: wrong package description)

2019-10-28 Thread Debian Bug Tracking System
Your message dated Mon, 28 Oct 2019 18:05:00 + with message-id and subject line Bug#928361: fixed in prometheus-bind-exporter 0.2.0+git20190914+ds-1 has caused the Debian Bug report #928361, regarding prometheus-bind-exporter: wrong package description to be marked as done. This means that y

Bug#932645: marked as done (Setting up kopano-search results in AppArmor parser error / syntax error)

2019-10-28 Thread Debian Bug Tracking System
Your message dated Mon, 28 Oct 2019 18:42:53 +0100 with message-id <20191028174252.ga13...@x260.cruise.homelinux.net> and subject line has caused the Debian Bug report #932645, regarding Setting up kopano-search results in AppArmor parser error / syntax error to be marked as done. This means tha

Bug#933964: marked as done (milkytracker: CVE-2019-14464 CVE-2019-14496 CVE-2019-14497)

2019-10-28 Thread Debian Bug Tracking System
Your message dated Mon, 28 Oct 2019 17:49:07 + with message-id and subject line Bug#933964: fixed in milkytracker 1.02.00+dfsg-2 has caused the Debian Bug report #933964, regarding milkytracker: CVE-2019-14464 CVE-2019-14496 CVE-2019-14497 to be marked as done. This means that you claim that

Bug#939507: marked as done (prometheus-postgres-exporter: please consider shipping queries.yaml)

2019-10-28 Thread Debian Bug Tracking System
Your message dated Mon, 28 Oct 2019 17:19:25 + with message-id and subject line Bug#939507: fixed in prometheus-postgres-exporter 0.5.1+ds-2 has caused the Debian Bug report #939507, regarding prometheus-postgres-exporter: please consider shipping queries.yaml to be marked as done. This means

Bug#931818: marked as done (cups: Jobs webpage /usr/lib/cups/cgi-bin/jobs.cgi segfault after package login removes /etc/securetty)

2019-10-28 Thread Debian Bug Tracking System
Your message dated Mon, 28 Oct 2019 17:17:47 + with message-id <28102019171546.cea2bddc3...@desktop.copernicus.org.uk> and subject line Re: Bug#931818: Please close this bug has caused the Debian Bug report #931818, regarding cups: Jobs webpage /usr/lib/cups/cgi-bin/jobs.cgi segfault after pac

Bug#942788: marked as done (Fix FTBFS for GNU/Hurd)

2019-10-28 Thread Debian Bug Tracking System
Your message dated Mon, 28 Oct 2019 16:51:18 + with message-id and subject line Bug#942788: fixed in libproc-processtable-perl 0.59-2 has caused the Debian Bug report #942788, regarding Fix FTBFS for GNU/Hurd to be marked as done. This means that you claim that the problem has been dealt with

Bug#942126: marked as done (gvfs-fuse: /run/user/ID/gvfs/ empty after upgrade)

2019-10-28 Thread Debian Bug Tracking System
Your message dated Mon, 28 Oct 2019 16:26:39 + with message-id and subject line Bug#942126: fixed in gvfs 1.42.1-2 has caused the Debian Bug report #942126, regarding gvfs-fuse: /run/user/ID/gvfs/ empty after upgrade to be marked as done. This means that you claim that the problem has been de

Bug#942139: marked as done (gvfs: smb of sftp shares no longer show up under /run/user/[UID]/gvfs)

2019-10-28 Thread Debian Bug Tracking System
Your message dated Mon, 28 Oct 2019 16:10:36 +0100 with message-id <20191028151036.ga13...@home.ouaza.com> and subject line Re: your mail has caused the Debian Bug report #942139, regarding gvfs: smb of sftp shares no longer show up under /run/user/[UID]/gvfs to be marked as done. This means that

Bug#942021: marked as done (README.Debian refers to an inexistent architecture.html file)

2019-10-28 Thread Debian Bug Tracking System
Your message dated Mon, 28 Oct 2019 15:06:16 + with message-id and subject line Bug#942021: fixed in postgresql-common 208 has caused the Debian Bug report #942021, regarding README.Debian refers to an inexistent architecture.html file to be marked as done. This means that you claim that the

Processed: RFS: yaz/5.27.2-1 -- utilities for YAZ Z39.50 toolkit

2019-10-28 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > close 942855 Bug #942855 [sponsorship-requests] RFS: yaz/5.27.2-1 -- utilities for YAZ Z39.50 toolkit Marked Bug as done > stop Stopping processing here. Please contact me if you need assistance. -- 942855: https://bugs.debian.org/cgi-bin/bugre

Bug#885493: marked as done (virtaal: Depends on unmaintained pygtk)

2019-10-28 Thread Debian Bug Tracking System
Your message dated Mon, 28 Oct 2019 13:54:09 + with message-id and subject line Bug#885493: fixed in virtaal 0.7.1+git20191021+ds1-1 has caused the Debian Bug report #885493, regarding virtaal: Depends on unmaintained pygtk to be marked as done. This means that you claim that the problem has

Bug#938781: marked as done (virtaal: Python2 removal in sid/bullseye)

2019-10-28 Thread Debian Bug Tracking System
Your message dated Mon, 28 Oct 2019 13:54:09 + with message-id and subject line Bug#938781: fixed in virtaal 0.7.1+git20191021+ds1-1 has caused the Debian Bug report #938781, regarding virtaal: Python2 removal in sid/bullseye to be marked as done. This means that you claim that the problem ha

Bug#937000: marked as done (med-fichier: Python2 removal in sid/bullseye)

2019-10-28 Thread Debian Bug Tracking System
Your message dated Mon, 28 Oct 2019 13:35:28 + with message-id and subject line Bug#937000: fixed in med-fichier 4.0.0+repack-8 has caused the Debian Bug report #937000, regarding med-fichier: Python2 removal in sid/bullseye to be marked as done. This means that you claim that the problem has

Bug#943409: marked as done (python3-cheroot: Missing dependency on python3-jaraco.functools)

2019-10-28 Thread Debian Bug Tracking System
Your message dated Mon, 28 Oct 2019 13:09:00 + with message-id and subject line Bug#943409: fixed in python-cheroot 8.2.1+ds-2 has caused the Debian Bug report #943409, regarding python3-cheroot: Missing dependency on python3-jaraco.functools to be marked as done. This means that you claim th

Bug#938621: marked as done (tagpy: Python2 removal in sid/bullseye)

2019-10-28 Thread Debian Bug Tracking System
Your message dated Mon, 28 Oct 2019 12:52:36 + with message-id and subject line Bug#938621: fixed in tagpy 2013.1-7 has caused the Debian Bug report #938621, regarding tagpy: Python2 removal in sid/bullseye to be marked as done. This means that you claim that the problem has been dealt with.

Bug#938796: marked as done (vnlog: Python2 removal in sid/bullseye)

2019-10-28 Thread Debian Bug Tracking System
Your message dated Mon, 28 Oct 2019 12:38:23 + with message-id and subject line Bug#938796: fixed in vnlog 1.21-2 has caused the Debian Bug report #938796, regarding vnlog: Python2 removal in sid/bullseye to be marked as done. This means that you claim that the problem has been dealt with. If

Bug#934459: marked as done (AppArmor configuration doesn't cover openssl.cnf in /etc/ssl/)

2019-10-28 Thread Debian Bug Tracking System
Your message dated Mon, 28 Oct 2019 12:34:13 + with message-id and subject line Bug#934459: fixed in kopanocore 8.7.0-4 has caused the Debian Bug report #934459, regarding AppArmor configuration doesn't cover openssl.cnf in /etc/ssl/ to be marked as done. This means that you claim that the pr

Bug#933761: marked as done (AppArmor configuration doesn't cover LDAP)

2019-10-28 Thread Debian Bug Tracking System
Your message dated Mon, 28 Oct 2019 12:34:13 + with message-id and subject line Bug#933761: fixed in kopanocore 8.7.0-4 has caused the Debian Bug report #933761, regarding AppArmor configuration doesn't cover LDAP to be marked as done. This means that you claim that the problem has been dealt

Bug#933762: marked as done (Initscript uses wrong PID file directory)

2019-10-28 Thread Debian Bug Tracking System
Your message dated Mon, 28 Oct 2019 12:34:12 + with message-id and subject line Bug#924569: fixed in kopanocore 8.7.0-4 has caused the Debian Bug report #924569, regarding Initscript uses wrong PID file directory to be marked as done. This means that you claim that the problem has been dealt

Bug#941610: marked as done (kopano-server crashes)

2019-10-28 Thread Debian Bug Tracking System
Your message dated Mon, 28 Oct 2019 12:34:13 + with message-id and subject line Bug#941610: fixed in kopanocore 8.7.0-4 has caused the Debian Bug report #941610, regarding kopano-server crashes to be marked as done. This means that you claim that the problem has been dealt with. If this is no

Bug#934460: marked as done (AppArmor configuration doesn't cover mime.types, pdftotext and proc)

2019-10-28 Thread Debian Bug Tracking System
Your message dated Mon, 28 Oct 2019 12:34:13 + with message-id and subject line Bug#934460: fixed in kopanocore 8.7.0-4 has caused the Debian Bug report #934460, regarding AppArmor configuration doesn't cover mime.types, pdftotext and proc to be marked as done. This means that you claim that

Bug#939751: marked as done (Kopano-Server in Stable not compatible with MariaDB 10.3)

2019-10-28 Thread Debian Bug Tracking System
Your message dated Mon, 28 Oct 2019 12:34:13 + with message-id and subject line Bug#939751: fixed in kopanocore 8.7.0-4 has caused the Debian Bug report #939751, regarding Kopano-Server in Stable not compatible with MariaDB 10.3 to be marked as done. This means that you claim that the problem

Bug#943573: marked as done (debian-edu-config: Don't depend on python-notify)

2019-10-28 Thread Debian Bug Tracking System
Your message dated Mon, 28 Oct 2019 12:34:01 + with message-id and subject line Bug#943573: fixed in debian-edu-config 2.11.7 has caused the Debian Bug report #943573, regarding debian-edu-config: Don't depend on python-notify to be marked as done. This means that you claim that the problem h

Bug#933759: marked as done (Missing /etc/kopano/ldap.cfg)

2019-10-28 Thread Debian Bug Tracking System
Your message dated Mon, 28 Oct 2019 12:34:12 + with message-id and subject line Bug#933759: fixed in kopanocore 8.7.0-4 has caused the Debian Bug report #933759, regarding Missing /etc/kopano/ldap.cfg to be marked as done. This means that you claim that the problem has been dealt with. If thi

Bug#942491: marked as done (kopano-presence: SysV init script stop action not working)

2019-10-28 Thread Debian Bug Tracking System
Your message dated Mon, 28 Oct 2019 12:34:13 + with message-id and subject line Bug#942491: fixed in kopanocore 8.7.0-4 has caused the Debian Bug report #942491, regarding kopano-presence: SysV init script stop action not working to be marked as done. This means that you claim that the proble

Bug#941999: marked as done (kopanocore: autopkgtest tries to install packages itself but doesn't exit appropriately if that fails)

2019-10-28 Thread Debian Bug Tracking System
Your message dated Mon, 28 Oct 2019 12:34:13 + with message-id and subject line Bug#941999: fixed in kopanocore 8.7.0-4 has caused the Debian Bug report #941999, regarding kopanocore: autopkgtest tries to install packages itself but doesn't exit appropriately if that fails to be marked as don

Bug#933760: marked as done (Missing /etc/kopano/ldap.cfg)

2019-10-28 Thread Debian Bug Tracking System
Your message dated Mon, 28 Oct 2019 12:34:12 + with message-id and subject line Bug#933759: fixed in kopanocore 8.7.0-4 has caused the Debian Bug report #933759, regarding Missing /etc/kopano/ldap.cfg to be marked as done. This means that you claim that the problem has been dealt with. If thi

Bug#933887: marked as done (Default userscripts try to execute relocated kscriptrun)

2019-10-28 Thread Debian Bug Tracking System
Your message dated Mon, 28 Oct 2019 12:34:13 + with message-id and subject line Bug#933887: fixed in kopanocore 8.7.0-4 has caused the Debian Bug report #933887, regarding Default userscripts try to execute relocated kscriptrun to be marked as done. This means that you claim that the problem

Bug#935789: marked as done (Kopano-Gateway crashes)

2019-10-28 Thread Debian Bug Tracking System
Your message dated Mon, 28 Oct 2019 12:34:13 + with message-id and subject line Bug#935789: fixed in kopanocore 8.7.0-4 has caused the Debian Bug report #935789, regarding Kopano-Gateway crashes to be marked as done. This means that you claim that the problem has been dealt with. If this is n

Bug#931008: marked as done (Bug causes unread/read status not to be saved)

2019-10-28 Thread Debian Bug Tracking System
Your message dated Mon, 28 Oct 2019 12:34:12 + with message-id and subject line Bug#931008: fixed in kopanocore 8.7.0-4 has caused the Debian Bug report #931008, regarding Bug causes unread/read status not to be saved to be marked as done. This means that you claim that the problem has been d

Bug#924569: marked as done (kopano-server: SysV init scripts use wrong pid files)

2019-10-28 Thread Debian Bug Tracking System
Your message dated Mon, 28 Oct 2019 12:34:12 + with message-id and subject line Bug#924569: fixed in kopanocore 8.7.0-4 has caused the Debian Bug report #924569, regarding kopano-server: SysV init scripts use wrong pid files to be marked as done. This means that you claim that the problem has

Bug#943494: marked as done (vokoscreen: outputs black video)

2019-10-28 Thread Debian Bug Tracking System
Your message dated Mon, 28 Oct 2019 08:42:19 -0300 with message-id and subject line Re: Bug#943494: vokoscreen: wayland issue has caused the Debian Bug report #943494, regarding vokoscreen: outputs black video to be marked as done. This means that you claim that the problem has been dealt with.

Bug#939960: marked as done (libprelude: fails to build with gtk-doc 1.32)

2019-10-28 Thread Debian Bug Tracking System
Your message dated Mon, 28 Oct 2019 11:00:26 + with message-id and subject line Bug#939960: fixed in libprelude 5.1.1-1 has caused the Debian Bug report #939960, regarding libprelude: fails to build with gtk-doc 1.32 to be marked as done. This means that you claim that the problem has been de

Bug#941797: marked as done (ITP: apertium-eval-translator -- Evaluate machine translation output against reference)

2019-10-28 Thread Debian Bug Tracking System
Your message dated Mon, 28 Oct 2019 11:00:13 + with message-id and subject line Bug#941797: fixed in apertium-eval-translator 1.2.1-1 has caused the Debian Bug report #941797, regarding ITP: apertium-eval-translator -- Evaluate machine translation output against reference to be marked as done

Bug#878121: marked as done (OpenBLAS flavors)

2019-10-28 Thread Debian Bug Tracking System
Your message dated Mon, 28 Oct 2019 11:00:49 + with message-id and subject line Bug#878121: fixed in openblas 0.3.7+ds-2 has caused the Debian Bug report #878121, regarding OpenBLAS flavors to be marked as done. This means that you claim that the problem has been dealt with. If this is not th

Bug#935673: marked as done (rust-ring depends on out-of-date rust-untrusted)

2019-10-28 Thread Debian Bug Tracking System
Your message dated Mon, 28 Oct 2019 11:01:05 + with message-id and subject line Bug#935673: fixed in rust-ring 0.16.9-1 has caused the Debian Bug report #935673, regarding rust-ring depends on out-of-date rust-untrusted to be marked as done. This means that you claim that the problem has been

Bug#821028: marked as done (mailutils: Short descriptions should begin with lowercase)

2019-10-28 Thread Debian Bug Tracking System
Your message dated Mon, 28 Oct 2019 11:00:31 + with message-id and subject line Bug#821028: fixed in mailutils 1:3.6-2 has caused the Debian Bug report #821028, regarding mailutils: Short descriptions should begin with lowercase to be marked as done. This means that you claim that the problem

Bug#927135: marked as done (src:rekall: Please update to python3 version)

2019-10-28 Thread Debian Bug Tracking System
Your message dated Mon, 28 Oct 2019 11:01:00 + with message-id and subject line Bug#927135: fixed in rekall 1.7.2~rc1+git20190104+dfsg-1 has caused the Debian Bug report #927135, regarding src:rekall: Please update to python3 version to be marked as done. This means that you claim that the pr

Bug#684344: marked as done (libopenblas-base: please install OpenMP version)

2019-10-28 Thread Debian Bug Tracking System
Your message dated Mon, 28 Oct 2019 11:00:49 + with message-id and subject line Bug#684344: fixed in openblas 0.3.7+ds-2 has caused the Debian Bug report #684344, regarding libopenblas-base: please install OpenMP version to be marked as done. This means that you claim that the problem has bee

Bug#938350: marked as done (remctl: Python2 removal in sid/bullseye)

2019-10-28 Thread Debian Bug Tracking System
Your message dated Mon, 28 Oct 2019 11:01:02 + with message-id and subject line Bug#938350: fixed in remctl 3.16-2 has caused the Debian Bug report #938350, regarding remctl: Python2 removal in sid/bullseye to be marked as done. This means that you claim that the problem has been dealt with.

Bug#943492: marked as done (qgis b-d on python3-all-dev, but doesn't build for all supported python versions)

2019-10-28 Thread Debian Bug Tracking System
Your message dated Mon, 28 Oct 2019 11:00:59 + with message-id and subject line Bug#943492: fixed in qgis 3.4.13+dfsg-1~exp1 has caused the Debian Bug report #943492, regarding qgis b-d on python3-all-dev, but doesn't build for all supported python versions to be marked as done. This means t

Bug#846602: marked as done (lua-compat53: Install lua-compat53.h in /usr/include/lua*/)

2019-10-28 Thread Debian Bug Tracking System
Your message dated Mon, 28 Oct 2019 11:00:28 + with message-id and subject line Bug#846602: fixed in lua-compat53 0.7-1 has caused the Debian Bug report #846602, regarding lua-compat53: Install lua-compat53.h in /usr/include/lua*/ to be marked as done. This means that you claim that the probl

Bug#849721: marked as done (please build mailutils with python3 bindings)

2019-10-28 Thread Debian Bug Tracking System
Your message dated Mon, 28 Oct 2019 11:00:31 + with message-id and subject line Bug#849721: fixed in mailutils 1:3.6-2 has caused the Debian Bug report #849721, regarding please build mailutils with python3 bindings to be marked as done. This means that you claim that the problem has been dea

Bug#938348: marked as done (rekall: Python2 removal in sid/bullseye)

2019-10-28 Thread Debian Bug Tracking System
Your message dated Mon, 28 Oct 2019 11:01:00 + with message-id and subject line Bug#938348: fixed in rekall 1.7.2~rc1+git20190104+dfsg-1 has caused the Debian Bug report #938348, regarding rekall: Python2 removal in sid/bullseye to be marked as done. This means that you claim that the problem

Bug#936982: marked as done (mailutils: Python2 removal in sid/bullseye)

2019-10-28 Thread Debian Bug Tracking System
Your message dated Mon, 28 Oct 2019 11:00:31 + with message-id and subject line Bug#936982: fixed in mailutils 1:3.6-2 has caused the Debian Bug report #936982, regarding mailutils: Python2 removal in sid/bullseye to be marked as done. This means that you claim that the problem has been dealt

Bug#938884: marked as done (zeitgeist: Python2 removal in sid/bullseye)

2019-10-28 Thread Debian Bug Tracking System
Your message dated Mon, 28 Oct 2019 11:01:14 + with message-id and subject line Bug#938884: fixed in zeitgeist 1.0.2-1 has caused the Debian Bug report #938884, regarding zeitgeist: Python2 removal in sid/bullseye to be marked as done. This means that you claim that the problem has been dealt

Bug#886181: marked as done (rrdtool: Please switch to automatic dbgsym package)

2019-10-28 Thread Debian Bug Tracking System
Your message dated Mon, 28 Oct 2019 11:01:04 + with message-id and subject line Bug#886181: fixed in rrdtool 1.7.2-2 has caused the Debian Bug report #886181, regarding rrdtool: Please switch to automatic dbgsym package to be marked as done. This means that you claim that the problem has been

Bug#936904: marked as done (libprelude: Python2 removal in sid/bullseye)

2019-10-28 Thread Debian Bug Tracking System
Your message dated Mon, 28 Oct 2019 11:00:26 + with message-id and subject line Bug#936904: fixed in libprelude 5.1.1-1 has caused the Debian Bug report #936904, regarding libprelude: Python2 removal in sid/bullseye to be marked as done. This means that you claim that the problem has been dea

Bug#911082: marked as done (nautilus-python: please build against python3)

2019-10-28 Thread Debian Bug Tracking System
Your message dated Mon, 28 Oct 2019 11:00:35 + with message-id and subject line Bug#911082: fixed in nautilus-python 1.2.2-3 has caused the Debian Bug report #911082, regarding nautilus-python: please build against python3 to be marked as done. This means that you claim that the problem has b

Bug#942639: marked as done (fix build with Python3.8 + unusual packaging of the debug extension)

2019-10-28 Thread Debian Bug Tracking System
Your message dated Mon, 28 Oct 2019 11:01:04 + with message-id and subject line Bug#942639: fixed in rrdtool 1.7.2-2 has caused the Debian Bug report #942639, regarding fix build with Python3.8 + unusual packaging of the debug extension to be marked as done. This means that you claim that the

Bug#939670: marked as done (gdcm-doc: depends on cruft package.)

2019-10-28 Thread Debian Bug Tracking System
Your message dated Mon, 28 Oct 2019 11:00:16 + with message-id and subject line Bug#939670: fixed in gdcm 3.0.3-1~exp1 has caused the Debian Bug report #939670, regarding gdcm-doc: depends on cruft package. to be marked as done. This means that you claim that the problem has been dealt with.

Bug#943637: marked as done (qgis: b-d on python3-all-dev, but not built for all supported Python3 versions)

2019-10-28 Thread Debian Bug Tracking System
Your message dated Mon, 28 Oct 2019 11:00:59 + with message-id and subject line Bug#943492: fixed in qgis 3.4.13+dfsg-1~exp1 has caused the Debian Bug report #943492, regarding qgis: b-d on python3-all-dev, but not built for all supported Python3 versions to be marked as done. This means tha

Bug#859698: marked as done (Stressant requires smartctl to run)

2019-10-28 Thread Debian Bug Tracking System
Your message dated Mon, 28 Oct 2019 11:01:10 + with message-id and subject line Bug#859698: fixed in stressant 0.5.0 has caused the Debian Bug report #859698, regarding Stressant requires smartctl to run to be marked as done. This means that you claim that the problem has been dealt with. If

Bug#912955: marked as done (python-zeitgeist: depends on deprecated python-gobject-2)

2019-10-28 Thread Debian Bug Tracking System
Your message dated Mon, 28 Oct 2019 11:01:14 + with message-id and subject line Bug#912955: fixed in zeitgeist 1.0.2-1 has caused the Debian Bug report #912955, regarding python-zeitgeist: depends on deprecated python-gobject-2 to be marked as done. This means that you claim that the problem

Bug#937162: marked as done (nototools: Python2 removal in sid/bullseye)

2019-10-28 Thread Debian Bug Tracking System
Your message dated Mon, 28 Oct 2019 11:00:46 + with message-id and subject line Bug#937162: fixed in nototools 0.2.0-1 has caused the Debian Bug report #937162, regarding nototools: Python2 removal in sid/bullseye to be marked as done. This means that you claim that the problem has been dealt

Bug#938573: marked as done (stressant: Python2 removal in sid/bullseye)

2019-10-28 Thread Debian Bug Tracking System
Your message dated Mon, 28 Oct 2019 11:01:10 + with message-id and subject line Bug#938573: fixed in stressant 0.5.0 has caused the Debian Bug report #938573, regarding stressant: Python2 removal in sid/bullseye to be marked as done. This means that you claim that the problem has been dealt w

Bug#663740: marked as done (python-zeitgeist: Drop obsolete python-gobject dependency)

2019-10-28 Thread Debian Bug Tracking System
Your message dated Mon, 28 Oct 2019 11:01:14 + with message-id and subject line Bug#663740: fixed in zeitgeist 1.0.2-1 has caused the Debian Bug report #663740, regarding python-zeitgeist: Drop obsolete python-gobject dependency to be marked as done. This means that you claim that the problem

Processed: RFS: austin/1.0.0-1 -- Frame stack sampler for CPython

2019-10-28 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > close 942738 Bug #942738 [sponsorship-requests] RFS: austin/1.0.0-1 -- Frame stack sampler for CPython Marked Bug as done > stop Stopping processing here. Please contact me if you need assistance. -- 942738: https://bugs.debian.org/cgi-bin/bugr

Bug#937295: marked as done (pivy: Python2 removal in sid/bullseye)

2019-10-28 Thread Debian Bug Tracking System
Your message dated Mon, 28 Oct 2019 10:04:20 + with message-id and subject line Bug#937295: fixed in pivy 0.6.4-2 has caused the Debian Bug report #937295, regarding pivy: Python2 removal in sid/bullseye to be marked as done. This means that you claim that the problem has been dealt with. If

Bug#943696: marked as done (qgit: Migrate to new fork GitQClient)

2019-10-28 Thread Debian Bug Tracking System
Your message dated Mon, 28 Oct 2019 14:17:27 +0500 with message-id <20191028091727.ga5...@belkar.wrar.name> and subject line Re: Bug#943696: qgit: Migrate to new fork GitQClient has caused the Debian Bug report #943696, regarding qgit: Migrate to new fork GitQClient to be marked as done. This mean

Bug#943689: marked as done (python-hamcrest: Long description incomplete)

2019-10-28 Thread Debian Bug Tracking System
Your message dated Mon, 28 Oct 2019 08:53:39 + with message-id and subject line Bug#943689: fixed in pyhamcrest 1.8.0-4 has caused the Debian Bug report #943689, regarding python-hamcrest: Long description incomplete to be marked as done. This means that you claim that the problem has been de

Bug#943688: marked as done (src:pyhamcrest: debian/copyright out of date)

2019-10-28 Thread Debian Bug Tracking System
Your message dated Mon, 28 Oct 2019 08:53:39 + with message-id and subject line Bug#943688: fixed in pyhamcrest 1.8.0-4 has caused the Debian Bug report #943688, regarding src:pyhamcrest: debian/copyright out of date to be marked as done. This means that you claim that the problem has been de

Bug#939533: marked as done (task-xfce-desktop: should use libreoffice-gtk3 instead of -gtk2)

2019-10-28 Thread Debian Bug Tracking System
Your message dated Mon, 28 Oct 2019 08:13:49 + with message-id and subject line Bug#939533: fixed in tasksel 3.56 has caused the Debian Bug report #939533, regarding task-xfce-desktop: should use libreoffice-gtk3 instead of -gtk2 to be marked as done. This means that you claim that the proble

Bug#942270: marked as done (task-spanish depends on removed manpages-es)

2019-10-28 Thread Debian Bug Tracking System
Your message dated Mon, 28 Oct 2019 08:13:49 + with message-id and subject line Bug#942270: fixed in tasksel 3.56 has caused the Debian Bug report #942270, regarding task-spanish depends on removed manpages-es to be marked as done. This means that you claim that the problem has been dealt wit

Bug#940278: marked as done (new upstream (1.0))

2019-10-28 Thread Debian Bug Tracking System
Your message dated Mon, 28 Oct 2019 08:12:10 + with message-id and subject line Bug#940278: fixed in gparted 1.0.0-0.1~exp has caused the Debian Bug report #940278, regarding new upstream (1.0) to be marked as done. This means that you claim that the problem has been dealt with. If this is no

Bug#942103: marked as done (tasksel: Move fonts-arphic-* to Suggests for task-chinese-{s,t}-desktop)

2019-10-28 Thread Debian Bug Tracking System
Your message dated Mon, 28 Oct 2019 08:13:49 + with message-id and subject line Bug#942103: fixed in tasksel 3.56 has caused the Debian Bug report #942103, regarding tasksel: Move fonts-arphic-* to Suggests for task-chinese-{s,t}-desktop to be marked as done. This means that you claim that t

Bug#925096: marked as done (Updating the gparted Uploaders list)

2019-10-28 Thread Debian Bug Tracking System
Your message dated Mon, 28 Oct 2019 08:12:10 + with message-id and subject line Bug#925096: fixed in gparted 1.0.0-0.1~exp has caused the Debian Bug report #925096, regarding Updating the gparted Uploaders list to be marked as done. This means that you claim that the problem has been dealt wi

Bug#932818: marked as done (Please add a transitional package for task-print-server?)

2019-10-28 Thread Debian Bug Tracking System
Your message dated Mon, 28 Oct 2019 08:13:49 + with message-id and subject line Bug#932818: fixed in tasksel 3.56 has caused the Debian Bug report #932818, regarding Please add a transitional package for task-print-server? to be marked as done. This means that you claim that the problem has b

Bug#934971: marked as done (libhavege.so: depends on error_exit symbol only provided by the daemon)

2019-10-28 Thread Debian Bug Tracking System
Your message dated Mon, 28 Oct 2019 08:12:15 + with message-id and subject line Bug#934971: fixed in haveged 1.9.8-1 has caused the Debian Bug report #934971, regarding libhavege.so: depends on error_exit symbol only provided by the daemon to be marked as done. This means that you claim that

Bug#883812: marked as done (gparted: Please don't use --enable-xhost-root)

2019-10-28 Thread Debian Bug Tracking System
Your message dated Mon, 28 Oct 2019 08:12:10 + with message-id and subject line Bug#883812: fixed in gparted 1.0.0-0.1~exp has caused the Debian Bug report #883812, regarding gparted: Please don't use --enable-xhost-root to be marked as done. This means that you claim that the problem has bee

Bug#938939: marked as done (haveged.service will break with the upcoming systemd v243)

2019-10-28 Thread Debian Bug Tracking System
Your message dated Mon, 28 Oct 2019 08:12:15 + with message-id and subject line Bug#938939: fixed in haveged 1.9.8-1 has caused the Debian Bug report #938939, regarding haveged.service will break with the upcoming systemd v243 to be marked as done. This means that you claim that the problem h

Bug#875075: marked as done ([openscenegraph] Future Qt4 removal from Buster)

2019-10-28 Thread Debian Bug Tracking System
Your message dated Mon, 28 Oct 2019 08:12:26 + with message-id and subject line Bug#875075: fixed in openscenegraph 3.6.4+dfsg1-1 has caused the Debian Bug report #875075, regarding [openscenegraph] Future Qt4 removal from Buster to be marked as done. This means that you claim that the proble

Bug#913394: marked as done (gparted FTCBFS: Build-Depends: libxml-parser-perl unsatisfiable)

2019-10-28 Thread Debian Bug Tracking System
Your message dated Mon, 28 Oct 2019 08:12:10 + with message-id and subject line Bug#913394: fixed in gparted 1.0.0-0.1~exp has caused the Debian Bug report #913394, regarding gparted FTCBFS: Build-Depends: libxml-parser-perl unsatisfiable to be marked as done. This means that you claim that t