Bug#1052888: epics-base: FTBFS: make[2]: *** [configure/RULES_TOP:62: runtests] Error 1
Control: tags -1 + unreproducible On Tue, 26 Sep 2023 15:34:01 +0200 Lucas Nussbaum wrote: Source: epics-base Version: 7.0.7+dfsg1-5 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. I cannot reproduce the issue on amd64. From your log the relevant part seems to be the following: epicsEventTrigger: pthread_mutex_lock failed: Invalid argument epicsEventMustTriggerThread CAC-event (0x7f4370025b30) can't proceed, suspending. Dumping a stack trace of thread 'CAC-event': [0x7f4384e76943]: /<>/lib/linux-x86_64/libCom.so.3.22.0(epicsStackTrace+0x73) [0x7f4384e679a9]: /<>/lib/linux-x86_64/libCom.so.3.22.0(cantProceed+0xc9) [0x7f4384eec0b1]: /<>/lib/linux-x86_64/libdbCore.so.3.22.0(testdbCaWaitForEventCB+0x21) [0x7f4384b4a2bc]: /<>/lib/linux-x86_64/libca.so.4.14.2(_ZN15oldSubscription7currentER10epicsGuardI10epicsMutexEjmPKv+0x6c) [0x7f4384ef052a]: /<>/lib/linux-x86_64/libdbCore.so.3.22.0(_ZN9dbContext15callStateNotifyEP9dbChanneljmPK12db_field_logR14cacStateNotify+0x17a) [0x7f4384ee4645]: /<>/lib/linux-x86_64/libdbCore.so.3.22.0(event_task+0x1e5) [0x7f4384e70842]: /<>/lib/linux-x86_64/libCom.so.3.22.0(start_routine+0xd2) [0x7f4384cd13ec]: /lib/x86_64-linux-gnu/libc.so.6(pthread_condattr_setpshared+0x4cc) [0x7f4384d51a2c]: /lib/x86_64-linux-gnu/libc.so.6(__clone+0x11c) Thread CAC-event (0x7f4370025b30) suspended regressTest.t: Timed out './regressTest' after 500 seconds regressTest.t ... I think the test has timed out due to the high load of the building machine. If this persists, increasing the timeout value could be a solution. Cheers, Andrius
Processed: Re: epics-base: FTBFS: make[2]: *** [configure/RULES_TOP:62: runtests] Error 1
Processing control commands: > tags -1 + unreproducible Bug #1052888 [src:epics-base] epics-base: FTBFS: make[2]: *** [configure/RULES_TOP:62: runtests] Error 1 Added tag(s) unreproducible. -- 1052888: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1052888 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1052847: python-marshmallow: FTBFS: dh_auto_test: error: pybuild --test -i python{version} -p 3.11 returned exit code 13
On Tue, 26 Sep 2023 15:23:12 +0200 Lucas Nussbaum wrote:
> During a rebuild of all packages in sid, your package failed to build
> on amd64.
...
> > ImportError while loading conftest
> > '/<>/.pybuild/cpython3_3.11_marshmallow/build/tests/conftest.py'.
> > tests/conftest.py:4: in
> > from tests.base import User, UserSchema, Blog
> > tests/base.py:14: in
> > central = pytz.timezone("US/Central")
> > /usr/lib/python3/dist-packages/pytz/__init__.py:202: in timezone
> > raise UnknownTimeZoneError(zone)
> > E pytz.exceptions.UnknownTimeZoneError: 'US/Central'
This was caused by the split of tzdata-legacy from tzdata, the fix is
to add tzdata-legacy to build-depends and I notice that you already
fixed the issue in git and tagged an upload but haven't uploaded yet.
Would you like me to upload for you or can you take care of it?
--
bye,
pabs
https://wiki.debian.org/PaulWise
signature.asc
Description: This is a digitally signed message part
Bug#1052835: marked as pending in utf8proc
On Sat, 30 Sep 2023 18:35:04 + Mo Zhou wrote: > Bug #1052835 in utf8proc 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/julia-team/utf8proc/-/commit/ba942e99629cb82bf92805c10e407826ac22bf24 > > > Patch to support unicode-data 15.1.0 (Closes: #1052835) > I note that this RC-bug-fix hasn't been uploaded yet nor sent upstream, would you and the Julia team like some help with those tasks? -- bye, pabs https://wiki.debian.org/PaulWise signature.asc Description: This is a digitally signed message part
Processed: Re: libdbd-odbc-perl: Test failure in t/rt_57957.t
Processing control commands: > reassign -1 libsqliteodbc 0.-1 Bug #1052327 [src:libdbd-odbc-perl] libdbd-odbc-perl: Test failure in t/rt_57957.t Bug reassigned from package 'src:libdbd-odbc-perl' to 'libsqliteodbc'. No longer marked as found in versions libdbd-odbc-perl/1.61-2. Ignoring request to alter fixed versions of bug #1052327 to the same values previously set Bug #1052327 [libsqliteodbc] libdbd-odbc-perl: Test failure in t/rt_57957.t Marked as found in versions sqliteodbc/0.-1. > retitle -1 libsqliteodbc: regression: crashes (SIGSEGV) with line comments Bug #1052327 [libsqliteodbc] libdbd-odbc-perl: Test failure in t/rt_57957.t Changed Bug title to 'libsqliteodbc: regression: crashes (SIGSEGV) with line comments' from 'libdbd-odbc-perl: Test failure in t/rt_57957.t'. > affects -1 + libdbd-odbc-perl Bug #1052327 [libsqliteodbc] libsqliteodbc: regression: crashes (SIGSEGV) with line comments Added indication that 1052327 affects libdbd-odbc-perl > tags -1 + patch Bug #1052327 [libsqliteodbc] libsqliteodbc: regression: crashes (SIGSEGV) with line comments Added tag(s) patch. > forwarded -1 Christian Werner Bug #1052327 [libsqliteodbc] libsqliteodbc: regression: crashes (SIGSEGV) with line comments Set Bug forwarded-to-address to 'Christian Werner '. -- 1052327: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1052327 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1052327: libdbd-odbc-perl: Test failure in t/rt_57957.t
Control: reassign -1 libsqliteodbc 0.-1
Control: retitle -1 libsqliteodbc: regression: crashes (SIGSEGV) with line
comments
Control: affects -1 + libdbd-odbc-perl
Control: tags -1 + patch
Control: forwarded -1 Christian Werner
On Wed, 20 Sep 2023 17:00:50 +0200 gregor herrmann wrote:
> As noticed by ci.debian.org, t/rt_57957.t started to fail at some
> point between 2023-09-02 and 2023-09-18.
The two tests that fail are the line comment ones:
4 - Prepare with line comment named placeholder
6 - Prepare with line comment and ? placeholder
They both fail by causing a SIGSEGV in Perl itself.
Executing the same SQL within sqlite3 does not cause a SIGSEGV:
$ sqlite3
SQLite version 3.43.1 2023-09-11 12:01:27
Enter ".help" for usage hints.
Connected to a transient in-memory database.
Use ".open FILENAME" to reopen on a persistent database.
sqlite> select -- placeholder ? in a comment
1;
1
When I modify the SQL a bit so that gdb can actually load the core dump
from inside pbuilder, I get a backtrace inside sqliteodbc.
When I downgrade libsqliteodbc from 0.-1 to 0.9998-3+b1 then the
crash no longer happens, so this is a bug in sqliteodbc.
When I modify the pyodbc tests to include a test with a line comment,
then I get a Python crash and the crash is fixed with 0.9998-3+b1.
Looking at the diff from 0.9998-3 to 0.-1, I see that this version
added support for line comments by adding this case to the code:
case '-':
*p++ = *q;
if (!inq && q[1] == '-') {
++q;
while (*q) {
*p++ = *q;
if (*q == '\n') {
break;
}
}
}
break;
So this is crashing because the q pointer isn't getting incremented so
it never reaches the \n character nor the end of the SQL string, but
the p pointer is getting incremented within the infinite loop, so it
gets incremented past the end of its allocated memory.
The fix is to increment both pointers at once.
*p++ = *q++;
This fixes the libdbd-odbc-perl test failures too.
I have sent the attached patch to upstream.
--
bye,
pabs
https://wiki.debian.org/PaulWise
From 0bc7d682561c1a3e4cec4627e45c8cefa91f14a9 Mon Sep 17 00:00:00 2001
From: Paul Wise
Date: Tue, 10 Oct 2023 12:45:17 +0800
Subject: [PATCH] Fix crash with line comments in SQL fixup
The handling of line comments is crashing because the q pointer isn't
getting incremented so it never reaches the \n character nor the end
of the SQL string, but the p pointer is getting incremented within the
infinite loop, so it gets incremented past the end of its allocated memory.
This crash was introduced in version 0..
---
sqlite3odbc.c | 2 +-
sqlite4odbc.c | 2 +-
sqliteodbc.c | 2 +-
3 files changed, 3 insertions(+), 3 deletions(-)
diff --git a/sqlite3odbc.c b/sqlite3odbc.c
index 94b407e..27f394f 100644
--- a/sqlite3odbc.c
+++ b/sqlite3odbc.c
@@ -2581,7 +2581,7 @@ errout:
if (!inq && q[1] == '-') {
++q;
while (*q) {
- *p++ = *q;
+ *p++ = *q++;
if (*q == '\n') {
break;
}
diff --git a/sqlite4odbc.c b/sqlite4odbc.c
index 78f2b1e..031cd1f 100644
--- a/sqlite4odbc.c
+++ b/sqlite4odbc.c
@@ -2561,7 +2561,7 @@ errout:
if (!inq && q[1] == '-') {
++q;
while (*q) {
- *p++ = *q;
+ *p++ = *q++;
if (*q == '\n') {
break;
}
diff --git a/sqliteodbc.c b/sqliteodbc.c
index c9c7a29..bad61ab 100644
--- a/sqliteodbc.c
+++ b/sqliteodbc.c
@@ -1730,7 +1730,7 @@ errout:
if (!inq && q[1] == '-') {
++q;
while (*q) {
- *p++ = *q;
+ *p++ = *q++;
if (*q == '\n') {
break;
}
--
2.42.0
signature.asc
Description: This is a digitally signed message part
Processed: tags changes for 942501
Processing commands for cont...@bugs.debian.org: > tags 942501 - bookworm Bug #942501 [src:milter-greylist] src:milter-greylist: please drop libbind-dev build dependency, it's not in use and libbind-dev is going away Removed tag(s) bookworm. > thanks Stopping processing here. Please contact me if you need assistance. -- 942501: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=942501 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#942501: src:milter-greylist: please drop libbind-dev build dependency, it's not in use and libbind-dev is going away
Control: tags -1 pending X-Debbugs-CC: Tobias Frost Tobi, would you please sponsor this to unstable? https://salsa.debian.org/debian/milter-greylist I'll start work on #1002527 shortly. Thanks, -a
Processed: Re: src:milter-greylist: please drop libbind-dev build dependency, it's not in use and libbind-dev is going away
Processing control commands: > tags -1 pending Bug #942501 [src:milter-greylist] src:milter-greylist: please drop libbind-dev build dependency, it's not in use and libbind-dev is going away Added tag(s) pending. -- 942501: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=942501 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1052812: marked as done (python-pytest-timeout: FTBFS: dh_auto_test: error: pybuild --test --test-pytest -i python{version} -p 3.11 returned exit code 13)
Your message dated Tue, 10 Oct 2023 00:49:00 +
with message-id
and subject line Bug#1052812: fixed in python-pytest-timeout 2.2.0-1
has caused the Debian Bug report #1052812,
regarding python-pytest-timeout: FTBFS: dh_auto_test: error: pybuild --test
--test-pytest -i python{version} -p 3.11 returned exit code 13
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.)
--
1052812: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1052812
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: python-pytest-timeout
Version: 2.1.0-3
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):
> debian/rules binary
> dh binary --buildsystem=pybuild --with python3
>dh_update_autotools_config -O--buildsystem=pybuild
>dh_autoreconf -O--buildsystem=pybuild
>dh_auto_configure -O--buildsystem=pybuild
> I: pybuild base:291: python3.11 setup.py config
> running config
>dh_auto_build -O--buildsystem=pybuild
> I: pybuild base:291: /usr/bin/python3 setup.py build
> running build
> running build_py
> copying pytest_timeout.py ->
> /<>/.pybuild/cpython3_3.11_python-pytest-timeout/build
>dh_auto_test -O--buildsystem=pybuild
> I: pybuild base:291: cd
> /<>/.pybuild/cpython3_3.11_python-pytest-timeout/build;
> python3.11 -m pytest
> = test session starts
> ==
> platform linux -- Python 3.11.5, pytest-7.4.2, pluggy-1.3.0
> rootdir: /<>
> configfile: tox.ini
> plugins: cov-4.1.0
> collected 33 items
>
> test_pytest_timeout.py FFF..FF.xx.FF
> [100%]
>
> === FAILURES
> ===
> _ test_header
> __
>
> testdir =
>
> def test_header(testdir):
> testdir.makepyfile(
> """
> def test_x(): pass
> """
> )
> result = testdir.runpytest("--timeout=1")
> > result.stdout.fnmatch_lines(
> ["timeout: 1.0s", "timeout method:*", "timeout func_only:*"]
> )
> E Failed: remains unmatched: 'timeout: 1.0s'
>
> /<>/.pybuild/cpython3_3.11_python-pytest-timeout/build/test_pytest_timeout.py:35:
> Failed
> - Captured stdout call
> -
> running: /usr/bin/python3.11 -mpytest
> --basetemp=/tmp/pytest-of-user42/pytest-9/test_header0/runpytest-0 --timeout=1
> in: /tmp/pytest-of-user42/pytest-9/test_header0
> - Captured stderr call
> -
> ERROR: usage: __main__.py [options] [file_or_dir] [file_or_dir] [...]
> __main__.py: error: unrecognized arguments: --timeout=1
> inifile: None
> rootdir: /tmp/pytest-of-user42/pytest-9/test_header0
>
> _ test_sigalrm
> _
>
> testdir =
>
> @have_sigalrm
> def test_sigalrm(testdir):
> testdir.makepyfile(
> """
> import time
>
> def test_foo():
> time.sleep(2)
> """
> )
> result = testdir.runpytest("--timeout=1")
> > result.stdout.fnmatch_lines(["*Failed: Timeout >1.0s*"])
> E Failed: remains unmatched: '*Failed: Timeout >1.0s*'
>
> /<>/.pybuild/cpython3_3.11_python-pytest-timeout/build/test_pytest_timeout.py:51:
> Failed
> - Captured stdout call
> -
> running: /usr/bin/python3.11 -mpytest
> --basetemp=/tmp/pytest-of-user42/pytest-9/test_sigalrm0/runpytest-0
> --timeout=1
> in: /tmp/pytest-of-user42/pytest-9/test_sigalrm0
> - Captured stderr call
> -
> ERROR: usage: __main__.py [options] [file_or_dir] [file_or_dir] [...]
> __main__.py: error: unrecognized arguments: --timeout=1
> inifile: None
> rootdir: /tmp/pytest-of-user42/pytest-9/test_sigalrm0
>
> _ test_thread
> __
>
> testdir =
>
> def test_thread(testdir):
> testdir.makepyfile(
> """
> import time
>
> def test_foo():
> time.sleep(2)
> """
> )
> result = testdir.runpytest("--timeout=1", "--timeout-method=thread")
> > result.stderr.fnmatch_lines(
>
Bug#1052812: marked as pending in python-pytest-timeout
Control: tag -1 pending Hello, Bug #1052812 in python-pytest-timeout 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/python-team/packages/python-pytest-timeout/-/commit/5b439776f7bb87c4f53bad8668fe82698e91b9e5 Switch to pyproject build (Closes: #1052812) (this message was generated automatically) -- Greetings https://bugs.debian.org/1052812
Processed: Bug#1052812 marked as pending in python-pytest-timeout
Processing control commands:
> tag -1 pending
Bug #1052812 [src:python-pytest-timeout] python-pytest-timeout: FTBFS:
dh_auto_test: error: pybuild --test --test-pytest -i python{version} -p 3.11
returned exit code 13
Added tag(s) pending.
--
1052812: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1052812
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Bug#1038687: radicale's autopkg tests fail with Python 3.11.4
The latest upload also have the failing autopkgtest checks, https://ci.debian.net/data/autopkgtest/unstable/amd64/r/radicale/38824358/log.gz > -- Happy hacking Petter Reinholdtsen
Bug#1051159: marked as done (gnome-packagekit: FTBFS: gnome-packagekit-self-test FAIL)
Your message dated Mon, 09 Oct 2023 22:19:03 + with message-id and subject line Bug#1051159: fixed in gnome-packagekit 43.0-2 has caused the Debian Bug report #1051159, regarding gnome-packagekit: FTBFS: gnome-packagekit-self-test FAIL 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.) -- 1051159: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1051159 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: gnome-packagekit Version: 43.0-1 Severity: serious Tags: ftbfs Justification: fails to build from source (but built successfully in the past) Dear maintainer, gnome-packagekit fails to build from source due to an issue in the testsuite. From my build log on amd64: | xvfb-run dh_auto_test | cd obj-x86_64-linux-gnu && DEB_PYTHON_INSTALL_LAYOUT=deb LC_ALL=C.UTF-8 MESON_TESTTHREADS=1 meson test | ninja: Entering directory `/<>/obj-x86_64-linux-gnu' | ninja: no work to do. | 1/1 gnome-packagekit-self-test FAIL0.22s killed by signal 5 SIGTRAP | >>> MALLOC_PERTURB_=101 /<>/obj-x86_64-linux-gnu/src/gpk-self-test | | | Ok: 0 | Expected Fail: 0 | Fail: 1 | Unexpected Pass:0 | Skipped:0 | Timeout:0 | | Full log written to /<>/obj-x86_64-linux-gnu/meson-logs/testlog.txt | cd obj-x86_64-linux-gnu && tail -v -n \+0 meson-logs/testlog.txt | ==> meson-logs/testlog.txt <== | Log of Meson test suite run on 2023-09-03T10:39:44.785950 | | Inherited environment: DEB_HOST_GNU_SYSTEM=linux-gnu DFLAGS=-frelease DEB_BUILD_ARCH_BITS=64 DEB_TARGET_GNU_CPU=x86_64 DEB_HOST_ARCH_OS=linux USER=aurel32 CXXFLAGS='-g -O2 -ffile-prefix-map=/<>=. -fstack-protector-strong -fstack-clash-protection -Wformat -Werror=format-security -fcf-protection' DEB_BUILD_GNU_TYPE=x86_64-linux-gnu DEB_TARGET_MULTIARCH=x86_64-linux-gnu OBJCFLAGS='-g -O2 -ffile-prefix-map=/<>=. -fstack-protector-strong -fstack-clash-protection -Wformat -Werror=format-security -fcf-protection' DH_INTERNAL_OPTIONS=-a DEB_BUILD_ARCH_CPU=amd64 DEB_HOST_ARCH_LIBC=gnu DEB_HOST_ARCH_ABI=base HOME=/<>/debian/.debhelper/generated/_source/home APT_CONFIG=/var/lib/sbuild/apt.conf SCHROOT_CHROOT_NAME=sid-amd64-sbuild DEB_BUILD_ARCH_ENDIAN=little LDFLAGS=-Wl,-z,relro DEB_TARGET_ARCH_BITS=64 DEB_BUILD_GNU_SYSTEM=linux-gnu MAKEFLAGS=w SCHROOT_UID=1000 DEB_BUILD_ARCH_OS=linux DEB_TARGET_GNU_TYPE=x86_64-linux-gnu DEB_TARGET_ARCH_CPU=amd64 LOGNAME=aurel32 DEB_BUILD_ARCH_LIBC=gnu DEB_BUILD_ARCH_ABI=base DEB_HOST_ARCH=amd64 DEB_TARGET_ARCH_ENDIAN=little DH_INTERNAL_OVERRIDE=dh_auto_test DEB_HOST_GNU_CPU=x86_64 LC_COLLATE=C.UTF-8 DEB_TARGET_GNU_SYSTEM=linux-gnu PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games DEB_TARGET_ARCH_OS=linux CFLAGS='-g -O2 -ffile-prefix-map=/<>=. -fstack-protector-strong -fstack-clash-protection -Wformat -Werror=format-security -fcf-protection' MAKELEVEL=2 DEB_HOST_MULTIARCH=x86_64-linux-gnu SOURCE_DATE_EPOCH=1668444324 FCFLAGS='-g -O2 -ffile-prefix-map=/<>=. -fstack-protector-strong -fstack-clash-protection -fcf-protection' SCHROOT_SESSION_ID=sid-amd64-sbuild-de330d22-e06b-4bad-9ea9-b7730d412354 SCHROOT_COMMAND='dpkg-buildpackage --sanitize-env -us -uc -mAurelien Jarno -eAurelien Jarno -B -rfakeroot' DISPLAY=:99 OBJCXXFLAGS='-g -O2 -ffile-prefix-map=/<>=. -fstack-protector-strong -fstack-clash-protection -Wformat -Werror=format-security -fcf-protection' LANG=fr_FR.UTF-8 SCHROOT_ALIAS_NAME=sid-amd64-sbuild DEB_TARGET_ARCH_LIBC=gnu DEB_TARGET_ARCH_ABI=base XAUTHORITY=/tmp/xvfb-run.G9VJQT/Xauthority DEB_BUILD_OPTIONS=parallel=1 SCHROOT_GROUP=aurel32 SCHROOT_USER=aurel32 CPPFLAGS='-Wdate-time -D_FORTIFY_SOURCE=2' DH_INTERNAL_BUILDFLAGS=1 SHELL=/bin/sh DEB_HOST_ARCH_BITS=64 DEB_BUILD_ARCH=amd64 DEB_BUILD_GNU_CPU=x86_64 ASFLAGS='' DEB_HOST_GNU_TYPE=x86_64-linux-gnu LC_ALL=C.UTF-8 DEB_HOST_ARCH_CPU=amd64 DEB_RULES_REQUIRES_ROOT=no PWD=/<> FFLAGS='-g -O2 -ffile-prefix-map=/<>=. -fstack-protector-strong -fstack-clash-protection -fcf-protection' DEB_BUILD_MULTIARCH=x86_64-linux-gnu SCHROOT_GID=1000 MFLAGS=-w GCJFLAGS='-g -O2 -ffile-prefix-map=/<>=. -fstack-protector-strong -fstack-clash-protection -fcf-protection' DEB_HOST_ARCH_ENDIAN=little DEB_TARGET_ARCH=amd64 XDG_RUNTIME_DIR=/tmp/dh-xdg-rundir-f0RupSXS DEB_PYTHON_INSTALL_LAYOUT=deb MESON_TESTTHREADS=1 | | 1/1 = | test: gnome-packagekit-self-test | start time: 10:39:44 | duration: 0.22s | result: killed by signal 5 SIGTRA
Bug#1052838: [debian-mysql] Bug#1052838: Bug#1052838: mariadb: FTBFS: make[1]: *** [debian/rules:161: override_dh_auto_test] Error 1
I restarted the build for powerpc yesterday, and it did not run into reserved ports issue and build passed. I suspect that this is because the ppc64 build (which runs on the same builder 'blaauw' was not running in parallel and thus the two build jobs were not competing for the same ports on that host. A later restart of ppc64 when the powerpc build had completed likewise did not run into reserved ports issues. Thus I'd say this is a Debian builder problem. The builds should be running inside a container or something so that they can't affect each other.
Bug#1053728: marked as done (FTBFS due to Makefile variable not being set)
Your message dated Mon, 09 Oct 2023 18:52:38 + with message-id and subject line Bug#1053728: fixed in yacas 1.3.6-2.3 has caused the Debian Bug report #1053728, regarding FTBFS due to Makefile variable not being set 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.) -- 1053728: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1053728 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: yacas Version: 1.3.6-2.2 Severity: serious The package fails to build from scratch because $(CXX_FOR_BUILD) is not set properly: o manripper manripper.cpp /bin/bash: line 1: o: command not found make[3]: [Makefile:616: manripper] Error 127 (ignored) o removeduplicates removeduplicates.cpp /bin/bash: line 1: o: command not found make[3]: [Makefile:619: removeduplicates] Error 127 (ignored) --- End Message --- --- Begin Message --- Source: yacas Source-Version: 1.3.6-2.3 Done: Bastian Germann We believe that the bug you reported is fixed in the latest version of yacas, 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 1053...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Bastian Germann (supplier of updated yacas 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: Mon, 09 Oct 2023 20:28:32 +0200 Source: yacas Architecture: source Version: 1.3.6-2.3 Distribution: unstable Urgency: medium Maintainer: Muammar El Khatib Changed-By: Bastian Germann Closes: 1053728 Changes: yacas (1.3.6-2.3) unstable; urgency=medium . * Non-maintainer upload. * Add build dependency autoconf-archive. (Closes: #1053728) Checksums-Sha1: 31edc6bf2ddd848f1914a315419a30f2cf09d3ba 1762 yacas_1.3.6-2.3.dsc 851c408ba1bf074b5ca719b5b4e556ee68dad565 33656 yacas_1.3.6-2.3.debian.tar.xz 17ebb770e1c0adc567e4dc1c1387dc9b5cc1be5d 7667 yacas_1.3.6-2.3_source.buildinfo Checksums-Sha256: 974927c3f5cb84d82535ad270cb958c36d1f8eedf865e38528587de899a44634 1762 yacas_1.3.6-2.3.dsc 05eec8b8a17cd6c0ce4ae8cf77a6b1d2a04691b35c1661a8a56869bdd7e3e6d2 33656 yacas_1.3.6-2.3.debian.tar.xz 4ae28c13f3c6bbe11383b7c6264865ed1f1df77f2b2b57141df9830f2d6ed1d9 7667 yacas_1.3.6-2.3_source.buildinfo Files: a60a4e817726e13e2d077e8e1a44a627 1762 math extra yacas_1.3.6-2.3.dsc 864af129efced535208174da649359ed 33656 math extra yacas_1.3.6-2.3.debian.tar.xz c108788eac44ac0f9f016db0a870b8c6 7667 math extra yacas_1.3.6-2.3_source.buildinfo -BEGIN PGP SIGNATURE- iQHEBAEBCgAuFiEEQGIgyLhVKAI3jM5BH1x6i0VWQxQFAmUkRxsQHGJhZ2VAZGVi aWFuLm9yZwAKCRAfXHqLRVZDFJLiC/0fVZz3967IfIlRaxVEmVLigSySzY4Qhyoa k8JETooernZG6gUzlTWSEJ9ZsADS1p/R0nAM060x2jcMYj+TkCdNJKFjt5cEYHy/ 7Ocav0cnRwbYBRruLu1zNtiqKi80FBgUW+8n9nH8l/Y+no8BEe+EI6W9HOCqh1XP 1GaWTTHiNrwktB17sq5I03qy6Kw1oz/GSjN71uQuPqXKe58jmzYvYaKga7p7/6Rf dDryBdCCxkiReyXOv+zf6TZsHvz2ntJ7MvJ6nBtmBLKHyldjhmroFtAWmAUjN0d+ qDlns5vDkWIt9ajRjAx0IoeY9IldaAjkS8O+a+Vu0KohCeaONW/DCagm1ta421QM cUVG+JtpYoAGvNPNrBgvojDq9RisxyJq1oP4vVx2doDQqEL+XwdfUtm9NsUPNriX lOblPVDYjBj3naBKGsTUDowwzj3/ng29D/P1Q+iibm/WWU/izuXLI/M/DRRIs2iY sOTr4chLhw6vAldD3EDHJhmvZ1nY37M= =mL5I -END PGP SIGNATURE End Message ---
Bug#1042177: marked as done (rust-cid-npm: FTBFS: build-dependency not installable: librust-block-padding-0.2+default-dev)
Your message dated Mon, 09 Oct 2023 18:52:08 + with message-id and subject line Bug#1042177: fixed in rust-cid-npm 0.0~git20200813.59cf068-2 has caused the Debian Bug report #1042177, regarding rust-cid-npm: FTBFS: build-dependency not installable: librust-block-padding-0.2+default-dev 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.) -- 1042177: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1042177 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: rust-cid-npm Version: 0.0~git20200813.59cf068-1 Severity: serious Justification: FTBFS Tags: trixie sid ftbfs User: lu...@debian.org Usertags: ftbfs-20230726 ftbfs-trixie Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > +--+ > | Install package build dependencies > | > +--+ > > > Setup apt archive > - > > Merged Build-Depends: debhelper-compat (= 13), dh-cargo (>= 25), cargo, > rustc, librust-ipfs-unixfs+filetime-dev, librust-cid-0.5-dev, > librust-console-error-panic-hook-dev, build-essential, fakeroot > Filtered Build-Depends: debhelper-compat (= 13), dh-cargo (>= 25), cargo, > rustc, librust-ipfs-unixfs+filetime-dev, librust-cid-0.5-dev, > librust-console-error-panic-hook-dev, build-essential, fakeroot > dpkg-deb: building package 'sbuild-build-depends-main-dummy' in > '/<>/apt_archive/sbuild-build-depends-main-dummy.deb'. > Ign:1 copy:/<>/apt_archive ./ InRelease > Get:2 copy:/<>/apt_archive ./ Release [957 B] > Ign:3 copy:/<>/apt_archive ./ Release.gpg > Get:4 copy:/<>/apt_archive ./ Sources [439 B] > Get:5 copy:/<>/apt_archive ./ Packages [521 B] > Fetched 1917 B in 0s (166 kB/s) > Reading package lists... > Reading package lists... > > Install main build dependencies (apt-based resolver) > > > Installing build dependencies > Reading package lists... > Building dependency tree... > Some packages could not be installed. This may mean that you have > requested an impossible situation or if you are using the unstable > distribution that some required packages have not yet been created > or been moved out of Incoming. > The following information may help to resolve the situation: > > The following packages have unmet dependencies: > librust-block-buffer-0.9+block-padding-dev : Depends: > librust-block-padding-0.2+default-dev but it is not installable > E: Unable to correct problems, you have held broken packages. > apt-get failed. The full build log is available from: http://qa-logs.debian.net/2023/07/26/rust-cid-npm_0.0~git20200813.59cf068-1_unstable.log All bugs filed during this archive rebuild are listed at: https://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=ftbfs-20230726;users=lu...@debian.org or: https://udd.debian.org/bugs/?release=na&merged=ign&fnewerval=7&flastmodval=7&fusertag=only&fusertagtag=ftbfs-20230726&fusertaguser=lu...@debian.org&allbugs=1&cseverity=1&ctags=1&caffected=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: rust-cid-npm Source-Version: 0.0~git20200813.59cf068-2 Done: Jochen Sprickerhof We believe that the bug you reported is fixed in the latest version of rust-cid-npm, 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 1042...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Jochen Sprickerhof (supplier of updated rust-cid-npm 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: Mon, 09 Oct 2023 20:34:50 +0200 Source: rus
Bug#1053728: FTBFS due to Makefile variable not being set
I am uploading a NMU to fix this. The debdiff is attached.diff -Nru yacas-1.3.6/debian/changelog yacas-1.3.6/debian/changelog --- yacas-1.3.6/debian/changelog2023-09-29 17:12:48.0 +0200 +++ yacas-1.3.6/debian/changelog2023-10-09 20:28:32.0 +0200 @@ -1,3 +1,10 @@ +yacas (1.3.6-2.3) unstable; urgency=medium + + * Non-maintainer upload. + * Add build dependency autoconf-archive. (Closes: #1053728) + + -- Bastian Germann Mon, 09 Oct 2023 20:28:32 +0200 + yacas (1.3.6-2.2) unstable; urgency=medium * Non-maintainer upload. diff -Nru yacas-1.3.6/debian/control yacas-1.3.6/debian/control --- yacas-1.3.6/debian/control 2023-09-29 17:12:48.0 +0200 +++ yacas-1.3.6/debian/control 2023-10-09 20:28:32.0 +0200 @@ -8,6 +8,7 @@ libgsl-dev, automake, autoconf, + autoconf-archive, freeglut3-dev, libxmu-dev, libxt-dev,
Bug#1052967: emacsql-sqlite3: FTBFS: make: *** [debian/rules:4: build] Error 25
Hello Sean, Le lundi 9 octobre 2023 à 18:16, Sean Whitton a écrit : Given that you maintain emacsql, would you be interested in taking over emacsql-sqlite3 as well? No. In fact, I think we should not be packaging emacsql-sqlite3 anymore, and we should use the occasion to remove it. The upstream maintainers themselves contend that package developers should not use it, and rely on emacsql instead : https://github.com/cireu/emacsql-sqlite3#important-note. It has no reverse dependencies, and I fail to see how it could be useful to anyone if not as a dependency for another package. The next release of emacsql will not support it, and will make it obsolete, a point of view the upstream maintainers of emacsql-sqlite3 themselves seem to accept : https://github.com/cireu/emacsql-sqlite3/issues/38. It was removed from MELPA last April for this reason. Best, Aymeric
Bug#1042044: marked as done (network-manager-strongswan: FTBFS: nm-strongswan.c:122:9: error: ‘gtk_combo_box_get_active’ is deprecated: Use 'GtkDropDown' instead [-Werror=deprecated-declarations])
Your message dated Mon, 09 Oct 2023 17:34:49 + with message-id and subject line Bug#1042044: fixed in network-manager-strongswan 1.6.0-2.1 has caused the Debian Bug report #1042044, regarding network-manager-strongswan: FTBFS: nm-strongswan.c:122:9: error: ‘gtk_combo_box_get_active’ is deprecated: Use 'GtkDropDown' instead [-Werror=deprecated-declarations] 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.) -- 1042044: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1042044 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: network-manager-strongswan Version: 1.6.0-2 Severity: serious Justification: FTBFS Tags: trixie sid ftbfs Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > /bin/bash ../libtool --tag=CC --mode=compile gcc -DHAVE_CONFIG_H -I. -I.. > -Wdate-time -D_FORTIFY_SOURCE=2 -I/usr/include/gtk-4.0 > -I/usr/include/pango-1.0 -I/usr/include/glib-2.0 > -I/usr/lib/x86_64-linux-gnu/glib-2.0/include -I/usr/include/harfbuzz > -I/usr/include/freetype2 -I/usr/include/libpng16 -I/usr/include/libmount > -I/usr/include/blkid -I/usr/include/fribidi -I/usr/include/cairo > -I/usr/include/pixman-1 -I/usr/include/gdk-pixbuf-2.0 > -I/usr/include/x86_64-linux-gnu -I/usr/include/graphene-1.0 > -I/usr/lib/x86_64-linux-gnu/graphene-1.0/include -mfpmath=sse -msse -msse2 > -pthread -I/usr/include/libnm -I/usr/include/glib-2.0 > -I/usr/lib/x86_64-linux-gnu/glib-2.0/include -pthread -I/usr/include/libmount > -I/usr/include/blkid -DNM_VERSION_MIN_REQUIRED=NM_VERSION_1_2 > -DNM_VERSION_MAX_ALLOWED=NM_VERSION_1_2 -I/usr/include/libnma > -I/usr/include/libnm -I/usr/include/glib-2.0 > -I/usr/lib/x86_64-linux-gnu/glib-2.0/include -pthread -I/usr/include/libmount > -I/usr/include/blkid -DG_DISABLE_DEPRECATED -DGDK_DISABLE_DEPRECATED -Wall > -Werror -std=gnu89 -g -O2 -ffile-prefix-map=/<>=. > -fstack-protector-strong -Wformat -Werror=format-security -Wshadow > -Wmissing-declarations -Wmissing-prototypes -Wdeclaration-after-statement > -Wstrict-prototypes -Wfloat-equal -Wno-unused-parameter -Wno-sign-compare > -fno-strict-aliasing -c -o > gtk4/libnm_gtk4_vpn_plugin_strongswan_editor_la-nm-strongswan-resources.lo > `test -f 'gtk4/nm-strongswan-resources.c' || echo > './'`gtk4/nm-strongswan-resources.c > libtool: compile: gcc -DHAVE_CONFIG_H -I. -I.. -Wdate-time > -D_FORTIFY_SOURCE=2 -I/usr/include/gtk-4.0 -I/usr/include/pango-1.0 > -I/usr/include/glib-2.0 -I/usr/lib/x86_64-linux-gnu/glib-2.0/include > -I/usr/include/harfbuzz -I/usr/include/freetype2 -I/usr/include/libpng16 > -I/usr/include/libmount -I/usr/include/blkid -I/usr/include/fribidi > -I/usr/include/cairo -I/usr/include/pixman-1 -I/usr/include/gdk-pixbuf-2.0 > -I/usr/include/x86_64-linux-gnu -I/usr/include/graphene-1.0 > -I/usr/lib/x86_64-linux-gnu/graphene-1.0/include -mfpmath=sse -msse -msse2 > -pthread -I/usr/include/libnm -I/usr/include/glib-2.0 > -I/usr/lib/x86_64-linux-gnu/glib-2.0/include -pthread -I/usr/include/libmount > -I/usr/include/blkid -DNM_VERSION_MIN_REQUIRED=NM_VERSION_1_2 > -DNM_VERSION_MAX_ALLOWED=NM_VERSION_1_2 -I/usr/include/libnma > -I/usr/include/libnm -I/usr/include/glib-2.0 > -I/usr/lib/x86_64-linux-gnu/glib-2.0/include -pthread -I/usr/include/libmount > -I/usr/include/blkid -DG_DISABLE_DEPRECATED -DGDK_DISABLE_DEPRECATED -Wall > -Werror -std=gnu89 -g -O2 -ffile-prefix-map=/<>=. > -fstack-protector-strong -Wformat -Werror=format-security -Wshadow > -Wmissing-declarations -Wmissing-prototypes -Wdeclaration-after-statement > -Wstrict-prototypes -Wfloat-equal -Wno-unused-parameter -Wno-sign-compare > -fno-strict-aliasing -c nm-strongswan.c -fPIC -DPIC -o > .libs/libnm_gtk4_vpn_plugin_strongswan_editor_la-nm-strongswan.o > libtool: compile: gcc -DHAVE_CONFIG_H -I. -I.. -Wdate-time > -D_FORTIFY_SOURCE=2 -I/usr/include/gtk-3.0 -I/usr/include/pango-1.0 > -I/usr/include/glib-2.0 -I/usr/lib/x86_64-linux-gnu/glib-2.0/include > -I/usr/include/harfbuzz -I/usr/include/freetype2 -I/usr/include/libpng16 > -I/usr/include/libmount -I/usr/include/blkid -I/usr/include/fribidi > -I/usr/include/cairo -I/usr/include/pixman-1 -I/usr/include/gdk-pixbuf-2.0 > -I/usr/include/x86_64-linux-gnu -I/usr/include/gio-unix-2.0 > -I/usr/include/atk-1.0 -I/usr/include/at-spi2-atk/2.0 > -I/usr/include/at-spi-2.0 -I/usr/include/dbus-1.0 > -I/usr/lib/x86_64-linux-gnu/dbus-1.0/include -pthread -I/usr/include/libnm > -I/usr/include/glib-2.0 -I/usr/lib/x86_64-linux-gnu/glib-2.0/include -pthread > -I/usr/include/libmount -I/usr/includ
Processed: [bts-link] source package src:tracker-miners
Processing commands for cont...@bugs.debian.org: > # > # bts-link upstream status pull for source package src:tracker-miners > # see http://lists.debian.org/debian-devel-announce/2006/05/msg1.html > # https://bts-link-team.pages.debian.net/bts-link/ > # > user debian-bts-l...@lists.debian.org Setting user to debian-bts-l...@lists.debian.org (was debian-bts-l...@lists.debian.org). > # remote status report for #1053238 (http://bugs.debian.org/1053238) > # Bug title: tracker-miners: Fails to build on many architectures, failed to > load seccomp rules > # * https://gitlab.gnome.org/GNOME/tracker-miners/-/issues/280 > # * remote status changed: opened -> closed > # * closed upstream > tags 1053238 + fixed-upstream Bug #1053238 [src:tracker-miners] tracker-miners: Fails to build on many architectures, failed to load seccomp rules Added tag(s) fixed-upstream. > usertags 1053238 - status-opened Usertags were: status-opened. There are now no usertags set. > usertags 1053238 + status-closed There were no usertags set. Usertags are now: status-closed. > thanks Stopping processing here. Please contact me if you need assistance. -- 1053238: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1053238 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: [bts-link] source package src:purify
Processing commands for cont...@bugs.debian.org: > # > # bts-link upstream status pull for source package src:purify > # see http://lists.debian.org/debian-devel-announce/2006/05/msg1.html > # https://bts-link-team.pages.debian.net/bts-link/ > # > user debian-bts-l...@lists.debian.org Setting user to debian-bts-l...@lists.debian.org (was debian-bts-l...@lists.debian.org). > # remote status report for #1001528 (http://bugs.debian.org/1001528) > # Bug title: FTBFS with eigen3/3.4.0 > # * https://github.com/astro-informatics/purify/issues/290 > # * remote status changed: open -> closed > # * closed upstream > tags 1001528 + fixed-upstream Bug #1001528 [src:purify] FTBFS with eigen3/3.4.0 Added tag(s) fixed-upstream. > usertags 1001528 - status-open Usertags were: status-open. There are now no usertags set. > usertags 1001528 + status-closed There were no usertags set. Usertags are now: status-closed. > thanks Stopping processing here. Please contact me if you need assistance. -- 1001528: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1001528 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: [bts-link] source package hash-slinger
Processing commands for cont...@bugs.debian.org: > # > # bts-link upstream status pull for source package hash-slinger > # see http://lists.debian.org/debian-devel-announce/2006/05/msg1.html > # https://bts-link-team.pages.debian.net/bts-link/ > # > user debian-bts-l...@lists.debian.org Setting user to debian-bts-l...@lists.debian.org (was debian-bts-l...@lists.debian.org). > # remote status report for #1053483 (http://bugs.debian.org/1053483) > # Bug title: tlsa can produce invalid records > # * https://github.com/letoams/hash-slinger/issues/45 > # * remote status changed: (?) -> closed > # * closed upstream > tags 1053483 + fixed-upstream Bug #1053483 [hash-slinger] tlsa can produce invalid records Added tag(s) fixed-upstream. > usertags 1053483 + status-closed There were no usertags set. Usertags are now: status-closed. > thanks Stopping processing here. Please contact me if you need assistance. -- 1053483: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1053483 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1052967: emacsql-sqlite3: FTBFS: make: *** [debian/rules:4: build] Error 25
Hello Aymeric, On Tue 26 Sep 2023 at 03:44pm +02, Lucas Nussbaum wrote: > Source: emacsql-sqlite3 > Version: 1.0.2+git20220304.1.2113618-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. Given that you maintain emacsql, would you be interested in taking over emacsql-sqlite3 as well? -- Sean Whitton signature.asc Description: PGP signature
Bug#1042885: (No Subject)
>-- /proc/filesystems > ext3 > ext2 > ext4 > fuseblk Is your /boot on an ext2 partition by chance?
Bug#1052784: marked as done (pyephem: FTBFS: AssertionError: Failed doctest test for quick.rst)
Your message dated Mon, 09 Oct 2023 17:04:48 +
with message-id
and subject line Bug#1052784: fixed in pyephem 4.1.4-3
has caused the Debian Bug report #1052784,
regarding pyephem: FTBFS: AssertionError: Failed doctest test for quick.rst
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.)
--
1052784: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1052784
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: pyephem
Version: 4.1.4-2
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):
> debian/rules binary
> dh binary --with python3 --buildsystem=pybuild
>dh_update_autotools_config -O--buildsystem=pybuild
>dh_autoreconf -O--buildsystem=pybuild
>dh_auto_configure -O--buildsystem=pybuild
> I: pybuild base:291: python3.11 setup.py config
>dh_auto_build -O--buildsystem=pybuild
> I: pybuild base:291: /usr/bin/python3 setup.py build
> extensions/_libastro.c: In function ‘scansexa’:
> extensions/_libastro.c:183:11: warning: ‘PyUnicode_GET_SIZE’ is deprecated
> [-Wdeprecated-declarations]
> 183 | Py_ssize_t item_length = PyUnicode_GET_SIZE(item);
> | ^~
> In file included from /usr/include/python3.11/unicodeobject.h:1042,
> from /usr/include/python3.11/Python.h:51,
> from extensions/_libastro.c:4:
> /usr/include/python3.11/cpython/unicodeobject.h:652:26: note: declared here
> 652 | static inline Py_ssize_t PyUnicode_GET_SIZE(PyObject *op)
> | ^~
> extensions/_libastro.c: At top level:
> extensions/_libastro.c:624:12: warning: ‘Date_print’ defined but not used
> [-Wunused-function]
> 624 | static int Date_print(PyObject *self, FILE *fp, int flags)
> |^~
> extensions/_libastro.c:308:12: warning: ‘Angle_print’ defined but not used
> [-Wunused-function]
> 308 | static int Angle_print(PyObject *self, FILE *fp, int flags)
> |^~~
> extensions/dtoa.c: In function ‘Balloc’:
> extensions/dtoa.c:577:64: warning: comparison of integer expressions of
> different signedness: ‘long int’ and ‘long unsigned int’ [-Wsign-compare]
> 577 | if (k <= Kmax && pmem_next - private_mem + len <=
> PRIVATE_mem) {
> |^~
> extensions/dtoa.c: In function ‘rv_alloc’:
> extensions/dtoa.c:3570:66: warning: comparison of integer expressions of
> different signedness: ‘long unsigned int’ and ‘int’ [-Wsign-compare]
> 3570 | sizeof(Bigint) - sizeof(ULong) - sizeof(int) + j <= i;
> | ^~
> extensions/dtoa.c: At top level:
> extensions/dtoa.c:3655:1: warning: ‘dtoa’ defined but not used
> [-Wunused-function]
> 3655 | dtoa
> | ^~~~
> extensions/dtoa.c: In function ‘ascii_strtod’:
> extensions/dtoa.c:317:24: warning: ‘rv’ may be used uninitialized
> [-Wmaybe-uninitialized]
> 317 | #define word0(x) (x)->L[1]
> | ~~^~~
> extensions/dtoa.c:2869:25: note: in expansion of macro ‘word0’
> 2869 | word0(&rv) -= P*Exp_msk1;
> | ^
> extensions/dtoa.c:2495:23: note: ‘rv’ declared here
> 2495 | U aadj2, adj, rv, rv0;
> | ^~
> extensions/dtoa.c:317:24: warning: ‘rv’ may be used uninitialized
> [-Wmaybe-uninitialized]
> 317 | #define word0(x) (x)->L[1]
> | ~~^~~
> extensions/dtoa.c:2897:58: note: in expansion of macro ‘word0’
> 2897 | if (bc.scale && (j = 2*P + 1 - ((word0(&rv) &
> Exp_mask)
> | ^
> extensions/dtoa.c:2495:23: note: ‘rv’ declared here
> 2495 | U aadj2, adj, rv, rv0;
> | ^~
> extensions/dtoa.c:3384:36: warning: ‘rv0.L[1]’ may be used uninitialized
> [-Wmaybe-uninitialized]
> 3384 | if (word0(&rv0) == Big0 &&
> word1(&rv0) == Big1)
> |^
> extensions/dtoa.c:2495:27: note: ‘rv0.L[1]’ was declared here
> 2495 | U aadj2, adj, rv, rv0;
> | ^~~
> libastro/circum.c: In function ‘obj_hyperbolic’:
> libastro/circum.c:427:16: warning: variable ‘a’ set but not used
> [-Wunused-but-set-varia
Bug#1053728: FTBFS due to Makefile variable not being set
Source: yacas Version: 1.3.6-2.2 Severity: serious The package fails to build from scratch because $(CXX_FOR_BUILD) is not set properly: o manripper manripper.cpp /bin/bash: line 1: o: command not found make[3]: [Makefile:616: manripper] Error 127 (ignored) o removeduplicates removeduplicates.cpp /bin/bash: line 1: o: command not found make[3]: [Makefile:619: removeduplicates] Error 127 (ignored)
Bug#1053727: marked as done (leaktracer: FTBFS on amd64)
Your message dated Mon, 09 Oct 2023 16:37:06 + with message-id and subject line Bug#1053727: fixed in leaktracer 2.4-6.3 has caused the Debian Bug report #1053727, regarding leaktracer: FTBFS on amd64 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.) -- 1053727: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1053727 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: leaktracer Version: 2.4-6.2 Severity: serious The package fails to build from source on amd64 due to a change in my NMU: ./LeakCheck ./test make[1]: *** [Makefile:50: test] Segmentation fault --- End Message --- --- Begin Message --- Source: leaktracer Source-Version: 2.4-6.3 Done: Bastian Germann We believe that the bug you reported is fixed in the latest version of leaktracer, 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 1053...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Bastian Germann (supplier of updated leaktracer 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: Mon, 09 Oct 2023 18:11:18 +0200 Source: leaktracer Architecture: source Version: 2.4-6.3 Distribution: unstable Urgency: medium Maintainer: Yann Dirson Changed-By: Bastian Germann Closes: 1053727 Changes: leaktracer (2.4-6.3) unstable; urgency=medium . * Non-maintainer upload. * Drop CFLAGS from test run, which results in FTBFS (Closes: #1053727). Checksums-Sha1: c8ecf147ced7091dbeebddb8593d64a37bc1e76e 1553 leaktracer_2.4-6.3.dsc ec19d1a6167227d5f1519a9492e078a5f64cd967 5152 leaktracer_2.4-6.3.debian.tar.xz c692acebe3f8e240b3204299790ad20524673c70 9183 leaktracer_2.4-6.3_source.buildinfo Checksums-Sha256: 5e89e53a8632387dc8b2b1d56d1a512f8c1ad8cab241571c3f6513c67e37f561 1553 leaktracer_2.4-6.3.dsc 46da9dfafed4466ec3774df8b8f7e306076fd919ee11bb1b54bb9b29a427b2ee 5152 leaktracer_2.4-6.3.debian.tar.xz ff4a87f01d160f4fe05f373a3efcbc36677c0ce1553cf43e2d0af3914621a716 9183 leaktracer_2.4-6.3_source.buildinfo Files: 8b6de3e9391fc8ec78a6c3513989cc3e 1553 devel optional leaktracer_2.4-6.3.dsc c13e4633504b2908198225f18401e0a3 5152 devel optional leaktracer_2.4-6.3.debian.tar.xz 09bd4225b6f71176482b75ee89980066 9183 devel optional leaktracer_2.4-6.3_source.buildinfo -BEGIN PGP SIGNATURE- iQHEBAEBCgAuFiEEQGIgyLhVKAI3jM5BH1x6i0VWQxQFAmUkKOQQHGJhZ2VAZGVi aWFuLm9yZwAKCRAfXHqLRVZDFKKpC/kB7n5JRlWe/zfqz4WTTPxaO0jC7kp/PJTT unHWVTBJNXfV/ikvTXlEMFqPZZdH9Wt9/Ck5w3jdMgVtzh2qqgFjVK+aXQgViEEd JIa2FszAmkrfnwCtOF7jgX2h5l6LTx5BFPaxOeGCCGtTg7Sy+Pb7YCO47qQHlKWj Ulhgkys/2jnRMnqeHyaZMR10fIQ0BS6ONn+9ZiftZJLKPhtXRta7SHB85kfSbjqf 3j4+J1w5xACld3uiE+2q9/Xix+I4xYc0C/FGhyur30JeS+YNP0unBoaUkpoQHeys c9hbBQaqe/+qBGVl2+N6layWq+nYSZHQ82M4UjP+vh7EkG+/RhSgGH/ji/In3GB/ lAvic/2v7bmUc3Xl1Cv9Nh1zsnLCnwYjRwYYopdzYoI7FJ0fJlmsQnEpGJzsH4nD a8PHP4uTNo1apGcqYNF+HZVMmN67SsalUkgrRwBmq6xnrIJtKSPdcb9Lt9OQRm8O aUe4k58Kan2bWDmuwPrxYaNh48tqBUs= =Y4NU -END PGP SIGNATURE End Message ---
Bug#1053727: leaktracer: FTBFS on amd64
I am uploading another NMU to fix this.
The debdiff is attached.diff -Nru leaktracer-2.4/debian/changelog leaktracer-2.4/debian/changelog
--- leaktracer-2.4/debian/changelog 2023-09-29 12:17:22.0 +0200
+++ leaktracer-2.4/debian/changelog 2023-10-09 18:11:18.0 +0200
@@ -1,3 +1,10 @@
+leaktracer (2.4-6.3) unstable; urgency=medium
+
+ * Non-maintainer upload.
+ * Drop CFLAGS from test run, which results in FTBFS (Closes: #1053727).
+
+ -- Bastian Germann Mon, 09 Oct 2023 18:11:18 +0200
+
leaktracer (2.4-6.2) unstable; urgency=medium
* Non-maintainer upload.
diff -Nru leaktracer-2.4/debian/rules leaktracer-2.4/debian/rules
--- leaktracer-2.4/debian/rules 2023-09-29 12:17:22.0 +0200
+++ leaktracer-2.4/debian/rules 2023-10-09 18:11:03.0 +0200
@@ -27,7 +27,7 @@
dh_testdir
$(MAKE) CC="$(CXX)" CFLAGS="${CFLAGS}"
- [ $(NOCHECK) = 1 ] || $(MAKE) test CC="$(CXX)" CFLAGS="${CFLAGS}"
+ [ $(NOCHECK) = 1 ] || $(MAKE) test CC="$(CXX)"
touch build-stamp
Bug#1053727: leaktracer: FTBFS on amd64
Source: leaktracer Version: 2.4-6.2 Severity: serious The package fails to build from source on amd64 due to a change in my NMU: ./LeakCheck ./test make[1]: *** [Makefile:50: test] Segmentation fault
Bug#1053552: marked as done (gavodachs2-server: Error while setting up with postgresql 16)
Your message dated Mon, 09 Oct 2023 15:34:08 + with message-id and subject line Bug#1053552: fixed in gavodachs 2.8+dfsg-4 has caused the Debian Bug report #1053552, regarding gavodachs2-server: Error while setting up with postgresql 16 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.) -- 1053552: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1053552 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: gavodachs2-server Version: 2.8+dfsg-3 Severity: serious Hi Markus, While running the migration test for astropy 5.3.4-1, the installation of gavodachs2-server failed. Relevant lines from the log: 103s Setting up gavodachs2-server (2.8+dfsg-3) ... 103s Created symlink /etc/systemd/system/multi-user.target.wants/dachs.service → /lib/systemd/system/dachs.service. 103s info: Selecting GID from range 1000 to 5 ... 103s info: Adding group `gavo' (GID 1001) ... 103s info: The home dir /nonexistent you specified can't be accessed: No such file or directory 103s 103s info: Selecting UID from range 100 to 999 ... 103s 103s info: Adding system user `gavo' (UID 103) ... 103s info: Adding new user `gavo' (UID 103) with group `gavo' ... 103s info: Not creating `/nonexistent'. 103s info: Adding user `dachsroot' ... 103s info: Selecting UID from range 1000 to 5 ... 103s 103s info: Adding new user `dachsroot' (1001) with group `gavo (1001)' ... 103s info: Creating home directory `/home/dachsroot' ... 103s info: Copying files from `/etc/skel' ... 103s info: Adding new user `dachsroot' to supplemental / extra groups `users' ... 103s info: Adding user `dachsroot' to group `users' ... 108s *** Error: While executing DB query: 108s 108s alter role untrusted set extra_float_digits=3 108s 108s The database engine reported: 108s 108s ERROR: permission denied to alter role 108s DETAIL: Only roles with the CREATEROLE attribute and the ADMIN option 108s on role "untrusted" may alter this role. 108s 108s dpkg: error processing package gavodachs2-server (--configure): 108s installed gavodachs2-server package post-installation script subprocess returned error exit status 1 108s dpkg: dependency problems prevent configuration of autopkgtest-satdep: 108s autopkgtest-satdep depends on gavodachs2-server; however: 108s Package gavodachs2-server is not configured yet. 108s 108s dpkg: error processing package autopkgtest-satdep (--configure): 108s dependency problems - leaving unconfigured 108s Errors were encountered while processing: 108s gavodachs2-server Full log here: https://ci.debian.net/data/autopkgtest/testing/amd64/g/gavodachs/38631770/log.gz I don't think that has anything to do with the astropy update. This seems to be connected to Postgresql version (16.0-2); a similar install (with Postgresql 15.4-3) succeeded. --- End Message --- --- Begin Message --- Source: gavodachs Source-Version: 2.8+dfsg-4 Done: Markus Demleitner We believe that the bug you reported is fixed in the latest version of gavodachs, 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 1053...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Markus Demleitner (supplier of updated gavodachs 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: Mon, 09 Oct 2023 11:35:10 +0200 Source: gavodachs Architecture: source Version: 2.8+dfsg-4 Distribution: unstable Urgency: medium Maintainer: Debian Astronomy Team Changed-By: Markus Demleitner Closes: 1053552 Changes: gavodachs (2.8+dfsg-4) unstable; urgency=medium . * Dropping extra_float_digit setup in dachs init (Closes: #1053552) Checksums-Sha1: 79102efb25bc2adec2eab005b7d6cf611a7a3580 2400 gavodachs_2.8+dfsg-4.dsc 6c8bdde2b76c34597e9bbcfec3ae5d13b50f0092 10620 gavodachs_2.8+dfsg-4.debian.tar.xz Checksums-Sha256: e95c40ce685e8a9a4ea9ce22486678129b368b93b2206c9b0fd919a9217a4164 2400 gavodachs_2.8+dfsg-4.dsc 52b1e27502523b438af4ca0fc423030a0db331bd98b18d7a61bb8aa3e6411f1e 10620 gavodachs_2.8+dfsg-4.debian.tar.xz Files: 98b24bdfe5dbc539a447ca6262c57137 2400 python optional gavodachs_2.8+dfsg-4.dsc d180404f105943d264c702951a0551ac 10620 python optional gavodachs_2
Bug#1053573: libpython3.11-testsuite install fails due to syntax error: 'uft-8' in /usr/lib/python3.11/test/tokenizedata/bad_coding.py
Sounds good to me! thanks! On Mon, Oct 9, 2023, 11:19 gregor herrmann wrote: > On Fri, 06 Oct 2023 14:43:14 -0400, Albedo Black wrote: > > > Package: libpython3.11-testsuite > > Version: 3.11.6-2 > > Severity: serious > > File: /usr/share/doc/libpython3.11-testsuite > > Tags: ftbfs > > Justification: makes the package in question unusable or mostly so > > > > $sudo dpkg --configure libpython3.11-testsuite > > Setting up libpython3.11-testsuite (3.11.6-2) ... > > File "/usr/lib/python3.11/test/tokenizedata/bad_coding.py", line > 0 > > SyntaxError: unknown encoding: uft-8 > > dpkg: error processing package libpython3.11-testsuite > > (--configure): > > installed libpython3.11-testsuite package post-installation > script > > subprocess returned error exit status 1 > > Errors were encountered while processing: > > libpython3.11-testsuite > > According to the changelog [0] this was fixed in 3.11.6-3, and I > didn't encounter any problems when upgrading from 3.11.5-3 to > 3.11.6-3, so I think this bug can be closed at version 3.11.6-3. > > > Cheers, > gregor > > > [0] > https://tracker.debian.org/news/1469422/accepted-python311-3116-3-source-into-unstable/ > > -- > .''`. https://info.comodo.priv.at -- Debian Developer > https://www.debian.org > : :' : OpenPGP fingerprint D1E1 316E 93A7 60A8 104D 85FA BB3A 6801 8649 > AA06 > `. `' Member VIBE!AT & SPI Inc. -- Supporter Free Software Foundation > Europe >`- >
Bug#1052891: marked as done (asdf-transform-schemas: FTBFS: RuntimeError: Missing resources directory)
Your message dated Mon, 09 Oct 2023 15:19:13 + with message-id and subject line Bug#1052891: fixed in asdf-transform-schemas 0.3.0-2 has caused the Debian Bug report #1052891, regarding asdf-transform-schemas: FTBFS: RuntimeError: Missing resources 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.) -- 1052891: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1052891 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: asdf-transform-schemas Version: 0.3.0-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): > debian/rules binary > dh binary --with python3 --buildsystem=pybuild >dh_update_autotools_config -O--buildsystem=pybuild >dh_autoreconf -O--buildsystem=pybuild >dh_auto_configure -O--buildsystem=pybuild >dh_auto_build -O--buildsystem=pybuild > I: pybuild plugin_pyproject:110: Building wheel for python3.11 with "build" > module > I: pybuild base:291: python3.11 -m build --skip-dependency-check > --no-isolation --wheel --outdir /<>/.pybuild/cpython3_3.11 > * Building wheel... > running bdist_wheel > running build > running build_py > creating build > creating build/lib > creating build/lib/asdf_transform_schemas > copying src/asdf_transform_schemas/_version.py -> > build/lib/asdf_transform_schemas > copying src/asdf_transform_schemas/__init__.py -> > build/lib/asdf_transform_schemas > copying src/asdf_transform_schemas/integration.py -> > build/lib/asdf_transform_schemas > running egg_info > creating src/asdf_transform_schemas.egg-info > writing src/asdf_transform_schemas.egg-info/PKG-INFO > writing dependency_links to > src/asdf_transform_schemas.egg-info/dependency_links.txt > writing entry points to src/asdf_transform_schemas.egg-info/entry_points.txt > writing requirements to src/asdf_transform_schemas.egg-info/requires.txt > writing top-level names to src/asdf_transform_schemas.egg-info/top_level.txt > writing manifest file 'src/asdf_transform_schemas.egg-info/SOURCES.txt' > reading manifest file 'src/asdf_transform_schemas.egg-info/SOURCES.txt' > adding license file 'LICENSE' > writing manifest file 'src/asdf_transform_schemas.egg-info/SOURCES.txt' > installing to build/bdist.linux-x86_64/wheel > running install > running install_lib > creating build/bdist.linux-x86_64 > creating build/bdist.linux-x86_64/wheel > creating build/bdist.linux-x86_64/wheel/asdf_transform_schemas > copying build/lib/asdf_transform_schemas/_version.py -> > build/bdist.linux-x86_64/wheel/asdf_transform_schemas > copying build/lib/asdf_transform_schemas/__init__.py -> > build/bdist.linux-x86_64/wheel/asdf_transform_schemas > copying build/lib/asdf_transform_schemas/integration.py -> > build/bdist.linux-x86_64/wheel/asdf_transform_schemas > running install_egg_info > Copying src/asdf_transform_schemas.egg-info to > build/bdist.linux-x86_64/wheel/asdf_transform_schemas-0.3.0.egg-info > running install_scripts > creating > build/bdist.linux-x86_64/wheel/asdf_transform_schemas-0.3.0.dist-info/WHEEL > creating > '/<>/.pybuild/cpython3_3.11/.tmp-a6wgzywh/asdf_transform_schemas-0.3.0-py3-none-any.whl' > and adding 'build/bdist.linux-x86_64/wheel' to it > adding 'asdf_transform_schemas/__init__.py' > adding 'asdf_transform_schemas/_version.py' > adding 'asdf_transform_schemas/integration.py' > adding 'asdf_transform_schemas-0.3.0.dist-info/LICENSE' > adding 'asdf_transform_schemas-0.3.0.dist-info/METADATA' > adding 'asdf_transform_schemas-0.3.0.dist-info/WHEEL' > adding 'asdf_transform_schemas-0.3.0.dist-info/entry_points.txt' > adding 'asdf_transform_schemas-0.3.0.dist-info/top_level.txt' > adding 'asdf_transform_schemas-0.3.0.dist-info/RECORD' > removing build/bdist.linux-x86_64/wheel > Successfully built asdf_transform_schemas-0.3.0-py3-none-any.whl > I: pybuild plugin_pyproject:122: Unpacking wheel built for python3.11 with > "installer" module >dh_auto_test -O--buildsystem=pybuild > I: pybuild base:291: cd /<>/.pybuild/cpython3_3.11/build; > python3.11 -m pytest tests > [1m= test session starts > ==[0m > platform linux -- Python 3.11.5, pytest-7.4.2, pluggy-1.3.0 > rootdir: /<>/.pybuild/cpython3_3.11/build > configfile: pyproject.toml > plugins: asdf-2.15.0 > collected 35 items > > tests/test_integration.py [33ms[0m[33ms[0m[33m > [ 5%][0m > tests/test_invalid.
Bug#1052816: marked as done (asdf-standard: FTBFS: dh_auto_test: error: pybuild --test --test-pytest -i python{version} -p 3.11 returned exit code 13)
Your message dated Mon, 09 Oct 2023 15:19:04 +
with message-id
and subject line Bug#1052816: fixed in asdf-standard 1.0.3-2
has caused the Debian Bug report #1052816,
regarding asdf-standard: FTBFS: dh_auto_test: error: pybuild --test
--test-pytest -i python{version} -p 3.11 returned exit code 13
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.)
--
1052816: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1052816
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: asdf-standard
Version: 1.0.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):
> debian/rules binary
> dh binary --with python3 --buildsystem=pybuild
>dh_update_autotools_config -O--buildsystem=pybuild
>dh_autoreconf -O--buildsystem=pybuild
>dh_auto_configure -O--buildsystem=pybuild
>dh_auto_build -O--buildsystem=pybuild
> I: pybuild plugin_pyproject:110: Building wheel for python3.11 with "build"
> module
> I: pybuild base:291: python3.11 -m build --skip-dependency-check
> --no-isolation --wheel --outdir /<>/.pybuild/cpython3_3.11
> * Building wheel...
> running bdist_wheel
> running build
> running build_py
> creating build
> creating build/lib
> creating build/lib/asdf_standard
> copying src/asdf_standard/_version.py -> build/lib/asdf_standard
> copying src/asdf_standard/__init__.py -> build/lib/asdf_standard
> copying src/asdf_standard/integration.py -> build/lib/asdf_standard
> copying src/asdf_standard/resource.py -> build/lib/asdf_standard
> running egg_info
> creating src/asdf_standard.egg-info
> writing src/asdf_standard.egg-info/PKG-INFO
> writing dependency_links to src/asdf_standard.egg-info/dependency_links.txt
> writing entry points to src/asdf_standard.egg-info/entry_points.txt
> writing requirements to src/asdf_standard.egg-info/requires.txt
> writing top-level names to src/asdf_standard.egg-info/top_level.txt
> writing manifest file 'src/asdf_standard.egg-info/SOURCES.txt'
> reading manifest file 'src/asdf_standard.egg-info/SOURCES.txt'
> adding license file 'LICENSE'
> writing manifest file 'src/asdf_standard.egg-info/SOURCES.txt'
> installing to build/bdist.linux-x86_64/wheel
> running install
> running install_lib
> creating build/bdist.linux-x86_64
> creating build/bdist.linux-x86_64/wheel
> creating build/bdist.linux-x86_64/wheel/asdf_standard
> copying build/lib/asdf_standard/_version.py ->
> build/bdist.linux-x86_64/wheel/asdf_standard
> copying build/lib/asdf_standard/__init__.py ->
> build/bdist.linux-x86_64/wheel/asdf_standard
> copying build/lib/asdf_standard/integration.py ->
> build/bdist.linux-x86_64/wheel/asdf_standard
> copying build/lib/asdf_standard/resource.py ->
> build/bdist.linux-x86_64/wheel/asdf_standard
> running install_egg_info
> Copying src/asdf_standard.egg-info to
> build/bdist.linux-x86_64/wheel/asdf_standard-1.0.3.egg-info
> running install_scripts
> creating build/bdist.linux-x86_64/wheel/asdf_standard-1.0.3.dist-info/WHEEL
> creating
> '/<>/.pybuild/cpython3_3.11/.tmp-3g3njkg3/asdf_standard-1.0.3-py3-none-any.whl'
> and adding 'build/bdist.linux-x86_64/wheel' to it
> adding 'asdf_standard/__init__.py'
> adding 'asdf_standard/_version.py'
> adding 'asdf_standard/integration.py'
> adding 'asdf_standard/resource.py'
> adding 'asdf_standard-1.0.3.dist-info/LICENSE'
> adding 'asdf_standard-1.0.3.dist-info/METADATA'
> adding 'asdf_standard-1.0.3.dist-info/WHEEL'
> adding 'asdf_standard-1.0.3.dist-info/entry_points.txt'
> adding 'asdf_standard-1.0.3.dist-info/top_level.txt'
> adding 'asdf_standard-1.0.3.dist-info/RECORD'
> removing build/bdist.linux-x86_64/wheel
> Successfully built asdf_standard-1.0.3-py3-none-any.whl
> I: pybuild plugin_pyproject:122: Unpacking wheel built for python3.11 with
> "installer" module
>dh_auto_test -O--buildsystem=pybuild
> I: pybuild base:291: cd /<>/.pybuild/cpython3_3.11/build;
> python3.11 -m pytest tests
> [1m= test session starts
> ==[0m
> platform linux -- Python 3.11.5, pytest-7.4.2, pluggy-1.3.0
> rootdir: /<>/.pybuild/cpython3_3.11/build
> configfile: pyproject.toml
> plugins: mock-3.11.1, doctestplus-1.0.0, cov-4.1.0, openfiles-0.5.0,
> filter-subpackage-0.1.2, astropy-header-0.2.2, asdf-2.15.0, arraydiff-0.5.0,
> hypothesis-6.87.0, remotedata-0.4.0, astropy-0.10.0
> collected 20 items / 1 error
>
> ERRORS
> ==
Bug#1053573: libpython3.11-testsuite install fails due to syntax error: 'uft-8' in /usr/lib/python3.11/test/tokenizedata/bad_coding.py
On Fri, 06 Oct 2023 14:43:14 -0400, Albedo Black wrote: > Package: libpython3.11-testsuite > Version: 3.11.6-2 > Severity: serious > File: /usr/share/doc/libpython3.11-testsuite > Tags: ftbfs > Justification: makes the package in question unusable or mostly so > $sudo dpkg --configure libpython3.11-testsuite > Setting up libpython3.11-testsuite (3.11.6-2) ... > File "/usr/lib/python3.11/test/tokenizedata/bad_coding.py", line 0 > SyntaxError: unknown encoding: uft-8 > dpkg: error processing package libpython3.11-testsuite > (--configure): > installed libpython3.11-testsuite package post-installation script > subprocess returned error exit status 1 > Errors were encountered while processing: > libpython3.11-testsuite According to the changelog [0] this was fixed in 3.11.6-3, and I didn't encounter any problems when upgrading from 3.11.5-3 to 3.11.6-3, so I think this bug can be closed at version 3.11.6-3. Cheers, gregor [0] https://tracker.debian.org/news/1469422/accepted-python311-3116-3-source-into-unstable/ -- .''`. https://info.comodo.priv.at -- Debian Developer https://www.debian.org : :' : OpenPGP fingerprint D1E1 316E 93A7 60A8 104D 85FA BB3A 6801 8649 AA06 `. `' Member VIBE!AT & SPI Inc. -- Supporter Free Software Foundation Europe `- signature.asc Description: Digital Signature
Bug#1031874: upx-ucl: CVE-2023-23457
* Moritz Mühlenhoff [Fri Feb 24, 2023 at 05:04:53PM +0100]: > The following vulnerability was published for upx-ucl. > > CVE-2023-23457[0]: > | A Segmentation fault was found in UPX in > | PackLinuxElf64::invert_pt_dynamic() in p_lx_elf.cpp. An attacker with > | a crafted input file allows invalid memory address access that could > | lead to a denial of service. > > https://github.com/upx/upx/issues/631 > https://github.com/upx/upx/commit/779b648c5f6aa9b33f4728f79dd4d0efec0bf860 [...] There are patches available for this and also for #1033258 since several months, also upstream released multiple versions since 3.96 (latest being v4.1.0 as of 2023-08-08). Is there any reason why this wasn't yet taken care of? Is the package maintainer still around? regards -mika- signature.asc Description: PGP signature
Bug#1052882: marked as done (xtensor: FTBFS: make[1]: *** [debian/rules:65: override_dh_auto_configure] Error 2)
Your message dated Mon, 09 Oct 2023 14:42:45 + with message-id and subject line Bug#1052882: fixed in xtensor 0.24.7-2 has caused the Debian Bug report #1052882, regarding xtensor: FTBFS: make[1]: *** [debian/rules:65: override_dh_auto_configure] Error 2 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.) -- 1052882: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1052882 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: xtensor Version: 0.24.3-2 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): > make[1]: Entering directory '/<>' > dh_auto_configure -- -DBUILD_TESTS=ON -DXTENSOR_USE_XSIMD=ON > cd obj-x86_64-linux-gnu && DEB_PYTHON_INSTALL_LAYOUT=deb cmake > -DCMAKE_INSTALL_PREFIX=/usr -DCMAKE_BUILD_TYPE=None > -DCMAKE_INSTALL_SYSCONFDIR=/etc -DCMAKE_INSTALL_LOCALSTATEDIR=/var > -DCMAKE_EXPORT_NO_PACKAGE_REGISTRY=ON -DCMAKE_FIND_USE_PACKAGE_REGISTRY=OFF > -DCMAKE_FIND_PACKAGE_NO_PACKAGE_REGISTRY=ON > -DFETCHCONTENT_FULLY_DISCONNECTED=ON -DCMAKE_INSTALL_RUNSTATEDIR=/run > -DCMAKE_SKIP_INSTALL_ALL_DEPENDENCY=ON "-GUnix Makefiles" > -DCMAKE_VERBOSE_MAKEFILE=ON -DCMAKE_INSTALL_LIBDIR=lib/x86_64-linux-gnu > -DBUILD_TESTS=ON -DXTENSOR_USE_XSIMD=ON .. > CMake Deprecation Warning at CMakeLists.txt:10 (cmake_minimum_required): > Compatibility with CMake < 3.5 will be removed from a future version of > CMake. > > Update the VERSION argument value or use a ... suffix to tell > CMake that the project does not need compatibility with older versions. > > > -- The CXX compiler identification is GNU 13.2.0 > -- Detecting CXX compiler ABI info > -- Detecting CXX compiler ABI info - done > -- Check for working CXX compiler: /usr/bin/c++ - skipped > -- Detecting CXX compile features > -- Detecting CXX compile features - done > -- Building xtensor v0.24.3 > -- Found xtl: /usr/include/xtl > CMake Error at CMakeLists.txt:72 (find_package): > Could not find a configuration file for package "xsimd" that is compatible > with requested version "8.0.2". > > The following configuration files were considered but not accepted: > > /usr/lib/x86_64-linux-gnu/cmake/xsimd/xsimdConfig.cmake, version: 10.0.0 > > > > -- Configuring incomplete, errors occurred! > cd obj-x86_64-linux-gnu && tail -v -n \+0 CMakeCache.txt > ==> CMakeCache.txt <== > # This is the CMakeCache file. > # For build in directory: /<>/obj-x86_64-linux-gnu > # It was generated by CMake: /usr/bin/cmake > # You can edit this file to change values found and used by cmake. > # If you do not want to change any of the values, simply exit the editor. > # If you do want to change a value, simply edit, save, and exit the editor. > # The syntax for the file is as follows: > # KEY:TYPE=VALUE > # KEY is the name of a variable in the cache. > # TYPE is a hint to GUIs for the type of VALUE, DO NOT EDIT TYPE!. > # VALUE is the current value for the KEY. > > > # EXTERNAL cache entries > > > //No help, variable specified on the command line. > BUILD_TESTS:UNINITIALIZED=ON > > //Path to a program. > CMAKE_ADDR2LINE:FILEPATH=/usr/bin/addr2line > > //Path to a program. > CMAKE_AR:FILEPATH=/usr/bin/ar > > //Choose the type of build, options are: None Debug Release RelWithDebInfo > // MinSizeRel ... > CMAKE_BUILD_TYPE:STRING=None > > //Enable/Disable color output during build. > CMAKE_COLOR_MAKEFILE:BOOL=ON > > //CXX compiler > CMAKE_CXX_COMPILER:FILEPATH=/usr/bin/c++ > > //A wrapper around 'ar' adding the appropriate '--plugin' option > // for the GCC compiler > CMAKE_CXX_COMPILER_AR:FILEPATH=/usr/bin/gcc-ar-13 > > //A wrapper around 'ranlib' adding the appropriate '--plugin' option > // for the GCC compiler > CMAKE_CXX_COMPILER_RANLIB:FILEPATH=/usr/bin/gcc-ranlib-13 > > //Flags used by the CXX compiler during all build types. > CMAKE_CXX_FLAGS:STRING=-g -O2 -ffile-prefix-map=/<>=. > -fstack-protector-strong -fstack-clash-protection -Wformat > -Werror=format-security -fcf-protection -Wdate-time -D_FORTIFY_SOURCE=2 > > //Flags used by the CXX compiler during DEBUG builds. > CMAKE_CXX_FLAGS_DEBUG:STRING=-g > > //Flags used by the CXX compiler during MINSIZEREL builds. > CMAKE_CXX_FLAGS_MINSIZEREL:STRING=-Os -DNDEBUG > > //Flags used by the CXX compiler during NONE builds. > CMAKE_CXX_FLAGS_NONE:STRING= > > //Flags used by the CXX compiler during RELEASE builds. > CMAKE_CX
Bug#1053703: marked as done (orca: Incorrect required dependency)
Your message dated Mon, 09 Oct 2023 11:34:48 + with message-id and subject line Bug#1053703: fixed in orca 45.1-2 has caused the Debian Bug report #1053703, regarding orca: Incorrect required dependency 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.) -- 1053703: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1053703 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: orca Version: 45.1-1 Severity: grave Tags: a11y Justification: renders package unusable Dear Maintainer, When trying to upgrade Orca using 'apt upgrade orca', apt gives the following error: Some packages could not be installed. This may mean that you have requested an impossible situation or if you are using the unstable distribution that some required packages have not yet been created or been moved out of Incoming. The following information may help to resolve the situation: The following packages have unmet dependencies: orca : Depends: python2:any but it is not installable E: Broken packages Orca requires python3, not python2. -- System Information: Debian Release: trixie/sid APT prefers unstable APT policy: (500, 'unstable') Architecture: amd64 (x86_64) Kernel: Linux 6.5.0-1-amd64 (SMP w/2 CPU threads; PREEMPT) Kernel taint flags: 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 --- End Message --- --- Begin Message --- Source: orca Source-Version: 45.1-2 Done: Samuel Thibault We believe that the bug you reported is fixed in the latest version of orca, 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 1053...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Samuel Thibault (supplier of updated orca 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: Mon, 09 Oct 2023 13:17:06 +0200 Source: orca Architecture: source Version: 45.1-2 Distribution: unstable Urgency: medium Maintainer: Debian Accessibility Team Changed-By: Samuel Thibault Closes: 1053703 Changes: orca (45.1-2) unstable; urgency=medium . * Rebuild on buildd (Closes: Bug#1053703) Checksums-Sha1: 0ad223df2e3f3fece6f6105e6b93fd3a85a2f6cf 2312 orca_45.1-2.dsc f5da6a7ff856fde6ad5d3eb5f6f83fb72f467e81 11048 orca_45.1-2.debian.tar.xz ce22db9010c3455bad8ece1c89410d4ef130594c 10201 orca_45.1-2_amd64.buildinfo Checksums-Sha256: 0b7cd587227cb9d6ea6873d33385dba8039c2d0b437f125755d6e0c990153a94 2312 orca_45.1-2.dsc 831d6b82d75ba8bb5ea755a1d78ae4fd7d9a7a0bd9d4030f83145a0c29e511df 11048 orca_45.1-2.debian.tar.xz 78c079608fa7d0854f5b1501b517ac7c9d9b69b51bf5130a44a0695b78e1fb17 10201 orca_45.1-2_amd64.buildinfo Files: cab8309886bb2aa78d1b90f8914f0f74 2312 gnome optional orca_45.1-2.dsc ee5952b4b30a264a50cc810c607b5513 11048 gnome optional orca_45.1-2.debian.tar.xz 0a2d8ff1aaaccd955d34575a66a80757 10201 gnome optional orca_45.1-2_amd64.buildinfo -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEEi6MnFvk67auaclLJ5pG0tXV4H2IFAmUj4b0ACgkQ5pG0tXV4 H2LSXg//RwxMF55dyI5pxS487m7313s/ZRYYQbJSyVaGUBeHGLwQdVXb/v5fLXci Egr2iNSb/B6bwWP8HWx/7X3zn9+eoE7CHVyclawHQzjr9/SQQBwdoL7SN95nvDPm SNTOtk9piZAArKoETIa6b0QXXdgYPBuIuudf9iN3Ksq9jikG8bt+LNZ9PeNZK9XI GctPDwSWBHwYgD4hlVTc1jb6l3Zdk6YPHazUUpz3GASlmW7lcbVo8eKjQvCQQviV H6rhNjqhZ2IwDVjmSB2rMDv2FZALPSDtVLez4rN6KdjkgeJk5JzkgzicsOLxILSg 1ytu90rK9Z0jqmtT229kQM8wOfmARR8NbP87Z3mO4wCizSP3SKCGJgPlfj1dFJte belm3weIEIrnIl5MPgd2R6AvYpyriO+dGo0VatGZ239uBxjAOvMRfC0W/FZiXS2n 9LW5k6DQzUxBrn2nZXCN4fZnsoW9ddjOxQajwElSyI1VEaWnRXTZDjiu8skz1FEU jzmCQeiSjPBhbXWiQpaB08mAUJdJVZlZXTwiAjiZMU8j3gUGRt9W8bcr/iV1u9+n vtv+6NR4WYmmyjdNVeelACYMj9jkSbs7MsS6UXd9WmiwjTw6npdZblUwVXEOUq1/ v/gbpJilhNQEZWLxamYGfS0RJFK14x+D9GlNonUVHgfP+fmSA/k= =WqPy -END PGP SIGNATURE End Message ---
Bug#1053703: orca: Incorrect required dependency
Control: tags -1 + pending Hello, Jeremy Lincicome, le lun. 09 oct. 2023 04:52:18 -0600, a ecrit: > The following packages have unmet dependencies: > orca : Depends: python2:any but it is not installable Oops. That shows how useful it is that the archive makes sure that only packages built on buildds get migrated to testing :) Samuel
Processed: Re: Bug#1053703: orca: Incorrect required dependency
Processing control commands: > tags -1 + pending Bug #1053703 [orca] orca: Incorrect required dependency Added tag(s) pending. -- 1053703: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1053703 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1052929: marked as done (yasnippet: FTBFS: make: *** [debian/rules:4: binary] Error 25)
Your message dated Mon, 09 Oct 2023 11:05:01 +
with message-id
and subject line Bug#1052929: fixed in yasnippet 0.14.0+git20230912.76e1eee6-1
has caused the Debian Bug report #1052929,
regarding yasnippet: FTBFS: make: *** [debian/rules:4: binary] Error 25
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.)
--
1052929: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1052929
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: yasnippet
Version: 0.14.0+git20200603.5cbdbf0d-2
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):
> make[1]: Entering directory '/<>'
> HOME=$(pwd) emacs -Q -L /usr/share/emacs/site-lisp/elpa-src/htmlize-* -L .
> --batch -l htmlize -l doc/yas-doc-helper.el -f yas--generate-html-batch
> Package cl is deprecated
> doc/yas-doc-helper.el: Warning: ‘loop’ is an obsolete alias (as of 27.1); use
> ‘cl-loop’ instead.
> doc/yas-doc-helper.el: Warning: ‘loop’ is an obsolete alias (as of 27.1); use
> ‘cl-loop’ instead.
> doc/yas-doc-helper.el: Warning: ‘return’ is an obsolete alias (as of 27.1);
> use ‘cl-return’ instead.
> doc/yas-doc-helper.el: Warning: ‘loop’ is an obsolete alias (as of 27.1); use
> ‘cl-loop’ instead.
> Publishing file /<>/doc/faq.org using ‘org-html-publish-to-html’
> Publishing file /<>/doc/index.org using
> ‘org-html-publish-to-html’
> Publishing file /<>/doc/snippet-development.org using
> ‘org-html-publish-to-html’
> Publishing file /<>/doc/snippet-reference.org using
> ‘org-html-publish-to-html’
> Executing Emacs-Lisp unknown at position 49...
> Code block evaluation complete.
> Publishing file /<>/doc/snippet-organization.org using
> ‘org-html-publish-to-html’
> Publishing file /<>/doc/snippet-expansion.org using
> ‘org-html-publish-to-html’
> Publishing file /<>/doc/snippet-menu.org using
> ‘org-html-publish-to-html’
> make[1]: Leaving directory '/<>'
>dh_elpa_test
> emacs -batch -Q -l package --eval "(add-to-list 'package-directory-list
> \"/usr/share/emacs/site-lisp/elpa\")" --eval "(add-to-list
> 'package-directory-list \"/usr/share/emacs/site-lisp/elpa-src\")" -f
> package-initialize -L . --eval "(setq user-emacs-directory (make-temp-file
> \"yasnippet-test\" 'dir-flag))" -l yasnippet-tests.el --eval
> \(ert-run-tests-batch-and-exit\)
> Running 91 tests (2023-09-26 06:54:06+, selector ‘t’)
>failed 1/91 another-example-for-issue-271 (0.000494 sec)
>passed 2/91 auto-fill-with-multiparagraph (0.000850 sec)
>
> [yas] Prepared just-in-time loading of snippets successfully.
>
>passed 3/91 auto-next-field (0.039849 sec)
>passed 4/91 basic-indentation (0.045317 sec)
>
> [yas] Prepared just-in-time loading of snippets successfully.
>
>passed 5/91 basic-jit-loading (0.107436 sec)
>
> [yas] Prepared just-in-time loading of snippets successfully.
> [yas] Prepared just-in-time loading of snippets successfully.
>
>passed 6/91 basic-jit-loading-with-compiled-snippets (0.096542 sec)
>passed 7/91 be-careful-when-escaping-in-yas-selected-text (0.000777 sec)
>passed 8/91 be-careful-when-escaping-in-yas-selected-text-2 (0.000395
> sec)
>
> [yas] Prepared just-in-time loading of snippets successfully.
> [yas] Error in condition evaluation: Symbol’s value as variable is void:
> yas--barbaz
>
>passed 9/91 complicated-yas-key-syntaxes (0.028898 sec)
>passed 10/91 deep-nested-mirroring-issue-351 (0.002675 sec)
> [yas] Committing snippets. Action would destroy a protection overlay.
> Test delete-nested-simple-field-issue-824 backtrace:
> signal(wrong-type-argument (yas--snippet nil))
> (or (progn (and (memq (type-of snippet) cl-struct-yas--snippet-tags)
> (progn (or (progn (and (memq (type-of snippet) cl-struct-yas--snippe
> (cl-remove-if #'(lambda (field) (and (not (eq field active)) (yas--f
> (let ((live-fields (cl-remove-if #'(lambda (field) (and (not ...) (y
> yas--find-next-field(1 nil #s(yas--field :number 3 :start 1 :end 1 :
> (let* ((active-field (overlay-get yas--active-field-overlay 'yas--fi
> yas-next-field(1)
> (cond ((yas--maybe-clear-field-filter t) (yas--skip-and-clear (or fi
> yas-skip-and-clear-or-delete-char()
> apply(yas-skip-and-clear-or-delete-char nil)
> ert-simulate-command((yas-skip-and-clear-or-delete-char))
> (progn (yas-minor-mode 1) (yas-expand-snippet "${3:so-$4and}$0${2:-s
> (unwind-protect (progn (yas-minor-mode 1)
Bug#1053703: orca: Incorrect required dependency
Package: orca Version: 45.1-1 Severity: grave Tags: a11y Justification: renders package unusable Dear Maintainer, When trying to upgrade Orca using 'apt upgrade orca', apt gives the following error: Some packages could not be installed. This may mean that you have requested an impossible situation or if you are using the unstable distribution that some required packages have not yet been created or been moved out of Incoming. The following information may help to resolve the situation: The following packages have unmet dependencies: orca : Depends: python2:any but it is not installable E: Broken packages Orca requires python3, not python2. -- System Information: Debian Release: trixie/sid APT prefers unstable APT policy: (500, 'unstable') Architecture: amd64 (x86_64) Kernel: Linux 6.5.0-1-amd64 (SMP w/2 CPU threads; PREEMPT) Kernel taint flags: 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
Bug#1051227: marked as done (grub2: Block the 2.12 transition to testing)
Your message dated Mon, 9 Oct 2023 12:26:43 +0200 with message-id <20231009122534.ga205...@debian.org> and subject line Re: Bug#1051227: grub2: Block the 2.12 transition to testing has caused the Debian Bug report #1051227, regarding grub2: Block the 2.12 transition to testing 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.) -- 1051227: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1051227 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: grub2 Version: 2.12~rc1-7 Severity: serious X-Debbugs-Cc: j...@debian.org This bug is a blocking bug for grub2 to be lifted in in October barring further issues such that we get more testing. I sadly forgot to also adjust urgency to low. -- debian developer - deb.li/jak | jak-linux.org - free software dev ubuntu core developer i speak de, en signature.asc Description: PGP signature --- End Message --- --- Begin Message --- On Mon, Sep 04, 2023 at 08:24:15PM +0200, Julian Andres Klode wrote: > Source: grub2 > Version: 2.12~rc1-7 > Severity: serious > X-Debbugs-Cc: j...@debian.org > > This bug is a blocking bug for grub2 to be lifted in in October > barring further issues such that we get more testing. > > I sadly forgot to also adjust urgency to low. Going to lift this bug now, but the XFS one still remains in review upstream so we're going to have to wait for it to migrate. Hence I'll be uploading 2.06-13+deb13u1 via testing-proposed-updates to get the security update out to people. -- debian developer - deb.li/jak | jak-linux.org - free software dev ubuntu core developer i speak de, en signature.asc Description: PGP signature --- End Message ---
Bug#1053302: marked as done (pytorch-sparse: FTBFS on arm64)
Your message dated Mon, 9 Oct 2023 12:38:18 +0300
with message-id <5d801ff9-9c4a-f508-26af-dd8e0ecf4...@debian.org>
and subject line Re: pytorch-sparse: FTBFS on arm64
has caused the Debian Bug report #1053302,
regarding pytorch-sparse: FTBFS on arm64
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.)
--
1053302: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1053302
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: pytorch-sparse
Version: 0.6.17-1
Severity: serious
Tags: ftbfs sid trixie
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=pytorch-sparse&arch=arm64&ver=0.6.17-1&stamp=1694243524&raw=0
=== FAILURES ===
test_spmm[dtype5-device5-sum] _
dtype = torch.float32, device = device(type='cpu'), reduce = 'sum'
@pytest.mark.parametrize('dtype,device,reduce',
product(grad_dtypes, devices, reductions))
def test_spmm(dtype, device, reduce):
if device == torch.device('cuda:0') and dtype == torch.bfloat16:
return # Not yet implemented.
src = torch.randn((10, 8), dtype=dtype, device=device)
src[2:4, :] = 0 # Remove multiple rows.
src[:, 2:4] = 0 # Remove multiple columns.
src = SparseTensor.from_dense(src).requires_grad_()
row, col, value = src.coo()
other = torch.randn((2, 8, 2), dtype=dtype, device=device,
requires_grad=True)
src_col = other.index_select(-2, col) * value.unsqueeze(-1)
expected = torch_scatter.scatter(src_col, row, dim=-2, reduce=reduce)
if reduce == 'min':
expected[expected > 1000] = 0
if reduce == 'max':
expected[expected < -1000] = 0
grad_out = torch.randn_like(expected)
expected.backward(grad_out)
expected_grad_value = value.grad
value.grad = None
expected_grad_other = other.grad
other.grad = None
out = matmul(src, other, reduce)
out.backward(grad_out)
atol = 1e-7
if dtype == torch.float16 or dtype == torch.bfloat16:
atol = 1e-1
assert torch.allclose(expected, out, atol=atol)
assert torch.allclose(expected_grad_value, value.grad, atol=atol)
> assert torch.allclose(expected_grad_other, other.grad, atol=atol)
E assert False
E+ where False = (tensor([[[-1.2813e+00, -1.5149e+00],\n [-5.9411e-02,
-3.7580e-01],\n [ 0.e+00, 0.e+00],\n ...e+00],\n
[ 1.9554e+00, 2.9660e+00],\n [-2.2483e+00, -2.2663e+00],\n [
4.1025e-03, -9.0971e-01]]]), tensor([[[-1.2813e+00, -1.5149e+00],\n
[-5.9411e-02, -3.7580e-01],\n [ 0.e+00, 0.e+00],\n
...e+00],\n [ 1.9554e+00, 2.9660e+00],\n [-2.2483e+00,
-2.2663e+00],\n [ 4.1023e-03, -9.0971e-01]]]), atol=1e-07)
E+where
= torch.allclose
E+and tensor([[[-1.2813e+00, -1.5149e+00],\n
[-5.9411e-02, -3.7580e-01],\n [ 0.e+00, 0.e+00],\n
...e+00],\n [ 1.9554e+00, 2.9660e+00],\n [-2.2483e+00,
-2.2663e+00],\n [ 4.1023e-03, -9.0971e-01]]]) = tensor([[[ 4.5925e-01,
-1.0188e+00],\n [ 1.6147e-03, 1.0610e+00],\n [-1.3520e+00,
-9.0994e-01],\n ...0452e-01, 7.3244e-01],\n [-1.1243e+00,
6.4083e-01],\n [ 6.1791e-01, 2.0024e-01]]], requires_grad=True).grad
test/test_matmul.py:51: AssertionError
=== warnings summary ===
.pybuild/cpython3_3.11_torch-sparse/build/test/test_matmul.py::test_spspmm[dtype1-device1]
/<>/.pybuild/cpython3_3.11_torch-sparse/build/torch_sparse/matmul.py:97:
UserWarning: Sparse CSR tensor support is in beta state. If you miss a
functionality in the sparse tensor support, please submit a feature request to
https://github.com/pytorch/pytorch/issues. (Triggered internally at
./aten/src/ATen/SparseCsrTensorImpl.cpp:54.)
C = torch.sparse.mm(A, B)
-- Docs: https://docs.pytest.org/en/stable/how-to/capture-warnings.html
=== short test summary info
FAILED test/test_matmul.py::test_spmm[dtype5-device5-sum] - assert False
Cheers
--
Sebastian Ramacher
--- End Message ---
--- Begin Message ---
Version: 0.6.18-1
Hi
Bug#1053314: Depends: python3-h5py-mpi without python3-h5py
On 2023-10-09 08:30, Rafael Laboissière wrote: Thanks for this detailed explanation, Drew. I released version 3.1.0+dfsg2-5 of the xmds2 package before reading it. I added python3-h5py to Build-Depends and libhdf5-mpi-dev to Depends, as you suggested (even though there is a typo in the debian/changelog entry, stating eroneaously that libhdf5-serial-dev has been added; I will fix this in the next release). I also used H5PY_ALWAYS_USE_MPI=1, as you mentioned. As regards adding also python3-h5py-serial to Depends and putting a fallback code in place, I will have to give it a little thought. Maybe, I should discuss this with the upstream authors, to know what they thing. Let us see how things evolve. At least, I hope that version 3.1.0+dfsg2-5 will really fix Bug#1053314 and the h5py transition will be completed. Keep in mind when I discussed the fallback mechanism, I meant the way it is handled in the h5py package (h5py/__init__.py), not xmds2 directly. If xmds2 itself doesn't really care which variant of h5py it uses, then (in terms of xdms2 runtime) it can just import h5py as normal and let h5py figure out which variant it's serving up. (although it might need to Depend on both variants to ensure they're both available) But it would be helpful to hear from xmds2 upstream what their intentions with h5py and MPI are, especially given that xmds2 links to libhdf5 directly. Drew
Bug#1053700: python-xarray: autopkgtest regression on s390x
Source: python-xarray
Version: 2023.09.0-2
Severity: serious
User: debian...@lists.debian.org
Usertags: regression
Hi Maintainer
There are new autopkgtest failures on s390x [1] which seem to be
related to endianness, dtype('>M8[ns]') vs dtype('https://ci.debian.net/packages/p/python-xarray/unstable/s390x/
207s _
test_roundtrip_datetime64_nanosecond_precision[1677-09-21T00:12:43.145224193-ns-int64-20-True]
_
207s
207s timestr = '1677-09-21T00:12:43.145224193', timeunit = 'ns'
207s dtype = , fill_value = 20, use_encoding = True
207s
207s @pytest.mark.parametrize(
207s "timestr, timeunit, dtype, fill_value, use_encoding",
207s [
207s ("1677-09-21T00:12:43.145224193", "ns", np.int64, 20, True),
207s ("1970-09-21T00:12:44.145224808", "ns", np.float64,
1e30, True),
207s (
207s "1677-09-21T00:12:43.145225216",
207s "ns",
207s np.float64,
207s -9.223372036854776e18,
207s True,
207s ),
207s ("1677-09-21T00:12:43.145224193", "ns", np.int64, None, False),
207s ("1677-09-21T00:12:43.145225", "us", np.int64, None, False),
207s ("1970-01-01T00:00:01.01", "us", np.int64, None, False),
207s ("1677-09-21T00:21:52.901038080", "ns", np.float32,
20.0, True),
207s ],
207s )
207s def test_roundtrip_datetime64_nanosecond_precision(
207s timestr: str,
207s timeunit: str,
207s dtype: np.typing.DTypeLike,
207s fill_value: int | float | None,
207s use_encoding: bool,
207s ) -> None:
207s # test for GH7817
207s time = np.datetime64(timestr, timeunit)
207s times = [np.datetime64("1970-01-01T00:00:00", timeunit),
np.datetime64("NaT"), time]
207s
207s if use_encoding:
207s encoding = dict(dtype=dtype, _FillValue=fill_value)
207s else:
207s encoding = {}
207s
207s var = Variable(["time"], times, encoding=encoding)
207s > assert var.dtype == np.dtype("M8[ns]') == dtype('M8[ns]') = \narray(['1970-01-01T00:00:00.0',
'NaT',\n '1677-09-21T00:12:43.145224193'],
dtype='datetime64[ns]').dtype
207s E+ and dtype('(' = np.dtype
Bug#1052773: marked as done (python-tempora: FTBFS: dh_auto_test: error: pybuild --test --test-pytest -i python{version} -p 3.11 returned exit code 13)
Your message dated Mon, 09 Oct 2023 08:43:08 +
with message-id
and subject line Bug#1052773: fixed in python-tempora 5.5.0-1
has caused the Debian Bug report #1052773,
regarding python-tempora: FTBFS: dh_auto_test: error: pybuild --test
--test-pytest -i python{version} -p 3.11 returned exit code 13
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.)
--
1052773: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1052773
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: python-tempora
Version: 5.3.0-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):
> debian/rules binary
> dh binary --with python3 --buildsystem=pybuild --test-pytest
>dh_update_autotools_config -O--buildsystem=pybuild -O--test-pytest
>dh_autoreconf -O--buildsystem=pybuild -O--test-pytest
>dh_auto_configure -O--buildsystem=pybuild -O--test-pytest
>dh_auto_build -O--buildsystem=pybuild -O--test-pytest
> I: pybuild plugin_pyproject:110: Building wheel for python3.11 with "build"
> module
> I: pybuild base:291: python3.11 -m build --skip-dependency-check
> --no-isolation --wheel --outdir
> /<>/.pybuild/cpython3_3.11_tempora
> * Building wheel...
> running bdist_wheel
> running build
> running build_py
> creating build
> creating build/lib
> creating build/lib/tempora
> copying tempora/__init__.py -> build/lib/tempora
> copying tempora/timing.py -> build/lib/tempora
> copying tempora/schedule.py -> build/lib/tempora
> copying tempora/utc.py -> build/lib/tempora
> running egg_info
> creating tempora.egg-info
> writing tempora.egg-info/PKG-INFO
> writing dependency_links to tempora.egg-info/dependency_links.txt
> writing entry points to tempora.egg-info/entry_points.txt
> writing requirements to tempora.egg-info/requires.txt
> writing top-level names to tempora.egg-info/top_level.txt
> writing manifest file 'tempora.egg-info/SOURCES.txt'
> reading manifest file 'tempora.egg-info/SOURCES.txt'
> adding license file 'LICENSE'
> writing manifest file 'tempora.egg-info/SOURCES.txt'
> installing to build/bdist.linux-x86_64/wheel
> running install
> running install_lib
> creating build/bdist.linux-x86_64
> creating build/bdist.linux-x86_64/wheel
> creating build/bdist.linux-x86_64/wheel/tempora
> copying build/lib/tempora/__init__.py ->
> build/bdist.linux-x86_64/wheel/tempora
> copying build/lib/tempora/timing.py -> build/bdist.linux-x86_64/wheel/tempora
> copying build/lib/tempora/schedule.py ->
> build/bdist.linux-x86_64/wheel/tempora
> copying build/lib/tempora/utc.py -> build/bdist.linux-x86_64/wheel/tempora
> running install_egg_info
> Copying tempora.egg-info to
> build/bdist.linux-x86_64/wheel/tempora-5.3.0.egg-info
> running install_scripts
> creating build/bdist.linux-x86_64/wheel/tempora-5.3.0.dist-info/WHEEL
> creating
> '/<>/.pybuild/cpython3_3.11_tempora/.tmp-ufwl34rz/tempora-5.3.0-py3-none-any.whl'
> and adding 'build/bdist.linux-x86_64/wheel' to it
> adding 'tempora/__init__.py'
> adding 'tempora/schedule.py'
> adding 'tempora/timing.py'
> adding 'tempora/utc.py'
> adding 'tempora-5.3.0.dist-info/LICENSE'
> adding 'tempora-5.3.0.dist-info/METADATA'
> adding 'tempora-5.3.0.dist-info/WHEEL'
> adding 'tempora-5.3.0.dist-info/entry_points.txt'
> adding 'tempora-5.3.0.dist-info/top_level.txt'
> adding 'tempora-5.3.0.dist-info/RECORD'
> removing build/bdist.linux-x86_64/wheel
> Successfully built tempora-5.3.0-py3-none-any.whl
> I: pybuild plugin_pyproject:122: Unpacking wheel built for python3.11 with
> "installer" module
>dh_auto_test -O--buildsystem=pybuild -O--test-pytest
> I: pybuild pybuild:314: cp -va /<>/pytest.ini
> /<>/tests /<>/.pybuild/cpython3_3.11_tempora/build/
> '/<>/pytest.ini' ->
> '/<>/.pybuild/cpython3_3.11_tempora/build/pytest.ini'
> '/<>/tests' ->
> '/<>/.pybuild/cpython3_3.11_tempora/build/tests'
> '/<>/tests/test_schedule.py' ->
> '/<>/.pybuild/cpython3_3.11_tempora/build/tests/test_schedule.py'
> '/<>/tests/test_timing.py' ->
> '/<>/.pybuild/cpython3_3.11_tempora/build/tests/test_timing.py'
> I: pybuild base:291: cd
> /<>/.pybuild/cpython3_3.11_tempora/build; python3.11 -m pytest
> -k 'not tempora.get_nearest_year_for_day'
> = test session starts
> ==
> platform linux -- Python 3.11.5, pytest-7.4.2, pluggy-1.3.0
> rootdir: /<>/.pybuild/cpython3_3.11_tempora/build
> configfile: pytest.ini
> collected 42 items / 1 desele
Bug#1053314: marked as done (Depends: python3-h5py-mpi without python3-h5py)
Your message dated Mon, 09 Oct 2023 08:44:07 + with message-id and subject line Bug#1053314: fixed in xmds2 3.1.0+dfsg2-5 has caused the Debian Bug report #1053314, regarding Depends: python3-h5py-mpi without python3-h5py 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.) -- 1053314: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1053314 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: xmds2 Version: 3.1.0+dfsg2-4 Severity: serious Justification: debci xmds2 Depends: python3-h5py-mpi without depending on python3-h5py python3-h5py-mpi only provides the h5py._debian_h5py_mpi namespace, not h5py. Hence tests using h5py without specifying _debian_h5py_mpi fail. This is the case with h5py 3.9.0. (Marking Severity: serious due to debci failure) python3-h5py provides the h5py namespace, so if xmds2 strictly needs the mpi build, but accessing via the generic h5py namespace, then the Depends should specify both packages Depends: python3-h5py python3-h5py-mpi Note there seems to be an inconsistency in the xmds2 package configuration. It has MPI dependencies (python3-h5py-mpi, also mpi-default-dev, libfftw3-mpi-dev), but with respect to hdf5 it has Depends: libhdf5-serial-dev Should that instead be Depends: libhdf5-mpi-dev ? --- End Message --- --- Begin Message --- Source: xmds2 Source-Version: 3.1.0+dfsg2-5 Done: Rafael Laboissière We believe that the bug you reported is fixed in the latest version of xmds2, 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 1053...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Rafael Laboissière (supplier of updated xmds2 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: Sun, 08 Oct 2023 14:24:24 -0300 Source: xmds2 Architecture: source Version: 3.1.0+dfsg2-5 Distribution: unstable Urgency: medium Maintainer: Debian Science Team Changed-By: Rafael Laboissière Closes: 1053314 Changes: xmds2 (3.1.0+dfsg2-5) unstable; urgency=medium . * Fix dependencies on h5py + d/control: - Build-depend on python3-h5py - Depend on libhdf5-serial-dev + d/p/h5py-always-use-mpi.patch: New patch Thanks to Drew Parsons for the suggestions and Nilesh Patra for the discussion. (Closes: #1053314) Checksums-Sha1: a5214b2dffa04e7e32da784eb6d507cdd9914a37 2850 xmds2_3.1.0+dfsg2-5.dsc 00d53e47a4663a3849e5adb5bd0de57f1061639e 16520 xmds2_3.1.0+dfsg2-5.debian.tar.xz Checksums-Sha256: dca81b73cc2653bbd8e7c96e7d3d00b3e1e2391e106c7e2eef8c97bd8640184b 2850 xmds2_3.1.0+dfsg2-5.dsc 0d9189dfefd4fd0a26057a153918bb5be7a56ee8c272a625a686c5c0db8b9155 16520 xmds2_3.1.0+dfsg2-5.debian.tar.xz Files: 8865c79458d3d14757a2be9ca0b57a35 2850 science optional xmds2_3.1.0+dfsg2-5.dsc b348753afefdc553f61338e61f019f74 16520 science optional xmds2_3.1.0+dfsg2-5.debian.tar.xz -BEGIN PGP SIGNATURE- iQIzBAEBCAAdFiEEP0ZDkUmP6HS9tdmPISSqGYN4XJAFAmUjsFwACgkQISSqGYN4 XJClCQ//dlwLDK42OOJtQgXrVvHkOA7wYFzPPJsISSnAPpd43Wic94X5JdZrPRZt Asf8+xCt3H59bl7Th48EUJ1pxNBJrpRJU9AW2vo0i+oU5qqAGblBbGVbgWAGLBcF MKqSwa8o9hBtU2ubuluAJTeIJWXqQF02VYF2feawsyu6bi5DyvKskfWAWWuDkBKI Eqx2kaC7UhNkrDsHnVM7aJ/XT66krez6XuYfpthA90AZAyn65c/z88GcqmkUq+2R B3G3W2Tdnu40isJJonhWEOl+oaeXsncuJzqZ7/OSUZsea23MbadmEmwUDZUWio3t k69ZDQWR94F77zfA71CwCwau+dzCmgKbmXw+mIqeJKyqsBpd9QYMFsp8MLUsGtI/ WVTL8s9lST0ZDUlbXn23QGwLaTfpR3ddmuvR3hGkOjl+XbuKsiEUBEVJ5zh7JGCL cnHfjOUPKCSLh66hmMKJ/KpK3SnT+PiOoAOPVK55/kV55fvuj0w9SfteUBT1TtAW UTLdo/wcVv4NKYQMDW9lU0FU9kCmyMNC65gYSYDhKxqCBkRTU75I4nAQigQojrsg 4GYOTa0Nky89dNbF0rJdVua4kv80qVH1I3xVt6lK/OYiQ8s0mXN8buIhtM/ed1fM h8XTijJ4RYhBM09hIsXrUz0NYIToumU3WCqTo+7GmpnaqbAJS7k= =jZ4H -END PGP SIGNATURE End Message ---
Processed: Bug#1052773 marked as pending in python-tempora
Processing control commands:
> tag -1 pending
Bug #1052773 [src:python-tempora] python-tempora: FTBFS: dh_auto_test: error:
pybuild --test --test-pytest -i python{version} -p 3.11 returned exit code 13
Added tag(s) pending.
--
1052773: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1052773
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Bug#1052773: marked as pending in python-tempora
Control: tag -1 pending Hello, Bug #1052773 in python-tempora 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/python-team/packages/python-tempora/-/commit/f3428212c1df1a22d7bf514f46523bad9673be8e Control, tests: add (build-)depends on tzdata-legacy to avoid issues with missing timezones caused by changes in tzdata/2023c-8 (Closes: #1052773). (this message was generated automatically) -- Greetings https://bugs.debian.org/1052773
