Bug#1060792: marked as done (r-cran-openmx: switch to default version of boost)

2024-01-14 Thread Debian Bug Tracking System
Your message dated Mon, 15 Jan 2024 07:51:05 + with message-id and subject line Bug#1060792: fixed in r-cran-openmx 2.21.11+dfsg-2 has caused the Debian Bug report #1060792, regarding r-cran-openmx: switch to default version of boost to be marked as done. This means that you claim that the

Processed: severity of 1059701 is serious

2024-01-14 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > severity 1059701 serious Bug #1059701 [sccache] sccache - upcoming rust-object update Severity set to 'serious' from 'normal' > thanks Stopping processing here. Please contact me if you need assistance. -- 1059701:

Bug#1056764: grub-efi-amd64: can't boot with GRUB 2.12~rc1-12

2024-01-14 Thread Mate Kukri
Hello, Just letting you know that the 2.12 merge is in progress, and GRUB 2.12 (non-rc1) will be available in Debian the (hopefully) not too distant future. Mate On Fri, Jan 12, 2024 at 9:18 PM wrote: > > Good day, > > does grub 2.12 (without rc1) help? There are a good pile of fixups >

Bug#1059812: marked as done (elan - dependency updates.)

2024-01-14 Thread Debian Bug Tracking System
Your message dated Mon, 15 Jan 2024 07:35:45 + with message-id and subject line has caused the Debian Bug report #1059812, regarding elan - dependency updates. 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#1058278: marked as done (r-bioc-demixt: FTBFS: build-dependency not installable: r-api-bioc-3.17)

2024-01-14 Thread Debian Bug Tracking System
Your message dated Mon, 15 Jan 2024 07:36:48 + with message-id and subject line Bug#1058278: fixed in r-bioc-demixt 1.18.0+dfsg-1 has caused the Debian Bug report #1058278, regarding r-bioc-demixt: FTBFS: build-dependency not installable: r-api-bioc-3.17 to be marked as done. This means

Bug#1058613: marked as done (r-bioc-dss: Prevent migration to testing due to missing source)

2024-01-14 Thread Debian Bug Tracking System
Your message dated Mon, 15 Jan 2024 07:21:09 + with message-id and subject line Bug#1058613: fixed in r-bioc-dss 2.50.1+dfsg-1 has caused the Debian Bug report #1058613, regarding r-bioc-dss: Prevent migration to testing due to missing source to be marked as done. This means that you claim

Processed: severity of 1060119 is serious

2024-01-14 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > severity 1060119 serious Bug #1060119 [src:python-vulndb] python-vulndb: please patch-out dependency on python3-future Severity set to 'serious' from 'important' > thanks Stopping processing here. Please contact me if you need assistance. --

Processed: severity of 1059109 is serious

2024-01-14 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > severity 1059109 serious Bug #1059109 [src:plaso] plaso: please remove extraneous dependency on python3-future Severity set to 'serious' from 'important' > thanks Stopping processing here. Please contact me if you need assistance. -- 1059109:

Processed: severity of 1060116 is serious

2024-01-14 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > severity 1060116 serious Bug #1060116 [src:wfuzz] wfuzz: please remove python3-future build-dependency Severity set to 'serious' from 'important' > thanks Stopping processing here. Please contact me if you need assistance. -- 1060116:

Processed: severity of 1059110 is serious

2024-01-14 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > severity 1059110 serious Bug #1059110 [src:chirp] chirp: please remove extraneous dependency on python3-future Severity set to 'serious' from 'important' > thanks Stopping processing here. Please contact me if you need assistance. -- 1059110:

Processed: severity of 1058987 is serious

2024-01-14 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > severity 1058987 serious Bug #1058987 [src:turing] turing: please remove extraneous dependency on python3-future Severity set to 'serious' from 'important' > thanks Stopping processing here. Please contact me if you need assistance. --

Bug#1058410: marked as done (smbus2: FTBFS: dh_auto_test: error: pybuild --test --test-pytest -i python{version} -p "3.12 3.11" returned exit code 13)

2024-01-14 Thread Debian Bug Tracking System
Your message dated Mon, 15 Jan 2024 06:49:49 + with message-id and subject line Bug#1058410: fixed in smbus2 0.4.3-1 has caused the Debian Bug report #1058410, regarding smbus2: FTBFS: dh_auto_test: error: pybuild --test --test-pytest -i python{version} -p "3.12 3.11" returned exit code 13

Bug#1060827: hxtools has an undeclared file conflict on /usr/bin/xmlformat

2024-01-14 Thread Helmut Grohne
Package: hxtools Version: 20231224-1 Severity: serious User: debian...@lists.debian.org Usertags: fileconflict Control: affects -1 + xmlformat-perl xmlformat-ruby hxtools has an undeclared file conflict. This may result in an unpack error from dpkg. The file /usr/bin/xmlformat is contained in

Processed: hxtools has an undeclared file conflict on /usr/bin/xmlformat

2024-01-14 Thread Debian Bug Tracking System
Processing control commands: > affects -1 + xmlformat-perl xmlformat-ruby Bug #1060827 [hxtools] hxtools has an undeclared file conflict on /usr/bin/xmlformat Added indication that 1060827 affects xmlformat-perl and xmlformat-ruby -- 1060827:

Bug#1055697: marked as done (pivy ftbfs with Python 3.12)

2024-01-14 Thread Debian Bug Tracking System
Your message dated Mon, 15 Jan 2024 06:04:00 + with message-id and subject line Bug#1055697: fixed in pivy 0.6.9~a0-1 has caused the Debian Bug report #1055697, regarding pivy ftbfs with Python 3.12 to be marked as done. This means that you claim that the problem has been dealt with. If this

Bug#1059990: marked as done (vcr.py: autopkgtest failure with Python 3.12)

2024-01-14 Thread Debian Bug Tracking System
Your message dated Mon, 15 Jan 2024 02:49:03 + with message-id and subject line Bug#1059990: fixed in vcr.py 5.1.0-1.1 has caused the Debian Bug report #1059990, regarding vcr.py: autopkgtest failure with Python 3.12 to be marked as done. This means that you claim that the problem has been

Processed: Bug#1059990 marked as pending in vcr.py

2024-01-14 Thread Debian Bug Tracking System
Processing control commands: > tag -1 pending Bug #1059990 [src:vcr.py] vcr.py: autopkgtest failure with Python 3.12 Added tag(s) pending. -- 1059990: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1059990 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems

Bug#1059990: marked as pending in vcr.py

2024-01-14 Thread Matthias Klose
Control: tag -1 pending Hello, Bug #1059990 in vcr.py 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:

Bug#1057430:

2024-01-14 Thread john faulk
I can't seem to figure why, it compiles fine on my machine. the error you're showing is due to libsdbus-c++-dev being missing from your system. If this is not in the build-deps, a simple fix would be to add this package to them.

Bug#1056414: marked as pending in ipython4

2024-01-14 Thread Stefano Rivera
Control: tag -1 pending Hello, Bug #1056414 in ipython4 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:

Processed: Bug#1056414 marked as pending in ipython4

2024-01-14 Thread Debian Bug Tracking System
Processing control commands: > tag -1 pending Bug #1056414 [src:ipython] ipython's autopkg tests fail with Python 3.12 Added tag(s) pending. -- 1056414: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1056414 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems

Bug#1060698: marked as done (yubioath-desktop: Doesn't see yubikeys anymore.)

2024-01-14 Thread Debian Bug Tracking System
Your message dated Sun, 14 Jan 2024 22:50:54 + with message-id and subject line Bug#1060698: fixed in yubioath-desktop 5.1.0-3 has caused the Debian Bug report #1060698, regarding yubioath-desktop: Doesn't see yubikeys anymore. to be marked as done. This means that you claim that the problem

Bug#1052938: marked as done (wine: FTBFS: Open failed: No such file or directory at ./tools/make_unicode line 1920.)

2024-01-14 Thread Debian Bug Tracking System
Your message dated Sun, 14 Jan 2024 22:33:11 + with message-id and subject line Bug#1052938: fixed in wine 8.0.2~repack-1 has caused the Debian Bug report #1052938, regarding wine: FTBFS: Open failed: No such file or directory at ./tools/make_unicode line 1920. to be marked as done. This

Bug#1054829: php-fpdf: FTBFS: make: *** [/usr/share/quilt/quilt.make:23: unpatch] Error 1

2024-01-14 Thread Bastian Germann
Control: fixed -1 php-fpdf/3:1.8.4.dfsg-2

Processed: Re: php-fpdf: FTBFS: make: *** [/usr/share/quilt/quilt.make:23: unpatch] Error 1

2024-01-14 Thread Debian Bug Tracking System
Processing control commands: > fixed -1 php-fpdf/3:1.8.4.dfsg-2 Bug #1054829 {Done: Bastian Germann } [src:php-fpdf] php-fpdf: FTBFS: make: *** [/usr/share/quilt/quilt.make:23: unpatch] Error 1 The source php-fpdf and version 3:1.8.4.dfsg-2 do not appear to match any binary packages Marked as

Bug#1013285: marked as done (needrestart: Failed to check for processor microcode upgrades.)

2024-01-14 Thread Debian Bug Tracking System
Your message dated Sun, 14 Jan 2024 22:17:09 + with message-id and subject line Bug#1013285: fixed in needrestart 3.6-4+deb12u1 has caused the Debian Bug report #1013285, regarding needrestart: Failed to check for processor microcode upgrades. to be marked as done. This means that you claim

Bug#1060698: [Pkg-auth-maintainers] Bug#1060698: Bug#1060698: yubioath-desktop: Doesn't see yubikeys anymore.

2024-01-14 Thread Florian Schlichting
Hi Sébastien, On Sun, Jan 14, 2024 at 02:36:38PM +0100, Sébastien Noel wrote: > for what it's worth, i have been running yubioath with this patch > for ~11 months, so I would feel confident to ship it in Debian > and take responsibility for it very good, I'm going to prepare an upload that

Bug#1058197: marked as done (straight.plugin: FTBFS: ModuleNotFoundError: No module named 'imp')

2024-01-14 Thread Debian Bug Tracking System
Your message dated Sun, 14 Jan 2024 21:48:52 + with message-id and subject line Bug#1058197: fixed in straight.plugin 1.4.1-5 has caused the Debian Bug report #1058197, regarding straight.plugin: FTBFS: ModuleNotFoundError: No module named 'imp' to be marked as done. This means that you

Bug#1058188: marked as done (python-spinners: FTBFS: AttributeError: 'TestSpinners' object has no attribute 'assertEquals'. Did you mean: 'assertEqual'?)

2024-01-14 Thread Debian Bug Tracking System
Your message dated Sun, 14 Jan 2024 21:41:56 + with message-id and subject line Bug#1058188: fixed in python-spinners 0.0~git20200220.a73d561-4 has caused the Debian Bug report #1058188, regarding python-spinners: FTBFS: AttributeError: 'TestSpinners' object has no attribute 'assertEquals'.

Bug#1058107: marked as done (python-django-rest-hooks: FTBFS: AttributeError: 'RESTHooksTest' object has no attribute 'assertEquals'. Did you mean: 'assertEqual'?)

2024-01-14 Thread Debian Bug Tracking System
Your message dated Sun, 14 Jan 2024 21:41:37 + with message-id and subject line Bug#1058107: fixed in python-django-rest-hooks 1.6.0-4 has caused the Debian Bug report #1058107, regarding python-django-rest-hooks: FTBFS: AttributeError: 'RESTHooksTest' object has no attribute 'assertEquals'.

Bug#1054829: marked as done (php-fpdf: FTBFS: make: *** [/usr/share/quilt/quilt.make:23: unpatch] Error 1)

2024-01-14 Thread Debian Bug Tracking System
Your message dated Sun, 14 Jan 2024 22:41:04 +0100 with message-id and subject line Re: php-fpdf: FTBFS: make: *** [/usr/share/quilt/quilt.make:23: unpatch] Error 1 has caused the Debian Bug report #1054829, regarding php-fpdf: FTBFS: make: *** [/usr/share/quilt/quilt.make:23: unpatch] Error 1

Bug#1056466: marked as done (python-django-rest-hooks autopkg tests fail with Python 3.12)

2024-01-14 Thread Debian Bug Tracking System
Your message dated Sun, 14 Jan 2024 21:41:37 + with message-id and subject line Bug#1056466: fixed in python-django-rest-hooks 1.6.0-4 has caused the Debian Bug report #1056466, regarding python-django-rest-hooks autopkg tests fail with Python 3.12 to be marked as done. This means that you

Bug#1058095: marked as done (ripe-atlas-cousteau: FTBFS: AttributeError: 'TestProbeRepresentation' object has no attribute 'assertEquals'. Did you mean: 'assertEqual'?)

2024-01-14 Thread Debian Bug Tracking System
Your message dated Sun, 14 Jan 2024 20:01:11 + with message-id and subject line Bug#1058095: fixed in ripe-atlas-cousteau 2.0.0-1 has caused the Debian Bug report #1058095, regarding ripe-atlas-cousteau: FTBFS: AttributeError: 'TestProbeRepresentation' object has no attribute 'assertEquals'.

Bug#1032104: marked as done (linux: ppc64el iouring corrupted read)

2024-01-14 Thread Debian Bug Tracking System
Your message dated Sun, 14 Jan 2024 19:48:12 + with message-id and subject line Bug#1032104: fixed in linux 5.10.205-1 has caused the Debian Bug report #1032104, regarding linux: ppc64el iouring corrupted read to be marked as done. This means that you claim that the problem has been dealt

Bug#1058082: marked as done (stardicter: FTBFS: AttributeError: 'WordTest' object has no attribute 'assertEquals'. Did you mean: 'assertEqual'?)

2024-01-14 Thread Debian Bug Tracking System
Your message dated Sun, 14 Jan 2024 19:37:26 + with message-id and subject line Bug#1058082: fixed in stardicter 1.2-3 has caused the Debian Bug report #1058082, regarding stardicter: FTBFS: AttributeError: 'WordTest' object has no attribute 'assertEquals'. Did you mean: 'assertEqual'? to be

Processed: boost1.83: not have sufficient long double support issue on ppc64le

2024-01-14 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > severity 1060786 important Bug #1060786 [src:graph-tool] graph-tool: FTBFS on ppc64el: /usr/include/boost/math/tools/promotion.hpp:267:27: error: static assertion failed: Sorry, but this platform does not have sufficient long double support

Bug#1056811: marked as done (libgpuarray: ftbfs with cython 3.0.x)

2024-01-14 Thread Debian Bug Tracking System
Your message dated Sun, 14 Jan 2024 17:53:18 + with message-id and subject line Bug#1060374: Removed package(s) from unstable has caused the Debian Bug report #1056811, regarding libgpuarray: ftbfs with cython 3.0.x to be marked as done. This means that you claim that the problem has been

Bug#1031414: marked as done (libgpuarray: i386 test fail with new pocl)

2024-01-14 Thread Debian Bug Tracking System
Your message dated Sun, 14 Jan 2024 17:53:18 + with message-id and subject line Bug#1060374: Removed package(s) from unstable has caused the Debian Bug report #1031414, regarding libgpuarray: i386 test fail with new pocl to be marked as done. This means that you claim that the problem has

Bug#1055690: marked as done (libgpuarray ftbfs with Python 3.12)

2024-01-14 Thread Debian Bug Tracking System
Your message dated Sun, 14 Jan 2024 17:53:18 + with message-id and subject line Bug#1060374: Removed package(s) from unstable has caused the Debian Bug report #1055690, regarding libgpuarray ftbfs with Python 3.12 to be marked as done. This means that you claim that the problem has been

Bug#1014461: marked as done (gnome-online-miners: unmaintained)

2024-01-14 Thread Debian Bug Tracking System
Your message dated Sun, 14 Jan 2024 17:08:56 + with message-id and subject line Bug#1060396: Removed package(s) from unstable has caused the Debian Bug report #1014461, regarding gnome-online-miners: unmaintained to be marked as done. This means that you claim that the problem has been dealt

Processed: your mail

2024-01-14 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > severity 1060295 important Bug #1060295 [src:boost1.83] boost1.83: not have sufficient long double support issue on ppc64le Severity set to 'important' from 'serious' > thanks Stopping processing here. Please contact me if you need assistance.

Bug#1058127: python-mpiplus: FTBFS: AttributeError: module 'configparser' has no attribute 'SafeConfigParser'. Did you mean: 'RawConfigParser'?

2024-01-14 Thread Yogeswaran Umasankar
Hi, I created a patch for fixing AttributeError: module 'configparser' has no attribute 'SafeConfigParser'. In the process I have updated it to the latest upstream too. I’ve attached the debdiff for you to check out. Cheers! diff -Nru python-mpiplus-0.0.1/debian/changelog

Processed: boost1.83: not have sufficient long double support issue on ppc64le

2024-01-14 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > block 1060786 by 1060295 Bug #1060786 [src:graph-tool] graph-tool: FTBFS on ppc64el: /usr/include/boost/math/tools/promotion.hpp:267:27: error: static assertion failed: Sorry, but this platform does not have sufficient long double support for

Processed: found 1056243 in 2.0-3

2024-01-14 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > found 1056243 2.0-3 Bug #1056243 [src:django-assets] django-assets autopkg tests fail with Python 3.12 The source 'django-assets' and version '2.0-3' do not appear to match any binary packages Marked as found in versions django-assets/2.0-3. >

Bug#1055718: marked as done (python-openstep-plist ftbfs with Python 3.12)

2024-01-14 Thread Debian Bug Tracking System
Your message dated Sun, 14 Jan 2024 12:02:26 -0400 with message-id and subject line Re: Bug#1055718: python-openstep-plist ftbfs with Python 3.12 has caused the Debian Bug report #1055718, regarding python-openstep-plist ftbfs with Python 3.12 to be marked as done. This means that you claim

Bug#1056440: marked as done (pyopengl's autopkg tests fail with Python 3.12)

2024-01-14 Thread Debian Bug Tracking System
Your message dated Sun, 14 Jan 2024 15:51:39 + with message-id and subject line Bug#1056440: fixed in pyopengl 3.1.7+dfsg-1 has caused the Debian Bug report #1056440, regarding pyopengl's autopkg tests fail with Python 3.12 to be marked as done. This means that you claim that the problem has

Bug#1058308: marked as done (pyopengl: FTBFS: dh_auto_test: error: pybuild --test --test-pytest -i python{version} -p "3.12 3.11" returned exit code 13)

2024-01-14 Thread Debian Bug Tracking System
Your message dated Sun, 14 Jan 2024 15:51:39 + with message-id and subject line Bug#1058308: fixed in pyopengl 3.1.7+dfsg-1 has caused the Debian Bug report #1058308, regarding pyopengl: FTBFS: dh_auto_test: error: pybuild --test --test-pytest -i python{version} -p "3.12 3.11" returned exit

Processed: severity of 952735 is serious

2024-01-14 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > severity 952735 serious Bug #952735 [gnupg-pkcs11-scd] gnupg-pkcs11-scd: when used as scdaemon, `gnupg --card-status` reports wrong informations Severity set to 'serious' from 'normal' > thanks Stopping processing here. Please contact me if you

Processed: Bug#1055570 marked as pending in lazy-object-proxy

2024-01-14 Thread Debian Bug Tracking System
Processing control commands: > tag -1 pending Bug #1055570 [src:lazy-object-proxy] lazy-object-proxy fails tests with Python 3.12 Added tag(s) pending. -- 1055570: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1055570 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems

Bug#1055570: marked as pending in lazy-object-proxy

2024-01-14 Thread Stefano Rivera
Control: tag -1 pending Hello, Bug #1055570 in lazy-object-proxy 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:

Processed: boost1.83: not have sufficient long double support issue on ppc64le

2024-01-14 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > affects 1060295 + graph-tool Bug #1060295 [src:boost1.83] boost1.83: not have sufficient long double support issue on ppc64le Added indication that 1060295 affects graph-tool > thanks Stopping processing here. Please contact me if you need

Processed (with 2 errors): boost1.83: not have sufficient long double support issue on ppc64le

2024-01-14 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > severity 1060295 serious Bug #1060295 [src:boost1.83] boost1.83: not have sufficient long double support issue on ppc64le Severity set to 'serious' from 'important' > merge 1060295 1060786 Bug #1060295 [src:boost1.83] boost1.83: not have

Bug#1060804: hickle: failing tests with h5py 3.10

2024-01-14 Thread Drew Parsons
Source: hickle Version: 5.0.2-7 Severity: serious Justification: debci h5py 3.10 is triggering test failure in hickle 54s test_H5NodeFilterProxy 54s 54s h5_data = 54s 54s def test_H5NodeFilterProxy(h5_data): 54s """

Bug#1055568: marked as pending in m2crypto

2024-01-14 Thread Stefano Rivera
Control: tag -1 pending Hello, Bug #1055568 in m2crypto 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:

Processed: Bug#1055568 marked as pending in m2crypto

2024-01-14 Thread Debian Bug Tracking System
Processing control commands: > tag -1 pending Bug #1055568 [src:m2crypto] m2crypto ftbfs with Python 3.12 Added tag(s) pending. -- 1055568: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1055568 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems

Bug#1060802: stellarium: FTBFS on armel, ppc64el, s390x: unsatisfiable Build-Depends: qtwebengine5-dev (>= 5.15)

2024-01-14 Thread Dmitry Shachnev
Source: stellarium Version: 23.4-1 Severity: serious Justification: fails to build from source (but built successfully in the past) Tags: ftbfs Dear Maintainer, stellarium 23.4-1 added a new build-dependency on qtwebengine5-dev, which prevents it from building on some release architectures (and

Bug#1058420: marked as done (pydocstyle: FTBFS: dh_auto_test: error: pybuild --test --test-pytest -i python{version} -p "3.12 3.11" returned exit code 13)

2024-01-14 Thread Debian Bug Tracking System
Your message dated Sun, 14 Jan 2024 13:35:00 + with message-id and subject line Bug#1058420: fixed in pydocstyle 6.3.0-1.1 has caused the Debian Bug report #1058420, regarding pydocstyle: FTBFS: dh_auto_test: error: pybuild --test --test-pytest -i python{version} -p "3.12 3.11" returned exit

Bug#1056437: marked as done (pydocstyle's autopkg tests fail with Python 3.12)

2024-01-14 Thread Debian Bug Tracking System
Your message dated Sun, 14 Jan 2024 13:35:00 + with message-id and subject line Bug#1056437: fixed in pydocstyle 6.3.0-1.1 has caused the Debian Bug report #1056437, regarding pydocstyle's autopkg tests fail with Python 3.12 to be marked as done. This means that you claim that the problem

Bug#1060698: [Pkg-auth-maintainers] Bug#1060698: yubioath-desktop: Doesn't see yubikeys anymore.

2024-01-14 Thread Sébastien Noel
Hi Florian, Le 2024-01-14 13:51, Florian Schlichting a écrit : Hi Sébastien, thank you for the patch. I'm not opposed to applying it. In my superficial testing, it seems to work well. I'm not a user of yubioath-desktop, though, and while I can help with an occasional upload, I don't want to

Bug#1060773: Filed an upload request to release team

2024-01-14 Thread Daniel Markstedt
I prepared a deb patch and filed this upload request with the release team: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1060774

Processed: Bug#1056437 marked as pending in pydocstyle

2024-01-14 Thread Debian Bug Tracking System
Processing control commands: > tag -1 pending Bug #1056437 [src:pydocstyle] pydocstyle's autopkg tests fail with Python 3.12 Added tag(s) pending. -- 1056437: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1056437 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems

Processed: Bug#1058420 marked as pending in pydocstyle

2024-01-14 Thread Debian Bug Tracking System
Processing control commands: > tag -1 pending Bug #1058420 [src:pydocstyle] pydocstyle: FTBFS: dh_auto_test: error: pybuild --test --test-pytest -i python{version} -p "3.12 3.11" returned exit code 13 Added tag(s) pending. -- 1058420: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1058420

Bug#1056437: marked as pending in pydocstyle

2024-01-14 Thread Matthias Klose
Control: tag -1 pending Hello, Bug #1056437 in pydocstyle 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:

Bug#1058420: marked as pending in pydocstyle

2024-01-14 Thread Matthias Klose
Control: tag -1 pending Hello, Bug #1058420 in pydocstyle 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:

Bug#1060458: uploaded release 804.036+dfsg1-2

2024-01-14 Thread gregor herrmann
On Sun, 14 Jan 2024 10:10:03 +0100, Georges Khaznadar wrote: > Hi, > I just uploaded a new release, with your changes included. Great, thanks alot! Cheers, gregor -- .''`. https://info.comodo.priv.at -- Debian Developer https://www.debian.org : :' : OpenPGP fingerprint D1E1 316E 93A7 60A8

Bug#1060698: [Pkg-auth-maintainers] Bug#1060698: yubioath-desktop: Doesn't see yubikeys anymore.

2024-01-14 Thread Florian Schlichting
Hi Sébastien, On Sat, Jan 13, 2024 at 01:34:44PM +0100, Sébastien Noel wrote: > On Sat, 13 Jan 2024 11:26:50 +0100 Florian Schlichting > wrote: > > > > [...] > > While it might be possible to patch py/yubikey.py to work with the > > interface changes in current python3-ykman, I doubt this is a >

Bug#1060101: Boost 1.81 removal

2024-01-14 Thread Dirk Eddelbuettel
FYI two days before you filed #1060101 I actually happened to have updated r-cran-bh to 1.84.0 (upstream, which is me, went to the 1.84.0 version released in December as Boost releases every four months) using 1.83: r-cran-bh (1.84.0-1) unstable; urgency=medium * debian/control: Update

Bug#1060707: dh-make-elpa: autopkgtest failure with Perl 5.38: smartmatch is deprecated

2024-01-14 Thread gregor herrmann
On Sun, 14 Jan 2024 10:41:08 +0500, Lev Lamberov wrote: > > In case you have troubles finding someone from the team to upload, > > please shout, I'm happy to help. > I've just looked into the bug report and commited changes, and uploaded > the updated package. Great, thanks to both of you!

Bug#1058417: marked as done (pytest-mock: FTBFS: dh_auto_test: error: pybuild --test --test-pytest -i python{version} -p "3.12 3.11" returned exit code 13)

2024-01-14 Thread Debian Bug Tracking System
Your message dated Sun, 14 Jan 2024 12:19:18 + with message-id and subject line Bug#1058417: fixed in pytest-mock 3.12.0-1.1 has caused the Debian Bug report #1058417, regarding pytest-mock: FTBFS: dh_auto_test: error: pybuild --test --test-pytest -i python{version} -p "3.12 3.11" returned

Bug#1060432: closing 1060432

2024-01-14 Thread Roland Mas
close 1060432 thanks rust-archery and rust-rpds (and rust-triomphe, a third dependency in the chain) are now part of unstable.

Processed: closing 1060432

2024-01-14 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > close 1060432 Bug #1060432 [src:rpds-py] rpds-py ftbfs in unstable Marked Bug as done > thanks Stopping processing here. Please contact me if you need assistance. -- 1060432: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1060432 Debian Bug

Processed: Bug#1058417 marked as pending in pytest-mock

2024-01-14 Thread Debian Bug Tracking System
Processing control commands: > tag -1 pending Bug #1058417 [src:pytest-mock] pytest-mock: FTBFS: dh_auto_test: error: pybuild --test --test-pytest -i python{version} -p "3.12 3.11" returned exit code 13 Added tag(s) pending. -- 1058417: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1058417

Bug#1058417: marked as pending in pytest-mock

2024-01-14 Thread Matthias Klose
Control: tag -1 pending Hello, Bug #1058417 in pytest-mock 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:

Bug#1060790: marked as done (filezilla: switch to default version of boost)

2024-01-14 Thread Debian Bug Tracking System
Your message dated Sun, 14 Jan 2024 11:19:13 + with message-id and subject line Bug#1060790: fixed in filezilla 3.66.4-2 has caused the Debian Bug report #1060790, regarding filezilla: switch to default version of boost to be marked as done. This means that you claim that the problem has

Bug#1060790: filezilla: switch to default version of boost

2024-01-14 Thread Phil Wyett
Hi, Fixed and this bug closed with uploaded package: filezilla (3.66.4-2). Regards Phil -- Playing the game for the games sake. Web: * Debian Wiki: https://wiki.debian.org/PhilWyett * Website: https://kathenas.org * Social Debian: https://pleroma.debian.social/kathenas/ * Social Instagram:

Bug#1060154: marked as done (turing: does not start at all)

2024-01-14 Thread Debian Bug Tracking System
Your message dated Sun, 14 Jan 2024 10:50:29 + with message-id and subject line Bug#1060154: fixed in turing 0.11~beta-5 has caused the Debian Bug report #1060154, regarding turing: does not start at all to be marked as done. This means that you claim that the problem has been dealt with. If

Bug#1060794: ccdproc fails tests, missing dependency

2024-01-14 Thread Matthias Klose
Package: src:ccdproc Version: 2.4.1-1 Severity: serious Tags: sid trixie ccdproc fails the autopkg tests, missing dependency. Note, that I also commented out the dependency on python3-memory-profiler, because it's RC buggy without a patch. please see

Processed: blocking 1056529 1058408 by 1058371

2024-01-14 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > block 1056529 by 1058371 Bug #1056529 [src:sphinx-autoapi] sphinx-autoapi's autopkg tests fail with Python 3.12 1056529 was not blocked by any bugs. 1056529 was not blocking any bugs. Added blocking bug(s) of 1056529: 1058371 > block 1058408 by

Processed (with 1 error): Re: Bug#1058371: python-cloup: FTBFS: make[1]: *** [Makefile:20: html] Error 2

2024-01-14 Thread Debian Bug Tracking System
Processing control commands: > reassign -1 python3-astroid 2.15.6-1 Bug #1058371 [python3-sphinx-autoapi] python3-sphinx-autoapi: incompatible with Python 3.12 (exception: 'TreeRebuilder' object has no attribute 'visit_typealias') Bug reassigned from package 'python3-sphinx-autoapi' to

Bug#1058371: python-cloup: FTBFS: make[1]: *** [Makefile:20: html] Error 2

2024-01-14 Thread Dmitry Shachnev
Control: reassign -1 python3-astroid 2.15.6-1 Control: retitle -1 python3-astroid: incompatible with Python 3.12 (exception: 'TreeRebuilder' object has no attribute 'visit_typealias') Control: affects -1 + src:python-cloup src:sphinx-autoapi Control: block 1056529 1058408 by -1 Control: tags -1 +

Bug#1060104: dcmtk: FTBFS on armel: Error: bad immediate value for offset (4100)

2024-01-14 Thread Mathieu Malaterre
Control: fixed -1 3.6.8-3 On Sat, Jan 13, 2024 at 9:42 PM Emanuele Rocca wrote: > > Control: user -1 debian-...@lists.debian.org > Control: usertag -1 + 32bit-stackclash > > Hi, > > On Fri, Jan 05, 2024 at 11:45:28PM +0100, Sebastian Ramacher wrote: > > /tmp/ccm0eYhx.s: Assembler messages: > >

Processed: Re: Bug#1060104: dcmtk: FTBFS on armel: Error: bad immediate value for offset (4100)

2024-01-14 Thread Debian Bug Tracking System
Processing control commands: > fixed -1 3.6.8-3 Bug #1060104 [src:dcmtk] dcmtk: FTBFS on armel: Error: bad immediate value for offset (4100) Marked as fixed in versions dcmtk/3.6.8-3. -- 1060104: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1060104 Debian Bug Tracking System Contact

Bug#1060792: r-cran-openmx: switch to default version of boost

2024-01-14 Thread Sebastian Ramacher
Source: r-cran-openmx Version: 2.21.11+dfsg-1 Severity: serious X-Debbugs-Cc: sramac...@debian.org boost1.81 is scheduled for removal. Please switch the (Build-)Depends of r-cran-openmx to point to boost1.83 or -- preferably -- to the unversioned boost -dev packages. The latter helps with future

Bug#1060790: filezilla: switch to default version of boost

2024-01-14 Thread Sebastian Ramacher
Source: filezilla Version: 3.66.4-1 Severity: serious X-Debbugs-Cc: sramac...@debian.org boost1.81 is scheduled for removal. Please either update the (Build-)Depends for boost1.83 or switch them to the default boost version. If possible, the latter is preferred for future boost transitions.

Bug#1060791: pbcopper: switch to default version of boost

2024-01-14 Thread Sebastian Ramacher
Source: pbcopper Version: 2.2.0+dfsg-1 Severity: serious X-Debbugs-Cc: sramac...@debian.org boost1.81 is scheduled for removal. Please switch the (Build-)Depends of pbcopper to use boost1.83 or the unversioned boost packages. If possible, the latter is preferred for future boost transitions.

Bug#1060789: strace FTBFS with linux-libc-dev >= 6.6

2024-01-14 Thread Adrian Bunk
Source: strace Version: 6.5-0.1 Severity: serious Tags: ftbfs https://buildd.debian.org/status/fetch.php?pkg=strace=riscv64=6.5-0.1%2Bb1=1705203098=0 https://tests.reproducible-builds.org/debian/rb-pkg/unstable/arm64/strace.html ... In file included from ../../src/btrfs.c:51:

Bug#1060788: pycuda: requires rebuild for boost 1.83 transition

2024-01-14 Thread Sebastian Ramacher
Source: pycuda Version: 2023.1~dfsg-1 Severity: serious X-Debbugs-Cc: sramac...@debian.org pycuda is involved in the boost transition, but cannot be built on the buildds. Please rebuild with boost 1.83 as default and upload new binaries. Cheers -- Sebastian Ramacher

Bug#1060787: i2pd: FTBFS on armel: Host compiler appears to require libatomic for 64-bit operations, but cannot find it.

2024-01-14 Thread Sebastian Ramacher
Source: i2pd Version: 2.49.0-1 Severity: serious Tags: ftbfs Justification: fails to build from source (but built successfully in the past) X-Debbugs-Cc: sramac...@debian.org https://buildd.debian.org/status/fetch.php?pkg=i2pd=armel=2.49.0-1=1704531194=0 dh_auto_configure --buildsystem=cmake

Bug#1060786: graph-tool: FTBFS on ppc64el: /usr/include/boost/math/tools/promotion.hpp:267:27: error: static assertion failed: Sorry, but this platform does not have sufficient long double support for

2024-01-14 Thread Sebastian Ramacher
Source: graph-tool Version: 2.59+ds-1 Severity: serious Tags: ftbfs Justification: fails to build from source (but built successfully in the past) X-Debbugs-Cc: sramac...@debian.org https://buildd.debian.org/status/fetch.php?pkg=graph-tool=ppc64el=2.59%2Bds-1=1704656087=0 libtool: compile: g++

Bug#1060458: marked as done (perl-tk: FTBFS with Perl 5.38 on big-endian 64-bit: test failures)

2024-01-14 Thread Debian Bug Tracking System
Your message dated Sun, 14 Jan 2024 09:21:27 + with message-id and subject line Bug#1060458: fixed in perl-tk 1:804.036+dfsg1-2 has caused the Debian Bug report #1060458, regarding perl-tk: FTBFS with Perl 5.38 on big-endian 64-bit: test failures to be marked as done. This means that you

Bug#1060458: uploaded release 804.036+dfsg1-2

2024-01-14 Thread Georges Khaznadar
Hi, I just uploaded a new release, with your changes included. Best regards, Georges. -- Georges KHAZNADAR et Jocelyne FOURNIER 22 rue des mouettes, 59240 Dunkerque France. Téléphone +33 (0)3 28 29 17 70 signature.asc Description: PGP signature

Bug#1056449: marked as done (pytest-localserver's autopkg tests fail with Python 3.12)

2024-01-14 Thread Debian Bug Tracking System
Your message dated Sun, 14 Jan 2024 08:41:33 + with message-id and subject line Bug#1056449: fixed in pytest-localserver 0.8.1-1 has caused the Debian Bug report #1056449, regarding pytest-localserver's autopkg tests fail with Python 3.12 to be marked as done. This means that you claim that

Bug#1058352: marked as done (pytest-localserver: FTBFS: dh_auto_test: error: pybuild --test --test-pytest -i python{version} -p "3.12 3.11" returned exit code 13)

2024-01-14 Thread Debian Bug Tracking System
Your message dated Sun, 14 Jan 2024 08:41:33 + with message-id and subject line Bug#1058352: fixed in pytest-localserver 0.8.1-1 has caused the Debian Bug report #1058352, regarding pytest-localserver: FTBFS: dh_auto_test: error: pybuild --test --test-pytest -i python{version} -p "3.12 3.11"

Bug#1060783: src:rasdaemon: fails to migrate to testing for too long: autopkgtest failure

2024-01-14 Thread Paul Gevers
Source: rasdaemon Version: 0.6.8-1.1 Severity: serious Control: close -1 0.8.0-1 Tags: sid trixie User: release.debian@packages.debian.org Usertags: out-of-sync Control: block -1 by 1059484 Dear maintainer(s), The Release Team considers packages that are out-of-sync between testing and

Processed: src:rasdaemon: fails to migrate to testing for too long: autopkgtest failure

2024-01-14 Thread Debian Bug Tracking System
Processing control commands: > close -1 0.8.0-1 Bug #1060783 [src:rasdaemon] src:rasdaemon: fails to migrate to testing for too long: autopkgtest failure Marked as fixed in versions rasdaemon/0.8.0-1. Bug #1060783 [src:rasdaemon] src:rasdaemon: fails to migrate to testing for too long:

Processed: Bug#1056449 marked as pending in pytest-localserver

2024-01-14 Thread Debian Bug Tracking System
Processing control commands: > tag -1 pending Bug #1056449 [src:pytest-localserver] pytest-localserver's autopkg tests fail with Python 3.12 Added tag(s) pending. -- 1056449: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1056449 Debian Bug Tracking System Contact ow...@bugs.debian.org with

Bug#1056449: marked as pending in pytest-localserver

2024-01-14 Thread Matthias Klose
Control: tag -1 pending Hello, Bug #1056449 in pytest-localserver 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: