Processed: Cron sending email is *NOT* an RC bug please...

2023-12-11 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > severity 1057083 important Bug #1057083 [openstack-cluster-installer] openstack-cluster-installer: cronjob produces output after package removal Severity set to 'important' from 'serious' > End of message, stopping processing here. Please

Processed: gtsam b-d's on python3-all-dev, but only builds for the default python version

2023-12-11 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > tags 1055683 + ftbfs Bug #1055683 [src:gtsam] gtsam b-d's on python3-all-dev, but only builds for the default python version Added tag(s) ftbfs. > thanks Stopping processing here. Please contact me if you need assistance. -- 1055683:

Bug#1057967: linux-image-6.1.0-15-amd64 renders my physical bookworm/gnome computer largely unusable

2023-12-11 Thread Grand T
Hello all Same issue here The update to linux-image-6.1.0-15-amd64 broke the system Despite this Calcul de la mise à jour… Les NOUVEAUX paquets suivants seront installés : linux-headers-6.1.0-15-amd64 linux-headers-6.1.0-15-common linux-image-6.1.0-15-amd64 Les paquets suivants seront mis

Bug#1056471: Patch for 3.12

2023-12-11 Thread Jerome Kieffer
Hi, I am the upstream author of FabIO and indeed, there is a regression in the tests when run for the first time. This is linked to an un-flushed file. This can simply be corrected with this simple patch https://github.com/silx-kit/fabio/pull/550/files It is probably simpler to debian to just

Bug#1058024: skimage tries to access the net during the build

2023-12-11 Thread Matthias Klose
Package: src:skimage Version: 0.22.0-2 Severity: serious Tags: sid trixie User: debian-pyt...@lists.debian.org Usertags: python3.12 skimage tries to access the net during the build, only seen when the binary-indep packages are also built. [...] debian/rules override_dh_installdocs-indep

Bug#1050623: marked as done (intake: newlines in error messages)

2023-12-11 Thread Debian Bug Tracking System
Your message dated Mon, 11 Dec 2023 09:49:07 + with message-id and subject line Bug#1050623: fixed in intake 0.6.6-2 has caused the Debian Bug report #1050623, regarding intake: newlines in error messages to be marked as done. This means that you claim that the problem has been dealt with.

Bug#1044050: marked as done (intake: newlines in error messages)

2023-12-11 Thread Debian Bug Tracking System
Your message dated Mon, 11 Dec 2023 09:49:07 + with message-id and subject line Bug#1050623: fixed in intake 0.6.6-2 has caused the Debian Bug report #1050623, regarding intake: newlines in error messages to be marked as done. This means that you claim that the problem has been dealt with.

Bug#1044050: marked as done (intake: newlines in error messages)

2023-12-11 Thread Debian Bug Tracking System
Your message dated Mon, 11 Dec 2023 09:49:07 + with message-id and subject line Bug#1044050: fixed in intake 0.6.6-2 has caused the Debian Bug report #1044050, regarding intake: newlines in error messages to be marked as done. This means that you claim that the problem has been dealt with.

Bug#1050623: marked as done (intake: newlines in error messages)

2023-12-11 Thread Debian Bug Tracking System
Your message dated Mon, 11 Dec 2023 09:49:07 + with message-id and subject line Bug#1044050: fixed in intake 0.6.6-2 has caused the Debian Bug report #1044050, regarding intake: newlines in error messages to be marked as done. This means that you claim that the problem has been dealt with.

Bug#1057843: linux: ext4 data corruption in 6.1.64-1

2023-12-11 Thread helios . solaris
I have been running debian 12.3 with kernel 6.1.64-1 for a few hours, how can I find out whether the file system has been corrupted?

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

2023-12-11 Thread Debian Bug Tracking System
Your message dated Mon, 11 Dec 2023 09:34:04 + with message-id and subject line Bug#1056421: fixed in loguru 0.7.2-1 has caused the Debian Bug report #1056421, regarding loguro's autopkg tests fail with Python 3.12 to be marked as done. This means that you claim that the problem has been

Bug#1055734: marked as done (python-yappi ftbfs with Python 3.12)

2023-12-11 Thread Debian Bug Tracking System
Your message dated Mon, 11 Dec 2023 09:19:41 + with message-id and subject line Bug#1055734: fixed in python-yappi 1.4.0-3 has caused the Debian Bug report #1055734, regarding python-yappi ftbfs with Python 3.12 to be marked as done. This means that you claim that the problem has been dealt

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

2023-12-11 Thread Debian Bug Tracking System
Your message dated Mon, 11 Dec 2023 09:19:29 + with message-id and subject line Bug#1056475: fixed in python-imageio 2.33.1-1 has caused the Debian Bug report #1056475, regarding python-imageio's autopkg tests fail with Python 3.12 to be marked as done. This means that you claim that the

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

2023-12-11 Thread Debian Bug Tracking System
Your message dated Mon, 11 Dec 2023 08:34:44 + with message-id and subject line Bug#1056541: fixed in xdoctest 1.1.2-1 has caused the Debian Bug report #1056541, regarding xdoctest's autopkg tests fail with Python 3.12 to be marked as done. This means that you claim that the problem has been

Bug#1058018: libadios2-common-core-dev has an undeclared file conflict on /usr/lib/x86_64-linux-gnu/cmake/adios2/adios2-config.cmake

2023-12-11 Thread Helmut Grohne
Package: libadios2-common-core-dev Version: 2.9.2+dfsg1-4 Severity: serious User: debian...@lists.debian.org Usertags: fileconflict Control: affects -1 + libadios2-serial-core-dev libadios2-common-core-dev has an undeclared file conflict. This may result in an unpack error from dpkg. The file

Processed: libadios2-common-core-dev has an undeclared file conflict on /usr/lib/x86_64-linux-gnu/cmake/adios2/adios2-config.cmake

2023-12-11 Thread Debian Bug Tracking System
Processing control commands: > affects -1 + libadios2-serial-core-dev Bug #1058018 [libadios2-common-core-dev] libadios2-common-core-dev has an undeclared file conflict on /usr/lib/x86_64-linux-gnu/cmake/adios2/adios2-config.cmake Added indication that 1058018 affects libadios2-serial-core-dev

<    1   2