Processed: reassign 1058265 to src:sqlalchemy, affects 1058265

2023-12-15 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > reassign 1058265 src:sqlalchemy Bug #1058265 [src:python-flask-marshmallow] python-flask-marshmallow: FTBFS: dh_auto_test: error: pybuild --test --test-pytest -i python{version} -p "3.12 3.11" returned exit code 13 Bug reassigned from package

Bug#1058301: resampy: FTBFS: dh_auto_test: error: pybuild --test --test-pytest -i python{version} -p "3.12 3.11" returned exit code 13

2023-12-15 Thread Antonio Valentino
On Tue, 12 Dec 2023 09:24:48 +0100 Lucas Nussbaum wrote: Source: resampy Version: 0.4.2+ds-3 Severity: serious Justification: FTBFS Tags: trixie sid ftbfs User: lu...@debian.org Usertags: ftbfs-20231212 ftbfs-trixie Hi, During a rebuild of all packages in sid, your package failed to build on

Processed: reassign #1058301

2023-12-15 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > reassign 1058301 src:numba Bug #1058301 [src:resampy] resampy: FTBFS: dh_auto_test: error: pybuild --test --test-pytest -i python{version} -p "3.12 3.11" returned exit code 13 Bug reassigned from package 'src:resampy' to 'src:numba'. No longer

Bug#1058148: marked as done (bleachbit: FTBFS: ImportError: cannot import name 'SafeConfigParser' from 'configparser' (/usr/lib/python3.12/configparser.py). Did you mean: 'RawConfigParser'?)

2023-12-15 Thread Debian Bug Tracking System
Your message dated Sat, 16 Dec 2023 04:49:05 + with message-id and subject line Bug#1058148: fixed in bleachbit 4.6.0-1 has caused the Debian Bug report #1058148, regarding bleachbit: FTBFS: ImportError: cannot import name 'SafeConfigParser' from 'configparser'

Bug#1058336: visidata: FTBFS: dh_auto_test: error: pybuild --test --test-pytest -i python{version} -p "3.12 3.11" returned exit code 13

2023-12-15 Thread Anja
Hello! Thanks for letting us know. > > self = , k = '_parts' > > def __getattr__(self, k): > if hasattr(self.__dict__, k): > r = getattr(self.__dict__, k) > else: > if self.__dict__.get('_path', None) is not None: > > r =

Bug#1052309: marked as done (lirc FTBFS when systemd.pc changes systemdsystemunitdir)

2023-12-15 Thread Debian Bug Tracking System
Your message dated Sat, 16 Dec 2023 01:04:40 + with message-id and subject line Bug#1052309: fixed in lirc 0.10.1-7.3 has caused the Debian Bug report #1052309, regarding lirc FTBFS when systemd.pc changes systemdsystemunitdir to be marked as done. This means that you claim that the problem

Bug#1058556: marked as done (binutils-or1k-elf: FTBFS: make[1]: *** [debian/rules:29: src] Error 1)

2023-12-15 Thread Debian Bug Tracking System
Your message dated Fri, 15 Dec 2023 23:04:32 + with message-id and subject line Bug#1058556: fixed in binutils-or1k-elf 1.0.10 has caused the Debian Bug report #1058556, regarding binutils-or1k-elf: FTBFS: make[1]: *** [debian/rules:29: src] Error 1 to be marked as done. This means that you

Bug#1052983: Bug#1057914: Bug#1056996: bluez: diff for NMU version 5.70-1.1~exp0

2023-12-15 Thread Nobuhiro Iwamatsu
HI Salvatore, 2023年12月16日(土) 5:40 Salvatore Bonaccorso : > > Hi Nobuhiro, > > On Fri, Dec 15, 2023 at 05:38:17AM +0100, Salvatore Bonaccorso wrote: > > Hi Nobuhiro > > > > On Fri, Dec 15, 2023 at 08:37:13AM +0900, Nobuhiro Iwamatsu wrote: > > > Hi Salvatore, > > > > > > Thanks for your work. > >

Bug#1057329: marked as done (rust-rlp: autopkgtest failure on 32bit)

2023-12-15 Thread Debian Bug Tracking System
Your message dated Fri, 15 Dec 2023 22:25:21 + with message-id and subject line re: rust-rlp: autopkgtest failure on 32bit has caused the Debian Bug report #1057329, regarding rust-rlp: autopkgtest failure on 32bit to be marked as done. This means that you claim that the problem has been

Bug#1057760: marked as done (settle - upcoming rust-rusqlite update.)

2023-12-15 Thread Debian Bug Tracking System
Your message dated Fri, 15 Dec 2023 21:24:24 + with message-id and subject line Bug#1057760: fixed in settle 0.40.1-2 has caused the Debian Bug report #1057760, regarding settle - upcoming rust-rusqlite update. to be marked as done. This means that you claim that the problem has been dealt

Bug#1058074: marked as done (rust-hyper-rustls - autopkgtest failure)

2023-12-15 Thread Debian Bug Tracking System
Your message dated Fri, 15 Dec 2023 21:06:14 + with message-id and subject line Bug#1058074: fixed in rust-hyper-rustls 0.24.2-2 has caused the Debian Bug report #1058074, regarding rust-hyper-rustls - autopkgtest failure to be marked as done. This means that you claim that the problem has

Bug#1058239: marked as done (onionbalance: FTBFS: AttributeError: module 'configparser' has no attribute 'SafeConfigParser'. Did you mean: 'RawConfigParser'?)

2023-12-15 Thread Debian Bug Tracking System
Your message dated Fri, 15 Dec 2023 20:55:13 + with message-id and subject line Bug#1058239: fixed in onionbalance 0.2.2-1.2 has caused the Debian Bug report #1058239, regarding onionbalance: FTBFS: AttributeError: module 'configparser' has no attribute 'SafeConfigParser'. Did you mean:

Bug#1058767: netplug: unmaintained

2023-12-15 Thread Chris Hofstaedtler
Source: netplug Version: 1.2.9.2-3.2 Severity: serious I'm filing this to get netplug removed from testing, with the goal of removing it from unstable later, and before that happens, anyone who wants to actually maintain this package can speak up. As demonstrated today, having packages in stable

Bug#1057403: marked as done (fq: Please upgrade to fq 0.9.0 (resolves FTBFS with latest golang-golang-x-exp-dev))

2023-12-15 Thread Debian Bug Tracking System
Your message dated Fri, 15 Dec 2023 12:41:03 -0800 with message-id and subject line Fixed in 0.9.0-1 has caused the Debian Bug report #1057403, regarding fq: Please upgrade to fq 0.9.0 (resolves FTBFS with latest golang-golang-x-exp-dev) to be marked as done. This means that you claim that the

Bug#1057591: octave-vibes: FTBFS: fatal: caught signal Segmentation fault -- stopping myself...

2023-12-15 Thread Rafael Laboissière
* Santiago Vila [2023-12-15 18:15]: The thing I don't understand here is why this problem in octave-vibes was diagnosed as an "unwritable $HOME" in the first place. This is what I concluded after running some tests, but I do not remember the details. I will try to replicate it. Best,

Bug#1052983: Bug#1057914: Bug#1056996: bluez: diff for NMU version 5.70-1.1~exp0

2023-12-15 Thread Salvatore Bonaccorso
Hi Nobuhiro, On Fri, Dec 15, 2023 at 05:38:17AM +0100, Salvatore Bonaccorso wrote: > Hi Nobuhiro > > On Fri, Dec 15, 2023 at 08:37:13AM +0900, Nobuhiro Iwamatsu wrote: > > Hi Salvatore, > > > > Thanks for your work. > > This patch looks good to me. > > Please upload without DELAYED/2 to

Bug#1057914: marked as done (bluez: CVE-2023-45866)

2023-12-15 Thread Debian Bug Tracking System
Your message dated Fri, 15 Dec 2023 20:35:01 + with message-id and subject line Bug#1057914: fixed in bluez 5.70-1.1 has caused the Debian Bug report #1057914, regarding bluez: CVE-2023-45866 to be marked as done. This means that you claim that the problem has been dealt with. If this is not

Bug#1052983: marked as done (bluez FTBFS when systemd.pc changes systemdsystemunitdir)

2023-12-15 Thread Debian Bug Tracking System
Your message dated Fri, 15 Dec 2023 20:35:01 + with message-id and subject line Bug#1052983: fixed in bluez 5.70-1.1 has caused the Debian Bug report #1052983, regarding bluez FTBFS when systemd.pc changes systemdsystemunitdir to be marked as done. This means that you claim that the problem

Bug#1058752: bug#62572: cp --no-clobber behavior has changed

2023-12-15 Thread Michael Stone
On Fri, Dec 15, 2023 at 11:21:06AM -0800, Paul Eggert wrote: Stlll, Pádraig gave a reasonable summary of why the change was made, despite its incompatibility with previous behavior. (One thing I'd add is that the FreeBSD behavior is inherently less race-prone.) It seemed like a good idea at

Processed: forcibly merging 1057564 1058116

2023-12-15 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > forcemerge 1057564 1058116 Bug #1057564 [src:gnome-bluetooth3] gnome-bluetooth3: FTBFS: failing tests Bug #1057564 [src:gnome-bluetooth3] gnome-bluetooth3: FTBFS: failing tests Added tag(s) sid and trixie. Bug #1058116 [src:gnome-bluetooth3]

Bug#1057604: marked as done (texext: FTBFS: AttributeError: module 'configparser' has no attribute 'SafeConfigParser'. Did you mean: 'RawConfigParser'?)

2023-12-15 Thread Debian Bug Tracking System
Your message dated Fri, 15 Dec 2023 19:49:37 + with message-id and subject line Bug#1057604: fixed in texext 0.6.7-3 has caused the Debian Bug report #1057604, regarding texext: FTBFS: AttributeError: module 'configparser' has no attribute 'SafeConfigParser'. Did you mean: 'RawConfigParser'?

Bug#1058752: bug#62572: cp --no-clobber behavior has changed

2023-12-15 Thread Paul Eggert
On 2023-12-15 10:49, Michael Stone wrote: There's no compelling reason to force this change Well, certainly nobody compelled us at gunpoint Stlll, Pádraig gave a reasonable summary of why the change was made, despite its incompatibility with previous behavior. (One thing I'd add is that

Bug#1058752: bug#62572: cp --no-clobber behavior has changed

2023-12-15 Thread Michael Stone
On Fri, Dec 15, 2023 at 06:33:00PM +, Pádraig Brady wrote: Advantages of leaving as is: We get consistency of "noclobber" behavior across systems / shells. You don't, unless you ignore the coreutils/linux installed base entirely. Essentially the current situation is that -n shouldn't be

Bug#1058752: bug#62572: cp --no-clobber behavior has changed

2023-12-15 Thread Pádraig Brady
On 15/12/2023 15:56, Michael Stone wrote: I tend to think this was a serious mistake: it breaks the behavior of existing scripts with no deprecation period. A stated advantage is better compatibility with freebsd, but I don't understand why that is more desirable than compatibility with all

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

2023-12-15 Thread Debian Bug Tracking System
Your message dated Fri, 15 Dec 2023 18:22:47 + with message-id and subject line Bug#1058295: fixed in python-markdown2 2.4.11-1 has caused the Debian Bug report #1058295, regarding python-markdown2: FTBFS: dh_auto_test: error: pybuild --test --test-pytest -i python{version} -p "3.12 3.11"

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

2023-12-15 Thread Debian Bug Tracking System
Your message dated Fri, 15 Dec 2023 18:22:47 + with message-id and subject line Bug#1056480: fixed in python-markdown2 2.4.11-1 has caused the Debian Bug report #1056480, regarding python-markdown2's autopkg tests fail with Python 3.12 to be marked as done. This means that you claim that the

Bug#996801: marked as done (db2twitter: unusable with tweepy version 4)

2023-12-15 Thread Debian Bug Tracking System
Your message dated Fri, 15 Dec 2023 18:15:19 + with message-id and subject line Bug#1056611: Removed package(s) from unstable has caused the Debian Bug report #996801, regarding db2twitter: unusable with tweepy version 4 to be marked as done. This means that you claim that the problem has

Bug#984100: marked as done (libdjconsole: ftbfs with GCC-11)

2023-12-15 Thread Debian Bug Tracking System
Your message dated Fri, 15 Dec 2023 17:49:05 + with message-id and subject line Bug#984100: fixed in libdjconsole 0.1.3-3.1 has caused the Debian Bug report #984100, regarding libdjconsole: ftbfs with GCC-11 to be marked as done. This means that you claim that the problem has been dealt

Processed: block 1055694 with 1058752

2023-12-15 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > block 1055694 with 1058752 Bug #1055694 [klibc-utils] initramfs-tools: After updating coreutils cp: not replacing in console when running update-initramfs Bug #1056912 [klibc-utils] initramfs-tools: update-initramfs - can't generate initramfs

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

2023-12-15 Thread Debian Bug Tracking System
Your message dated Fri, 15 Dec 2023 17:19:02 + with message-id and subject line Bug#1056510: fixed in python-upsetplot 0.8.0-2 has caused the Debian Bug report #1056510, regarding python-upsetplot's autopkg tests fail with Python 3.12 to be marked as done. This means that you claim that the

Bug#1057591: octave-vibes: FTBFS: fatal: caught signal Segmentation fault -- stopping myself...

2023-12-15 Thread Santiago Vila
El 15/12/23 a las 17:00, Rafael Laboissière escribió:     […]     HOME=/sbuild-nonexistent     […] It seems that your building system is setting HOME to an non-existent directory. How do you explain that ? In this case, given its name, the variable is set by sbuild before starting the

Processed: tagging 1058749

2023-12-15 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > tags 1058749 + sid trixie Bug #1058749 [scanbd] scanbd: fails to upgrade from bookworm: mv: not replacing '/etc/scanbd/dll.conf' Added tag(s) trixie and sid. > thanks Stopping processing here. Please contact me if you need assistance. --

Bug#1058281: octave-ncarray: FTBFS: make: *** [debian/rules:5: binary] Error 139

2023-12-15 Thread Rafael Laboissière
Control: block -1 by 1058621 Control: merge -1 1057590 Trying again…

Processed: Re: Bug#1058281: octave-ncarray: FTBFS: make: *** [debian/rules:5: binary] Error 139

2023-12-15 Thread Debian Bug Tracking System
Processing control commands: > block -1 by 1058621 Bug #1058281 [src:octave-netcdf] octave-ncarray: FTBFS: make: *** [debian/rules:5: binary] Error 139 1058281 was not blocked by any bugs. 1058281 was not blocking any bugs. Added blocking bug(s) of 1058281: 1058621 > merge -1 1057590 Bug

Bug#1057591: octave-vibes: FTBFS: fatal: caught signal Segmentation fault -- stopping myself...

2023-12-15 Thread Rafael Laboissière
Rafael * Santiago Vila [2023-12-15 12:59]: El 13/12/23 a las 9:27, Rafael Laboissière escribió: i.e. you may rely on a writable $HOME if it's for a "good cause" (i.e. dh_auto_test). So, the simple question: Should this not be also implemented in dh_octave_check as well, which is what

Bug#1058752: cp --no-clobber behavior has changed

2023-12-15 Thread Michael Stone
I tend to think this was a serious mistake: it breaks the behavior of existing scripts with no deprecation period. A stated advantage is better compatibility with freebsd, but I don't understand why that is more desirable than compatibility with all deployed gnu/linux systems? I also don't

Bug#1058124: marked as done (graphite-web: FTBFS: AttributeError: 'ConfigParser' object has no attribute 'readfp'. Did you mean: 'read'?)

2023-12-15 Thread Debian Bug Tracking System
Your message dated Fri, 15 Dec 2023 15:50:26 + with message-id and subject line Bug#1058124: fixed in graphite-web 1.1.10-2 has caused the Debian Bug report #1058124, regarding graphite-web: FTBFS: AttributeError: 'ConfigParser' object has no attribute 'readfp'. Did you mean: 'read'? to be

Processed: notfound 1058749 in scanbd/1.5.1-6+b1, found 1058749 in scanbd/1.5.1-6

2023-12-15 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > notfound 1058749 scanbd/1.5.1-6+b1 Bug #1058749 [scanbd] scanbd: fails to upgrade from bookworm: mv: not replacing '/etc/scanbd/dll.conf' The source scanbd and version 1.5.1-6+b1 do not appear to match any binary packages No longer marked as

Processed: Re: Bug#1058749: scanbd: fails to upgrade from bookworm: mv: not replacing '/etc/scanbd/dll.conf'

2023-12-15 Thread Debian Bug Tracking System
Processing control commands: > found -1 scanbd/1.5.1-6+b1 Bug #1058749 [scanbd] scanbd: fails to upgrade from bookworm: mv: not replacing '/etc/scanbd/dll.conf' The source scanbd and version 1.5.1-6+b1 do not appear to match any binary packages Marked as found in versions scanbd/1.5.1-6+b1. >

Bug#1058749: scanbd: fails to upgrade from bookworm: mv: not replacing '/etc/scanbd/dll.conf'

2023-12-15 Thread Chris Hofstaedtler
Control: found -1 scanbd/1.5.1-6+b1 Control: block -1 by 1058752 Hi Andreas, I'm unsure what to do here. This problem is triggered by a behaviour change in coreutils. On Fri, Dec 15, 2023 at 03:17:18PM +0100, Andreas Beckmann wrote: > during a test with piuparts I noticed your package fails to

Processed: bug 1058752 is forwarded to https://debbugs.gnu.org/cgi/bugreport.cgi?bug=62572

2023-12-15 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > forwarded 1058752 https://debbugs.gnu.org/cgi/bugreport.cgi?bug=62572 Bug #1058752 [coreutils] coreutils: cp/mv changed return code in incompatible way Set Bug forwarded-to-address to 'https://debbugs.gnu.org/cgi/bugreport.cgi?bug=62572'. >

Bug#1058551: marked as done (git-buildpackage: FTBFS: make[2]: *** [Makefile:22: syntax-check] Error 1)

2023-12-15 Thread Debian Bug Tracking System
Your message dated Fri, 15 Dec 2023 15:19:40 + with message-id and subject line Bug#1058551: fixed in git-buildpackage 0.9.33 has caused the Debian Bug report #1058551, regarding git-buildpackage: FTBFS: make[2]: *** [Makefile:22: syntax-check] Error 1 to be marked as done. This means that

Processed: user debian...@lists.debian.org, usertagging 1054931, affects 1054931, usertagging 1055511 ...

2023-12-15 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > user debian...@lists.debian.org Setting user to debian...@lists.debian.org (was a...@debian.org). > usertags 1054931 piuparts There were no usertags set. Usertags are now: piuparts. > affects 1054931 + libghc-tidal-dev Bug #1054931

Processed: coreutils: cp/mv changed return code in incompatible way

2023-12-15 Thread Debian Bug Tracking System
Processing control commands: > affects -1 initramfs-tools scanbd Bug #1058752 [coreutils] coreutils: cp/mv changed return code in incompatible way Added indication that 1058752 affects initramfs-tools and scanbd -- 1058752: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1058752 Debian Bug

Bug#1058752: coreutils: cp/mv changed return code in incompatible way

2023-12-15 Thread Chris Hofstaedtler
Package: coreutils Version: 9.4-1 Severity: serious Tags: upstream Control: affects -1 initramfs-tools scanbd Hi, cp and mv -n changed their behaviour with regard to their exit code when doing nothing, and also now write to stderr. This causes a few problems in existing packages: 1)

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

2023-12-15 Thread Debian Bug Tracking System
Your message dated Fri, 15 Dec 2023 15:05:50 + with message-id and subject line Bug#1058297: fixed in python-svg.path 6.3-2 has caused the Debian Bug report #1058297, regarding python-svg.path: FTBFS: dh_auto_test: error: pybuild --test --test-pytest -i python{version} -p "3.12 3.11"

Bug#1058751: r-cran-rcppparallel: broken symlinks: /usr/lib/R/site-library/RcppParallel/lib/libtbb*.so.*.8 -> ../../../..//libtbb*.so.*.8

2023-12-15 Thread Andreas Beckmann
Package: r-cran-rcppparallel Version: 5.1.7+dfsg-1 Severity: serious User: debian...@lists.debian.org Usertags: piuparts Hi, during a test with piuparts I noticed your package ships broken symlinks. >From the attached log (scroll to the bottom...): 3m44.2s ERROR: FAIL: Broken symlinks:

Bug#1055159: marked as done (python-svg.path's autopkg tests fail with pillow 10.1.0)

2023-12-15 Thread Debian Bug Tracking System
Your message dated Fri, 15 Dec 2023 15:05:50 + with message-id and subject line Bug#1055159: fixed in python-svg.path 6.3-2 has caused the Debian Bug report #1055159, regarding python-svg.path's autopkg tests fail with pillow 10.1.0 to be marked as done. This means that you claim that the

Bug#1058516: marked as done (fiat-ecmwf: FTBFS: make[1]: *** [debian/rules:42: override_dh_auto_configure] Error 2)

2023-12-15 Thread Debian Bug Tracking System
Your message dated Fri, 15 Dec 2023 15:02:14 + with message-id and subject line FIxed in last upload has caused the Debian Bug report #1058516, regarding fiat-ecmwf: FTBFS: make[1]: *** [debian/rules:42: override_dh_auto_configure] Error 2 to be marked as done. This means that you claim

Bug#1058749: scanbd: fails to upgrade from bookworm: mv: not replacing '/etc/scanbd/dll.conf'

2023-12-15 Thread Andreas Beckmann
Package: scanbd Version: 1.5.1-7 Severity: serious User: debian...@lists.debian.org Usertags: piuparts X-Debbugs-Cc: Chris Hofstaedtler Hi, during a test with piuparts I noticed your package fails to upgrade from 'bookworm'. It installed fine in 'bookworm', then the upgrade to 'sid' fails.

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

2023-12-15 Thread Debian Bug Tracking System
Your message dated Fri, 15 Dec 2023 14:08:46 + with message-id and subject line Re: Bug#1058402: spyder-kernels: FTBFS: dh_auto_test: error: pybuild --test --test-pytest -i python{version} -p "3.12 3.11" returned exit code 13 has caused the Debian Bug report #1058402, regarding

Processed: Re: Bug#1056531: cython 3.x (for Python 3.12)

2023-12-15 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > severity 1056531 important Bug #1056531 [src:spyder-kernels] spyder-kernels autopkg tests fail with Python 3.12 Severity set to 'important' from 'serious' > retitle 1056531 spyder-kernels: cannot handle Cython files with Python 3.12 Bug #1056531

Bug#1056531: cython 3.x (for Python 3.12)

2023-12-15 Thread Julian Gilbey
severity 1056531 important retitle 1056531 spyder-kernels: cannot handle Cython files with Python 3.12 thanks Update on this bug. cython3-legacy and the current cython3 (which I've just updated to not fail the autopkgtest tests with Python 3.12) do not have working pyximport modules. So I'm

Bug#1058532: golang-google-api: FTBFS: tests failed

2023-12-15 Thread M Hickford
> --- FAIL: TestTokenSource (0.00s) > panic: cannot handle unexported field at {*google.Credentials}.universeDomain: > "golang.org/x/oauth2/google".Credentials This is fixed upstream https://github.com/googleapis/google-api-go-client/commit/b3a71bda027d9ff92df3bf76b5ee9ffa55520dd9 so hopefully

Bug#1055554: marked as done (python-libais ftbfs with Python 3.12)

2023-12-15 Thread Debian Bug Tracking System
Your message dated Fri, 15 Dec 2023 13:51:00 + with message-id and subject line Bug#104: fixed in python-libais 0.17+git.20190917.master.e464cf8-4 has caused the Debian Bug report #104, regarding python-libais ftbfs with Python 3.12 to be marked as done. This means that you claim

Bug#1050097: Maintainers, please fix

2023-12-15 Thread hardpenguin13
Hi there. Installing the dependencies manually works. Please accept the patch and rebuild the package and then close the bug ️.

Processed: Re: Bug#1056485: python-mpd asyncio tests fail with Python 3.12

2023-12-15 Thread Debian Bug Tracking System
Processing control commands: > retitle -1 python-mpd asyncio tests fail with Python 3.12 Bug #1056485 [src:python-mpd] python-mpd's autopkg tests fail with Python 3.12 Changed Bug title to 'python-mpd asyncio tests fail with Python 3.12' from 'python-mpd's autopkg tests fail with Python 3.12'. >

Bug#1056485: python-mpd asyncio tests fail with Python 3.12

2023-12-15 Thread Simon McVittie
Control: retitle -1 python-mpd asyncio tests fail with Python 3.12 Control: severity -1 important On Sun, 10 Dec 2023 at 20:59:48 +, Simon McVittie wrote: > On Wed, 22 Nov 2023 at 15:18:06 +0100, Matthias Klose wrote: > > python-mpd's autopkg tests fail with Python 3.12: > > [...] > > 248s

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

2023-12-15 Thread Debian Bug Tracking System
Your message dated Fri, 15 Dec 2023 13:22:02 + with message-id and subject line Bug#1056492: fixed in python-pomegranate 0.14.8-4 has caused the Debian Bug report #1056492, regarding python-pomegranate's autopkg tests fail with Python 3.12 to be marked as done. This means that you claim that

Bug#1058746: libghc-swish-doc: Depends: haddock-interface-38 but it is not installable

2023-12-15 Thread Sebastian Ramacher
Package: libghc-swish-doc Version: 0.10.4.0-1 Severity: serious X-Debbugs-Cc: sramac...@debian.org libghc-swish-doc is currently not installable. $ apt install libghc-swish-doc Reading package lists... Done Building dependency tree... Done Reading state information... Done Some packages could

Processed: affects 1058380

2023-12-15 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > affects 1058380 + src:ros2-ament-cmake-ros src:ros2-ament-index Bug #1058380 [python3-ament-flake8] python3-ament-flake8: incompatible with flake8 version 6 Bug #1058418 [python3-ament-flake8] python3-ament-flake8: incompatible with flake8

Bug#1058744: dateparser's autopkg tests fail on 32bit platforms

2023-12-15 Thread Matthias Klose
Package: src:dateparser Version: 1.2.0-1 Severity: serious Tags: sid trixie dateparser's autopkg tests fail on 32bit platforms: [...] 151s === FAILURES === 151s _ TestLocalTZOffset.test_timezone_offset_calculation_1

Bug#1057591: octave-vibes: FTBFS: fatal: caught signal Segmentation fault -- stopping myself...

2023-12-15 Thread Santiago Vila
El 13/12/23 a las 9:27, Rafael Laboissière escribió: i.e. you may rely on a writable $HOME if it's for a "good cause" (i.e. dh_auto_test). So, the simple question: Should this not be also implemented in dh_octave_check as well, which is what octave-vibes was using? Thanks for bringing this

Bug#1058678: blt: disable jpeg support

2023-12-15 Thread Adrian Bunk
On Fri, Dec 15, 2023 at 11:20:09AM +0100, Helmut Grohne wrote: >... > The resulting artifacts > still differed a lot from an unmodified build and in particular, the > _uuid.so and _nis.so module went missing. The former probably is due to > something from tk or blt issuing a dependency on uuid-dev

Bug#1058743: libuv1: FTBFS on s390x on older kernels

2023-12-15 Thread Simon Chopin
Package: libuv1 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 noble ubuntu-patch X-Debbugs-Cc: scho...@ubuntu.com Hi! If the buildd is using an older kernel version,

Bug#1058521: marked as done (libhinoko: FTBFS: make: *** [debian/rules:8: binary] Error 25)

2023-12-15 Thread Debian Bug Tracking System
Your message dated Fri, 15 Dec 2023 11:50:50 + with message-id and subject line Bug#1058521: fixed in libhinoko 1.0.1-1 has caused the Debian Bug report #1058521, regarding libhinoko: FTBFS: make: *** [debian/rules:8: binary] Error 25 to be marked as done. This means that you claim that the

Bug#1058678: blt: disable jpeg support

2023-12-15 Thread Adrian Bunk
On Thu, Dec 14, 2023 at 06:22:45PM +0300, Sergei Golovan wrote: >... > Can someone investigate if blt is really necessary for Python now? > It's a very old > unmaintained piece of software, and I think that dependence of Python on it > should be a bug. >... The src:python3.x packages build

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

2023-12-15 Thread Debian Bug Tracking System
Your message dated Fri, 15 Dec 2023 11:36:45 + with message-id and subject line Bug#1058360: fixed in specreduce 1.3.0-2 has caused the Debian Bug report #1058360, regarding specreduce: FTBFS: dh_auto_test: error: pybuild --test --test-pytest -i python{version} -p "3.12 3.11" returned exit

Bug#1056583: kaidan: FTBFS with disabled network

2023-12-15 Thread Gianfranco Costamagna
control: tags -1 patch https://patches.ubuntu.com/k/kaidan/kaidan_0.9.1-2ubuntu1.patch this patch might do the trick. +Description: Disable test requiring internet access +Author: Gianfranco Costamagna +Bug-Debian: https://bugs.debian.org/1056583 +Last-Update: 2023-11-23 + +---

Processed: Re: kaidan: FTBFS with disabled network

2023-12-15 Thread Debian Bug Tracking System
Processing control commands: > tags -1 patch Bug #1056583 [src:kaidan] kaidan: FTBFS with disabled network Bug #1058510 [src:kaidan] kaidan: FTBFS: dh_auto_test: error: cd obj-x86_64-linux-gnu && make -j8 test ARGS\+=--verbose ARGS\+=-j8 returned exit code 2 Added tag(s) patch. Added tag(s)

Bug#1058196: marked as done (swift-bench: FTBFS: AttributeError: 'TestUtils' object has no attribute 'assertEquals'. Did you mean: 'assertEqual'?)

2023-12-15 Thread Debian Bug Tracking System
Your message dated Fri, 15 Dec 2023 11:21:01 + with message-id and subject line Bug#1058196: fixed in swift-bench 1.2.0-7 has caused the Debian Bug report #1058196, regarding swift-bench: FTBFS: AttributeError: 'TestUtils' object has no attribute 'assertEquals'. Did you mean: 'assertEqual'?

Bug#1058739: lyskom-elisp-client: fails to install with Emacs 29: lyskom-elisp-client.el:17452:2: Error: Optimizer error: too much on the stack

2023-12-15 Thread Andreas Beckmann
Package: lyskom-elisp-client Version: 0.48+git.20200923.ec349ff4-3 Severity: serious Tags: sid trixie User: debian...@lists.debian.org Usertags: piuparts Hi, during a test with piuparts I noticed your package failed to install. As per definition of the release team this makes the package too

Processed: Bug#1058196 marked as pending in swift-bench

2023-12-15 Thread Debian Bug Tracking System
Processing control commands: > tag -1 pending Bug #1058196 [src:swift-bench] swift-bench: FTBFS: AttributeError: 'TestUtils' object has no attribute 'assertEquals'. Did you mean: 'assertEqual'? Added tag(s) pending. -- 1058196: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1058196 Debian

Bug#1058196: marked as pending in swift-bench

2023-12-15 Thread Philippe Seraphin
Control: tag -1 pending Hello, Bug #1058196 in swift-bench 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#1058678: blt: disable jpeg support

2023-12-15 Thread Helmut Grohne
Hi Sergei, On Thu, Dec 14, 2023 at 06:22:45PM +0300, Sergei Golovan wrote: > I'm sorry, I wasn't aware about these implications. Meanwhile, I'm > setting this bug > severity to serious and will fix it as soon as possible. Thank you. I agree that this is surprising at times. Hence, I'm looking

Bug#1058252: marked as done (pynn: FTBFS: AttributeError: 'SpaceTest' object has no attribute 'assert_'. Did you mean: 'assertIn'?)

2023-12-15 Thread Debian Bug Tracking System
Your message dated Fri, 15 Dec 2023 10:35:18 + with message-id and subject line Bug#1058252: fixed in pynn 0.10.1-3 has caused the Debian Bug report #1058252, regarding pynn: FTBFS: AttributeError: 'SpaceTest' object has no attribute 'assert_'. Did you mean: 'assertIn'? to be marked as done.

Bug#1058678: marked as done (blt: disable jpeg support)

2023-12-15 Thread Debian Bug Tracking System
Your message dated Fri, 15 Dec 2023 10:34:13 + with message-id and subject line Bug#1058678: fixed in blt 2.5.3+dfsg-7 has caused the Debian Bug report #1058678, regarding blt: disable jpeg support to be marked as done. This means that you claim that the problem has been dealt with. If this

Processed: Bug#1058323 marked as pending in python-magnumclient

2023-12-15 Thread Debian Bug Tracking System
Processing control commands: > tag -1 pending Bug #1058323 [src:python-magnumclient] python-magnumclient: FTBFS: TypeError: HTTPSConnection.__init__() got an unexpected keyword argument 'key_file' Added tag(s) pending. -- 1058323: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1058323

Bug#1058323: marked as pending in python-magnumclient

2023-12-15 Thread Thomas Goirand
Control: tag -1 pending Hello, Bug #1058323 in python-magnumclient 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#1058252: marked as pending in pynn

2023-12-15 Thread Étienne Mollier
Control: tag -1 pending Hello, Bug #1058252 in pynn 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#1058252 marked as pending in pynn

2023-12-15 Thread Debian Bug Tracking System
Processing control commands: > tag -1 pending Bug #1058252 [src:pynn] pynn: FTBFS: AttributeError: 'SpaceTest' object has no attribute 'assert_'. Did you mean: 'assertIn'? Ignoring request to alter tags of bug #1058252 to the same tags previously set -- 1058252:

Processed: Bug#1058252 marked as pending in pynn

2023-12-15 Thread Debian Bug Tracking System
Processing control commands: > tag -1 pending Bug #1058252 [src:pynn] pynn: FTBFS: AttributeError: 'SpaceTest' object has no attribute 'assert_'. Did you mean: 'assertIn'? Added tag(s) pending. -- 1058252: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1058252 Debian Bug Tracking System

Bug#1058252: marked as pending in pynn

2023-12-15 Thread Étienne Mollier
Control: tag -1 pending Hello, Bug #1058252 in pynn 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 (with 2 errors): Re: Bug#1058281: octave-ncarray: FTBFS: make: *** [debian/rules:5: binary] Error 139

2023-12-15 Thread Debian Bug Tracking System
Processing control commands: > blocked -1 by 1058621 Unknown command or malformed arguments to command. > merge -1 1057590 Bug #1058281 [src:octave-netcdf] octave-ncarray: FTBFS: make: *** [debian/rules:5: binary] Error 139 Unable to merge bugs because: blockedby of #1057589 is '1058621' not ''

Bug#1058281: octave-ncarray: FTBFS: make: *** [debian/rules:5: binary] Error 139

2023-12-15 Thread Rafael Laboissière
Control: blocked -1 by 1058621 Control: merge -1 1057590 I hope that the merge goes well this time. Best, Rafael Laboissière

Bug#1055692: marked as done (macs ftbfs with Python 3.12)

2023-12-15 Thread Debian Bug Tracking System
Your message dated Fri, 15 Dec 2023 08:55:06 -0100 with message-id and subject line macs ftbfs with Python 3.12 has caused the Debian Bug report #1055692, regarding macs ftbfs with Python 3.12 to be marked as done. This means that you claim that the problem has been dealt with. If this is not

Processed: Re: astroquery: FTBFS: ModuleNotFoundError: No module named 'imp'

2023-12-15 Thread Debian Bug Tracking System
Processing control commands: > tags -1 fixed-upstream Bug #1057543 [src:astroquery] astroquery: FTBFS: ModuleNotFoundError: No module named 'imp' Added tag(s) fixed-upstream. -- 1057543: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1057543 Debian Bug Tracking System Contact

Bug#1057543: astroquery: FTBFS: ModuleNotFoundError: No module named 'imp'

2023-12-15 Thread Ole Streicher
Control: tags -1 fixed-upstream The problem here is that the python3-astropy-helpers package is not ready for Python 3.12, see #1058104. https://bugs.debian.org/1058104 Astropy-helpers is EOL upstream, therefore I think we should no longer rely on that package. For astroquery, there is a

Bug#1058698: mozilla-devscripts should be removed from testing/unstable

2023-12-15 Thread Carsten Schoenert
Hello Mechtilde, Am Thu, Dec 14, 2023 at 07:09:16PM +0100 schrieb Mechtilde: > Hello Mathias, > > thanks for the hint, > > At this time mozilla-devscript is needed when you want to build > Mozilla-AddOns from the *.xpi. > > So we need to elaborate another way to do it. I've dropped

Bug#1058150: marked as done (sixer: FTBFS: AssertionError: '/<>/sixer.py:44[104 chars]")\n' != '')

2023-12-15 Thread Debian Bug Tracking System
Your message dated Fri, 15 Dec 2023 09:20:02 + with message-id and subject line Bug#1058150: fixed in sixer 1.6-5 has caused the Debian Bug report #1058150, regarding sixer: FTBFS: AssertionError: '/<>/sixer.py:44[104 chars]")\n' != '' to be marked as done. This means that you claim that

Processed: Bug #1055697: forwarded to upstream commit that fix the FTBFS

2023-12-15 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > forwarded 1055697 > https://github.com/coin3d/pivy/commit/d3faf04b8770c60ca9b2186059ee82201e3620ad Bug #1055697 [src:pivy] pivy ftbfs with Python 3.12 Set Bug forwarded-to-address to

Processed: 1058441 is forwarded

2023-12-15 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > forwarded 1058441 https://github.com/python-openxml/python-docx/issues/1300 Bug #1058441 [src:python-docx] python-docx: FTBFS: dh_auto_test: error: pybuild --test --test-pytest -i python{version} -p "3.12 3.11" returned exit code 13 Set Bug