Processed: reassign 998448 to ruby-ruby-magic-static, tagging 996125, tagging 984208, tagging 999409 ...

2021-11-19 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > reassign 998448 ruby-ruby-magic-static 0.5.0-1 Bug #998448 [ruby-ruby-file-magic] Rename source and binary version to ruy-ruby-magic Warning: Unknown package 'ruby-ruby-file-magic' Bug reassigned from package 'ruby-ruby-file-magic' to 'ruby-ruby-

Processed: tagging ftbfs

2021-11-19 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > tags 999361 + ftbfs Bug #999361 [src:mypy] mypy ftbfs with python3.10 as supported (test failures) Added tag(s) ftbfs. > tags 1000178 + ftbfs Bug #1000178 [src:llvmlite] llvmlite: FTBFS with Python 3.10 Added tag(s) ftbfs. > thanks Stopping proces

Bug#1000182: python-jira: network access during the build

2021-11-19 Thread Mattia Rizzolo
Source: python-jira Version: 3.0-1 Severity: serious Dear maintainer, It has been brought to our attention[1] that python-jira is doing network access during its build. On a build with network enabled: |PYTHONPATH=. http_proxy='127.0.0.1:9' python3 -m sphinx -N -bhtml docs/ build/html # HTML g

Processed: found 1000182 in 2.0.0-1

2021-11-19 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > found 1000182 2.0.0-1 Bug #1000182 [src:python-jira] python-jira: network access during the build Marked as found in versions python-jira/2.0.0-1. > thanks Stopping processing here. Please contact me if you need assistance. -- 1000182: https://b

Processed: reassign 985847 to src:mutter, fixed 985847 in 40.1-1, notfixed 481015 in 2.1.1 ..., tagging 974797 ...

2021-11-19 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > # bts housekeeping to allow bug archival > reassign 985847 src:mutter 3.38.4-1 Bug #985847 {Done: Simon McVittie } [libmutter-7-0] libmutter-7-0: gnome-shell with wayland shows deformed output with v3d.ko Bug reassigned from package 'libmutter-7-

Bug#971783: mate-volume-control-status-icon dies here too

2021-11-19 Thread Maxime G.
Thank you for your actions Mike. Can you look at these open tickets for the same issue and take actions ? #966840 https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=966840 #856072 (this one since 2017) https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=856072 Thanks. Max. 19 novembre 2021 08:05 "

Bug#1000182: Clone to sphinx-common

2021-11-19 Thread Neil Williams
clone 1000182 sphinx-common retitle -1 python3-sphinx: intersphinx_mapping causes network access despite proxy setting thanks Does dh_sphinxdoc need to also disable https: or does intersphinx_mapping have to be patched out of every package using Sphinx? This will inevitably cause another differe

Bug#999764: closed by Debian FTP Masters (reply to Matthias Klose ) (Bug#999764: fixed in gcc-12 12-20211117-1)

2021-11-19 Thread Andreas Beckmann
Control: found -1 12-2027-1 All fixed but gcc-11-locales=11.2.0-10 vs. gcc-12-locales=12-2027-1: usr/share/locale/be/LC_MESSAGES/cpplib-11.mo usr/share/locale/ca/LC_MESSAGES/cpplib-11.mo usr/share/locale/da/LC_MESSAGES/cpplib-11.mo usr/share/locale/de/LC_MESSAGES/cpplib-11.mo usr/share/l

Processed: Re: Bug#999764 closed by Debian FTP Masters (reply to Matthias Klose ) (Bug#999764: fixed in gcc-12 12-20211117-1)

2021-11-19 Thread Debian Bug Tracking System
Processing control commands: > found -1 12-2027-1 Bug #999764 {Done: Matthias Klose } [src:gcc-12] gcc-12: file conflicts with gcc-11 due to missing Breaks+Replaces or renaming Marked as found in versions gcc-12/12-2027-1; no longer marked as fixed in versions gcc-12/12-2027-1 and re

Bug#1000182: marked as pending in python-jira

2021-11-19 Thread Neil Williams
Control: tag -1 pending Hello, Bug #1000182 in python-jira 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/python-team/packages/python-jira/-/commit/5a65b90b606

Processed: Bug#1000182 marked as pending in python-jira

2021-11-19 Thread Debian Bug Tracking System
Processing control commands: > tag -1 pending Bug #1000182 [src:python-jira] python-jira: network access during the build Added tag(s) pending. -- 1000182: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1000182 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems

Processed: clone 1000182

2021-11-19 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > clone 1000182 -1 Bug #1000182 [src:python-jira] python-jira: network access during the build Bug 1000182 cloned as bug 1000184 > reassign -1 sphinx-common 4.2.0-5 Bug #1000184 [src:python-jira] python-jira: network access during the build Bug reas

Processed: Can dh_sphinxdoc disable intersphinx_mapping support?

2021-11-19 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > tag 1000184 - pending Bug #1000184 [sphinx-common] sphinx-common: dh_sphinxdoc support for intersphinx_mapping causes network access despite proxy setting Removed tag(s) pending. > thanks Stopping processing here. Please contact me if you need a

Bug#1000184: Can dh_sphinxdoc disable intersphinx_mapping support?

2021-11-19 Thread Neil Williams
tag 1000184 - pending thanks Does dh_sphinxdoc need to also disable https: or does intersphinx_mapping have to be patched out of every package using Sphinx? This will inevitably cause another difference between the upstream documentation and the packaged documentation, unless some sort of cache

Bug#1000182: marked as pending in python-jira

2021-11-19 Thread Neil Williams
Control: tag -1 pending Hello, Bug #1000182 in python-jira 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/python-team/packages/python-jira/-/commit/e950de00d30

Processed: Bug#1000182 marked as pending in python-jira

2021-11-19 Thread Debian Bug Tracking System
Processing control commands: > tag -1 pending Bug #1000182 [src:python-jira] python-jira: network access during the build Ignoring request to alter tags of bug #1000182 to the same tags previously set -- 1000182: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1000182 Debian Bug Tracking Syste

Bug#984345: marked as done (sphde: ftbfs with GCC-11)

2021-11-19 Thread Debian Bug Tracking System
Your message dated Fri, 19 Nov 2021 10:18:39 + with message-id and subject line Bug#984345: fixed in sphde 1.4.0-3 has caused the Debian Bug report #984345, regarding sphde: ftbfs with GCC-11 to be marked as done. This means that you claim that the problem has been dealt with. If this is not

Bug#1000157: marked as done (pampi FTBFS: pyuic5: No such file or directory)

2021-11-19 Thread Debian Bug Tracking System
Your message dated Fri, 19 Nov 2021 10:33:40 + with message-id and subject line Bug#1000157: fixed in pampi 1.1+dfsg1-3 has caused the Debian Bug report #1000157, regarding pampi FTBFS: pyuic5: No such file or directory to be marked as done. This means that you claim that the problem has been

Processed (with 2 errors): salt: Set fixed version for security vulnerabilities

2021-11-19 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > fixed 983632 2018.3.4+dfsg1-6+deb10u3 Failed to add fixed on 983632: Not altering archived bugs; see unarchive. > fixed 994016 2018.3.4+dfsg1-6+deb10u3 Bug #994016 {Done: Benjamin Drung } [src:salt] salt: CVE-2021-21996 CVE-2021-22004 Marked as

Processed: salt: #983632

2021-11-19 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > unarchive 983632 Bug #983632 {Done: Benjamin Drung } [src:salt] salt: CVE-2020-28243 CVE-2020-28972 CVE-2020-35662 CVE-2021-3148 CVE-2021-3144 CVE-2021-25281 CVE-2021-25282 CVE-2021-25283 CVE-2021-25284 CVE-2021-3197 Unarchived Bug 983632 > fixe

Bug#1000187: yubikey-manager: Exception when trying to add an oath account

2021-11-19 Thread Tobias Bengfort
Package: yubikey-manager Version: 4.0.0~a1-4 Severity: grave Justification: renders package unusable Dear Maintainer, $ ykman oath accounts add foo bar always results in AttributeError: 'OATH_TYPE' object has no attribute 'upper' The only way to prevent this is to explicitly pass both oa

Bug#1000188: python3.10: testsuite gets stuck in a loop on buildds

2021-11-19 Thread Aurelien Jarno
Source: python3.10 Version: 3.10.0-5 Severity: serious python3.10 testsuite regularly gets stuck in a loop on buildds with the following kind of output: | 186:53:00 load avg: 0.28 running: test_multiprocessing_fork (186 hour 45 min) Full builds logs are available there: https://buildd.debian.org

Processed: bug 996303 is forwarded to https://github.com/nov/json-jwt/issues/96

2021-11-19 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > forwarded 996303 https://github.com/nov/json-jwt/issues/96 Bug #996303 [src:ruby-json-jwt] ruby-json-jwt: FTBFS with ruby3.0: ERROR: Test "ruby3.0" failed: Failure/Error: Set Bug forwarded-to-address to 'https://github.com/nov/json-jwt/issue

Bug#1000197: assimp: binary-any FTBFS

2021-11-19 Thread Adrian Bunk
Source: assimp Version: 5.0.1~ds0-4 Severity: serious Tags: ftbfs https://buildd.debian.org/status/logs.php?pkg=assimp&ver=5.0.1~ds0-4 ... dh clean --buildsystem=cmake dh_auto_clean -O--buildsystem=cmake debian/rules execute_after_dh_auto_clean-arch make[1]: Entering directory '/<>' rm -rf

Bug#1000163: marked as done (phast FTBFS: pcre.h: No such file or directory)

2021-11-19 Thread Debian Bug Tracking System
Your message dated Fri, 19 Nov 2021 13:21:17 + with message-id and subject line Bug#1000163: fixed in phast 1.6+dfsg-3 has caused the Debian Bug report #1000163, regarding phast FTBFS: pcre.h: No such file or directory to be marked as done. This means that you claim that the problem has been

Bug#1000165: marked as done (xdmf FTBFS with more than one supported python3 version)

2021-11-19 Thread Debian Bug Tracking System
Your message dated Fri, 19 Nov 2021 13:22:56 + with message-id and subject line Bug#1000165: fixed in xdmf 3.0+git20190531-10 has caused the Debian Bug report #1000165, regarding xdmf FTBFS with more than one supported python3 version to be marked as done. This means that you claim that the p

Bug#1000163: phast FTBFS: pcre.h: No such file or directory

2021-11-19 Thread Adrian Bunk
On Fri, Nov 19, 2021 at 07:38:14AM +0100, Andreas Tille wrote: > Hi Adrian, Hi Andreas, > Am Thu, Nov 18, 2021 at 11:13:33PM +0200 schrieb Adrian Bunk: > > Source: phast > > Version: 1.6+dfsg-2 > > Severity: serious > > Tags: ftbfs > > > > https://buildd.debian.org/status/logs.php?pkg=phast&ver=

Bug#1000175: marked as pending in magnum-ui

2021-11-19 Thread Thomas Goirand
Control: tag -1 pending Hello, Bug #1000175 in magnum-ui 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/openstack-team/python/python-lz4tools/-/commit/735d350c

Processed: Bug#1000175 marked as pending in magnum-ui

2021-11-19 Thread Debian Bug Tracking System
Processing control commands: > tag -1 pending Bug #1000175 [python3-lz4tools] python3-lz4tools is empty Added tag(s) pending. -- 1000175: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1000175 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems

Bug#1000163: phast FTBFS: pcre.h: No such file or directory

2021-11-19 Thread Andreas Tille
Hi Adrian, Am Fri, Nov 19, 2021 at 03:26:39PM +0200 schrieb Adrian Bunk: > > Just for the sake of interest: If this would not have built in my own > > pbuilder chroot I would not have considered uploading. Well, I could > > have checked Salsa CI first but it seems my assumption "builds in > > pb

Bug#1000175: marked as done (python3-lz4tools is empty)

2021-11-19 Thread Debian Bug Tracking System
Your message dated Fri, 19 Nov 2021 14:39:04 + with message-id and subject line Bug#1000175: fixed in lz4tools 1.3.1.1-5 has caused the Debian Bug report #1000175, regarding python3-lz4tools is empty to be marked as done. This means that you claim that the problem has been dealt with. If this

Processed: python-coverage: diff for NMU version 5.1+dfsg.1-2.1

2021-11-19 Thread Debian Bug Tracking System
Processing control commands: > tags 997378 + patch Bug #997378 [src:python-coverage] python-coverage: FTBFS: AttributeError: 'Sphinx' object has no attribute 'add_stylesheet' Added tag(s) patch. -- 997378: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=997378 Debian Bug Tracking System Conta

Bug#997378: python-coverage: diff for NMU version 5.1+dfsg.1-2.1

2021-11-19 Thread Joe Nahmias
Control: tags 997378 + patch Dear maintainer, I've prepared an NMU for python-coverage (versioned as 5.1+dfsg.1-2.1). The diff is attached to this message. Regards. diff -Nru python-coverage-5.1+dfsg.1/debian/changelog python-coverage-5.1+dfsg.1/debian/changelog --- python-coverage-5.1+dfsg.1/

Bug#984242: marked as done (mpich: ftbfs with GCC-11)

2021-11-19 Thread Debian Bug Tracking System
Your message dated Fri, 19 Nov 2021 15:41:20 + with message-id and subject line Bug#984242: fixed in mpich 4.0~b1-1 has caused the Debian Bug report #984242, regarding mpich: ftbfs with GCC-11 to be marked as done. This means that you claim that the problem has been dealt with. If this is not

Bug#997378: marked as done (python-coverage: FTBFS: AttributeError: 'Sphinx' object has no attribute 'add_stylesheet')

2021-11-19 Thread Debian Bug Tracking System
Your message dated Fri, 19 Nov 2021 15:42:22 + with message-id and subject line Bug#997378: fixed in python-coverage 5.1+dfsg.1-2.1 has caused the Debian Bug report #997378, regarding python-coverage: FTBFS: AttributeError: 'Sphinx' object has no attribute 'add_stylesheet' to be marked as don

Bug#1000204: pyfai: FTBFS if built using python3.10 (collections.MutableSets deprecated)

2021-11-19 Thread Lukas Märdian
Package: pyfai Version: 0.20.0+dfsg1-4 Severity: serious Tags: patch ftbfs Justification: fails to build from source (but built successfully in the past) User: ubuntu-de...@lists.ubuntu.com Usertags: origin-ubuntu jammy ubuntu-patch X-Debbugs-Cc: sl...@ubuntu.com Dear Maintainer, collections.Muta

Bug#997698: marked as done (pg-dirtyread: FTBFS: Error: debian/control needs updating from debian/control.in. Run 'pg_buildext updatecontrol'.)

2021-11-19 Thread Debian Bug Tracking System
Your message dated Fri, 19 Nov 2021 16:59:51 +0100 with message-id and subject line Re: Bug#997698: pg-dirtyread: FTBFS: Error: debian/control needs updating from debian/control.in. Run 'pg_buildext updatecontrol'. has caused the Debian Bug report #997698, regarding pg-dirtyread: FTBFS: Error: de

Bug#999370: marked as done (pystemd ftbfs with Python 3.10)

2021-11-19 Thread Debian Bug Tracking System
Your message dated Fri, 19 Nov 2021 16:04:39 + with message-id and subject line Bug#999370: fixed in pystemd 0.7.0-5 has caused the Debian Bug report #999370, regarding pystemd ftbfs with Python 3.10 to be marked as done. This means that you claim that the problem has been dealt with. If this

Bug#999373: marked as pending in python-dmidecode

2021-11-19 Thread Stefano Rivera
Control: tag -1 pending Hello, Bug #999373 in python-dmidecode 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/python-team/packages/python-dmidecode/-/commit/c1

Processed: Bug#999373 marked as pending in python-dmidecode

2021-11-19 Thread Debian Bug Tracking System
Processing control commands: > tag -1 pending Bug #999373 [src:python-dmidecode] python-dmidcode ftbfs with Python 3.10 (test failures) Added tag(s) pending. -- 999373: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=999373 Debian Bug Tracking System Contact ow...@bugs.debian.org with problem

Bug#997176: marked as done (pgmodeler: FTBFS: Project ERROR: libpq development package not found)

2021-11-19 Thread Debian Bug Tracking System
Your message dated Fri, 19 Nov 2021 17:12:52 +0100 with message-id and subject line Re: Bug#997176: pgmodeler: FTBFS: Project ERROR: libpq development package not found has caused the Debian Bug report #997176, regarding pgmodeler: FTBFS: Project ERROR: libpq development package not found to be m

Bug#999374: marked as done (python-gammu ftbfs with Python 3.10 (test failures))

2021-11-19 Thread Debian Bug Tracking System
Your message dated Fri, 19 Nov 2021 16:37:17 + with message-id and subject line Bug#999374: fixed in python-gammu 3.2.4-1 has caused the Debian Bug report #999374, regarding python-gammu ftbfs with Python 3.10 (test failures) to be marked as done. This means that you claim that the problem ha

Bug#984384: marked as done (varconf: ftbfs with GCC-11)

2021-11-19 Thread Debian Bug Tracking System
Your message dated Fri, 19 Nov 2021 17:06:05 + with message-id and subject line Bug#984384: fixed in varconf 1.0.1-8 has caused the Debian Bug report #984384, regarding varconf: ftbfs with GCC-11 to be marked as done. This means that you claim that the problem has been dealt with. If this is

Bug#999743: marked as done (xfsprogs FTBFS: .gitcensus: No such file or directory)

2021-11-19 Thread Debian Bug Tracking System
Your message dated Fri, 19 Nov 2021 18:33:43 +0100 with message-id and subject line xfsprogs fix has caused the Debian Bug report #999743, regarding xfsprogs FTBFS: .gitcensus: No such file or directory to be marked as done. This means that you claim that the problem has been dealt with. If this

Bug#999853: marked as done (src:boost1.74: fails to migrate to testing for too long: FTBFS on armhf)

2021-11-19 Thread Debian Bug Tracking System
Your message dated Fri, 19 Nov 2021 17:33:36 + with message-id and subject line Bug#999853: fixed in boost1.74 1.74.0-13 has caused the Debian Bug report #999853, regarding src:boost1.74: fails to migrate to testing for too long: FTBFS on armhf to be marked as done. This means that you claim

Bug#999760: marked as done (opencv: libopencv-*4.5d: missing Breaks+Replaces: libopencv-*4.5)

2021-11-19 Thread Debian Bug Tracking System
Your message dated Fri, 19 Nov 2021 18:34:42 + with message-id and subject line Bug#999760: fixed in opencv 4.5.4+dfsg-4 has caused the Debian Bug report #999760, regarding opencv: libopencv-*4.5d: missing Breaks+Replaces: libopencv-*4.5 to be marked as done. This means that you claim that th

Bug#999376: marked as pending in python-gmpy2

2021-11-19 Thread Stefano Rivera
Control: tag -1 pending Hello, Bug #999376 in python-gmpy2 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/python-team/packages/python-gmpy2/-/commit/30777bba0f

Processed: Bug#999376 marked as pending in python-gmpy2

2021-11-19 Thread Debian Bug Tracking System
Processing control commands: > tag -1 pending Bug #999376 [src:python-gmpy2] python-gmpy2 ftbfs with Python 3.10 Added tag(s) pending. -- 999376: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=999376 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems

Bug#1000210: [regression] uscan die: filenamemangle failed

2021-11-19 Thread Michael Biebl
Package: devscripts Version: 2.21.5 Severity: serious Hi, since upgrading to devscrips 2.21.5, uscan fails when trying to run it for the systemd package: $ uscan --report --verbose uscan info: uscan (version 2.21.5) See uscan(1) for help uscan info: Scan watch files in . find: Dateisystemschleif

Processed: Bug#999380 marked as pending in python-lzo

2021-11-19 Thread Debian Bug Tracking System
Processing control commands: > tag -1 pending Bug #999380 [src:python-lzo] python-lzo ftbfs with Python 3.10 (test failures) Added tag(s) pending. -- 999380: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=999380 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems

Bug#999380: marked as pending in python-lzo

2021-11-19 Thread Stefano Rivera
Control: tag -1 pending Hello, Bug #999380 in python-lzo 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/python-team/packages/python-lzo/-/commit/12313fdb5ba010

Processed: fixed 999743 in 5.14.0-release-1

2021-11-19 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > fixed 999743 5.14.0-release-1 Bug #999743 {Done: Bastian Germann } [src:xfsprogs] xfsprogs FTBFS: .gitcensus: No such file or directory The source 'xfsprogs' and version '5.14.0-release-1' do not appear to match any binary packages Marked as fix

Bug#1000213: gcc-python-plugin: Don't use -Werror=deprecated-declarations

2021-11-19 Thread Steve Langasek
Package: gcc-python-plugin Version: 0.17-6 Severity: serious Tags: patch Justification: ftbfs User: ubuntu-de...@lists.ubuntu.com Usertags: origin-ubuntu jammy ubuntu-patch Hello, The gcc-python-plugin package currently fails to build because the source uses functions that are deprecated in pytho

Bug#702011: gtkmathview: uses pangox which is going away

2021-11-19 Thread Paul Gevers
Hi, On Fri, 01 Mar 2013 17:13:47 +0100 Emilio Pozuelo Monfort wrote: gtkmathview uses pangox internally. pangox is no longer maintained and we want to remove it from Debian. Ideally gtkmathview should stop using pangox, perhaps by using one of the other pango backends. Unless you object (pl

Bug#702011: gtkmathview: uses pangox which is going away

2021-11-19 Thread Sylvestre Ledru
Hello, Le 19/11/2021 à 21:09, Paul Gevers a écrit : > Hi, > > On Fri, 01 Mar 2013 17:13:47 +0100 Emilio Pozuelo Monfort > wrote: >> gtkmathview uses pangox internally. pangox is no longer maintained >> and we want to remove it from Debian. Ideally gtkmathview should stop >> using pangox, perhaps

Bug#1000215: glusterfs: FTBFS on armel, armhf, mipsel

2021-11-19 Thread Sebastian Ramacher
Source: glusterfs Version: 10.0-1.2 Severity: serious Tags: ftbfs Justification: fails to build from source (but built successfully in the past) X-Debbugs-Cc: sramac...@debian.org, Christian Ehrhardt | libtool: link: gcc -Wall -I/usr/include/uuid -I/usr/include/tirpc -Wformat -Werror=format-sec

Processed: RM: pangox-compat -- RoQA; deprecated since 2012

2021-11-19 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > reassign 947649 ftp.debian.org Bug #947649 [src:pangox-compat] pangox-compat: deprecated since 2012, unmaintained, should probably be removed Bug reassigned from package 'src:pangox-compat' to 'ftp.debian.org'. No longer marked as found in versio

Bug#999380: marked as done (python-lzo ftbfs with Python 3.10 (test failures))

2021-11-19 Thread Debian Bug Tracking System
Your message dated Fri, 19 Nov 2021 20:47:46 + with message-id and subject line Bug#999380: fixed in python-lzo 1.12-4 has caused the Debian Bug report #999380, regarding python-lzo ftbfs with Python 3.10 (test failures) to be marked as done. This means that you claim that the problem has bee

Processed: tagging 984233

2021-11-19 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > tags 984233 + ftbfs Bug #984233 {Done: Alastair McKinstry } [src:mia] mia: ftbfs with GCC-11 Added tag(s) ftbfs. > thanks Stopping processing here. Please contact me if you need assistance. -- 984233: https://bugs.debian.org/cgi-bin/bugreport.c

Bug#999376: marked as done (python-gmpy2 ftbfs with Python 3.10)

2021-11-19 Thread Debian Bug Tracking System
Your message dated Fri, 19 Nov 2021 21:40:53 + with message-id and subject line Bug#999376: fixed in python-gmpy2 2.1.0~b5-1 has caused the Debian Bug report #999376, regarding python-gmpy2 ftbfs with Python 3.10 to be marked as done. This means that you claim that the problem has been dealt

Bug#1000220: dicomscope: error: cannot bind non-const lvalue reference of type ‘std::__cxx11::list >::const_iterator&’ to an rvalue of type ‘std::__cxx11::list

2021-11-19 Thread Sebastian Ramacher
Source: dicomscope Version: 3.6.0-22 Severity: serious Tags: ftbfs sid bookworm Justification: fails to build from source (but built successfully in the past) X-Debbugs-Cc: sramac...@debian.org | cd /<>/obj-x86_64-linux-gnu/interface/libsrc && /usr/bin/c++ -DHAVE_CONFIG_H -DHAVE_STRSTREAM_H -DNDE

Bug#1000221: ginkgocadx: error: ‘OFIterator’ was not declared in this scope; did you mean ‘OF_error’?

2021-11-19 Thread Sebastian Ramacher
Source: ginkgocadx Version: 3.8.8-5 Severity: serious Tags: ftbfs sid bookworm Justification: fails to build from source (but built successfully in the past) X-Debbugs-Cc: sramac...@debian.org | cd /<>/obj-x86_64-linux-gnu/cadxcore && /usr/bin/c++ -DAPIEXPORT -DCURL_STATICLIB -DDCMTK_POST_2017022

Bug#1000222: orthanc: DCMTK was configured to use C++14 features, but your compiler does not or was not configured to provide them.

2021-11-19 Thread Sebastian Ramacher
Source: orthanc Version: 1.9.7+dfsg-1 Severity: serious Tags: ftbfs sid bookworm Justification: fails to build from source (but built successfully in the past) X-Debbugs-Cc: sramac...@debian.org | /usr/bin/c++ -DBOOST_ALL_NO_LIB -DBOOST_ATOMIC_DYN_LINK -DBOOST_CHRONO_DYN_LINK -DBOOST_DATE_TIME_DY

Bug#1000224: plastimatch: DCMTK was configured to use C++14 features, but your compiler does not or was not configured to provide them.

2021-11-19 Thread Sebastian Ramacher
Source: plastimatch Version: 1.9.3+dfsg.1-1 Severity: serious Tags: ftbfs sid bookworm Justification: fails to build from source (but built successfully in the past) X-Debbugs-Cc: sramac...@debian.org | cd /<>/obj-x86_64-linux-gnu/src/plastimatch/base && /usr/bin/c++ -DITK_IO_FACTORY_REGISTER_MAN

Processed: limit source to php-async-aws-core, tagging 995908

2021-11-19 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > limit source php-async-aws-core Limiting to bugs with field 'source' containing at least one of 'php-async-aws-core' Limit currently set to 'source':'php-async-aws-core' > tags 995908 + pending Bug #995908 [src:php-async-aws-core] php-async-aws-

Bug#996369: marked as done (ruby-responders: FTBFS with ruby3.0: ERROR: Test "ruby3.0" failed.)

2021-11-19 Thread Debian Bug Tracking System
Your message dated Fri, 19 Nov 2021 22:09:49 + with message-id and subject line Bug#996369: fixed in ruby-responders 3.0.1-2 has caused the Debian Bug report #996369, regarding ruby-responders: FTBFS with ruby3.0: ERROR: Test "ruby3.0" failed. to be marked as done. This means that you claim t

Processed: reassign 995358 to src:ruby-graphql

2021-11-19 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > reassign 995358 src:ruby-graphql 1.11.8-2 Bug #995358 [src:ruby-batch-loader] ruby-graphql breaks ruby-batch-loader autopkgtest: uninitialized constant GraphQL::StaticValidation::Validator::Timeout Bug reassigned from package 'src:ruby-batch-loa

Processed: tagging 995358

2021-11-19 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > # > https://github.com/rmosolgo/graphql-ruby/commit/56abba472dbb48a1f8445d41f928bea72b5148e9.patch > tags 995358 + fixed-upstream patch Bug #995358 [src:ruby-graphql] ruby-graphql breaks ruby-batch-loader autopkgtest: uninitialized constant Gra

Processed: block 996159 with 995358

2021-11-19 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > block 996159 with 995358 Bug #996159 [src:ruby-batch-loader] ruby-batch-loader: FTBFS: ERROR: Test "ruby2.7" failed: Failure/Error: result = schema.execute(query) 996159 was not blocked by any bugs. 996159 was not blocking any bugs. Added bl

Bug#1000226: python-python-docx_0.8.11+dfsg1-2_all-buildd.changes REJECTED

2021-11-19 Thread Aurelien Jarno
Source: python-python-docx Version: 0.8.11+dfsg1-2 Severity: serious On 2021-11-19 17:49, Debian FTP Masters wrote: > > python3-python-docx_0.8.11+dfsg1-2_all.deb: Does not match binary in database. > > > Mapping sid to unstable. > > === > > Please feel free to respond to this email if you do

Processed: Bug#995358 marked as pending in ruby-graphql

2021-11-19 Thread Debian Bug Tracking System
Processing control commands: > tag -1 pending Bug #995358 [src:ruby-graphql] ruby-graphql breaks ruby-batch-loader autopkgtest: uninitialized constant GraphQL::StaticValidation::Validator::Timeout Added tag(s) pending. -- 995358: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=995358 Debian

Bug#995358: marked as pending in ruby-graphql

2021-11-19 Thread Daniel Leidert
Control: tag -1 pending Hello, Bug #995358 in ruby-graphql 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/ruby-team/ruby-graphql/-/commit/68709ce9c8c544d7c9df4

Bug#1000229: binary package is missing /usr/sbin/memlockd

2021-11-19 Thread Sven Hartge
Package: memlockd Version: 1.3-2 Severity: grave Hello! The subject says it all: The package is missing the binary: , | oweh@ds9:~$ dpkg -L memlockd | /. | /etc | /etc/default | /etc/init.d | /etc/init.d/memlockd | /etc/memlockd.d | /lib | /lib/systemd | /lib/systemd/system | /lib/systemd/sy

Bug#996159: marked as pending in ruby-batch-loader

2021-11-19 Thread Daniel Leidert
Control: tag -1 pending Hello, Bug #996159 in ruby-batch-loader 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/ruby-team/ruby-batch-loader/-/commit/df92d61337b

Processed: Bug#996159 marked as pending in ruby-batch-loader

2021-11-19 Thread Debian Bug Tracking System
Processing control commands: > tag -1 pending Bug #996159 [src:ruby-batch-loader] ruby-batch-loader: FTBFS: ERROR: Test "ruby2.7" failed: Failure/Error: result = schema.execute(query) Added tag(s) pending. -- 996159: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=996159 Debian Bug Track

Bug#995358: marked as done (ruby-graphql breaks ruby-batch-loader autopkgtest: uninitialized constant GraphQL::StaticValidation::Validator::Timeout)

2021-11-19 Thread Debian Bug Tracking System
Your message dated Fri, 19 Nov 2021 22:50:33 + with message-id and subject line Bug#995358: fixed in ruby-graphql 1.11.8-3 has caused the Debian Bug report #995358, regarding ruby-graphql breaks ruby-batch-loader autopkgtest: uninitialized constant GraphQL::StaticValidation::Validator::Timeou

Bug#996228: marked as pending in ruby-ffaker

2021-11-19 Thread Daniel Leidert
Control: tag -1 pending Hello, Bug #996228 in ruby-ffaker 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/ruby-team/ruby-ffaker/-/commit/a341b7e36f4f9bcbe855064

Processed: Bug#996228 marked as pending in ruby-ffaker

2021-11-19 Thread Debian Bug Tracking System
Processing control commands: > tag -1 pending Bug #996228 [src:ruby-ffaker] ruby-ffaker: FTBFS with ruby3.0: ERROR: Test "ruby3.0" failed: Error: test_ssn_with_from_to(TestSSNSE): ArgumentError: wrong number of arguments (given 4, expected 3) Added tag(s) pending. -- 996228: https://bugs.debia

Bug#996159: marked as done (ruby-batch-loader: FTBFS: ERROR: Test "ruby2.7" failed: Failure/Error: result = schema.execute(query))

2021-11-19 Thread Debian Bug Tracking System
Your message dated Fri, 19 Nov 2021 23:05:44 + with message-id and subject line Bug#996159: fixed in ruby-batch-loader 2.0.1+dfsg-3 has caused the Debian Bug report #996159, regarding ruby-batch-loader: FTBFS: ERROR: Test "ruby2.7" failed: Failure/Error: result = schema.execute(query) to

Processed: installing canberra-gtk-module doesn't help

2021-11-19 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > severity 1000230 grave Bug #1000230 [screenruler] screenruler fails to start Severity set to 'grave' from 'normal' > thanks Stopping processing here. Please contact me if you need assistance. -- 1000230: https://bugs.debian.org/cgi-bin/bugreport

Bug#996117: Update after uploading Rails 6.1

2021-11-19 Thread Daniel Leidert
With Rails 6.1 the package now fails to build with Ruby 2.7 and a bunch of errors like this: Failure: ActionController::Serialization::ImplicitSerializerTest#test_render_array_using_custom_root [/<>/test/action_controller/serialization_test.rb:186]: --- expected +++ actual @@ -1 +1 @@ -"applicati

Bug#1000231: ceres-solver: error: variable or field ‘it’ declared void

2021-11-19 Thread Sebastian Ramacher
Source: ceres-solver Version: 1.14.0-14 Severity: serious Tags: ftbfs sid bookworm Justification: fails to build from source (but built successfully in the past) X-Debbugs-Cc: sramac...@debian.org | In file included from /<>/internal/ceres/residual_block_test.cc:33: | /<>/internal/ceres/gtest/gte

Bug#996117: Update after uploading Rails 6.1

2021-11-19 Thread Daniel Leidert
Am Samstag, dem 20.11.2021 um 00:18 +0100 schrieb Daniel Leidert: > With Rails 6.1 the package now fails to build with Ruby 2.7 and a bunch of > errors like this: > > Failure: > ActionController::Serialization::ImplicitSerializerTest#test_render_array_using > _custom_root > [/<>/test/action_contro

Bug#996228: marked as done (ruby-ffaker: FTBFS with ruby3.0: ERROR: Test "ruby3.0" failed: Error: test_ssn_with_from_to(TestSSNSE): ArgumentError: wrong number of arguments (given 4, expected 3))

2021-11-19 Thread Debian Bug Tracking System
Your message dated Fri, 19 Nov 2021 23:36:55 + with message-id and subject line Bug#996228: fixed in ruby-ffaker 2.13.0-3 has caused the Debian Bug report #996228, regarding ruby-ffaker: FTBFS with ruby3.0: ERROR: Test "ruby3.0" failed: Error: test_ssn_with_from_to(TestSSNSE): ArgumentError:

Bug#1000233: php-remctl lost its phpapi-20190902 dependency

2021-11-19 Thread Adrian Bunk
Package: php-remctl Version: 3.17-1 Severity: serious Tags: bookworm sid After the src:remctl rebuild to add Python 3.10 as supported version, php-remctl lost its phpapi-20190902 dependency: Package: php-remctl Source: remctl Version: 3.17-1 Installed-Size: 109 Depends: php-common (>= 1:7.0+33~),

Bug#1000237: pygame: FTBFS with python3.10

2021-11-19 Thread Steve Langasek
Package: pygame Version: 1.9.6+dfsg-4 Severity: serious Tags: patch Justification: FTBFS User: ubuntu-de...@lists.ubuntu.com Usertags: origin-ubuntu jammy ubuntu-patch Dear maintainers, Now that python3.10 is a supported python version in unstable, pygame fails to build from source. I wasn't abl

Bug#999381: python-pairix ftbfs with Python 3.10 (test failures)

2021-11-19 Thread Stefano Rivera
Control: affects -1 python3.10 Hi Matthias (2021.11.10_11:31:16_-0400) This looks like fallout from https://bugs.python.org/issue45475, a Python 3.10 regression. python-pairix is easily patched to avoid hitting the bug, though. SR -- Stefano Rivera http://tumbleweed.org.za/ +1 415 683 327

Processed: Re: Bug#999381: python-pairix ftbfs with Python 3.10 (test failures)

2021-11-19 Thread Debian Bug Tracking System
Processing control commands: > affects -1 python3.10 Bug #999381 [src:python-pairix] python-pairix ftbfs with Python 3.10 (test failures) Added indication that 999381 affects python3.10 -- 999381: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=999381 Debian Bug Tracking System Contact ow...@

Bug#999381: python-pairix: diff for NMU version 0.3.7-4.1

2021-11-19 Thread Stefano Rivera
Control: tags 999381 + patch Dear maintainer, I've prepared an NMU for python-pairix (versioned as 0.3.7-4.1). The diff is attached to this message. Regards. SR diff -Nru python-pairix-0.3.7/debian/changelog python-pairix-0.3.7/debian/changelog --- python-pairix-0.3.7/debian/changelog 2021-10-0

Processed: python-pairix: diff for NMU version 0.3.7-4.1

2021-11-19 Thread Debian Bug Tracking System
Processing control commands: > tags 999381 + patch Bug #999381 [src:python-pairix] python-pairix ftbfs with Python 3.10 (test failures) Added tag(s) patch. -- 999381: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=999381 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems

Processed: Bug#999385 marked as pending in python-pyalsa

2021-11-19 Thread Debian Bug Tracking System
Processing control commands: > tag -1 pending Bug #999385 [src:python-pyalsa] python-pyalsa ftbfs with Python 3.10 Added tag(s) pending. -- 999385: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=999385 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems

Bug#999385: marked as pending in python-pyalsa

2021-11-19 Thread Stefano Rivera
Control: tag -1 pending Hello, Bug #999385 in python-pyalsa 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/python-team/packages/python-pyalsa/-/commit/cd02a79d

Bug#999381: marked as done (python-pairix ftbfs with Python 3.10 (test failures))

2021-11-19 Thread Debian Bug Tracking System
Your message dated Sat, 20 Nov 2021 03:04:46 + with message-id and subject line Bug#999381: fixed in python-pairix 0.3.7-4.1 has caused the Debian Bug report #999381, regarding python-pairix ftbfs with Python 3.10 (test failures) to be marked as done. This means that you claim that the proble

Bug#999385: marked as done (python-pyalsa ftbfs with Python 3.10)

2021-11-19 Thread Debian Bug Tracking System
Your message dated Sat, 20 Nov 2021 03:04:52 + with message-id and subject line Bug#999385: fixed in python-pyalsa 1.1.6-3 has caused the Debian Bug report #999385, regarding python-pyalsa ftbfs with Python 3.10 to be marked as done. This means that you claim that the problem has been dealt w

Bug#999373: marked as done (python-dmidcode ftbfs with Python 3.10 (test failures))

2021-11-19 Thread Debian Bug Tracking System
Your message dated Sat, 20 Nov 2021 03:51:02 + with message-id and subject line Bug#999373: fixed in python-dmidecode 3.12.2-13 has caused the Debian Bug report #999373, regarding python-dmidcode ftbfs with Python 3.10 (test failures) to be marked as done. This means that you claim that the p

Processed: Re: libjs-xterm: update to newer major release for bullseye

2021-11-19 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > retitle 964170 new upstream (4.15) Bug #964170 [libjs-xterm] libjs-xterm: update to newer major release for bullseye Changed Bug title to 'new upstream (4.15)' from 'libjs-xterm: update to newer major release for bullseye'. > severity 964170 nor

Bug#995318: marked as done (numpy: Does not build from source in current unstable)

2021-11-19 Thread Debian Bug Tracking System
Your message dated Sat, 20 Nov 2021 05:03:34 + with message-id and subject line Bug#995318: fixed in numpy 1:1.21.4-2 has caused the Debian Bug report #995318, regarding numpy: Does not build from source in current unstable to be marked as done. This means that you claim that the problem has

Processed: severity of 999515 is serious, severity of 999517 is serious, severity of 999522 is serious ...

2021-11-19 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > # > https://tracker.debian.org/news/1278745/accepted-numpy-11214-2-source-into-unstable/ > severity 999515 serious Bug #999515 [src:imbalanced-learn] imbalanced-learn: FTBFS with numpy 1.21 (in experimental): dh_auto_test: error: pybuild --test

Processed: bts

2021-11-19 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > block 1000242 by 996042 Bug #1000242 [node-css-loader] new upstream required for ttyd 1000242 was not blocked by any bugs. 1000242 was not blocking any bugs. Added blocking bug(s) of 1000242: 996042 > thanks Stopping processing here. Please conta

Processed: Bug#1000224 marked as pending in plastimatch

2021-11-19 Thread Debian Bug Tracking System
Processing control commands: > tag -1 pending Bug #1000224 [src:plastimatch] plastimatch: DCMTK was configured to use C++14 features, but your compiler does not or was not configured to provide them. Added tag(s) pending. -- 1000224: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1000224 Deb

  1   2   >