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

2024-01-15 Thread Debian Bug Tracking System
Your message dated Tue, 16 Jan 2024 07:35:06 + with message-id and subject line Bug#1058127: fixed in python-mpiplus 0.0.2+ds-1 has caused the Debian Bug report #1058127, regarding python-mpiplus: FTBFS: AttributeError: module 'configparser' has no attribute 'SafeConfigParser'. Did you mean:

Bug#1055568: marked as done (m2crypto ftbfs with Python 3.12)

2024-01-15 Thread Debian Bug Tracking System
Your message dated Tue, 16 Jan 2024 07:04:39 + with message-id and subject line Bug#1055568: fixed in m2crypto 0.40.1-1 has caused the Debian Bug report #1055568, regarding m2crypto ftbfs with Python 3.12 to be marked as done. This means that you claim that the problem has been dealt with.

Bug#1055570: marked as done (lazy-object-proxy fails tests with Python 3.12)

2024-01-15 Thread Debian Bug Tracking System
Your message dated Tue, 16 Jan 2024 06:34:00 + with message-id and subject line Bug#1055570: fixed in lazy-object-proxy 1.10.0-1 has caused the Debian Bug report #1055570, regarding lazy-object-proxy fails tests with Python 3.12 to be marked as done. This means that you claim that the

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

2024-01-15 Thread Debian Bug Tracking System
Your message dated Tue, 16 Jan 2024 06:34:00 + with message-id and subject line Bug#1058384: fixed in lazy-object-proxy 1.10.0-1 has caused the Debian Bug report #1058384, regarding lazy-object-proxy: FTBFS: dh_auto_test: error: pybuild --test --test-pytest -i python{version} -p "3.12 3.11"

Bug#1059701: marked as done (sccache - upcoming rust-object update)

2024-01-15 Thread Debian Bug Tracking System
Your message dated Tue, 16 Jan 2024 06:05:05 + with message-id and subject line Bug#1059701: fixed in sccache 0.7.5-1 has caused the Debian Bug report #1059701, regarding sccache - upcoming rust-object update to be marked as done. This means that you claim that the problem has been dealt

Bug#1057484: pelican: "ModuleNotFoundError: No module named 'watchfiles"

2024-01-15 Thread Louis-Philippe Véronneau
It seems this library isn't currently packaged in Debian? I've just ITPed the package and will be uploading it to NEW ASAP. -- ⢀⣴⠾⠻⢶⣦⠀ ⣾⠁⢠⠒⠀⣿⡁ Louis-Philippe Véronneau ⢿⡄⠘⠷⠚⠋ po...@debian.org / veronneau.org ⠈⠳⣄ OpenPGP_0xE1E5457C8BAD4113.asc Description: OpenPGP public key

Processed: Bug#1060709 marked as pending in dh-runit

2024-01-15 Thread Debian Bug Tracking System
Processing control commands: > tag -1 pending Bug #1060709 [dh-runit] dh-runit: autopkgtest failure with Perl 5.38: given is deprecated Ignoring request to alter tags of bug #1060709 to the same tags previously set -- 1060709: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1060709 Debian

Bug#1060709: marked as pending in dh-runit

2024-01-15 Thread Lorenzo Puliti
Control: tag -1 pending Hello, Bug #1060709 in dh-runit 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#1060709 marked as pending in dh-runit

2024-01-15 Thread Debian Bug Tracking System
Processing control commands: > tag -1 pending Bug #1060709 [dh-runit] dh-runit: autopkgtest failure with Perl 5.38: given is deprecated Added tag(s) pending. -- 1060709: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1060709 Debian Bug Tracking System Contact ow...@bugs.debian.org with

Bug#1060709: marked as pending in dh-runit

2024-01-15 Thread Lorenzo Puliti
Control: tag -1 pending Hello, Bug #1060709 in dh-runit 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#1058127: python-mpiplus: FTBFS: AttributeError: module 'configparser' has no attribute 'SafeConfigParser'. Did you mean: 'RawConfigParser'?

2024-01-15 Thread Yogeswaran Umasankar
Hi Andrius, I have removed the hard-coded version number from setup.py. I found that the issue was due to changes in PEP440 version naming convention in versioneer. For this package no need python3-versioneer, upstream has its own versioneer.py. The work around is, once have everything in master

Processed (with 1 error): 1057573

2024-01-15 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > tags 1057573 + pending patch Bug #1057573 [src:linpac] linpac: FTBFS: error: invalid use of incomplete type ‘WINDOW’ {aka ‘struct _win_st’} Added tag(s) pending. > kthxbai Unknown command or malformed arguments to command. > End of message,

Bug#1055545: marked as done (zfec ftbfs with Python 3.12)

2024-01-15 Thread Debian Bug Tracking System
Your message dated Tue, 16 Jan 2024 00:07:28 + with message-id and subject line Bug#1055545: fixed in zfec 1.5.7.4-0.1 has caused the Debian Bug report #1055545, regarding zfec ftbfs with Python 3.12 to be marked as done. This means that you claim that the problem has been dealt with. If

Bug#1031874: marked as done (upx-ucl: CVE-2023-23457)

2024-01-15 Thread Debian Bug Tracking System
Your message dated Tue, 16 Jan 2024 00:32:14 +0100 with message-id and subject line Re: Bug#1033258: Bug#1031874: upx-ucl: CVE-2023-23457 has caused the Debian Bug report #1031874, regarding upx-ucl: CVE-2023-23457 to be marked as done. This means that you claim that the problem has been dealt

Bug#1056494: marked as done (python-py's autopkg tests fail with Python 3.12)

2024-01-15 Thread Debian Bug Tracking System
Your message dated Mon, 15 Jan 2024 21:07:15 + with message-id and subject line Bug#1056494: fixed in python-py 1.11.0-2 has caused the Debian Bug report #1056494, regarding python-py's autopkg tests fail with Python 3.12 to be marked as done. This means that you claim that the problem has

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

2024-01-15 Thread Debian Bug Tracking System
Your message dated Mon, 15 Jan 2024 20:40:22 + with message-id and subject line Bug#1054729: fixed in errbot 6.2.0+ds-1 has caused the Debian Bug report #1054729, regarding errbot: FTBFS: dh_auto_test: error: pybuild --test --test-pytest -i python{version} -p 3.11 returned exit code 13 to be

Processed: Re: python-molotov's autopkg tests fail with Python 3.12

2024-01-15 Thread Debian Bug Tracking System
Processing control commands: > tags -1 upstream Bug #1056484 [src:python-molotov] python-molotov's autopkg tests fail with Python 3.12 Added tag(s) upstream. > forwarded -1 https://github.com/tarekziade/molotov/issues/164 Bug #1056484 [src:python-molotov] python-molotov's autopkg tests fail with

Bug#1056484: python-molotov's autopkg tests fail with Python 3.12

2024-01-15 Thread Andreas Tille
Control: tags -1 upstream Control: forwarded -1 https://github.com/tarekziade/molotov/issues/164 -- http://fam-tille.de

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

2024-01-15 Thread Debian Bug Tracking System
Your message dated Mon, 15 Jan 2024 19:21:13 + with message-id and subject line Bug#1058385: fixed in python-lti 0.9.5-3 has caused the Debian Bug report #1058385, regarding python-lti: FTBFS: dh_auto_test: error: pybuild --test --test-pytest -i python{version} -p "3.12 3.11" returned exit

Bug#1056479: marked as done (python-lti's autopkg tests fail with Python 3.12)

2024-01-15 Thread Debian Bug Tracking System
Your message dated Mon, 15 Jan 2024 19:21:13 + with message-id and subject line Bug#1056479: fixed in python-lti 0.9.5-3 has caused the Debian Bug report #1056479, regarding python-lti's autopkg tests fail with Python 3.12 to be marked as done. This means that you claim that the problem has

Bug#1056477: marked as done (python-languagecodes autopkg tests fail with Python 3.12)

2024-01-15 Thread Debian Bug Tracking System
Your message dated Mon, 15 Jan 2024 18:07:26 + with message-id and subject line Bug#1056477: fixed in python-languagecodes 1.1.1-3 has caused the Debian Bug report #1056477, regarding python-languagecodes autopkg tests fail with Python 3.12 to be marked as done. This means that you claim

Bug#1058257: marked as done (python-persist-queue: FTBFS: AttributeError: 'SQLite3QueueTest' object has no attribute 'assertEquals'. Did you mean: 'assertEqual'?)

2024-01-15 Thread Debian Bug Tracking System
Your message dated Mon, 15 Jan 2024 17:20:01 + with message-id and subject line Bug#1058257: fixed in python-persist-queue 0.5.1-2 has caused the Debian Bug report #1058257, regarding python-persist-queue: FTBFS: AttributeError: 'SQLite3QueueTest' object has no attribute 'assertEquals'. Did

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

2024-01-15 Thread Debian Bug Tracking System
Your message dated Mon, 15 Jan 2024 17:05:24 + with message-id and subject line Bug#1058228: fixed in python-hglib 2.6.2-2 has caused the Debian Bug report #1058228, regarding python-hglib: FTBFS: AttributeError: 'test_update' object has no attribute 'assertEquals'. Did you mean:

Bug#1060850: jtdx: FTBFS on armel: Error: bad immediate value for offset (4096)

2024-01-15 Thread Emanuele Rocca
Source: jtdx Version: 2.2.159-1 Severity: serious Tags: ftbfs, patch User: debian-...@lists.debian.org Usertags: 32bit-stackclash Dear Maintainer, jtdx currently fails to build from source on armel. To address the immediate issue, please disable stack-clash-protection with the following snippet

Bug#1060779: src:mesa: fails to migrate to testing for too long: unavailable Build-Depends on mips64el

2024-01-15 Thread Simon McVittie
On Sun, 14 Jan 2024 at 08:39:52 +0100, Paul Gevers wrote: > The Release Team considers packages that are out-of-sync between testing and > unstable for more than 30 days as having a Release Critical bug in testing > [1]. Your package src:mesa has been trying to migrate for 31 days [2]. > Hence, I

Bug#1058231: marked as done (python-testing.postgresql: FTBFS: AttributeError: 'TestPostgresql' object has no attribute 'assertRegexpMatches')

2024-01-15 Thread Debian Bug Tracking System
Your message dated Mon, 15 Jan 2024 16:19:01 + with message-id and subject line Bug#1058231: fixed in python-testing.postgresql 1.3.0-5 has caused the Debian Bug report #1058231, regarding python-testing.postgresql: FTBFS: AttributeError: 'TestPostgresql' object has no attribute

Processed: mesa: FTBFS on armel: static assertion failed: "vn_ring_shared requires lock-free 32-bit atomic_uint"

2024-01-15 Thread Debian Bug Tracking System
Processing control commands: > block 1060779 by -1 Bug #1060779 {Done: Paul Gevers } [src:mesa] src:mesa: fails to migrate to testing for too long: unavailable Build-Depends on mips64el 1060779 was blocked by: 1056116 1060779 was not blocking any bugs. Added blocking bug(s) of 1060779: 1060849

Bug#1060849: mesa: FTBFS on armel: static assertion failed: "vn_ring_shared requires lock-free 32-bit atomic_uint"

2024-01-15 Thread Simon McVittie
Source: mesa Version: 23.3.3-1 Severity: serious Tags: ftbfs Justification: fails to build from source (but built successfully in the past) X-Debbugs-Cc: debian-...@lists.debian.org User: debian-...@lists.debian.org Usertags: armel Control: block 1060779 by -1 The armel baseline does not have

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

2024-01-15 Thread Andrius Merkys
Hi Yogeswaran, On 2024-01-14 18:46, Yogeswaran Umasankar wrote: 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. I noticed you

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

2024-01-15 Thread Debian Bug Tracking System
Your message dated Mon, 15 Jan 2024 15:49:01 + with message-id and subject line Bug#1054974: fixed in behave 1.2.6-5 has caused the Debian Bug report #1054974, regarding behave: FTBFS: dh_auto_test: error: pybuild --test --test-pytest -i python{version} -p 3.11 returned exit code 13 to be

Bug#1060848: rust-isahc: Autopkgtest failures

2024-01-15 Thread Matthias Geiger
Source: rust-isahc Version: 1.7.2+ds-24 Severity: serious Justification: fails to migrate to testing X-Debbugs-Cc: werdah...@riseup.net -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 See https://ci.debian.net/data/autopkgtest/testing/amd64/r/rust-isahc/40410753/log.gz. snip:

Bug#1042610: marked as done (behave: FTBFS with Sphinx 7.1, docutils 0.20: TypeError: not all arguments converted during string formatting)

2024-01-15 Thread Debian Bug Tracking System
Your message dated Mon, 15 Jan 2024 15:49:01 + with message-id and subject line Bug#1042610: fixed in behave 1.2.6-5 has caused the Debian Bug report #1042610, regarding behave: FTBFS with Sphinx 7.1, docutils 0.20: TypeError: not all arguments converted during string formatting to be marked

Bug#1054974: behave: FTBFS: dh_auto_test: error: pybuild --test --test-pytest -i python{version} -p 3.11 returned exit code 13

2024-01-15 Thread Andrius Merkys
Hi, On 2024-01-15 17:34, Christoph Berg wrote: Re: Andrius Merkys The patch proposed in #1042610 does not fix test failure. Interestingly, the failure seems to be nondeterministic: after patching #1042610 some builds succeed. However, I did not manage to find the root cause. The difference

Bug#1054974: behave: FTBFS: dh_auto_test: error: pybuild --test --test-pytest -i python{version} -p 3.11 returned exit code 13

2024-01-15 Thread Christoph Berg
Re: Andrius Merkys > The patch proposed in #1042610 does not fix test failure. Interestingly, the > failure seems to be nondeterministic: after patching #1042610 some builds > succeed. However, I did not manage to find the root cause. The difference between a working and a failing run is this

Processed: Bug#1054974 marked as pending in behave

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

Bug#1054974: marked as pending in behave

2024-01-15 Thread Christoph Berg
Control: tag -1 pending Hello, Bug #1054974 in behave 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#1055515: ldc: diff for NMU version 1:1.35.0-1.1

2024-01-15 Thread Gianfranco Costamagna
Control: tags 1055515 + patch Control: tags 1055515 + pending Dear maintainer, I've prepared an NMU for ldc (versioned as 1:1.35.0-1.1) and uploaded it to DELAYED/15. Please feel free to delete it from queue if you think it isn't useful. Regards. Gianfranco diff -Nru

Processed: ldc: diff for NMU version 1:1.35.0-1.1

2024-01-15 Thread Debian Bug Tracking System
Processing control commands: > tags 1055515 + patch Bug #1055515 [ldc] ldc: diff for NMU version 1:1.35.0-1.1 Ignoring request to alter tags of bug #1055515 to the same tags previously set > tags 1055515 + pending Bug #1055515 [ldc] ldc: diff for NMU version 1:1.35.0-1.1 Added tag(s) pending. --

Bug#1058217: marked as done (python-smoke-zephyr: FTBFS: AttributeError: 'UtilitiesTests' object has no attribute 'assertEquals'. Did you mean: 'assertEqual'?)

2024-01-15 Thread Debian Bug Tracking System
Your message dated Mon, 15 Jan 2024 15:19:52 + with message-id and subject line Bug#1058217: fixed in python-smoke-zephyr 2.0.1-3 has caused the Debian Bug report #1058217, regarding python-smoke-zephyr: FTBFS: AttributeError: 'UtilitiesTests' object has no attribute 'assertEquals'. Did you

Bug#1060660: marked as done (newt: does not trap errors from python extension build (policy 4.6))

2024-01-15 Thread Debian Bug Tracking System
Your message dated Mon, 15 Jan 2024 14:35:12 + with message-id and subject line Bug#1060660: fixed in newt 0.52.24-2 has caused the Debian Bug report #1060660, regarding newt: does not trap errors from python extension build (policy 4.6) to be marked as done. This means that you claim that

Bug#1058205: marked as done (django-markupfield: FTBFS: AttributeError: 'MarkupFieldFormSaveTests' object has no attribute 'assertEquals'. Did you mean: 'assertEqual'?)

2024-01-15 Thread Debian Bug Tracking System
Your message dated Mon, 15 Jan 2024 14:34:36 + with message-id and subject line Bug#1058205: fixed in django-markupfield 2.0.1-2 has caused the Debian Bug report #1058205, regarding django-markupfield: FTBFS: AttributeError: 'MarkupFieldFormSaveTests' object has no attribute 'assertEquals'.

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

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

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

2024-01-15 Thread Debian Bug Tracking System
Your message dated Mon, 15 Jan 2024 14:35:21 + with message-id and subject line Bug#1056431: fixed in numpydoc 1.6.0-1 has caused the Debian Bug report #1056431, regarding numpydoc's autopkg tests fail with Python 3.12 to be marked as done. This means that you claim that the problem has been

Processed: Bug#1042610 marked as pending in behave

2024-01-15 Thread Debian Bug Tracking System
Processing control commands: > tag -1 pending Bug #1042610 [src:behave] behave: FTBFS with Sphinx 7.1, docutils 0.20: TypeError: not all arguments converted during string formatting Added tag(s) pending. -- 1042610: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1042610 Debian Bug Tracking

Bug#1042610: marked as pending in behave

2024-01-15 Thread Christoph Berg
Control: tag -1 pending Hello, Bug #1042610 in behave 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#1058147: marked as done (ipython-genutils: FTBFS: AttributeError: module 'nose.tools' has no attribute 'assert_equals'. Did you mean: 'assert_equal'?)

2024-01-15 Thread Debian Bug Tracking System
Your message dated Mon, 15 Jan 2024 13:34:03 + with message-id and subject line Bug#1058147: fixed in ipython-genutils 0.2.0-6 has caused the Debian Bug report #1058147, regarding ipython-genutils: FTBFS: AttributeError: module 'nose.tools' has no attribute 'assert_equals'. Did you mean:

Bug#833828: marked as done (Migrations of stable's python3-django-markupfield (1.2.1) do not work with stable's django version (1.7.x).)

2024-01-15 Thread Debian Bug Tracking System
Your message dated Mon, 15 Jan 2024 14:24:37 +0100 with message-id and subject line Bug not relevant any more has caused the Debian Bug report #833828, regarding Migrations of stable's python3-django-markupfield (1.2.1) do not work with stable's django version (1.7.x). to be marked as done.

Processed: Re: Bug#1060735: glib2.0/experimental: FTBFS on s390x and other 64-bit BE: gdatetime test fails or crashes

2024-01-15 Thread Debian Bug Tracking System
Processing control commands: > severity -1 important Bug #1060735 [src:glib2.0] glib2.0/experimental: FTBFS on s390x and other 64-bit BE: gdatetime test fails or crashes Severity set to 'important' from 'serious' -- 1060735: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1060735 Debian Bug

Bug#1060735: glib2.0/experimental: FTBFS on s390x and other 64-bit BE: gdatetime test fails or crashes

2024-01-15 Thread Simon McVittie
Control: severity -1 important On Sat, 13 Jan 2024 at 19:32:58 +, Simon McVittie wrote: > On Sat, 13 Jan 2024 at 16:21:46 +, Simon McVittie wrote: > > On Sat, 13 Jan 2024 at 15:21:02 +, Simon McVittie wrote: > > > I recently uploaded a snapshot of GLib 2.79.x to experimental (in > > >

Processed: intent to salvage package

2024-01-15 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > forwarded 1054725 https://github.com/manugarg/pacparser/issues/185 Bug #1054725 [src:pacparser] pacparser: FTBFS: IndexError: list index out of range Set Bug forwarded-to-address to 'https://github.com/manugarg/pacparser/issues/185'. > End of

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

2024-01-15 Thread Jörg Riesmeier
Hi Mathieu et al., it seems that the stack problem is limited to the "drttest" tool, which is not really needed for a Linux distribution like Debian. Anyway, in the meantime, I have revised the implementation of this test tool to avoid the creation of huge data structures on the stack. See

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

2024-01-15 Thread Emanuele Rocca
Hi Mathieu, On 2024-01-14 11:24, Mathieu Malaterre wrote: > On Sat, Jan 13, 2024 at 9:42 PM Emanuele Rocca wrote: > > We should downgrade the severity to minor once the fix enters unstable, but > > keep the bug open as this seems to be an interesting case of > > stack-clash-protection

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

2024-01-15 Thread Debian Bug Tracking System
Your message dated Mon, 15 Jan 2024 12:34:32 + with message-id and subject line Bug#1056414: fixed in ipython 8.20.0-1 has caused the Debian Bug report #1056414, regarding ipython's autopkg tests fail with Python 3.12 to be marked as done. This means that you claim that the problem has been

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

2024-01-15 Thread Debian Bug Tracking System
Your message dated Mon, 15 Jan 2024 12:20:17 + with message-id and subject line Bug#1058441: fixed in python-docx 1.1.0+dfsg-2 has caused the Debian Bug report #1058441, regarding python-docx: FTBFS: dh_auto_test: error: pybuild --test --test-pytest -i python{version} -p "3.12 3.11" returned

Bug#1060788: marked as done (pycuda: requires rebuild for boost 1.83 transition)

2024-01-15 Thread Debian Bug Tracking System
Your message dated Mon, 15 Jan 2024 11:55:04 + with message-id and subject line Bug#1060788: fixed in pycuda 2024.1~dfsg-1 has caused the Debian Bug report #1060788, regarding pycuda: requires rebuild for boost 1.83 transition to be marked as done. This means that you claim that the problem

Bug#1057949: nbconvert: needs update for new version of pandoc: PDF creating failed

2024-01-15 Thread Drew Parsons
Source: nbconvert Version: 6.5.3-4 Followup-For: Bug #1057949 An nbconvert update (>= 7.6) is also needed to support the latest version of pandoc 3.1.3. That is, to avoid the warning that pandoc 3.1.3 is "unsupported". cf.

Processed: Re: Bug#1059936: Tracked down `behavior of -n is non-portable`

2024-01-15 Thread Debian Bug Tracking System
Processing control commands: > reassign -1 klibc-utils Bug #1059936 [initramfs-tools] initramfs-tools: update-initramfs yields "cp: warning: behavior of -n is non-portable and may change in future" Bug reassigned from package 'initramfs-tools' to 'klibc-utils'. No longer marked as found in

Processed: severity of 1058497 is normal

2024-01-15 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > severity 1058497 normal Bug #1058497 [reform-firedecor] reform-firedecor: Please update to wlroots 0.17 Severity set to 'normal' from 'serious' > thanks Stopping processing here. Please contact me if you need assistance. -- 1058497:

Processed: Re: FTBFS: object has no attribute 'assertNotEquals'. Did you mean: 'assertNotEqual'

2024-01-15 Thread Debian Bug Tracking System
Processing control commands: > tags -1 upstream Bug #1057393 [src:azure-cli] FTBFS: object has no attribute 'assertNotEquals'. Did you mean: 'assertNotEqual' Added tag(s) upstream. > forwarded -1 https://github.com/Azure/azure-cli/issues/28194 Bug #1057393 [src:azure-cli] FTBFS: object has no

Bug#1057393: FTBFS: object has no attribute 'assertNotEquals'. Did you mean: 'assertNotEqual'

2024-01-15 Thread Andreas Tille
Control: tags -1 upstream Control: forwarded -1 https://github.com/Azure/azure-cli/issues/28194 Control: retitle -1 FTBFS: object has no attribute 'assertDictContainsSubset' Hi, while I was able to fix the object has no attribute 'assertNotEquals'. Did you mean: 'assertNotEqual' issue in Git I

Bug#1060827: marked as done (hxtools has an undeclared file conflict on /usr/bin/xmlformat)

2024-01-15 Thread Debian Bug Tracking System
Your message dated Mon, 15 Jan 2024 09:49:04 + with message-id and subject line Bug#1060827: fixed in hxtools 20231224-2 has caused the Debian Bug report #1060827, regarding hxtools has an undeclared file conflict on /usr/bin/xmlformat to be marked as done. This means that you claim that the

Bug#1060653: marked as done (os-autoinst: FTBFS on i386: t/01-test_needle.t failure)

2024-01-15 Thread Debian Bug Tracking System
Your message dated Mon, 15 Jan 2024 09:49:21 + with message-id and subject line Bug#1060653: fixed in os-autoinst 4.6.1699947509.970d0609-2 has caused the Debian Bug report #1060653, regarding os-autoinst: FTBFS on i386: t/01-test_needle.t failure to be marked as done. This means that you

Bug#1058371: marked as done (python3-astroid: incompatible with Python 3.12 (exception: 'TreeRebuilder' object has no attribute 'visit_typealias'))

2024-01-15 Thread Debian Bug Tracking System
Your message dated Mon, 15 Jan 2024 09:03:58 + with message-id and subject line Bug#1058371: fixed in astroid 3.0.2-1 has caused the Debian Bug report #1058371, regarding python3-astroid: incompatible with Python 3.12 (exception: 'TreeRebuilder' object has no attribute 'visit_typealias') to

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

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

Bug#1033167: marked as done (usrmerge: messes with /etc/shells)

2024-01-15 Thread Debian Bug Tracking System
Your message dated Mon, 15 Jan 2024 08:32:08 + with message-id and subject line Bug#1033167: fixed in usrmerge 37~deb12u1 has caused the Debian Bug report #1033167, regarding usrmerge: messes with /etc/shells to be marked as done. This means that you claim that the problem has been dealt

Bug#1058371: marked as pending in astroid

2024-01-15 Thread Sandro Tosi
Control: tag -1 pending Hello, Bug #1058371 in astroid 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#1058103: marked as pending in astroid

2024-01-15 Thread Sandro Tosi
Control: tag -1 pending Hello, Bug #1058103 in astroid 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#1058103 marked as pending in astroid

2024-01-15 Thread Debian Bug Tracking System
Processing control commands: > tag -1 pending Bug #1058103 [src:astroid] astroid: 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. -- 1058103: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1058103 Debian

Processed: Bug#1058371 marked as pending in astroid

2024-01-15 Thread Debian Bug Tracking System
Processing control commands: > tag -1 pending Bug #1058371 [python3-astroid] python3-astroid: incompatible with Python 3.12 (exception: 'TreeRebuilder' object has no attribute 'visit_typealias') Added tag(s) pending. -- 1058371: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1058371 Debian