Bug#1010002: libgeos++-dev: Missing files or misconfigured build

2022-04-21 Thread Pierre Gergondet
Package: libgeos++-dev Version: 3.10.2-1 Severity: grave Justification: renders package unusable X-Debbugs-Cc: pierre.gergon...@gmail.com Dear Maintainer, libgeos++-dev is missing .inl files required to build programs with the C++ interface. When GEOS is built, the GEOS_INLINE macro is defined.

Processed: forcibly merging 953032 1009920

2022-04-21 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > forcemerge 953032 1009920 Bug #953032 {Done: Timo Aaltonen } [x11-xkb-utils] xkbcomp: Internal error: Could not resolve keysym XF86FullScreen Bug #994036 {Done: Timo Aaltonen } [x11-xkb-utils] x11-xkb-utils: xkbcomp gives internal errors on unkn

Bug#997414: marked as done (debomatic: FTBFS: '! LaTeX Error: File `tgtermes.sty' not found.')

2022-04-21 Thread Debian Bug Tracking System
Your message dated Fri, 22 Apr 2022 06:33:43 + with message-id and subject line Bug#997414: fixed in debomatic 0.25+git20210925-2 has caused the Debian Bug report #997414, regarding debomatic: FTBFS: '! LaTeX Error: File `tgtermes.sty' not found.' to be marked as done. This means that you c

Bug#1009168: marked as done (gzip: CVE-2022-1271: zgrep: arbitrary-file-write vulnerability)

2022-04-21 Thread Debian Bug Tracking System
Your message dated Fri, 22 Apr 2022 06:17:07 + with message-id and subject line Bug#1009168: fixed in gzip 1.10-4+deb11u1 has caused the Debian Bug report #1009168, regarding gzip: CVE-2022-1271: zgrep: arbitrary-file-write vulnerability to be marked as done. This means that you claim that th

Bug#1009167: marked as done (xz-utils: CVE-2022-1271: xzgrep: arbitrary-file-write vulnerability)

2022-04-21 Thread Debian Bug Tracking System
Your message dated Fri, 22 Apr 2022 06:17:10 + with message-id and subject line Bug#1009167: fixed in xz-utils 5.2.5-2.1~deb11u1 has caused the Debian Bug report #1009167, regarding xz-utils: CVE-2022-1271: xzgrep: arbitrary-file-write vulnerability to be marked as done. This means that you c

Processed: Re: Bug#1009199: src:tcpreplay: fails to migrate to testing for too long: ftbfs on armhf

2022-04-21 Thread Debian Bug Tracking System
Processing control commands: > tags 1009199 confirmed Bug #1009199 {Done: Paul Gevers } [src:tcpreplay] src:tcpreplay: fails to migrate to testing for too long: ftbfs on armhf Added tag(s) confirmed. -- 1009199: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1009199 Debian Bug Tracking Syste

Bug#1009199: src:tcpreplay: fails to migrate to testing for too long: ftbfs on armhf

2022-04-21 Thread Christoph Biedl
Control: tags 1009199 confirmed Paul Gevers wrote... > The Release Team considers packages that are out-of-sync between testing and > unstable for more than 60 days as having a Release Critical bug in testing > [1]. Your package src:tcpreplay has been trying to migrate for 61 days [2]. > Hence, I

Bug#1009168: marked as done (gzip: CVE-2022-1271: zgrep: arbitrary-file-write vulnerability)

2022-04-21 Thread Debian Bug Tracking System
Your message dated Fri, 22 Apr 2022 06:02:29 + with message-id and subject line Bug#1009168: fixed in gzip 1.9-3+deb10u1 has caused the Debian Bug report #1009168, regarding gzip: CVE-2022-1271: zgrep: arbitrary-file-write vulnerability to be marked as done. This means that you claim that the

Bug#1009167: marked as done (xz-utils: CVE-2022-1271: xzgrep: arbitrary-file-write vulnerability)

2022-04-21 Thread Debian Bug Tracking System
Your message dated Fri, 22 Apr 2022 06:02:33 + with message-id and subject line Bug#1009167: fixed in xz-utils 5.2.4-1+deb10u1 has caused the Debian Bug report #1009167, regarding xz-utils: CVE-2022-1271: xzgrep: arbitrary-file-write vulnerability to be marked as done. This means that you cla

Bug#1009998: gvfs-backends: Unable to access smb://host/sharing on any file manager after upgrade

2022-04-21 Thread mount -t cifs unable to mount shared folders on windows server active director
Package: gvfs-backends Version: 1.50.0-1 Severity: grave Tags: a11y Justification: renders package unusable X-Debbugs-Cc: draco...@gmail.com Dear Maintainer, When try access smb://host/sharing on all file systens managers the system report fails when mount Windows sharing. Invalid argument. Thi

Bug#1008573: gpg-agent -managed SSH keys stored in Yubikeys cannot be used with OpenSSH 8.9

2022-04-21 Thread NIIBE Yutaka
On Mon, 11 Apr 2022 11:00:55 -0700 Vagrant Cascadian wrote: > Same problem with Gnuk, presumably multiple or all smartcards are > affected? I found an issue of scdaemon. At upstream development, it is tracked by: https://dev.gnupg.org/T5935 When the data is not so large (smaller than t

Processed: oneliner-el: diff for NMU version 0.3.6-9.2

2022-04-21 Thread Debian Bug Tracking System
Processing control commands: > tags 965756 + patch Bug #965756 [src:oneliner-el] oneliner-el: Removal of obsolete debhelper compat 5 and 6 in bookworm Added tag(s) patch. > tags 965756 + pending Bug #965756 [src:oneliner-el] oneliner-el: Removal of obsolete debhelper compat 5 and 6 in bookworm A

Bug#1005500: NMU upload pending

2022-04-21 Thread Jonas Smedegaard
Quoting Timo Röhling (2022-04-22 00:02:37) > I took the liberty to massage the PR to apply cleanly to version 2.4.8 > and uploaded the fix. Great! Thanks a lot! - Jonas -- * Jonas Smedegaard - idealist & Internet-arkitekt * Tlf.: +45 40843136 Website: http://dr.jones.dk/ [x] quote me fre

Bug#965756: oneliner-el: diff for NMU version 0.3.6-9.2

2022-04-21 Thread Guilherme de Paula Xavier Segundo
Control: tags 965756 + patch Control: tags 965756 + pending Dear maintainer, I've prepared an NMU for oneliner-el (versioned as 0.3.6-9.2) and uploaded it to DELAYED/5. Please feel free to tell me if I should delay it longer. Regards. diff -u oneliner-el-0.3.6/debian/changelog oneliner-el-0.3.6

Processed: nagios-plugins-rabbitmq: diff for NMU version 1:1.2.0-2.4

2022-04-21 Thread Debian Bug Tracking System
Processing control commands: > tags 965742 + patch Bug #965742 [src:nagios-plugins-rabbitmq] nagios-plugins-rabbitmq: Removal of obsolete debhelper compat 5 and 6 in bookworm Added tag(s) patch. > tags 965742 + pending Bug #965742 [src:nagios-plugins-rabbitmq] nagios-plugins-rabbitmq: Removal of

Bug#965742: nagios-plugins-rabbitmq: diff for NMU version 1:1.2.0-2.4

2022-04-21 Thread Guilherme de Paula Xavier Segundo
Control: tags 965742 + patch Control: tags 965742 + pending Dear maintainer, I've prepared an NMU for nagios-plugins-rabbitmq (versioned as 1:1.2.0-2.4) and uploaded it to DELAYED/2. Please feel free to tell me if I should delay it longer. Regards. diff -u nagios-plugins-rabbitmq-1.2.0/debian/c

Processed: mylvmbackup: diff for NMU version 0.15-1.2

2022-04-21 Thread Debian Bug Tracking System
Processing control commands: > tags 965738 + patch Bug #965738 [src:mylvmbackup] mylvmbackup: Removal of obsolete debhelper compat 5 and 6 in bookworm Added tag(s) patch. > tags 965738 + pending Bug #965738 [src:mylvmbackup] mylvmbackup: Removal of obsolete debhelper compat 5 and 6 in bookworm A

Bug#965738: mylvmbackup: diff for NMU version 0.15-1.2

2022-04-21 Thread Guilherme de Paula Xavier Segundo
Control: tags 965738 + patch Control: tags 965738 + pending Dear maintainer, I've prepared an NMU for mylvmbackup (versioned as 0.15-1.2) and uploaded it to DELAYED/5. Please feel free to tell me if I should delay it longer. Regards. diff -Nru mylvmbackup-0.15/debian/changelog mylvmbackup-0.15/d

Bug#965733: mrb: diff for NMU version 0.3+nmu2

2022-04-21 Thread Guilherme de Paula Xavier Segundo
Control: tags 965733 + patch Control: tags 965733 + pending Dear maintainer, I've prepared an NMU for mrb (versioned as 0.3+nmu2) and uploaded it to DELAYED/2. Please feel free to tell me if I should delay it longer. Regards. diff -Nru mrb-0.3+nmu1/debian/changelog mrb-0.3+nmu2/debian/changelog

Processed: mrb: diff for NMU version 0.3+nmu2

2022-04-21 Thread Debian Bug Tracking System
Processing control commands: > tags 965733 + patch Bug #965733 [src:mrb] mrb: Removal of obsolete debhelper compat 5 and 6 in bookworm Added tag(s) patch. > tags 965733 + pending Bug #965733 [src:mrb] mrb: Removal of obsolete debhelper compat 5 and 6 in bookworm Added tag(s) pending. -- 965733

Bug#1005500: NMU upload pending

2022-04-21 Thread Timo Röhling
Hi, I took the liberty to massage the PR to apply cleanly to version 2.4.8 and uploaded the fix. Cheers Timo -- ⢀⣴⠾⠻⢶⣦⠀ ╭╮ ⣾⠁⢠⠒⠀⣿⡁ │ Timo Röhling │ ⢿⡄⠘⠷⠚⠋⠀ │ 9B03 EBB9 8300 DF97 C2B1 23BF CC8C 6BDD

Bug#1005500: marked as done (doctest breaks argh build: doctest.h:1398:92: error: use of deleted function ‘doctest::detail::Expression_lhs >::Expression_l

2022-04-21 Thread Debian Bug Tracking System
Your message dated Thu, 21 Apr 2022 22:05:18 + with message-id and subject line Bug#1005500: fixed in doctest 2.4.8~ds-1.1 has caused the Debian Bug report #1005500, regarding doctest breaks argh build: doctest.h:1398:92: error: use of deleted function ‘doctest::detail::Expression_lhs >::Exp

Processed: cli-common: diff for NMU version 0.10+nmu1

2022-04-21 Thread Debian Bug Tracking System
Processing control commands: > tags 965460 + patch Bug #965460 [src:cli-common] cli-common: Removal of obsolete debhelper compat 5 and 6 in bookworm Added tag(s) patch. > tags 965460 + pending Bug #965460 [src:cli-common] cli-common: Removal of obsolete debhelper compat 5 and 6 in bookworm Added

Bug#965460: cli-common: diff for NMU version 0.10+nmu1

2022-04-21 Thread Guilherme de Paula Xavier Segundo
Control: tags 965460 + patch Control: tags 965460 + pending Dear maintainer, I've prepared an NMU for cli-common (versioned as 0.10+nmu1) and uploaded it to DELAYED/5. Please feel free to tell me if I should delay it longer. Regards. diff -Nru cli-common-0.10/debian/changelog cli-common-0.10+nmu

Bug#1008653: backintime-qt broken in sid after python upgrade

2022-04-21 Thread Agustin Martin
El jue, 21 abr 2022 a las 23:47, Agustin Martin () escribió: > If a new upstream version contains many changes that maintainer wants > to inspect closely, it is trivial to just include upstream fix for > this issue. I am attaching a patch (with unclosed changelog formatted > for NMU, modify as appr

Processed: Bug#1008653: backintime-qt broken in sid after python upgrade

2022-04-21 Thread Debian Bug Tracking System
Processing control commands: > tags -1 + patch fixed-upstream Bug #1008653 [backintime-qt] backintime-qt broken in sid after python upgrade Added tag(s) fixed-upstream and patch. -- 1008653: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1008653 Debian Bug Tracking System Contact ow...@bugs.d

Bug#1008653: backintime-qt broken in sid after python upgrade

2022-04-21 Thread Agustin Martin
Control: tags -1 + patch fixed-upstream On Wed, Apr 20, 2022 at 09:45:26AM +0200, Leonardo Canducci wrote: > Package: backintime-qt > Followup-For: Bug #1008653 > > I've installed backintime-qt from github (it's pretty straightforward, > just donwload the source and build two deb files with the pr

Bug#999139: marked as done (bplay: missing required debian/rules targets build-arch and/or build-indep)

2022-04-21 Thread Debian Bug Tracking System
Your message dated Thu, 21 Apr 2022 20:22:43 + with message-id and subject line Bug#999139: fixed in bplay 0.991-10.1 has caused the Debian Bug report #999139, regarding bplay: missing required debian/rules targets build-arch and/or build-indep to be marked as done. This means that you claim

Bug#965610: marked as done (kdc2tiff: Removal of obsolete debhelper compat 5 and 6 in bookworm)

2022-04-21 Thread Debian Bug Tracking System
Your message dated Thu, 21 Apr 2022 20:23:03 + with message-id and subject line Bug#965610: fixed in kdc2tiff 0.35-10.1 has caused the Debian Bug report #965610, regarding kdc2tiff: Removal of obsolete debhelper compat 5 and 6 in bookworm to be marked as done. This means that you claim that t

Bug#1009606: marked as done (node-browserify-aes: FTBFS: ERROR: Coverage for statements (97.19%) does not meet global threshold (100%))

2022-04-21 Thread Debian Bug Tracking System
Your message dated Thu, 21 Apr 2022 20:24:55 + with message-id and subject line Bug#1009606: fixed in node-browserify-aes 1.2.0-5 has caused the Debian Bug report #1009606, regarding node-browserify-aes: FTBFS: ERROR: Coverage for statements (97.19%) does not meet global threshold (100%) to b

Bug#965440: marked as done (bplay: Removal of obsolete debhelper compat 5 and 6 in bookworm)

2022-04-21 Thread Debian Bug Tracking System
Your message dated Thu, 21 Apr 2022 20:22:43 + with message-id and subject line Bug#965440: fixed in bplay 0.991-10.1 has caused the Debian Bug report #965440, regarding bplay: Removal of obsolete debhelper compat 5 and 6 in bookworm to be marked as done. This means that you claim that the pr

Processed: Bug#1009606 marked as pending in node-browserify-aes

2022-04-21 Thread Debian Bug Tracking System
Processing control commands: > tag -1 pending Bug #1009606 [src:node-browserify-aes] node-browserify-aes: FTBFS: ERROR: Coverage for statements (97.19%) does not meet global threshold (100%) Added tag(s) pending. -- 1009606: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1009606 Debian Bug T

Bug#1009606: marked as pending in node-browserify-aes

2022-04-21 Thread Yadd
Control: tag -1 pending Hello, Bug #1009606 in node-browserify-aes reported by you has been fixed in the Git repository and is awaiting an upload. You can see the commit message below and you can check the diff of the fix at: https://salsa.debian.org/js-team/node-browserify-aes/-/commit/fe01c893

Bug#1009519: marked as pending in node-fstream-ignore

2022-04-21 Thread Yadd
Control: tag -1 pending Hello, Bug #1009519 in node-fstream-ignore reported by you has been fixed in the Git repository and is awaiting an upload. You can see the commit message below and you can check the diff of the fix at: https://salsa.debian.org/js-team/node-fstream-ignore/-/commit/d664a300

Processed: Bug#1009519 marked as pending in node-fstream-ignore

2022-04-21 Thread Debian Bug Tracking System
Processing control commands: > tag -1 pending Bug #1009519 [src:node-fstream-ignore] node-fstream-ignore: FTBFS: ERROR: Coverage for statements (87.6%) does not meet global threshold (100%) Added tag(s) pending. -- 1009519: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1009519 Debian Bug Tr

Bug#1005175: marked as done (libtest-harness-perl: uninstallable, older than Perl 5.34 bundled version)

2022-04-21 Thread Debian Bug Tracking System
Your message dated Thu, 21 Apr 2022 19:49:19 + with message-id and subject line Bug#1005175: fixed in libtest-harness-perl 3.44-1 has caused the Debian Bug report #1005175, regarding libtest-harness-perl: uninstallable, older than Perl 5.34 bundled version to be marked as done. This means th

Bug#1009917: (no subject)

2022-04-21 Thread ZenWalker
Thanks for your quick answer. > Mobian appears to be a Debian derivative, containing modifications > relative to Debian. I reported the bug using 'reportbug', you can see the related packages, seems there is no mobian specific packages. The mobian packages are here: https://packages.mobian-proje

Bug#1009418: autokey: diff for NMU version 0.95.10-2.1

2022-04-21 Thread Tobias Frost
Control: tags 1009418 + patch Control: tags 1009418 + pending Dear maintainer, I've prepared an NMU for autokey (versioned as 0.95.10-2.1) and uploaded it to DELAYED/5. Please feel free to tell me if I should delay it longer. Regards. diff -Nru autokey-0.95.10/debian/changelog autokey-0.95.10/

Processed: autokey: diff for NMU version 0.95.10-2.1

2022-04-21 Thread Debian Bug Tracking System
Processing control commands: > tags 1009418 + patch Bug #1009418 [src:autokey] autokey: FTBFS: dh_missing: warning: usr/lib/python3.10/dist-packages/autokey/__pycache__/__init__.cpython-310.pyc exists in debian/tmp but is not installed to anywhere Added tag(s) patch. > tags 1009418 + pending Bug

Processed: update bts metadata

2022-04-21 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > reassign 1009207 src:python-hbmqtt 0.9.6-1.2 Bug #1009207 {Done: Debian FTP Masters } [src:python-websockets, src:python-hbmqtt] python-websockets breaks python-hbmqtt autopkgtest: cannot import name 'InvalidURI' from 'websockets.uri' Bug reassi

Bug#1009987: bluez: Bluetooth service does not start

2022-04-21 Thread Benjamin Mesing
Package: bluez Version: 5.64-1 Severity: grave Justification: renders package unusable Hi, I installed testing non-free and immediately upgraded to unstable on a lenovo thinkbook in the last two day. After that bluetooth was not working. Note, that I did not test bluetooth while still being on te

Processed: Re: Bug#1009917: gtk4 applications randomly crash on Mobian Pinephone

2022-04-21 Thread Debian Bug Tracking System
Processing control commands: > retitle -1 gtk4 applications randomly crash on Mobian Pinephone Bug #1009917 [libgtk-4-1] gtk4 applications randomly crash Changed Bug title to 'gtk4 applications randomly crash on Mobian Pinephone' from 'gtk4 applications randomly crash'. > tags -1 = upstream morei

Bug#1009917: gtk4 applications randomly crash on Mobian Pinephone

2022-04-21 Thread Simon McVittie
Control: retitle -1 gtk4 applications randomly crash on Mobian Pinephone Control: tags -1 = upstream moreinfo On Wed, 20 Apr 2022 at 18:03:34 +0200, ZenWalker wrote: > Unable to run these applications 10 times without crash with mobian pinephone: > > megapixels, gnome-calculator, and gnome-clocks

Bug#1008312: marked as done (clementine doesn't start)

2022-04-21 Thread Debian Bug Tracking System
Your message dated Thu, 21 Apr 2022 17:04:32 + with message-id and subject line Bug#1008312: fixed in clementine 1.4.0~rc1+git347-gfc4cb6fc7+dfsg-2.1 has caused the Debian Bug report #1008312, regarding clementine doesn't start to be marked as done. This means that you claim that the problem

Bug#828550: marked as done (socat: FTBFS with openssl 1.1.0)

2022-04-21 Thread Debian Bug Tracking System
Your message dated Thu, 21 Apr 2022 19:01:23 +0200 with message-id and subject line Re: Bug#828550: socat: FTBFS with openssl 1.1.0 has caused the Debian Bug report #828550, regarding socat: FTBFS with openssl 1.1.0 to be marked as done. This means that you claim that the problem has been dealt

Bug#979719: marked as done (socat in experimental is obsolete and no installable)

2022-04-21 Thread Debian Bug Tracking System
Your message dated Thu, 21 Apr 2022 18:55:41 +0200 with message-id and subject line Re: Bug#979719: socat in experimental is obsolete and no installable has caused the Debian Bug report #979719, regarding socat in experimental is obsolete and no installable to be marked as done. This means that

Bug#1009555: marked as done (node-ini: FTBFS: ERROR: Coverage for statements (88.98%) does not meet global threshold (100%))

2022-04-21 Thread Debian Bug Tracking System
Your message dated Thu, 21 Apr 2022 16:36:27 + with message-id and subject line Bug#1009555: fixed in node-ini 2.0.1-2 has caused the Debian Bug report #1009555, regarding node-ini: FTBFS: ERROR: Coverage for statements (88.98%) does not meet global threshold (100%) to be marked as done. Thi

Bug#1009535: marked as done (node-console-control-strings: FTBFS: ERROR: Coverage for branches (90%) does not meet global threshold (100%))

2022-04-21 Thread Debian Bug Tracking System
Your message dated Thu, 21 Apr 2022 16:36:22 + with message-id and subject line Bug#1009535: fixed in node-console-control-strings 1.1.0-3 has caused the Debian Bug report #1009535, regarding node-console-control-strings: FTBFS: ERROR: Coverage for branches (90%) does not meet global threshol

Processed: Bug#1009535 marked as pending in node-console-control-strings

2022-04-21 Thread Debian Bug Tracking System
Processing control commands: > tag -1 pending Bug #1009535 [src:node-console-control-strings] node-console-control-strings: FTBFS: ERROR: Coverage for branches (90%) does not meet global threshold (100%) Added tag(s) pending. -- 1009535: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1009535

Bug#1009555: marked as pending in node-ini

2022-04-21 Thread Yadd
Control: tag -1 pending Hello, Bug #1009555 in node-ini reported by you has been fixed in the Git repository and is awaiting an upload. You can see the commit message below and you can check the diff of the fix at: https://salsa.debian.org/js-team/node-ini/-/commit/809f90105ebd891f0345da7e7d1ed4

Bug#1009535: marked as pending in node-console-control-strings

2022-04-21 Thread Yadd
Control: tag -1 pending Hello, Bug #1009535 in node-console-control-strings reported by you has been fixed in the Git repository and is awaiting an upload. You can see the commit message below and you can check the diff of the fix at: https://salsa.debian.org/js-team/node-console-control-string

Processed: Bug#1009555 marked as pending in node-ini

2022-04-21 Thread Debian Bug Tracking System
Processing control commands: > tag -1 pending Bug #1009555 [src:node-ini] node-ini: FTBFS: ERROR: Coverage for statements (88.98%) does not meet global threshold (100%) Added tag(s) pending. -- 1009555: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1009555 Debian Bug Tracking System Contact

Bug#1009685: Resolved due to migration of Python3.10 (was: opm-grid: autopkgtest regression: No rule to make target '/usr/lib/x86_64-linux-gnu/libpython3.10.so')

2022-04-21 Thread Markus Blatt
Dear Paul, thanks for noticing. You are right the migration was not possible due to the Python transition. The problem was a chicken and egg one. And the update of the package was done to make the python migration possible (by removing remnants of the old python version from all opm packages). I

Bug#1008708: Bug is fixed in 2.14, current is 2.15

2022-04-21 Thread Heinz Repp
Unfortunately PysolFC is severely outdated in Debian. PysolFC not running with Python 3.10 has been fixed in 2.14, the current version is 2.15. The Debian package hasn't seen updates since two years ago, and now it's broken. Please update to 2.15 a.s.a.p.!

Bug#912682: marked as done (libextutils-parsexs-perl: version is older than Replaces+Breaks in perl-modules-5.28)

2022-04-21 Thread Debian Bug Tracking System
Your message dated Thu, 21 Apr 2022 15:25:37 + with message-id and subject line Bug#1009785: Removed package(s) from unstable has caused the Debian Bug report #912682, regarding libextutils-parsexs-perl: version is older than Replaces+Breaks in perl-modules-5.28 to be marked as done. This me

Bug#1009836: marked as done (python3-pylsp-flake8: give upstream source in the d/copyright file)

2022-04-21 Thread Debian Bug Tracking System
Your message dated Thu, 21 Apr 2022 15:25:07 + with message-id and subject line Bug#1009941: Removed package(s) from unstable has caused the Debian Bug report #1009836, regarding python3-pylsp-flake8: give upstream source in the d/copyright file to be marked as done. This means that you claim

Bug#978869: marked as done (nemiver: ftbfs with autoconf 2.70)

2022-04-21 Thread Debian Bug Tracking System
Your message dated Thu, 21 Apr 2022 15:21:01 + with message-id and subject line Bug#1009860: Removed package(s) from unstable has caused the Debian Bug report #978869, regarding nemiver: ftbfs with autoconf 2.70 to be marked as done. This means that you claim that the problem has been dealt w

Bug#966745: marked as done (gjots2: Unversioned Python removal in sid/bullseye)

2022-04-21 Thread Debian Bug Tracking System
Your message dated Thu, 21 Apr 2022 15:23:03 + with message-id and subject line Bug#1009932: Removed package(s) from unstable has caused the Debian Bug report #936619, regarding gjots2: Unversioned Python removal in sid/bullseye to be marked as done. This means that you claim that the problem

Bug#936619: marked as done (gjots2: Python2 removal in sid/bullseye)

2022-04-21 Thread Debian Bug Tracking System
Your message dated Thu, 21 Apr 2022 15:23:03 + with message-id and subject line Bug#1009932: Removed package(s) from unstable has caused the Debian Bug report #936619, regarding gjots2: Python2 removal in sid/bullseye to be marked as done. This means that you claim that the problem has been d

Bug#1008781: marked as done (nemiver: Intent to remove from Debian)

2022-04-21 Thread Debian Bug Tracking System
Your message dated Thu, 21 Apr 2022 15:21:01 + with message-id and subject line Bug#1009860: Removed package(s) from unstable has caused the Debian Bug report #1008781, regarding nemiver: Intent to remove from Debian to be marked as done. This means that you claim that the problem has been de

Bug#996263: marked as done (ctop: Should this package be removed?)

2022-04-21 Thread Debian Bug Tracking System
Your message dated Thu, 21 Apr 2022 15:19:18 + with message-id and subject line Bug#1009800: Removed package(s) from unstable has caused the Debian Bug report #996263, regarding ctop: Should this package be removed? to be marked as done. This means that you claim that the problem has been dea

Bug#930874: marked as done ([ERROR] Failed to locate cgroup mountpoints.)

2022-04-21 Thread Debian Bug Tracking System
Your message dated Thu, 21 Apr 2022 15:19:18 + with message-id and subject line Bug#1009800: Removed package(s) from unstable has caused the Debian Bug report #930874, regarding [ERROR] Failed to locate cgroup mountpoints. to be marked as done. This means that you claim that the problem has b

Bug#1009522: marked as done (node-move-concurrently: FTBFS: ERROR: Coverage for branches (93.75%) does not meet global threshold (100%))

2022-04-21 Thread Debian Bug Tracking System
Your message dated Thu, 21 Apr 2022 15:18:46 + with message-id and subject line Bug#1009522: fixed in node-move-concurrently 1.0.1-5 has caused the Debian Bug report #1009522, regarding node-move-concurrently: FTBFS: ERROR: Coverage for branches (93.75%) does not meet global threshold (100%)

Bug#1007126: marked as done (laszip: Should not be included in bookworm)

2022-04-21 Thread Debian Bug Tracking System
Your message dated Thu, 21 Apr 2022 15:15:49 + with message-id and subject line Bug#1009625: Removed package(s) from unstable has caused the Debian Bug report #1007126, regarding laszip: Should not be included in bookworm to be marked as done. This means that you claim that the problem has be

Bug#1006910: marked as done (pdal: Should not be included in bookworm)

2022-04-21 Thread Debian Bug Tracking System
Your message dated Thu, 21 Apr 2022 15:15:07 + with message-id and subject line Bug#1009624: Removed package(s) from unstable has caused the Debian Bug report #1006910, regarding pdal: Should not be included in bookworm to be marked as done. This means that you claim that the problem has been

Bug#938544: marked as done (sphinx-patchqueue: Python2 removal in sid/bullseye)

2022-04-21 Thread Debian Bug Tracking System
Your message dated Thu, 21 Apr 2022 15:12:09 + with message-id and subject line Bug#1009269: Removed package(s) from unstable has caused the Debian Bug report #938544, regarding sphinx-patchqueue: Python2 removal in sid/bullseye to be marked as done. This means that you claim that the problem

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

2022-04-21 Thread Debian Bug Tracking System
Your message dated Thu, 21 Apr 2022 15:13:24 + with message-id and subject line Bug#1009335: Removed package(s) from unstable has caused the Debian Bug report #937869, regarding python-keepkey: Python2 removal in sid/bullseye to be marked as done. This means that you claim that the problem ha

Bug#934839: marked as done (python-keepkey: depends on cruft package.)

2022-04-21 Thread Debian Bug Tracking System
Your message dated Thu, 21 Apr 2022 15:13:24 + with message-id and subject line Bug#1009335: Removed package(s) from unstable has caused the Debian Bug report #934839, regarding python-keepkey: depends on cruft package. to be marked as done. This means that you claim that the problem has been

Bug#1009273: marked as done (Should python-keepkey be removed?)

2022-04-21 Thread Debian Bug Tracking System
Your message dated Thu, 21 Apr 2022 15:13:24 + with message-id and subject line Bug#1009335: Removed package(s) from unstable has caused the Debian Bug report #1009273, regarding Should python-keepkey be removed? to be marked as done. This means that you claim that the problem has been dealt

Bug#1009207: marked as done (python-websockets breaks python-hbmqtt autopkgtest: cannot import name 'InvalidURI' from 'websockets.uri')

2022-04-21 Thread Debian Bug Tracking System
Your message dated Thu, 21 Apr 2022 15:14:10 + with message-id and subject line Bug#1009377: Removed package(s) from unstable has caused the Debian Bug report #1009207, regarding python-websockets breaks python-hbmqtt autopkgtest: cannot import name 'InvalidURI' from 'websockets.uri' to be ma

Bug#1009113: marked as done (python-hbmqtt: (autopkgtest) needs update for python3.10: the *loop* parameter was removed from Queue() since it is no longer necessary)

2022-04-21 Thread Debian Bug Tracking System
Your message dated Thu, 21 Apr 2022 15:14:10 + with message-id and subject line Bug#1009377: Removed package(s) from unstable has caused the Debian Bug report #1009113, regarding python-hbmqtt: (autopkgtest) needs update for python3.10: the *loop* parameter was removed from Queue() since it i

Processed: Re: Bug#1009475: meson: FTBFS: ./b 52a78b9866/../test cases/failing build/2 hidden symbol/bobuser.c:4: undefined reference to `hidden_function'

2022-04-21 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > forcemerge 1009097 1009475 Bug #1009097 [src:meson] meson: (autopkgtest) needs update for python3.10: MesonVersionMismatchException.__init__() missing 1 required positional argument: 'current_version' Bug #1009475 [src:meson] meson: FTBFS: ./b 5

Processed: Bug#1009522 marked as pending in node-move-concurrently

2022-04-21 Thread Debian Bug Tracking System
Processing control commands: > tag -1 pending Bug #1009522 [src:node-move-concurrently] node-move-concurrently: FTBFS: ERROR: Coverage for branches (93.75%) does not meet global threshold (100%) Added tag(s) pending. -- 1009522: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1009522 Debian B

Bug#1009522: marked as pending in node-move-concurrently

2022-04-21 Thread Yadd
Control: tag -1 pending Hello, Bug #1009522 in node-move-concurrently reported by you has been fixed in the Git repository and is awaiting an upload. You can see the commit message below and you can check the diff of the fix at: https://salsa.debian.org/js-team/node-move-concurrently/-/commit/f6

Bug#1008608: marked as done (r-cran-purrrogress: autopkgtest failure: Error in `is(pb, c("winProgressBar", "tkProgressBar", "txtProgressBar"))`: length(class2) == 1L is not TRUE)

2022-04-21 Thread Debian Bug Tracking System
Your message dated Thu, 21 Apr 2022 15:06:03 + with message-id and subject line Bug#1009121: Removed package(s) from unstable has caused the Debian Bug report #1008608, regarding r-cran-purrrogress: autopkgtest failure: Error in `is(pb, c("winProgressBar", "tkProgressBar", "txtProgressBar"))`

Bug#994036: marked as done (x11-xkb-utils: xkbcomp gives internal errors on unknown keysyms (e.g. some XF86* with xkb-data 2.33-1))

2022-04-21 Thread Debian Bug Tracking System
Your message dated Thu, 21 Apr 2022 13:33:56 + with message-id and subject line Bug#953032: fixed in x11-xkb-utils 7.7+6 has caused the Debian Bug report #953032, regarding x11-xkb-utils: xkbcomp gives internal errors on unknown keysyms (e.g. some XF86* with xkb-data 2.33-1) to be marked as d

Bug#953032: marked as done (xkbcomp: Internal error: Could not resolve keysym XF86FullScreen)

2022-04-21 Thread Debian Bug Tracking System
Your message dated Thu, 21 Apr 2022 13:33:56 + with message-id and subject line Bug#953032: fixed in x11-xkb-utils 7.7+6 has caused the Debian Bug report #953032, regarding xkbcomp: Internal error: Could not resolve keysym XF86FullScreen to be marked as done. This means that you claim that th

Bug#1009968: cannot import name 'Mapping' from 'collections' with Python 3.10 -- new upstream version needed

2022-04-21 Thread Eric Marsden
Package: python3-frozen-flask Version: 0.11-3.1 Severity: critical Using this library in Python 3.10 generates an ImportError. % python3 Python 3.10.4 (main, Apr  2 2022, 09:04:19) [GCC 11.2.0] on linux Type "help", "copyright", "credits" or "license" for more information. >>> from flask_frozen

Bug#1009184: marked as done (FTBFS against Octave 7)

2022-04-21 Thread Debian Bug Tracking System
Your message dated Thu, 21 Apr 2022 14:42:32 +0200 with message-id <5b5e22b0ccb50f5966ff2c7b69a3f7733df75dc8.ca...@debian.org> and subject line Re: Bug#1009184: FTBFS against Octave 7 has caused the Debian Bug report #1009184, regarding FTBFS against Octave 7 to be marked as done. This means that

Processed: #1003463 found outside experimental too

2022-04-21 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > found 1003463 arcanist/0~git20200925-1 Bug #1003463 [arcanist] Functionally broken with current PHP The source arcanist and version 0~git20200925-1 do not appear to match any binary packages Marked as found in versions arcanist/0~git20200925-1. >

Bug#1009966: libpam-tacplus: CVE-2016-20014

2022-04-21 Thread Salvatore Bonaccorso
Source: libpam-tacplus Version: 1.3.8-2.1 Severity: grave Tags: security upstream X-Debbugs-Cc: car...@debian.org, Debian Security Team Control: found -1 1.3.8-2+deb10u1 Control: found -1 1.3.8-2 Hi, The following vulnerability was published for libpam-tacplus. CVE-2016-20014[0]: | In pam_tacpl

Processed: libpam-tacplus: CVE-2016-20014

2022-04-21 Thread Debian Bug Tracking System
Processing control commands: > found -1 1.3.8-2+deb10u1 Bug #1009966 [src:libpam-tacplus] libpam-tacplus: CVE-2016-20014 Marked as found in versions libpam-tacplus/1.3.8-2+deb10u1. > found -1 1.3.8-2 Bug #1009966 [src:libpam-tacplus] libpam-tacplus: CVE-2016-20014 Marked as found in versions libpa

Processed: severity of 1009888 is grave

2022-04-21 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > severity 1009888 grave Bug #1009888 [rust-h2] rust-h2, existing version is badly broken, new upstream needs new package Severity set to 'grave' from 'normal' > thanks Stopping processing here. Please contact me if you need assistance. -- 100988

Bug#1009504: marked as done (node-create-hmac: FTBFS: ERROR: Coverage for statements (97.1%) does not meet global threshold (100%))

2022-04-21 Thread Debian Bug Tracking System
Your message dated Thu, 21 Apr 2022 11:18:54 + with message-id and subject line Bug#1009504: fixed in node-create-hmac 1.1.7+~1.1.0-2 has caused the Debian Bug report #1009504, regarding node-create-hmac: FTBFS: ERROR: Coverage for statements (97.1%) does not meet global threshold (100%) to b

Bug#1009531: marked as done (node-browserify: FTBFS: ERROR: Coverage for statements (84.75%) does not meet global threshold (100%))

2022-04-21 Thread Debian Bug Tracking System
Your message dated Thu, 21 Apr 2022 11:18:48 + with message-id and subject line Bug#1009531: fixed in node-browserify 17.0.0+ds-4 has caused the Debian Bug report #1009531, regarding node-browserify: FTBFS: ERROR: Coverage for statements (84.75%) does not meet global threshold (100%) to be ma

Bug#1009420: irssi is marked for autoremoval from testing

2022-04-21 Thread Rhonda D'Vine
tags 1009420 + patch thanks Hi, given the potential autoremoval of irssi we looked into this, irssi upstream suggested the attached patch which I can confirm to fix the build. Cheers, Rhonda -- Fühlst du dich mutlos, fass endlich Mut, los | Fühlst du dich hilflos, geh raus und hilf,

Processed: Re: irssi is marked for autoremoval from testing

2022-04-21 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > tags 1009420 + patch Bug #1009420 [src:libotr] libotr: FTBFS: client.c:624:30: error: ‘PF_UNIX’ undeclared (first use in this function) Added tag(s) patch. > thanks Stopping processing here. Please contact me if you need assistance. -- 1009420:

Processed: Bug#1009504 marked as pending in node-create-hmac

2022-04-21 Thread Debian Bug Tracking System
Processing control commands: > tag -1 pending Bug #1009504 [src:node-create-hmac] node-create-hmac: FTBFS: ERROR: Coverage for statements (97.1%) does not meet global threshold (100%) Added tag(s) pending. -- 1009504: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1009504 Debian Bug Tracking

Bug#1009531: marked as pending in node-browserify

2022-04-21 Thread Yadd
Control: tag -1 pending Hello, Bug #1009531 in node-browserify reported by you has been fixed in the Git repository and is awaiting an upload. You can see the commit message below and you can check the diff of the fix at: https://salsa.debian.org/js-team/node-browserify/-/commit/33bbc9db5d2a7457

Bug#1009504: marked as pending in node-create-hmac

2022-04-21 Thread Yadd
Control: tag -1 pending Hello, Bug #1009504 in node-create-hmac reported by you has been fixed in the Git repository and is awaiting an upload. You can see the commit message below and you can check the diff of the fix at: https://salsa.debian.org/js-team/node-create-hmac/-/commit/166cd9e2f7a10d

Processed: Bug#1009531 marked as pending in node-browserify

2022-04-21 Thread Debian Bug Tracking System
Processing control commands: > tag -1 pending Bug #1009531 [src:node-browserify] node-browserify: FTBFS: ERROR: Coverage for statements (84.75%) does not meet global threshold (100%) Added tag(s) pending. -- 1009531: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1009531 Debian Bug Tracking

Bug#1009517: marked as done (node-function-bind: FTBFS: ERROR: Coverage for branches (90%) does not meet global threshold (100%))

2022-04-21 Thread Debian Bug Tracking System
Your message dated Thu, 21 Apr 2022 10:49:01 + with message-id and subject line Bug#1009517: fixed in node-function-bind 1.1.1+repacked+~1.0.3-2 has caused the Debian Bug report #1009517, regarding node-function-bind: FTBFS: ERROR: Coverage for branches (90%) does not meet global threshold (

Bug#1009543: marked as done (node-callback-stream: FTBFS: ERROR: Coverage for branches (83.33%) does not meet global threshold (100%))

2022-04-21 Thread Debian Bug Tracking System
Your message dated Thu, 21 Apr 2022 10:33:53 + with message-id and subject line Bug#1009543: fixed in node-callback-stream 1.1.0-4 has caused the Debian Bug report #1009543, regarding node-callback-stream: FTBFS: ERROR: Coverage for branches (83.33%) does not meet global threshold (100%) to b

Bug#1009517: marked as pending in node-function-bind

2022-04-21 Thread Yadd
Control: tag -1 pending Hello, Bug #1009517 in node-function-bind reported by you has been fixed in the Git repository and is awaiting an upload. You can see the commit message below and you can check the diff of the fix at: https://salsa.debian.org/js-team/node-function-bind/-/commit/d7f0b932f7

Processed: Bug#1009517 marked as pending in node-function-bind

2022-04-21 Thread Debian Bug Tracking System
Processing control commands: > tag -1 pending Bug #1009517 [src:node-function-bind] node-function-bind: FTBFS: ERROR: Coverage for branches (90%) does not meet global threshold (100%) Added tag(s) pending. -- 1009517: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1009517 Debian Bug Tracking

Processed: Bug#1009608 marked as pending in node-fstream

2022-04-21 Thread Debian Bug Tracking System
Processing control commands: > tag -1 pending Bug #1009608 [src:node-fstream] node-fstream: FTBFS: ERROR: Coverage for statements (73.3%) does not meet global threshold (100%) Added tag(s) pending. -- 1009608: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1009608 Debian Bug Tracking System

Processed: Bug#1009543 marked as pending in node-callback-stream

2022-04-21 Thread Debian Bug Tracking System
Processing control commands: > tag -1 pending Bug #1009543 [src:node-callback-stream] node-callback-stream: FTBFS: ERROR: Coverage for branches (83.33%) does not meet global threshold (100%) Added tag(s) pending. -- 1009543: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1009543 Debian Bug T

Bug#1009608: marked as pending in node-fstream

2022-04-21 Thread Yadd
Control: tag -1 pending Hello, Bug #1009608 in node-fstream reported by you has been fixed in the Git repository and is awaiting an upload. You can see the commit message below and you can check the diff of the fix at: https://salsa.debian.org/js-team/node-fstream/-/commit/d105b07e45f3a2f45b8afd

Bug#1009543: marked as pending in node-callback-stream

2022-04-21 Thread Yadd
Control: tag -1 pending Hello, Bug #1009543 in node-callback-stream reported by you has been fixed in the Git repository and is awaiting an upload. You can see the commit message below and you can check the diff of the fix at: https://salsa.debian.org/js-team/node-callback-stream/-/commit/da2207

Bug#1008465: #1008465 (python-fabio FTBFS): works for me

2022-04-21 Thread Roland Mas
Hi, I was trying to reproduce bug  #1008465 to see if I could fix it, but an up-to-date pbuilder and an up-to-date git clone build fine. Maybe something changed in the dependencies? I suggest closing this bug, because python-fabio is marked for autoremoval from testing and several packages w

  1   2   >