Processed: your mail

2020-04-11 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > fixed 768858 torbrowser-launcher/0.3.2-1 Bug #768858 [torbrowser-launcher] torbrowser-launcher: add (possibly opt-in) audio support to AppArmor profiles Marked as fixed in versions torbrowser-launcher/0.3.2-1. > close 768858 Bug #768858 [torbrows

Bug#955167: marked as done (r-cran-sf: autopkgtest regression)

2020-04-11 Thread Debian Bug Tracking System
Your message dated Sun, 12 Apr 2020 08:06:51 +0200 with message-id and subject line has caused the Debian Bug report #955167, regarding r-cran-sf: autopkgtest regression to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your

Bug#890335: marked as done (Document which download/upload directory is supported by the AppArmor policy)

2020-04-11 Thread Debian Bug Tracking System
Your message dated Sun, 12 Apr 2020 14:17:16 +0900 with message-id and subject line Bug#890335: torbrowser-launcher: couldn't upload has caused the Debian Bug report #890335, regarding Document which download/upload directory is supported by the AppArmor policy to be marked as done. This means

Bug#956461: marked as done (saga: FTBFS with Qhull 2019.1)

2020-04-11 Thread Debian Bug Tracking System
Your message dated Sun, 12 Apr 2020 04:49:53 + with message-id and subject line Bug#956461: fixed in saga 7.3.0+dfsg-4 has caused the Debian Bug report #956461, regarding saga: FTBFS with Qhull 2019.1 to be marked as done. This means that you claim that the problem has been dealt with. If thi

Bug#855374: marked as done ([rhythmbox-plugins] Replaygain plugin does not work)

2020-04-11 Thread Debian Bug Tracking System
Your message dated Sun, 12 Apr 2020 06:41:28 +0200 with message-id <3b5ee0ee699a0a8e1915435139e482f2846f926d.ca...@debian.org> and subject line has caused the Debian Bug report #855374, regarding [rhythmbox-plugins] Replaygain plugin does not work to be marked as done. This means that you claim t

Bug#859624: marked as done ([pitivi] Freezes when attempting to load saved projects)

2020-04-11 Thread Debian Bug Tracking System
Your message dated Sun, 12 Apr 2020 06:25:16 +0200 with message-id <2e9b103c27264ab4bdebdc9474d7e93a160b597b.ca...@debian.org> and subject line has caused the Debian Bug report #859624, regarding [pitivi] Freezes when attempting to load saved projects to be marked as done. This means that you cla

Bug#956148: marked as done (python3-virtualenv: Broken venv/bin/pip when using Python 2.7)

2020-04-11 Thread Debian Bug Tracking System
Your message dated Sun, 12 Apr 2020 03:19:04 + with message-id and subject line Bug#956148: fixed in python-virtualenv 20.0.16-2 has caused the Debian Bug report #956148, regarding python3-virtualenv: Broken venv/bin/pip when using Python 2.7 to be marked as done. This means that you claim th

Bug#956144: marked as done (virtualenv: caching of debian wheels breaks pip-installed virtualenv)

2020-04-11 Thread Debian Bug Tracking System
Your message dated Sun, 12 Apr 2020 03:19:04 + with message-id and subject line Bug#956144: fixed in python-virtualenv 20.0.16-2 has caused the Debian Bug report #956144, regarding virtualenv: caching of debian wheels breaks pip-installed virtualenv to be marked as done. This means that you c

Bug#954878: marked as done (Obsolete suggests on python-pygments)

2020-04-11 Thread Debian Bug Tracking System
Your message dated Sun, 12 Apr 2020 03:19:11 + with message-id and subject line Bug#954878: fixed in ranger 1.9.3-2 has caused the Debian Bug report #954878, regarding Obsolete suggests on python-pygments to be marked as done. This means that you claim that the problem has been dealt with. If

Bug#956429: marked as done (oomd: incorrect information in systemd service file)

2020-04-11 Thread Debian Bug Tracking System
Your message dated Sun, 12 Apr 2020 02:35:24 + with message-id and subject line Bug#956429: fixed in oomd 0.3.2-1 has caused the Debian Bug report #956429, regarding oomd: incorrect information in systemd service file to be marked as done. This means that you claim that the problem has been d

Bug#955844: marked as done (gpick: unnecessarily Build-Depends on deprecated dbus-glib)

2020-04-11 Thread Debian Bug Tracking System
Your message dated Sun, 12 Apr 2020 01:48:31 + with message-id and subject line Bug#955844: fixed in gpick 0.2.6~rc1-3 has caused the Debian Bug report #955844, regarding gpick: unnecessarily Build-Depends on deprecated dbus-glib to be marked as done. This means that you claim that the proble

Bug#922595: marked as done (FTBFS due to PDF compilation failure (against Opencv 4.0.1))

2020-04-11 Thread Debian Bug Tracking System
Your message dated Sun, 12 Apr 2020 01:35:05 + with message-id and subject line Bug#922595: fixed in sdaps 1.9.8-0.1 has caused the Debian Bug report #922595, regarding FTBFS due to PDF compilation failure (against Opencv 4.0.1) to be marked as done. This means that you claim that the problem

Bug#956476: marked as done (libnet-async-ssl-perl: long description contains boilerplate from dh-make-perl)

2020-04-11 Thread Debian Bug Tracking System
Your message dated Sat, 11 Apr 2020 23:48:54 + with message-id and subject line Bug#956476: fixed in libio-async-ssl-perl 0.22-3 has caused the Debian Bug report #956476, regarding libnet-async-ssl-perl: long description contains boilerplate from dh-make-perl to be marked as done. This means

Bug#956044: marked as done (qnapi FTCBFS: calls the build architecture qmake)

2020-04-11 Thread Debian Bug Tracking System
Your message dated Sat, 11 Apr 2020 23:19:28 + with message-id and subject line Bug#956044: fixed in qnapi 0.2.3-2 has caused the Debian Bug report #956044, regarding qnapi FTCBFS: calls the build architecture qmake to be marked as done. This means that you claim that the problem has been dea

Bug#940089: marked as done (debianutils: broken maintainer scripts)

2020-04-11 Thread Debian Bug Tracking System
Your message dated Sat, 11 Apr 2020 22:57:20 + with message-id <20200411225720.ga10...@scru.org> and subject line update-mime has caused the Debian Bug report #940089, regarding debianutils: broken maintainer scripts to be marked as done. This means that you claim that the problem has been dea

Bug#940091: marked as done (debianutils: update-mime error upgrading to version 4.9)

2020-04-11 Thread Debian Bug Tracking System
Your message dated Sat, 11 Apr 2020 22:58:06 + with message-id <20200411225806.ga10...@scru.org> and subject line update-mime has caused the Debian Bug report #940091, regarding debianutils: update-mime error upgrading to version 4.9 to be marked as done. This means that you claim that the pro

Bug#953540: marked as done (aspectc++: FTBFS on armel)

2020-04-11 Thread Debian Bug Tracking System
Your message dated Sat, 11 Apr 2020 22:48:34 + with message-id and subject line Bug#953540: fixed in aspectc++ 1:2.2+git20200405-1 has caused the Debian Bug report #953540, regarding aspectc++: FTBFS on armel to be marked as done. This means that you claim that the problem has been dealt with

Bug#942903: marked as done (libbpf library is from kernel source)

2020-04-11 Thread Debian Bug Tracking System
Your message dated Sat, 11 Apr 2020 22:00:23 + with message-id and subject line Bug#948041: fixed in libbpf 0.0.6-1 has caused the Debian Bug report #948041, regarding libbpf library is from kernel source to be marked as done. This means that you claim that the problem has been dealt with. If

Bug#948041: marked as done (libbpf-dev: please build from https://github.com/libbpf/libbpf)

2020-04-11 Thread Debian Bug Tracking System
Your message dated Sat, 11 Apr 2020 22:00:23 + with message-id and subject line Bug#948041: fixed in libbpf 0.0.6-1 has caused the Debian Bug report #948041, regarding libbpf-dev: please build from https://github.com/libbpf/libbpf to be marked as done. This means that you claim that the probl

Bug#945696: marked as done (lokalize: Python2 removal in sid/bullseye)

2020-04-11 Thread Debian Bug Tracking System
Your message dated Sat, 11 Apr 2020 20:35:28 + with message-id and subject line Bug#945696: fixed in lokalize 4:19.12.0-2 has caused the Debian Bug report #945696, regarding lokalize: Python2 removal in sid/bullseye to be marked as done. This means that you claim that the problem has been dea

Bug#942404: marked as done (discosnp: flaky autopkgtest: discoRes_k_31_c_auto_D_100_P_1_b_0_coherent.fa: No such file or directory)

2020-04-11 Thread Debian Bug Tracking System
Your message dated Sat, 11 Apr 2020 21:50:47 +0200 with message-id and subject line Re: Tests seem to work again has caused the Debian Bug report #942404, regarding discosnp: flaky autopkgtest: discoRes_k_31_c_auto_D_100_P_1_b_0_coherent.fa: No such file or directory to be marked as done. This m

Bug#956475: marked as done (libnet-async-http-perl: should recommend (or at least suggest) libnet-async-ssl-perl)

2020-04-11 Thread Debian Bug Tracking System
Your message dated Sat, 11 Apr 2020 19:48:35 + with message-id and subject line Bug#956475: fixed in libnet-async-http-perl 0.45-2 has caused the Debian Bug report #956475, regarding libnet-async-http-perl: should recommend (or at least suggest) libnet-async-ssl-perl to be marked as done. Th

Bug#924362: marked as done (package fails to configure (postinst))

2020-04-11 Thread Debian Bug Tracking System
Your message dated Sat, 11 Apr 2020 21:15:24 +0200 with message-id <6e97934bf8bd84977c5bf815819517ff5d4ceb14.ca...@gmail.com> and subject line Bug closed has caused the Debian Bug report #924362, regarding package fails to configure (postinst) to be marked as done. This means that you claim that t

Bug#956082: marked as done (ITP: python3-validators -- Python data validation for humans)

2020-04-11 Thread Debian Bug Tracking System
Your message dated Sat, 11 Apr 2020 19:00:09 + with message-id and subject line Bug#956082: fixed in validators 0.14.2-1 has caused the Debian Bug report #956082, regarding ITP: python3-validators -- Python data validation for humans to be marked as done. This means that you claim that the pr

Processed: RFS: genwqe-user/4.0.18-3.1 [NMU, RC] -- accelerated libz implementation (development headers)

2020-04-11 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > close 956386 Bug #956386 [sponsorship-requests] RFS: genwqe-user/4.0.18-3.1 [NMU, RC] -- accelerated libz implementation (development headers) Marked Bug as done > stop Stopping processing here. Please contact me if you need assistance. -- 9563

Processed: RFS: sipxtapi/3.3.0~test17-3.1 [NMU, RC] -- SIP stack, RTP media framework and codecs

2020-04-11 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > close 956416 Bug #956416 [sponsorship-requests] RFS: sipxtapi/3.3.0~test17-3.1 [NMU, RC] -- SIP stack, RTP media framework and codecs Marked Bug as done > stop Stopping processing here. Please contact me if you need assistance. -- 956416: https

Bug#956333: marked as done (catch2: Python2 removal in sid/bullseye)

2020-04-11 Thread Debian Bug Tracking System
Your message dated Sat, 11 Apr 2020 18:33:36 + with message-id and subject line Bug#956333: fixed in catch2 2.11.3-2 has caused the Debian Bug report #956333, regarding catch2: Python2 removal in sid/bullseye to be marked as done. This means that you claim that the problem has been dealt with

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

2020-04-11 Thread Debian Bug Tracking System
Your message dated Sat, 11 Apr 2020 18:22:30 + with message-id and subject line Bug#956425: Removed package(s) from unstable has caused the Debian Bug report #938229, regarding python-trollius: Python2 removal in sid/bullseye to be marked as done. This means that you claim that the problem ha

Bug#956425: marked as done (RM: python-trollius -- RoQA; python2-only; backport of a another project; deprecated upstream; no rdeps)

2020-04-11 Thread Debian Bug Tracking System
Your message dated Sat, 11 Apr 2020 18:22:26 + with message-id and subject line Bug#956425: Removed package(s) from unstable has caused the Debian Bug report #956425, regarding RM: python-trollius -- RoQA; python2-only; backport of a another project; deprecated upstream; no rdeps to be marked

Bug#955641: marked as done (qevercloud still FTBFS with upcoming doxygen 1.8.15)

2020-04-11 Thread Debian Bug Tracking System
Your message dated Sat, 11 Apr 2020 18:20:24 + with message-id and subject line Bug#955641: fixed in qevercloud 3.0.3+ds-6 has caused the Debian Bug report #955641, regarding qevercloud still FTBFS with upcoming doxygen 1.8.15 to be marked as done. This means that you claim that the problem h

Bug#954530: marked as done (python-trollius: FTBFS: tests failed)

2020-04-11 Thread Debian Bug Tracking System
Your message dated Sat, 11 Apr 2020 18:22:30 + with message-id and subject line Bug#956425: Removed package(s) from unstable has caused the Debian Bug report #954530, regarding python-trollius: FTBFS: tests failed to be marked as done. This means that you claim that the problem has been dealt

Bug#937403: marked as done (pycassa: Python2 removal in sid/bullseye)

2020-04-11 Thread Debian Bug Tracking System
Your message dated Sat, 11 Apr 2020 18:18:37 + with message-id and subject line Bug#956468: Removed package(s) from unstable has caused the Debian Bug report #937403, regarding pycassa: Python2 removal in sid/bullseye to be marked as done. This means that you claim that the problem has been d

Bug#806355: marked as done (django-ratelimit: FTBFS with Django 1.9)

2020-04-11 Thread Debian Bug Tracking System
Your message dated Sat, 11 Apr 2020 18:18:10 + with message-id and subject line Bug#956466: Removed package(s) from unstable has caused the Debian Bug report #806355, regarding django-ratelimit: FTBFS with Django 1.9 to be marked as done. This means that you claim that the problem has been de

Bug#849906: marked as done (python-django-ratelimit: please add dependency “Suggests: python-django-ratelimit-doc”)

2020-04-11 Thread Debian Bug Tracking System
Your message dated Sat, 11 Apr 2020 18:18:10 + with message-id and subject line Bug#956466: Removed package(s) from unstable has caused the Debian Bug report #849906, regarding python-django-ratelimit: please add dependency “Suggests: python-django-ratelimit-doc” to be marked as done. This m

Bug#956466: marked as done (RM: django-ratelimit -- RoQA; Depends on Python 2, unmaintained)

2020-04-11 Thread Debian Bug Tracking System
Your message dated Sat, 11 Apr 2020 18:18:06 + with message-id and subject line Bug#956466: Removed package(s) from unstable has caused the Debian Bug report #956466, regarding RM: django-ratelimit -- RoQA; Depends on Python 2, unmaintained to be marked as done. This means that you claim that

Bug#956468: marked as done (RM: pycassa -- RoQA; Depends on Python 2, dead upstream)

2020-04-11 Thread Debian Bug Tracking System
Your message dated Sat, 11 Apr 2020 18:18:34 + with message-id and subject line Bug#956468: Removed package(s) from unstable has caused the Debian Bug report #956468, regarding RM: pycassa -- RoQA; Depends on Python 2, dead upstream to be marked as done. This means that you claim that the pro

Bug#936420: marked as done (django-ratelimit: Python2 removal in sid/bullseye)

2020-04-11 Thread Debian Bug Tracking System
Your message dated Sat, 11 Apr 2020 18:18:10 + with message-id and subject line Bug#956466: Removed package(s) from unstable has caused the Debian Bug report #936420, regarding django-ratelimit: Python2 removal in sid/bullseye to be marked as done. This means that you claim that the problem h

Bug#938612: marked as done (sx: Python2 removal in sid/bullseye)

2020-04-11 Thread Debian Bug Tracking System
Your message dated Sat, 11 Apr 2020 18:17:04 + with message-id and subject line Bug#956444: Removed package(s) from unstable has caused the Debian Bug report #938612, regarding sx: Python2 removal in sid/bullseye to be marked as done. This means that you claim that the problem has been dealt

Bug#939995: marked as done (libltcsmpte: no reverse dependencies - remove from the archive?)

2020-04-11 Thread Debian Bug Tracking System
Your message dated Sat, 11 Apr 2020 18:15:08 + with message-id and subject line Bug#956432: Removed package(s) from unstable has caused the Debian Bug report #939995, regarding libltcsmpte: no reverse dependencies - remove from the archive? to be marked as done. This means that you claim that

Bug#956432: marked as done (RM: libltcsmpte -- RoQA; Maintainer Inactive; Upstream Deprecated; No Reverse Dependencies)

2020-04-11 Thread Debian Bug Tracking System
Your message dated Sat, 11 Apr 2020 18:15:03 + with message-id and subject line Bug#956432: Removed package(s) from unstable has caused the Debian Bug report #956432, regarding RM: libltcsmpte -- RoQA; Maintainer Inactive; Upstream Deprecated; No Reverse Dependencies to be marked as done. Th

Bug#956444: marked as done (RM: sx -- RoM; abandoned upstream and Python 2 only)

2020-04-11 Thread Debian Bug Tracking System
Your message dated Sat, 11 Apr 2020 18:16:55 + with message-id and subject line Bug#956444: Removed package(s) from unstable has caused the Debian Bug report #956444, regarding RM: sx -- RoM; abandoned upstream and Python 2 only to be marked as done. This means that you claim that the problem

Bug#847264: marked as done (Updating the python-cdd Uploaders list)

2020-04-11 Thread Debian Bug Tracking System
Your message dated Sat, 11 Apr 2020 18:17:25 + with message-id and subject line Bug#956445: Removed package(s) from unstable has caused the Debian Bug report #847264, regarding Updating the python-cdd Uploaders list to be marked as done. This means that you claim that the problem has been dea

Bug#956448: marked as done (RM: ros-pcl-conversions -- ROM; integrated into ros-perception-pcl)

2020-04-11 Thread Debian Bug Tracking System
Your message dated Sat, 11 Apr 2020 18:17:40 + with message-id and subject line Bug#956448: Removed package(s) from unstable has caused the Debian Bug report #956448, regarding RM: ros-pcl-conversions -- ROM; integrated into ros-perception-pcl to be marked as done. This means that you claim t

Bug#956445: marked as done (RM: python-cdd -- RoQA; Depends on Python 2, dead upstream, unmaintained)

2020-04-11 Thread Debian Bug Tracking System
Your message dated Sat, 11 Apr 2020 18:17:19 + with message-id and subject line Bug#956445: Removed package(s) from unstable has caused the Debian Bug report #956445, regarding RM: python-cdd -- RoQA; Depends on Python 2, dead upstream, unmaintained to be marked as done. This means that you

Bug#840175: marked as done (sx: new upstream: SX 2.3)

2020-04-11 Thread Debian Bug Tracking System
Your message dated Sat, 11 Apr 2020 18:17:04 + with message-id and subject line Bug#956444: Removed package(s) from unstable has caused the Debian Bug report #840175, regarding sx: new upstream: SX 2.3 to be marked as done. This means that you claim that the problem has been dealt with. If th

Bug#895090: marked as done (sx: Please replace 'c_rehash' with 'openssl rehash')

2020-04-11 Thread Debian Bug Tracking System
Your message dated Sat, 11 Apr 2020 18:17:04 + with message-id and subject line Bug#956444: Removed package(s) from unstable has caused the Debian Bug report #895090, regarding sx: Please replace 'c_rehash' with 'openssl rehash' to be marked as done. This means that you claim that the problem

Bug#885544: marked as done (sx: homepage points to an oops-page)

2020-04-11 Thread Debian Bug Tracking System
Your message dated Sat, 11 Apr 2020 18:17:04 + with message-id and subject line Bug#956444: Removed package(s) from unstable has caused the Debian Bug report #885544, regarding sx: homepage points to an oops-page to be marked as done. This means that you claim that the problem has been dealt

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

2020-04-11 Thread Debian Bug Tracking System
Your message dated Sat, 11 Apr 2020 18:17:25 + with message-id and subject line Bug#956445: Removed package(s) from unstable has caused the Debian Bug report #937635, regarding python-cdd: Python2 removal in sid/bullseye to be marked as done. This means that you claim that the problem has bee

Bug#956421: marked as done (RM: editobj -- RoQA; Depends on Python 2, outdated, unmaintained)

2020-04-11 Thread Debian Bug Tracking System
Your message dated Sat, 11 Apr 2020 18:13:04 + with message-id and subject line Bug#956421: Removed package(s) from unstable has caused the Debian Bug report #956421, regarding RM: editobj -- RoQA; Depends on Python 2, outdated, unmaintained to be marked as done. This means that you claim tha

Bug#938947: marked as done (mpris-remote: Python2 removal in sid/bullseye)

2020-04-11 Thread Debian Bug Tracking System
Your message dated Sat, 11 Apr 2020 18:13:32 + with message-id and subject line Bug#956422: Removed package(s) from unstable has caused the Debian Bug report #938947, regarding mpris-remote: Python2 removal in sid/bullseye to be marked as done. This means that you claim that the problem has b

Bug#953999: marked as done (RM: iwyu [armel] -- ANAIS; no longer built on armel)

2020-04-11 Thread Debian Bug Tracking System
Your message dated Sat, 11 Apr 2020 18:12:40 + with message-id and subject line Bug#953999: Removed package(s) from unstable has caused the Debian Bug report #953999, regarding RM: iwyu [armel] -- ANAIS; no longer built on armel to be marked as done. This means that you claim that the problem

Bug#956422: marked as done (RM: mpris-remote -- RoQA; Depends on Python 2, dead upstream, unmaintained)

2020-04-11 Thread Debian Bug Tracking System
Your message dated Sat, 11 Apr 2020 18:13:27 + with message-id and subject line Bug#956422: Removed package(s) from unstable has caused the Debian Bug report #956422, regarding RM: mpris-remote -- RoQA; Depends on Python 2, dead upstream, unmaintained to be marked as done. This means that yo

Bug#936467: marked as done (editobj: Python2 removal in sid/bullseye)

2020-04-11 Thread Debian Bug Tracking System
Your message dated Sat, 11 Apr 2020 18:13:10 + with message-id and subject line Bug#956421: Removed package(s) from unstable has caused the Debian Bug report #936467, regarding editobj: Python2 removal in sid/bullseye to be marked as done. This means that you claim that the problem has been d

Bug#168966: marked as done (reports wrong line number for error in sudoers)

2020-04-11 Thread Debian Bug Tracking System
Your message dated Sat, 11 Apr 2020 11:58:03 -0600 with message-id <87eestj45w@gag.com> and subject line fixed long ago has caused the Debian Bug report #168966, regarding reports wrong line number for error in sudoers to be marked as done. This means that you claim that the problem has been d

Bug#283161: marked as done (visudo: please use /tmp or other location for temporary file)

2020-04-11 Thread Debian Bug Tracking System
Your message dated Sat, 11 Apr 2020 11:57:09 -0600 with message-id <87h7xpj47e@gag.com> and subject line not a bug has caused the Debian Bug report #283161, regarding visudo: please use /tmp or other location for temporary file to be marked as done. This means that you claim that the problem h

Bug#279172: marked as done (sudo does not work correctly with multiple NSS services)

2020-04-11 Thread Debian Bug Tracking System
Your message dated Sat, 11 Apr 2020 11:59:43 -0600 with message-id <875ze5j434@gag.com> and subject line fixed long ago has caused the Debian Bug report #279172, regarding sudo does not work correctly with multiple NSS services to be marked as done. This means that you claim that the problem h

Bug#950080: marked as done (kwartz-client: modifies conffiles (policy 10.7.3): /etc/kwartz-cloud.conf)

2020-04-11 Thread Debian Bug Tracking System
Your message dated Sat, 11 Apr 2020 18:05:12 + with message-id and subject line Bug#950080: fixed in kwartz-client 1.5-1 has caused the Debian Bug report #950080, regarding kwartz-client: modifies conffiles (policy 10.7.3): /etc/kwartz-cloud.conf to be marked as done. This means that you cla

Bug#640671: marked as done (sudoers gid: Operation not permitted)

2020-04-11 Thread Debian Bug Tracking System
Your message dated Sat, 11 Apr 2020 11:59:00 -0600 with message-id <878sj1j44b@gag.com> and subject line fixed in 1.8.3 has caused the Debian Bug report #640671, regarding sudoers gid: Operation not permitted to be marked as done. This means that you claim that the problem has been dealt with.

Bug#660746: marked as done (sudo: segfault when run with -i and -g but not -u)

2020-04-11 Thread Debian Bug Tracking System
Your message dated Sat, 11 Apr 2020 11:58:32 -0600 with message-id <87blnxj453@gag.com> and subject line fixed in 1.8.4 has caused the Debian Bug report #660746, regarding sudo: segfault when run with -i and -g but not -u to be marked as done. This means that you claim that the problem has bee

Bug#956409: marked as done (kwartz-client: German translation of the debconf messages)

2020-04-11 Thread Debian Bug Tracking System
Your message dated Sat, 11 Apr 2020 18:05:12 + with message-id and subject line Bug#956409: fixed in kwartz-client 1.5-1 has caused the Debian Bug report #956409, regarding kwartz-client: German translation of the debconf messages to be marked as done. This means that you claim that the probl

Bug#924696: marked as done (debian-faq on debian website: chinese translation not updated to latest version)

2020-04-11 Thread Debian Bug Tracking System
Your message dated Sat, 11 Apr 2020 18:02:33 + with message-id <5e920639b09fa_73e92ad2dbc405bc95...@godard.mail> and subject line Bug#924696 fixed in www.debian.org has caused the Debian Bug report #924696, regarding debian-faq on debian website: chinese translation not updated to latest versi

Bug#954611: marked as done (genwqe-user: FTBFS: hw_defs.h:36:21: error: static declaration of ‘gettid’ follows non-static declaration)

2020-04-11 Thread Debian Bug Tracking System
Your message dated Sat, 11 Apr 2020 17:34:31 + with message-id and subject line Bug#954611: fixed in genwqe-user 4.0.18-3.1 has caused the Debian Bug report #954611, regarding genwqe-user: FTBFS: hw_defs.h:36:21: error: static declaration of ‘gettid’ follows non-static declaration to be marke

Bug#947595: marked as done (singularity: New upstream pre-release 1.0a2)

2020-04-11 Thread Debian Bug Tracking System
Your message dated Sat, 11 Apr 2020 17:37:14 + with message-id and subject line Bug#947595: fixed in singularity 1.0b1-1 has caused the Debian Bug report #947595, regarding singularity: New upstream pre-release 1.0a2 to be marked as done. This means that you claim that the problem has been de

Bug#954547: marked as done (sipxtapi: FTBFS: os/linux/OsTaskLinux.cpp:52:19: error: ‘int gettid()’ was declared ‘extern’ and later ‘static’ [-fpermissive])

2020-04-11 Thread Debian Bug Tracking System
Your message dated Sat, 11 Apr 2020 17:24:05 + with message-id and subject line Bug#954547: fixed in sipxtapi 3.3.0~test17-3.1 has caused the Debian Bug report #954547, regarding sipxtapi: FTBFS: os/linux/OsTaskLinux.cpp:52:19: error: ‘int gettid()’ was declared ‘extern’ and later ‘static’ [-

Bug#936802: marked as done (kmer: Python2 removal in sid/bullseye)

2020-04-11 Thread Debian Bug Tracking System
Your message dated Sat, 11 Apr 2020 16:52:25 + with message-id and subject line Bug#936802: fixed in kmer 0~20150903+r2013-7 has caused the Debian Bug report #936802, regarding kmer: Python2 removal in sid/bullseye to be marked as done. This means that you claim that the problem has been deal

Processed: RFS: libbpf/0.0.6-1 -- eBPF helper library (development files)

2020-04-11 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > close 956360 Bug #956360 [sponsorship-requests] RFS: libbpf/0.0.6-1 -- eBPF helper library (development files) Marked Bug as done > stop Stopping processing here. Please contact me if you need assistance. -- 956360: https://bugs.debian.org/cgi-

Bug#926500: marked as done (freecad: FreeCad crashes when attemting to edit a existing sketch)

2020-04-11 Thread Debian Bug Tracking System
Your message dated Sat, 11 Apr 2020 18:45:23 +0200 with message-id and subject line Re: freecad: FreeCad crashes when attemting to edit a existing sketch has caused the Debian Bug report #926500, regarding freecad: FreeCad crashes when attemting to edit a existing sketch to be marked as done. Th

Bug#956280: marked as done (shapelib: change in ronn 0.9.0 breaks generation of manpages)

2020-04-11 Thread Debian Bug Tracking System
Your message dated Sat, 11 Apr 2020 15:53:52 + with message-id and subject line Bug#956280: fixed in shapelib 1.5.0-2 has caused the Debian Bug report #956280, regarding shapelib: change in ronn 0.9.0 breaks generation of manpages to be marked as done. This means that you claim that the probl

Bug#830078: marked as done (gemspec not installed)

2020-04-11 Thread Debian Bug Tracking System
Your message dated Sat, 11 Apr 2020 15:11:46 + with message-id and subject line Bug#830078: fixed in ruby-cssmin 1.0.3-5 has caused the Debian Bug report #830078, regarding gemspec not installed to be marked as done. This means that you claim that the problem has been dealt with. If this is n

Bug#956449: marked as done (exclude packaged node modules from babel-loader)

2020-04-11 Thread Debian Bug Tracking System
Your message dated Sat, 11 Apr 2020 15:04:57 + with message-id and subject line Bug#956449: fixed in gitlab 12.9.2-4 has caused the Debian Bug report #956449, regarding exclude packaged node modules from babel-loader to be marked as done. This means that you claim that the problem has been de

Bug#944081: marked as done (libmoo-perl: Please recommend libnamespace-clean-perl)

2020-04-11 Thread Debian Bug Tracking System
Your message dated Sat, 11 Apr 2020 15:05:28 + with message-id and subject line Bug#944081: fixed in libmoo-perl 2.004000-1 has caused the Debian Bug report #944081, regarding libmoo-perl: Please recommend libnamespace-clean-perl to be marked as done. This means that you claim that the proble

Bug#955831: marked as done (libsocl-contrib-1.3-0: please rebuild against new libhdf5 packages on sid)

2020-04-11 Thread Debian Bug Tracking System
Your message dated Sat, 11 Apr 2020 14:50:09 + with message-id and subject line Bug#955831: fixed in starpu 1.3.3+dfsg-3 has caused the Debian Bug report #955831, regarding libsocl-contrib-1.3-0: please rebuild against new libhdf5 packages on sid to be marked as done. This means that you cla

Bug#955794: marked as done (starpu-contrib: switch B-D to nvidia-cuda-toolkit-gcc)

2020-04-11 Thread Debian Bug Tracking System
Your message dated Sat, 11 Apr 2020 14:50:09 + with message-id and subject line Bug#955794: fixed in starpu 1.3.3+dfsg-3 has caused the Debian Bug report #955794, regarding starpu-contrib: switch B-D to nvidia-cuda-toolkit-gcc to be marked as done. This means that you claim that the problem h

Bug#914342: marked as done (ruby-validate-email: Source doesn't contain testsuite.)

2020-04-11 Thread Debian Bug Tracking System
Your message dated Sat, 11 Apr 2020 14:49:42 + with message-id and subject line Bug#914342: fixed in ruby-validate-email 0.1.6+git-1 has caused the Debian Bug report #914342, regarding ruby-validate-email: Source doesn't contain testsuite. to be marked as done. This means that you claim that

Bug#955831: marked as done (libsocl-contrib-1.3-0: please rebuild against new libhdf5 packages on sid)

2020-04-11 Thread Debian Bug Tracking System
Your message dated Sat, 11 Apr 2020 14:50:54 + with message-id and subject line Bug#955831: fixed in starpu-contrib 1.3.3+dfsg-3 has caused the Debian Bug report #955831, regarding libsocl-contrib-1.3-0: please rebuild against new libhdf5 packages on sid to be marked as done. This means that

Bug#955794: marked as done (starpu-contrib: switch B-D to nvidia-cuda-toolkit-gcc)

2020-04-11 Thread Debian Bug Tracking System
Your message dated Sat, 11 Apr 2020 14:50:54 + with message-id and subject line Bug#955794: fixed in starpu-contrib 1.3.3+dfsg-3 has caused the Debian Bug report #955794, regarding starpu-contrib: switch B-D to nvidia-cuda-toolkit-gcc to be marked as done. This means that you claim that the p

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

2020-04-11 Thread Debian Bug Tracking System
Your message dated Sat, 11 Apr 2020 14:42:35 + with message-id and subject line Bug#954616: fixed in python-aioopenssl 0.5.1-1 has caused the Debian Bug report #954616, regarding python-aioopenssl: FTBFS: dh_auto_test: error: pybuild --test -i python{version} -p 3.8 returned exit code 13 to b

Bug#955791: marked as done (RFS: libkqueue/2.3.1-1 -- cross-platform library for kernel event notification)

2020-04-11 Thread Debian Bug Tracking System
Your message dated Sat, 11 Apr 2020 10:39:19 -0400 with message-id <304696edf66945785eb090c327d1f90a21b8fa0a.ca...@debian.org> and subject line Re: Bug#955791: RFS: libkqueue/2.3.1-1 -- cross-platform library for kernel event notification has caused the Debian Bug report #955791, regarding RFS: li

Bug#956314: marked as done (ITS: can-utils maintenance)

2020-04-11 Thread Debian Bug Tracking System
Your message dated Sat, 11 Apr 2020 14:37:21 + with message-id and subject line Bug#956314: fixed in can-utils 2020.02.04-1 has caused the Debian Bug report #956314, regarding ITS: can-utils maintenance to be marked as done. This means that you claim that the problem has been dealt with. If t

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

2020-04-11 Thread Debian Bug Tracking System
Your message dated Sat, 11 Apr 2020 13:21:02 + with message-id and subject line Bug#954521: fixed in golang-github-go-errors-errors 1.0.1-4 has caused the Debian Bug report #954521, regarding golang-github-go-errors-errors: FTBFS: dh_auto_test: error: cd obj-x86_64-linux-gnu && go test -vet=o

Bug#956441: marked as done (cyrus-imapd: autopkgtests failure)

2020-04-11 Thread Debian Bug Tracking System
Your message dated Sat, 11 Apr 2020 12:49:44 + with message-id and subject line Bug#956441: fixed in cyrus-imapd 3.0.13-5 has caused the Debian Bug report #956441, regarding cyrus-imapd: autopkgtests failure to be marked as done. This means that you claim that the problem has been dealt with.

Bug#954497: marked as done (siconos: FTBFS: cc: error: 654: No such file or directory)

2020-04-11 Thread Debian Bug Tracking System
Your message dated Sat, 11 Apr 2020 14:44:28 +0200 with message-id <20200411124428.ga3...@angband.pl> and subject line fixed has caused the Debian Bug report #954497, regarding siconos: FTBFS: cc: error: 654: No such file or directory to be marked as done. This means that you claim that the proble

Bug#934117: marked as done (torbrowser-launcher: Does not remove obsolete /etc/apparmor.d/torbrowser.Browser.plugin-container conffile on upgrade)

2020-04-11 Thread Debian Bug Tracking System
Your message dated Sat, 11 Apr 2020 21:31:30 +0900 with message-id and subject line Re: [Pkg-privacy-maintainers] Bug#934117: torbrowser-launcher: Does not remove obsolete /etc/apparmor.d/torbrowser.Browser.plugin-container conffile on upgrade has caused the Debian Bug report #934117, regarding

Processed (with 1 error): Re: [Pkg-privacy-maintainers] Bug#944823: it's same as #942901 and the workaround shared by Paul works.

2020-04-11 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > close 944823 Bug #944823 [torbrowser-launcher] Failure to open shm and ggx failures. Marked Bug as done > forcemerge 944823 942901 Bug #944823 {Done: Roger Shimizu } [torbrowser-launcher] Failure to open shm and ggx failures. Bug #942901 {Done: R

Bug#921486: marked as done (ruby-adsf: make test suite compatible with $http_proxy)

2020-04-11 Thread Debian Bug Tracking System
Your message dated Sat, 11 Apr 2020 10:49:02 + with message-id and subject line Bug#921486: fixed in ruby-adsf 1.4.3+dfsg1-1 has caused the Debian Bug report #921486, regarding ruby-adsf: make test suite compatible with $http_proxy to be marked as done. This means that you claim that the prob

Bug#920535: marked as done (autopkg tests succeed, but have some output on stderr)

2020-04-11 Thread Debian Bug Tracking System
Your message dated Sat, 11 Apr 2020 12:49:20 +0200 with message-id <73b1aa0944b1e890968ffbc396659d5d3823296c.ca...@debian.org> and subject line Re: autopkg tests succeed, but have some output on stderr has caused the Debian Bug report #920535, regarding autopkg tests succeed, but have some output o

Bug#825861: marked as done (freecad: After update to 0.16 design contents are "invisible", ViewProvider2DObjectPython on console)

2020-04-11 Thread Debian Bug Tracking System
Your message dated Sat, 11 Apr 2020 12:43:46 +0200 with message-id <41ddba120315b4dfd9ef1851a2bade50fa5e74db.ca...@debian.org> and subject line Re: Bug#825861: freecad: After update to 0.16 design contents are "invisible", ViewProvider2DObjectPython on console has caused the Debian Bug report #825

Bug#933876: marked as done (freecad: Can't create a new file in FreeCAD in Debian 10 Gnome Edition)

2020-04-11 Thread Debian Bug Tracking System
Your message dated Sat, 11 Apr 2020 12:40:54 +0200 with message-id <07370712472c7c02c20b1049346a7f87ccbbec47.ca...@debian.org> and subject line Re: freecad: Can't create a new file in FreeCAD in Debian 10 Gnome Edition has caused the Debian Bug report #933876, regarding freecad: Can't create a new

Bug#810161: marked as done (New online b43 firmware installer)

2020-04-11 Thread Debian Bug Tracking System
Your message dated Sat, 11 Apr 2020 10:33:34 + with message-id and subject line Bug#810161: fixed in b43-fwcutter 1:019-5 has caused the Debian Bug report #810161, regarding New online b43 firmware installer to be marked as done. This means that you claim that the problem has been dealt with.

Bug#760813: marked as done (firmware-b43-installer: Package device detection fails without PCI hardware)

2020-04-11 Thread Debian Bug Tracking System
Your message dated Sat, 11 Apr 2020 10:33:34 + with message-id and subject line Bug#760813: fixed in b43-fwcutter 1:019-5 has caused the Debian Bug report #760813, regarding firmware-b43-installer: Package device detection fails without PCI hardware to be marked as done. This means that you

Bug#956442: marked as done (nmu: python-mapnik_1:0.0~20200224-7da019cf9-1+b1)

2020-04-11 Thread Debian Bug Tracking System
Your message dated Sat, 11 Apr 2020 12:32:22 +0200 with message-id <20200411103222.ga1614...@ramacher.at> and subject line Re: Bug#956442: nmu: python-mapnik_1:0.0~20200224-7da019cf9-1+b1 has caused the Debian Bug report #956442, regarding nmu: python-mapnik_1:0.0~20200224-7da019cf9-1+b1 to be mar

Bug#925277: marked as done (freecad: there's no manpage entry)

2020-04-11 Thread Debian Bug Tracking System
Your message dated Sat, 11 Apr 2020 12:22:58 +0200 with message-id <402ff3f13023dc356f3a066ee09b9ddca42aee65.ca...@debian.org> and subject line Re: Bug#925277: freecad: there's no manpage entry has caused the Debian Bug report #925277, regarding freecad: there's no manpage entry to be marked as don

Processed: closing 918356

2020-04-11 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > close 918356 Bug #918356 [src:ruby-prawn-svg] ruby-prawn-svg: Vcs doesn't exist Marked Bug as done > thanks Stopping processing here. Please contact me if you need assistance. -- 918356: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=918356 D

Bug#882532: marked as done (freecad: FreeCADGuiInit.py not existing but mentioned in the log file)

2020-04-11 Thread Debian Bug Tracking System
Your message dated Sat, 11 Apr 2020 12:07:48 +0200 with message-id <14b00d3d314445d27179ae8f8589f8c8177510f8.ca...@debian.org> and subject line Re: freecad: FreeCADGuiInit.py not existing but mentioned in the log file has caused the Debian Bug report #882532, regarding freecad: FreeCADGuiInit.py n

Bug#882509: marked as done (freecad: manpage is not up to date and miss some informations)

2020-04-11 Thread Debian Bug Tracking System
Your message dated Sat, 11 Apr 2020 11:54:17 +0200 with message-id <40879f0d74aadc61d3a2d9f087c90408c694a811.ca...@debian.org> and subject line Re: freecad: manpage is not up to date and miss some informations has caused the Debian Bug report #882509, regarding freecad: manpage is not up to date a

Bug#860790: marked as done (freecad: "couldn't create parsetab in /usr/lib....")

2020-04-11 Thread Debian Bug Tracking System
Your message dated Sat, 11 Apr 2020 11:48:18 +0200 with message-id <0370536e6906b83271f603e9573bf45f1b45e9a9.ca...@debian.org> and subject line Re: freecad: "couldn't create parsetab in /usr/lib" has caused the Debian Bug report #860790, regarding freecad: "couldn't create parsetab in /usr/lib.

Bug#678258: marked as done (Need to upgrade firmware-b43-installer package files, to continue to work with linux 3.2.X kernel)

2020-04-11 Thread Debian Bug Tracking System
Your message dated Sat, 11 Apr 2020 11:37:35 +0200 with message-id <20200411093735.ga1142...@home.ouaza.com> and subject line Old bug, no longer relevant has caused the Debian Bug report #678258, regarding Need to upgrade firmware-b43-installer package files, to continue to work with linux 3.2.X k

Bug#813442: marked as done (SIGSEGV in _PyObject_GC_Malloc while drawing DWires)

2020-04-11 Thread Debian Bug Tracking System
Your message dated Sat, 11 Apr 2020 11:29:05 +0200 with message-id and subject line Re: cannot reproduce has caused the Debian Bug report #813442, regarding SIGSEGV in _PyObject_GC_Malloc while drawing DWires to be marked as done. This means that you claim that the problem has been dealt with. If

Bug#718569: marked as done (mouse-selectability of objects is lost right after saving a project)

2020-04-11 Thread Debian Bug Tracking System
Your message dated Sat, 11 Apr 2020 11:27:05 +0200 with message-id <1bb51794c78162dfb5c57f4e63dec9e6505927b1.ca...@debian.org> and subject line Re: mouse-selectability of objects is lost right after saving a project has caused the Debian Bug report #718569, regarding mouse-selectability of objects

Bug#778509: marked as done (freecad crashes whis SIGSEV when attempting to save a file created in a previous session)

2020-04-11 Thread Debian Bug Tracking System
Your message dated Sat, 11 Apr 2020 11:23:34 +0200 with message-id and subject line Re: freecad crashes whis SIGSEV when attempting to save a file created in a previous session has caused the Debian Bug report #778509, regarding freecad crashes whis SIGSEV when attempting to save a file created i

  1   2   >