Bug#1052866: python-plaster: FTBFS: dh_auto_test: error: pybuild --test --test-pytest -i python{version} -p 3.11 returned exit code 13
Hi, I upgraded python-plaster to latest upstream - but this did not changed the test suite error. Kind regards Andreas. -- http://fam-tille.de
Bug#1061659: src:golang-github-hanwen-go-fuse: fails to migrate to testing for too long: i386 autopkgtest regression
Source: golang-github-hanwen-go-fuse Version: 2.1.0+git20220822.58a7e14-1 Severity: serious Control: close -1 2.4.2-1 Tags: sid trixie User: release.debian@packages.debian.org Usertags: out-of-sync Dear maintainer(s), The Release Team considers packages that are out-of-sync between testing and unstable for more than 30 days as having a Release Critical bug in testing [1]. Your package src:golang-github-hanwen-go-fuse has been trying to migrate for 31 days [2]. Hence, I am filing this bug. The version in unstable fails its own autopkgtest on i386. If a package is out of sync between unstable and testing for a longer period, this usually means that bugs in the package in testing cannot be fixed via unstable. Additionally, blocked packages can have impact on other packages, which makes preparing for the release more difficult. Finally, it often exposes issues with the package and/or its (reverse-)dependencies. We expect maintainers to fix issues that hamper the migration of their package in a timely manner. This bug will trigger auto-removal when appropriate. As with all new bugs, there will be at least 30 days before the package is auto-removed. I have immediately closed this bug with the version in unstable, so if that version or a later version migrates, this bug will no longer affect testing. I have also tagged this bug to only affect sid and trixie, so it doesn't affect (old-)stable. If you believe your package is unable to migrate to testing due to issues beyond your control, don't hesitate to contact the Release Team. Paul [1] https://lists.debian.org/debian-devel-announce/2023/06/msg1.html [2] https://qa.debian.org/excuses.php?package=golang-github-hanwen-go-fuse OpenPGP_signature.asc Description: OpenPGP digital signature
Processed: src:golang-github-hanwen-go-fuse: fails to migrate to testing for too long: i386 autopkgtest regression
Processing control commands: > close -1 2.4.2-1 Bug #1061659 [src:golang-github-hanwen-go-fuse] src:golang-github-hanwen-go-fuse: fails to migrate to testing for too long: i386 autopkgtest regression Marked as fixed in versions golang-github-hanwen-go-fuse/2.4.2-1. Bug #1061659 [src:golang-github-hanwen-go-fuse] src:golang-github-hanwen-go-fuse: fails to migrate to testing for too long: i386 autopkgtest regression Marked Bug as done -- 1061659: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1061659 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1052861: marked as done (pastedeploy: FTBFS: dh_auto_test: error: pybuild --test --test-pytest -i python{version} -p 3.11 returned exit code 13)
Your message dated Sun, 28 Jan 2024 08:25:30 +0100
with message-id
and subject line Re: pastedeploy: FTBFS: dh_auto_test: error: pybuild --test
--test-pytest -i python{version} -p 3.11 returned exit code 13
has caused the Debian Bug report #1052861,
regarding pastedeploy: 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.)
--
1052861: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1052861
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: pastedeploy
Version: 3.0.1-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.
Relevant part (hopefully):
> === short test summary info
>
> FAILED tests/test_basic_app.py::test_main - LookupError: Entry point
> 'basic_a...
> FAILED tests/test_basic_app.py::test_other - LookupError: Entry point
> 'other'...
> FAILED tests/test_basic_app.py::test_composit - LookupError: Entry point
> 'rem...
> FAILED tests/test_config.py::test_config_egg - LookupError: Entry point
> 'conf...
> FAILED tests/test_config.py::test_config1 - LookupError: Entry point
> 'confige...
> FAILED tests/test_config.py::test_config2 - LookupError: Entry point
> 'confige...
> FAILED tests/test_config.py::test_config3 - LookupError: Entry point
> 'confige...
> FAILED tests/test_config.py::test_config_get - LookupError: Entry point
> 'conf...
> FAILED tests/test_config.py::test_appconfig - LookupError: Entry point
> 'confi...
> FAILED tests/test_config.py::test_appconfig_filter_with - LookupError: Entry
> ...
> FAILED tests/test_config.py::test_global_conf - LookupError: Entry point
> 'con...
> FAILED tests/test_filter.py::test_filter_app - LookupError: Entry point
> 'basi...
> FAILED tests/test_filter.py::test_pipeline - LookupError: Entry point
> 'basic_...
> FAILED tests/test_filter.py::test_filter_app2 - LookupError: Entry point
> 'bas...
> FAILED tests/test_filter.py::test_pipeline2 - LookupError: Entry point
> 'basic...
> FAILED tests/test_filter.py::test_filter_app_inverted - LookupError: Entry
> po...
> FAILED tests/test_filter.py::test_filter_with_filter_with - LookupError:
> Entr...
> === 17 failed, 9 passed, 1 skipped in 2.87s
>
> E: pybuild pybuild:395: test: plugin pyproject failed with: exit code=1: cd
> /<>/.pybuild/cpython3_3.11_pastedeploy/build; python3.11 -m
> pytest tests
> dh_auto_test: error: pybuild --test --test-pytest -i python{version} -p 3.11
> returned exit code 13
The full build log is available from:
http://qa-logs.debian.net/2023/09/25/pastedeploy_3.0.1-5_unstable.log
All bugs filed during this archive rebuild are listed at:
https://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=ftbfs-20230925;users=lu...@debian.org
or:
https://udd.debian.org/bugs/?release=na&merged=ign&fnewerval=7&flastmodval=7&fusertag=only&fusertagtag=ftbfs-20230925&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 ---
Closing bug which was not closed in changelog of latest upload of package 3.1-1
--
http://fam-tille.de--- End Message ---
Bug#1052826: Broken entrypoints package: actually a pybuild issue?
Hi Jullien, upstream page[1] says: This package is in maintenance-only mode. New code should use the importlib.metadata module in the Python standard library to find and load entry points. So it seems we do not need adapt you patch very frequently since no changes will be to be expected (but the dependencies of entrypoint should be adapted. Kind regards Andreas. [1] https://github.com/takluyver/entrypoints -- http://fam-tille.de
Bug#1061655: wine: FTBFS with error: unknown conversion type character ‘I’ in format [-Werror=format=]
Package: wine
Version: 9.0~repack-2
Severity: serious
The source package fail to build on armel and armhf with the following error.
programs/winedbg/info.c:356:27: error: unknown conversion type character ‘I’ in
format [-Werror=format=]
356 | dbg_printf("'0x%0*I64lld' is not a valid module address\n",
ADDRWIDTH, base);
| ^
programs/winedbg/info.c:356:20: error: too many arguments for format
[-Werror=format-extra-args]
356 | dbg_printf("'0x%0*I64lld' is not a valid module address\n",
ADDRWIDTH, base);
|^~~
The build failures are available from
https://buildd.debian.org/status/package.php?p=wine >.
The issue seem to have been introduced in an upstream commit 2021-10-12:
commit 3a869c1f9ba8a35eb0781fc5cb0b6684a9a7960b
Author: Eric Pouech
Date: Tue Oct 12 18:10:58 2021 +0200
winedbg: Simplify some printing of addresses.
Signed-off-by: Eric Pouech
Signed-off-by: Alexandre Julliard
diff --git a/programs/winedbg/info.c b/programs/winedbg/info.c
index dc0e6591f1f..477438d83e3 100644
--- a/programs/winedbg/info.c
+++ b/programs/winedbg/info.c
@@ -284,7 +284,7 @@ void info_win32_module(DWORD64 base)
HeapFree(GetProcessHeap(), 0, im.modules);
if (base && !num_printed)
-dbg_printf("'0x%x%08x' is not a valid module address\n", (DWORD)(base
>> 32), (DWORD)b
ase);
+dbg_printf("'0x%0*I64x' is not a valid module address\n", ADDRWIDTH,
base);
}
struct class_walker
I do not understand the printf() notation well enough to understand what
is wrong. According to printf(3) in glibc 2.36, the I flag was added in
glibc 2.2. Could it be a compiler error, that the compiler do not
understand this "new" flag?
--
Happy hacking
Petter Reinholdtsen
Processed: Re: Bug#1061650: elpa-dpkg-dev-el: fails to install: debian-bts-control.el:85:2: Error: Cannot open load file: No such file or directory, debian-bug
Processing control commands: > tags -1 pending Bug #1061650 [elpa-dpkg-dev-el] elpa-dpkg-dev-el: fails to install: debian-bts-control.el:85:2: Error: Cannot open load file: No such file or directory, debian-bug Ignoring request to alter tags of bug #1061650 to the same tags previously set -- 1061650: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1061650 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: Re: Bug#1061650: elpa-dpkg-dev-el: fails to install: debian-bts-control.el:85:2: Error: Cannot open load file: No such file or directory, debian-bug
Processing control commands: > tags -1 pending Bug #1061650 [elpa-dpkg-dev-el] elpa-dpkg-dev-el: fails to install: debian-bts-control.el:85:2: Error: Cannot open load file: No such file or directory, debian-bug Added tag(s) pending. -- 1061650: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1061650 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1061650: elpa-dpkg-dev-el: fails to install: debian-bts-control.el:85:2: Error: Cannot open load file: No such file or directory, debian-bug
Control: tags -1 pending Hi Andreas, Andreas Beckmann writes: > Package: elpa-dpkg-dev-el > Version: 37.10 > Severity: serious > User: debian...@lists.debian.org > Usertags: piuparts > > Hi, > > during a test with piuparts I noticed your package failed to install. > >>From the attached log (scroll to the bottom...): > > Setting up elpa-dpkg-dev-el (37.10) ... > Install emacsen-common for emacs > emacsen-common: Handling install of emacsen flavor emacs > Install elpa-dpkg-dev-el for emacs > install/dpkg-dev-el-37.10: Handling install of emacsen flavor emacs > install/dpkg-dev-el-37.10: byte-compiling for emacs > > In toplevel form: > debian-bts-control.el:85:2: Error: Cannot open load file: No such file or > directory, debian-bug > > In debian-changelog-mode: > debian-changelog-mode.el:1382:4: Warning: `easy-menu-add' is an obsolete > function (as of 28.1); this was always a no-op in Emacs and can be safely > removed. > debian-changelog-mode.el:1382:18: Warning: reference to free variable > `debian-changelog-menu' > debian-changelog-mode.el:1423:4: Warning: `make-face' called with 2 > arguments, but accepts only 1 > debian-changelog-mode.el:1428:4: Warning: `set-face-foreground' called with > 5 arguments, but accepts only 2 or 3 > > In end of data: > debian-changelog-mode.el:1679:12: Warning: the function > `set-extent-property' is not known to be defined. > debian-changelog-mode.el:1676:25: Warning: the function `make-extent' is > not known to be defined. > debian-changelog-mode.el:1654:18: Warning: the function `delete-extent' is > not known to be defined. > debian-changelog-mode.el:1653:42: Warning: the function > `extent-end-position' is not known to be defined. > debian-changelog-mode.el:1652:42: Warning: the function > `extent-start-position' is not known to be defined. > debian-changelog-mode.el:1651:22: Warning: the function `extent-detached-p' > is not known to be defined. > debian-changelog-mode.el:1625:14: Warning: the function `set-keymap-name' > is not known to be defined. > debian-changelog-mode.el:880:4: Warning: the function > `debian-bug-build-bug-menu' is not known to be defined. > > In toplevel form: > debian-control-mode.el:198:11: Warning: `max-specpdl-size' is an obsolete > variable (as of 29.1). > debian-control-mode.el:206:11: Warning: `max-specpdl-size' is an obsolete > variable (as of 29.1). > > In debian-control-mode: > debian-control-mode.el:269:4: Warning: `easy-menu-add' is an obsolete > function (as of 28.1); this was always a no-op in Emacs and can be safely > removed. > debian-control-mode.el:270:34: Warning: reference to free variable > `goto-address-highlight-p' > > In end of data: > debian-control-mode.el:424:28: Warning: the function `position' is not > known to be defined. > debian-control-mode.el:408:43: Warning: the function `subseq' is not known > to be defined. > > In debian-copyright-mode: > debian-copyright.el:76:16: Warning: reference to free variable > `goto-address-highlight-p' > > In toplevel form: > dpkg-dev-el.el:118:44: Warning: reference to free variable `filename' > > In readme-debian-update-timestamp: > readme-debian.el:64:2: Warning: docstring wider than 80 characters > readme-debian.el:67:6: Warning: `goto-line' is for interactive use only; > use `forward-line' instead. > > In readme-debian-mode: > readme-debian.el:119:14: Warning: `write-contents-hooks' is an obsolete > variable (as of 22.1); use `write-contents-functions' instead. > > In end of data: > readme-debian.el:118:8: Warning: the function `make-local-hook' is not > known to be defined. > ERROR: install script from elpa-dpkg-dev-el package failed > dpkg: error processing package elpa-dpkg-dev-el (--configure): >installed elpa-dpkg-dev-el package post-installation script subprocess > returned error exit status 1 > Errors were encountered while processing: >elpa-dpkg-dev-el > > > Cheers, > > Andreas > > Thanks for detecting the bug! It looks like without byte-compiling we weren't able to detect such issue when building. I have added the missing dependency of elpa-debian-el[1] and prepared another version on mentors[2] for which I would need a sponsor. TIA! [1] https://salsa.debian.org/emacsen-team/dpkg-dev-el/-/commit/5d6a77b97440ee9da7d0209bf7e7579506c8b8b2 [2] https://mentors.debian.net/package/dpkg-dev-el/ -- Xiyue Deng
Bug#1042325: marked as done (python-miio: FTBFS: dh_auto_test: error: pybuild --test --test-pytest -i python{version} -p 3.11 returned exit code 13)
Your message dated Sun, 28 Jan 2024 03:53:22 +
with message-id
and subject line Bug#1042325: fixed in python-miio 0.5.12-1
has caused the Debian Bug report #1042325,
regarding python-miio: 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.)
--
1042325: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1042325
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: python-miio
Version: 0.5.0.1-2
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):
> make[1]: Entering directory '/<>'
> # the core file must not exist before tests are run
> [ -z "$(find ./.pybuild -regex './.pybuild/cpython3_[0-9.]+/build/core'
> -print -quit)" ] || exit 1
> dh_auto_test
> I: pybuild base:240: cd /<>/.pybuild/cpython3_3.11/build;
> python3.11 -m pytest
> = test session starts
> ==
> platform linux -- Python 3.11.4, pytest-7.4.0, pluggy-1.2.0
> rootdir: /<>
> collected 0 items / 28 errors
>
> ERRORS
>
> _ ERROR collecting
> .pybuild/cpython3_3.11/build/miio/tests/test_airconditioningcompanion.py _
> ImportError while importing test module
> '/<>/.pybuild/cpython3_3.11/build/miio/tests/test_airconditioningcompanion.py'.
> Hint: make sure your test modules/packages have valid Python names.
> Traceback:
> /usr/lib/python3.11/importlib/__init__.py:126: in import_module
> return _bootstrap._gcd_import(name[level:], package, level)
> miio/__init__.py:15: in
> from miio.aqaracamera import AqaraCamera
> miio/aqaracamera.py:14: in
> import attr
> E ModuleNotFoundError: No module named 'attr'
> _ ERROR collecting
> .pybuild/cpython3_3.11/build/miio/tests/test_airdehumidifier.py _
> ImportError while importing test module
> '/<>/.pybuild/cpython3_3.11/build/miio/tests/test_airdehumidifier.py'.
> Hint: make sure your test modules/packages have valid Python names.
> Traceback:
> /usr/lib/python3.11/importlib/__init__.py:126: in import_module
> return _bootstrap._gcd_import(name[level:], package, level)
> miio/__init__.py:15: in
> from miio.aqaracamera import AqaraCamera
> miio/aqaracamera.py:14: in
> import attr
> E ModuleNotFoundError: No module named 'attr'
> _ ERROR collecting
> .pybuild/cpython3_3.11/build/miio/tests/test_airfilter_util.py _
> ImportError while importing test module
> '/<>/.pybuild/cpython3_3.11/build/miio/tests/test_airfilter_util.py'.
> Hint: make sure your test modules/packages have valid Python names.
> Traceback:
> /usr/lib/python3.11/importlib/__init__.py:126: in import_module
> return _bootstrap._gcd_import(name[level:], package, level)
> miio/__init__.py:15: in
> from miio.aqaracamera import AqaraCamera
> miio/aqaracamera.py:14: in
> import attr
> E ModuleNotFoundError: No module named 'attr'
> __ ERROR collecting .pybuild/cpython3_3.11/build/miio/tests/test_airfresh.py
> ___
> ImportError while importing test module
> '/<>/.pybuild/cpython3_3.11/build/miio/tests/test_airfresh.py'.
> Hint: make sure your test modules/packages have valid Python names.
> Traceback:
> /usr/lib/python3.11/importlib/__init__.py:126: in import_module
> return _bootstrap._gcd_import(name[level:], package, level)
> miio/__init__.py:15: in
> from miio.aqaracamera import AqaraCamera
> miio/aqaracamera.py:14: in
> import attr
> E ModuleNotFoundError: No module named 'attr'
> _ ERROR collecting
> .pybuild/cpython3_3.11/build/miio/tests/test_airfresh_t2017.py _
> ImportError while importing test module
> '/<>/.pybuild/cpython3_3.11/build/miio/tests/test_airfresh_t2017.py'.
> Hint: make sure your test modules/packages have valid Python names.
> Traceback:
> /usr/lib/python3.11/importlib/__init__.py:126: in import_module
> return _bootstrap._gcd_import(name[level:], package, level)
> miio/__init__.py:15: in
> from miio.aqaracamera import AqaraCamera
> miio/aqaracamera.py:14: in
> import attr
> E ModuleNotFoundError: No module named 'attr'
> _ ERROR collecting
> .pybuild/cpython3_3.11/build/miio/tests/test_airhumidifier.py _
> ImportError while importing test module
> '/<>/.pybuild/cpython3_3.11/build/miio/tests/test_airhumidifier.py'.
> Hint: make sure your test modules/packages have valid Python names.
> Traceback
Bug#1042325: python-miio: FTBFS: dh_auto_test: error: pybuild --test --test-pytest -i python{version} -p 3.11 returned exit code 13
On Sat, 27 Jan 2024, Andreas Tille wrote: Control: tags -1 help Hi, I upgraded python-miio in Git. Unfortunately there are some test suite errors[1] Any help would be welcome Andreas. Fixed.
Processed: your mail
Processing commands for cont...@bugs.debian.org: > affects 1061591 src:wine Bug #1061591 [src:rhsrvany] rhsrvany: tests can fail on ci.debian.net due to wine32 installation Added indication that 1061591 affects src:wine > thanks Stopping processing here. Please contact me if you need assistance. -- 1061591: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1061591 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1061650: elpa-dpkg-dev-el: fails to install: debian-bts-control.el:85:2: Error: Cannot open load file: No such file or directory, debian-bug
Package: elpa-dpkg-dev-el Version: 37.10 Severity: serious User: debian...@lists.debian.org Usertags: piuparts Hi, during a test with piuparts I noticed your package failed to install. >From the attached log (scroll to the bottom...): Setting up elpa-dpkg-dev-el (37.10) ... Install emacsen-common for emacs emacsen-common: Handling install of emacsen flavor emacs Install elpa-dpkg-dev-el for emacs install/dpkg-dev-el-37.10: Handling install of emacsen flavor emacs install/dpkg-dev-el-37.10: byte-compiling for emacs In toplevel form: debian-bts-control.el:85:2: Error: Cannot open load file: No such file or directory, debian-bug In debian-changelog-mode: debian-changelog-mode.el:1382:4: Warning: `easy-menu-add' is an obsolete function (as of 28.1); this was always a no-op in Emacs and can be safely removed. debian-changelog-mode.el:1382:18: Warning: reference to free variable `debian-changelog-menu' debian-changelog-mode.el:1423:4: Warning: `make-face' called with 2 arguments, but accepts only 1 debian-changelog-mode.el:1428:4: Warning: `set-face-foreground' called with 5 arguments, but accepts only 2 or 3 In end of data: debian-changelog-mode.el:1679:12: Warning: the function `set-extent-property' is not known to be defined. debian-changelog-mode.el:1676:25: Warning: the function `make-extent' is not known to be defined. debian-changelog-mode.el:1654:18: Warning: the function `delete-extent' is not known to be defined. debian-changelog-mode.el:1653:42: Warning: the function `extent-end-position' is not known to be defined. debian-changelog-mode.el:1652:42: Warning: the function `extent-start-position' is not known to be defined. debian-changelog-mode.el:1651:22: Warning: the function `extent-detached-p' is not known to be defined. debian-changelog-mode.el:1625:14: Warning: the function `set-keymap-name' is not known to be defined. debian-changelog-mode.el:880:4: Warning: the function `debian-bug-build-bug-menu' is not known to be defined. In toplevel form: debian-control-mode.el:198:11: Warning: `max-specpdl-size' is an obsolete variable (as of 29.1). debian-control-mode.el:206:11: Warning: `max-specpdl-size' is an obsolete variable (as of 29.1). In debian-control-mode: debian-control-mode.el:269:4: Warning: `easy-menu-add' is an obsolete function (as of 28.1); this was always a no-op in Emacs and can be safely removed. debian-control-mode.el:270:34: Warning: reference to free variable `goto-address-highlight-p' In end of data: debian-control-mode.el:424:28: Warning: the function `position' is not known to be defined. debian-control-mode.el:408:43: Warning: the function `subseq' is not known to be defined. In debian-copyright-mode: debian-copyright.el:76:16: Warning: reference to free variable `goto-address-highlight-p' In toplevel form: dpkg-dev-el.el:118:44: Warning: reference to free variable `filename' In readme-debian-update-timestamp: readme-debian.el:64:2: Warning: docstring wider than 80 characters readme-debian.el:67:6: Warning: `goto-line' is for interactive use only; use `forward-line' instead. In readme-debian-mode: readme-debian.el:119:14: Warning: `write-contents-hooks' is an obsolete variable (as of 22.1); use `write-contents-functions' instead. In end of data: readme-debian.el:118:8: Warning: the function `make-local-hook' is not known to be defined. ERROR: install script from elpa-dpkg-dev-el package failed dpkg: error processing package elpa-dpkg-dev-el (--configure): installed elpa-dpkg-dev-el package post-installation script subprocess returned error exit status 1 Errors were encountered while processing: elpa-dpkg-dev-el Cheers, Andreas elpa-dpkg-dev-el=37.10_emacs.log.gz Description: application/gzip
Bug#1058502: marked as done (libqtdbusmock: FTBFS: make[3]: *** No rule to make target 'tests/gmock/lib/libgmock_main.a', needed by 'tests/CMakeFiles/unit-tests_autogen_timestamp_deps'. Stop.)
Your message dated Sun, 28 Jan 2024 01:20:14 + with message-id and subject line Bug#1058502: fixed in libqtdbusmock 0.9.1-1 has caused the Debian Bug report #1058502, regarding libqtdbusmock: FTBFS: make[3]: *** No rule to make target 'tests/gmock/lib/libgmock_main.a', needed by 'tests/CMakeFiles/unit-tests_autogen_timestamp_deps'. Stop. 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.) -- 1058502: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1058502 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: libqtdbusmock Version: 0.9.0-2 Severity: serious Justification: FTBFS Tags: trixie sid ftbfs User: lu...@debian.org Usertags: ftbfs-20231212 ftbfs-trixie Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > make[3]: Entering directory '/<>/obj-x86_64-linux-gnu' > cd /<>/obj-x86_64-linux-gnu && /usr/bin/cmake -E cmake_depends > "Unix Makefiles" /<> /<>/tests > /<>/obj-x86_64-linux-gnu > /<>/obj-x86_64-linux-gnu/tests > /<>/obj-x86_64-linux-gnu/tests/CMakeFiles/unit-tests_autogen_timestamp_deps.dir/DependInfo.cmake > "--color=" > make[3]: Leaving directory '/<>/obj-x86_64-linux-gnu' > make -f tests/CMakeFiles/unit-tests_autogen_timestamp_deps.dir/build.make > tests/CMakeFiles/unit-tests_autogen_timestamp_deps.dir/build > make[3]: Entering directory '/<>/obj-x86_64-linux-gnu' > make[3]: *** No rule to make target 'tests/gmock/lib/libgmock_main.a', needed > by 'tests/CMakeFiles/unit-tests_autogen_timestamp_deps'. Stop. > make[3]: Leaving directory '/<>/obj-x86_64-linux-gnu' > make[2]: *** [CMakeFiles/Makefile2:337: > tests/CMakeFiles/unit-tests_autogen_timestamp_deps.dir/all] Error 2 The full build log is available from: http://qa-logs.debian.net/2023/12/12/libqtdbusmock_0.9.0-2_unstable.log All bugs filed during this archive rebuild are listed at: https://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=ftbfs-20231212;users=lu...@debian.org or: https://udd.debian.org/bugs/?release=na&merged=ign&fnewerval=7&flastmodval=7&fusertag=only&fusertagtag=ftbfs-20231212&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: libqtdbusmock Source-Version: 0.9.1-1 Done: Marius Gripsgard We believe that the bug you reported is fixed in the latest version of libqtdbusmock, 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 1058...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Marius Gripsgard (supplier of updated libqtdbusmock 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, 28 Jan 2024 01:59:41 +0100 Source: libqtdbusmock Architecture: source Version: 0.9.1-1 Distribution: unstable Urgency: medium Maintainer: Debian UBports Team Changed-By: Marius Gripsgard Closes: 1058502 Changes: libqtdbusmock (0.9.1-1) unstable; urgency=medium . [ Debian Janitor ] * Apply multi-arch hints. + libqtdbusmock1-dev: Drop Multi-Arch: same. * Set upstream metadata fields: Repository-Browse. . [ Marius Gripsgard ] * New upstream release v0.9.1 * debian/patches: Drop upstreamed patch - 0001-Bump-cpp-std-to-17-fixes-googletest-1.13.0.patch * debian/patches: Add patch to workaround cmake bug (Closes: #1058502) Checksums-Sha1: 8dc8605e762d82f6a6268e661fe492a9f4282135 1770 libqtdbusmock_0.9.1-1.dsc 991dad10707d42e45e72733e673c35aa43497a88 39957 libqtdbusmock_0.9.1.orig.tar.gz 54f065cc969040fd5f5a0d14675bf7aa941bd2c6 6340 libqtdbusmock_0.9.1-1.debian.tar.xz 1b7481b767056af0673240418006d3b00c24d801 12492 libqtdbusmock_0.9.1-1_source.buildinfo Checksums-Sha256: 8a762a1f9a3027ed03e1986a319afaa591e6f42256e
Bug#1058527: marked as done (libqtdbustest: FTBFS: make[3]: *** No rule to make target 'tests/gmock/lib/libgtest.a', needed by 'tests/CMakeFiles/unit-tests_autogen_timestamp_deps'. Stop.)
Your message dated Sun, 28 Jan 2024 01:06:17 + with message-id and subject line Bug#1058527: fixed in libqtdbustest 0.3.2-3 has caused the Debian Bug report #1058527, regarding libqtdbustest: FTBFS: make[3]: *** No rule to make target 'tests/gmock/lib/libgtest.a', needed by 'tests/CMakeFiles/unit-tests_autogen_timestamp_deps'. Stop. 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.) -- 1058527: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1058527 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: libqtdbustest Version: 0.3.2-2 Severity: serious Justification: FTBFS Tags: trixie sid ftbfs User: lu...@debian.org Usertags: ftbfs-20231212 ftbfs-trixie Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > make[3]: Entering directory '/<>/obj-x86_64-linux-gnu' > make[3]: Nothing to be done for > 'src/qdbus-test-runner/CMakeFiles/qdbus-simple-test-runner_autogen_timestamp_deps.dir/build'. > make[3]: Leaving directory '/<>/obj-x86_64-linux-gnu' > make[3]: Leaving directory '/<>/obj-x86_64-linux-gnu' > make -f tests/CMakeFiles/unit-tests_autogen_timestamp_deps.dir/build.make > tests/CMakeFiles/unit-tests_autogen_timestamp_deps.dir/build > make[3]: Entering directory '/<>/obj-x86_64-linux-gnu' > make[3]: *** No rule to make target 'tests/gmock/lib/libgtest.a', needed by > 'tests/CMakeFiles/unit-tests_autogen_timestamp_deps'. Stop. > make[3]: Leaving directory '/<>/obj-x86_64-linux-gnu' > make[2]: *** [CMakeFiles/Makefile2:518: > tests/CMakeFiles/unit-tests_autogen_timestamp_deps.dir/all] Error 2 The full build log is available from: http://qa-logs.debian.net/2023/12/12/libqtdbustest_0.3.2-2_unstable.log All bugs filed during this archive rebuild are listed at: https://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=ftbfs-20231212;users=lu...@debian.org or: https://udd.debian.org/bugs/?release=na&merged=ign&fnewerval=7&flastmodval=7&fusertag=only&fusertagtag=ftbfs-20231212&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: libqtdbustest Source-Version: 0.3.2-3 Done: Marius Gripsgard We believe that the bug you reported is fixed in the latest version of libqtdbustest, 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 1058...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Marius Gripsgard (supplier of updated libqtdbustest 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, 28 Jan 2024 01:35:54 +0100 Source: libqtdbustest Architecture: source Version: 0.3.2-3 Distribution: unstable Urgency: medium Maintainer: Debian UBports Team Changed-By: Marius Gripsgard Closes: 1058527 Changes: libqtdbustest (0.3.2-3) unstable; urgency=medium . [ Mike Gabriel ] * debian/control: Drop Debian UBports Team from Uploaders: field. Team is now maintainer. . [ Marius Gripsgard ] * debian/patches: Add patch to workaround cmake bug (Closes: #1058527) Checksums-Sha1: ebd1f4b2d66d8c830921cda37651dfeb5fc2dc40 1710 libqtdbustest_0.3.2-3.dsc 03bee1fbfd61bd59cdb77890d01750539e80f833 29260 libqtdbustest_0.3.2.orig.tar.gz 365de36309a574717c17b48f69550c2e432225dd 7748 libqtdbustest_0.3.2-3.debian.tar.xz 98669747f26f05f671eb46adc977a04c7e78c37a 13682 libqtdbustest_0.3.2-3_source.buildinfo Checksums-Sha256: 1d8fb729b326660296af17764ea4e8a535e2de7ee7594b6e49df6dbec034a638 1710 libqtdbustest_0.3.2-3.dsc 3ecaa14a3caa72b73a1106d145a07256d779b7902dee491d4083e708cb9b5f0a 29260 libqtdbustest_0.3.2.orig.tar.gz 97d3f4a5851746914f4dfcfeaeefcaf437b9a0694a2d51c05c4c818519f3514b 7748 libqtdbustest_0.3.2-3.debian.tar.xz
Bug#1061648: gnat-13-x86-64-linux-gnu: needs to inherit the Conflicts from gnat-13
Package: gnat-13-x86-64-linux-gnu Version: 13.2.0-12 Severity: serious User: debian...@lists.debian.org Usertags: piuparts Hi, during a test with piuparts I noticed your package failed to install because it tries to overwrite other packages files. >From the attached log (scroll to the bottom...): Selecting previously unselected package gnat-13-x86-64-linux-gnu. Preparing to unpack .../5-gnat-13-x86-64-linux-gnu_13.2.0-12_amd64.deb ... Unpacking gnat-13-x86-64-linux-gnu (13.2.0-12) ... dpkg: error processing archive /tmp/apt-dpkg-install-N8eYXp/5-gnat-13-x86-64-linux-gnu_13.2.0-12_amd64.deb (--unpack): trying to overwrite '/usr/bin/x86_64-linux-gnu-gnatgcc', which is also in package gnat-12 12.3.0-14 Errors were encountered while processing: /tmp/apt-dpkg-install-N8eYXp/5-gnat-13-x86-64-linux-gnu_13.2.0-12_amd64.deb There are currently Package: gnat-13 Version: 13.2.0-12 Depends: gnat-13-x86-64-linux-gnu (= 13.2.0-12), gcc-13-base (= 13.2.0-12), gcc-13 (>= 13) Suggests: gnat-13-doc, ada-reference-manual-2012, gnat-13-sjlj Conflicts: gnat-10, gnat-11, gnat-12, gnat-4.9, gnat-5, gnat-6, gnat-7, gnat-8, gnat-9 but these Conflicts are no longer effective (and can probably be removed) due to the introduction of gnat-13- This bug probably affects all gnat-13- packages for all architectures. cheers, Andreas
Bug#1061647: libgccjit-14-doc: missing Breaks+Replaces: libgccjit-13-doc (and maybe more old versions)
Package: libgccjit-14-doc Version: 14-20240127-1 Severity: serious User: debian...@lists.debian.org Usertags: piuparts Hi, during a test with piuparts I noticed your package fails to upgrade from 'testing'. It installed fine in 'testing', then the upgrade to 'sid' fails because it tries to overwrite other packages files without declaring a Breaks+Replaces relation. See policy 7.6 at https://www.debian.org/doc/debian-policy/ch-relationships.html#overwriting-files-and-replacing-packages-replaces >From the attached log (scroll to the bottom...): Preparing to unpack .../libgccjit-14-doc_14-20240127-1_all.deb ... Unpacking libgccjit-14-doc (14-20240127-1) ... dpkg: error processing archive /var/cache/apt/archives/libgccjit-14-doc_14-20240127-1_all.deb (--unpack): trying to overwrite '/usr/share/info/libgccjit-figures/factorial.png', which is also in package libgccjit-13-doc 13.2.0-10 Errors were encountered while processing: /var/cache/apt/archives/libgccjit-14-doc_14-20240127-1_all.deb The files in conflict are usr/share/info/libgccjit-figures/factorial.png usr/share/info/libgccjit-figures/factorial1.png usr/share/info/libgccjit-figures/sum-of-squares.png usr/share/info/libgccjit-figures/sum-of-squares1.png usr/share/info/libgccjit.info.gz cheers, Andreas libgccjit-13-doc=13.2.0-10_libgccjit-14-doc=14-20240127-1.log.gz Description: application/gzip
Bug#1061646: marked as done (falcosecurity-libs: build-depends on unavailable libluajit-5.1-dev)
Your message dated Sat, 27 Jan 2024 23:49:18 +
with message-id
and subject line Bug#1061646: fixed in falcosecurity-libs 0.14.1-3
has caused the Debian Bug report #1061646,
regarding falcosecurity-libs: build-depends on unavailable libluajit-5.1-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.)
--
1061646: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1061646
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: falcosecurity-libs
Version: 0.14.1-2
Severity: serious
Tags: patch ftbfs
Justification: fails to build from source (but built successfully in the past)
falcosecurity-libs now build-depends unconditionally on
libluajit-5.1-dev. This prevents the package to be buildable on some
architectures where it was available before: ppc64el for release
architectures, and riscv64 and ppc64 for non-release architectures.
The version 0.14.1-1 force libsinsp to be linked to a few additional
libraries, including -lluajit-5.1. This causes FTBFS on architectures
where it was not build-depended on. This has been wrongly fixed in
version 0.14.1-2 by changing the build-depends on libluajit-5.1-dev to
be unconditional.
The patch below fixes the issue by using the ${LUAJIT_LIB} cmake
variable instead of using -lluajit-5.1 and reverting the
build-dependency changes. At the same time, the list of architectures
which have libluajit-5.1-dev has been updated to reflect the current
status.
--- falcosecurity-libs-0.14.1/debian/control
+++ falcosecurity-libs-0.14.1/debian/control
@@ -21,7 +21,7 @@
protobuf-compiler,
protobuf-compiler-grpc,
libprotobuf-dev,
- libluajit-5.1-dev,
+ libluajit-5.1-dev [amd64 arm64 armel armhf i386 mips64el s390x]
| liblua5.1-0-dev,
libelf-dev,
libre2-dev,
libcap-dev,
---
falcosecurity-libs-0.14.1/debian/patches/libsinsp-added-missing-libraries.patch
+++
falcosecurity-libs-0.14.1/debian/patches/libsinsp-added-missing-libraries.patch
@@ -7,7 +7,7 @@
"${JSONCPP_LIB}"
"${RE2_LIB}"
+ -lprotobuf
-+ -lluajit-5.1
++ "${LUAJIT_LIB}"
+ -lgrpc++
)
--- End Message ---
--- Begin Message ---
Source: falcosecurity-libs
Source-Version: 0.14.1-3
Done: Dima Kogan
We believe that the bug you reported is fixed in the latest version of
falcosecurity-libs, which is due to be installed in the Debian FTP archive.
A summary of the changes between this version and the previous one is
attached.
Thank you for reporting the bug, which will now be closed. If you
have further comments please address them to 1061...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Dima Kogan (supplier of updated falcosecurity-libs package)
(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Format: 1.8
Date: Sat, 27 Jan 2024 15:24:44 -0800
Source: falcosecurity-libs
Architecture: source
Version: 0.14.1-3
Distribution: unstable
Urgency: medium
Maintainer: Dima Kogan
Changed-By: Dima Kogan
Closes: 1061646
Changes:
falcosecurity-libs (0.14.1-3) unstable; urgency=medium
.
* More precise Build-Depends: libluajit-5.1-dev
Thanks to Aurelien Jarno for the report and
patch. (Closes: #1061646)
Checksums-Sha1:
ce62f687df132b314749cd20cdddf84125e916cf 2572 falcosecurity-libs_0.14.1-3.dsc
2cb5246fa5f8398baba9a4bae09e2ba17bf084bc 9416
falcosecurity-libs_0.14.1-3.debian.tar.xz
c5326cc10c99316eb369eb061aa61a77be66357d 14045
falcosecurity-libs_0.14.1-3_source.buildinfo
Checksums-Sha256:
9f1881cba35a8b534a68a5281dcf0c7b2fc3ae478bf08cc851c1884cc5d55f99 2572
falcosecurity-libs_0.14.1-3.dsc
e440195fa2900c8a31c36b3c1e20165f0ea90a2d6aa656b3bd4888d56f7f3efb 9416
falcosecurity-libs_0.14.1-3.debian.tar.xz
79c822af8cd203becb802166bd6c0bdec686171db936c22e57752c81269be80c 14045
falcosecurity-libs_0.14.1-3_source.buildinfo
Files:
d9b2150799736770d83afe88de0741d5 2572 libdevel optional
falcosecurity-libs_0.14.1-3.dsc
165e8b3fe8f96641d1d695b7e85bbd78 9416 libdevel optional
falcosecurity-libs_0.14.1-3.debian.tar.xz
2261e47fe03b869fe151b114ffcf899d 14045 libdevel optional
falcosecurity-libs_0.14.1-3_source.buildinfo
-BEGIN PGP SIGNATURE-
iQJGBAEBCgAwFiEEteL6GQ/fmv4hiInPrMfCz
Bug#1061646: falcosecurity-libs: build-depends on unavailable libluajit-5.1-dev
Thanks for the note. 0.14.1-2 makes the build work on arm64, and I wanted to get that done, before thinking of other arches. I' about to apply your suggested patches.
Bug#1053787: marked as done (qbrz calls give internal error)
Your message dated Sat, 27 Jan 2024 23:05:35 + with message-id and subject line Bug#1053787: fixed in qbrz 0.23.2+bzr1663-1 has caused the Debian Bug report #1053787, regarding qbrz calls give internal error to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 1053787: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1053787 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Subject: qbrz calls give internal error Package: qbrz Version: 0.23.2+bzr1641-1 Severity: grave Justification: renders package unusable Dear Maintainer, The package qbzr seems to be broken on Debian 12. For example using "brz qlog" I get the following error: <<< brz: ERROR: TypeError: arguments did not match any overloaded call: singleShot(msec: int, slot: PYQT_SLOT): argument 1 has unexpected type 'float' singleShot(msec: int, timerType: Qt.TimerType, slot: PYQT_SLOT): argument 1 has unexpected type 'float' Traceback (most recent call last): File "/usr/lib/python3/dist-packages/breezy/plugins/qbrz/lib/util.py", line 971, in run_in_loading_queue f(*args, **kargs) File "/usr/lib/python3/dist-packages/breezy/plugins/qbrz/lib/revtreeview.py", line 135, in _load_visible_revisions load_revisions(revids, model.get_repo(), File "/usr/lib/python3/dist-packages/breezy/lazy_import.py", line 153, in __call__ return obj(*args, **kwargs) File "/usr/lib/python3/dist-packages/breezy/plugins/qbrz/lib/lazycachedrevloader.py", line 93, in load_revisions stop = before_batch_load(repo, batch_revids) ^ File "/usr/lib/python3/dist-packages/breezy/plugins/qbrz/lib/revtreeview.py", line 130, in before_batch_load self.delay(0.5) File "/usr/lib/python3/dist-packages/breezy/plugins/qbrz/lib/revtreeview.py", line 151, in delay QtCore.QTimer.singleShot(timeout, null) TypeError: arguments did not match any overloaded call: singleShot(msec: int, slot: PYQT_SLOT): argument 1 has unexpected type 'float' singleShot(msec: int, timerType: Qt.TimerType, slot: PYQT_SLOT): argument 1 has unexpected type 'float' brz 3.3.2 on python 3.11.2 (Linux-6.1.0-11-amd64-x86_64-with-glibc2.36) arguments: ['bzr', 'qlog'] plugins: bash_completion[3.3.2], changelog_merge[3.3.2], commitfromnews[3.3.2], cvs[3.3.2], darcs[3.3.2], email[3.3.2], fastimport[3.3.2], flake8[unknown], fossil[3.3.2], github[3.3.2], gitlab[3.3.2], hg[3.3.2], launchpad[3.3.2], mtn[3.3.2], netrc_credential_store[3.3.2], news_merge[3.3.2], po_merge[3.3.2], propose[3.3.2], pypi[3.3.2], qbrz[0.4.1.dev], quilt[unknown], repodebug[3.3.2], rewrite[unknown], stats[3.3.2], svn[3.3.2], upload[3.3.2], weave_fmt[3.3.2], webdav[3.3.2], zsh_completion[3.3.2] encoding: 'utf-8', fsenc: 'utf-8', lang: 'it_IT.UTF-8' *** Breezy has encountered an internal error. This probably indicates a bug in Breezy. You can help us fix it by filing a bug report at https://bugs.launchpad.net/brz/+filebug including this traceback and a description of the problem. QPainter::end: Painter ended with 7 saved states >>> -- System Information: Debian Release: 12.1 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'stable-security'), (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 6.1.0-11-amd64 (SMP w/4 CPU threads; PREEMPT) Locale: LANG=it_IT.UTF-8, LC_CTYPE=it_IT.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 Versions of packages qbrz depends on: ii python3 3.11.2-1+b1 ii python3-all 3.11.2-1+b1 ii python3-breezy 3.3.2-3 ii python3-patiencediff 0.2.13-1 ii python3-pyqt5 5.15.9+dfsg-1 qbrz recommends no packages. qbrz suggests no packages. -- no debconf information --- End Message --- --- Begin Message --- Source: qbrz Source-Version: 0.23.2+bzr1663-1 Done: Jelmer Vernooij We believe that the bug you reported is fixed in the latest version of qbrz, 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. Jelmer Vernooij (supplier of updated qbrz package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact t
Bug#1061646: falcosecurity-libs: build-depends on unavailable libluajit-5.1-dev
Source: falcosecurity-libs
Version: 0.14.1-2
Severity: serious
Tags: patch ftbfs
Justification: fails to build from source (but built successfully in the past)
falcosecurity-libs now build-depends unconditionally on
libluajit-5.1-dev. This prevents the package to be buildable on some
architectures where it was available before: ppc64el for release
architectures, and riscv64 and ppc64 for non-release architectures.
The version 0.14.1-1 force libsinsp to be linked to a few additional
libraries, including -lluajit-5.1. This causes FTBFS on architectures
where it was not build-depended on. This has been wrongly fixed in
version 0.14.1-2 by changing the build-depends on libluajit-5.1-dev to
be unconditional.
The patch below fixes the issue by using the ${LUAJIT_LIB} cmake
variable instead of using -lluajit-5.1 and reverting the
build-dependency changes. At the same time, the list of architectures
which have libluajit-5.1-dev has been updated to reflect the current
status.
--- falcosecurity-libs-0.14.1/debian/control
+++ falcosecurity-libs-0.14.1/debian/control
@@ -21,7 +21,7 @@
protobuf-compiler,
protobuf-compiler-grpc,
libprotobuf-dev,
- libluajit-5.1-dev,
+ libluajit-5.1-dev [amd64 arm64 armel armhf i386 mips64el s390x]
| liblua5.1-0-dev,
libelf-dev,
libre2-dev,
libcap-dev,
---
falcosecurity-libs-0.14.1/debian/patches/libsinsp-added-missing-libraries.patch
+++
falcosecurity-libs-0.14.1/debian/patches/libsinsp-added-missing-libraries.patch
@@ -7,7 +7,7 @@
"${JSONCPP_LIB}"
"${RE2_LIB}"
+ -lprotobuf
-+ -lluajit-5.1
++ "${LUAJIT_LIB}"
+ -lgrpc++
)
Processed: Re: python-miio: FTBFS: dh_auto_test: error: pybuild --test --test-pytest -i python{version} -p 3.11 returned exit code 13
Processing control commands:
> tags -1 help
Bug #1042325 [src:python-miio] python-miio: FTBFS: dh_auto_test: error: pybuild
--test --test-pytest -i python{version} -p 3.11 returned exit code 13
Added tag(s) help.
--
1042325: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1042325
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Bug#1042325: python-miio: FTBFS: dh_auto_test: error: pybuild --test --test-pytest -i python{version} -p 3.11 returned exit code 13
Control: tags -1 help Hi, I upgraded python-miio in Git. Unfortunately there are some test suite errors[1] Any help would be welcome Andreas. [1] https://salsa.debian.org/python-team/packages/miio/-/jobs/5212674 -- http://fam-tille.de
Bug#1061311: marked as done (neuron ftbfs with Python 3.12 as the default)
Your message dated Sat, 27 Jan 2024 20:58:07 + with message-id and subject line Bug#1061311: fixed in neuron 8.2.2-6 has caused the Debian Bug report #1061311, regarding neuron ftbfs with Python 3.12 as the default to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 1061311: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1061311 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: src:neuron Version: 8.2.2-5 Severity: serious Tags: sid trixie ftbfs User: debian-pyt...@lists.debian.org Usertags: python3.12 with python3-defaults from experimental: [...] + /usr/bin/python3 setup.py build_ext --build-lib=/<>/obj-x86_64-linux-gnu/lib/python Traceback (most recent call last): File "/<>/obj-x86_64-linux-gnu/share/lib/python/neuron/rxd/geometry3d/setup.py", line 19, in from distutils.core import setup ModuleNotFoundError: No module named 'distutils' make[3]: *** [share/lib/python/neuron/rxd/geometry3d/CMakeFiles/rx3dextensions_0.dir/build.make:73: share/lib/python/neuron/rxd/geometry3d/CMakeFiles/rx3dextensions_0] Error 1 make[3]: Leaving directory '/<>/obj-x86_64-linux-gnu' --- End Message --- --- Begin Message --- Source: neuron Source-Version: 8.2.2-6 Done: Nilesh Patra We believe that the bug you reported is fixed in the latest version of neuron, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 1061...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Nilesh Patra (supplier of updated neuron 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: Sat, 27 Jan 2024 19:49:16 + Source: neuron Architecture: source Version: 8.2.2-6 Distribution: unstable Urgency: medium Maintainer: Debian Science Team Changed-By: Nilesh Patra Closes: 1048047 1061311 Changes: neuron (8.2.2-6) unstable; urgency=medium . * Team Upload. * Add patch to reove distutils usage (Closes: #1061311) * python3-neuron.install: fixup to get correct py lib installed * Cleanup files to fixup build-after-build (Closes: #1048047) Checksums-Sha1: a1ed17e8440a58ecd9ea70263ffcb944e9e05a2e 1737 neuron_8.2.2-6.dsc 6f73037a98c12b1269b8ff6ba9415b70e799e60b 29396 neuron_8.2.2-6.debian.tar.xz db2000876870e7bae88142ae518fea17bbd7 11841 neuron_8.2.2-6_amd64.buildinfo Checksums-Sha256: 7816c679b28adc6a906f1cdb87ed2037e24020fcef660e908b6c63e42267fdde 1737 neuron_8.2.2-6.dsc ed44d9244f0df47662bb0ab9f0ef714f633f8dbed057c1db7e7e6e5d6f35aa51 29396 neuron_8.2.2-6.debian.tar.xz 21a78790d616a7435a6c822c529a537a5e35ce40105d728b9d75f7401404de1f 11841 neuron_8.2.2-6_amd64.buildinfo Files: 3fed8c447b3f644987ff9daac861184b 1737 science optional neuron_8.2.2-6.dsc 48bb7e175e4a2dc288afd1367744c44e 29396 science optional neuron_8.2.2-6.debian.tar.xz 1fd4b52782edca726a4b0cb1857adf0f 11841 science optional neuron_8.2.2-6_amd64.buildinfo -BEGIN PGP SIGNATURE- iHUEARYIAB0WIQSglbZu4JAkvuai8HIqJ5BL1yQ+2gUCZbVgNwAKCRAqJ5BL1yQ+ 2hJpAQDgeZcfkQyKeJLazsMInvW3f47IIh/FaIL71mVnxSSnkQD/V1SgZjinCyxZ 7gAMfQhEl+xLfBqwmOYODZl4w15jdQA= =8KdQ -END PGP SIGNATURE End Message ---
Bug#1061605: scipy: tests skipped during build and autopkgtest not in sync
Source: scipy Followup-For: Bug #1061605 Easy enough to relax tolerances or skip tests if we needed to. test_maxiter_worsening was giving problems on other arches. But strange the test only started failing when pythran was deactivated. I've reactivated it in 1.10.1-8, we'll see if it restores success.
Bug#1024830: ERROR: Unable to connect to servers to test latency.
Hi, speedtest-cli 2.1.3-2 works for me on Bookworm. Best regards, Peter
Bug#1042620: New upstream version of flufl.i18n fails its test
Hi, I checked some random DPT packages and had a look into flufl.i18n. Unfortunately the new upstream version fails its test as you can see in Salsa CI[1]. Any help is welcome Andreas. [1] https://salsa.debian.org/python-team/packages/flufl.i18n/-/jobs/5148646 -- http://fam-tille.de
Bug#1061633: libtemplates-parser: autopkgtest needs update for new version of gcc-12
Source: libtemplates-parser
Version: 23.0.0-3
Severity: serious
X-Debbugs-CC: gcc...@packages.debian.org
Tags: sid trixie
User: debian...@lists.debian.org
Usertags: needs-update
Control: affects -1 src:gcc-12
Dear maintainer(s),
With a recent upload of gcc-12 the autopkgtest of libtemplates-parser
fails in testing when that autopkgtest is run with the binary packages
of gcc-12 from unstable. It passes when run with only packages from
testing. In tabular form:
passfail
gcc-12 from testing12.3.0-14
libtemplates-parserfrom testing23.0.0-3
all others from testingfrom testing
I copied some of the output at the bottom of this report.
Currently this regression is blocking the migration of gcc-12 to testing
[1]. Of course, gcc-12 shouldn't just break your autopkgtest (or even
worse, your package), so please investigate.
If this is a real problem in your package (and not only in your
autopkgtest), the right binary package(s) from gcc-12 should really add
a versioned Breaks on the unfixed version of (one of your) package(s).
Note: the Breaks is nice even if the issue is only in the autopkgtest as
it helps the migration software to figure out the right versions to
combine in the tests.
More information about this bug and the reason for filing it can be found on
https://wiki.debian.org/ContinuousIntegration/RegressionEmailInformation
Paul
[1] https://qa.debian.org/excuses.php?package=gcc-12
https://ci.debian.net/data/autopkgtest/testing/amd64/libt/libtemplates-parser/42388674/log.gz
30s Changing to object directory of "P":
"/tmp/autopkgtest-lxc.xtf31hge/downtmp/autopkgtest_tmp/"
30s /usr/bin/gcc-12 -c -x ada -gnatA -gnatec=/tmp/GNAT-TEMP-03.TMP
-gnatem=/tmp/GNAT-TEMP-04.TMP
/tmp/autopkgtest-lxc.xtf31hge/downtmp/build.69k/src/docs/src/demo.adb
30s /usr/libexec/gprbuild/gprbind demo.bexch
30s /usr/bin/gnatbind -shared -o b__demo.adb
/tmp/autopkgtest-lxc.xtf31hge/downtmp/autopkgtest_tmp/demo.ali -x
-F=/tmp/GNAT-TEMP-05.TMP -O=/tmp/GNAT-TEMP-07.TMP
30s error: "templates_parser_tasking__standard_tasking.adb" must be
compiled
30s error:
("/usr/lib/x86_64-linux-gnu/ada/adalib/templates_parser/templates_parser_tasking__standard_tasking.ali"
is obsolete and read-only)
30s gprbind: invocation of gnatbind failed
30s gprbuild: unable to bind demo.adb
30s autopkgtest [11:05:41]: test link-with-shared
OpenPGP_signature.asc
Description: OpenPGP digital signature
Processed: libtemplates-parser: autopkgtest needs update for new version of gcc-12
Processing control commands: > affects -1 src:gcc-12 Bug #1061633 [src:libtemplates-parser] libtemplates-parser: autopkgtest needs update for new version of gcc-12 Added indication that 1061633 affects src:gcc-12 -- 1061633: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1061633 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: libgnatcoll: autopkgtest needs update for new version of gcc-12
Processing control commands: > affects -1 src:gcc-12 Bug #1061631 [src:libgnatcoll] libgnatcoll: autopkgtest needs update for new version of gcc-12 Added indication that 1061631 affects src:gcc-12 -- 1061631: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1061631 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1061631: libgnatcoll: autopkgtest needs update for new version of gcc-12
Source: libgnatcoll
Version: 23.0.0-3
Severity: serious
X-Debbugs-CC: gcc...@packages.debian.org
Tags: sid trixie
User: debian...@lists.debian.org
Usertags: needs-update
Control: affects -1 src:gcc-12
Dear maintainer(s),
With a recent upload of gcc-12 the autopkgtest of libgnatcoll fails in
testing when that autopkgtest is run with the binary packages of gcc-12
from unstable. It passes when run with only packages from testing. In
tabular form:
passfail
gcc-12 from testing12.3.0-14
libgnatcollfrom testing23.0.0-3
all others from testingfrom testing
I copied some of the output at the bottom of this report.
Currently this regression is blocking the migration of gcc-12 to testing
[1]. Of course, gcc-12 shouldn't just break your autopkgtest (or even
worse, your package), so please investigate.
If this is a real problem in your package (and not only in your
autopkgtest), the right binary package(s) from gcc-12 should really add
a versioned Breaks on the unfixed version of (one of your) package(s).
Note: the Breaks is nice even if the issue is only in the autopkgtest as
it helps the migration software to figure out the right versions to
combine in the tests.
More information about this bug and the reason for filing it can be found on
https://wiki.debian.org/ContinuousIntegration/RegressionEmailInformation
Paul
[1] https://qa.debian.org/excuses.php?package=gcc-12
https://ci.debian.net/data/autopkgtest/testing/amd64/libg/libgnatcoll/42388673/log.gz
30s Changing to object directory of "proj":
"/tmp/autopkgtest-lxc.mdq8ugbr/downtmp/autopkgtest_tmp/"
30s /usr/bin/gcc-12 -c -x ada -gnatA -gnata
-gnatec=/tmp/GNAT-TEMP-03.TMP -gnatem=/tmp/GNAT-TEMP-04.TMP
/tmp/autopkgtest-lxc.mdq8ugbr/downtmp/autopkgtest_tmp/exec.adb
31s /usr/libexec/gprbuild/gprbind exec.bexch
31s /usr/bin/gnatbind -shared -o b__exec.adb
/tmp/autopkgtest-lxc.mdq8ugbr/downtmp/autopkgtest_tmp/exec.ali -x
-F=/tmp/GNAT-TEMP-05.TMP -O=/tmp/GNAT-TEMP-07.TMP
31s error: "gnatcoll-projects.adb" must be compiled
31s error:
("/usr/lib/x86_64-linux-gnu/ada/adalib/gnatcoll/gnatcoll-projects.ali"
is obsolete and read-only)
31s error: "gnatcoll-projects-krunch.adb" must be compiled
31s error:
("/usr/lib/x86_64-linux-gnu/ada/adalib/gnatcoll/gnatcoll-projects-krunch.ali"
is obsolete and read-only)
31s error: "gnatcoll-projects-normalize.adb" must be compiled
31s error:
("/usr/lib/x86_64-linux-gnu/ada/adalib/gnatcoll/gnatcoll-projects-normalize.ali"
is obsolete and read-only)
31s error: "gpr-tree.adb" must be compiled
31s error:
("/usr/lib/x86_64-linux-gnu/ada/adalib/gnatprj/gpr-tree.ali" is obsolete
and read-only)
31s error: "gpr-env.adb" must be compiled
31s error: ("/usr/lib/x86_64-linux-gnu/ada/adalib/gnatprj/gpr-env.ali"
is obsolete and read-only)
31s error: "gpr-util.adb" must be compiled
31s error:
("/usr/lib/x86_64-linux-gnu/ada/adalib/gnatprj/gpr-util.ali" is obsolete
and read-only)
31s error: "gpr-ali.adb" must be compiled
31s error: ("/usr/lib/x86_64-linux-gnu/ada/adalib/gnatprj/gpr-ali.ali"
is obsolete and read-only)
31s error: "gpr-conf.adb" must be compiled
31s error:
("/usr/lib/x86_64-linux-gnu/ada/adalib/gnatprj/gpr-conf.ali" is obsolete
and read-only)
31s error: "gpr-nmsc.adb" must be compiled
31s error:
("/usr/lib/x86_64-linux-gnu/ada/adalib/gnatprj/gpr-nmsc.ali" is obsolete
and read-only)
31s error: "gpr-part.adb" must be compiled
31s error:
("/usr/lib/x86_64-linux-gnu/ada/adalib/gnatprj/gpr-part.ali" is obsolete
and read-only)
31s error: "gpr-dect.adb" must be compiled
31s error:
("/usr/lib/x86_64-linux-gnu/ada/adalib/gnatprj/gpr-dect.ali" is obsolete
and read-only)
31s error: "gpr-strt.adb" must be compiled
31s error:
("/usr/lib/x86_64-linux-gnu/ada/adalib/gnatprj/gpr-strt.ali" is obsolete
and read-only)
31s error: "gpr-proc.adb" must be compiled
31s error:
("/usr/lib/x86_64-linux-gnu/ada/adalib/gnatprj/gpr-proc.ali" is obsolete
and read-only)
31s error: "gpr-knowledge.adb" must be compiled
31s error:
("/usr/lib/x86_64-linux-gnu/ada/adalib/gnatprj/gpr-knowledge.ali" is
obsolete and read-only)
31s error: "gpr-sdefault.adb" must be compiled
31s error:
("/usr/lib/x86_64-linux-gnu/ada/adalib/gnatprj/gpr-sdefault.ali" is
obsolete and read-only)
31s error: "gpr_build_util.adb" must be compiled
31s error:
("/usr/lib/x86_64-linux-gnu/ada/adalib/gnatprj/gpr_build_util.ali" is
obsolete and read-only)
31s error: "gpr-pp.adb" must be compiled
31s error: ("/usr/lib/x86_64-linux-gnu/ada/adalib/gnatprj/gpr-pp.ali"
is obsolete and read-only)
31s gprbind: invocation of gnatbind failed
31s gprbuild: unable to bind exec.adb
31s autopkgtest [11:05:42]: test projects
OpenPGP_signature.asc
Description: OpenPGP digital signature
Bug#1040626: marked as done (gcc-13-cross-mipsen ftbfs in unstable)
Your message dated Sat, 27 Jan 2024 17:51:13 +0100 with message-id and subject line Re: gcc-13-cross-mipsen ftbfs in unstable has caused the Debian Bug report #1040626, regarding gcc-13-cross-mipsen ftbfs in unstable 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.) -- 1040626: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1040626 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: src:gcc-13-cross-mipsen Version: 1+c1 Severity: serious Tags: sid trixie [...] checking linker soname option... yes checking linker --demangle support... no checking linker plugin support... 0 checking assembler for explicit relocation support... no checking assembler for -mno-shared support... no checking assembler for .gnu_attribute support... no checking assembler for .module support... no configure: error: Requesting --with-fp-32= requires assembler support for .module. make[4]: *** [Makefile:4569: configure-gcc] Error 1 make[4]: Leaving directory '/<>/gcc/build' make[3]: *** [Makefile:1042: all] Error 2 make[3]: Leaving directory '/<>/gcc/build' --- End Message --- --- Begin Message --- Version: 2+c1 On Sat, 8 Jul 2023 08:43:46 +0200 Matthias Klose wrote: checking linker soname option... yes checking linker --demangle support... no checking linker plugin support... 0 checking assembler for explicit relocation support... no checking assembler for -mno-shared support... no checking assembler for .gnu_attribute support... no checking assembler for .module support... no configure: error: Requesting --with-fp-32= requires assembler support for .module. make[4]: *** [Makefile:4569: configure-gcc] Error 1 make[4]: Leaving directory '/<>/gcc/build' make[3]: *** [Makefile:1042: all] Error 2 make[3]: Leaving directory '/<>/gcc/build' Seems like that's resolved in the last upload. Paul OpenPGP_signature.asc Description: OpenPGP digital signature --- End Message ---
Bug#1054683: marked as done (nmodl: FTBFS: fast_math.cpp:12:10: fatal error: catch2/catch.hpp: No such file or directory)
Your message dated Sat, 27 Jan 2024 16:33:45 + with message-id and subject line Bug#1054683: fixed in nmodl 0.6-1 has caused the Debian Bug report #1054683, regarding nmodl: FTBFS: fast_math.cpp:12:10: fatal error: catch2/catch.hpp: No such file or directory to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 1054683: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1054683 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: nmodl Version: 0.5-1 Severity: serious Justification: FTBFS Tags: trixie sid ftbfs User: lu...@debian.org Usertags: ftbfs-20231027 ftbfs-trixie Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > cd /<>/obj-x86_64-linux-gnu/test/unit && /usr/bin/c++ > -I/<> -I/<>/src > -I/<>/obj-x86_64-linux-gnu/src -I/usr/include/python3.11 > -I/<>/test -I/<>/src/solver > -I/<>/src/utils -I/<>/ext/eigen -isystem > /usr/include/eigen3 -g -O2 -ffile-prefix-map=/<>=. > -fstack-protector-strong -fstack-clash-protection -Wformat > -Werror=format-security -fcf-protection -Wdate-time -D_FORTIFY_SOURCE=2 > -std=c++17 -fvisibility=hidden -MD -MT > test/unit/CMakeFiles/testcrout.dir/crout/crout.cpp.o -MF > CMakeFiles/testcrout.dir/crout/crout.cpp.o.d -o > CMakeFiles/testcrout.dir/crout/crout.cpp.o -c > /<>/test/unit/crout/crout.cpp > /<>/test/unit/fast_math/fast_math.cpp:12:10: fatal error: > catch2/catch.hpp: No such file or directory >12 | #include > | ^~ > compilation terminated. > make[3]: *** [test/unit/CMakeFiles/testfast_math.dir/build.make:79: > test/unit/CMakeFiles/testfast_math.dir/fast_math/fast_math.cpp.o] Error 1 The full build log is available from: http://qa-logs.debian.net/2023/10/27/nmodl_0.5-1_unstable.log All bugs filed during this archive rebuild are listed at: https://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=ftbfs-20231027;users=lu...@debian.org or: https://udd.debian.org/bugs/?release=na&merged=ign&fnewerval=7&flastmodval=7&fusertag=only&fusertagtag=ftbfs-20231027&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: nmodl Source-Version: 0.6-1 Done: Nilesh Patra We believe that the bug you reported is fixed in the latest version of nmodl, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 1054...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Nilesh Patra (supplier of updated nmodl 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: Sat, 27 Jan 2024 20:54:26 +0530 Source: nmodl Architecture: source Version: 0.6-1 Distribution: unstable Urgency: medium Maintainer: Debian Science Team Changed-By: Nilesh Patra Closes: 1034327 1047577 1054683 Changes: nmodl (0.6-1) unstable; urgency=medium . * Team Upload. * New upstream version 0.6 * Backport upstream patch and add few more changes to fixup catchv2_3 compatibility (Closes: #1054683) * Enable Build-Time tests * Add d/salsa-ci.yml * Add patch to fix FTBFS with 32 bit archs * Do not run tests in parallel to help prevent race condition based failures * Add patch to make build reproducible + Thanks to Vagrant Cascadian for the patch (Closes: #1034327) * Add d/clean to clean off __pycache__ (Closes: #1047577) Checksums-Sha1: 108dc682716151d655841dc83cde14c9bddb146c 1687 nmodl_0.6-1.dsc 652d917570f9ec64ba4ed7df83f4fb4ebdc06d56 2148544 nmodl_0.6.orig.tar.gz 809b88a4e414fd1644687724e0f52753ffe0cc73 76560 nmodl_0.6-1.debian.tar.xz 36acfe87d27601d9d10ce6d7d7583e4871dbbda4 9697 nmodl_0.6-1_source.buildinfo Checksums-Sha256: 1c77b0601d9dd5ca84cf615ba6faeba1eb
Bug#1061627: jpeg-xl: 0.8 failing autopkgtest
Source: jpeg-xl Version: 0.8.2-1 Severity: serious jpeg-xl in Experimental has a failing autopkgtest. This will need to be fixed before it is possible for jpeg-xl 0.8.2 to reach Testing. Log excerpt --- Test - Lossless Roundtrip JPEG XL encoder v0.8.2 [AVX2,SSE4,SSSE3,SSE2] ./lib/extras/dec/color_hints.cc:54: No color_space/icc_pathname given, assuming sRGB Read 320x320 image, 1228816 bytes, 814.0 MP/s Encoding [Modular, lossless, effort: 7], ./lib/jxl/encode.cc:263: Only JXL_BIT_DEPTH_FROM_PIXEL_FORMAT is implemented for float types. ./lib/jxl/encode.cc:1848: Invalid input bit depth JxlEncoderAddImageFrame() failed. EncodeImageJXL() failed. Full logs --- https://release.debian.org/britney/pseudo-excuses-experimental.html#jpeg-xl https://ci.debian.net/packages/j/jpeg-xl/unstable/amd64/ Thank you, Jeremy Bícha
Bug#1061392: marked as done (swig 4.2.0 needed for Python 3.12 compatibility)
Your message dated Sat, 27 Jan 2024 14:54:24 + with message-id and subject line Bug#1061392: fixed in swig 4.2.0-1 has caused the Debian Bug report #1061392, regarding swig 4.2.0 needed for Python 3.12 compatibility 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.) -- 1061392: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1061392 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: src:swig Version: 4.1.0-0.3 Severity: important Tags: sid trixie User: debian-pyt...@lists.debian.org Usertags: python3.12 please update to swig 4.2.0 needed for Python 3.12 compatibility, at least that's what the upstream changelog suggests at https://www.swig.org/ --- End Message --- --- Begin Message --- Source: swig Source-Version: 4.2.0-1 Done: Torsten Landschoff We believe that the bug you reported is fixed in the latest version of swig, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 1061...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Torsten Landschoff (supplier of updated swig package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Fri, 26 Jan 2024 18:15:05 +0100 Source: swig Architecture: source Version: 4.2.0-1 Distribution: unstable Urgency: medium Maintainer: Torsten Landschoff Changed-By: Torsten Landschoff Closes: 1060801 1061392 Changes: swig (4.2.0-1) unstable; urgency=medium . [ Rafael Laboissière ] * New upstream release 4.2.0: Update patches. + Drop d/p/octave-8.1.patch (applied upstream). + Drop d/p/substitute-libv8-dev-with-libnode-dev.patch (applied upstream). . [ Torsten Landschoff ] * Drop versioned packages swig4.0*, add conflicts and replaces. * Release to unstable (closes: #1061392, #1060801). Checksums-Sha1: 16f097b28e557e533bf5b4e9e03f002b26f72daf 2042 swig_4.2.0-1.dsc 00079558670252b1357000feb157193b982209d9 8339586 swig_4.2.0.orig.tar.gz 318b17004b2378220753aedf36bac06ac113c94c 20752 swig_4.2.0-1.debian.tar.xz be80425088e33070c9ff748d60482b2bb56ecda4 6795 swig_4.2.0-1_amd64.buildinfo Checksums-Sha256: b01c4e1ca6540b8c2e0105f7c6ef46627c6c8aa7d3aa3979040bf42e5ced9731 2042 swig_4.2.0-1.dsc 261ca2d7589e260762817b912c075831572b72ff2717942f75b3e51244829c97 8339586 swig_4.2.0.orig.tar.gz f34ccf81787e9f5ea8f6c09aefe21a17619417957a1e809a1fd0d4968103bc39 20752 swig_4.2.0-1.debian.tar.xz 34cac46b82eb882b448b2a6550dce7344df203cdccc03ed66145d0d87848b7f7 6795 swig_4.2.0-1_amd64.buildinfo Files: 30045d0259f4a5cc400e93ed3629a04e 2042 interpreters optional swig_4.2.0-1.dsc 4d03374a2c30367699fa0928e1d901e8 8339586 interpreters optional swig_4.2.0.orig.tar.gz 51d93b8a7c85d7390edb0f08718bc5b5 20752 interpreters optional swig_4.2.0-1.debian.tar.xz ebdcafed209543b18e8fed10176feda9 6795 interpreters optional swig_4.2.0-1_amd64.buildinfo -BEGIN PGP SIGNATURE- iQJHBAEBCgAxFiEEe9EGRjlLC8TE41VWHl+Vp4Y7fHcFAmW0wncTHHRvcnN0ZW5A ZGViaWFuLm9yZwAKCRAeX5Wnhjt8d37fD/4qH2eHZe+p9zPaf2OiQNMauSXDNj2x Czflek/86GBGamymII0RCzdEjhwCpMHbcZTkQdnpcrbn2IAgfw+32raiYFt2y8La 3VfaPy3VXd8XkiRqeCqOCFSnBbsU1TDcXcBROe2WK8uuUwkMtcjINI/ykuFqgiEq GoXDpCx0zaTynAcPNZ5s4ONHnJY3jLCdPPfDPcpFq6Y7YUBVa5nbnD9/4YjyAWVp dDTMcHPdYRtZTn5+Qp6L5BWej2F9+k2CdzO0Dpv21pvFZOD2Tfstd99qse9leNqN KvOumUg2yvItia5Pc5sTh0Z16F8+X+7GGqXxhMijoew7IOpD6bF5Ty4RCenptRgS 9JGZd2QiD2DweQQX2sUcxktLqGC44d+dIWS/p6qPJfutpfUrwBjhDqcJkeAmlUgN v8sCfMny/Q0BA98DbZcpnUB6fOoMApqKDpNOG+yWdMqlkAyzYLqu5jzbh7qBW1IJ tR+D69JjQQC+jNjI6K8ywPBuRV5tn2TgE355GYEmWdzIcYiSGOBhGIqTuVLdw6YL YG6rVvD1oi6nX9MrYOC6fQB0yuNA0hf74obd9X3hD1OHavRkoaE3mhtMzhGhzIek Z9tu2QDeJoQchyWSQwWpfQxml27ZQ1n5Kzewl3GqvHcCAukuwjsTwYWQZz1NF1Pd EnMFOXwcqiuYFg== =sU6k -END PGP SIGNATURE End Message ---
Bug#1061621: filament: FTBFS: too few arguments to function call, expected 3, have 2
Source: filament Version: 1.9.25+dfsg2-12 Severity: serious Tags: ftbfs Justification: fails to build from source (but built successfully in the past) X-Debbugs-Cc: sramac...@debian.org https://buildd.debian.org/status/fetch.php?pkg=filament&arch=amd64&ver=1.9.25%2Bdfsg2-12%2Bb2&stamp=1706352699&raw=0 make[3]: Entering directory '/<>/obj-x86_64-linux-gnu' [ 93%] Building CXX object filament/benchmark/CMakeFiles/benchmark_filament.dir/benchmark_filament.cpp.o cd /<>/obj-x86_64-linux-gnu/filament/benchmark && /usr/bin/clang++ -DFILAMENT_DFG_LUT_SIZE=128 -DFILAMENT_DRIVER_SUPPORTS_VULKAN -DFILAMENT_ENABLE_MATDBG=0 -DFILAMENT_MIN_COMMAND_BUFFERS_SIZE_IN_MB=1 -DFILAMENT_OPENGL_HANDLE_ARENA_SIZE_IN_MB=2 -DFILAMENT_PER_FRAME_COMMANDS_SIZE_IN_MB=1 -DFILAMENT_PER_RENDER_PASS_ARENA_SIZE_IN_MB=2 -DFILAMENT_SUPPORTS_XCB -DFILAMENT_SUPPORTS_XLIB -DSYSTRACE_TAG=2 -I/<>/filament/benchmark/../src -I/<>/libs/utils/include -I/<>/libs/math/include -I/<>/filament/include -I/<>/filament/backend/include -I/<>/libs/filabridge/include -g -O2 -ffile-prefix-map=/<>=. -fstack-protector-strong -fstack-clash-protection -Wformat -Werror=format-security -fcf-protection -Wdate-time -D_FORTIFY_SOURCE=2 -DNDEBUG -std=c++17 -fstrict-aliasing -Wno-unknown-pragmas -Wno-unused-function -fPIC -MD -MT filament/benchmark/CMakeFiles/benchmark_filament.dir/benchmark_filament.cpp.o -MF CMakeFiles/benchmark_filament.dir/benchmark_filament.cpp.o.d -o CMakeFiles/benchmark_filament.dir/benchmark_filament.cpp.o -c /<>/filament/benchmark/benchmark_filament.cpp /<>/libs/filagui/src/ImGuiExtensions.cpp:122:58: error: too few arguments to function call, expected 3, have 2 const bool hovered = ImGui::ItemHoverable(inner_bb, 0); ^ /usr/include/imgui/imgui_internal.h:3037:29: note: 'ItemHoverable' declared here IMGUI_API bool ItemHoverable(const ImRect& bb, ImGuiID id, ImGuiItemFlags item_flags); ^ 1 error generated. make[3]: *** [libs/filagui/CMakeFiles/filagui.dir/build.make:116: libs/filagui/CMakeFiles/filagui.dir/src/ImGuiExtensions.cpp.o] Error 1 make[3]: Leaving directory '/<>/obj-x86_64-linux-gnu' make[2]: *** [CMakeFiles/Makefile2:1027: libs/filagui/CMakeFiles/filagui.dir/all] Error 2 Cheers -- Sebastian Ramacher
Bug#1061618: src:haskell-misfortune: unsatisfied build dependency in testing: libghc-regex-pcre-doc
Source: haskell-misfortune Version: 0.1.2.1-3 Severity: serious Tags: sid trixie User: debian...@lists.debian.org Usertags: edos-uninstallable Dear maintainer(s), Dose [1] is reporting a build issue with your package, it's missing a build dependency. Obviously your build dependencies shouldn't be removed from testing, but unfortunately there are multiple scenarios where that can happen nevertheless. To uphold our social contract, Debian requires that packages can be rebuild from source in the suite we are shipping them, so currently this is a serious issue with your package in testing. Can you please investigate the situation and figure out how to resolve it? Regularly, if the build dependency is available in unstable, helping the maintainer of your Build-Depends to enable migration to testing is a great way to solve the issue. If your build dependency is gone from unstable and testing, you'll have to fix the build process in some other way. Paul Note: this bug report was sent after some quick manual checks using a template. Please reach out to me if you believe I made a mistake in my process. [1] https://qa.debian.org/dose/debcheck/src_testing_main/latest/amd64.html OpenPGP_signature.asc Description: OpenPGP digital signature
Bug#1061617: src:roundcube: unsatisfied build dependency in testing: php-bacon-qr-code
Source: roundcube Version: 1.6.6+dfsg-1 Severity: serious Tags: sid trixie User: debian...@lists.debian.org Usertags: edos-uninstallable Dear maintainer(s), Dose [1] is reporting a build issue with your package, it's missing a build dependency. Obviously your build dependencies shouldn't be removed from testing, but unfortunately there are multiple scenarios where that can happen nevertheless. To uphold our social contract, Debian requires that packages can be rebuild from source in the suite we are shipping them, so currently this is a serious issue with your package in testing. Can you please investigate the situation and figure out how to resolve it? Regularly, if the build dependency is available in unstable, helping the maintainer of your Build-Depends to enable migration to testing is a great way to solve the issue. If your build dependency is gone from unstable and testing, you'll have to fix the build process in some other way. Paul Note: this bug report was sent after some quick manual checks using a template. Please reach out to me if you believe I made a mistake in my process. [1] https://qa.debian.org/dose/debcheck/src_testing_main/latest/amd64.html OpenPGP_signature.asc Description: OpenPGP digital signature
Bug#1061615: src:nanobind: unsatisfied build dependency in testing: python3-torch
Source: nanobind Version: 1.8.0-3 Severity: serious Tags: sid trixie User: debian...@lists.debian.org Usertags: edos-uninstallable Dear maintainer(s), Dose [1] is reporting a build issue with your package, it's missing a build dependency. Obviously your build dependencies shouldn't be removed from testing, but unfortunately there are multiple scenarios where that can happen nevertheless. To uphold our social contract, Debian requires that packages can be rebuild from source in the suite we are shipping them, so currently this is a serious issue with your package in testing.python3-torch Can you please investigate the situation and figure out how to resolve it? Regularly, if the build dependency is available in unstable, helping the maintainer of your Build-Depends to enable migration to testing is a great way to solve the issue. If your build dependency is gone from unstable and testing, you'll have to fix the build process in some other way. Paul Note: this bug report was sent after some quick manual checks using a template. Please reach out to me if you believe I made a mistake in my process. [1] https://qa.debian.org/dose/debcheck/src_testing_main/latest/amd64.html OpenPGP_signature.asc Description: OpenPGP digital signature
Processed: src:stellarium: fails to migrate to testing for too long: FTBFS on armel, ppc64el and s390x
Processing control commands: > close -1 23.4-1 Bug #1061613 [src:stellarium] src:stellarium: fails to migrate to testing for too long: FTBFS on armel, ppc64el and s390x Marked as fixed in versions stellarium/23.4-1. Bug #1061613 [src:stellarium] src:stellarium: fails to migrate to testing for too long: FTBFS on armel, ppc64el and s390x Marked Bug as done -- 1061613: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1061613 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1061613: src:stellarium: fails to migrate to testing for too long: FTBFS on armel, ppc64el and s390x
Source: stellarium Version: 23.3-1 Severity: serious Control: close -1 23.4-1 Tags: sid trixie User: release.debian@packages.debian.org Usertags: out-of-sync Dear maintainer(s), The Release Team considers packages that are out-of-sync between testing and unstable for more than 30 days as having a Release Critical bug in testing [1]. Your package src:stellarium has been trying to migrate for 31 days [2]. Hence, I am filing this bug. The version in unstable failed to build on armel, ppc64el and s390x as reported in bug 1060802. If a package is out of sync between unstable and testing for a longer period, this usually means that bugs in the package in testing cannot be fixed via unstable. Additionally, blocked packages can have impact on other packages, which makes preparing for the release more difficult. Finally, it often exposes issues with the package and/or its (reverse-)dependencies. We expect maintainers to fix issues that hamper the migration of their package in a timely manner. This bug will trigger auto-removal when appropriate. As with all new bugs, there will be at least 30 days before the package is auto-removed. I have immediately closed this bug with the version in unstable, so if that version or a later version migrates, this bug will no longer affect testing. I have also tagged this bug to only affect sid and trixie, so it doesn't affect (old-)stable. If you believe your package is unable to migrate to testing due to issues beyond your control, don't hesitate to contact the Release Team. Paul [1] https://lists.debian.org/debian-devel-announce/2023/06/msg1.html [2] https://qa.debian.org/excuses.php?package=stellarium OpenPGP_signature.asc Description: OpenPGP digital signature
Processed (with 1 error): cfgrib
Processing commands for cont...@bugs.debian.org:
> reassign 1055848 ecmwflibs 2:0.5.7-
Bug #1055848 {Done: Alastair McKinstry } [src:cfgrib]
cfgrib: test failure - can't find eccodes
Bug reassigned from package 'src:cfgrib' to 'ecmwflibs'.
No longer marked as found in versions cfgrib/0.9.10.4-2.
No longer marked as fixed in versions ecmwflibs/2:0.5.7-4.
Bug #1055848 {Done: Alastair McKinstry } [ecmwflibs]
cfgrib: test failure - can't find eccodes
There is no source info for the package 'ecmwflibs' at version '2:0.5.7-' with
architecture ''
Unable to make a source version for version '2:0.5.7-'
Marked as found in versions 2:0.5.7-.
> 3
Unknown command or malformed arguments to command.
> affects 1055848 cfgrib
Bug #1055848 {Done: Alastair McKinstry } [ecmwflibs]
cfgrib: test failure - can't find eccodes
Added indication that 1055848 affects cfgrib
> close 1055848
Bug #1055848 {Done: Alastair McKinstry } [ecmwflibs]
cfgrib: test failure - can't find eccodes
Bug 1055848 is already marked as done; not doing anything.
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
1055848: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1055848
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Bug#1060052: Status?
Hi, On Thu, Jan 25, 2024 at 02:55:52AM +, Dennis Haney wrote: > Can we please get a new release of a stable kernel? > This keeps crashing our machines, and it is a pain manually updating > to the 6.5 kernel on all of them. A fix for this issue will be released with the upcoming point releases scheduled on 10th of february as per https://lists.debian.org/debian-release/2024/01/msg00399.html . The kernel will be latest available as well one week earlier in bookworm-proposed-updates. Regards, Salvatore
Bug#1059660: marked as done (python-aioredlock: autopkgtest failure with Python 3.12)
Your message dated Sat, 27 Jan 2024 12:49:59 + with message-id and subject line Bug#1059660: fixed in python-aioredlock 0.7.3-3 has caused the Debian Bug report #1059660, regarding python-aioredlock: autopkgtest failure with Python 3.12 to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 1059660: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1059660 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: python-aioredlock Version: 0.7.3-2 Severity: serious User: debian-pyt...@lists.debian.org Usertags: python3.12 Hi Maintainer python-aioredlock's autopkgtests fail with Python 3.12 [1]. I've copied what I hope is the relevant part of the log below. Regards Graham [1] https://ci.debian.net/packages/p/python-aioredlock/testing/amd64/ 24s autopkgtest [20:09:56]: test autodep8-python3: [--- 24s Testing with python3.12: 24s Traceback (most recent call last): 24s File "", line 1, in 24s File "/usr/lib/python3/dist-packages/aioredlock/__init__.py", line 1, in 24s from aioredlock.algorithm import Aioredlock 24s File "/usr/lib/python3/dist-packages/aioredlock/algorithm.py", line 11, in 24s from aioredlock.redis import Redis 24s File "/usr/lib/python3/dist-packages/aioredlock/redis.py", line 5, in 24s from distutils.version import StrictVersion 24s ModuleNotFoundError: No module named 'distutils' 25s autopkgtest [20:09:57]: test autodep8-python3: ---] --- End Message --- --- Begin Message --- Source: python-aioredlock Source-Version: 0.7.3-3 Done: Jelmer Vernooij We believe that the bug you reported is fixed in the latest version of python-aioredlock, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 1059...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Jelmer Vernooij (supplier of updated python-aioredlock package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Sat, 27 Jan 2024 12:08:04 + Source: python-aioredlock Architecture: source Version: 0.7.3-3 Distribution: unstable Urgency: medium Maintainer: Jelmer Vernooij Changed-By: Jelmer Vernooij Closes: 1059660 Changes: python-aioredlock (0.7.3-3) unstable; urgency=medium . * Add patch python3.12: fix FTBFS, compatibility with Python 3.12. Closes: #1059660 * Add dependency on python3-packaging. Checksums-Sha1: 6c24d6accb68da8969e2a15353a730ce9487ef16 1778 python-aioredlock_0.7.3-3.dsc 3622b23ea37ed80c32d4a352e5b5fe16e8641a4f 2716 python-aioredlock_0.7.3-3.debian.tar.xz 0167bee8a13e5787ce91da0aec82814cc08e9d69 8065 python-aioredlock_0.7.3-3_source.buildinfo Checksums-Sha256: 1584429f0f27c1967fb049dc774b34c416c2592ea3bfc4a24f64a4fc22ca3cbf 1778 python-aioredlock_0.7.3-3.dsc e5d3db818d52cf567e090b32eea67acc6953eeac4c7a9a7b0ffb28f54ef06fa7 2716 python-aioredlock_0.7.3-3.debian.tar.xz b5dad504675622d3b443cc12b2b2dd9b9a34a7b868ee8b1fb3644c02669ad711 8065 python-aioredlock_0.7.3-3_source.buildinfo Files: 03d4aff3d8aa94899edaed211be8cee6 1778 python optional python-aioredlock_0.7.3-3.dsc 37984533a345a081233ea4e79816689c 2716 python optional python-aioredlock_0.7.3-3.debian.tar.xz 328d6f9c5cd414edb42a863cb711271e 8065 python optional python-aioredlock_0.7.3-3_source.buildinfo -BEGIN PGP SIGNATURE- iQEzBAEBCgAdFiEEgIoEfJX3ae+y722SMG8hYYBCUGYFAmW09WsACgkQMG8hYYBC UGYeEggAiOlZ1WuPKsWJqdnp2pnBcsWPKlyaF+GANwvLLIom8VPC04yMELdMj29F KLIFBlVd9lUdOf/UQa7ekzqq3fmdycOR8N3hCYA6uUGwkR47L5mNCBU5nrgxdRrE AwJ0MwydbQStmZR98ExoXHGCfsPSGQ47gGR8Ols4O8UR7tegAJW/CgiiSFyMfSAp Y2FI6ZlIM4uvdCxxeGybGUEGuDiLNLmuaBtwNMQNxw7R12YO31GKKV9DUw4GJ/4F pYto1Gvj9UcbYjQDcTbhD1xzYOIK1UpNL0/Q+O6jzK418akWOWlhYq956Gb/tMEA WHYxnDVIxqrY6hNZJGO6Vj77AROdMg== =gNFs -END PGP SIGNATURE End Message ---
Bug#1061392: uploaded NMU to DELAYED/5
Sorry for the confusion, On 27.01.24 12:37, Torsten Landschoff wrote: Hi Matthias, Am 2024-01-26 17:14, schrieb Matthias Klose: uploaded NMU 4.2.0-0.1 to DELAYED/5 I had 4.2.0-1 in work at salsa and tried uploading it now to avoid the delay. Now the queue daemon rejected my upload because the existing uploaded: -- /swig_4.2.0-1_source.changes is already present on target host: 5-day/swig_4.2.0.orig.tar.gz Either you already uploaded it, or someone else came first. Job swig_4.2.0-1_source.changes removed. -- AFAIR remember, a direct upload should take precedence over a delayed one. I wonder what the best way forward would be here. * Wait for the delayed upload to get processed * Prepare a new upload without the orig.tar.gz * Overwrite 4.2.0-0.1? I'd like to have the debian/changelog contain all versions ever in unstable, but I have no idea how I would merge those changes. Maybe just put your changelog entry into debian/master :shrug: Do you have a better solution? I just ran dcut ftp-master cancel swig_4.2.0-0.1_source.changes So you should be able to do a normal upload, when this command is processed.
Bug#1061392: uploaded NMU to DELAYED/5
Hi Matthias, Am 2024-01-26 17:14, schrieb Matthias Klose: uploaded NMU 4.2.0-0.1 to DELAYED/5 I had 4.2.0-1 in work at salsa and tried uploading it now to avoid the delay. Now the queue daemon rejected my upload because the existing uploaded: -- /swig_4.2.0-1_source.changes is already present on target host: 5-day/swig_4.2.0.orig.tar.gz Either you already uploaded it, or someone else came first. Job swig_4.2.0-1_source.changes removed. -- AFAIR remember, a direct upload should take precedence over a delayed one. I wonder what the best way forward would be here. * Wait for the delayed upload to get processed * Prepare a new upload without the orig.tar.gz * Overwrite 4.2.0-0.1? I'd like to have the debian/changelog contain all versions ever in unstable, but I have no idea how I would merge those changes. Maybe just put your changelog entry into debian/master :shrug: Do you have a better solution? Greetings, Torsten
Bug#1058376: marked as done (python-django-extensions: FTBFS: TypeError: Can't instantiate abstract class CRNoFunction without an implementation for abstract method 'resolve_collisions')
Your message dated Sat, 27 Jan 2024 11:39:02 +
with message-id
and subject line Bug#1058376: fixed in python-django-extensions 3.2.3-1
has caused the Debian Bug report #1058376,
regarding python-django-extensions: FTBFS: TypeError: Can't instantiate
abstract class CRNoFunction without an implementation for abstract method
'resolve_collisions'
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.)
--
1058376: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1058376
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: python-django-extensions
Version: 3.2.1-2
Severity: serious
Justification: FTBFS
Tags: trixie sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20231212 ftbfs-trixie
Hi,
During a rebuild of all packages in sid, your package failed to build
on amd64.
Relevant part (hopefully):
> make[1]: Entering directory '/<>'
> PYTHONPATH=. \
> dh_auto_test -- --system=custom --test-args="{interpreter} -m pytest
> --cov=django_extensions --ds=tests.testapp.settings
> --ignore=tests/management/commands/test_create_template_tags.py
> --ignore=tests/management/commands/test_pipchecker.py
> --ignore=tests/templatetags/test_highlighting.py
> --ignore=tests/management/commands/shell_plus_tests/test_shell_plus.py tests"
> I: pybuild base:310: python3.12 -m pytest --cov=django_extensions
> --ds=tests.testapp.settings
> --ignore=tests/management/commands/test_create_template_tags.py
> --ignore=tests/management/commands/test_pipchecker.py
> --ignore=tests/templatetags/test_highlighting.py
> --ignore=tests/management/commands/shell_plus_tests/test_shell_plus.py tests
> = test session starts
> ==
> platform linux -- Python 3.12.1, pytest-7.4.3, pluggy-1.3.0
> django: settings: tests.testapp.settings (from option)
> rootdir: /<>
> configfile: setup.cfg
> plugins: cov-4.1.0, django-4.5.2
> collected 502 items / 1 skipped
>
> tests/test_admin_filter.py . [
> 0%]
> tests/test_admin_widgets.py .[
> 1%]
> tests/test_autoslug_fields.py .. [
> 6%]
> tests/test_clean_pyc.py ... [
> 6%]
> tests/test_compat.py ... [
> 7%]
> tests/test_compile_pyc.py .. [
> 7%]
> tests/test_dumpscript.py . [
> 8%]
> tests/test_find_template.py .. [
> 9%]
> tests/test_json_field.py .. [
> 11%]
> tests/test_logging_filters.py ...[
> 11%]
> tests/test_management_command.py F. [
> 16%]
> tests/test_models.py .. [
> 17%]
> tests/test_modificationdatetime_fields.py ...[
> 18%]
> tests/test_parse_mysql_cnf.py ...[
> 18%]
> tests/test_randomchar_field.py [
> 21%]
> tests/test_runscript.py [
> 28%]
> tests/test_shortuuid_field.py [
> 29%]
> tests/test_sqldiff.py ...sss... [
> 30%]
> tests/test_template_rendering.py .. [
> 31%]
> tests/test_templatetags.py ... [
> 31%]
> tests/test_timestamped_model.py .. [
> 32%]
> tests/test_validators.py .. [
> 33%]
> tests/test_version.py ...[
> 34%]
> tests/auth/test_mixins.py .. [
> 34%]
> tests/db/fields/test_uniq_field_mixin.py ... [
> 35%]
> tests/db/fields/test_uniq_field_mixin_compat.py ... [
> 37%]
> tests/jobs/daily/test_cache_cleanup.py ..[
> 37%]
> tests/management/test_email_notifications.py [
> 38%]
> tests/management/commands/test_admin_generator.py [
> 39%]
> tests/management/commands/test_clear_cache.py .. [
> 40%]
> tests/management/commands/test_create_command.py [
> 41%]
> tests/management/co
Bug#1060950: marked as done (cage: FTBFS: ../idle_inhibit_v1.c:11:10: fatal error: wlr/types/wlr_idle.h: No such file or directory)
Your message dated Sat, 27 Jan 2024 10:49:34 + with message-id and subject line Bug#1058495: fixed in cage 0.1.5+20240127-1 has caused the Debian Bug report #1058495, regarding cage: FTBFS: ../idle_inhibit_v1.c:11:10: fatal error: wlr/types/wlr_idle.h: No such file or directory to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 1058495: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1058495 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: cage Version: 0.1.5-1 Severity: serious Justification: FTBFS Tags: trixie sid ftbfs User: lu...@debian.org Usertags: ftbfs-20240115 ftbfs-trixie Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > cc -Icage.p -I. -I.. -I/usr/include/libdrm -I/usr/include/pixman-1 > -fdiagnostics-color=always -D_FILE_OFFSET_BITS=64 -Wall -Winvalid-pch -Wextra > -Werror -std=c11 -DWLR_USE_UNSTABLE -Wundef -Wno-unused-parameter -g -O2 > -ffile-prefix-map=/<>=. -fstack-protector-strong > -fstack-clash-protection -Wformat -Werror=format-security -fcf-protection > -Wdate-time -D_FORTIFY_SOURCE=2 -MD -MQ cage.p/idle_inhibit_v1.c.o -MF > cage.p/idle_inhibit_v1.c.o.d -o cage.p/idle_inhibit_v1.c.o -c > ../idle_inhibit_v1.c > ../idle_inhibit_v1.c:11:10: fatal error: wlr/types/wlr_idle.h: No such file > or directory >11 | #include > | ^~ > compilation terminated. > [4/10] cc -Icage.p -I. -I.. -I/usr/include/libdrm -I/usr/include/pixman-1 > -fdiagnostics-color=always -D_FILE_OFFSET_BITS=64 -Wall -Winvalid-pch -Wextra > -Werror -std=c11 -DWLR_USE_UNSTABLE -Wundef -Wno-unused-parameter -g -O2 > -ffile-prefix-map=/<>=. -fstack-protector-strong > -fstack-clash-protection -Wformat -Werror=format-security -fcf-protection > -Wdate-time -D_FORTIFY_SOURCE=2 -MD -MQ cage.p/cage.c.o -MF cage.p/cage.c.o.d > -o cage.p/cage.c.o -c ../cage.c > FAILED: cage.p/cage.c.o > cc -Icage.p -I. -I.. -I/usr/include/libdrm -I/usr/include/pixman-1 > -fdiagnostics-color=always -D_FILE_OFFSET_BITS=64 -Wall -Winvalid-pch -Wextra > -Werror -std=c11 -DWLR_USE_UNSTABLE -Wundef -Wno-unused-parameter -g -O2 > -ffile-prefix-map=/<>=. -fstack-protector-strong > -fstack-clash-protection -Wformat -Werror=format-security -fcf-protection > -Wdate-time -D_FORTIFY_SOURCE=2 -MD -MQ cage.p/cage.c.o -MF cage.p/cage.c.o.d > -o cage.p/cage.c.o -c ../cage.c > ../cage.c:28:10: fatal error: wlr/types/wlr_idle.h: No such file or directory >28 | #include > | ^~ > compilation terminated. > [5/10] cc -Icage.p -I. -I.. -I/usr/include/libdrm -I/usr/include/pixman-1 > -fdiagnostics-color=always -D_FILE_OFFSET_BITS=64 -Wall -Winvalid-pch -Wextra > -Werror -std=c11 -DWLR_USE_UNSTABLE -Wundef -Wno-unused-parameter -g -O2 > -ffile-prefix-map=/<>=. -fstack-protector-strong > -fstack-clash-protection -Wformat -Werror=format-security -fcf-protection > -Wdate-time -D_FORTIFY_SOURCE=2 -MD -MQ cage.p/view.c.o -MF cage.p/view.c.o.d > -o cage.p/view.c.o -c ../view.c > FAILED: cage.p/view.c.o > cc -Icage.p -I. -I.. -I/usr/include/libdrm -I/usr/include/pixman-1 > -fdiagnostics-color=always -D_FILE_OFFSET_BITS=64 -Wall -Winvalid-pch -Wextra > -Werror -std=c11 -DWLR_USE_UNSTABLE -Wundef -Wno-unused-parameter -g -O2 > -ffile-prefix-map=/<>=. -fstack-protector-strong > -fstack-clash-protection -Wformat -Werror=format-security -fcf-protection > -Wdate-time -D_FORTIFY_SOURCE=2 -MD -MQ cage.p/view.c.o -MF cage.p/view.c.o.d > -o cage.p/view.c.o -c ../view.c > In file included from ../view.c:19: > ../output.h:6:10: fatal error: wlr/types/wlr_output_damage.h: No such file or > directory > 6 | #include > | ^~~ > compilation terminated. > [6/10] cc -Icage.p -I. -I.. -I/usr/include/libdrm -I/usr/include/pixman-1 > -fdiagnostics-color=always -D_FILE_OFFSET_BITS=64 -Wall -Winvalid-pch -Wextra > -Werror -std=c11 -DWLR_USE_UNSTABLE -Wundef -Wno-unused-parameter -g -O2 > -ffile-prefix-map=/<>=. -fstack-protector-strong > -fstack-clash-protection -Wformat -Werror=format-security -fcf-protection > -Wdate-time -D_FORTIFY_SOURCE=2 -MD -MQ cage.p/seat.c.o -MF cage.p/seat.c.o.d > -o cage.p/seat.c.o -c ../seat.c > FAILED: cage.p/seat.c.o > cc -Icage.p -I. -I.. -I/usr/include/libdrm -I/usr/include/pixman-1 &g
Bug#1058495: marked as done (cage: Please update to wlroots 0.17)
Your message dated Sat, 27 Jan 2024 10:49:34 + with message-id and subject line Bug#1058495: fixed in cage 0.1.5+20240127-1 has caused the Debian Bug report #1058495, regarding cage: Please update to wlroots 0.17 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.) -- 1058495: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1058495 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: cage Severity: wishlist User: team+swa...@tracker.debian.org Usertags: wlroots-0.17 Dear Maintainer, Please update cage to work with wlroots 0.17. 0.17.0 is currently in experimental an will be uploaded to unstable by the end of December 2023. Cheers, -- Guido --- End Message --- --- Begin Message --- Source: cage Source-Version: 0.1.5+20240127-1 Done: Birger Schacht We believe that the bug you reported is fixed in the latest version of cage, 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 1058...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Birger Schacht (supplier of updated cage package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Sat, 27 Jan 2024 10:44:53 +0100 Source: cage Architecture: source Version: 0.1.5+20240127-1 Distribution: unstable Urgency: medium Maintainer: Sway and related packages team Changed-By: Birger Schacht Closes: 1058495 Changes: cage (0.1.5+20240127-1) unstable; urgency=medium . * Upload updated unrelease upstream sources for wlroots 0.17 compatibility (Closes: #1058495) * d/rules: change meson option from `true` to `enabled` * d/copyright: bump years * d/control: set and update build-dep version constraints Checksums-Sha1: 096801f071aee4fd235b837f6ac8438706d73091 2084 cage_0.1.5+20240127-1.dsc f0f59471f02715d8d343c165e62e862f24c27ade 23793 cage_0.1.5+20240127.orig.tar.gz b74bc5c91f92c2a2cbafcb32c41be250a5117ba5 6972 cage_0.1.5+20240127-1.debian.tar.xz 219155f5a9108d2f45df5c620ac15811c61b748a 11389 cage_0.1.5+20240127-1_amd64.buildinfo Checksums-Sha256: 61080f3b1d700a6e5f3cb3bd19b9b1f4e3045125802cdbc9d0345fb9dabb06e7 2084 cage_0.1.5+20240127-1.dsc cc0ac53e2b5827c41084f085f4850d12fdbd58dcea29ee5fb3cc039fd17b860e 23793 cage_0.1.5+20240127.orig.tar.gz 7f40f90fb926c2528fd16a0a328ccd268577cb956864f01ede6fc4296d4db9a4 6972 cage_0.1.5+20240127-1.debian.tar.xz 986c8cb038c842ae49b6ee308475f6952212cec1d295cbf4ab869b4993e6b328 11389 cage_0.1.5+20240127-1_amd64.buildinfo Files: d2e7601c3ea113d4cb17d85b3f9a7ff7 2084 x11 optional cage_0.1.5+20240127-1.dsc ff281c62cb627a9a804c760f0e8fbb3e 23793 x11 optional cage_0.1.5+20240127.orig.tar.gz a35f8205e0467732b348d3c348741cda 6972 x11 optional cage_0.1.5+20240127-1.debian.tar.xz ab3d1e5bf5a17d652a62c1730054b1bc 11389 x11 optional cage_0.1.5+20240127-1_amd64.buildinfo -BEGIN PGP SIGNATURE- iQJGBAEBCgAwFiEEOvC8tnwmrEjOtOW8KgxdYPIEvbAFAmW01rgSHGJpcmdlckBk ZWJpYW4ub3JnAAoJECoMXWDyBL2wDyQQALsqai9+qkXbmr2xNsWFfBoHR4uz/FrJ zjJznXrf5wk5SdnYhVrMPy5h1ybKjLLZwYMdtUSQRKnEJCCEVN39SJ1NF3Yg+vSc whfe69eCkCT1B7ZmNLt4LT66j13irkbKL5+qeo7ar8DzGIgmmYEVbYAg4vfy3nJn R+si1o9Ai/EjFDUWtw4PIZDvp3Lw205HhpRnvlnN3aykuYrPd3Zgj9DHp0Bi613U vH2snJfXtB6GJ4eVBwF4GmR2WFIxTUqBXw6VmIW1xT/6jnowKwA2K0LTQjjCSktf 8IYkvqNZ0ExehrE6fQdDbFVhjyy9MKSD+KV5dURywiIrKmHI6Af8+muyoPzEIqGf FhuKGzRjhMaHjtbyAGVuugQHEim/xGaQHKCmTgEbzWaoAXtJJKHyWei6Tp+nYJNJ 3CuZDpfGmv7iRwgrdqngV7Bgx2iGmjS7GfPdxwPtgo5GRYN3F7L7+q8bpyg+dpYi OaqVxRMxXabzvhcN1CUF0v2yWeCd/RIqK9f2iNQzreoDLoYTCMMF2X1QjF4FdrxS hW13C+sm1GVVJX51fW27ciuL2wRO71SoWRmkTqv4TAH+07ANAvL1PXrVG4YIDRef jRri7Q16Tn/5uE/2WAYwKL60kLactWhJN0iDABBxHt6se+KCi1SHluZ501ZvTnqY 1+PpAQw+a5DN =eG9t -END PGP SIGNATURE End Message ---
Processed: fixed 1058375 in 1.99.0-1
Processing commands for cont...@bugs.debian.org:
> fixed 1058375 1.99.0-1
Bug #1058375 [src:matrix-synapse] matrix-synapse: FTBFS: dh_auto_test: error:
pybuild --test --test-pytest -i python{version} -p "3.12 3.11" returned exit
code 13
Marked as fixed in versions matrix-synapse/1.99.0-1.
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
1058375: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1058375
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Processed: retitle 1061577 to rust-io: RUSTSEC-2020-0021: CVE-2020-35876: use-after-free buffer access when a future is leaked
Processing commands for cont...@bugs.debian.org: > retitle 1061577 rust-io: RUSTSEC-2020-0021: CVE-2020-35876: use-after-free > buffer access when a future is leaked Bug #1061577 [src:rust-rio] rust-rio: use-after-free buffer access when a future is leaked Changed Bug title to 'rust-io: RUSTSEC-2020-0021: CVE-2020-35876: use-after-free buffer access when a future is leaked' from 'rust-rio: use-after-free buffer access when a future is leaked'. > thanks Stopping processing here. Please contact me if you need assistance. -- 1061577: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1061577 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: tagging 1061577
Processing commands for cont...@bugs.debian.org: > tags 1061577 + security Bug #1061577 [src:rust-rio] rust-rio: use-after-free buffer access when a future is leaked Added tag(s) security. > thanks Stopping processing here. Please contact me if you need assistance. -- 1061577: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1061577 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1061605: scipy: tests skipped during build and autopkgtest not in sync
Source: scipy Version: 1.10.1-7 Severity: serious Tags: sid trixie User: debian...@lists.debian.org Usertags: regression Hi Maintainer scipy's autopkgtests have regressed on arm64 [1], i386 [2], ppc64el [3] and s390x [4]. It seems (at least for arm64) that test_maxiter_worsening[lgmres] is skipped during the build [5], but fails during the autopkgtest. The same may be true for the other architectures. I think there are enough logs available to go through and figure out the remaining. I'll try to do this in the next week or so. Regards Graham [1] https://ci.debian.net/packages/s/scipy/testing/arm64/ [2] https://ci.debian.net/packages/s/scipy/testing/i386/ [3] https://ci.debian.net/packages/s/scipy/testing/ppc64el/ [4] https://ci.debian.net/packages/s/scipy/testing/s390x/ [5] https://salsa.debian.org/python-team/packages/scipy/-/blob/debian/1.10.1-6/debian/rules?ref_type=tags#L33-35
Bug#1061604: cctbx: autopkgtest regression
Source: cctbx Version: 2023.12+ds2+~3.17.0+ds1-3 Severity: serious User: debian...@lists.debian.org Usertags: regression Hi Maintainer The cctbx's autopkgtest are failing [1], preventing migration. I've copied what I hope is the relevant part of the log below. I suspect there are missing (test) dependencies. Previously, gcc was pulled in as a dependency through python3-pythran, through python3-scipy. This is currently not the case. Regards Graham [1] https://ci.debian.net/packages/c/cctbx/testing/amd64/ 75s Standard error: 75s Traceback (most recent call last): 75s File "/usr/lib/python3/dist-packages/boost_adaptbx/tests/tst_python_streambuf.py", line 7, in 75s import StringIO 75s ModuleNotFoundError: No module named 'StringIO' 78s Standard error: 78s Traceback (most recent call last): 78s File "/usr/lib/python3/dist-packages/fable/test/tst_separate_files.py", line 95, in 78s run(args=sys.argv[1:]) 78s File "/usr/lib/python3/dist-packages/fable/test/tst_separate_files.py", line 70, in run 78s exercise(verbose, 78s File "/usr/lib/python3/dist-packages/fable/test/tst_separate_files.py", line 38, in exercise 78s cmd = comp_env.compilation_command(file_name_cpp=file_name_cpp) 78s ^ 78s File "/usr/lib/python3/dist-packages/fable/simple_compilation.py", line 121, in compilation_command 78s return O.assemble_command( 78s ^^^ 78s File "/usr/lib/python3/dist-packages/fable/simple_compilation.py", line 91, in assemble_command 78s if (disable_warnings or O.gcc_version < 30400): 78s ^ 78s TypeError: '<' not supported between instances of 'NoneType' and 'int' 78s libtbx.python "/usr/lib/python3/dist-packages/cctbx/regression/tst_sampled_model_density.py" P31 [OK] 2.0s
