Bug#1061655: marked as done (wine: FTBFS with error: unknown conversion type character ‘I’ in format [-Werror=format=])
Your message dated Sat, 10 Feb 2024 07:29:28 +
with message-id
and subject line Bug#1061655: fixed in wine 9.0~repack-3
has caused the Debian Bug report #1061655,
regarding wine: FTBFS with error: unknown conversion type character ‘I’ in
format [-Werror=format=]
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 responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)
--
1061655: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1061655
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: wine
Version: 9.0~repack-2
Severity: serious
The source package fail to build on armel and armhf with the following error.
programs/winedbg/info.c:356:27: error: unknown conversion type character ‘I’ in
format [-Werror=format=]
356 | dbg_printf("'0x%0*I64lld' is not a valid module address\n",
ADDRWIDTH, base);
| ^
programs/winedbg/info.c:356:20: error: too many arguments for format
[-Werror=format-extra-args]
356 | dbg_printf("'0x%0*I64lld' is not a valid module address\n",
ADDRWIDTH, base);
|^~~
The build failures are available from
https://buildd.debian.org/status/package.php?p=wine >.
The issue seem to have been introduced in an upstream commit 2021-10-12:
commit 3a869c1f9ba8a35eb0781fc5cb0b6684a9a7960b
Author: Eric Pouech
Date: Tue Oct 12 18:10:58 2021 +0200
winedbg: Simplify some printing of addresses.
Signed-off-by: Eric Pouech
Signed-off-by: Alexandre Julliard
diff --git a/programs/winedbg/info.c b/programs/winedbg/info.c
index dc0e6591f1f..477438d83e3 100644
--- a/programs/winedbg/info.c
+++ b/programs/winedbg/info.c
@@ -284,7 +284,7 @@ void info_win32_module(DWORD64 base)
HeapFree(GetProcessHeap(), 0, im.modules);
if (base && !num_printed)
-dbg_printf("'0x%x%08x' is not a valid module address\n", (DWORD)(base
>> 32), (DWORD)b
ase);
+dbg_printf("'0x%0*I64x' is not a valid module address\n", ADDRWIDTH,
base);
}
struct class_walker
I do not understand the printf() notation well enough to understand what
is wrong. According to printf(3) in glibc 2.36, the I flag was added in
glibc 2.2. Could it be a compiler error, that the compiler do not
understand this "new" flag?
--
Happy hacking
Petter Reinholdtsen
--- End Message ---
--- Begin Message ---
Source: wine
Source-Version: 9.0~repack-3
Done: Michael Gilbert
We believe that the bug you reported is fixed in the latest version of
wine, which is due to be installed in the Debian FTP archive.
A summary of the changes between this version and the previous one is
attached.
Thank you for reporting the bug, which will now be closed. If you
have further comments please address them to 1061...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Michael Gilbert (supplier of updated wine package)
(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Format: 1.8
Date: Sat, 10 Feb 2024 02:12:06 +
Source: wine
Architecture: source
Version: 9.0~repack-3
Distribution: unstable
Urgency: medium
Maintainer: Debian Wine Party
Changed-By: Michael Gilbert
Closes: 1061655
Changes:
wine (9.0~repack-3) unstable; urgency=medium
.
* Update git branch.
* Support building with vulkan 1.3.275.
* Fix incorrect handling of WRITECOPY memory protection.
* Fix build failures on armel and armhf (closes: #1061655).
Checksums-Sha1:
dc37ba50919199353c2de56b679ea268a66bf462 4382 wine_9.0~repack-3.dsc
c50c4719d60126c54991f3fff80228b20a8fe4a0 58743668
wine_9.0~repack-3.debian.tar.xz
f69236e2f728135a994f1eaaff0b5e0ea24e4573 20589
wine_9.0~repack-3_source.buildinfo
Checksums-Sha256:
b191ea99dd2517c1434a23e3116aa1f8add2c2018eb65a4b1c024fbfe27bad14 4382
wine_9.0~repack-3.dsc
d223f910e2c32b2e1139e2742ec000d1454436c1072379aceeb3d7013e0bc619 58743668
wine_9.0~repack-3.debian.tar.xz
10b5a4a74cd56920e2bec4d419b25a3223c843645e0cef44ff3f130bb49f555a 20589
wine_9.0~repack-3_source.buildinfo
Files:
2e57135f46861587fe1c370ad20de95d 4382 otherosfs optional wine_9.0~repack-3.dsc
55f9c354f84f94caf36a60f9aa18834a 58743668 otherosfs optional
wine_9.0~repack-3.debian.tar.xz
e66019549bfb3418dc63749fb3ae4a45 20589 otherosfs optional
wine_9.0~repack-3_source.buildinfo
-BEGIN PGP SIGNATURE-
iQQzBAEBCgAdFiEEIwTlZiOEpzUxIyp4mD40ZYkUaygFAmXHCI4ACgkQmD40ZYkU
Processed: Re: openvswitch: CVE-2023-3966: Invalid memory access in Geneve with HW offload
Processing control commands: > tags -1 fixed-upstream Bug #1063492 [src:openvswitch] openvswitch: CVE-2023-3966: Invalid memory access in Geneve with HW offload Added tag(s) fixed-upstream. -- 1063492: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1063492 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1063492: openvswitch: CVE-2023-3966: Invalid memory access in Geneve with HW offload
Control: tags -1 fixed-upstream According to this announcment [1], CVE-2023-3966 and CVE-2023-5366 are fixed with versions Latest stable: https://www.openvswitch.org/releases/openvswitch-3.2.2.tar.gz Current LTS series: https://www.openvswitch.org/releases/openvswitch-2.17.9.tar.gz Other: https://www.openvswitch.org/releases/openvswitch-3.1.4.tar.gz https://www.openvswitch.org/releases/openvswitch-3.0.6.tar.gz [1] https://mail.openvswitch.org/pipermail/ovs-announce/2024-February/000338.html As sid has currently a git snapshot, it is not clear to me if that has been fixed there too. On Thu, 08 Feb 2024 22:35:46 +0100 Salvatore Bonaccorso wrote: > Source: openvswitch > Version: 3.3.0~git20240118.e802fe7-3 > Severity: important > Tags: security upstream > X-Debbugs-Cc: car...@debian.org, Debian Security Team > Control: found -1 3.1.0-2 > > Hi, > > The following vulnerability was published for openvswitch. > > CVE-2023-3966[0]: > | Invalid memory access in Geneve with HW offload > > > If you fix the vulnerability please also make sure to include the > CVE (Common Vulnerabilities & Exposures) id in your changelog entry. > > For further information see: > > [0] https://security-tracker.debian.org/tracker/CVE-2023-3966 > https://www.cve.org/CVERecord?id=CVE-2023-3966 > [1] https://www.openwall.com/lists/oss-security/2024/02/08/3 > [2] https://mail.openvswitch.org/pipermail/ovs-dev/2024-February/411702.html > > Please adjust the affected versions in the BTS as needed. > > Regards, > Salvatore > >
Bug#1061791: marked as done (comitup fails its autopkg tests with Python 3.12)
Your message dated Sat, 10 Feb 2024 05:50:48 +
with message-id
and subject line Bug#1061791: fixed in comitup 1.39-1
has caused the Debian Bug report #1061791,
regarding comitup fails its autopkg tests 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 the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)
--
1061791: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1061791
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:comitup
Version: 1.38-2
Severity: important
Tags: sid trixie ftbfs
User: debian-pyt...@lists.debian.org
Usertags: python3.12
With python3-defaults from experimental, the package fails its autopkg
tests:
[...]
503s = test session starts
==
503s platform linux -- Python 3.12.1, pytest-7.4.4, pluggy-1.3.0
503s rootdir: /tmp/autopkgtest.MuWHxO/build.zsl/src
503s configfile: pytest.ini
503s collected 65 items
503s
503s test/test_config.py .
[ 26%]
503s test/test_persist.py ..
[ 47%]
503s test/test_web.py ..
[ 75%]
503s test/test_webmgr.py .FF.
[100%]
503s
503s === FAILURES
===
503s test_webmgr_callback[-HOTSPOT-pass--]
_
503s
503s stop_svc =
503s start_svc = ,
svc = ''
503s state = 'HOTSPOT', action = 'pass'
503s fn_fact = at 0x76ae0bcc23e0>
503s arg_fact = at 0x76ae0bcc2480>, websvc_fxt = None
503s
503s @pytest.mark.parametrize(
503s "state, action, fn_fact, arg_fact",
503s (
503s (
503s "HOTSPOT",
503s "start",
503s lambda: webmgr.stop_service,
503s lambda: webmgr.web_service,
503s ), # noqa
503s (
503s "HOTSPOT",
503s "pass",
503s lambda: webmgr.start_service,
503s lambda: webmgr.COMITUP_SERVICE,
503s ), # noqa
503s (
503s "CONNECTING",
503s "start",
503s lambda: webmgr.stop_service,
503s lambda: webmgr.COMITUP_SERVICE,
503s ), # noqa
503s (
503s "CONNECTED",
503s "start",
503s lambda: webmgr.start_service,
503s lambda: webmgr.web_service,
503s ), # noqa
503s ),
503s ) # noqa
503s @pytest.mark.parametrize("svc", ("", "foo"))
503s @patch("comitup.webmgr.start_service")
503s @patch("comitup.webmgr.stop_service")
503s def test_webmgr_callback(
503s stop_svc, start_svc, svc, state, action, fn_fact, arg_fact,
websvc_fxt
503s ):
503s webmgr.web_service = svc
503s webmgr.state_callback(state, action)
503s
503s if arg_fact():
503s assert fn_fact().called
503s > assert fn_fact().called_with(call(arg_fact()))
503s
503s test/test_webmgr.py:62:
503s _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
_ _ _ _ _ _
503s
503s self =
503s name = 'called_with'
503s
503s def __getattr__(self, name):
503s if name in {'_mock_methods', '_mock_unsafe'}:
503s raise AttributeError(name)
503s elif self._mock_methods is not None:
503s if name not in self._mock_methods or name in _all_magics:
503s raise AttributeError("Mock object has no attribute
%r" % name)
503s elif _is_magic(name):
503s raise AttributeError(name)
503s if not self._mock_unsafe and (not self._mock_methods or
name not in self._mock_methods):
503s if name.startswith(('assert', 'assret', 'asert',
'aseert', 'assrt')) or name in _ATTRIB_DENY_LIST:
503s > raise AttributeError(
503s f"{name!r} is not a valid assertion. Use a spec "
503s f"for the mock if {name!r} is meant to be an
attribute.")
503s E AttributeError: 'called_with' is not a valid
assertion. Use a spec for the mock if 'called_with' is meant to be an
attribute.
503s
503s /usr/lib/python3/dist-packages/mock/mock.py:695: AttributeError
503s __
test_webmgr_callback[-CONNECTING-start--] ___
503s
503s stop_svc =
503s start_svc = ,
svc = ''
503s state = 'CONNECTING', action = 'start'
503s fn_fact = at 0x76ae0bcc2520>
503s arg_fact = at 0x76ae0bcc25c0>, websvc_fxt = None
503s
503s @pytest.mark.parametrize(
503s "state, action, fn_fact, arg_fact",
503s (
503s (
503s
Bug#1062596: libqt5qxlsx: NMU diff for 64-bit time_t transition
The latest stable version of QtXlxs is 1.4.6 and prepelease of 1.4.7 is published now. Probably updating to latest stable may be important. — WBW, Alex
Bug#1040375: /usr/lib/x86_64-linux-gnu/simplescreenrecorder/libssr-glinject.so: Segmentation fault when used with anything
I had a look upstream, and found two issues that seem to be about this crash bug: https://github.com/MaartenBaert/ssr/issues/992 and https://github.com/MaartenBaert/ssr/issues/1013 . The latter have some patch proposals. If the latest upstream git edition work, could the fix be the change descrived as "Switch to PLT hooks to make GLInject work with new dlopen/dlsym in libc" in https://github.com/MaartenBaert/ssr/commit/83b8f9f5d9c9ab06152657e57f85b6f71954a6b9 >? I do not use ssr much myself, and have not had time to test. -- Happy hacking Petter Reinholdtsen
Processed: Re: valgrind: Segmentation fault on armhf checking programs built with -fstack-clash-protection or -fstack-check
Processing control commands: > affects -1 + libvorbis-dev Bug #1061496 [valgrind] valgrind: Segmentation fault on armhf checking programs built with -fstack-clash-protection or -fstack-check Added indication that 1061496 affects libvorbis-dev > block 1061501 by -1 Bug #1061501 [src:libvorbis] libvorbis: Please disable test-coupling-segfault autopkgtest on armhf 1061501 was not blocked by any bugs. 1061501 was not blocking any bugs. Added blocking bug(s) of 1061501: 1061496 -- 1061496: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1061496 1061501: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1061501 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: ipyparallel: Patch to fix failing unit test
Processing control commands: > tags -1 patch Bug #1061744 [src:ipyparallel] ipyparallel ftbfs with Python 3.12 as default Added tag(s) patch. -- 1061744: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1061744 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1061744: ipyparallel: Patch to fix failing unit test
Package: ipyparallel
Followup-For: Bug #1061744
User: ubuntu-de...@lists.ubuntu.com
Usertags: origin-ubuntu noble ubuntu-patch
X-Debbugs-Cc: chris.peter...@canonical.com
Control: tags -1 patch
Dear Maintainer,
In Ubuntu, the attached patch was applied to achieve the following:
* Fix tests for python3.12 (LP: #2052727)
Python3.12 added checks for mock methods prefixed with `called_` since
assert mock.called_once()
was a common mistake.
Thanks for considering the patch.
- Chris
diff -Nru
ipyparallel-7.1.0/debian/patches/python3-assert-called-once-with.patch
ipyparallel-7.1.0/debian/patches/python3-assert-called-once-with.patch
--- ipyparallel-7.1.0/debian/patches/python3-assert-called-once-with.patch
1969-12-31 16:00:00.0 -0800
+++ ipyparallel-7.1.0/debian/patches/python3-assert-called-once-with.patch
2024-02-08 10:44:16.0 -0800
@@ -0,0 +1,24 @@
+Description: Fix bad test assert for python3.12
+ Python3.12 includes a check for the common mistake of:
+assert mocked_object.called_once_with(params)
+ and now raises an attribute error instead of erroneously passing the test.
+ The correct assertion method is `assert_called_once_with`. See:
+ https://github.com/python/cpython/issues/100690
+ for more information.
+Author: Chris Peterson
+Bug-Ubuntu: https://bugs.launchpad.net/ubuntu/+source/ipyparallel/+bug/2052727
+Bug-Debian: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1061744
+Last-Update: 2024-02-08
+---
+This patch header follows DEP-3: http://dep.debian.net/deps/dep3/
+--- a/ipyparallel/tests/test_util.py
b/ipyparallel/tests/test_util.py
+@@ -14,7 +14,7 @@
+ assert util.disambiguate_ip_address('0.0.0.0', socket.gethostname()) ==
localhost()
+ wontresolve = 'this.wontresolve.dns'
+ assert util.disambiguate_ip_address('0.0.0.0', wontresolve) == wontresolve
+-assert warn_mock.called_once_with(
++warn_mock.assert_called_once_with(
+ 'IPython could not determine IPs for {}: '
+ '[Errno -2] Name or service not known'.format(wontresolve),
+ RuntimeWarning,
diff -Nru ipyparallel-7.1.0/debian/patches/series
ipyparallel-7.1.0/debian/patches/series
--- ipyparallel-7.1.0/debian/patches/series 2023-02-10 00:19:19.0
-0800
+++ ipyparallel-7.1.0/debian/patches/series 2024-02-08 10:42:39.0
-0800
@@ -5,3 +5,4 @@
fix_docs
fix_setuptools_import.patch
0007-generate-code-reducer-from-CodeType-signature.patch
+python3-assert-called-once-with.patch
Processed: 389-ds-base: Build flags for 32bit architectures
Processing control commands:
> tags -1 patch
Bug #1063434 {Done: Paul Gevers } [src:389-ds-base]
src:389-ds-base: fails to migrate to testing for too long: FTBFS on 32 bits
Added tag(s) patch.
--
1063434: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1063434
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Bug#1063434: 389-ds-base: Build flags for 32bit architectures
Package: 389-ds-base Version: 2.4.4+dfsg1-1 Followup-For: Bug #1063434 User: ubuntu-de...@lists.ubuntu.com Usertags: origin-ubuntu noble ubuntu-patch X-Debbugs-Cc: chris.peter...@canonical.com Control: tags -1 patch Dear Maintainer, I see this has been marked for autoremoval, but I have recently introduced a patch in Ubuntu which fixed builds for armhf. Please see the attached for a functionally similar patch that should enable builds on your 32bit architectures (armhf, armel, and i386). I can provide armhf autopkgtest results shortly. Thanks, Chris diff -Nru 389-ds-base-2.4.4+dfsg1/debian/rules 389-ds-base-2.4.4+dfsg1/debian/rules --- 389-ds-base-2.4.4+dfsg1/debian/rules2024-01-08 07:40:49.0 -0800 +++ 389-ds-base-2.4.4+dfsg1/debian/rules2024-02-08 16:26:51.0 -0800 @@ -7,6 +7,9 @@ ifneq (,$(filter $(DEB_HOST_ARCH), armel m68k mips mipsel powerpc powerpcspe sh4)) export DEB_LDFLAGS_MAINT_APPEND=-latomic endif +ifneq (,$(filter $(DEB_HOST_ARCH), armhf armel i386)) + export DEB_CFLAGS_MAINT_APPEND=-D_LARGEFILE64_SOURCE +endif REALFILE = \ bin/ds-logpipe.py \
Bug#1063632: spirv-llvm-translator-17 FTBFS: error: ‘CapabilityLongConstantCompositeINTEL’ was not declared in this scope
Source: spirv-llvm-translator-17 Version: 17.0.0-3 Severity: serious Tags: ftbfs Forwarded: https://github.com/KhronosGroup/SPIRV-LLVM-Translator/issues/2261 https://buildd.debian.org/status/logs.php?pkg=spirv-llvm-translator-17=17.0.0-3%2Bb1 ... In file included from /<>/lib/SPIRV/libSPIRV/SPIRVModule.h:44, from /<>/lib/SPIRV/LLVMToSPIRVDbgTran.h:42, from /<>/lib/SPIRV/LLVMToSPIRVDbgTran.cpp:38: /<>/lib/SPIRV/libSPIRV/SPIRVEntry.h: In member function ‘SPIRV::SPIRVCapVec SPIRV::SPIRVContinuedInstINTELBase::getRequiredCapability() const’: /<>/lib/SPIRV/libSPIRV/SPIRVEntry.h:911:19: error: ‘CapabilityLongConstantCompositeINTEL’ was not declared in this scope 911 | return getVec(CapabilityLongConstantCompositeINTEL); | ^~~~ ...
Bug#1061761: marked as done (snakemake ftbfs with Python 3.12 as default)
Your message dated Sat, 10 Feb 2024 01:14:50 + with message-id and subject line Bug#1061761: fixed in snakemake 7.32.4-2 has caused the Debian Bug report #1061761, regarding snakemake ftbfs with Python 3.12 as default 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 responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 1061761: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1061761 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: src:snakemake Version: 7.32.4-1 Severity: serious Tags: sid trixie ftbfs User: debian-pyt...@lists.debian.org Usertags: python3.12 With python3-defaults from experimental, the package fails to build: see https://launchpadlibrarian.net/711666054/buildlog_ubuntu-noble-amd64.snakemake_7.32.4-1_BUILDING.txt.gz for the complete build log. [...] --- End Message --- --- Begin Message --- Source: snakemake Source-Version: 7.32.4-2 Done: Rebecca N. Palmer We believe that the bug you reported is fixed in the latest version of snakemake, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 1061...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Rebecca N. Palmer (supplier of updated snakemake package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Fri, 09 Feb 2024 19:11:23 + Source: snakemake Architecture: source Version: 7.32.4-2 Distribution: unstable Urgency: medium Maintainer: Debian Med Packaging Team Changed-By: Rebecca N. Palmer Closes: 1061761 Changes: snakemake (7.32.4-2) unstable; urgency=medium . * Tests: don't mix tabs and spaces, as Python 3.12 rejects this. * Adapt to f-strings being tokenized in Python 3.12. (together, Closes: #1061761) Checksums-Sha1: fc9688c52848086ca6276097adf60e44f2c80654 3509 snakemake_7.32.4-2.dsc a39c97a969cc5db3c87671e7714afed5322d3661 26880 snakemake_7.32.4-2.debian.tar.xz b7f618486453216416a10893a84ab52b95c751c0 8114 snakemake_7.32.4-2_source.buildinfo Checksums-Sha256: 1a81745aca7f0f305663ec6057e55613147c83354dc938c48f453fdd35f9de0f 3509 snakemake_7.32.4-2.dsc 2642674db078a6ef52fcb53501cf19409e75aff09405964b1b511b9aef07456f 26880 snakemake_7.32.4-2.debian.tar.xz 6443f48ee372d55edf9e7623b6ed64d84acb2f2363a945f5a611a772ede785e6 8114 snakemake_7.32.4-2_source.buildinfo Files: 023a955d8b346c487d2e2dfcfbbdc4bc 3509 science optional snakemake_7.32.4-2.dsc c396143d62438a2ff44733ceeb5dd153 26880 science optional snakemake_7.32.4-2.debian.tar.xz 71f1ce0eedd9d43353faabb726eb4f0f 8114 science optional snakemake_7.32.4-2_source.buildinfo -BEGIN PGP SIGNATURE- iQJMBAEBCgA2FiEEZ8sxEAXE7b4yF1MI3uUNDVZ+omYFAmXGq7MYHHJlYmVjY2Ff cGFsbWVyQHpvaG8uY29tAAoJEN7lDQ1WfqJmgoQP/2MfVS/khctDfCCiYSd0dmBu caH23X3CqNsVXVziN+picMSvoNBULj2iz7BvnwGq4+PLXmuaUCngIfE/nDitFIj0 jGLLH33mfJzY2+gNUju3WHMbsKbGaigz+7qHu4sKqL1VPOLk9jB02oNbOA/yXrAQ dvPJ9Q010BRWbKc0a5GWVDAwLpNQEHfhZ445e7PJCT2w1E/XXreJ8hcJy+jXV6Sq eNv6kidctQyvrWIh7AdK2saWKpnPDH48ck+oV6aE2XF/YZZFDU5UZrSnkwT6/uZ1 kUKzkTTQIFNzOQyaJCvQhGZSDHhYqrbROsrxlLvv3Nk0O4K3GmuK0YeKb711KTbI HKDT9NHRfmvXiiZAhJbeYDZ/ryOiew3M7NHb3qfCMWwCBLBiovpipgTLgeyYpzXx bF+aPCocgldicM07313MFBAavpKeZ4+xFspAh/LpxHcugaDxt/RcIUJ3ieugD7HH ZRbMs/+Wv3AHTEQY1RgQYKtD2qMhETGrdEwBU3/FUnE2cgbgJLuI3NAonG45pZ0q S+Yw2LI+M5yL967iameUHoxyE3peULxJ1TBQC+R+KlemYNL0z9sGMTpvGgfzwi+K mwBb3DtqVUPZsnfHQpzmrBZh8WRfukduG3sVWxK0hd2fMKCenYAAiPmHIy+MDKdy iqTmpr1L+eMpw7yU9ZnY =Ml8N -END PGP SIGNATURE End Message ---
Bug#1063631: hkl FTBFS with libcglm-dev 0.9.2-1
Source: hkl Version: 5.0.0.3381-1 Severity: serious Tags: ftbfs patch Forwarded: https://repo.or.cz/hkl.git/commit/c3badf0779a70f1666ccf8241d144ebb01897a0e https://buildd.debian.org/status/logs.php?pkg=hkl=5.0.0.3381-1%2Bb1 ... hkl-binoculars-geometry.c: In function ‘hkl_binoculars_parameter_transformation_get’: hkl-binoculars-geometry.c:45:45: error: incompatible type for argument 1 of ‘glms_rotate_atm’ 45 | r = glms_rotate_atm(m, pivot, angle, axis); | ^ | | | mat4s ...
Bug#1063499: marked as done (rust-gobject-sys FTBFS with nocheck build profile: cp: cannot stat '/usr/share/gir-1.0/GObject-2.0.gir': No such file or directory)
Your message dated Sat, 10 Feb 2024 00:25:49 +0100 with message-id <547b0cc2-5e12-4ea0-8c36-f7e5ceb28...@riseup.net> and subject line Re: rust-gobject-sys FTBFS with nocheck build profile: cp: cannot stat '/usr/share/gir-1.0/GObject-2.0.gir': No such file or directory has caused the Debian Bug report #1063499, regarding rust-gobject-sys FTBFS with nocheck build profile: cp: cannot stat '/usr/share/gir-1.0/GObject-2.0.gir': No such file or directory 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 responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 1063499: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1063499 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: rust-gobject-sys Version: 0.18.0-2 Severity: serious Tags: ftbfs trixie sid rust-gobject-sys fails to build from source in unstable when built with the nocheck build profile. Since trixie, a nocheck build failure is considered release-critical. A build ends with: |debian/rules execute_before_dh_auto_build | make[1]: Entering directory '/<>' | cp /usr/share/gir-1.0/GObject-2.0.gir /<> | cp: cannot stat '/usr/share/gir-1.0/GObject-2.0.gir': No such file or directory | make[1]: *** [debian/rules:8: execute_before_dh_auto_build] Error 1 | make[1]: Leaving directory '/<>' | make: *** [debian/rules:3: binary] Error 2 | dpkg-buildpackage: error: debian/rules binary subprocess returned exit status 2 Please review the annotations. Helmut --- End Message --- --- Begin Message --- Version: 0.19.0-2 -- Matthias Geiger Debian Maintainer "Freiheit ist immer Freiheit des anders Denkenden" -- Rosa Luxemburg OpenPGP_0x18BD106B3B6C5475.asc Description: OpenPGP public key OpenPGP_signature.asc Description: OpenPGP digital signature --- End Message ---
Bug#1052735: marked as done (ruby-delayed-job-active-record: FTBFS: ERROR: Test "ruby3.1" failed: ArgumentError:)
Your message dated Fri, 09 Feb 2024 22:55:34 + with message-id and subject line Bug#1052735: fixed in ruby-delayed-job-active-record 4.1.8-1 has caused the Debian Bug report #1052735, regarding ruby-delayed-job-active-record: FTBFS: ERROR: Test "ruby3.1" failed: ArgumentError: 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 responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 1052735: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1052735 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: ruby-delayed-job-active-record Version: 4.1.6-3.1 Severity: serious Justification: FTBFS Tags: trixie sid ftbfs User: lu...@debian.org Usertags: ftbfs-20230925 ftbfs-trixie Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > ArgumentError: >Invalid Timezone: US/Eastern > Shared Example Group: "a delayed_job backend" called from > ./spec/delayed/backend/active_record_spec.rb:7 > # > /usr/share/rubygems-integration/all/gems/activesupport-6.1.7.3/lib/active_support/core_ext/time/zones.rb:100:in > `rescue in find_zone!' > # > /usr/share/rubygems-integration/all/gems/activesupport-6.1.7.3/lib/active_support/core_ext/time/zones.rb:82:in > `find_zone!' > # > /usr/share/rubygems-integration/all/gems/activesupport-6.1.7.3/lib/active_support/core_ext/time/zones.rb:42:in > `zone=' > # > /usr/share/rubygems-integration/all/gems/delayed_job-4.1.9/lib/delayed/backend/shared_spec.rb:233:in > `block (3 levels) in ' > # -- > # --- Caused by: --- > # TZInfo::InvalidTimezoneIdentifier: > # Invalid identifier: US/Eastern > # > /usr/share/rubygems-integration/all/gems/tzinfo-2.0.6/lib/tzinfo/data_source.rb:321:in > `validate_timezone_identifier' > > Finished in 0.11955 seconds (files took 0.64496 seconds to load) > 34 examples, 1 failure > > Failed examples: > > rspec './spec/delayed/backend/active_record_spec.rb[1:1:7:4]' # > Delayed::Backend::ActiveRecord::Job behaves like a delayed_job backend > reserve reserves jobs scheduled for the past when time zones are involved > > /usr/bin/ruby3.1 > -I/usr/share/rubygems-integration/all/gems/rspec-support-3.12.0/lib:/usr/share/rubygems-integration/all/gems/rspec-core-3.12.0/lib > /usr/share/rubygems-integration/all/gems/rspec-core-3.12.0/exe/rspec > --pattern ./spec/\*\*/\*_spec.rb --format documentation failed > ERROR: Test "ruby3.1" failed: The full build log is available from: http://qa-logs.debian.net/2023/09/25/ruby-delayed-job-active-record_4.1.6-3.1_unstable.log All bugs filed during this archive rebuild are listed at: https://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=ftbfs-20230925;users=lu...@debian.org or: https://udd.debian.org/bugs/?release=na=ign=7=7=only=ftbfs-20230925=lu...@debian.org=1=1=1=1#results A list of current common problems and possible solutions is available at http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute! If you reassign this bug to another package, please mark it as 'affects'-ing this package. See https://www.debian.org/Bugs/server-control#affects If you fail to reproduce this, please provide a build log and diff it with mine so that we can identify if something relevant changed in the meantime. --- End Message --- --- Begin Message --- Source: ruby-delayed-job-active-record Source-Version: 4.1.8-1 Done: Pirate Praveen We believe that the bug you reported is fixed in the latest version of ruby-delayed-job-active-record, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 1052...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Pirate Praveen (supplier of updated ruby-delayed-job-active-record package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Sat, 10 Feb 2024 01:30:38 +0530 Source: ruby-delayed-job-active-record Architecture: source Version: 4.1.8-1 Distribution: unstable Urgency: medium Maintainer: Debian Ruby Team Changed-By: Pirate Praveen Closes: 1052735 Changes: ruby-delayed-job-active-record (4.1.8-1) unstable; urgency=medium . * Team upload. * New upstream version *
Bug#1063363: marked as done (nvidia-graphics-drivers: autopkgtest needs update for new version of linux)
Your message dated Fri, 09 Feb 2024 22:54:17 + with message-id and subject line Bug#1063363: fixed in nvidia-graphics-drivers 525.147.05-6 has caused the Debian Bug report #1063363, regarding nvidia-graphics-drivers: autopkgtest needs update for new version of linux 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 responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 1063363: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1063363 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: nvidia-graphics-drivers Version: 525.147.05-5 Severity: serious X-Debbugs-CC: li...@packages.debian.org Tags: sid trixie User: debian...@lists.debian.org Usertags: needs-update Control: affects -1 src:linux Dear maintainer(s), With a recent upload of linux the autopkgtest of nvidia-graphics-drivers fails in testing when that autopkgtest is run with the binary packages of linux from unstable. It passes when run with only packages from testing. In tabular form: passfail linux from testing6.6.15-2 nvidia-graphics-drivers from testing525.147.05-5 all others from testingfrom testing I copied some of the output at the bottom of this report. Currently this regression is blocking the migration of linux to testing [1]. Of course, linux shouldn't just break your autopkgtest (or even worse, your package), but it seems to me that the change in linux was intended and your package needs to update to the new situation. If this is a real problem in your package (and not only in your autopkgtest), the right binary package(s) from linux should really add a versioned Breaks on the unfixed version of (one of your) package(s). Note: the Breaks is nice even if the issue is only in the autopkgtest as it helps the migration software to figure out the right versions to combine in the tests. More information about this bug and the reason for filing it can be found on https://wiki.debian.org/ContinuousIntegration/RegressionEmailInformation Paul [1] https://qa.debian.org/excuses.php?package=linux https://ci.debian.net/data/autopkgtest/testing/amd64/n/nvidia-graphics-drivers/42760274/log.gz 810s # MODPOST /usr/src/modules/nvidia-kernel/Module.symvers 810sscripts/mod/modpost -M -m -o /usr/src/modules/nvidia-kernel/Module.symvers -T /usr/src/modules/nvidia-kernel/modules.order -i Module.symvers -e 811s ERROR: modpost: GPL-incompatible module nvidia.ko uses GPL-only symbol '__rcu_read_unlock' 811s ERROR: modpost: GPL-incompatible module nvidia.ko uses GPL-only symbol '__rcu_read_lock' 811s make[6]: *** [/usr/src/linux-headers-6.6.15-common/scripts/Makefile.modpost:145: /usr/src/modules/nvidia-kernel/Module.symvers] Error 1 811s make[5]: *** [/usr/src/linux-headers-6.6.15-common/Makefile:1890: modpost] Error 2 811s make[4]: *** [/usr/src/linux-headers-6.6.15-common/Makefile:246: __sub-make] Error 2 811s make[4]: Leaving directory '/usr/src/linux-headers-6.6.15-cloud-amd64' 811s make[3]: *** [Makefile:246: __sub-make] Error 2 811s make[3]: Leaving directory '/usr/src/linux-headers-6.6.15-common' 811s make[2]: *** [Makefile:82: modules] Error 2 811s make[2]: Leaving directory '/usr/src/modules/nvidia-kernel' 811s make[1]: *** [debian/rules:39: binary-modules] Error 2 811s make[1]: Leaving directory '/usr/src/modules/nvidia-kernel' 811s make: *** [/usr/share/modass/include/common-rules.make:56: kdist_build] Error 2 811s tput: No value for $TERM and no -T specified 811s BUILD FAILED! 811s tput: No value for $TERM and no -T specified 811s See /var/cache/modass/nvidia-kernel-source.buildlog.6.6.15-cloud-amd64.1707198843 for details. 811s Build failed. Press Return to continue... 811s I: nvidia-kernel does not support the 6.6.15-rt-amd64 kernel (!CONFIG_PREEMPT_RT) 811s I: Summary: 811s I: FAIL nvidia-kernel 6.6.15-amd64 (7) 811s I: FAIL nvidia-kernel 6.6.15-cloud-amd64 (7) 811s I: SKIP nvidia-kernel 6.6.15-rt-amd64 (!CONFIG_PREEMPT_RT) 811s autopkgtest [05:58:24]: test m-a-autopkgtest OpenPGP_signature.asc Description: OpenPGP digital signature --- End Message --- --- Begin Message --- Source: nvidia-graphics-drivers Source-Version: 525.147.05-6 Done: Andreas Beckmann We believe that the bug you reported is fixed in the latest version of nvidia-graphics-drivers, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 1063...@bugs.debian.org, and the maintainer will
Bug#1063617: sogo FTBFS on little endian
Source: sogo Version: 5.9.0-1 Severity: serious Tags: ftbfs https://buildd.debian.org/status/logs.php?pkg=sogo=5.9.0-1 https://buildd.debian.org/status/logs.php?pkg=sogo=5.9.1-1 ... == FAIL: test_recurrenceRangesWithinCalendarDateRange_ (TestiCalRecurrenceCalculator.m:381) -- Invalid occurrence for recurrence rule FREQ=YEARLY;UNTIL=2131T09Z;BYMONTH=1;BYDAY=SU,MO,TU,WE,TH,FR,SA: Fri 1999-01-01 09:00 (expected date was Sat 1998-01-31 09:00) == FAIL: test_NGInternetSocketAddressFromString (TestNGNetUtlilities.m:86) -- isIpv4 mismatch. Expected: '1', result: '0'. Test url: 'localhost:1001' == FAIL: test_generateDataForHeaderFieldNamed_value_ (TestNGMimeAddressHeaderFieldGenerator.m:78) -- received 'wolfg...@test.com, wolfg...@test.com' instead of '"" ' for '"" ' -- Ran 38 tests FAILED (3 failures, 0 errors) hash = $argon2id$v=19$m=65536,t=2,p=1$H1BrOTIX9XOi2WuD7zx+pw$Vvik3l21HkuRr5LhnJz0RBq35hxI8woG51F/gEuUt78 make[3]: *** [GNUmakefile:63: check] Error 1 debian/rules ignores test failures on big endian
Bug#1063498: marked as done (rust-glib-sys FTBFS with the nocheck build profile: cp: cannot stat '/usr/share/gir-1.0/GLib-2.0.gir': No such file or directory)
Your message dated Fri, 9 Feb 2024 21:52:52 +0100 with message-id <20240209205252.ga3097...@subdivi.de> and subject line Re: rust-glib-sys FTBFS with the nocheck build profile: cp: cannot stat '/usr/share/gir-1.0/GLib-2.0.gir': No such file or directory has caused the Debian Bug report #1063498, regarding rust-glib-sys FTBFS with the nocheck build profile: cp: cannot stat '/usr/share/gir-1.0/GLib-2.0.gir': No such file or directory 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 responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 1063498: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1063498 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: rust-glib-sys Version: 0.18.1-2 Severity: serious Tags: ftbfs trixie sid rust-glib-sys fails to build from source in unstable when built with the nocheck build profile. Since trixie, a nocheck failure is considered release-critical. A build ends with: |debian/rules execute_before_dh_auto_build | make[1]: Entering directory '/<>' | cp /usr/share/gir-1.0/GLib-2.0.gir /<> | cp: cannot stat '/usr/share/gir-1.0/GLib-2.0.gir': No such file or directory | make[1]: *** [debian/rules:9: execute_before_dh_auto_build] Error 1 | make[1]: Leaving directory '/<>' | make: *** [debian/rules:4: binary] Error 2 | dpkg-buildpackage: error: debian/rules binary subprocess returned exit status 2 Helmut --- End Message --- --- Begin Message --- Version: 0.19.0-1 On Fri, Feb 09, 2024 at 09:41:22PM +0100, Matthias Geiger wrote: > the version in experimental already contains the fix for this. I hope to > subsequently upload all of gtk-rs to experimental this weekend and then to > unstable soon after. Cool. In that case, just close the bug with the experimental version. We have version tracking and that tells that the bug still affects unstable. If you upload another 0.18.* to unstable, you should reclose the bug. Helmut--- End Message ---
Bug#1063498: rust-glib-sys FTBFS with the nocheck build profile: cp: cannot stat '/usr/share/gir-1.0/GLib-2.0.gir': No such file or directory
On Thu, 8 Feb 2024 15:20:53 +0100 Helmut Grohne wrote: > Source: rust-glib-sys > Version: 0.18.1-2 > Severity: serious > Tags: ftbfs trixie sid > > rust-glib-sys fails to build from source in unstable when built with the > nocheck build profile. Since trixie, a nocheck failure is considered > release-critical. A build ends with: > > | debian/rules execute_before_dh_auto_build > | make[1]: Entering directory '/<>' > | cp /usr/share/gir-1.0/GLib-2.0.gir /<> > | cp: cannot stat '/usr/share/gir-1.0/GLib-2.0.gir': No such file or directory > | make[1]: *** [debian/rules:9: execute_before_dh_auto_build] Error 1 > | make[1]: Leaving directory '/<>' > | make: *** [debian/rules:4: binary] Error 2 > | dpkg-buildpackage: error: debian/rules binary subprocess returned exit status 2 > > Helmut Control: tags +1 patch Hi Helmut, the version in experimental already contains the fix for this. I hope to subsequently upload all of gtk-rs to experimental this weekend and then to unstable soon after. Actually some other gtk-rs packages are also affected; this will be remedied. best, -- Matthias Geiger Debian Maintainer "Freiheit ist immer Freiheit des anders Denkenden" -- Rosa Luxemburg OpenPGP_0x18BD106B3B6C5475.asc Description: OpenPGP public key OpenPGP_signature.asc Description: OpenPGP digital signature
Bug#1063609: texstudio_4.7.2+ds-1_all-buildd.changes REJECTED
Source: texstudio Version: 4.7.2+ds-1 Severity: serious On 2024-02-07 17:06, Debian FTP Masters wrote: > > texstudio-doc_4.7.2+ds-1_all.deb: Built-Using refers to non-existing source > package python3-pygments (= 2.17.2+dfsg-1) > > > Mapping sid to unstable. > > === > > Please feel free to respond to this email if you don't understand why > your files were rejected, or if you upload new files which address our > concerns. > > >
Bug#1063607: igraph: FTBFS on i386: test::igraph_hrg (Failed)
Source: igraph Version: 0.10.9+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=igraph=i386=0.10.9%2Bds-1=1707132840=0 526: Test timeout computed to be: 1500 521/554 Test #508: test::igraph_hrg ...***Failed0.20 sec -- Test case output differs from the expected output -- See diff below: -- --- --- /<>/tests/unit/igraph_hrg.out 2024-02-04 21:40:29.0 + +++ /<>/_BUILD_STATIC/tests/test_igraph_hrg.out2024-02-05 11:14:47.195150846 + @@ -1,24 +1,24 @@ -Vertex # 25, left: # 29, right: # 43, prob: 0.0067 -Vertex # 26, left: # 13, right: # 46, prob: 1 -Vertex # 27, left: # 14, right: # 19, prob: 1 -Vertex # 28, left: # 15, right: # 16, prob: 0 -Vertex # 29, left: # 28, right: # 41, prob: 0.23 -Vertex # 30, left: # 33, right: # 37, prob: 0.13 -Vertex # 31, left: # 8, right: # 34, prob: 1 -Vertex # 32, left: # 23, right: # 24, prob: 0 -Vertex # 33, left: # 22, right: # 27, prob: 0 -Vertex # 34, left: # 7, right: # 44, prob: 1 -Vertex # 35, left: # 17, right: # 39, prob:0.1 -Vertex # 36, left: # 12, right: # 20, prob: 0 -Vertex # 37, left: # 26, right: # 36, prob: 0 -Vertex # 38, left: # 42, right: # 45, prob: 1 -Vertex # 39, left: # 21, right: # 48, prob: 0 -Vertex # 40, left: # 2, right: # 5, prob: 1 -Vertex # 41, left: # 32, right: # 35, prob: 0 -Vertex # 42, left: # 4, right: # 31, prob: 1 -Vertex # 43, left: # 0, right: # 47, prob: 1 -Vertex # 44, left: # 6, right: # 9, prob: 1 -Vertex # 45, left: # 1, right: # 40, prob: 1 -Vertex # 46, left: # 11, right: # 18, prob: 0 -Vertex # 47, left: # 3, right: # 38, prob: 1 -Vertex # 48, left: # 10, right: # 30, prob: 0.25 +Vertex # 25, left: # 33, right: # 36, prob: 0.029 +Vertex # 26, left: # 19, right: # 20, prob: 0 +Vertex # 27, left: # 14, right: # 26, prob: 1 +Vertex # 28, left: # 10, right: # 37, prob: 0.15 +Vertex # 29, left: # 21, right: # 30, prob: 0 +Vertex # 30, left: # 18, right: # 35, prob: 0 +Vertex # 31, left: # 1, right: # 42, prob: 1 +Vertex # 32, left: # 16, right: # 41, prob: 1 +Vertex # 33, left: # 32, right: # 39, prob: 0 +Vertex # 34, left: # 0, right: # 45, prob: 1 +Vertex # 35, left: # 11, right: # 17, prob: 0 +Vertex # 36, left: # 27, right: # 28, prob: 0 +Vertex # 37, left: # 43, right: # 48, prob: 0 +Vertex # 38, left: # 6, right: # 9, prob: 1 +Vertex # 39, left: # 13, right: # 29, prob: 0.75 +Vertex # 40, left: # 5, right: # 44, prob: 1 +Vertex # 41, left: # 23, right: # 24, prob: 0 +Vertex # 42, left: # 40, right: # 47, prob: 1 +Vertex # 43, left: # 3, right: # 31, prob: 1 +Vertex # 44, left: # 8, right: # 34, prob: 1 +Vertex # 45, left: # 2, right: # 4, prob: 1 +Vertex # 46, left: # 12, right: # 22, prob: 0 +Vertex # 47, left: # 7, right: # 38, prob: 1 +Vertex # 48, left: # 15, right: # 46, prob: 1 -- --- CMake Error at /<>/etc/cmake/run_legacy_test.cmake:67 (message): Exiting test. Cheers -- Sebastian Ramacher
Bug#1063604: nng: FTBFS on i396, ppc64el, s390x
Source: nng Version: 1.7.2-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=nng=i386=1.7.2-1=1707038234=0 The following tests FAILED: 14 - nng.sp.protocol.bus0.bus_test (Failed) 35 - nng.supplemental.tls_test (Failed) 50 - nng.compat.compat.nanomsg.compat_tcp_test (Timeout) 53 - nng.httpserver (Failed) 57 - nng.multistress (Subprocess aborted) 64 - nng.tls (Failed) 65 - nng.tcpsupp (Failed) 66 - nng.tcp (Failed) 69 - nng.ws (Failed) 72 - nng.reqstress (Subprocess aborted) 77 - nng.compat_msg (Subprocess aborted) 85 - nng.compat_reqttl (Subprocess aborted) 87 - nng.compat_surveyttl (Subprocess aborted) Errors while running CTest make[2]: *** [Makefile:94: test] Error 8 https://buildd.debian.org/status/fetch.php?pkg=nng=ppc64el=1.7.2-1=1707038154=0 The following tests FAILED: 14 - nng.sp.protocol.bus0.bus_test (Failed) 35 - nng.supplemental.tls_test (Failed) 50 - nng.compat.compat.nanomsg.compat_tcp_test (Timeout) 53 - nng.httpserver (Failed) 57 - nng.multistress (Subprocess aborted) 64 - nng.tls (Failed) 65 - nng.tcpsupp (Failed) 66 - nng.tcp (Failed) 69 - nng.ws (Failed) 72 - nng.reqstress (Subprocess aborted) 77 - nng.compat_msg (Subprocess aborted) 85 - nng.compat_reqttl (Subprocess aborted) 87 - nng.compat_surveyttl (Subprocess aborted) Errors while running CTest make[2]: *** [Makefile:94: test] Error 8 https://buildd.debian.org/status/fetch.php?pkg=nng=s390x=1.7.2-1=1707052223=0 The following tests FAILED: 67 - nng.tcp6 (Failed) Errors while running CTest make[2]: *** [Makefile:94: test] Error 8 Cheers -- Sebastian Ramacher
Processed: severity of 1057562 is serious
Processing commands for cont...@bugs.debian.org: > severity 1057562 serious Bug #1057562 [src:gcr4] gcr4: FTBFS: failing tests Severity set to 'serious' from 'important' > thanks Stopping processing here. Please contact me if you need assistance. -- 1057562: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1057562 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1063603: composer: CVE-2024-24821
Source: composer Version: 2.6.6-1 Severity: grave Tags: security upstream Justification: user security hole X-Debbugs-Cc: car...@debian.org, Debian Security Team Hi, The following vulnerability was published for composer. CVE-2024-24821[0]: | Composer is a dependency Manager for the PHP language. In affected | versions several files within the local working directory are | included during the invocation of Composer and in the context of the | executing user. As such, under certain conditions arbitrary code | execution may lead to local privilege escalation, provide lateral | user movement or malicious code execution when Composer is invoked | within a directory with tampered files. All Composer CLI commands | are affected, including composer.phar's self-update. The following | scenarios are of high risk: Composer being run with sudo, Pipelines | which may execute Composer on untrusted projects, Shared | environments with developers who run Composer individually on the | same project. This vulnerability has been addressed in versions | 2.7.0 and 2.2.23. It is advised that the patched versions are | applied at the earliest convenience. Where not possible, the | following should be addressed: Remove all sudo composer privileges | for all users to mitigate root privilege escalation, and avoid | running Composer within an untrusted directory, or if needed, verify | that the contents of `vendor/composer/InstalledVersions.php` and | `vendor/composer/installed.php` do not include untrusted code. A | reset can also be done on these files by the following:```sh rm | vendor/composer/installed.php vendor/composer/InstalledVersions.php | composer install --no-scripts --no-plugins ``` If you fix the vulnerability please also make sure to include the CVE (Common Vulnerabilities & Exposures) id in your changelog entry. For further information see: [0] https://security-tracker.debian.org/tracker/CVE-2024-24821 https://www.cve.org/CVERecord?id=CVE-2024-24821 [1] https://github.com/composer/composer/security/advisories/GHSA-7c6p-848j-wh5h [2] https://github.com/composer/composer/commit/64e4eb356b159a30c766cd1ea83450a38dc23bf5 Please adjust the affected versions in the BTS as needed. Regards, Salvatore
Bug#1063602: seqan-needle: FTBFS on amd64: test/api/insert_delete_test (Failed)
Source: seqan-needle Version: 1.0.2+ds-2 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=seqan-needle=amd64=1.0.2%2Bds-2=1707394988=0 2: [ RUN ] insert.ibfmin 2: unknown file: Failure 2: C++ exception with description "std::bad_alloc" thrown in the test body. 2: 2: [ FAILED ] insert.ibfmin (0 ms) [...] 2: [ FAILED ] 1 test, listed below: 2: [ FAILED ] insert.ibfmin 2: 2: 1 FAILED TEST 2/13 Test #2: test/api/insert_delete_test ...***Failed0.03 sec Cheers -- Sebastian Ramacher
Bug#1063601: tailspin: FTBFS: error[E0407]: method `backtrace` is not a member of trait `Error`
Source: tailspin
Version: 3.0.0+dfsg-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=tailspin=amd64=3.0.0%2Bdfsg-1=1706195420=0
Running
`/<>/target/release/build/eyre-15058028a1ebd405/build-script-build`
[eyre 0.6.8] error[E0407]: method `backtrace` is not a member of trait `Error`
[eyre 0.6.8] -->
/<>/target/x86_64-unknown-linux-gnu/release/build/eyre-eb1eb971e427fb49/out/probe.rs:19:9
[eyre 0.6.8]|
[eyre 0.6.8] 19 | / fn backtrace() -> Option<> {
[eyre 0.6.8] 20 | | let backtrace = Backtrace::capture();
[eyre 0.6.8] 21 | | match backtrace.status() {
[eyre 0.6.8] 22 | | BacktraceStatus::Captured |
BacktraceStatus::Disabled | _ => {}
[eyre 0.6.8] 23 | | }
[eyre 0.6.8] 24 | | unimplemented!()
[eyre 0.6.8] 25 | | }
[eyre 0.6.8]| |_^ not a member of trait `Error`
[eyre 0.6.8]
[eyre 0.6.8] error[E0554]: `#![feature]` may not be used on the stable release
channel
[eyre 0.6.8] -->
/<>/target/x86_64-unknown-linux-gnu/release/build/eyre-eb1eb971e427fb49/out/probe.rs:2:16
[eyre 0.6.8] |
[eyre 0.6.8] 2 | #![feature(backtrace)]
[eyre 0.6.8] |^
[eyre 0.6.8]
[eyre 0.6.8] warning: the feature `backtrace` has been stable since 1.65.0 and
no longer requires an attribute to enable
[eyre 0.6.8] -->
/<>/target/x86_64-unknown-linux-gnu/release/build/eyre-eb1eb971e427fb49/out/probe.rs:2:16
[eyre 0.6.8] |
[eyre 0.6.8] 2 | #![feature(backtrace)]
[eyre 0.6.8] |^
[eyre 0.6.8] |
[eyre 0.6.8] = note: `#[warn(stable_features)]` on by default
[eyre 0.6.8]
[eyre 0.6.8] error: aborting due to 2 previous errors; 1 warning emitted
[eyre 0.6.8]
[eyre 0.6.8] Some errors have detailed explanations: E0407, E0554.
[eyre 0.6.8] For more information about an error, try `rustc --explain E0407`.
[eyre 0.6.8] cargo:rustc-cfg=track_caller
Cheers
--
Sebastian Ramacher
Bug#1063600: open3d: FTBFS: embree3/rtcore.h: No such file or directory
Source: open3d Version: 0.17.0+ds-9 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=open3d=amd64=0.17.0%2Bds-9%2Bb1=1705418499=0 [ 44%] Building CXX object cpp/open3d/t/geometry/CMakeFiles/tgeometry.dir/RaycastingScene.cpp.o cd /<>/obj-x86_64-linux-gnu/cpp/open3d/t/geometry && /usr/bin/c++ -DBUILD_GUI -DFMT_SHARED -DOPEN3D_CUDA_COMPILER_ID=\"\" -DOPEN3D_CUDA_COMPILER_VERSION=\"\" -DOPEN3D_CXX_COMPILER_ID=\"GNU\" -DOPEN3D_CXX_COMPILER_VERSION=\"13.2.0\" -DOPEN3D_CXX_STANDARD=\"17\" -DOPEN3D_ENABLE_DLL_EXPORTS -DUNIX -DUSE_BLAS -DZMQ_STATIC -D_FORTIFY_SOURCE=2 -D_GLIBCXX_USE_CXX11_ABI=1 -D__TBB_LIB_NAME=tbb_static -Dkiss_fft_scalar=double -I/<>/cpp -I/<> -isystem /<>/3rdparty/tomasakeninemoeller/include -isystem /<>/3rdparty/rply/rply -isystem /<>/3rdparty/tinyfiledialogs/include -isystem /usr/include/vtk-9.1 -isystem /usr/include/jsoncpp -isystem /usr/include/liblzf -isystem /usr/include/minizip -isystem /usr/include/imgui -isystem /usr/include/pgm-5.3 -isystem /usr/include/libxml2 -isystem /usr/include/mit-krb5 -isystem /usr/include/eigen3 -isystem /usr/include/filament-1.9 -g -O2 -ffile-prefix-map=/<>=. -fstack-protector-strong -fstack-clash-protection -Wformat -Werror=format-security -fcf-protection -faligned-new -Wno-psabi -Wdate-time -D_FORTIFY_SOURCE=2 -std=gnu++17 -fPIC -Wall -Wextra -Wno-unused-parameter -fstack-protector-strong -Wformat -Wformat-security -fopenmp -MD -MT cpp/open3d/t/geometry/CMakeFiles/tgeometry.dir/RaycastingScene.cpp.o -MF CMakeFiles/tgeometry.dir/RaycastingScene.cpp.o.d -o CMakeFiles/tgeometry.dir/RaycastingScene.cpp.o -c /<>/cpp/open3d/t/geometry/RaycastingScene.cpp /<>/cpp/open3d/t/geometry/RaycastingScene.cpp:15:10: fatal error: embree3/rtcore.h: No such file or directory 15 | #include | ^~ compilation terminated. make[3]: *** [cpp/open3d/t/geometry/CMakeFiles/tgeometry.dir/build.make:219: cpp/open3d/t/geometry/CMakeFiles/tgeometry.dir/RaycastingScene.cpp.o] Error 1 Cheers -- Sebastian Ramacher
Processed: tagging 1063044
Processing commands for cont...@bugs.debian.org: > tags 1063044 + ftbfs Bug #1063044 [src:vecgeom] vecgeom: FTBFS with embree 4.3.0+dfsg-2 in unstable Added tag(s) ftbfs. > thanks Stopping processing here. Please contact me if you need assistance. -- 1063044: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1063044 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1063599: mathgl: FTBFS on amd64: tests seg fault
Source: mathgl Version: 8.0.1-5 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=mathgl=amd64=8.0.1-5=1704780389=0 ape.png: ok tens.png: ok ternary.png: ok text.png: ok text2.png: ok textmark.png: ok ticks.png: ok tile.png: ok tiles.png: ok torus.png: ok traj.png: ok triangulation.png: ok triplot.png: ok tube.png: ok type0.png: ok type1.png: ok type2.png: ok vect.png: ok vect3.png: ok venn.png: ok Segmentation fault make[1]: *** [debian/rules:59: override_dh_auto_test] Error 139 make[1]: Leaving directory '/<>' Cheers -- Sebastian Ramacher
Bug#1063598: python-fastparquet: FTBFS: Python.h: No such file or directory
Source: python-fastparquet Version: 2023.10.1-2 Severity: serious Tags: ftbfs Justification: fails to build from source X-Debbugs-Cc: sramac...@debian.org https://buildd.debian.org/status/fetch.php?pkg=python-fastparquet=amd64=2023.10.1-2=1704222935=0 building 'fastparquet.speedups' extension creating build/temp.linux-x86_64-cpython-312 creating build/temp.linux-x86_64-cpython-312/fastparquet x86_64-linux-gnu-gcc -fno-strict-overflow -Wsign-compare -DNDEBUG -g -O2 -Wall -g -fstack-protector-strong -fstack-clash-protection -Wformat -Werror=format-security -fcf-protection -g -fwrapv -O2 -g -O2 -ffile-prefix-map=/<>=. -fstack-protector-strong -fstack-clash-protection -Wformat -Werror=format-security -fcf-protection -Wdate-time -D_FORTIFY_SOURCE=2 -fPIC -I/usr/include/python3.12 -I/usr/lib/python3/dist-packages/numpy/core/include -c fastparquet/speedups.c -o build/temp.linux-x86_64-cpython-312/fastparquet/speedups.o fastparquet/speedups.c:29:10: fatal error: Python.h: No such file or directory 29 | #include "Python.h" | ^~ compilation terminated. error: command '/usr/bin/x86_64-linux-gnu-gcc' failed with exit code 1 ERROR Backend subprocess exited when trying to invoke build_wheel Cheers -- Sebastian Ramacher
Processed: tagging 1056798
Processing commands for cont...@bugs.debian.org: > tags 1056798 + ftbfs Bug #1056798 [src:dioptas] dioptas: ftbfs with cython 3.0.x Added tag(s) ftbfs. > thanks Stopping processing here. Please contact me if you need assistance. -- 1056798: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1056798 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1063597: giac: FTBFS on amd64: tests seg fault
Source: giac Version: 1.9.0.69+dfsg2-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=giac=amd64=1.9.0.69%2Bdfsg2-1%2Bb1=1707503131=0 FAIL: chk_factor // Using locale /usr/share/locale/ // C.UTF-8 // /usr/share/locale/ // giac // UTF-8 // Maximum number of parallel threads 4 // Unable to find keyword file doc/en/keywords Added 0 synonyms // Time 0 // Time 0 // Time 0 // Time 0.01 // Time 0 // Time 0 // Time 0 // Time 0 // Time 0 // Time 0 // Time 0 // Time 0 // Time 0.01 // Time 0 // Time 0 // Time 0 // Time 0 // Time 0 // Time 0 // Time 0 // Time 0 // Time 0.01 // Time 0 // Time 0 // Time 0.01 // Time 0 // Time 0 // Time 0 Segmentation fault 28a29,32 > (5*x+11)*(8*x+1)*(12*x-13)*(15*x+8)*(30*x-31)*(120*x-209), > (x^20-x^15+x^10-x^5+1)*(x^20+x^15+x^10+x^5+1), > (x^2-x+1)*(x^2+x+1)*(x^8-x^7+x^5-x^4+x^3-x+1)*(x^8+x^7-x^5-x^4-x^3+x+1)*(x^40-x^35+x^25-x^20+x^15-x^5+1)*(x^40+x^35-x^25-x^20-x^15+x^5+1), > x^200-x^199+x^197-x^196+x^194-x^193+x^191-x^190+x^188-x^187+x^185-x^184+x^182-x^181+x^179-x^178+x^176-x^175+x^173-x^172+x^170-x^169+x^167-x^166+x^164-x^163+x^161-x^160+x^158-x^157+x^155-x^154+x^152-x^151+x^149-x^148+x^146-x^145+x^143-x^142+x^140-x^139+x^137-x^136+x^134-x^133+x^131-x^130+x^128-x^127+x^125-x^124+x^122-x^121+x^119-x^118+x^116-x^115+x^113-x^112+x^110-x^109+x^107-x^106+x^104-x^103+x^101-x^100+x^99-x^97+x^96-x^94+x^93-x^91+x^90-x^88+x^87-x^85+x^84-x^82+x^81-x^79+x^78-x^76+x^75-x^73+x^72-x^70+x^69-x^67+x^66-x^64+x^63-x^61+x^60-x^58+x^57-x^55+x^54-x^52+x^51-x^49+x^48-x^46+x^45-x^43+x^42-x^40+x^39-x^37+x^36-x^34+x^33-x^31+x^30-x^28+x^27-x^25+x^24-x^22+x^21-x^19+x^18-x^16+x^15-x^13+x^12-x^10+x^9-x^7+x^6-x^4+x^3-x+1 FAIL chk_factor (exit status: 1) Cheers -- Sebastian Ramacher
Bug#1063596: flint: FTBFS on amd64: test segfault
Source: flint Version: 3.0.1-3 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=flint=amd64=3.0.1-3=1707499549=0 powmod_x_fmpz_preinv...PASS randtest_irreduciblePASS scalar_addmul_fq... PASS scalar_div_fq... PASS scalar_mul_fq... PASS scalar_submul_fq... PASS set_fmpz_poly... PASS set_nmod_poly... PASS set_trunc... PASS PASS sqr... shift_left/right... PASS sqr_KS... PASS sqr_classical... PASS sqrt... PASS sqrt_seriesPASS sub... PASS sub_series... PASS xgcdPASS xgcd_euclidean_fPASS ctx_init_modulusPASS ctx_init_modulus_nmodPASS PASS make[2]: *** [Makefile:663: build/fq_default/test/t-ctx_init_modulus_nmod_TEST_RUN] Segmentation fault make[2]: *** Waiting for unfinished jobs PASS ctx_modulusPASS Cheers -- Sebastian Ramacher
Bug#1061659: marked as done (src:golang-github-hanwen-go-fuse: fails to migrate to testing for too long: i386 autopkgtest regression)
Your message dated Fri, 09 Feb 2024 19:45:43 + with message-id and subject line Bug#1061659: fixed in golang-github-hanwen-go-fuse 2.4.2-2 has caused the Debian Bug report #1061659, regarding src:golang-github-hanwen-go-fuse: fails to migrate to testing for too long: i386 autopkgtest regression 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 responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 1061659: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1061659 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: golang-github-hanwen-go-fuse Version: 2.1.0+git20220822.58a7e14-1 Severity: serious Control: close -1 2.4.2-1 Tags: sid trixie User: release.debian@packages.debian.org Usertags: out-of-sync Dear maintainer(s), 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:golang-github-hanwen-go-fuse has been trying to migrate for 31 days [2]. Hence, I am filing this bug. The version in unstable fails its own autopkgtest on i386. If a package is out of sync between unstable and testing for a longer period, this usually means that bugs in the package in testing cannot be fixed via unstable. Additionally, blocked packages can have impact on other packages, which makes preparing for the release more difficult. Finally, it often exposes issues with the package and/or its (reverse-)dependencies. We expect maintainers to fix issues that hamper the migration of their package in a timely manner. This bug will trigger auto-removal when appropriate. As with all new bugs, there will be at least 30 days before the package is auto-removed. I have immediately closed this bug with the version in unstable, so if that version or a later version migrates, this bug will no longer affect testing. I have also tagged this bug to only affect sid and trixie, so it doesn't affect (old-)stable. If you believe your package is unable to migrate to testing due to issues beyond your control, don't hesitate to contact the Release Team. Paul [1] https://lists.debian.org/debian-devel-announce/2023/06/msg1.html [2] https://qa.debian.org/excuses.php?package=golang-github-hanwen-go-fuse OpenPGP_signature.asc Description: OpenPGP digital signature --- End Message --- --- Begin Message --- Source: golang-github-hanwen-go-fuse Source-Version: 2.4.2-2 Done: Nilesh Patra We believe that the bug you reported is fixed in the latest version of golang-github-hanwen-go-fuse, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 1061...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Nilesh Patra (supplier of updated golang-github-hanwen-go-fuse package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Fri, 09 Feb 2024 23:30:50 +0530 Source: golang-github-hanwen-go-fuse Architecture: source Version: 2.4.2-2 Distribution: unstable Urgency: medium Maintainer: Debian Go Packaging Team Changed-By: Nilesh Patra Closes: 1061659 Changes: golang-github-hanwen-go-fuse (2.4.2-2) unstable; urgency=medium . * Team Upload. * Backport upstream patch to fix FTBFS on i386 (Closes: #1061659) Checksums-Sha1: aa3098dab56c0aad5590cd9db5c046f980ee4227 1714 golang-github-hanwen-go-fuse_2.4.2-2.dsc 0cc72adae9713b38b10eb2c300f558881219227e 5644 golang-github-hanwen-go-fuse_2.4.2-2.debian.tar.xz 38e450053d7e67df829ebeed81526fdbfd41 5655 golang-github-hanwen-go-fuse_2.4.2-2_amd64.buildinfo Checksums-Sha256: 76e5c22ef9ebc0a93b787d02885bcf63992d39d74124cde962a1c150b710a5a5 1714 golang-github-hanwen-go-fuse_2.4.2-2.dsc b43ce3cf7e0dc3ab6edccfb40bc6626d9e52c5ec1db4243e046c70f4d406904f 5644 golang-github-hanwen-go-fuse_2.4.2-2.debian.tar.xz 73d596d9dd262a53c2b7227e6cd4746e5d52ba3185d57c0ea82ccf6b99c1 5655 golang-github-hanwen-go-fuse_2.4.2-2_amd64.buildinfo Files: 0faca193092709cb8c3569430947267e 1714 golang optional golang-github-hanwen-go-fuse_2.4.2-2.dsc 02c341072244c675ff3b8c1def26b158 5644 golang optional golang-github-hanwen-go-fuse_2.4.2-2.debian.tar.xz 283db6f96b659e1c7274b2e42d069fb3 5655 golang optional
Processed: notfound 1062885 in 0.9.8-10, found 1062885 in 0.9.8-11
Processing commands for cont...@bugs.debian.org: > notfound 1062885 0.9.8-10 Bug #1062885 [src:mimetic] mimetic: NMU diff for 64-bit time_t transition No longer marked as found in versions mimetic/0.9.8-10. > # mark version in unstable and testing as affected, as was the original idea > found 1062885 0.9.8-11 Bug #1062885 [src:mimetic] mimetic: NMU diff for 64-bit time_t transition Marked as found in versions mimetic/0.9.8-11. > thanks Stopping processing here. Please contact me if you need assistance. -- 1062885: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1062885 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: 1061760
Processing commands for cont...@bugs.debian.org: > forwarded 1061760 https://github.com/SasView/sasview/issues/2806 Bug #1061760 [src:sasview] sasview ftbfs with Python 3.12 as default Set Bug forwarded-to-address to 'https://github.com/SasView/sasview/issues/2806'. > End of message, stopping processing here. Please contact me if you need assistance. -- 1061760: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1061760 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1058997: Patch is not sufficient (Was: flask-autoindex is incompatible with Py3.12)
Control: tags -1 - patch Hi Alexandre, I've applied your patch in Git but as you can see in Salsa CI[1] it is not sufficient to fix the build issue. Kind regards and thanks for your help anyway Andreas. [1] https://salsa.debian.org/python-team/packages/flask-autoindex/-/jobs/5272253 -- http://fam-tille.de
Processed: Patch is not sufficient (Was: flask-autoindex is incompatible with Py3.12)
Processing control commands: > tags -1 - patch Bug #1058997 [src:flask-autoindex] flask-autoindex is incompatible with Py3.12 Removed tag(s) patch. -- 1058997: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1058997 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: python-skbio: tests fail with scipy 1.11
Processing control commands: > block 1061605 by -1 Bug #1061605 [src:scipy] scipy: tests skipped during build and autopkgtest not in sync 1061605 was blocked by: 1063526 1063527 1061605 was not blocking any bugs. Added blocking bug(s) of 1061605: 1063584 -- 1061605: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1061605 1063584: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1063584 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1063273: marked as done (seaborn: autopkgtest fail on i386 - probable rounding error)
Your message dated Fri, 09 Feb 2024 17:29:01 + with message-id and subject line Bug#1063273: fixed in seaborn 0.13.2-2 has caused the Debian Bug report #1063273, regarding seaborn: autopkgtest fail on i386 - probable rounding error 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 responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 1063273: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1063273 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: python3-seaborn Version: 0.13.2-1 Severity: serious seaborn's autopkgtest failed on i386, with differences small enough that they are plausibly rounding error (i.e. should be ignored, by using *almost_equal instead of exact comparisons), but I haven't looked carefully. --- End Message --- --- Begin Message --- Source: seaborn Source-Version: 0.13.2-2 Done: Nilesh Patra We believe that the bug you reported is fixed in the latest version of seaborn, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 1063...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Nilesh Patra (supplier of updated seaborn package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Fri, 09 Feb 2024 22:22:55 +0530 Source: seaborn Architecture: source Version: 0.13.2-2 Distribution: unstable Urgency: medium Maintainer: Debian Science Maintainers Changed-By: Nilesh Patra Closes: 1063273 Changes: seaborn (0.13.2-2) unstable; urgency=medium . * Add patch to avoid test failures on 32-bit (Closes: #1063273) Checksums-Sha1: 7731e0c68678474291fdd38cc5f7c93f95d67c87 1726 seaborn_0.13.2-2.dsc bc0017496fed901ee040e48f38b37388ff9222ae 6012 seaborn_0.13.2-2.debian.tar.xz b7e4c083e060af268881d03261032140f73b1c97 10459 seaborn_0.13.2-2_amd64.buildinfo Checksums-Sha256: aaa30a40e68cb79050e7c0ad740b7a278b0b547c23eec64fc538030cc8857760 1726 seaborn_0.13.2-2.dsc d08478e8e072f3077c6879df4c9c7ba24189a511ff6a35032a2571837b3e6d2c 6012 seaborn_0.13.2-2.debian.tar.xz b0a7ba3e7a1d25a12aa8acb075a1c92b8ab651171150d529d24d654f97ca34b0 10459 seaborn_0.13.2-2_amd64.buildinfo Files: b6c06e6cb9490caf72f0454149cfc7e9 1726 python optional seaborn_0.13.2-2.dsc f50ac68eeb6eaf26eb4487567968b83e 6012 python optional seaborn_0.13.2-2.debian.tar.xz 72012b0d07edbd27412a4d9c5e5e83a1 10459 python optional seaborn_0.13.2-2_amd64.buildinfo -BEGIN PGP SIGNATURE- iHUEARYIAB0WIQSglbZu4JAkvuai8HIqJ5BL1yQ+2gUCZcZcrgAKCRAqJ5BL1yQ+ 2gNCAPwO8E2kpFgMQSWdFQP1M0SnvPJZnV73gpQMEWzeSil4AQD/WkHcfppfbEac YiDnUoEziTeWwetkjSb/AGALz4gorw8= =Sgku -END PGP SIGNATURE End Message ---
Bug#1059666: python-hug: autopkgtest failure with Python 3.12
Hi Federico, Am Thu, Feb 08, 2024 at 07:02:09PM +0100 schrieb Federico Ceratto: > Sure, go ahead, and thank you for taking care of the bug! Done.[1] Please note: I activated build-time testing and non-trivial autopkgtest. This involved some fixes for Python3.11, Python3.12 as well as numpy. I also marked tests accessing network skip. There were two remaining types of test failures I would like you to pay attention or point upstream to. This is documented in debian/README.source[2]. I have the feeling that also python-marshmallow would reside nicely in DPT but since there is no bug in this package I do not see any reason to act right now. Kind regards Andreas. [1] https://tracker.debian.org/news/1502390/accepted-python-hug-260-3-source-into-unstable/ [2] https://salsa.debian.org/python-team/packages/python-hug/-/blob/master/debian/README.source?ref_type=heads -- http://fam-tille.de
Processed: fix ftbfs bug metadata
Processing commands for cont...@bugs.debian.org: > # Reassign from binary to source > reassign 1013302 src:ntopng Bug #1013302 [ntopng] ntopng FTBFS /build/1st/ntopng-5.2.1+dfsg1/debian/missing-sources/gauge.coffee:179:3: error: Can't reference 'this' before calling super in derived class constructors Bug reassigned from package 'ntopng' to 'src:ntopng'. No longer marked as found in versions ntopng/5.2.1+dfsg1-1. Ignoring request to alter fixed versions of bug #1013302 to the same values previously set > # Restore versions after reassign > found 1013302 ntopng/5.2.1+dfsg1-1 Bug #1013302 [src:ntopng] ntopng FTBFS /build/1st/ntopng-5.2.1+dfsg1/debian/missing-sources/gauge.coffee:179:3: error: Can't reference 'this' before calling super in derived class constructors Marked as found in versions ntopng/5.2.1+dfsg1-1. > thanks Stopping processing here. Please contact me if you need assistance. -- 1013302: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1013302 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1063321: libwxgtk3.2-1t64 has an undeclared file conflict
On Fri, 9 Feb 2024, Scott Talbert wrote: On Tue, 6 Feb 2024, Helmut Grohne wrote: Package: libwxgtk3.2-1t64 Version: 3.2.4+dfsg-3.1~exp1 Severity: serious User: debian...@lists.debian.org Usertags: fileconflict Control: affects -1 + libwxgtk-gl3.2-1 libwxgtk-gl3.2-1t64 libwxgtk-media3.2-1 libwxgtk-media3.2-1t64 libwxgtk-webview3.2-1 libwxgtk-webview3.2-1t64 X-Debbugs-Cc: vor...@debian.org libwxgtk3.2-1t64 has an undeclared file conflict. This may result in an unpack error from dpkg. Hello Steve, Are you planning on fixing this, or would you like me to? If the latter, how would you like the fix submitted before this is uploaded to unstable? Sending to your vor...@dodds.net as your mail server rejected the mail sent through debian.org with some sort of SPF error. Probably something the debian server is doing? Scott
Bug#1052730: marked as done (ruby-delayed-job: FTBFS: ERROR: Test "ruby3.1" failed: ArgumentError:)
Your message dated Fri, 09 Feb 2024 16:20:46 +
with message-id
and subject line Bug#1052730: fixed in ruby-delayed-job 4.1.11-1
has caused the Debian Bug report #1052730,
regarding ruby-delayed-job: FTBFS: ERROR: Test "ruby3.1" failed: ArgumentError:
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 responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)
--
1052730: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1052730
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: ruby-delayed-job
Version: 4.1.9-1.1
Severity: serious
Justification: FTBFS
Tags: trixie sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20230925 ftbfs-trixie
Hi,
During a rebuild of all packages in sid, your package failed to build
on amd64.
Relevant part (hopefully):
> ArgumentError:
>Invalid Timezone: US/Eastern
> Shared Example Group: "a delayed_job backend" called from
> ./spec/test_backend_spec.rb:4
> #
> /usr/share/rubygems-integration/all/gems/activesupport-6.1.7.3/lib/active_support/core_ext/time/zones.rb:100:in
> `rescue in find_zone!'
> #
> /usr/share/rubygems-integration/all/gems/activesupport-6.1.7.3/lib/active_support/core_ext/time/zones.rb:82:in
> `find_zone!'
> #
> /usr/share/rubygems-integration/all/gems/activesupport-6.1.7.3/lib/active_support/core_ext/time/zones.rb:42:in
> `zone='
> # ./lib/delayed/backend/shared_spec.rb:233:in `block (3 levels) in (required)>'
> # --
> # --- Caused by: ---
> # TZInfo::InvalidTimezoneIdentifier:
> # Invalid identifier: US/Eastern
> #
> /usr/share/rubygems-integration/all/gems/tzinfo-2.0.6/lib/tzinfo/data_source.rb:321:in
> `validate_timezone_identifier'
>
> Deprecation Warnings:
>
> The implicit block expectation syntax is deprecated, you should pass a block
> rather than an argument to `expect` to use the provided block expectation
> matcher or the matcher must implement `supports_value_expectations?`. e.g
> `expect { value }.to raise Delayed::FatalBackendError` not `expect(value).to
> raise Delayed::FatalBackendError`
>
>
> If you need more of the backtrace for any of these deprecations to
> identify where to make the necessary changes, you can configure
> `config.raise_errors_for_deprecations!`, and it will turn the
> deprecation warnings into errors, giving you the full backtrace.
>
> 1 deprecation warning total
>
> Finished in 1.63 seconds (files took 1.28 seconds to load)
> 177 examples, 1 failure
>
> Failed examples:
>
> rspec './spec/test_backend_spec.rb[1:1:7:4]' # Delayed::Backend::Test::Job it
> should behave like a delayed_job backend reserve reserves jobs scheduled for
> the past when time zones are involved
>
> /usr/bin/ruby3.1
> -I/usr/share/rubygems-integration/all/gems/rspec-support-3.12.0/lib:/usr/share/rubygems-integration/all/gems/rspec-core-3.12.0/lib
> /usr/share/rubygems-integration/all/gems/rspec-core-3.12.0/exe/rspec
> --pattern ./spec/\*\*/\*_spec.rb --format documentation failed
> ERROR: Test "ruby3.1" failed:
The full build log is available from:
http://qa-logs.debian.net/2023/09/25/ruby-delayed-job_4.1.9-1.1_unstable.log
All bugs filed during this archive rebuild are listed at:
https://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=ftbfs-20230925;users=lu...@debian.org
or:
https://udd.debian.org/bugs/?release=na=ign=7=7=only=ftbfs-20230925=lu...@debian.org=1=1=1=1#results
A list of current common problems and possible solutions is available at
http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute!
If you reassign this bug to another package, please mark it as 'affects'-ing
this package. See https://www.debian.org/Bugs/server-control#affects
If you fail to reproduce this, please provide a build log and diff it with mine
so that we can identify if something relevant changed in the meantime.
--- End Message ---
--- Begin Message ---
Source: ruby-delayed-job
Source-Version: 4.1.11-1
Done: Pirate Praveen
We believe that the bug you reported is fixed in the latest version of
ruby-delayed-job, which is due to be installed in the Debian FTP archive.
A summary of the changes between this version and the previous one is
attached.
Thank you for reporting the bug, which will now be closed. If you
have further comments please address them to 1052...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Pirate Praveen (supplier of updated ruby-delayed-job
package)
(This message was generated automatically at their request; if you
believe that there is a problem with it please contact
Bug#1061737: marked as done (bookletimposer ftbfs with Python 3.12 as default)
Your message dated Fri, 09 Feb 2024 16:19:05 +
with message-id
and subject line Bug#1061737: fixed in bookletimposer 0.3.1-4
has caused the Debian Bug report #1061737,
regarding bookletimposer ftbfs with Python 3.12 as default
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 responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)
--
1061737: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1061737
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:bookletimposer
Version: 0.3.1-3
Severity: serious
Tags: sid trixie ftbfs
User: debian-pyt...@lists.debian.org
Usertags: python3.12
With python3-defaults from experimental, the package fails to build:
[...]
dpkg-buildpackage: info: host architecture amd64
debian/rules clean
dh clean --with python3 --buildsystem=pybuild
dh_auto_clean -O--buildsystem=pybuild
I: pybuild base:305: python3.11 setup.py clean
Traceback (most recent call last):
File "/<>/setup.py", line 73, in
class clean_man(distutils.command.clean.clean):
^^^
AttributeError: module 'distutils.command' has no attribute 'clean'
E: pybuild pybuild:391: clean: plugin distutils failed with: exit
code=1: python3.11 setup.py clean
dh_auto_clean: error: pybuild --clean -i python{version} -p "3.11 3.12"
returned exit code 13
make: *** [debian/rules:6: clean] Error 25
--- End Message ---
--- Begin Message ---
Source: bookletimposer
Source-Version: 0.3.1-4
Done: Andreas Tille
We believe that the bug you reported is fixed in the latest version of
bookletimposer, which is due to be installed in the Debian FTP archive.
A summary of the changes between this version and the previous one is
attached.
Thank you for reporting the bug, which will now be closed. If you
have further comments please address them to 1061...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Andreas Tille (supplier of updated bookletimposer package)
(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Format: 1.8
Date: Fri, 09 Feb 2024 16:56:19 +0100
Source: bookletimposer
Architecture: source
Version: 0.3.1-4
Distribution: unstable
Urgency: medium
Maintainer: Debian Python Team
Changed-By: Andreas Tille
Closes: 1043745 1049559 1054753 1061737 1061788 1061789
Changes:
bookletimposer (0.3.1-4) unstable; urgency=medium
.
* Team upload.
* Remove unneeded references to distutils
Closes: #1061789, #1061788, #1054753, #1061737
* Fix clean target
Closes: #1043745
* Fix building binary packages again after successful build
Closes: #1049559
* Standards-Version: 4.6.2 (routine-update)
* Build-Depends: s/dh-python/dh-sequence-python3/ (routine-update)
Checksums-Sha1:
6962e726312aa828906a4a0a90bc5b580099c3d5 2250 bookletimposer_0.3.1-4.dsc
7b21e8a679c32a0318e1b7bde75fe173bc8da97a 7500
bookletimposer_0.3.1-4.debian.tar.xz
63299e31ae0e919894399c40da043a989c693551 8162
bookletimposer_0.3.1-4_amd64.buildinfo
Checksums-Sha256:
643ef855fddea83811ad737696f8d83c387dd45003aba6f734a83222b381de89 2250
bookletimposer_0.3.1-4.dsc
300757ed73e4ac3022913dd7a69a7c3d1fec2f65d54223f61968835055cbedb3 7500
bookletimposer_0.3.1-4.debian.tar.xz
c28419968c8d719c132cea0143474da716f913a5e6096b532470f8e27990f03c 8162
bookletimposer_0.3.1-4_amd64.buildinfo
Files:
011fea52e942b7eca3cd4022755c9ec5 2250 python optional
bookletimposer_0.3.1-4.dsc
cfbe91bef5469daaf4514320836636c6 7500 python optional
bookletimposer_0.3.1-4.debian.tar.xz
aabbc1930c6c97be47cc9a2b583a2e7e 8162 python optional
bookletimposer_0.3.1-4_amd64.buildinfo
-BEGIN PGP SIGNATURE-
iQJFBAEBCgAvFiEE8fAHMgoDVUHwpmPKV4oElNHGRtEFAmXGTI8RHHRpbGxlQGRl
Ymlhbi5vcmcACgkQV4oElNHGRtG3iA//aqmPr2VYjDV4SWPJoEDG23D16fsOPuWd
rLQqbfG8ntVGzb6t2kj6+ZZF/Ly8nU1I3qU79tHAYHWYoo3S06W/VDwQ/kvwv0iV
2x9wuzta2j5rxZlMTu8AvC3WEcoIlb/CDEYem86xloXluxq3/fPdStCXLt/H49sb
f4kDlC2UNZq5L0xqm5LoXG1eDbd/IzHgPIMHKcvE6zC9ZyweB0/hA7N7c3xSEE7V
LrddDVH4W+/V8gSj2+cRMaeoboaiOHTotSd6zm+ExEdagVgcj3/yEoZXBUez1qlM
bKvyFbRadQ2yiKld0zLwODXDgWpsCCQRFSoBdq2AQ/3+2YcnjFJT2a7+BfD96LpE
cgHgpbDpn5DZ2KxgIDi1gDPDFnF8psqhBJq//3t5xAxsmEcX1H7niFr3nQhtkIbH
5IR1ops/W2LHrP7mmmweJxyQOhvqpGBh1JbEIr8558ks0BqIU+IQMy8HcpSWWcCA
xTdJ/Sb8P6+mwbkzCz/ilxncrKPZy+0ja/K3MTF261CpH+yUPKSKijYDQELQ1C4K
8uSw/t2kWC9gYlImq67HQlmR54NM05qjBlUHsMfsUowLV00Ck1UmSD/O+RLggi8E
oTnDW+kvJU+2ftU2HSrMEHaOaGrABV3ZxvDALVMERnyNq90jxMGMSI4UPzoa3U+s
Bug#1054753: marked as done (bookletimposer: FTBFS: AttributeError: module 'distutils.command' has no attribute 'clean')
Your message dated Fri, 09 Feb 2024 16:19:05 +
with message-id
and subject line Bug#1054753: fixed in bookletimposer 0.3.1-4
has caused the Debian Bug report #1054753,
regarding bookletimposer: FTBFS: AttributeError: module 'distutils.command' has
no attribute 'clean'
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 responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)
--
1054753: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1054753
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: bookletimposer
Version: 0.3.1-3
Severity: serious
Justification: FTBFS
Tags: trixie sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20231027 ftbfs-trixie
Hi,
During a rebuild of all packages in sid, your package failed to build
on amd64.
Relevant part (hopefully):
> debian/rules clean
> dh clean --with python3 --buildsystem=pybuild
>dh_auto_clean -O--buildsystem=pybuild
> I: pybuild base:310: python3.11 setup.py clean
> Traceback (most recent call last):
> File "/<>/setup.py", line 73, in
> class clean_man(distutils.command.clean.clean):
> ^^^
> AttributeError: module 'distutils.command' has no attribute 'clean'
> E: pybuild pybuild:395: clean: plugin distutils failed with: exit code=1:
> python3.11 setup.py clean
> dh_auto_clean: error: pybuild --clean -i python{version} -p 3.11 returned
> exit code 13
> make: *** [debian/rules:6: clean] Error 25
The full build log is available from:
http://qa-logs.debian.net/2023/10/27/bookletimposer_0.3.1-3_unstable.log
All bugs filed during this archive rebuild are listed at:
https://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=ftbfs-20231027;users=lu...@debian.org
or:
https://udd.debian.org/bugs/?release=na=ign=7=7=only=ftbfs-20231027=lu...@debian.org=1=1=1=1#results
A list of current common problems and possible solutions is available at
http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute!
If you reassign this bug to another package, please mark it as 'affects'-ing
this package. See https://www.debian.org/Bugs/server-control#affects
If you fail to reproduce this, please provide a build log and diff it with mine
so that we can identify if something relevant changed in the meantime.
--- End Message ---
--- Begin Message ---
Source: bookletimposer
Source-Version: 0.3.1-4
Done: Andreas Tille
We believe that the bug you reported is fixed in the latest version of
bookletimposer, which is due to be installed in the Debian FTP archive.
A summary of the changes between this version and the previous one is
attached.
Thank you for reporting the bug, which will now be closed. If you
have further comments please address them to 1054...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Andreas Tille (supplier of updated bookletimposer package)
(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Format: 1.8
Date: Fri, 09 Feb 2024 16:56:19 +0100
Source: bookletimposer
Architecture: source
Version: 0.3.1-4
Distribution: unstable
Urgency: medium
Maintainer: Debian Python Team
Changed-By: Andreas Tille
Closes: 1043745 1049559 1054753 1061737 1061788 1061789
Changes:
bookletimposer (0.3.1-4) unstable; urgency=medium
.
* Team upload.
* Remove unneeded references to distutils
Closes: #1061789, #1061788, #1054753, #1061737
* Fix clean target
Closes: #1043745
* Fix building binary packages again after successful build
Closes: #1049559
* Standards-Version: 4.6.2 (routine-update)
* Build-Depends: s/dh-python/dh-sequence-python3/ (routine-update)
Checksums-Sha1:
6962e726312aa828906a4a0a90bc5b580099c3d5 2250 bookletimposer_0.3.1-4.dsc
7b21e8a679c32a0318e1b7bde75fe173bc8da97a 7500
bookletimposer_0.3.1-4.debian.tar.xz
63299e31ae0e919894399c40da043a989c693551 8162
bookletimposer_0.3.1-4_amd64.buildinfo
Checksums-Sha256:
643ef855fddea83811ad737696f8d83c387dd45003aba6f734a83222b381de89 2250
bookletimposer_0.3.1-4.dsc
300757ed73e4ac3022913dd7a69a7c3d1fec2f65d54223f61968835055cbedb3 7500
bookletimposer_0.3.1-4.debian.tar.xz
c28419968c8d719c132cea0143474da716f913a5e6096b532470f8e27990f03c 8162
bookletimposer_0.3.1-4_amd64.buildinfo
Files:
011fea52e942b7eca3cd4022755c9ec5 2250 python optional
bookletimposer_0.3.1-4.dsc
cfbe91bef5469daaf4514320836636c6 7500 python optional
bookletimposer_0.3.1-4.debian.tar.xz
Processed: Bug#1052730 marked as pending in ruby-delayed-job
Processing control commands: > tag -1 pending Bug #1052730 [src:ruby-delayed-job] ruby-delayed-job: FTBFS: ERROR: Test "ruby3.1" failed: ArgumentError: Added tag(s) pending. -- 1052730: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1052730 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1052730: marked as pending in ruby-delayed-job
Control: tag -1 pending Hello, Bug #1052730 in ruby-delayed-job reported by you has been fixed in the Git repository and is awaiting an upload. You can see the commit message below and you can check the diff of the fix at: https://salsa.debian.org/ruby-team/ruby-delayed-job/-/commit/44203fe9814deb7de9c88d266aafc3f63f6850ba Fix invalid time zone US/Eastern error (Closes: #1052730) (this message was generated automatically) -- Greetings https://bugs.debian.org/1052730
Bug#1063518: console-setup: setupcon: 1386: Syntax error: Missing '))'
Michael Tokarev writes: > 09.02.2024 16:58, ca...@allfreemail.net >> Package: console-setup >> Followup-For: Bug #1063518 >> >> Consider making all scripts provided by console-setup >> shellcheck-clean, there are lots of tiny issues that can turn into >> big issues under the right conditions. > > Please do not do this. Shellcheck is a huge problem and we had large amount > of bugs due to people trying to apply its suggestions. It's very difficult > in many cases to spot why shellcheck is wrong (classic is the suggestion to > put $var into double quotes "$var" which breaks badly if $var is supposed to > contain zero or more separate words - this way, even boot scripts has become > buggy leading to system becoming unbootable). > > Shellcheck is a very bad tool. I think the reality is somewhere between these two positions. Shellcheck is not particularly helpful for most of D-I because it doesn't have a shell variant that perfectly matches our busybox sh build. That might have just improved, since I notice that a busybox sh variant has just been merged upstream, so we'll see if that makes things better. On the other hand, if I'd been paying attention at the time, the fact that this change dropped the number of shellcheck reports for setupcon from 189 to 1 should have rung some alarm bells, but it seems that I've learnt to ignore the little '!' in my emacs status bar -- I'll have to keep an eye on that in future. Cheers, Phil. -- Philip Hands -- https://hands.com/~phil
Bug#1063321: libwxgtk3.2-1t64 has an undeclared file conflict
On Tue, 6 Feb 2024, Helmut Grohne wrote: Package: libwxgtk3.2-1t64 Version: 3.2.4+dfsg-3.1~exp1 Severity: serious User: debian...@lists.debian.org Usertags: fileconflict Control: affects -1 + libwxgtk-gl3.2-1 libwxgtk-gl3.2-1t64 libwxgtk-media3.2-1 libwxgtk-media3.2-1t64 libwxgtk-webview3.2-1 libwxgtk-webview3.2-1t64 X-Debbugs-Cc: vor...@debian.org libwxgtk3.2-1t64 has an undeclared file conflict. This may result in an unpack error from dpkg. Hello Steve, Are you planning on fixing this, or would you like me to? If the latter, how would you like the fix submitted before this is uploaded to unstable? Regards, Scott
Bug#1063518: console-setup: setupcon: 1386: Syntax error: Missing '))'
09.02.2024 17:57, Thorsten Bonow :
dash << 'EOF' [15:28:53]
if $( (true) 2>/dev/null); then
echo "42"
fi
EOF
42
which only works in dash because of the added space between the command
substitution $(...) and the subshell (...).
Does dash think it has to do arithmetic expansion "$((...))"?
Yes, arithmetic, and that's what bash does too. dash does not understand
space between two closing parens though, ') )'. And this is logical - if
the opening is "((", use the same matching "))" for closing.
$(( ... )) is arithmetic expression,
$( ( ... ) ) is a subshell.
Everything else is asking for trouble like this.
But what's POSIX take on this? I couldn't find anything. Is this a bug in
dash or in setupcon?
It's a bug in setupcon.
/mjt
Bug#1063518: marked as done (console-setup: setupcon: 1386: Syntax error: Missing '))')
Your message dated Fri, 09 Feb 2024 15:34:15 +
with message-id
and subject line Bug#1063518: fixed in console-setup 1.226
has caused the Debian Bug report #1063518,
regarding console-setup: setupcon: 1386: Syntax error: Missing '))'
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 responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)
--
1063518: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1063518
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: console-setup
Version: 1.225
Severity: grave
After the upgrade from 1.223, console-setup.service failed to start due
to a syntax error in the setupcon script:
,
| $ setupcon
| /usr/bin/setupcon: 1386: Syntax error: Missing '))'
`
It looks like dash does not like the construct in line 907 where there
is an opening '$((' but the closing parentheses are split.
,
| $ dash << 'EOF'
| > echo $((true))
| > echo $((true) )
| > EOF
| 0
| dash: 3: Syntax error: Missing '))'
| $
`
-- System Information:
Debian Release: trixie/sid
APT prefers unstable
APT policy: (500, 'unstable'), (101, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386
--- End Message ---
--- Begin Message ---
Source: console-setup
Source-Version: 1.226
Done: Philip Hands
We believe that the bug you reported is fixed in the latest version of
console-setup, which is due to be installed in the Debian FTP archive.
A summary of the changes between this version and the previous one is
attached.
Thank you for reporting the bug, which will now be closed. If you
have further comments please address them to 1063...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Philip Hands (supplier of updated console-setup package)
(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Format: 1.8
Date: Fri, 09 Feb 2024 15:45:38 +0100
Source: console-setup
Architecture: source
Version: 1.226
Distribution: unstable
Urgency: medium
Maintainer: Debian Install System Team
Changed-By: Philip Hands
Closes: 1063518
Changes:
console-setup (1.226) unstable; urgency=medium
.
* Team upload
.
* setupcon: fix mistaken $(( (closes: 1063518)
Checksums-Sha1:
84294e5b75b00aad2cced6b0cfab0635682b6c3e 3340 console-setup_1.226.dsc
ff1036c7201a486a791040148128711a5a746106 1685272 console-setup_1.226.tar.xz
Checksums-Sha256:
25d949da1eb3e494bed1f3fc11074c5221ce54bd1463963b0b9417b9b89922f9 3340
console-setup_1.226.dsc
992be8dfcc5b99c42cb0f2914d987298e281e9232eb2492302d97dc3ff6412bd 1685272
console-setup_1.226.tar.xz
Files:
82130112e2f68bcbbe925f8d337b7acd 3340 utils optional console-setup_1.226.dsc
81e55c7e628e52eeb52efa6cbaeeb03f 1685272 utils optional
console-setup_1.226.tar.xz
-BEGIN PGP SIGNATURE-
iQJDBAEBCgAtFiEE3/FBWs4yJ/zyBwfW0EujoAEl1cAFAmXGQE8PHHBoaWxAaGFu
ZHMuY29tAAoJENBLo6ABJdXAuuMP/i3ZoM4rKVGU3yZilBPOYOeLxvPdqHzqxGuZ
huCceNMgLX7CFN4Je1t2CoUwV5Xp8V9/+uR1ZZ624nvoH+iIsuSyK9N+uk/xFTw+
9fwNgY3Wf1bRI7H6jMF35ZK8pwo9I1aCzoflEI/dTemzTi5ewgaGKwSL+MEkuZwB
MBs1gpnEe8ERsTfE6DEb9/7V8eK2rLXq1RFXSu1M+wMGG8i0vmvV7KavUcs1obgL
kYH0YMRO6DnBfmzqb3mOnwF3LKBRoiyejh8tk7qREfd5UDSt5zCwd+3erarFIjaw
3j4aPV6b26vMzlEIr85HhodjU0dOSrM/UeuYIQPTH0pvKO9mo9RXJ4FoJ8RVgALG
5/kGZIJJNlBASKksLli/HWR2zonyExz9d6un9KwQg7825TT4q5uaH09ytmfYI4Dz
nJL4VeUybWo/EyqfplknUUi3yBmlCAaUx3uuS1hYO2/HFDYa2YZP6RA4jEV9sreJ
koGzSI0AowPSziGx6n3rOiSLUfpik8ZBCfy+alm4zB5XYtPW/60qmYIs67UKqdmd
hnnPDQAAwF4Vmhb1f8ZXRpOLyvIgnx+vWWdy1pQf9YZFHA/UmTIPSR0ZAPtupLdj
HFHdQLeE0I5ZjymHVyh1SyUUK4v5swXYasfvXBXhTADODgMo1BXmZ9hQz+Bi31GP
MYv0Hz4t
=YBWD
-END PGP SIGNATURE End Message ---
Bug#1063518: console-setup: setupcon: 1386: Syntax error: Missing '))'
Thorsten Bonow writes:
[...]
But what's POSIX take on this? I couldn't find anything. Is this a
bug in dash or in setupcon?
I'm stupid[1]. It's a bug in setupcon, POSIX requires the space:
"The syntax of the shell command language has an ambiguity for
expansions beginning with "$((", which can introduce an arithmetic
expansion or a command substitution that starts with a subshell.
Arithmetic expansion has precedence; that is, the shell shall first
determine whether it can parse the expansion as an arithmetic
expansion and shall only parse the expansion as a command substitution
if it determines that it cannot parse the expansion as an arithmetic
expansion. The shell need not evaluate nested expansions when
performing this determination. If it encounters the end of input
without already having determined that it cannot parse the expansion
as an arithmetic expansion, the shell shall treat the expansion as an
incomplete arithmetic expansion and report a syntax error. A
conforming application shall ensure that it separates the "$(" and '('
into two tokens (that is, separate them with white space) in a command
substitution that starts with a subshell. For example, a command
substitution containing a single subshell could be written as:
$( (command) )"
Footnotes:
[1]
https://pubs.opengroup.org/onlinepubs/9699919799/utilities/V3_chap02.html#tag_18_06_03
Bug#1058100: marked as done (freedom-maker: FTBFS: ModuleNotFoundError: No module named 'imp')
Your message dated Fri, 9 Feb 2024 10:22:34 -0500
with message-id
and subject line Re: freedom-maker: FTBFS: ModuleNotFoundError: No module named
'imp'
has caused the Debian Bug report #1058100,
regarding freedom-maker: FTBFS: ModuleNotFoundError: No module named 'imp'
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 responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)
--
1058100: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1058100
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: freedom-maker
Version: 0.32
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 amd64.
Relevant part (hopefully):
> debian/rules clean
> dh clean --with python3 --buildsystem=pybuild
>dh_auto_clean -O--buildsystem=pybuild
> pybuild --clean -i python{version} -p "3.12 3.11"
> I: pybuild base:310: python3.12 setup.py clean
> Traceback (most recent call last):
> File "/<>/setup.py", line 9, in
> from freedommaker import __version__
> File "/<>/freedommaker/__init__.py", line 7, in
> from .application import Application
> File "/<>/freedommaker/application.py", line 15, in
> from .builder import ImageBuilder
> File "/<>/freedommaker/builder.py", line 9, in
> from . import internal, library
> File "/<>/freedommaker/internal.py", line 8, in
> from . import library, utils
> File "/<>/freedommaker/library.py", line 16, in
> import cliapp
> File "/usr/lib/python3/dist-packages/cliapp/__init__.py", line 45, in
>
> from .pluginmgr import PluginManager
> File "/usr/lib/python3/dist-packages/cliapp/pluginmgr.py", line 29, in
>
> import imp
> ModuleNotFoundError: No module named 'imp'
> E: pybuild pybuild:395: clean: plugin distutils failed with: exit code=1:
> python3.12 setup.py clean
> dh_auto_clean: error: pybuild --clean -i python{version} -p "3.12 3.11"
> returned exit code 13
> make: *** [debian/rules:7: clean] Error 25
The full build log is available from:
http://qa-logs.debian.net/2023/12/12/freedom-maker_0.32_unstable.log
All bugs filed during this archive rebuild are listed at:
https://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=ftbfs-20231212;users=lu...@debian.org
or:
https://udd.debian.org/bugs/?release=na=ign=7=7=only=ftbfs-20231212=lu...@debian.org=1=1=1=1#results
A list of current common problems and possible solutions is available at
http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute!
If you reassign this bug to another package, please mark it as 'affects'-ing
this package. See https://www.debian.org/Bugs/server-control#affects
If you fail to reproduce this, please provide a build log and diff it with mine
so that we can identify if something relevant changed in the meantime.
--- End Message ---
--- Begin Message ---
Same as #1056248, this was caused by #1061823
python-cliapp ftbfs with Python 3.12 as default
which was closed. Thus now also closing this bug.
OpenPGP_signature.asc
Description: OpenPGP digital signature
--- End Message ---
Bug#1063518: console-setup: setupcon: 1386: Syntax error: Missing '))'
Package: console-setup
Version: 1.225
Severity: grave
After the upgrade from 1.223, console-setup.service failed to start
due
to a syntax error in the setupcon script:
,
| $ setupcon
| /usr/bin/setupcon: 1386: Syntax error: Missing '))'
`
It looks like dash does not like the construct in line 907 where
there
is an opening '$((' but the closing parentheses are split.
,
| $ dash << 'EOF'
| > echo $((true))
| > echo $((true) )
| > EOF
| 0
| dash: 3: Syntax error: Missing '))'
| $
`
I tried
dash << 'EOF'[15:28:53]
if $( (true) 2>/dev/null); then
echo "42"
fi
EOF
42
which only works in dash because of the added space between the
command substitution $(...) and the subshell (...).
Does dash think it has to do arithmetic expansion "$((...))"?
bash and zsh in sh mode accept nesting a subshell within the command
substitution without an extra space. In the last version of the
script, backticks were used, circumventing this issue.
But what's POSIX take on this? I couldn't find anything. Is this a
bug in dash or in setupcon?
Toto
PS: To the proposal of a cleanup: 'checkbashisms' doesn't return any
errors, but IMHO, at least closing (double) quotes on
a line of their own should be fixed:
$ cat /bin/setupcon | grep -n "^\(\"\|'\)$"
[15:47:07]
87:'
145:"
148:"
190:"
193:"
208:"
Processed: severity of 1061972 is important
Processing commands for cont...@bugs.debian.org:
> severity 1061972 important
Bug #1061972 {Done: Bill Allombert } [src:gap] gap: NMU
diff for 64-bit time_t transition
Severity set to 'important' from 'serious'
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
1061972: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1061972
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Processed: bug 1052730 is forwarded to https://github.com/collectiveidea/delayed_job/pull/1203
Processing commands for cont...@bugs.debian.org: > forwarded 1052730 https://github.com/collectiveidea/delayed_job/pull/1203 Bug #1052730 [src:ruby-delayed-job] ruby-delayed-job: FTBFS: ERROR: Test "ruby3.1" failed: ArgumentError: Set Bug forwarded-to-address to 'https://github.com/collectiveidea/delayed_job/pull/1203'. > thanks Stopping processing here. Please contact me if you need assistance. -- 1052730: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1052730 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1052730: ruby-delayed-job: FTBFS: ERROR: Test "ruby3.1" failed: ArgumentError:
Control: forwarded -1 https://github.com/collectiveidea/delayed_job/pull/1203 On Tue, 26 Sep 2023 14:40:49 +0200 Lucas Nussbaum wrote: Relevant part (hopefully): > ArgumentError: >Invalid Timezone: US/Eastern Forwarded fix upstream https://github.com/collectiveidea/delayed_job/pull/1203
Bug#1059666: marked as done (python-hug: autopkgtest failure with Python 3.12)
Your message dated Fri, 09 Feb 2024 14:49:51 + with message-id and subject line Bug#1059666: fixed in python-hug 2.6.0-3 has caused the Debian Bug report #1059666, regarding python-hug: autopkgtest failure 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 the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 1059666: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1059666 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: python-hug Version: 2.6.0-2.4 Severity: serious Tags: sid trixie User: debian-pyt...@lists.debian.org Usertags: python3.12 Hi Maintainer python-hug's autopkgtests fail with Python 3.12 [1]. I've copied what I hope is the relevant part of the log below. Regards Graham [1] https://ci.debian.net/packages/p/python-hug/testing/amd64/ 26s autopkgtest [20:11:46]: test autodep8-python3: [--- 26s Testing with python3.12: 26s Traceback (most recent call last): 26s File "", line 1, in 26s File "/usr/lib/python3/dist-packages/hug/__init__.py", line 36, in 26s from hug import ( 26s File "hug/route.py", line 29, in init hug.route 26s File "hug/api.py", line 27, in init hug.api 26s ModuleNotFoundError: No module named 'distutils' 27s autopkgtest [20:11:47]: test autodep8-python3: ---] --- End Message --- --- Begin Message --- Source: python-hug Source-Version: 2.6.0-3 Done: Andreas Tille We believe that the bug you reported is fixed in the latest version of python-hug, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 1059...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Andreas Tille (supplier of updated python-hug package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Fri, 09 Feb 2024 15:21:29 +0100 Source: python-hug Architecture: source Version: 2.6.0-3 Distribution: unstable Urgency: medium Maintainer: Debian Python Team Changed-By: Andreas Tille Closes: 1059666 Changes: python-hug (2.6.0-3) unstable; urgency=medium . * Team upload. * Move package to DPT * Replace distutils which is removed in Python3.12 Closes: #1059666 * Enable build-time tests * Fix Python3.11 issue in tests * Fix Numpy issue in tests * Exclude tests requiring network access * Mark tests skip that seem to use the marshmallow API wrongly (see debian/README.source) * Mark tests skip that are failing for unknown reasons adding FIXME. This needs more investigation but its better than simply no tests at all. (see debian/README.source) * Reorder sequence of d/control fields by cme (routine-update) * Build-Depends: s/dh-python/dh-sequence-python3/ (routine-update) * Rules-Requires-Root: no (routine-update) Checksums-Sha1: 08e18a0f89c7a444cddf112ecfd89c707ecd78c2 2347 python-hug_2.6.0-3.dsc 149a07e0716b4a61f912e00b1de4ea80af590a1b 8732 python-hug_2.6.0-3.debian.tar.xz c4e5de40fe8163aebd83bceaf0349f410c4e65de 9566 python-hug_2.6.0-3_amd64.buildinfo Checksums-Sha256: 3338138d104fbf94e9c1b4aae9976be4d1f4b69037983c61c4e6f207ce1027a0 2347 python-hug_2.6.0-3.dsc 8823a74e10a5e8c50b165f2910ea33cd2fdbef0d1017dccfc363d14c896ef315 8732 python-hug_2.6.0-3.debian.tar.xz 59f6051073bfe9fb3f7950bcbf858d1be69e68e9f5656141bfcedba74cd6e7f5 9566 python-hug_2.6.0-3_amd64.buildinfo Files: e7d4ba1180b0fd5513b1935952342cda 2347 python optional python-hug_2.6.0-3.dsc 9425ac5c44966c49ff9403b7231594b8 8732 python optional python-hug_2.6.0-3.debian.tar.xz c34e5ae6b604e8b62a26aae9d7c06507 9566 python optional python-hug_2.6.0-3_amd64.buildinfo -BEGIN PGP SIGNATURE- iQJFBAEBCgAvFiEE8fAHMgoDVUHwpmPKV4oElNHGRtEFAmXGNssRHHRpbGxlQGRl Ymlhbi5vcmcACgkQV4oElNHGRtEYhg//XqTVNM+MO7mPvjiy10WPl9U90C92zxqJ zofdfYKQ/5Lpd4c8NNUEYscm1S3gSF0jqg+Y87R5PjI/bFIy2OsbLvQ8FdgX5ILD CFXvT3y0aPcp0h15ICG3oZjNqkJ+ss+IClG7LLwejuzhAo501SJx6Cwb820ksnxY iacTS/mQvhOQnRE8qqrf+AUQ5MRd+mWX6Trs1Yg5K6OtmGo07jZ8bdTlf/sidMLH KXvSWUGSVfrLUGEi87QAb2DB+Q31HChVnbxHQkZRjVU+bjQQauite+hHWnjd92n4 YGUE/ahKGA98AtWMHGYClcBCJyMPF5mWBeqz63AOhI0rd2UFPFHcYLVGWFQ6IJcM tvRBASCv4BYXYETNvU6YcZwlTylr6dub4kglLsMUq+aMjHYvQwCqo8bZEqEGw4eM vzlO/R1LgKarvuV2Dio0x5fboKsyLvpCXeUutl4XnbXyQKcVWNfhE0gCJWLBrzUF
Bug#1056844: marked as done (pyregion: ftbfs with cython 3.0.x)
Your message dated Fri, 09 Feb 2024 14:38:09 + with message-id and subject line Bug#1056844: fixed in pyregion 2.2.0-3 has caused the Debian Bug report #1056844, regarding pyregion: ftbfs with cython 3.0.x 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 responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 1056844: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1056844 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: src:pyregion Version: 2.2.0-1 Severity: important Tags: sid trixie User: debian-pyt...@lists.debian.org Usertags: cython3 [This bug is targeted to the upcoming trixie release] The package fails to build in a test rebuild on at least arm64 with cython 3.0.5, but succeeds to build with cython 0.29.36. Please update the package to build with cython 3.0.5 (available in experimental). If the package cannot be built with cython 3.0.5, please change the build dependency from cython3 to cython3-legacy (available now in unstable). There is no replacement for cython3-dbg. Build logs building with cython 3.0.5 can be found at https://people.debian.org/~stefanor/cython3/cython-3.0.5/ See also https://lists.debian.org/debian-python/2023/11/msg00034.html --- End Message --- --- Begin Message --- Source: pyregion Source-Version: 2.2.0-3 Done: Ole Streicher We believe that the bug you reported is fixed in the latest version of pyregion, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 1056...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Ole Streicher (supplier of updated pyregion package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Fri, 09 Feb 2024 15:12:39 +0100 Source: pyregion Architecture: source Version: 2.2.0-3 Distribution: unstable Urgency: medium Maintainer: Debian Astro Team Changed-By: Ole Streicher Closes: 1056844 Changes: pyregion (2.2.0-3) unstable; urgency=medium . * Team upload. * Switch to cython3-legacy. Closes: #1056844 Checksums-Sha1: 8ae846f7ce1196ef0a93f1087ae2b73813c5cdd0 2322 pyregion_2.2.0-3.dsc 34e138d2c8a3fa82dea52265d3f57398b6b57233 4536 pyregion_2.2.0-3.debian.tar.xz Checksums-Sha256: 50c5aedadd3439273e0f8ff284c9b63669db83415354cd9eb69b180a5fd56beb 2322 pyregion_2.2.0-3.dsc c8cf212626a32e3d71936308b32e060e771095d878345f21ab4e84e126a355d2 4536 pyregion_2.2.0-3.debian.tar.xz Files: e15570f01567ccb2b4b376b8c8b48727 2322 python optional pyregion_2.2.0-3.dsc 563d65d7f47ecf6df973b3a8b420e983 4536 python optional pyregion_2.2.0-3.debian.tar.xz -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEE7/BpV0Ra2/h0L3qtmk9WvbkOGL0FAmXGNWoACgkQmk9WvbkO GL1H0xAAnMyx+zC5RjfJSi5FtLeO6Nru9ncKmzrqE682e68pzVrVRs6IFvcWiVnm H+1hj5uWPB5Brc1N/UGURVq/NFj/dd+7VPTyWChRh8qB0bTUZg6aCNNiki/3Lv4o 8sDkfClS+H3lTuaMGG1wuXvgkn1HHTC4YWYfD8vSe6aI/HAghvfEBlF537cw/0Rm 2Kv0fJn2xfF3mdbjynwo7ymKgrO+sjSIJdU4l3iJdYbMfpkliVVu0wuBRKvpgiln 4IRlaG8BL2bIJgD1Q7BveqJi1vlly1kGkWjmxRtjOLp7yx58Glcswvfi+bcYvsfq 6ff4fglTQvNWwmlQtB/mINeqnIh5KI6a7YLCwsLp6ZIPAhULkEMKb/wEpCM/FVII +27BWhFx1Dzh1Cx5Wjl95ZscFRFJBRlhUVoZHr4Mmnav6px1oNlwbbwjwaYIDm5/ 0kODConzOMlz+ZW+FcmqPs83ud7p43+w7jzAdjiIwqhwTm2IIkgBMTnFHHq2IHQ8 xqjE7FuSAV0KMtryF/kEEg4yOLUo1n+wrzGj/I0rHJxXaEHlckOZvbKJhm/TVSbD otyIBf9JV7JT371pVFcTwxbgfkH2qemNej6SQ3Fwu/LcxvLLY5tR1x2sIMo66qoE 3gFxaPPf9z3XwDiGPkZQHpkFmrG5nXg3ZgqMZtYodhKZmqwylMg= =XoiJ -END PGP SIGNATURE End Message ---
Bug#1056227: marked as done (aplpy's autopkg tests fail with Python 3.12)
Your message dated Fri, 09 Feb 2024 14:34:13 + with message-id and subject line Bug#1056227: fixed in aplpy 2.1.0-2 has caused the Debian Bug report #1056227, regarding aplpy's autopkg tests fail 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 the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 1056227: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1056227 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: src:aplpy Version: 2.1.0-1 Severity: important Tags: sid trixie User: debian-pyt...@lists.debian.org Usertags: python3.12 aplpy's autopkg tests fail with Python 3.12 (distutils is removed in 3.12): [...] 272s = test session starts == 272s platform linux -- Python 3.12.0+, pytest-7.4.3, pluggy-1.3.0 272s Matplotlib: 3.6.3 272s Freetype: 2.13.2 272s rootdir: /tmp/autopkgtest.a7vquV/autopkgtest_tmp 272s plugins: arraydiff-0.6.0, remotedata-0.4.1, doctestplus-1.0.0, hypothesis-6.88.4, astropy-header-0.2.2, astropy-0.11.0, filter-subpackage-0.1.2, mpl-0.0.0, mock-3.11.1, cov-4.1.0 272s collected 0 items / 1 error 272s 272s ERRORS 272s ERROR collecting test session _ 272s /usr/lib/python3/dist-packages/_pytest/config/__init__.py:641: in _importconftest 272s mod = import_path(conftestpath, mode=importmode, root=rootpath) 272s /usr/lib/python3/dist-packages/_pytest/pathlib.py:567: in import_path 272s importlib.import_module(module_name) 272s /usr/lib/python3.12/importlib/__init__.py:90: in import_module 272s return _bootstrap._gcd_import(name[level:], package, level) 272s :1381: in _gcd_import 272s ??? 272s :1354: in _find_and_load 272s ??? 272s :1304: in _find_and_load_unlocked 272s ??? 272s :488: in _call_with_frames_removed 272s ??? 272s :1381: in _gcd_import 272s ??? 272s :1354: in _find_and_load 272s ??? 272s :1325: in _find_and_load_unlocked 272s ??? 272s :929: in _load_unlocked 272s ??? 272s :994: in exec_module 272s ??? 272s :488: in _call_with_frames_removed 272s ??? 272s /usr/lib/python3/dist-packages/aplpy/__init__.py:14: in 272s from .core import FITSFigure # noqa 272s /usr/lib/python3/dist-packages/aplpy/core.py:1: in 272s from distutils import version 272s E ModuleNotFoundError: No module named 'distutils' 272s === short test summary info 272s ERROR - ModuleNotFoundError: No module named 'distutils' 272s Interrupted: 1 error during collection 272s === 1 error in 0.28s === --- End Message --- --- Begin Message --- Source: aplpy Source-Version: 2.1.0-2 Done: Ole Streicher We believe that the bug you reported is fixed in the latest version of aplpy, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 1056...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Ole Streicher (supplier of updated aplpy package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Fri, 09 Feb 2024 14:45:53 +0100 Source: aplpy Architecture: source Version: 2.1.0-2 Distribution: unstable Urgency: medium Maintainer: Debian Astronomy Team Changed-By: Ole Streicher Closes: 1056227 Changes: aplpy (2.1.0-2) unstable; urgency=medium . [ Andreas Tille ] * Replace distutils which is removed in Python3.12 by packaging Closes: #1056227 * Standards-Version: 4.6.2 (routine-update) * Build-Depends: s/dh-python/dh-sequence-python3/ (routine-update) * Rules-Requires-Root: no (routine-update) . [ Ole Streicher ] * Disable configuration update for astropy-6 compatibility Checksums-Sha1: af694d69fd28484b7734286e2e1925f710514225 2279 aplpy_2.1.0-2.dsc f4bd7fc86c7a89bececde772c744fe3a8f18bfc4 4636 aplpy_2.1.0-2.debian.tar.xz Checksums-Sha256: 3ec730838f65c29dc7cf54e39657fa7ccd43cd08452df035be629af1b629e284 2279 aplpy_2.1.0-2.dsc b6312976a24bcd213bd27eabbbed951aed144ea143861fec458d0a24cdd8f1a3 4636 aplpy_2.1.0-2.debian.tar.xz
Bug#1063525: marked as done (d-spy FTBFS with nocheck profile: ../meson.build:187:6: ERROR: Program 'update-desktop-database' not found or not executable)
Your message dated Fri, 09 Feb 2024 14:34:28 + with message-id and subject line Bug#1063525: fixed in d-spy 1.9.0-1 has caused the Debian Bug report #1063525, regarding d-spy FTBFS with nocheck profile: ../meson.build:187:6: ERROR: Program 'update-desktop-database' not found or not executable 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 responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 1063525: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1063525 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: d-spy Version: 1.8.0-1 Severity: serious Tags: ftbfs trixie sid d-spy fails to build from source when built with the nocheck build profile. Since trixie such a failure is considered release-critical. A build ends with: | ../meson.build:187:6: ERROR: Program 'update-desktop-database' not found or not executable | dh_auto_configure: error: cd obj-x86_64-linux-gnu && DEB_PYTHON_INSTALL_LAYOUT=deb LC_ALL=C.UTF-8 meson setup .. --wrap-mode=nodownload --buildtype=plain --prefix=/usr --sysconfdir=/etc --localstatedir=/var --libdir=lib/x86_64-linux-gnu -Dpython.bytecompile=-1 returned exit code 1 | make: *** [debian/rules:8: binary] Error 25 | dpkg-buildpackage: error: debian/rules binary subprocess returned exit status 2 Helmut --- End Message --- --- Begin Message --- Source: d-spy Source-Version: 1.9.0-1 Done: Jeremy Bícha We believe that the bug you reported is fixed in the latest version of d-spy, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 1063...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Jeremy Bícha (supplier of updated d-spy package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Fri, 09 Feb 2024 08:54:04 -0500 Source: d-spy Built-For-Profiles: noudeb Architecture: source Version: 1.9.0-1 Distribution: unstable Urgency: medium Maintainer: Debian GNOME Maintainers Changed-By: Jeremy Bícha Closes: 1063525 Changes: d-spy (1.9.0-1) unstable; urgency=medium . * New upstream release * debian/control: Bump minimum glib, gtk4, and libadwaita * Stop using debian/control.in and dh-sequence-gnome * Drop invalid nocheck annotation for desktop-file-utils (Closes: #1063525) Checksums-Sha1: 81c7e8a5e1e6aab20405e0aeddee2ca1c20aa5b3 2215 d-spy_1.9.0-1.dsc 0c9637307c00a56db2b1d6564827affb2d2a3840 235404 d-spy_1.9.0.orig.tar.xz be252b1ce1438c9d85b7008b3a8219932dfcc26c 9052 d-spy_1.9.0-1.debian.tar.xz 60b9d9b83a09777672bf326cf6739bcc737b26fb 10286 d-spy_1.9.0-1_source.buildinfo Checksums-Sha256: 07f33633368d47c07a838538dc22012613d3c43ec5ccab00ab02bf2445405d01 2215 d-spy_1.9.0-1.dsc 372b6ba58ce1c10165dd147ebeeb3991048fd6d80239ee9a8db627f75c828f36 235404 d-spy_1.9.0.orig.tar.xz e6763f36df5b360be29b2f718ec1194c421dfcc338bb01bc9cb016aa4b2f4619 9052 d-spy_1.9.0-1.debian.tar.xz e172ed4e80aef5302446aba6a36a4d559757ffdac41f7f6d1204f92f06e706fb 10286 d-spy_1.9.0-1_source.buildinfo Files: 305f47b5705ff4c0fff475f120817b8a 2215 gnome optional d-spy_1.9.0-1.dsc 87bf2f3ae2488182e389843cfb119df0 235404 gnome optional d-spy_1.9.0.orig.tar.xz 0383dc0e66620c7a44e74627fdab5c23 9052 gnome optional d-spy_1.9.0-1.debian.tar.xz e853b2f7fe2250a9958c7cf37cf90674 10286 gnome optional d-spy_1.9.0-1_source.buildinfo -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEETQvhLw5HdtiqzpaW5mx3Wuv+bH0FAmXGLpEACgkQ5mx3Wuv+ bH1mXQ/9Gl7QPZYLxIBWhb+bRuIHXzqlZ7t3ekd175qYFhDC4kw8nLVi+eOUpOve Vkfys542TteF367uDVo+ec/Sc5p3x/5qVk5mCRfvnRnuBC+f/KF5HH1ZEvKOq2s5 ZuThjN+CvekCwJZZ5B8CiwUbg1GpKo4Fy6aHhK0ynBKrOy5mj4GPITPJhSreEL0f nbHPbM3TR0p/17pufuqfHe2xmLCTljom6i9Wgt8FoNasHjbSgX3MlxXloHl6mwIW Rq0mPUZmndptM+YOYQ7tZKOmnZnDk0e0rTwhCbNWpjl9xw9mTJmQiSA+P5fEludL biIoyxOOZfmGYqLPojml2wGQyBzwQGt0fBlgTiXKFtu36MMn0+233kJyXX5vDFSj /EU2EfI+W021E/ddhhqY4En+uwoepEUC2B21RiyO2PtLi9RMzyG4WQgEQ0Gm5oXv bG8c2ZtaCqNTbpAdVrtMH7pAD53IQvx8SqT/Eq6uum+oFkya5BSLa9IKo7qH+9kQ f9S5ctknovVOUklxuX6vKTqtCVzHQjunbWACfkwwGQa5RC9oHqVQBjrcSbzJ3zh+ xCDn3wFsZRVjircQC4vjXr1KifSYIJECrtJKf74TGETxIQXBArxDbpUVWQ7Z7zPG 64zkL9nNx8VOvDmeqaiQmBDbscZfw2Pr2Q3Ob3XWVhsQ04uw1Os= =G6XA -END PGP SIGNATURE End Message ---
Bug#1063518: console-setup: setupcon: 1386: Syntax error: Missing '))'
09.02.2024 16:58, ca...@allfreemail.net Package: console-setup Followup-For: Bug #1063518 Consider making all scripts provided by console-setup shellcheck-clean, there are lots of tiny issues that can turn into big issues under the right conditions. Please do not do this. Shellcheck is a huge problem and we had large amount of bugs due to people trying to apply its suggestions. It's very difficult in many cases to spot why shellcheck is wrong (classic is the suggestion to put $var into double quotes "$var" which breaks badly if $var is supposed to contain zero or more separate words - this way, even boot scripts has become buggy leading to system becoming unbootable). Shellcheck is a very bad tool. /mjt
Bug#1063518: console-setup: setupcon: 1386: Syntax error: Missing '))'
Package: console-setup Followup-For: Bug #1063518 Consider making all scripts provided by console-setup shellcheck-clean, there are lots of tiny issues that can turn into big issues under the right conditions. https://tracker.debian.org/pkg/shellcheck
Bug#1063478: gem2deb rails assets smoke test should handle links or skip the test during build
Control: severity -1 important On 9/2/24 6:48 PM, Pirate Praveen wrote: Without libjs-underscore in build depends, the test should fail, but it is passing. ruby-rails-assets-underscore source package includes underscore.js and it is replaced by symlink to libjs-underscore only in dh_install stage so rake assets:precompile can still find it. So it looks like gem2deb test is working as expected, but we still need to figure out a way out for symlinks. May be we should just link them in the build target itself as a solution. If that is the recommended solution, we can close this bug with a note in dh_ruby documentation.
Processed: Re: gem2deb rails assets smoke test should handle links or skip the test during build
Processing control commands: > severity -1 important Bug #1063478 [gem2deb] gem2deb rails assets smoke test should handle links or skip the test during build Severity set to 'important' from 'serious' -- 1063478: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1063478 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: severity of 1063492 is grave
Processing commands for cont...@bugs.debian.org: > severity 1063492 grave Bug #1063492 [src:openvswitch] openvswitch: CVE-2023-3966: Invalid memory access in Geneve with HW offload Severity set to 'grave' from 'important' > thanks Stopping processing here. Please contact me if you need assistance. -- 1063492: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1063492 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1063530: node-undici: FTBFS with nodejs 18.19.0+dfsg-6~deb12u1
Source: node-undici
Version: 5.15.0+dfsg1+~cs20.10.9.3-1+deb12u3
Severity: serious
Tags: bookworm
Usertags: apertis-ftbfs
Justification: FTBFS
Hello,
While doing a rebuild of some node packages in Bookworm, it appears several
packages (at least ~ 50 pkgs) no longer build with nodejs 18.19.0+dfsg-6~deb12u1
(from bookworm-security repo) while they still successfully build with nodejs
18.13.0+dfsg1-1 (from the main bookworm repo). They all fail with the
same error:
error TS2307: Cannot find module 'undici-types' or its corresponding
type declarations.
Since, I am not sure which package need to be fixed (nodejs, node-undici or
all of them), I fill this bug against the package referred by the error message,
please reassign to the relevent package.
Below is the relevant part of the log:
dh_auto_build --buildsystem=nodejs
Found debian/nodejs/additional_components
Adding component(s): types
/!\ types/package.json not found
/!\ types/package.json not found
Unable to load types
No build command found, searching known files
Found debian/nodejs/llparse-builder/build
cd ./llparse-builder && sh -ex ../debian/nodejs/llparse-builder/build
+ tsc
../../../../usr/share/nodejs/@types/node/ts4.8/globals.d.ts:325:84 -
error TS2307: Cannot find module 'undici-types' or its corresponding
type declarations.
325 type _Request = typeof globalThis extends { onmessage: any
} ? {} : import("undici-types").Request;
~~
../../../../usr/share/nodejs/@types/node/ts4.8/globals.d.ts:326:85 -
error TS2307: Cannot find module 'undici-types' or its corresponding
type declarations.
326 type _Response = typeof globalThis extends { onmessage:
any } ? {} : import("undici-types").Response;
~~
../../../../usr/share/nodejs/@types/node/ts4.8/globals.d.ts:327:85 -
error TS2307: Cannot find module 'undici-types' or its corresponding
type declarations.
327 type _FormData = typeof globalThis extends { onmessage:
any } ? {} : import("undici-types").FormData;
~~
../../../../usr/share/nodejs/@types/node/ts4.8/globals.d.ts:328:84 -
error TS2307: Cannot find module 'undici-types' or its corresponding
type declarations.
328 type _Headers = typeof globalThis extends { onmessage: any
} ? {} : import("undici-types").Headers;
~~
../../../../usr/share/nodejs/@types/node/ts4.8/globals.d.ts:330:22 -
error TS2307: Cannot find module 'undici-types' or its corresponding
type declarations.
330 : import("undici-types").RequestInit;
~~
../../../../usr/share/nodejs/@types/node/ts4.8/globals.d.ts:336:35 -
error TS2307: Cannot find module 'undici-types' or its corresponding
type declarations.
336 type RequestInfo = import("undici-types").RequestInfo;
~~
../../../../usr/share/nodejs/@types/node/ts4.8/globals.d.ts:337:35 -
error TS2307: Cannot find module 'undici-types' or its corresponding
type declarations.
337 type HeadersInit = import("undici-types").HeadersInit;
~~
../../../../usr/share/nodejs/@types/node/ts4.8/globals.d.ts:338:32 -
error TS2307: Cannot find module 'undici-types' or its corresponding
type declarations.
338 type BodyInit = import("undici-types").BodyInit;
~~
../../../../usr/share/nodejs/@types/node/ts4.8/globals.d.ts:339:39 -
error TS2307: Cannot find module 'undici-types' or its corresponding
type declarations.
339 type RequestRedirect = import("undici-types").RequestRedirect;
~~
../../../../usr/share/nodejs/@types/node/ts4.8/globals.d.ts:340:42 -
error TS2307: Cannot find module 'undici-types' or its corresponding
type declarations.
340 type RequestCredentials = import("undici-types").RequestCredentials;
~~
../../../../usr/share/nodejs/@types/node/ts4.8/globals.d.ts:341:35 -
error TS2307: Cannot find module 'undici-types' or its corresponding
type declarations.
341 type RequestMode = import("undici-types").RequestMode;
~~
../../../../usr/share/nodejs/@types/node/ts4.8/globals.d.ts:342:38 -
error TS2307: Cannot find module 'undici-types' or its corresponding
type declarations.
342 type ReferrerPolicy = import("undici-types").ReferrerPolicy;
~~
../../../../usr/share/nodejs/@types/node/ts4.8/globals.d.ts:343:34 -
error TS2307: Cannot find module 'undici-types' or its corresponding
type declarations.
343 type Dispatcher = import("undici-types").Dispatcher;
~~
../../../../usr/share/nodejs/@types/node/ts4.8/globals.d.ts:344:37 -
error TS2307: Cannot find module
Processed: Re: gem2deb rails assets smoke test should handle links or skip the test during build
Processing control commands: > severity -1 serious Bug #1063478 [gem2deb] gem2deb rails assets smoke test should handle links or skip the test during build Severity set to 'serious' from 'normal' -- 1063478: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1063478 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: einsteinpy: test_plotting fails to converge with scipy 1.11
Processing control commands: > block 1061605 by -1 Bug #1061605 [src:scipy] scipy: tests skipped during build and autopkgtest not in sync 1061605 was blocked by: 1063526 1061605 was not blocking any bugs. Added blocking bug(s) of 1061605: 1063527 -- 1061605: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1061605 1063527: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1063527 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: astroml: test_iterative_PCA fails with scipy 1.11: unexpected keyword argument 'sym_pos'
Processing control commands: > block 1061605 by -1 Bug #1061605 [src:scipy] scipy: tests skipped during build and autopkgtest not in sync 1061605 was not blocked by any bugs. 1061605 was not blocking any bugs. Added blocking bug(s) of 1061605: 1063526 -- 1061605: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1061605 1063526: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1063526 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: lockdown FTBFS due to B-D: dh-systemd
Processing control commands: > retitle -1 lockdown FTBFS: Build-Depends on deprecated dh-systemd which is no > longer available Bug #958587 [src:lockdown] lockdown: Build-Depends on deprecated dh-systemd which is going away Changed Bug title to 'lockdown FTBFS: Build-Depends on deprecated dh-systemd which is no longer available' from 'lockdown: Build-Depends on deprecated dh-systemd which is going away'. > tags -1 + ftbfs Bug #958587 [src:lockdown] lockdown FTBFS: Build-Depends on deprecated dh-systemd which is no longer available Added tag(s) ftbfs. -- 958587: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=958587 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: use of dh_dkms without b-d: dh-dkms is a FTBFS
Processing control commands: > retitle -1 kpatch FTBFS: please switch to B-D: dh-sequence-dkms (or dh-dkms) Bug #1027889 [src:kpatch] kpatch: please switch to B-D: dh-sequence-dkms (or dh-dkms) Changed Bug title to 'kpatch FTBFS: please switch to B-D: dh-sequence-dkms (or dh-dkms)' from 'kpatch: please switch to B-D: dh-sequence-dkms (or dh-dkms)'. > tags -1 + ftbfs Bug #1027889 [src:kpatch] kpatch FTBFS: please switch to B-D: dh-sequence-dkms (or dh-dkms) Added tag(s) ftbfs. -- 1027889: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1027889 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1063525: d-spy FTBFS with nocheck profile: ../meson.build:187:6: ERROR: Program 'update-desktop-database' not found or not executable
Source: d-spy Version: 1.8.0-1 Severity: serious Tags: ftbfs trixie sid d-spy fails to build from source when built with the nocheck build profile. Since trixie such a failure is considered release-critical. A build ends with: | ../meson.build:187:6: ERROR: Program 'update-desktop-database' not found or not executable | dh_auto_configure: error: cd obj-x86_64-linux-gnu && DEB_PYTHON_INSTALL_LAYOUT=deb LC_ALL=C.UTF-8 meson setup .. --wrap-mode=nodownload --buildtype=plain --prefix=/usr --sysconfdir=/etc --localstatedir=/var --libdir=lib/x86_64-linux-gnu -Dpython.bytecompile=-1 returned exit code 1 | make: *** [debian/rules:8: binary] Error 25 | dpkg-buildpackage: error: debian/rules binary subprocess returned exit status 2 Helmut
Bug#958587: lockdown FTBFS due to B-D: dh-systemd
Control: retitle -1 lockdown FTBFS: Build-Depends on deprecated dh-systemd which is no longer available Control: tags -1 + ftbfs This bug has become a FTBFS. Tagging as such. Helmut
Bug#1027889: use of dh_dkms without b-d: dh-dkms is a FTBFS
Control: retitle -1 kpatch FTBFS: please switch to B-D: dh-sequence-dkms (or dh-dkms) Control: tags -1 + ftbfs Using dh_dkms without Build-Depends: dh-dkms makes the package ftbfs: | make[1]: dh_dkms: No such file or directory | make[1]: *** [debian/rules:23: override_dh_install] Error 127 | make[1]: Leaving directory '/<>' | make: *** [debian/rules:11: binary] Error 2 | dpkg-buildpackage: error: fakeroot debian/rules binary subprocess returned exit status 2 Andreas filed the bug at serious severity, but it doesn't yet correctly identify as FTBFS. Helmut
Bug#1063518: console-setup: setupcon: 1386: Syntax error: Missing '))'
Package: console-setup
Version: 1.225
Severity: grave
After the upgrade from 1.223, console-setup.service failed to start due
to a syntax error in the setupcon script:
,
| $ setupcon
| /usr/bin/setupcon: 1386: Syntax error: Missing '))'
`
It looks like dash does not like the construct in line 907 where there
is an opening '$((' but the closing parentheses are split.
,
| $ dash << 'EOF'
| > echo $((true))
| > echo $((true) )
| > EOF
| 0
| dash: 3: Syntax error: Missing '))'
| $
`
-- System Information:
Debian Release: trixie/sid
APT prefers unstable
APT policy: (500, 'unstable'), (101, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386
Bug#1051017: marked as done (cdo: Major data error with ICON files)
Your message dated Fri, 09 Feb 2024 12:19:30 + with message-id and subject line Bug#1051017: fixed in cdo 2.3.0-3 has caused the Debian Bug report #1051017, regarding cdo: Major data error with ICON files 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 responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 1051017: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1051017 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: cdo Version: 2.2.1 Severity: serious Tags: upstream Justification: 2 X-Debbugs-Cc: Momtchil Momtchev Just a heads up that there is a serious issue with the cdo version in bookworm - it produces broken (flipped on the Y-axis) GRIBs when "remapping" (extracting) data from the ICON output files. The one in bullseye works correctly. As this is probably the number one reason commoners use cdo, it is a major showstopper. Here is the original bug report: https://code.mpimet.mpg.de/boards/1/topics/14808 The issue has been fixed in 2.2.2. -- System Information: Debian Release: 12.1 APT prefers stable-security APT policy: (500, 'stable-security'), (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 6.1.0-11-amd64 (SMP w/4 CPU threads; PREEMPT) Locale: LANG=en_IE.UTF-8, LC_CTYPE=en_IE.UTF-8 (charmap=UTF-8) (ignored: LC_ALL set to en_IE.UTF-8), LANGUAGE=en_IE:en Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages cdo depends on: ii libc6 2.36-9+deb12u1 pn libcdi0 ii libcurl3-gnutls 7.88.1-10+deb12u1 ii libfftw3-double3 3.3.10-1 ii libgcc-s1 12.2.0-14 ii libgomp1 12.2.0-14 pn libhdf5-103-1 pn libmagplus3v5 pn libnetcdf19 pn libproj25 ii libstdc++612.2.0-14 pn libudunits2-0 Versions of packages cdo recommends: pn python3-cdo cdo suggests no packages. --- End Message --- --- Begin Message --- Source: cdo Source-Version: 2.3.0-3 Done: Alastair McKinstry We believe that the bug you reported is fixed in the latest version of cdo, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 1051...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Alastair McKinstry (supplier of updated cdo package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Fri, 09 Feb 2024 11:52:03 + Source: cdo Architecture: source Version: 2.3.0-3 Distribution: unstable Urgency: medium Maintainer: Alastair McKinstry Changed-By: Alastair McKinstry Closes: 1051017 Changes: cdo (2.3.0-3) unstable; urgency=medium . * Typo in d/rules led to non-usage of libxml2 * AS_NEEDED not needed in d/rules * Drop usage of patchelf as it was breaking mips64el builds * Mark bug as fixed in 2.3.0. Closes: #1051017 Checksums-Sha1: f78bf266c2fba408543c1b98cec35c53cf5ce397 2366 cdo_2.3.0-3.dsc 89ea47ffdd7b0784ee038ba2705651735b21ff77 12352 cdo_2.3.0-3.debian.tar.xz Checksums-Sha256: 836303b85a1bf3c5374f4e6dff4855031256f3abff92abb55b7bcc9ad1acff22 2366 cdo_2.3.0-3.dsc b5b805719ad139b05db57f907ee2f02fdcc11524b4c597c9af542e4f82b9403d 12352 cdo_2.3.0-3.debian.tar.xz Files: 909c44c848d231b1717a8d8d043d427f 2366 utils optional cdo_2.3.0-3.dsc 1069e7bd5cdf21251cafbba51151bfd9 12352 utils optional cdo_2.3.0-3.debian.tar.xz -BEGIN PGP SIGNATURE- iQIzBAEBCAAdFiEEgjg86RZbNHx4cIGiy+a7Tl2a06UFAmXGFhAACgkQy+a7Tl2a 06Wlxg//ewMbNj8Xclg9PdBRiz/B8m+2xawkVjWd4hpfNs+qGPoTNARYp/QIAc8z YawWluBXpbeBgGlWd46Ts5H8sl7Cx2Qz3GqrwwHipCLg5Ba3SUfseaONgAVz7rMK nqOop81o89LZkkF5JEQpsOC5p23TYp1DBrOle0e1y4QjyTNXGJDurfmlzwDwgkrt cmx3nOMzr0/X54XTk30CLsZpmL5sJ/wj/m87G8buwSc3v85BpsE454hYeyEYiTk9 1LelLwWKYegM/1OfZx3QnV5NG8BOsQqETZwOfuZhd91ZFpcKzuVntPIu6RfNlINX rOPTMSnUi9FhJHrY0W6UVnoo4sxOkNtl7LScCNTxXVcth35E3MykbxWtNHr+dnnA srJgTxEmt6Q+SVQ2ZFQPk5VVhk0zUvBFYteCeAiy4EWQT8adyBW8jK9uC12eZXa8 Di21T4wFApUYdkVj7NhpDOVMbBwGGFqM9RjeQqfOuWaOHZ3MfYeqKIqFa/4Pe1bo vosrYwqtN/hwpFvDwREOBuj40z96DAsLQhbQvLYfB+cgcLj9EsMdEsltRZ4uO65o t4uWjWn0wFx9DOtbRJXwHZEkXb86QEoVV6lVh6uvnmpbd8+alPbeNWzCxftZgyO7 kqVzvh3RKvU4RGBjXJa3s3+DsY5XyFTpWdMzLNqY49pg9DSeU3I= =GOcn -END PGP SIGNATURE End Message ---
Processed: Re: comitup fails its autopkg tests with Python 3.12
Processing control commands: > severity -1 serious Bug #1061791 [src:comitup] comitup fails its autopkg tests with Python 3.12 Severity set to 'serious' from 'important' > tags -1 +patch Bug #1061791 [src:comitup] comitup fails its autopkg tests with Python 3.12 Added tag(s) patch. -- 1061791: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1061791 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: django-rich: upstream patch to fix the test failure on Python 3.12
Processing control commands: > tags -1 patch Bug #1061740 [src:django-rich] django-rich ftbfs with Python 3.12 as default Ignoring request to alter tags of bug #1061740 to the same tags previously set -- 1061740: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1061740 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1061740: django-rich: upstream patch to fix the test failure on Python 3.12
Package: django-rich
Version: 1.8.0-1
Followup-For: Bug #1061740
User: ubuntu-de...@lists.ubuntu.com
Usertags: origin-ubuntu noble ubuntu-patch
X-Debbugs-Cc: ravi.kant.sha...@canonical.com
Control: tags -1 patch
Dear Maintainer,
In Ubuntu, the attached patch was applied to achieve the following:
* The bug was identified during Ubuntu Noble migration to Python 3.12.
* The patch is chery picked commit from upstream.
* Fixes tests on Python-3.12 (LP: #2052724)
Added patch:
tests-Fix-skip-test-for-change-in-Python-3.12.patch
Thanks for considering the patch.
-- System Information:
Debian Release: trixie/sid
APT prefers mantic-updates
APT policy: (500, 'mantic-updates'), (500, 'mantic-security'), (500,
'mantic'), (100, 'mantic-backports')
Architecture: amd64 (x86_64)
Foreign Architectures: i386
Kernel: Linux 6.5.0-15-generic (SMP w/12 CPU threads; PREEMPT)
Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_WARN, TAINT_OOT_MODULE
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
diff -Nru django-rich-1.8.0/debian/patches/series
django-rich-1.8.0/debian/patches/series
--- django-rich-1.8.0/debian/patches/series 2023-01-23 17:48:06.0
+0100
+++ django-rich-1.8.0/debian/patches/series 2024-02-08 18:27:46.0
+0100
@@ -1,3 +1,4 @@
Use-python3-within-test-call.patch
tests-Drop-various-python-version-handling.patch
tests-Another-bunch-of-adoptions-for-Python-3.11.patch
+tests-Fix-skip-test-for-change-in-Python-3.12.patch
diff -Nru
django-rich-1.8.0/debian/patches/tests-Fix-skip-test-for-change-in-Python-3.12.patch
django-rich-1.8.0/debian/patches/tests-Fix-skip-test-for-change-in-Python-3.12.patch
---
django-rich-1.8.0/debian/patches/tests-Fix-skip-test-for-change-in-Python-3.12.patch
1970-01-01 01:00:00.0 +0100
+++
django-rich-1.8.0/debian/patches/tests-Fix-skip-test-for-change-in-Python-3.12.patch
2024-02-08 18:27:46.0 +0100
@@ -0,0 +1,28 @@
+From ddd703aa55cb76c7addd6cc87d4ecdbf695d870b Mon Sep 17 00:00:00 2001
+From: Adam Johnson
+Date: Tue, 19 Dec 2023 23:13:56 +
+Subject: [PATCH] Fix skip test for change in Python 3.12 (#172)
+Origin: upstream,
https://github.com/adamchainz/django-rich/commit/ddd703aa55cb76c7addd6cc87d4ecdbf695d870b
+Bug: https://bugs.launchpad.net/debian/+source/django-rich/+bug/2052724
+Bug-Debian: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1061740
+
+---
+ tests/test_test.py | 5 ++---
+ 1 file changed, 2 insertions(+), 3 deletions(-)
+
+diff --git a/tests/test_test.py b/tests/test_test.py
+index 86eac20..2b69bba 100644
+--- a/tests/test_test.py
b/tests/test_test.py
+@@ -36,9 +36,8 @@ def test_failure_sql_query(self):
+ )
+ self.assertTrue(False)
+
+-@unittest.skip("some reason")
+-def test_skip(self): # pragma: no cover
+-raise ValueError("never run")
++def test_skip(self):
++self.skipTest("some reason")
+
+ @unittest.expectedFailure
+ def test_expected_failure(self):
Processed: django-rich: upstream patch to fix the test failure on Python 3.12
Processing control commands: > tags -1 patch Bug #1061740 [src:django-rich] django-rich ftbfs with Python 3.12 as default Added tag(s) patch. -- 1061740: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1061740 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1061740: django-rich: upstream patch to fix the test failure on Python 3.12
Package: django-rich Version: 1.8.0-1 Followup-For: Bug #1061740 User: ubuntu-de...@lists.ubuntu.com Usertags: origin-ubuntu noble ubuntu-patch X-Debbugs-Cc: ravi.kant.sha...@canonical.com Control: tags -1 patch Dear Maintainer, In Ubuntu, the attached patch was applied to achieve the following: Fix a test failure identified during Python migration to 3.12. The patch cherry picks commit form upstream to fix the test case. * Fixes tests on Python-3.12 (LP: #2052724) Added patch: tests-Fix-skip-test-for-change-in-Python-3.12.patch Thanks for considering the patch. -- System Information: Debian Release: trixie/sid APT prefers mantic-updates APT policy: (500, 'mantic-updates'), (500, 'mantic-security'), (500, 'mantic'), (100, 'mantic-backports') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 6.5.0-15-generic (SMP w/12 CPU threads; PREEMPT) Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_WARN, TAINT_OOT_MODULE Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE not set Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled django-rich_1.8.0-1ubuntu1.debdiff Description: inode/empty
Bug#1061440: azure-cosmos-table-python: autopkgtest failure with Python 3.12
Source: azure-cosmos-table-python Followup-For: Bug #1061440 This package is deprecated, in favor of the python3-azure debian package. Please don't fix this bug, and let's get this eventually autoremoved. -- System Information: Debian Release: trixie/sid APT prefers testing APT policy: (101, 'testing') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 6.6.13-amd64 (SMP w/4 CPU threads; PREEMPT) Locale: LANG=fr_FR.utf8, LC_CTYPE=fr_FR.utf8 (charmap=UTF-8), LANGUAGE not set Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled
Processed: Fixed Python3.12 issue but astropy issue is pending (Was: aplpy's autopkg tests fail with Python 3.12)
Processing control commands: > tags -1 pending Bug #1056227 [src:aplpy] aplpy's autopkg tests fail with Python 3.12 Added tag(s) pending. -- 1056227: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1056227 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1056227: Fixed Python3.12 issue but astropy issue is pending (Was: aplpy's autopkg tests fail with Python 3.12)
Control: tags -1 pending Hi Ole, I've fixed the distutils issue of Python3.12 in Git but there is an issue pending which you probably can solve way more easier than I: from astropy.config.configuration import ( E ImportError: cannot import name 'update_default_config' from 'astropy.config.configuration' (/usr/lib/python3/dist-packages/astropy/config/configuration.py) (See Salsa CI https://salsa.debian.org/debian-astro-team/aplpy/-/jobs/5270405) Kind regards Andreas. -- http://fam-tille.de
Processed: not yet serious
Processing commands for cont...@bugs.debian.org: > severity 1062272 important Bug #1062272 [src:libdnf] libdnf: NMU diff for 64-bit time_t transition Severity set to 'important' from 'serious' > # downgrading to prevent autoremoval, this is not serious yet > thanks Stopping processing here. Please contact me if you need assistance. -- 1062272: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1062272 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1063446: libmozjs-115-dev: cannot call JS::CanonicalizeNaN(double) on mips64el
Hi Simon, On 08/02/2024 21:59, Simon McVittie wrote: On Thu, 08 Feb 2024 at 10:37:33 +, Simon McVittie wrote: Package: libmozjs-115-dev Justification: makes gjs FTBFS (#1063433) I believe mozjs115_115.7.0-3 should fix this. wb-team: Please could someone with wanna-build access schedule gjs on mips64el to be built after the fixed version of mozjs115 becomes available? I believe the correct spelling is: dw gjs_1.78.3-1 . unstable . mips64el . -m 'libmozjs-115-dev (>= 115.7.0-3)' mozjs115 is already built, so I just gave gjs back. Cheers, Emilio
