date:20231217

Bug#1056430: marked as done (neutron-vpnaas-dashboard's autopkg tests fail with Python 3.12)

2023-12-17 Thread Debian Bug Tracking System

Your message dated Mon, 18 Dec 2023 08:27:01 +0100
with message-id <2f9b6a79-0530-4613-bc92-c225414eb...@debian.org>
and subject line Fixed
has caused the Debian Bug report #1056430,
regarding neutron-vpnaas-dashboard's autopkg tests fail with Python 3.12
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
1056430: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1056430
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---

Package: src:neutron-vpnaas-dashboard
Version: 8.0.0-2
Severity: important
Tags: sid trixie
User: debian-pyt...@lists.debian.org
Usertags: python3.12

neutron-vpnaas-dashboard's autopkg tests fail with Python 3.12:

[...]
281s autopkgtest [18:30:15]: test unittests: [---
281s + PKGOS_TEST_PARALLEL=yes
281s + PKGOS_TEST_SERIAL=no
281s + PYTHONS=disabled
281s + PYTHON3S=disabled
281s + TEST_PARALLEL_OPT=--parallel
281s + TEST_SERIAL_OPT=
281s + echo WARNING: --no-py2 is deprecated, and always on.
281s + shift
281s + py3versions -vr
281s WARNING: --no-py2 is deprecated, and always on.
281s + PYTHON3S=3.12 3.11
281s + [ yes = no ]
281s + [ no = yes ]
281s + [ 3.12 = disabled ]
281s + echo 3.12
281s + cut -d. -f1
281s + PYMAJOR=3
281s + echo ===> Testing with python (python3)
281s + ===> Testing with python (python3)
281s pwd
281s + [ -d 
/tmp/autopkgtest.TNLwRP/build.JW4/src/debian/tmp/usr/lib/python3/dist-packages 
]

281s + [ -e .stestr.conf ]
281s + [ -e .testr.conf ]
281s + [ 3.11 = disabled ]
281s + echo 3.11
281s + cut -d. -f1
281s ===> Testing with python (python3)
281s + PYMAJOR=3
281s + echo ===> Testing with python (python3)
281s + pwd
281s + [ -d 
/tmp/autopkgtest.TNLwRP/build.JW4/src/debian/tmp/usr/lib/python3/dist-packages 
]

281s + [ -e .stestr.conf ]
281s + [ -e .testr.conf ]
282s /usr/lib/python3/dist-packages/pytz/__init__.py:30: SyntaxWarning: 
invalid escape sequence '\s'

282s   match = re.match("^#\s*version\s*([0-9a-z]*)\s*$", line)
282s Traceback (most recent call last):
282s   File "/tmp/autopkgtest.TNLwRP/build.JW4/src/manage.py", line 23, 
in 

282s execute_from_command_line(sys.argv)
282s   File 
"/usr/lib/python3/dist-packages/django/core/management/__init__.py", 
line 442, in execute_from_command_line

282s utility.execute()
282s   File 
"/usr/lib/python3/dist-packages/django/core/management/__init__.py", 
line 382, in execute

282s settings.INSTALLED_APPS
282s   File "/usr/lib/python3/dist-packages/django/conf/__init__.py", 
line 102, in __getattr__

282s self._setup(name)
282s   File "/usr/lib/python3/dist-packages/django/conf/__init__.py", 
line 89, in _setup

282s self._wrapped = Settings(settings_module)
282s ^
282s   File "/usr/lib/python3/dist-packages/django/conf/__init__.py", 
line 217, in __init__

282s mod = importlib.import_module(self.SETTINGS_MODULE)
282s   ^
282s   File "/usr/lib/python3.12/importlib/__init__.py", line 90, in 
import_module

282s return _bootstrap._gcd_import(name[level:], package, level)
282s
282s   File "", line 1381, in _gcd_import
282s   File "", line 1354, in _find_and_load
282s   File "", line 1325, in 
_find_and_load_unlocked

282s   File "", line 929, in _load_unlocked
282s   File "", line 994, in 
exec_module
282s   File "", line 488, in 
_call_with_frames_removed
282s   File 
"/tmp/autopkgtest.TNLwRP/build.JW4/src/neutron_vpnaas_dashboard/test/settings.py", 
line 15, in 

282s from openstack_dashboard.test.settings import *  # noqa
282s ^^^
282s   File 
"/usr/lib/python3/dist-packages/openstack_dashboard/test/settings.py", 
line 18, in 

282s from horizon.utils import secret_key
282s   File 
"/usr/lib/python3/dist-packages/horizon/utils/secret_key.py", line 21, 
in 

282s from oslo_concurrency import lockutils
282s   File 
"/usr/lib/python3/dist-packages/oslo_concurrency/lockutils.py", line 37, 
in 

282s import eventlet
282s   File "/usr/lib/python3/dist-packages/eventlet/__init__.py", line 
17, in 

282s from eventlet import convenience
282s   File "/usr/lib/python3/dist-packages/eventlet/convenience.py", 
line 7, in 

282s from eventlet.green import socket
282s   File "/usr/lib/python3/dist-packages/eventlet/green/socket.py", 
line 21, in 

282s from eventlet.support import greendns
282s   File 
"/usr/lib/python3/dist-packages/eventlet/support/greendns.py", line 45, 
in 

282s from eventlet.green import ssl
282s   File

Bug#985184: reminiscence not anymore licensed

2023-12-17 Thread Stephen Kitt

On Mon, 18 Dec 2023 00:38:26 +0100, Alexandre Detiste
 wrote:
> I think until the licensing problem is not resolved,
> this old version of the game should not be included in a release.

Why not? The license of the old version is still valid...

Regards,

Stephen


pgpxVFjnDIF0f.pgp
Description: OpenPGP digital signature

Bug#1053843: marked as done (src:user-mode-linux: unsatisfied build dependency in testing: linux-source-6.4)

2023-12-17 Thread Debian Bug Tracking System

Your message dated Mon, 18 Dec 2023 11:45:30 +0530
with message-id 
and subject line Re: Bug#1053843: src:user-mode-linux: unsatisfied build 
dependency in testing: linux-source-6.4
has caused the Debian Bug report #1053843,
regarding src:user-mode-linux: unsatisfied build dependency in testing: 
linux-source-6.4
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.)


-- 
1053843: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1053843
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---

Source: user-mode-linux
Version: 6.4um1
Severity: serious
Tags: sid bookworm
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
--- End Message ---
--- Begin Message ---



signature.asc
Description: This is a digitally signed message part
--- End Message ---

Bug#1056279: Bug#1057220: Looks like the systemctl links are gone but not the pm-utils ones

2023-12-17 Thread Francois Marier

Thank you Helmut and Chris for the helpful discussion.

I have finally found some time to review your comments and the proposed
molly-guard patches. While I'm still not 100% confident I understand the
problem (and the fix), the solution you have settled on makes sense to me.

With respect to the presence of the real commands in the path, I'm not too
worried about it personally. I do agree it's unfortunate and it would be
great if we could do this reliably without putting the diverted binary
within easy reach, but at the end of the day, molly-guard will never catch
all possible mistakes. As Helmut pointed out, it's already missing some
cases (and it's always been possible to "init 6" as well), but I think it
still provides a useful service if it catches the most common cases of
accidental reboots. I had a similar dilemma for another package I maintain
(safe-rm) and I've decided there to focus on the most common cases again to
reduce complexity, and improve reliability.

I will leave this for a few days in case others like Simó want to also chime
in, but otherwise I am planning to upload to experimental this week and then
unstable a few days later.

Again many thanks for all of the work that has gone into solving this thorny
problem.

Francois

Bug#1058904: python3-apt: apt_pkg.TagFile segfaults on files with comments

2023-12-17 Thread Stuart Prescott

Package: python3-apt
Version: 2.7.2
Severity: serious
X-Debbugs-Cc: stu...@debian.org

Dear Maintainer,

With the upgrade to python3-apt 2.7.2, CI for python-debian started
failing for both python3.11 and python3.12. The particular test where
the segfault is found feeds apt_pkg.TagFile data that contains comments
in the form permitted by Policy for source package control files.

https://salsa.debian.org/stuart/python-debian/-/blob/master/tests/test_deb822.py?ref_type=heads#L1279

Previous versions raised apt_pkg.Error for erronous data.

They key feature of the data that is causing the segfault is the
inclusion of a comment in a multiline field.

While users of python-debian's deb822 wrappers are encouraged to not use
apt_pkg.TagFile for anything other than archive-generated files such as
the Sources and Packages files, there are legacy users and
out-of-archive users that could be doing so. Unparsable data should also
not segfault the interpreter but generate an exception.

regards
Stuart


Steps to reproduce (output below are for git HEAD with a slightly
rearranged directory structure; current version in sid does the same):

$ debcheckout python-debian
$ cd python-debian
$ python3.11 -m pytest -k test_iter_paragraphs_comments_use_apt_pkg
== test session starts 
==
platform linux -- Python 3.11.7, pytest-7.4.3, pluggy-1.3.0 -- 
/usr/bin/python3.11
cachedir: .pytest_cache
rootdir: /tmp/pkgs/python-debian
configfile: pyproject.toml
testpaths: src, tests
plugins: cov-4.1.0
collected 295 items / 294 deselected / 1 selected

tests/test_deb822.py::TestDeb822::test_iter_paragraphs_comments_use_apt_pkg 
Fatal Python error: Segmentation fault

Current thread 0x7f97ca55a040 (most recent call first):
File "/tmp/pkgs/python-debian/src/debian/deb822.py", line 740 in iter_paragraphs
File "/tmp/pkgs/python-debian/tests/test_deb822.py", line 1297 in 
test_iter_paragraphs_comments_use_apt_pkg
File "/usr/lib/python3/dist-packages/_pytest/python.py", line 194 in 
pytest_pyfunc_call
File "/usr/lib/python3/dist-packages/pluggy/_callers.py", line 77 in _multicall
File "/usr/lib/python3/dist-packages/pluggy/_manager.py", line 115 in _hookexec
File "/usr/lib/python3/dist-packages/pluggy/_hooks.py", line 493 in __call__
File "/usr/lib/python3/dist-packages/_pytest/python.py", line 1792 in runtest
File "/usr/lib/python3/dist-packages/_pytest/runner.py", line 169 in 
pytest_runtest_call
File "/usr/lib/python3/dist-packages/pluggy/_callers.py", line 77 in _multicall
File "/usr/lib/python3/dist-packages/pluggy/_manager.py", line 115 in _hookexec
File "/usr/lib/python3/dist-packages/pluggy/_hooks.py", line 493 in __call__
File "/usr/lib/python3/dist-packages/_pytest/runner.py", line 262 in 
File "/usr/lib/python3/dist-packages/_pytest/runner.py", line 341 in from_call
File "/usr/lib/python3/dist-packages/_pytest/runner.py", line 261 in 
call_runtest_hook
File "/usr/lib/python3/dist-packages/_pytest/runner.py", line 222 in 
call_and_report
File "/usr/lib/python3/dist-packages/_pytest/runner.py", line 133 in 
runtestprotocol
File "/usr/lib/python3/dist-packages/_pytest/runner.py", line 114 in 
pytest_runtest_protocol
File "/usr/lib/python3/dist-packages/pluggy/_callers.py", line 77 in _multicall
File "/usr/lib/python3/dist-packages/pluggy/_manager.py", line 115 in _hookexec
File "/usr/lib/python3/dist-packages/pluggy/_hooks.py", line 493 in __call__
File "/usr/lib/python3/dist-packages/_pytest/main.py", line 350 in 
pytest_runtestloop
File "/usr/lib/python3/dist-packages/pluggy/_callers.py", line 77 in _multicall
File "/usr/lib/python3/dist-packages/pluggy/_manager.py", line 115 in _hookexec
File "/usr/lib/python3/dist-packages/pluggy/_hooks.py", line 493 in __call__
File "/usr/lib/python3/dist-packages/_pytest/main.py", line 325 in _main
File "/usr/lib/python3/dist-packages/_pytest/main.py", line 271 in wrap_session
File "/usr/lib/python3/dist-packages/_pytest/main.py", line 318 in 
pytest_cmdline_main
File "/usr/lib/python3/dist-packages/pluggy/_callers.py", line 77 in _multicall
File "/usr/lib/python3/dist-packages/pluggy/_manager.py", line 115 in _hookexec
File "/usr/lib/python3/dist-packages/pluggy/_hooks.py", line 493 in __call__
File "/usr/lib/python3/dist-packages/_pytest/config/__init__.py", line 169 in 
main
File "/usr/lib/python3/dist-packages/_pytest/config/__init__.py", line 192 in 
console_main
File "/usr/lib/python3/dist-packages/pytest/__main__.py", line 5 in 
File "", line 88 in _run_code
File "", line 198 in _run_module_as_main


Or a minimal example directly with apt_pkg:
$ echo "Source: foo
Build-Depends: debhelper,
# quux,
 python" > data
$ python3 -c "import apt_pkg; [p for p in apt_pkg.TagFile(open('data', 'rt'))]"
Segmentation fault (core dumped)

Bug#1055575: gst-python1.0 ftbfs with Python 3.12

2023-12-17 Thread Dean Serenevy




Hello, I also tried poking at this issue today and ran into the same problem. Replacing 
imp with what I believe to be the equivalent importlib commands results in a bunch of 
errors during testing (many "TypeError: SomeFunction() takes no arguments" 
errors).

However, the problematic imports appear only in two files, neither of which are 
installed in the final .debs, so the FTBFS is only a problem in running the 
test suite. I was able to build a working package by simply disabling the tests 
in debian/rules:

override_dh_auto_test:
@echo "Tests disabled in debian/rules, see https://bugs.debian.org/1055575;

While disabling tests isn't the best option in the world, it does prevent 
autoremoval until the upstream issue is resolved.


Thanks for all your work!
  - Dean

Processed: bug 1058657 is forwarded to https://salsa.debian.org/apt-team/python-apt/-/merge_requests/90

2023-12-17 Thread Debian Bug Tracking System

Processing commands for cont...@bugs.debian.org:

> forwarded 1058657 
> https://salsa.debian.org/apt-team/python-apt/-/merge_requests/90
Bug #1058657 [python3-apt] python3-apt: undefined symbol: PyAptWarning
Set Bug forwarded-to-address to 
'https://salsa.debian.org/apt-team/python-apt/-/merge_requests/90'.
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
1058657: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1058657
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Processed: tagging 985184, notfound 1058895 in 1.4.46+ds1-1, found 1058895 in 1.4.47+ds1-1, tagging 1020161 ...

2023-12-17 Thread Debian Bug Tracking System

Processing commands for cont...@bugs.debian.org:

> tags 985184 + sid trixie
Bug #985184 [src:reminiscence] reminiscence: New upstream version is not 
licensed
Added tag(s) trixie and sid.
> notfound 1058895 1.4.46+ds1-1
Bug #1058895 [python3-sqlalchemy] python 3.12 slices are hashable, affects one 
area of Row for 1.4 only
No longer marked as found in versions sqlalchemy/1.4.46+ds1-1.
> found 1058895 1.4.47+ds1-1
Bug #1058895 [python3-sqlalchemy] python 3.12 slices are hashable, affects one 
area of Row for 1.4 only
Marked as found in versions sqlalchemy/1.4.47+ds1-1.
> tags 1020161 + experimental
Bug #1020161 [src:golang-golang-x-net] golang-golang-x-net: FTBFS in bullseye 
(text offset 32797 is too large, or nodeBitsTextOffset is too small)
Added tag(s) experimental.
> tags 1058265 + experimental
Bug #1058265 [src:sqlalchemy] python-flask-marshmallow: FTBFS: dh_auto_test: 
error: pybuild --test --test-pytest -i python{version} -p "3.12 3.11" returned 
exit code 13
Added tag(s) experimental.
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
1020161: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1020161
1058265: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1058265
1058895: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1058895
985184: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=985184
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Processed: retitle 985184 to reminiscence: New upstream version is not licensed

2023-12-17 Thread Debian Bug Tracking System

Processing commands for cont...@bugs.debian.org:

> retitle 985184 reminiscence: New upstream version is not licensed
Bug #985184 [src:reminiscence] reminiscence: New upstream version available 
with SDL2 support
Changed Bug title to 'reminiscence: New upstream version is not licensed' from 
'reminiscence: New upstream version available with SDL2 support'.
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
985184: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=985184
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Processed: patch

2023-12-17 Thread Debian Bug Tracking System

Processing control commands:

> tags -1 +patch
Bug #1058657 [python3-apt] python3-apt: undefined symbol: PyAptWarning
Added tag(s) patch.

-- 
1058657: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1058657
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#1058657: patch

2023-12-17 Thread M. Zhou

Control: tags -1 +patch

https://salsa.debian.org/apt-team/python-apt/-/merge_requests/90

Bug#1057938: marked as done (python-duniterpy: FTBFS: RuntimeError: The Poetry configuration is invalid)

2023-12-17 Thread Debian Bug Tracking System

Your message dated Mon, 18 Dec 2023 00:21:26 +
with message-id 
and subject line Bug#1057938: fixed in python-duniterpy 1.1.1-3
has caused the Debian Bug report #1057938,
regarding python-duniterpy: FTBFS: RuntimeError: The Poetry configuration is 
invalid
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.)


-- 
1057938: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1057938
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---

Package: src:python-duniterpy
Version: 1.1.1-2
Severity: serious
Tags: ftbfs

Dear maintainer:

During a rebuild of all packages in unstable, your package failed to build:


[...]
 debian/rules build
dh build --buildsystem=pybuild --with=sphinxdoc
   dh_update_autotools_config -O--buildsystem=pybuild
   dh_autoreconf -O--buildsystem=pybuild
   dh_auto_configure -O--buildsystem=pybuild
   dh_auto_build -O--buildsystem=pybuild
I: pybuild plugin_pyproject:110: Building wheel for python3.11 with "build" 
module
I: pybuild base:310: python3.11 -m build --skip-dependency-check --no-isolation --wheel 
--outdir /<>/.pybuild/cpython3_3.11
* Building wheel...
Traceback (most recent call last):
  File "/usr/lib/python3/dist-packages/pyproject_hooks/_in_process/_in_process.py", 
line 353, in 
main()
  File 
"/usr/lib/python3/dist-packages/pyproject_hooks/_in_process/_in_process.py", 
line 335, in main
json_out['return_val'] = hook(**hook_input['kwargs'])
 
  File 
"/usr/lib/python3/dist-packages/pyproject_hooks/_in_process/_in_process.py", 
line 251, in build_wheel
return _build_backend().build_wheel(wheel_directory, config_settings,
   ^^
  File "/usr/lib/python3/dist-packages/poetry/core/masonry/api.py", line 55, in 
build_wheel
poetry = Factory().create_poetry(Path(".").resolve(), with_groups=False)
 ^^^
  File "/usr/lib/python3/dist-packages/poetry/core/factory.py", line 58, in 
create_poetry
raise RuntimeError("The Poetry configuration is invalid:\n" + message)
RuntimeError: The Poetry configuration is invalid:
  - data.homepage must be uri


ERROR Backend subprocess exited when trying to invoke build_wheel
E: pybuild pybuild:395: build: plugin pyproject failed with: exit code=1: python3.11 -m 
build --skip-dependency-check --no-isolation --wheel --outdir 
/<>/.pybuild/cpython3_3.11
dh_auto_build: error: pybuild --build -i python{version} -p 3.11 returned exit 
code 13
make: *** [debian/rules:13: build] Error 25
dpkg-buildpackage: error: debian/rules build subprocess returned exit status 2


The above is just how the build ends and not necessarily the most relevant part.
If required, the full build log is available here:

https://people.debian.org/~sanvila/build-logs/202312/

About the archive rebuild: The build was made using virtual machines
from AWS, with enough memory, enough disk, and either one or two
CPUs, using a reduced chroot with only build-essential packages.

If you could not reproduce the bug please contact me privately, as I
am willing to provide ssh access to a virtual machine where the bug is
fully reproducible.

If this is really a bug in one of the build-depends, please use
reassign and affects, so that this is still visible in the BTS web
page for this package.

Thanks.
--- End Message ---
--- Begin Message ---
Source: python-duniterpy
Source-Version: 1.1.1-3
Done: Bastian Germann 

We believe that the bug you reported is fixed in the latest version of
python-duniterpy, 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 1057...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Bastian Germann  (supplier of updated python-duniterpy package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Mon, 18 Dec 2023 00:42:33 +0100
Source: python-duniterpy
Architecture: source
Version: 1.1.1-3
Distribution: unstable

Processed: bug 1055723 is forwarded to https://github.com/sonofeft/RocketCEA/issues/37

2023-12-17 Thread Debian Bug Tracking System

Processing commands for cont...@bugs.debian.org:

> forwarded 1055723 https://github.com/sonofeft/RocketCEA/issues/37
Bug #1055723 [src:rocketcea] rocketcea ftbfs with Python 3.12
Set Bug forwarded-to-address to 
'https://github.com/sonofeft/RocketCEA/issues/37'.
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
1055723: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1055723
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Processed: reminiscence not anymore licensed

2023-12-17 Thread Debian Bug Tracking System

Processing control commands:

> severity -1 serious
Bug #985184 [src:reminiscence] reminiscence: New upstream version available 
with SDL2 support
Severity set to 'serious' from 'wishlist'

-- 
985184: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=985184
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Processed: Re: Bug#1057602: scm: FTBFS: error: invalid use of incomplete typedef ‘WINDOW’ {aka ‘struct _win_st’}

2023-12-17 Thread Debian Bug Tracking System

Processing control commands:

> tags -1 + patch
Bug #1057602 [src:scm] scm: FTBFS: error: invalid use of incomplete typedef 
‘WINDOW’ {aka ‘struct _win_st’}
Added tag(s) patch.

-- 
1057602: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1057602
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#1057602: scm: FTBFS: error: invalid use of incomplete typedef ‘WINDOW’ {aka ‘struct _win_st’}

2023-12-17 Thread Sven Joachim

Control: tags -1 + patch

On 2023-12-05 23:11 +0100, Santiago Vila wrote:

> Package: src:scm
> Version: 5f3-4
> Severity: serious
> Tags: ftbfs
>
> Dear maintainer:
>
> During a rebuild of all packages in unstable, your package failed to build:
> [...]
>
> The above is just how the build ends and not necessarily the most relevant 
> part.

Indeed, the actual error causing the FTBFS was missing.

> If required, the full build log is available here:
>
> https://people.debian.org/~sanvila/build-logs/202312/

The only fatal errors are these two:

,
| crs.c: In function ‘owidth’:
| crs.c:253:43: error: invalid use of incomplete typedef ‘WINDOW’ {aka ‘struct 
_win_st’}
|   253 | if (WINP(arg)) return MAKINUM(WIN(arg)->_maxx+1);
|   |   ^~
| scmfig.h:556:24: note: in definition of macro ‘MAKINUM’
|   556 | # define MAKINUM(x) (((x)<<2)+2L)
|   |^
| crs.c: In function ‘oheight’:
| crs.c:264:43: error: invalid use of incomplete typedef ‘WINDOW’ {aka ‘struct 
_win_st’}
|   264 | if (WINP(arg)) return MAKINUM(WIN(arg)->_maxy+1);
|   |   ^~
`

The attached patch fixes them and lets the package build, but I have
not tested if it actually works.

Cheers,
   Sven

Description: Fix build with opaque ncurses
 Since ncurses patchlevel 20231021 the WINDOW structure is opaque, its
 members cannot be addressed directly.  Use the functions ncurses
 provides for this purpose instead.
Author: Sven Joachim 
Bug-Debian: https://bugs.debian.org/1057602

--- scm-5f3.orig/crs.c
+++ scm-5f3/crs.c
@@ -250,7 +250,7 @@ SCM owidth(arg)
   if (UNBNDP(arg)) arg = cur_outp;
   ASRTER(NIMP(arg) && OPOUTPORTP(arg), arg, ARG1, s_owidth);
   if (NIMP(*loc_stdscr)) {
-if (WINP(arg)) return MAKINUM(WIN(arg)->_maxx+1);
+if (WINP(arg)) return MAKINUM(getmaxx(WIN(arg)));
 else return MAKINUM(COLS);
   }
   return MAKINUM(80);
@@ -261,7 +261,7 @@ SCM oheight(arg)
   if (UNBNDP(arg)) arg = cur_outp;
   ASRTER(NIMP(arg) && OPOUTPORTP(arg), arg, ARG1, s_owidth);
   if (NIMP(*loc_stdscr))
-if (WINP(arg)) return MAKINUM(WIN(arg)->_maxy+1);
+if (WINP(arg)) return MAKINUM(getmaxy(WIN(arg)));
 else return MAKINUM(LINES);
   return MAKINUM(24);
 }

Bug#1058895: python 3.12 slices are hashable, affects one area of Row for 1.4 only

2023-12-17 Thread Thomas Goirand

Package: python3-sqlalchemy
Version: 1.4.46+ds1-1
Severity: serious

Hi,

SQLAlchemy 1.4.47+ds1-1 in unstable is affected by this upstream bug:
https://github.com/sqlalchemy/sqlalchemy/issues/9819

Latest upstream release for 1.4.x (ie: 1.4.50). I tried building it locally,
and rebuild affected packages (for OpenStack), and this fixes these bugs (or
at least, it's part of solving these bugs as there are also other issues
unrelated):

https://bugs.debian.org/1058183 (barbican)
https://bugs.debian.org/1058123 (neutron-vpnaas) (FTBFS reported fixed by 
eventlet, but package affected by this bug)
https://bugs.debian.org/1058219 (senlin)
https://bugs.debian.org/1058233 (sahara)
https://bugs.debian.org/1058531 (heat) (some other failures, but also affected)

There's probably more (I didn't attempt to rebuild all affected packages yet),
but these are 5 examples of packages that FTBFS because of this problem.

It'd be nice if we could have the patch in Unstable with this series 1.4.x
before uploading 2.x, so that I have a chance to fix all Python 3.12 bugs and
not mix SQLA 2.x and Py 3.12 problems.

Cheers,

Thomas Goirand (zigo)

Processed: python-numpy-groupies: FTBFS: AttributeError: module 'configparser' has no attribute 'SafeConfigParser'. Did you mean: 'RawConfigParser'?

2023-12-17 Thread Debian Bug Tracking System

Processing control commands:

> tags -1 pending
Bug #1058133 [src:python-numpy-groupies] python-numpy-groupies: FTBFS: 
AttributeError: module 'configparser' has no attribute 'SafeConfigParser'. Did 
you mean: 'RawConfigParser'?
Added tag(s) pending.

-- 
1058133: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1058133
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#1058133: python-numpy-groupies: FTBFS: AttributeError: module 'configparser' has no attribute 'SafeConfigParser'. Did you mean: 'RawConfigParser'?

2023-12-17 Thread Sebastiaan Couwenberg


Control: tags -1 pending

This is fixed in the most recent upstream release, which unfortunately 
FTBFS with python3.12 due to test failures.


Kind Regards,

Bas

--
 GPG Key ID: 4096R/6750F10AE88D4AF1
Fingerprint: 8182 DE41 7056 408D 6146  50D1 6750 F10A E88D 4AF1

Processed: reopening 1058096

2023-12-17 Thread Debian Bug Tracking System

Processing commands for cont...@bugs.debian.org:

> reopen 1058096
Bug #1058096 {Done: Stefano Rivera } [src:python3-antlr4] 
python3-antlr4: FTBFS: AttributeError: 'TestIntervalSet' object has no 
attribute 'assertEquals'. Did you mean: 'assertEqual'?
'reopen' may be inappropriate when a bug has been closed with a version;
all fixed versions will be cleared, and you may need to re-add them.
Bug reopened
No longer marked as fixed in versions xonsh/0.14.3+dfsg-1.
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
1058096: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1058096
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Processed: 1025300 is grave

2023-12-17 Thread Debian Bug Tracking System

Processing commands for cont...@bugs.debian.org:

> severity 1025300 grave
Bug #1025300 [octocatalog-diff] octocatalog-diff crashes when the diff changes 
existing resources
Severity set to 'grave' from 'important'
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
1025300: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1025300
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#1058678: blt: disable jpeg support

2023-12-17 Thread Helmut Grohne

On Fri, Dec 15, 2023 at 01:43:12PM +0200, Adrian Bunk wrote:
> The src:python3.x packages build idle-python3.x packages.
> IDLE is an IDE for Python.[1]
> 
> The idle-python3.x packages depend on python3-tk, which depends on blt.

The idle-python3.x package is called python3.x-full. It happens to issue
a runtime dependency on python3.x-tk which is provided from python3-tk
which is built from python3-stdlib-extensions. Since idle is otherwise
implemented in Python, one doesn't actually need tk to perform the
install step for idle in the Python build.

> There is a certain weirdness in Python shipping an IDE that is based
> on Tcl/Tk, but that's an upstream issue.

...

> The tk-dev/blt-dev build dependencies in src:python3.x:
> - might be remnants from the times when python3-tk was built there, or

This definitely is true in some sense.

> - might be test-only, or

I guess this is also true.

> - might be workaroundable with a noidle build profile

Given your pointer at pkg-config, I now performed another build
comparison:
 * Add uuid-dev and pkg-config to Build-Depends.
 * Drop tk-dev and blt-dev from Build-Depends (in one of two builds).
 * Fix the build path.
 * Disable testing and profile guided optimization
   (DEB_BUILD_OPTIONS="nocheck nopgo").

The differences reduce significantly. I can no longer spot differences
in the filenames. The sysconfigdata changes and around tkinter even
though no tkinter module is installed into any package. LTO seems to
still shuffle things around quite a bit. Diffing Python binary builds is
hard.

Helmut

Bug#1058890: linux-image-6.1.0-16-amd64 breaks suspend

2023-12-17 Thread Dr . André Desgualdo Pereira

Package: src:linux
Version: 6.1.67-1
Severity: grave
Justification: renders package unusable

Dear Maintainer,

*** Reporter, please consider answering these questions, where appropriate ***

   * What led up to the situation?
   Updating the kernel
   * What exactly did you do (or not do) that was effective (or
 ineffective)?
   Booting from old kernel
   * What was the outcome of this action?
   Notebook can't wake up from suspend when using noveau driver, but worse yet 
the xserver doesn't even start when using Nvidia proprietary (error message 
saying no display was found)
   * What outcome did you expect instead?
   I expect updating the kernel doesn't break functionality.

*** End of the template - remove these template lines ***


-- Package-specific info:
** Version:
Linux version 6.1.0-16-amd64 (debian-ker...@lists.debian.org) (gcc-12 (Debian 
12.2.0-14) 12.2.0, GNU ld (GNU Binutils for Debian) 2.40) #1 SMP 
PREEMPT_DYNAMIC Debian 6.1.67-1 (2023-12-12)

** Command line:
BOOT_IMAGE=/boot/vmlinuz-6.1.0-16-amd64 
root=UUID=50906476-3c38-4fac-ab46-38d8ca6b9dd5 ro acpi_backlight=video 
nowatchdog libata.allow_tpm=1

** Not tainted

** Kernel log:
[7.330870] sd 0:0:0:0: Attached scsi generic sg0 type 0
[7.331146] sr 2:0:0:0: Attached scsi generic sg1 type 5
[7.356487] input: Lid Switch as 
/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0C0D:00/input/input11
[7.392564] ACPI: button: Lid Switch [LID0]
[7.393013] ACPI: AC: AC Adapter [ADP0] (on-line)
[7.403757] input: Sleep Button as 
/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0C0E:00/input/input12
[7.421153] ACPI: button: Sleep Button [SLPB]
[7.425107] input: Power Button as 
/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0C0C:00/input/input13
[7.425323] ACPI: button: Power Button [PWRB]
[7.425503] input: Power Button as 
/devices/LNXSYSTM:00/LNXPWRBN:00/input/input14
[7.430812] ACPI: button: Power Button [PWRF]
[7.452498] at24 0-0050: supply vcc not found, using dummy regulator
[7.453934] at24 0-0050: 256 byte spd EEPROM, read-only
[7.454744] at24 0-0051: supply vcc not found, using dummy regulator
[7.456352] at24 0-0051: 256 byte spd EEPROM, read-only
[7.457463] at24 0-0053: supply vcc not found, using dummy regulator
[7.474495] at24 0-0053: 256 byte spd EEPROM, read-only
[7.508907] input: PC Speaker as /devices/platform/pcspkr/input/input15
[7.511009] iTCO_vendor_support: vendor-support=0
[7.526518] mc: Linux media interface: v0.10
[7.528097] iTCO_wdt iTCO_wdt.1.auto: Found a Cougar Point TCO device 
(Version=2, TCOBASE=0x0460)
[7.528576] iTCO_wdt iTCO_wdt.1.auto: initialized. heartbeat=30 sec 
(nowayout=0)
[7.548311] Adding 3964924k swap on /dev/sda6.  Priority:-2 extents:1 
across:3964924k SSFS
[7.611599] cfg80211: Loading compiled-in X.509 certificates for regulatory 
database
[7.612026] cfg80211: Loaded X.509 cert 'b...@debian.org: 
577e021cb980e0e820821ba7b54b4961b8b4fadf'
[7.612427] cfg80211: Loaded X.509 cert 'romain.per...@gmail.com: 
3abbc6ec146e09d1b6016ab9d6cf71dd233f0328'
[7.612823] cfg80211: Loaded X.509 cert 'sforshee: 00b28ddf47aef9cea7'
[7.613701] platform regulatory.0: firmware: direct-loading firmware 
regulatory.db
[7.613950] platform regulatory.0: firmware: direct-loading firmware 
regulatory.db.p7s
[7.631031] random: crng init done
[7.678991] videodev: Linux video capture interface: v2.00
[7.684269] RAPL PMU: API unit is 2^-32 Joules, 2 fixed counters, 163840 ms 
ovfl timer
[7.684382] RAPL PMU: hw unit of domain pp0-core 2^-16 Joules
[7.684468] RAPL PMU: hw unit of domain package 2^-16 Joules
[7.684498] Intel(R) Wireless WiFi driver for Linux
[7.684930] iwlwifi :04:00.0: can't disable ASPM; OS doesn't have ASPM 
control
[7.688010] cryptd: max_cpu_qlen set to 1000
[7.700936] iwlwifi :04:00.0: firmware: direct-loading firmware 
iwlwifi-6000-4.ucode
[7.701178] iwlwifi :04:00.0: loaded firmware version 9.221.4.1 build 
25532 6000-4.ucode op_mode iwldvm
[7.708582] AVX version of gcm_enc/dec engaged.
[7.708721] AES CTR mode by8 optimization enabled
[7.725197] usb 3-1.6: Found UVC 1.00 device BisonCam, NB Pro (5986:0308)
[7.729530] snd_hda_intel :01:00.1: Disabling MSI
[7.729620] snd_hda_intel :01:00.1: Handle vga_switcheroo audio client
[7.750030] input: BisonCam, NB Pro: BisonCam, NB  as 
/devices/pci:00/:00:1d.0/usb3/3-1/3-1.6/3-1.6:1.0/input/input17
[7.750246] usbcore: registered new interface driver uvcvideo
[7.759394] input: HDA NVidia HDMI/DP,pcm=3 as 
/devices/pci:00/:00:01.0/:01:00.1/sound/card1/input16
[7.759606] input: HDA NVidia HDMI/DP,pcm=7 as 
/devices/pci:00/:00:01.0/:01:00.1/sound/card1/input18
[7.759786] input: HDA NVidia HDMI/DP,pcm=8 as 
/devices/pci:00/:00:01.0/:01:00.1/sound/card1/input19
[7.759963] input: HDA NVidia HDMI/DP,pcm=9 as

Processed: fix tags

2023-12-17 Thread Debian Bug Tracking System

Processing commands for cont...@bugs.debian.org:

> tag 1053843 = trixie sid
Bug #1053843 [src:user-mode-linux] src:user-mode-linux: unsatisfied build 
dependency in testing: linux-source-6.4
Added tag(s) trixie; removed tag(s) bookworm.
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
1053843: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1053843
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#1058889: src:openjdk-22: fails to migrate to testing for too long: FTBFS on armhf

2023-12-17 Thread Paul Gevers


Source: openjdk-22
Version: 22~22ea-1
Severity: serious
Control: close -1 22~25ea-1
Tags: sid trixie ftbfs
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:openjdk-22 has been trying to migrate for 
31 days [2]. Hence, I am filing this bug. The version in unstable failed 
to build on armhf.


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=openjdk-22



OpenPGP_signature.asc
Description: OpenPGP digital signature

Processed: src:openjdk-22: fails to migrate to testing for too long: FTBFS on armhf

2023-12-17 Thread Debian Bug Tracking System

Processing control commands:

> close -1 22~25ea-1
Bug #1058889 [src:openjdk-22] src:openjdk-22: fails to migrate to testing for 
too long: FTBFS on armhf
Marked as fixed in versions openjdk-22/22~25ea-1.
Bug #1058889 [src:openjdk-22] src:openjdk-22: fails to migrate to testing for 
too long: FTBFS on armhf
Marked Bug as done

-- 
1058889: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1058889
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#1058888: pyferret FTBSF on several architectures: dh_install: error: missing files, aborting

2023-12-17 Thread Adrian Bunk

Source: pyferret
Version: 7.6.5-5
Severity: serious
Tags: ftbfs

https://buildd.debian.org/status/logs.php?pkg=pyferret=7.6.5-5

...
   dh_install -a
dh_install: warning: Cannot find (any matches for) "debian/tmp/ext_func/pylibs" 
(tried in ., debian/tmp)

dh_install: warning: python3-ferret missing files: debian/tmp/ext_func/pylibs
install -m0755 -d debian/python3-ferret//usr/bin
cp --reflink=auto -a ./debian/pyferret3 debian/python3-ferret//usr/bin/
install -m0755 -d debian/python3-ferret//usr/lib/python3/dist-packages
cp --reflink=auto -a 
./debian/tmp/lib/python3.11/libpyferret.cpython-311-powerpc64le-linux-gnu.so 
./debian/tmp/lib/python3.12/libpyferret.cpython-312-powerpc64le-linux-gnu.so 
./install/local/lib/python3.11/dist-packages/__pycache__ 
./install/local/lib/python3.11/dist-packages/gcircle-7.65-py3.11.egg-info 
./install/local/lib/python3.11/dist-packages/gcircle.py 
./install/local/lib/python3.11/dist-packages/pipedviewer 
./install/local/lib/python3.11/dist-packages/pipedviewer-7.65-py3.11.egg-info 
./install/local/lib/python3.11/dist-packages/pyferret 
./install/local/lib/python3.11/dist-packages/pyferret-7.65-py3.11.egg-info 
debian/python3-ferret//usr/lib/python3/dist-packages/
install -m0755 -d 
debian/python3-ferret//usr/share/bash-completion/completions/
cp --reflink=auto -a ./debian/bash_completion.d/pyferret3 
debian/python3-ferret//usr/share/bash-completion/completions//
dh_install: error: missing files, aborting
make: *** [debian/rules:8: binary-arch] Error 25

Bug#1058096: marked as done (python3-antlr4: FTBFS: AttributeError: 'TestIntervalSet' object has no attribute 'assertEquals'. Did you mean: 'assertEqual'?)

2023-12-17 Thread Debian Bug Tracking System

Your message dated Sun, 17 Dec 2023 18:09:46 +
with message-id 
and subject line Bug#1058096: fixed in xonsh 0.14.3+dfsg-1
has caused the Debian Bug report #1058096,
regarding python3-antlr4: FTBFS: AttributeError: 'TestIntervalSet' object has 
no attribute 'assertEquals'. Did you mean: 'assertEqual'?
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.)


-- 
1058096: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1058096
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: python3-antlr4
Version: 4.9.1-1
Severity: serious
Justification: FTBFS
Tags: trixie sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20231212 ftbfs-trixie

Hi,

During a rebuild of all packages in sid, your package failed to build
on amd64.


Relevant part (hopefully):
>  debian/rules binary
> dh binary --with python3 --buildsystem=pybuild
>dh_update_autotools_config -O--buildsystem=pybuild
>dh_autoreconf -O--buildsystem=pybuild
>dh_auto_configure -O--buildsystem=pybuild
> I: pybuild base:310: python3.12 setup.py config 
> running config
> I: pybuild base:310: python3.11 setup.py config 
> running config
>dh_auto_build -O--buildsystem=pybuild
> I: pybuild base:310: /usr/bin/python3.12 setup.py build 
> running build
> running build_py
> creating 
> /<>/.pybuild/cpython3_3.12_antlr4-python3-runtime/build/antlr4
> copying src/antlr4/BufferedTokenStream.py -> 
> /<>/.pybuild/cpython3_3.12_antlr4-python3-runtime/build/antlr4
> copying src/antlr4/IntervalSet.py -> 
> /<>/.pybuild/cpython3_3.12_antlr4-python3-runtime/build/antlr4
> copying src/antlr4/Recognizer.py -> 
> /<>/.pybuild/cpython3_3.12_antlr4-python3-runtime/build/antlr4
> copying src/antlr4/__init__.py -> 
> /<>/.pybuild/cpython3_3.12_antlr4-python3-runtime/build/antlr4
> copying src/antlr4/LL1Analyzer.py -> 
> /<>/.pybuild/cpython3_3.12_antlr4-python3-runtime/build/antlr4
> copying src/antlr4/Token.py -> 
> /<>/.pybuild/cpython3_3.12_antlr4-python3-runtime/build/antlr4
> copying src/antlr4/ListTokenSource.py -> 
> /<>/.pybuild/cpython3_3.12_antlr4-python3-runtime/build/antlr4
> copying src/antlr4/ParserRuleContext.py -> 
> /<>/.pybuild/cpython3_3.12_antlr4-python3-runtime/build/antlr4
> copying src/antlr4/StdinStream.py -> 
> /<>/.pybuild/cpython3_3.12_antlr4-python3-runtime/build/antlr4
> copying src/antlr4/FileStream.py -> 
> /<>/.pybuild/cpython3_3.12_antlr4-python3-runtime/build/antlr4
> copying src/antlr4/Lexer.py -> 
> /<>/.pybuild/cpython3_3.12_antlr4-python3-runtime/build/antlr4
> copying src/antlr4/ParserInterpreter.py -> 
> /<>/.pybuild/cpython3_3.12_antlr4-python3-runtime/build/antlr4
> copying src/antlr4/CommonTokenStream.py -> 
> /<>/.pybuild/cpython3_3.12_antlr4-python3-runtime/build/antlr4
> copying src/antlr4/TokenStreamRewriter.py -> 
> /<>/.pybuild/cpython3_3.12_antlr4-python3-runtime/build/antlr4
> copying src/antlr4/RuleContext.py -> 
> /<>/.pybuild/cpython3_3.12_antlr4-python3-runtime/build/antlr4
> copying src/antlr4/PredictionContext.py -> 
> /<>/.pybuild/cpython3_3.12_antlr4-python3-runtime/build/antlr4
> copying src/antlr4/Parser.py -> 
> /<>/.pybuild/cpython3_3.12_antlr4-python3-runtime/build/antlr4
> copying src/antlr4/InputStream.py -> 
> /<>/.pybuild/cpython3_3.12_antlr4-python3-runtime/build/antlr4
> copying src/antlr4/Utils.py -> 
> /<>/.pybuild/cpython3_3.12_antlr4-python3-runtime/build/antlr4
> copying src/antlr4/CommonTokenFactory.py -> 
> /<>/.pybuild/cpython3_3.12_antlr4-python3-runtime/build/antlr4
> creating 
> /<>/.pybuild/cpython3_3.12_antlr4-python3-runtime/build/antlr4/atn
> copying src/antlr4/atn/ATNConfigSet.py -> 
> /<>/.pybuild/cpython3_3.12_antlr4-python3-runtime/build/antlr4/atn
> copying src/antlr4/atn/ATNDeserializationOptions.py -> 
> /<>/.pybuild/cpython3_3.12_antlr4-python3-runtime/build/antlr4/atn
> copying src/antlr4/atn/__init__.py -> 
> /<>/.pybuild/cpython3_3.12_antlr4-python3-runtime/build/antlr4/atn
> copying src/antlr4/atn/SemanticContext.py -> 
> /<>/.pybuild/cpython3_3.12_antlr4-python3-runtime/build/antlr4/atn
> copying src/antlr4/atn/ATNConfig.py -> 
> /<>/.pybuild/cpython3_3.12_antlr4-python3-runtime/build/antlr4/atn
> copying src/antlr4/atn/ATNDeserializer.py -> 
> /<>/.pybuild/cpython3_3.12_antlr4-python3-runtime/build/antlr4/atn
> copying src/antlr4/atn/ATNState.py -> 
> /<>/.pybuild/cpython3_3.12_antlr4-python3-runtime/build/antlr4/atn
> copying src/antlr4/atn/LexerAction.py -> 
> /<>/.pybuild/cpython3_3.12_antlr4-python3-runtime/build/antlr4/atn
> copying src/antlr4/atn/LexerActionExecutor.py -> 
> /<>/.pybuild/cpython3_3.12_antlr4-python3-runtime/build/antlr4/atn
> copying

Bug#1057596: marked as done (xonsh: FTBFS: TypeError: object of type 'LazyObject' has no len())

2023-12-17 Thread Debian Bug Tracking System

Your message dated Sun, 17 Dec 2023 14:03:09 -0400
with message-id <20231217180309.hfe6hdsmbhosh...@haydn.kardiogramm.net>
and subject line Closed in 0.14.3+dfsg-1
has caused the Debian Bug report #1057596,
regarding xonsh: FTBFS: TypeError: object of type 'LazyObject' has no len()
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.)


-- 
1057596: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1057596
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---

Package: src:xonsh
Version: 0.14.1+dfsg-1
Severity: serious
Tags: ftbfs

Dear maintainer:

During a rebuild of all packages in unstable, your package failed to build:


[...]
 debian/rules binary
dh binary --with python3,sphinxdoc --buildsystem=pybuild
   dh_update_autotools_config -O--buildsystem=pybuild
   dh_autoreconf -O--buildsystem=pybuild
   dh_auto_configure -O--buildsystem=pybuild
   dh_auto_build -O--buildsystem=pybuild
I: pybuild plugin_pyproject:110: Building wheel for python3.11 with "build" 
module
I: pybuild base:310: python3.11 -m build --skip-dependency-check --no-isolation --wheel 
--outdir /<>/.pybuild/cpython3_3.11
* Building wheel...
   ╓██▄
  ╙██▀██╕
 ▐██4Φ█▀█▌
   ²██▄███▀██^██
 -███╩▀ " ╒▄█▀█
  ║██▀▀W╤▄▀ ▐║█╘ ╝█
 ▄m▀%Φ▀▀  ╝*",α█▓▄,▄▀Γ"▀╕
 "▀██¼" ▄═╦█╟║█▀ ╓ `^`   ,▄ ╢╕
  ,▀╫M█▐j╓╟▀ ╔▓▄█▀  '║ ╔╣║▌  ▀▄
   ▄m▀▀███╬█╝▀  █▀^  "ÜM  j▐╟╫╨▒   ╙▀≡═╤═m▀╗
   █æsæ╓  ╕, ,▄Ä   ▐'╕H   LU  ║║╠╫Å^2=⌐ █
▄æ%Å███╠█ª╙▄█▀  $1╙   ║║╟╫╩*T▄   ▌
   ╙╗%▄,╦██▌█▌█╢M ╕  M█═⌐ⁿ"^ ╫
 ╙╣▀@█░█▌╕╕   `  ▌║▐▐║█D═≈⌐¬ⁿ  s ║⌐
   ╙╬███▓║█` ▌╚ ╕   ╕▌║▐▐╣▌⌐*▒▒Dù`   ▐▌
╙╬██╨U█  ╟  $ ▌ ▌▌▐▐▐M█▄═≤⌐%   ╓⌐ ▌
 ║║█▄▌║ ╟ ▌ ▌M▐▐▐M█▀▒▒▒22,   ▐▌
  ███╙^▌║ ▌ ⌐M▐▐▐M█≤⌐⌐¬──▐M
  ║██ ▌╙   ╓   H║ ▌╒ M║▐▐M█"^"ⁿ  ║
   ██╕╙@▓   ╕  ▌║ H'  ║▐▐▐█══=.,,,   █
   ╙█▓╔╚╚█ ╠   ▌└╒ ▌▐ ╚║║║▀ⁿ -  ╓▌
╙█▌¼V╚▌   ▌  ╕ ▌ ║╒ ║ ▌▒╠█▀≤⌐   █
 ╙█▌╔█╚▌ ┘ M ▌║ ╫ UUM██J^^"▐▌
  ╙██╙█╙▌  ╕$j  ▐⌐▌ ▌║╝╟█Å%%%≈═█
   ╙╣█╣█^▌ ╠║▐  ║ ▌▐.DU██^[""ⁿ   -╒▌
 ▀█▄█`▌ ░M▀ ▌▐ Å£╝╝█╜%≈═╓""w   ⁿ⌐ █
  `▀▄▀`▌ ▌█▐⌐║▐UW╖██%≤═░*─=z ▄Γ
╙██╙▄▌█  ▌Å╛╣██╨%╤ƒⁿ=-` ▄┘
  █▌╢▓▌▌ W £6█╤,"ⁿ `   ▄≡▀▀▀
   █"█▌▌╟Å╓█╓█▀%`▄▀
   ╙▌██`▒U▓U█%╗* █
▌╫║ ▌ÅÅ║▀╛¬`  `"█
▌╫  ╫╟ █▄ ~╦%▒╥4^
▌▌  "M█ `▀╕ X╕"╗▄▀^
█▌   ╓M   ╙▀e▀▀^
╙██▄▄▀
  ^^

running bdist_wheel
running build
running build_py
Building lexer and parser tables.
WARNING: /<>/xonsh/parsers/v38.py:523: No documentation string 
specified in function 'p_yield_arg_testlist' (ignored)
WARNING: /<>/xonsh/parsers/base.py:534: Rule 'testlist_opt' 
defined, but not used
WARNING: There is 1 unused rule
WARNING: Symbol 'testlist_opt' is unreachable
Generating LALR tables
WARNING: 872 shift/reduce conflicts
WARNING: 351 reduce/reduce conflicts
WARNING: reduce/reduce conflict in state 21 resolved using rule (test_or_star_expr 
-> test)
WARNING: rejected rule (testlist -> test) in state 21
WARNING: reduce/reduce conflict in state 366 resolved using rule 
(test_or_star_expr -> test)
WARNING: rejected rule (testlist -> test) in state 366
WARNING: reduce/reduce conflict in state 394 resolved using rule (string_literal 
-> string_tok)
WARNING: rejected rule (subproc_arg_part -> string_tok) in state 394
WARNING: reduce/reduce conflict in state 820 resolved using rule (atom -> 
SEARCHPATH)
WARNING: rejected rule (subproc_atom -> SEARCHPATH) in state 820
WARNING: reduce/reduce conflict in state 821 resolved using rule 
(string_literal_list -> string_literal)
WARNING: rejected rule (subproc_atom -> string_literal) in state 821
WARNING: reduce/reduce conflict in state 822 resolved using rule (empty -> 
)
WARNING: rejected rule (subproc_arg_part ->

Bug#1058096: Processed: Bug#1058096 marked as pending in xonsh

2023-12-17 Thread stefanor

Hi Debian (2023.12.17_17:48:05_+)

Whoops, that was a typo, I was meaning to close 1057596.

Stefano

-- 
Stefano Rivera
  http://tumbleweed.org.za/
  +1 415 683 3272

Bug#1057942: ydpdict: FTBFS: invalid use of incomplete typedef ‘WINDOW’ {aka ‘struct _win_st’}

2023-12-17 Thread Sven Joachim

Control: tags -1 + patch

On 2023-12-10 20:19 +0100, Santiago Vila wrote:

> Package: src:ydpdict
> Version: 1.0.4-1
> Severity: serious
> Tags: ftbfs
>
> Dear maintainer:
>
> During a rebuild of all packages in unstable, your package failed to build:
>
> 
> [...]
> gcc -DHAVE_CONFIG_H -I. -I..   -Wdate-time -D_FORTIFY_SOURCE=2 -Wall -g -O2 
> -ffile-prefix-map=/<>=. -fstack-protector-strong 
> -fstack-clash-protection -Wformat -Werror=format-security -fcf-protection 
> -DHAVE_CONFIG_H   -DSYSCONFDIR=\"/etc\" -g -O2 
> -ffile-prefix-map=/<>=. -fstack-protector-strong 
> -fstack-clash-protection -Wformat -Werror=format-security -fcf-protection 
> -DHAVE_CONFIG_H -c -o ydpdict-ydpdict.o `test -f 'ydpdict.c' || echo 
> './'`ydpdict.c
> ydpdict.c: In function ‘check_size’:
> ydpdict.c:324:22: error: invalid use of incomplete typedef ‘WINDOW’ {aka 
> ‘struct _win_st’}
>   324 | newx = stdscr->_maxx + 1;
>   |  ^~
> ydpdict.c:325:22: error: invalid use of incomplete typedef ‘WINDOW’ {aka 
> ‘struct _win_st’}
>   325 | newy = stdscr->_maxy + 1;
>   |  ^~
> ydpdict.c: In function ‘main’:
> ydpdict.c:855:27: error: invalid use of incomplete typedef ‘WINDOW’ {aka 
> ‘struct _win_st’}
>   855 |  event.y > (window->_begy + correct1) && event.y < 
> (window->_begy + window->_maxy + correct2) &&\
>   |   ^~
> ydpdict.c:862:88: note: in expansion of macro ‘__MOUSE_IN’
>   862 | if (m_event.bstate & 
> BUTTON1_DOUBLE_CLICKED && __MOUSE_IN(window_def, m_event, -2, 1, -3, 2)) {
>   |   
>  ^~
> ydpdict.c:855:67: error: invalid use of incomplete typedef ‘WINDOW’ {aka 
> ‘struct _win_st’}
>   855 |  event.y > (window->_begy + correct1) && event.y < 
> (window->_begy + window->_maxy + correct2) &&\
>   |   ^~
> ydpdict.c:862:88: note: in expansion of macro ‘__MOUSE_IN’
>   862 | if (m_event.bstate & 
> BUTTON1_DOUBLE_CLICKED && __MOUSE_IN(window_def, m_event, -2, 1, -3, 2)) {
>   |   
>  ^~
> ydpdict.c:855:83: error: invalid use of incomplete typedef ‘WINDOW’ {aka 
> ‘struct _win_st’}
>   855 |  event.y > (window->_begy + correct1) && event.y < 
> (window->_begy + window->_maxy + correct2) &&\
>   |   
> ^~
> ydpdict.c:862:88: note: in expansion of macro ‘__MOUSE_IN’
>   862 | if (m_event.bstate & 
> BUTTON1_DOUBLE_CLICKED && __MOUSE_IN(window_def, m_event, -2, 1, -3, 2)) {
>   |   
>  ^~
> ydpdict.c:856:27: error: invalid use of incomplete typedef ‘WINDOW’ {aka 
> ‘struct _win_st’}
>   856 |  event.x > (window->_begx + correct3) && event.x < 
> (window->_begx + window->_maxx + correct4))
>   |   ^~
> ydpdict.c:862:88: note: in expansion of macro ‘__MOUSE_IN’
>   862 | if (m_event.bstate & 
> BUTTON1_DOUBLE_CLICKED && __MOUSE_IN(window_def, m_event, -2, 1, -3, 2)) {
>   |   
>  ^~
> ydpdict.c:856:67: error: invalid use of incomplete typedef ‘WINDOW’ {aka 
> ‘struct _win_st’}
>   856 |  event.x > (window->_begx + correct3) && event.x < 
> (window->_begx + window->_maxx + correct4))
>   |   ^~
> ydpdict.c:862:88: note: in expansion of macro ‘__MOUSE_IN’
>   862 | if (m_event.bstate & 
> BUTTON1_DOUBLE_CLICKED && __MOUSE_IN(window_def, m_event, -2, 1, -3, 2)) {
>   |   
>  ^~
> ydpdict.c:856:83: error: invalid use of incomplete typedef ‘WINDOW’ {aka 
> ‘struct _win_st’}
>   856 |  event.x > (window->_begx + correct3) && event.x < 
> (window->_begx + window->_maxx + correct4))
>   |   
> ^~
> ydpdict.c:862:88: note: in expansion of macro ‘__MOUSE_IN’
>   862 | if (m_event.bstate & 
> BUTTON1_DOUBLE_CLICKED && __MOUSE_IN(window_def, m_event, -2, 1, -3, 2)) {
>   |   
>  ^~
> ydpdict.c:887:104: error: invalid use of incomplete typedef ‘WINDOW’ {aka 
> ‘struct _win_st’}
>   887 |

Processed: Re: Bug#1057942: ydpdict: FTBFS: invalid use of incomplete typedef ‘WINDOW’ {aka ‘struct _win_st’}

2023-12-17 Thread Debian Bug Tracking System

Processing control commands:

> tags -1 + patch
Bug #1057942 [src:ydpdict] ydpdict: FTBFS: invalid use of incomplete typedef 
‘WINDOW’ {aka ‘struct _win_st’}
Added tag(s) patch.

-- 
1057942: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1057942
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Processed: Bug#1058096 marked as pending in xonsh

2023-12-17 Thread Debian Bug Tracking System

Processing control commands:

> tag -1 pending
Bug #1058096 [src:python3-antlr4] python3-antlr4: FTBFS: AttributeError: 
'TestIntervalSet' object has no attribute 'assertEquals'. Did you mean: 
'assertEqual'?
Added tag(s) pending.

-- 
1058096: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1058096
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#1058096: marked as pending in xonsh

2023-12-17 Thread Stefano Rivera

Control: tag -1 pending

Hello,

Bug #1058096 in xonsh reported by you has been fixed in the
Git repository and is awaiting an upload. You can see the commit
message below and you can check the diff of the fix at:

https://salsa.debian.org/python-team/packages/xonsh/-/commit/5b83ef4462292c31069c63514d4d7f86ebe85283


Patch: Support Sphinx >= 5. (Closes: #1058096)


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/1058096

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

2023-12-17 Thread Debian Bug Tracking System

Your message dated Sun, 17 Dec 2023 17:42:23 +
with message-id 
and subject line Bug#1056515: fixed in pythran 0.14.0+ds-3
has caused the Debian Bug report #1056515,
regarding pythran's autopkg tests fail with Python 3.12
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
1056515: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1056515
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---

Package: src:pythran
Version: 0.11.0+ds-8
Severity: important
Tags: sid trixie
User: debian-pyt...@lists.debian.org
Usertags: python3.12

pythran's autopkg tests fail with Python 3.12:

[...]
656s autopkgtest [19:07:52]: test pythran-blas: [---
656s update-alternatives: using 
/usr/lib/x86_64-linux-gnu/blas/libblas.so.3 to provide 
/usr/lib/x86_64-linux-gnu/libblas.so.3 (libblas.so.3-x86_64-linux-gnu) 
in manual mode

656s Running testsuite with python3.12 using CXXFLAGS=-DUSE_XSIMD
657s = test session starts 
==

657s platform linux -- Python 3.12.0+, pytest-7.4.3, pluggy-1.3.0
657s rootdir: /tmp/autopkgtest.0nZXc2/autopkgtest_tmp/pythran_tests
657s collected 0 items / 1 error
657s
657s  ERRORS 

657s  ERROR collecting test_base.py 
_
657s ImportError while importing test module 
'/tmp/autopkgtest.0nZXc2/autopkgtest_tmp/pythran_tests/test_base.py'.

657s Hint: make sure your test modules/packages have valid Python names.
657s Traceback:
657s /usr/lib/python3.12/importlib/__init__.py:90: in import_module
657s return _bootstrap._gcd_import(name[level:], package, level)
657s __init__.py:29: in 
657s from pythran import compile_pythrancode, spec_parser, 
load_specfile, frontend

657s /usr/lib/python3/dist-packages/pythran/__init__.py:127: in __getattr__
657s import pythran.toolchain
657s /usr/lib/python3/dist-packages/pythran/toolchain.py:11: in 
657s from pythran.dist import PythranExtension, PythranBuildExt
657s /usr/lib/python3/dist-packages/pythran/dist.py:16: in 
657s from distutils.command.build_ext import build_ext as LegacyBuildExt
657s E   ModuleNotFoundError: No module named 'distutils'
657s === short test summary info 


657s ERROR test_base.py
657s  Interrupted: 1 error during collection 

657s === 1 error in 0.41s 
===
--- End Message ---
--- Begin Message ---
Source: pythran
Source-Version: 0.14.0+ds-3
Done: Drew Parsons 

We believe that the bug you reported is fixed in the latest version of
pythran, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 1056...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Drew Parsons  (supplier of updated pythran 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, 17 Dec 2023 16:45:24 +0100
Source: pythran
Architecture: source
Version: 0.14.0+ds-3
Distribution: unstable
Urgency: medium
Maintainer: Debian Python Team 
Changed-By: Drew Parsons 
Closes: 1056515
Changes:
 pythran (0.14.0+ds-3) unstable; urgency=medium
 .
   * Team upload.
   * debian patch python_3.12_258ab9a.diff applies upstream
 commit 258ab9a to support Python 3.12. Closes: #1056515.
   * drop debian patch 0004-Enhance-atlas-auto-detection.patch.
 The ATLAS BLAS implementation is deprecated, and its patch
 interferes with application of the Python 3.12 patch.
Checksums-Sha1:
 08ed6f7852ae05d7598921e26d9cd1cfc0db01dd 2517 pythran_0.14.0+ds-3.dsc
 52e7a9994be46b2b48912f8cb1cefcbab5eb05b2 15604 
pythran_0.14.0+ds-3.debian.tar.xz
Checksums-Sha256:
 014948cdbd4760b2c9261ab29efc788924102190bb370a199619ac135eb091e4 2517 
pythran_0.14.0+ds-3.dsc
 b45c93eb8d10cbb2ac19c4851f07afa125a88bf61f3d6581d8325bc0793f4cb7 15604 
pythran_0.14.0+ds-3.debian.tar.xz
Files:
 54eb6d7e6f24ea5b096598a303c4cb97 2517 python optional pythran_0.14.0+ds-3.dsc
 58c7fe59197fe6f7dc2cc8c8d207fb40 15604 python optional 
pythran_0.14.0+ds-3.debian.tar.xz

-BEGIN

Bug#1056515: marked as pending in pythran

2023-12-17 Thread Drew Parsons

Control: tag -1 pending

Hello,

Bug #1056515 in pythran reported by you has been fixed in the
Git repository and is awaiting an upload. You can see the commit
message below and you can check the diff of the fix at:

https://salsa.debian.org/python-team/packages/pythran/-/commit/62d67370b0cabcc2e626f01a160d90824835076d


add debian patch python_3.12_258ab9a.diff

applies upstream commit 258ab9a to support Python 3.12.
https://github.com/serge-sans-paille/pythran/commit/258ab9aaf26172f669eab1bf2a346b5f65db3ac0

Closes: #1056515.


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/1056515

Processed: Bug#1056515 marked as pending in pythran

2023-12-17 Thread Debian Bug Tracking System

Processing control commands:

> tag -1 pending
Bug #1056515 [src:pythran] pythran's autopkg tests fail with Python 3.12
Added tag(s) pending.

-- 
1056515: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1056515
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Processed: linphone: diff for NMU version 5.2.0-4.1

2023-12-17 Thread Debian Bug Tracking System

Processing control commands:

> tags 1058849 + patch
Bug #1058849 [src:linphone] linphone FTBFS with zxing-cpp 2.2.1
Ignoring request to alter tags of bug #1058849 to the same tags previously set
> tags 1058849 + pending
Bug #1058849 [src:linphone] linphone FTBFS with zxing-cpp 2.2.1
Added tag(s) pending.

-- 
1058849: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1058849
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#1058849: linphone: diff for NMU version 5.2.0-4.1

2023-12-17 Thread Boyuan Yang

Control: tags 1058849 + patch
Control: tags 1058849 + pending

Dear maintainer,

I've prepared an NMU for linphone (versioned as 5.2.0-4.1) and
uploaded it to DELAYED/5. Please feel free to tell me if I
should delay it longer or cancel it.

Regards.

diff -Nru linphone-5.2.0/debian/changelog linphone-5.2.0/debian/changelog
--- linphone-5.2.0/debian/changelog 2023-07-29 16:10:37.0 -0400
+++ linphone-5.2.0/debian/changelog 2023-12-17 11:31:05.0 -0500
@@ -1,3 +1,12 @@
+linphone (5.2.0-4.1) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * debian/patches/use-cxx17-standard.patch: Build the whole project
+with C++17 instead of C++14 due to new requirement from zxing-cpp
+headers. (Closes: #1058849)
+
+ -- Boyuan Yang   Sun, 17 Dec 2023 11:31:05 -0500
+
 linphone (5.2.0-4) unstable; urgency=medium
 
   * Release to unstable.
diff -Nru linphone-5.2.0/debian/patches/series linphone-
5.2.0/debian/patches/series
--- linphone-5.2.0/debian/patches/series2023-07-29 16:10:37.0
-0400
+++ linphone-5.2.0/debian/patches/series2023-12-17 11:30:43.0
-0500
@@ -1,4 +1,3 @@
-#desktop-file-keywords
 fix-jsoncpp-include-path.patch
 fix-jsoncpp-linker-flag.patch
 ldap-hostname-override.patch
@@ -16,3 +15,4 @@
 fix-ldap-abandon.patch
 fix-L_STRING_TO_C-inlining-errors.patch
 bc-b52e8f62-build-with-gcc13.patch
+use-cxx17-standard.patch
diff -Nru linphone-5.2.0/debian/patches/use-cxx17-standard.patch linphone-
5.2.0/debian/patches/use-cxx17-standard.patch
--- linphone-5.2.0/debian/patches/use-cxx17-standard.patch  1969-12-31
19:00:00.0 -0500
+++ linphone-5.2.0/debian/patches/use-cxx17-standard.patch  2023-12-17
11:30:20.0 -0500
@@ -0,0 +1,25 @@
+From: Boyuan Yang 
+Date: Sun, 17 Dec 2023 11:29:16 -0500
+Subject: Use C++17 Standard
+
+New zxing-cpp header uses C++17 features. This requires building
+the project with C++17 instead of C++14.
+
+Bug-Debian: https://bugs.debian.org/1058849
+---
+ CMakeLists.txt | 2 +-
+ 1 file changed, 1 insertion(+), 1 deletion(-)
+
+diff --git a/CMakeLists.txt b/CMakeLists.txt
+index b3060af..c846dc7 100644
+--- a/CMakeLists.txt
 b/CMakeLists.txt
+@@ -93,7 +93,7 @@ cmake_dependent_option(ENABLE_QRCODE "Enable QRCode
support" YES "ENABLE_VIDEO"
+ # * DISABLE_BC_PACKAGE_SEARCH: skip find_package() for every BC package
(bctoolbox, ortp, etc.)
+ # * DISABLE_SOCI_PACKAGE_SEARCH: skip find_package() for Soci.
+ 
+-set(CMAKE_CXX_STANDARD 14)
++set(CMAKE_CXX_STANDARD 17)
+ set(CMAKE_CXX_EXTENSIONS NO)
+ 
+ if(NOT CMAKE_BUILD_TYPE)


signature.asc
Description: This is a digitally signed message part

Bug#1058354: marked as done (py-macaroon-bakery: FTBFS: dh_auto_test: error: pybuild --test -i python{version} -p "3.12 3.11" returned exit code 13)

2023-12-17 Thread Debian Bug Tracking System

Your message dated Sun, 17 Dec 2023 16:25:25 +
with message-id 
and subject line Bug#1058354: fixed in py-macaroon-bakery 1.3.4-1
has caused the Debian Bug report #1058354,
regarding py-macaroon-bakery: FTBFS: dh_auto_test: error: pybuild --test -i 
python{version} -p "3.12 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.)


-- 
1058354: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1058354
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: py-macaroon-bakery
Version: 1.3.1-5
Severity: serious
Justification: FTBFS
Tags: trixie sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20231212 ftbfs-trixie

Hi,

During a rebuild of all packages in sid, your package failed to build
on amd64.


Relevant part (hopefully):
>  debian/rules binary
> dh binary --with python3 --buildsystem=pybuild
>dh_update_autotools_config -O--buildsystem=pybuild
>dh_autoreconf -O--buildsystem=pybuild
>dh_auto_configure -O--buildsystem=pybuild
> I: pybuild base:310: python3.12 setup.py config 
> running config
> I: pybuild base:310: python3.11 setup.py config 
> running config
>dh_auto_build -O--buildsystem=pybuild
> I: pybuild base:310: /usr/bin/python3.12 setup.py build 
> running build
> running build_py
> creating 
> /<>/.pybuild/cpython3_3.12_macaroonbakery/build/macaroonbakery
> copying macaroonbakery/__init__.py -> 
> /<>/.pybuild/cpython3_3.12_macaroonbakery/build/macaroonbakery
> creating 
> /<>/.pybuild/cpython3_3.12_macaroonbakery/build/macaroonbakery/httpbakery
> copying macaroonbakery/httpbakery/_interactor.py -> 
> /<>/.pybuild/cpython3_3.12_macaroonbakery/build/macaroonbakery/httpbakery
> copying macaroonbakery/httpbakery/_keyring.py -> 
> /<>/.pybuild/cpython3_3.12_macaroonbakery/build/macaroonbakery/httpbakery
> copying macaroonbakery/httpbakery/__init__.py -> 
> /<>/.pybuild/cpython3_3.12_macaroonbakery/build/macaroonbakery/httpbakery
> copying macaroonbakery/httpbakery/_error.py -> 
> /<>/.pybuild/cpython3_3.12_macaroonbakery/build/macaroonbakery/httpbakery
> copying macaroonbakery/httpbakery/_discharge.py -> 
> /<>/.pybuild/cpython3_3.12_macaroonbakery/build/macaroonbakery/httpbakery
> copying macaroonbakery/httpbakery/_browser.py -> 
> /<>/.pybuild/cpython3_3.12_macaroonbakery/build/macaroonbakery/httpbakery
> copying macaroonbakery/httpbakery/_client.py -> 
> /<>/.pybuild/cpython3_3.12_macaroonbakery/build/macaroonbakery/httpbakery
> creating 
> /<>/.pybuild/cpython3_3.12_macaroonbakery/build/macaroonbakery/tests
> copying macaroonbakery/tests/__init__.py -> 
> /<>/.pybuild/cpython3_3.12_macaroonbakery/build/macaroonbakery/tests
> copying macaroonbakery/tests/test_time.py -> 
> /<>/.pybuild/cpython3_3.12_macaroonbakery/build/macaroonbakery/tests
> copying macaroonbakery/tests/test_bakery.py -> 
> /<>/.pybuild/cpython3_3.12_macaroonbakery/build/macaroonbakery/tests
> copying macaroonbakery/tests/test_client.py -> 
> /<>/.pybuild/cpython3_3.12_macaroonbakery/build/macaroonbakery/tests
> copying macaroonbakery/tests/test_codec.py -> 
> /<>/.pybuild/cpython3_3.12_macaroonbakery/build/macaroonbakery/tests
> copying macaroonbakery/tests/test_checker.py -> 
> /<>/.pybuild/cpython3_3.12_macaroonbakery/build/macaroonbakery/tests
> copying macaroonbakery/tests/common.py -> 
> /<>/.pybuild/cpython3_3.12_macaroonbakery/build/macaroonbakery/tests
> copying macaroonbakery/tests/test_namespace.py -> 
> /<>/.pybuild/cpython3_3.12_macaroonbakery/build/macaroonbakery/tests
> copying macaroonbakery/tests/test_httpbakery.py -> 
> /<>/.pybuild/cpython3_3.12_macaroonbakery/build/macaroonbakery/tests
> copying macaroonbakery/tests/test_checkers.py -> 
> /<>/.pybuild/cpython3_3.12_macaroonbakery/build/macaroonbakery/tests
> copying macaroonbakery/tests/test_authorizer.py -> 
> /<>/.pybuild/cpython3_3.12_macaroonbakery/build/macaroonbakery/tests
> copying macaroonbakery/tests/test_utils.py -> 
> /<>/.pybuild/cpython3_3.12_macaroonbakery/build/macaroonbakery/tests
> copying macaroonbakery/tests/test_keyring.py -> 
> /<>/.pybuild/cpython3_3.12_macaroonbakery/build/macaroonbakery/tests
> copying macaroonbakery/tests/test_oven.py -> 
> /<>/.pybuild/cpython3_3.12_macaroonbakery/build/macaroonbakery/tests
> copying macaroonbakery/tests/test_discharge.py -> 
> /<>/.pybuild/cpython3_3.12_macaroonbakery/build/macaroonbakery/tests
> copying macaroonbakery/tests/test_discharge_all.py -> 
> /<>/.pybuild/cpython3_3.12_macaroonbakery/build/macaroonbakery/tests
> copying macaroonbakery/tests/test_macaroon.py -> 
> /<>/.pybuild/cpython3_3.12_macaroonbakery/build/macaroonbakery/tests
>

Bug#1058186: marked as done (python-swiftclient: FTBFS: ModuleNotFoundError: No module named 'imp')

2023-12-17 Thread Debian Bug Tracking System

Your message dated Sun, 17 Dec 2023 16:04:58 +
with message-id 
and subject line Bug#1058186: fixed in python-swiftclient 1:4.4.0-4
has caused the Debian Bug report #1058186,
regarding python-swiftclient: FTBFS: ModuleNotFoundError: No module named 'imp'
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
1058186: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1058186
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: python-swiftclient
Version: 1:4.4.0-3
Severity: serious
Justification: FTBFS
Tags: trixie sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20231212 ftbfs-trixie

Hi,

During a rebuild of all packages in sid, your package failed to build
on amd64.


Relevant part (hopefully):
> make[1]: Entering directory '/<>'
> make[1]: pyversions: No such file or directory
> py3versions: no X-Python3-Version in control file, using supported versions
> PYBUILD_SYSTEM=custom \
>   PYBUILD_TEST_ARGS="cd {build_dir} ; {interpreter} -m stestr run" \
>   dh_auto_test
> I: pybuild base:310: cd 
> /<>/.pybuild/cpython3_3.12_swiftclient/build ; python3.12 -m 
> stestr run
> No module named 'imp'
> Traceback (most recent call last):
>   File "/usr/lib/python3/dist-packages/cliff/app.py", line 410, in 
> run_subcommand
> result = cmd.run(parsed_args)
>  
>   File "/usr/lib/python3/dist-packages/cliff/command.py", line 176, in run
> return_code = self.take_action(parsed_args) or 0
>   ^
>   File "/usr/lib/python3/dist-packages/stestr/commands/run.py", line 229, in 
> take_action
> result = run_command(
>  
>   File "/usr/lib/python3/dist-packages/stestr/commands/run.py", line 360, in 
> run_command
> repo = util.get_repo_open(repo_url=repo_url)
>^
>   File "/usr/lib/python3/dist-packages/stestr/repository/util.py", line 40, 
> in get_repo_open
> repo_module = importlib.import_module('stestr.repository.' + repo_type)
>   ^
>   File "/usr/lib/python3.12/importlib/__init__.py", line 90, in import_module
> return _bootstrap._gcd_import(name[level:], package, level)
>
>   File "", line 1387, in _gcd_import
>   File "", line 1360, in _find_and_load
>   File "", line 1331, in _find_and_load_unlocked
>   File "", line 935, in _load_unlocked
>   File "", line 994, in exec_module
>   File "", line 488, in _call_with_frames_removed
>   File "/usr/lib/python3/dist-packages/stestr/repository/file.py", line 22, 
> in 
> from future.moves.dbm import dumb as my_dbm
>   File "/usr/lib/python3/dist-packages/future/moves/__init__.py", line 5, in 
> 
> from future.standard_library import import_top_level_modules
>   File "/usr/lib/python3/dist-packages/future/standard_library/__init__.py", 
> line 65, in 
> import imp
> ModuleNotFoundError: No module named 'imp'
> E: pybuild pybuild:395: test: plugin custom failed with: exit code=1: cd 
> /<>/.pybuild/cpython3_3.12_swiftclient/build ; python3.12 -m 
> stestr run
> I: pybuild base:310: cd 
> /<>/.pybuild/cpython3_3.11_swiftclient/build ; python3.11 -m 
> stestr run
> {1} test.unit.test_authv1.TestPlugin.test_get_access [0.002551s] ... ok
> {1} test.unit.test_authv1.TestPluginLoading.test_can_load [0.013575s] ... ok
> {1} 
> test.unit.test_command_helpers.TestStatHelpers.test_stat_account_policy_stat_with_container_counts
>  [0.001926s] ... ok
> {7} test.unit.test_authv1.TestPlugin.test_get_access_accepts_storage_token 
> [0.001228s] ... ok
> {7} test.unit.test_authv1.TestPlugin.test_get_access_missing_url [0.001005s] 
> ... ok
> {7} test.unit.test_authv1.TestPluginWithAccount.test_get_access_bad_expiry 
> [0.001201s] ... ok
> {7} test.unit.test_authv1.TestPluginWithAccount.test_get_access_missing_url 
> [0.000910s] ... ok
> {7} 
> test.unit.test_command_helpers.TestStatHelpers.test_stat_container_verbose 
> [0.001734s] ... ok
> {7} test.unit.test_command_helpers.TestStatHelpers.test_stat_object_human 
> [0.001453s] ... ok
> {7} test.unit.test_service.TestServiceDelete.test_bulk_delete [0.004388s] ... 
> ok
> {7} test.unit.test_service.TestServiceDelete.test_delete_object [0.001267s] 
> ... ok
> {7} 
> test.unit.test_service.TestServiceDownload.test_download_object_job_exception 
> [0.002465s] ... ok
> {7} test.unit.test_service.TestServiceDownload.test_download_version_id 
> [0.002225s] ... ok
> {7} 
>

Bug#1057863: slepc4py ftbfs with Python 3.12

2023-12-17 Thread Drew Parsons

Source: slepc4py
Followup-For: Bug #1057863

Correction: curexc_traceback is not used in slepc4py 3.19.
Maybe it's time to upgrade to PETSc 3.19.

Processed: Bug#1058186 marked as pending in python-swiftclient

2023-12-17 Thread Debian Bug Tracking System

Processing control commands:

> tag -1 pending
Bug #1058186 [src:python-swiftclient] python-swiftclient: FTBFS: 
ModuleNotFoundError: No module named 'imp'
Added tag(s) pending.

-- 
1058186: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1058186
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#1058186: marked as pending in python-swiftclient

2023-12-17 Thread Thomas Goirand

Control: tag -1 pending

Hello,

Bug #1058186 in python-swiftclient reported by you has been fixed in the
Git repository and is awaiting an upload. You can see the commit
message below and you can check the diff of the fix at:

https://salsa.debian.org/openstack-team/clients/python-swiftclient/-/commit/874d95bab6ecbd8398fdb7a5cfef0917599d133e


Add py3.12-Fix_call_assertion.patch (Closes: #1058186).


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/1058186

Bug#999964: shush: depends on obsolete pcre3 library

2023-12-17 Thread Yavor Doganov

Control: tags -1 + patch

Please find attached a patch.
Description: Port to PCRE2.
Bug-Debian: https://bugs.debian.org/64
Author: Yavor Doganov 
Forwarded: no
Last-Update: 2023-12-17
---

--- shush-1.2.3.orig/configure.ac
+++ shush-1.2.3/configure.ac
@@ -60,9 +60,19 @@
 # Checks for libraries.
 AC_SEARCH_LIBS([basename], [gen])
 if test "x$with_pcre" != "xno"; then
-   AC_SEARCH_LIBS([pcre_compile], [pcre], ,
-   AC_MSG_WARN([Perl Compatible Regular Expressions library is missing.])
-   with_pcre="no")
+   save_libs="$LIBS"
+   LIBS="$LIBS -lpcre2-8"
+   AC_MSG_CHECKING([for pcre library])
+   AC_LINK_IFELSE(
+ [AC_LANG_PROGRAM([[#define PCRE2_CODE_UNIT_WIDTH 8
+#include 
+]],
+  [[pcre2_match_data_create(4, NULL);]])],
+ [AC_MSG_RESULT([yes])],
+ [AC_MSG_RESULT([no])
+  AC_MSG_WARN([Perl Compatible Regular Expressions library is missing.])
+  with_pcre="no"
+  LIBS="$save_libs"])
 fi
 AC_SEARCH_LIBS([MD5Data], [md])
 AC_SEARCH_LIBS([md5_calc], [md5])
@@ -70,7 +80,11 @@
 # Checks for header files.
 AC_CHECK_HEADERS([md5.h paths.h pthread.h])
 if test "x$with_pcre" != "xno"; then
-   AC_CHECK_HEADERS([pcre.h])
+   AC_CHECK_HEADERS([pcre2.h],
+ [AC_DEFINE([HAVE_PCRE_H], [1],
+[Define to 1 if you have the  header file.])],
+ [], [[#define PCRE2_CODE_UNIT_WIDTH 8
+ ]])
 fi
 
 # Checks for typedefs, structures, and compiler characteristics.
--- shush-1.2.3.orig/src/analyzer.c
+++ shush-1.2.3/src/analyzer.c
@@ -16,7 +16,8 @@
 #include 
 #include 
 #if defined(HAVE_PCRE_H)
-# include 
+# define PCRE2_CODE_UNIT_WIDTH 8
+# include 
 #endif
 
 #include "analyzer.h"
@@ -40,7 +41,7 @@
 {
regex_t re;
 #if defined(HAVE_PCRE_H)
-   pcre *pcre;
+   pcre2_code *pcre;
 #endif
 } val;
 };
@@ -98,15 +99,19 @@
 static int
 compile_pcre(void *pcreptr, char *str)
 {
-pcre **re;
-const char *errmsg;
-int erroffset;
+pcre2_code **re;
+int err;
+PCRE2_SIZE erroffset;
 
 re = pcreptr;
-*re = pcre_compile(str, 0, , , NULL);
+*re = pcre2_compile((PCRE2_SPTR)str, strlen(str), 0,
+, , NULL);
 if (*re == NULL)
   {
-   error("Bad PCRE (offset %d): %s", erroffset, errmsg);
+   PCRE2_UCHAR errmsg[120];
+
+   pcre2_get_error_message(err, errmsg, sizeof(errmsg));
+   error("Bad PCRE (offset %zu): %s", erroffset, errmsg);
return -1;
   }
 return 0;
@@ -501,15 +506,17 @@
 #if defined(HAVE_PCRE_H)
  else if (type == PCRE)
{
- int ovector[3072];
+ PCRE2_SIZE *ovector;
+ pcre2_match_data *md;
 
- r = pcre_exec(list[condno].val.pcre, NULL, ln,
+ md = pcre2_match_data_create(3072, NULL);
+ r = pcre2_match(list[condno].val.pcre, (PCRE2_SPTR)ln,
(lndup != NULL) ? strlen(lndup) : nl - ln,
-   0, 0, ovector, 3072);
- if (r < 0 && r != PCRE_ERROR_NOMATCH)
+   0, 0, md, NULL);
+ if (r < 0 && r != PCRE2_ERROR_NOMATCH)
{
  /* Something bad happened */
- error("Fatal error during output analysis: pcre_exec() failed 
with code %d", r);
+ error("Fatal error during output analysis: pcre2_match() 
failed with code %d", r);
  error("Regular expression used was: %s",
list[condno].expression);
  error("Trying to match the following line of data: %s", ln);
@@ -517,6 +524,7 @@
  free(lndup);
  else
  *nl = '\n';
+  pcre2_match_data_free(md);
  return -1;
}
  else
@@ -527,14 +535,15 @@
 
  /* Matched */
  debug(DDATA,
-   "Matched: #%d %d[%c] (PCRE_ERROR_NOMATCH=%d)",
-   condno+1, r, list[condno].code, PCRE_ERROR_NOMATCH);
+   "Matched: #%d %d[%c] (PCRE2_ERROR_NOMATCH=%d)",
+   condno+1, r, list[condno].code, 
PCRE2_ERROR_NOMATCH);
  byteset_set(list[condno].code, 1);
  /* Check for substrings */
  i = 1;
+ ovector = pcre2_get_ovector_pointer(md);
  while (i < r)
{
- if (ovector[i*2] < 0 || ovector[i*2+1] < 0)
+ if ((int)ovector[i*2] < 0 || (int)ovector[i*2+1] < 0)
  continue;
  set_mark(marks, , ,
   ln - str + ovector[i*2], TOGGLE);
@@ -546,8 +555,9 @@
}
  else
  debug(DVDATA,
-   "Failed: #%d %d[%c] (PCRE_ERROR_NOMATCH=%d)",
-   condno+1, r,

Processed: Re: Bug#999964: shush: depends on obsolete pcre3 library

2023-12-17 Thread Debian Bug Tracking System

Processing control commands:

> tags -1 + patch
Bug #64 [src:shush] shush: depends on obsolete pcre3 library
Added tag(s) patch.

-- 
64: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=64
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#1058870: marked as done (jq: Got illegal instruction in unit test in i386)

2023-12-17 Thread Debian Bug Tracking System

Your message dated Sun, 17 Dec 2023 15:34:58 +
with message-id 
and subject line Bug#1058870: fixed in jq 1.7.1-2
has caused the Debian Bug report #1058870,
regarding jq: Got illegal instruction in unit test in i386
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.)


-- 
1058870: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1058870
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: jq
Version: 1.7.1-1
Severity: serious
Tags: ftbfs
Justification: fails to build from source (but built successfully in the past)

jq failed to build in i386 with illegal instruction in unit test. The
following is build log


FAIL: tests/jqtest
FAIL: tests/mantest
FAIL: tests/utf8test
FAIL: tests/shtest
FAIL: tests/optionaltest
FAIL: tests/onigtest
FAIL: tests/base64test
FAIL: tests/manonigtest
==
   jq 1.7: ./test-suite.log
==

# TOTAL: 8
# PASS:  0
# SKIP:  0
# XFAIL: 0
# FAIL:  8
# XPASS: 0
# ERROR: 0

.. contents:: :depth: 2

FAIL: tests/mantest
===

==2576563== 
==2576563== Process terminating with default action of signal 4 (SIGILL)
==2576563==  Illegal opcode at address 0x40199A6
==2576563==at 0x40199A6: _dl_sysdep_parse_arguments (dl-sysdep.c:83)
==2576563==by 0x40199A6: _dl_sysdep_start (dl-sysdep.c:106)
==2576563==by 0x401B3C2: _dl_start_final (rtld.c:498)
==2576563==by 0x401B3C2: _dl_start (rtld.c:585)
==2576563==by 0x401A23A: ??? (in /usr/lib/i386-linux-gnu/ld-linux.so.2)
Illegal instruction
FAIL tests/mantest (exit status: 132)

FAIL: tests/jqtest
==

==2576560== 
==2576560== Process terminating with default action of signal 4 (SIGILL)
==2576560==  Illegal opcode at address 0x40199A6
==2576560==at 0x40199A6: _dl_sysdep_parse_arguments (dl-sysdep.c:83)
==2576560==by 0x40199A6: _dl_sysdep_start (dl-sysdep.c:106)
==2576560==by 0x401B3C2: _dl_start_final (rtld.c:498)
==2576560==by 0x401B3C2: _dl_start (rtld.c:585)
==2576560==by 0x401A23A: ??? (in /usr/lib/i386-linux-gnu/ld-linux.so.2)
Illegal instruction
FAIL tests/jqtest (exit status: 132)

FAIL: tests/shtest
==

+ . ./tests/setup
+ [ -n  ]
+ set -eu
+ dirname ./tests/shtest
+ cd ./tests
+ pwd
+ JQTESTDIR=/<>/tests
+ JQBASEDIR=/<>/tests/..
+ JQ=/<>/jq
+ [ -z  ]
+ which valgrind
+ VALGRIND=libtool --mode=execute -- valgrind --error-exitcode=1 
--leak-check=full
--suppressions=/<>/tests/onig.supp
--suppressions=/<>/tests/local.supp
+ VG_EXIT0=--error-exitcode=0
+ Q=-q
+ mods=/<>/tests/modules
+ clean=true
+ d=
+ trap clean EXIT
+ mktemp -d -t jqXX
+ d=/tmp/jqh5V7Wd
+ [ -z /tmp/jqh5V7Wd ]
+ msys=false
+ mingw=false
+ uname -s
+ JQ_NO_B=/<>/jq
+ JQ=/<>/jq -b
+ 
PATH=/<>/tests/..:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games
 /<>/tests/../tests/jq-f-test.sh
+ [ -f /<>/tests/../.libs/libinject_errors.so ]
+ printf a\0b\nc\0d\ne
+ libtool --mode=execute -- valgrind --error-exitcode=1 --leak-check=full 
--suppressions=/<>/tests/onig.supp 
--suppressions=/<>/tests/local.supp -q /<>/jq -b -Rse 
. == "a\ub\nc\ud\ne" /tmp/jqh5V7Wd/input
==2576629== 
==2576629== Process terminating with default action of signal 4 (SIGILL)
==2576629==  Illegal opcode at address 0x40199A6
==2576629==at 0x40199A6: _dl_sysdep_parse_arguments (dl-sysdep.c:83)
==2576629==by 0x40199A6: _dl_sysdep_start (dl-sysdep.c:106)
==2576629==by 0x401B3C2: _dl_start_final (rtld.c:498)
==2576629==by 0x401B3C2: _dl_start (rtld.c:585)
==2576629==by 0x401A23A: ??? (in /usr/lib/i386-linux-gnu/ld-linux.so.2)
Illegal instruction
+ clean
+ true
+ [ -n /tmp/jqh5V7Wd ]
+ rm -rf /tmp/jqh5V7Wd
FAIL tests/shtest (exit status: 132)

FAIL: tests/utf8test


==2576567== 
==2576567== Process terminating with default action of signal 4 (SIGILL)
==2576567==  Illegal opcode at address 0x40199A6
==2576567==at 0x40199A6: _dl_sysdep_parse_arguments (dl-sysdep.c:83)
==2576567==by 0x40199A6: _dl_sysdep_start (dl-sysdep.c:106)
==2576567==by 0x401B3C2: _dl_start_final (rtld.c:498)
==2576567==by 0x401B3C2: _dl_start (rtld.c:585)
==2576567==by 0x401A23A: ??? (in /usr/lib/i386-linux-gnu/ld-linux.so.2)
Illegal instruction
UTF-8 byte sequences that span the jv_load_file read buffer are mangled
FAIL tests/utf8test (exit status: 1)

FAIL: tests/base64test
==

==2576797== 
==2576797== Process terminating with default action of signal 4 (SIGILL)
==2576797==  Illegal opcode at address 0x40199A6
==2576797==at 0x40199A6:

Processed: Re: Bug#1057935: ncurses-hexedit: FTBFS: invalid use of incomplete typedef ‘WINDOW’ {aka ‘struct _win_st’}

2023-12-17 Thread Debian Bug Tracking System

Processing control commands:

> tags -1 + patch
Bug #1057935 [src:ncurses-hexedit] ncurses-hexedit: FTBFS: invalid use of 
incomplete typedef ‘WINDOW’ {aka ‘struct _win_st’}
Added tag(s) patch.

-- 
1057935: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1057935
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#1057863: slepc4py ftbfs with Python 3.12

2023-12-17 Thread Drew Parsons

Source: slepc4py
Followup-For: Bug #1057863

slepc4py does not use curexc_traceback.

Perhaps this is a bug in cython?

Bug#1057935: ncurses-hexedit: FTBFS: invalid use of incomplete typedef ‘WINDOW’ {aka ‘struct _win_st’}

2023-12-17 Thread Sven Joachim

Control: tags -1 + patch

On 2023-12-10 20:18 +0100, Santiago Vila wrote:

> Package: src:ncurses-hexedit
> Version: 0.9.7+orig-7.2
> Severity: serious
> Tags: ftbfs
>
> Dear maintainer:
>
> During a rebuild of all packages in unstable, your package failed to build:
>
> 
> [...]
> gcc -DHAVE_CONFIG_H -I. -I..  -Wdate-time -D_FORTIFY_SOURCE=2 -g -O2
> -ffile-prefix-map=/<>=. -fstack-protector-strong
> -fstack-clash-protection -Wformat -Werror=format-security
> -fcf-protection -Wall -c -o file.o file.c
> file.c: In function ‘printPage’:
> file.c:647:34: error: invalid use of incomplete typedef ‘WINDOW’ {aka ‘struct 
> _win_st’}
>   647 |   for (result = Globals.wmain->_curx; result < COLS; result++)
>   |  ^~

There are quite a few more instances of such errors across the source
code, the attached patch should fix all of them.  The package builds and
from a cursory look appears to work, but it would be good if a potential
NMU'er reviews and tests the patch before uploading.

Cheers,
   Sven

From 676299deb4fa83c7f100011da2948c49ba97499c Mon Sep 17 00:00:00 2001
From: Sven Joachim 
Date: Sun, 17 Dec 2023 16:15:43 +0100
Subject: [PATCH] Avoid accessing internal ncurses structures

Since ncurses patchlevel 20231021 the WINDOW structure is opaque, its
members cannot be addressed directly.  Use the functions ncurses
provides for this purpose instead.
---
 src/file.c|  2 +-
 src/misc.c|  6 ++
 src/print.c   | 16 
 src/widgets.c | 24 
 4 files changed, 23 insertions(+), 25 deletions(-)

diff --git a/src/file.c b/src/file.c
index 14a2475..ba7c147 100644
--- a/src/file.c
+++ b/src/file.c
@@ -644,7 +644,7 @@ printPage (const struct FileNames *fp)
   wprintw (Globals.wmain, "%s", trunc_file);
   fp = fp->p;

-  for (result = Globals.wmain->_curx; result < COLS; result++)
+  for (result = getcurx(Globals.wmain); result < COLS; result++)
  wprintw (Globals.wmain, " ");
}

diff --git a/src/misc.c b/src/misc.c
index 24068b4..8b0fb4b 100644
--- a/src/misc.c
+++ b/src/misc.c
@@ -641,10 +641,8 @@ handleSigwinch (int i)
if (!newlines)
   die_horribly (NOT_ENOUGH_MEMORY, NULL);

-   Globals.wmain->_cury = cursor_y - 1;
-   Globals.wmain->_curx = cursor_x;
-   stdscr->_cury = cursor_y;
-   stdscr->_curx = cursor_x;
+   wmove(Globals.wmain, cursor_y - 1, cursor_x);
+   move(cursor_y, cursor_x);
if (cursor_y >= BOTTOM_LINE)
   cursor_y = BOTTOM_LINE;
if (Globals.mode == FILE_MODE)
diff --git a/src/print.c b/src/print.c
index 57b291e..59b0ca1 100644
--- a/src/print.c
+++ b/src/print.c
@@ -196,16 +196,16 @@ drawAsciiDump (unsigned long off, unsigned long *offs)
   if (*offs > Globals.filesize)
  break;
 #ifdef __NCURSES_H /* i don't know why this works */
-  if (Globals.wmain->_cury == MAIN_BOTTOM_LINE)
+  if (getcury(Globals.wmain) == MAIN_BOTTOM_LINE)
 #else
-  if (Globals.wmain->_cury == MAIN_HEIGHT)
+  if (getcury(Globals.wmain) == MAIN_HEIGHT)
 #endif
  break;
-  if (Globals.wmain->_curx == COLS - 2)
+  if (getcurx(Globals.wmain) == COLS - 2)
   {
  move = 1;
   }
-  if (Globals.wmain->_curx == 0)
+  if (getcurx(Globals.wmain) == 0)
  *(newlines + i++) = *offs;
   bold = hash_lookup (*offs, NULL);
   if (!bold)
@@ -215,8 +215,8 @@ drawAsciiDump (unsigned long off, unsigned long *offs)
   {
  if (filebuffer (*offs) == '\n')
  {
-int cury = Globals.wmain->_cury;
-int i = Globals.wmain->_curx;
+int cury = getcury(Globals.wmain);
+int i = getcurx(Globals.wmain);
 for (; i < COLS - 2; i++)
wprintw (Globals.wmain, " ");
 wprintw (Globals.wmain, ".");
@@ -235,7 +235,7 @@ drawAsciiDump (unsigned long off, unsigned long *offs)
   {
  if (filebuffer (*offs) == EBCDIC['\n'])
  {
-int cury = Globals.wmain->_cury;
+int cury = getcury(Globals.wmain);
 wprintw (Globals.wmain, ".");
 wmove (Globals.wmain, cury + 1, 0);
  }
@@ -257,7 +257,7 @@ drawAsciiDump (unsigned long off, unsigned long *offs)
   (*offs)++;
   if (move)
   {
- wmove (Globals.wmain, Globals.wmain->_cury + 1, 0);
+ wmove (Globals.wmain, getcury(Globals.wmain) + 1, 0);
  move = 0;
  continue;
   }
diff --git a/src/widgets.c b/src/widgets.c
index eb627ad..38183f8 100644
--- a/src/widgets.c
+++ b/src/widgets.c
@@ -99,11 +99,11 @@ stringBox (WINDOW *win, int y, int x, int len, int max, char *sample)
  case KEY_LEFT:
 if (i > 0)
 {
-   if (win->_curx > x)
+   if (getcurx(win) > x)
/* not at left hand side */
{
   i--;
-  wmove

Bug#1058870: jq: Got illegal instruction in unit test in i386

2023-12-17 Thread 陳昌倬

The issue only happens when using valgrind. Need to investigate.


-- 
ChangZhuo Chen (陳昌倬) czchen@{czchen,debian}.org
Key fingerprint = BA04 346D C2E1 FE63 C790  8793 CC65 B0CD EC27 5D5B


signature.asc
Description: PGP signature

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

2023-12-17 Thread Pádraig Brady


On 16/12/2023 21:46, Bernhard Voelker wrote:

On 12/15/23 21:13, Michael Stone wrote:

On Fri, Dec 15, 2023 at 11:21:06AM -0800, Paul Eggert wrote:

Stlll, Pádraig gave a reasonable summary of why the change was made,


To clarify my summary a little, there I said that -n now _immediately_ fails.
I should have said _silently_ fails.  I.e. the complete copy operation
proceeds as before, and only the exit status is at issue here.


despite its incompatibility with previous behavior. (One thing I'd add
is that the FreeBSD behavior is inherently less race-prone.)


Whether the implementation is race-prone or not is an internal thing.
I think we're currently discussing more on a user-perspective level.

IIUC then the question is whether `cp -n` should continue to behave like
the (new) `cp --update=none` which returns EXIT_SUCCESS.

Regardless what other implementations do, when reading the -n description
from a user's point of view:

-n, --no-clobber do not overwrite an existing file (overrides a
   -u or previous -i option). See also --update

then I'd expect the tool to just skip existing files like `rsync 
--ignore-existing`
does.  In that regard I would be surprised if skipping files would result in an 
error.
Well, I would understand if there'd be a '--no-clobber=fail' option.


Agreed we should improve the docs a bit for this option.
I'll apply this at least:

diff --git a/doc/coreutils.texi b/doc/coreutils.texi
index 1f8b356d1..bf0f424d3 100644
--- a/doc/coreutils.texi
+++ b/doc/coreutils.texi
@@ -9057,6 +9057,8 @@ Do not overwrite an existing file; silently fail instead.
 This option overrides a previous
 @option{-i} option.  This option is mutually exclusive with @option{-b} or
 @option{--backup} option.
+See also the @option{--update=none} option which will
+skip existing files but not fail.

 @item -P
 @itemx --no-dereference
diff --git a/src/cp.c b/src/cp.c
index 04a5cbee3..3ccc4c4e6 100644
--- a/src/cp.c
+++ b/src/cp.c
@@ -192,8 +192,8 @@ Copy SOURCE to DEST, or multiple SOURCE(s) to DIRECTORY.\n\
   -L, --dereferencealways follow symbolic links in SOURCE\n\
 "), stdout);
   fputs (_("\
-  -n, --no-clobber do not overwrite an existing file (overrides 
a\n\
- -u or previous -i option). See also 
--update\n\
+  -n, --no-clobber ensure no existing files overwritten, and 
fail\n\
+ silently instead. See also --update\n\
 "), stdout);
   fputs (_("\
   -P, --no-dereference never follow symbolic links in SOURCE\n\



As Kamil added the option in 2009, I'd assume that the same patch was already
active in RHEL versions for quite some longer time.
Now changing the exit code feels kind of rough.


Well RHEL 6 came out a bit after (2010), and had the --no-clobber change,
while RHEL 5 before that did not.

Taking about distros, it's worth noting that the change is Fedora 39
which has been released for a month now.
We'll keep a close eye on issues, but haven't heard much as
of yet at least.


Therefore, from a pure user's perspective and regarding many years of 
precedence,
I am 80:20 for reverting the exit code change.


Thanks for your thoughts,
appreciated as always.

cheers,
Pádraig

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

2023-12-17 Thread Michael Stone


On Sun, Dec 17, 2023 at 12:34:11AM -0800, Paul Eggert wrote:

On 2023-12-16 13:46, Bernhard Voelker wrote:

Whether the implementation is race-prone or not is an internal thing.


I wasn't referring to the internal implementation. I was referring to 
cp users. With the newer Coreutils (FreeBSD) behavior, you can 
reliably write a script to do something if cp -n didn't copy the file 
because the destination already existed. With the older Coreutils 
behavior you cannot do that reliably; there will always be a race 
condition.


You can now reliably write a script using the new long option. Changing 
the behavior of the short option helped nobody.

Bug#1058657: python3-apt: undefined symbol: PyAptWarning

2023-12-17 Thread Alexandre Detiste

This is really bad because it also breaks unattended-upgrades,
so I guess the only way out is to run "apt upgrade" by hand
(after it's fixed) on each impacted system.

Processed: adios2 openmpi

2023-12-17 Thread Debian Bug Tracking System

Processing commands for cont...@bugs.debian.org:

> block 1058353 by 1058876
Bug #1058353 [libadios2-mpi-c-dev] libadios2-mpi-c-dev: ships headers already 
shipped in libadios2-common-c-dev
1058353 was not blocked by any bugs.
1058353 was not blocking any bugs.
Added blocking bug(s) of 1058353: 1058876
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
1058353: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1058353
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Processed: bug 1057596 is forwarded to https://github.com/xonsh/xonsh/issues/5248

2023-12-17 Thread Debian Bug Tracking System

Processing commands for cont...@bugs.debian.org:

> forwarded 1057596 https://github.com/xonsh/xonsh/issues/5248
Bug #1057596 [src:xonsh] xonsh: FTBFS: TypeError: object of type 'LazyObject' 
has no len()
Set Bug forwarded-to-address to 'https://github.com/xonsh/xonsh/issues/5248'.
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
1057596: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1057596
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#999965: shadowsocks-libev: depends on obsolete pcre3 library

2023-12-17 Thread Yavor Doganov

Control: tags -1 + patch

Please find attached a patch, build-tested only.
>From a214f32480e417c9bf3358652f96d29d51325560 Mon Sep 17 00:00:00 2001
From: Yavor Doganov 
Date: Sun, 17 Dec 2023 14:23:39 +0200
Subject: [PATCH] Port to PCRE2 (#65)

---
 debian/changelog   |   7 ++
 debian/control |   2 +-
 debian/patches/pcre2.patch | 157 +
 debian/patches/series  |   1 +
 4 files changed, 166 insertions(+), 1 deletion(-)
 create mode 100644 debian/patches/pcre2.patch

diff --git a/debian/changelog b/debian/changelog
index c43a915..20c1f63 100644
--- a/debian/changelog
+++ b/debian/changelog
@@ -1,3 +1,10 @@
+shadowsocks-libev (3.3.5+ds-11) UNRELEASED; urgency=medium
+
+  * debian/patches/pcre2.patch: New; port to PCRE2 (Closes: #65).
+  * debian/control (Build-Depends): Replace libpcre3-dev with libpcre2-dev.
+
+ -- Yavor Doganov   Sun, 17 Dec 2023 14:22:39 +0200
+
 shadowsocks-libev (3.3.5+ds-10) unstable; urgency=medium
 
   * Revert the move of systemd service files from /lib/ to /usr/lib/.
diff --git a/debian/control b/debian/control
index c2becba..d944661 100644
--- a/debian/control
+++ b/debian/control
@@ -16,7 +16,7 @@ Build-Depends:
  libev-dev,
  libjsonparser-dev,
  libmbedtls-dev,
- libpcre3-dev,
+ libpcre2-dev,
  libsodium-dev,
  pkg-config,
  xmlto,
diff --git a/debian/patches/pcre2.patch b/debian/patches/pcre2.patch
new file mode 100644
index 000..2691534
--- /dev/null
+++ b/debian/patches/pcre2.patch
@@ -0,0 +1,157 @@
+Description: Port to PCRE2.
+Bug-Debian: https://bugs.debian.org/65
+Author: Yavor Doganov 
+Forwarded: no
+Last-Update: 2023-12-17
+---
+
+--- shadowsocks-libev.orig/src/rule.c
 shadowsocks-libev/src/rule.c
+@@ -78,14 +78,18 @@
+ init_rule(rule_t *rule)
+ {
+ if (rule->pattern_re == NULL) {
+-const char *reerr;
+-int reerroffset;
++int reerr;
++PCRE2_SIZE reerroffset;
+ 
+ rule->pattern_re =
+-pcre_compile(rule->pattern, 0, , , NULL);
++pcre2_compile((PCRE2_SPTR)rule->pattern, strlen(rule->pattern),
++  0, , , NULL);
+ if (rule->pattern_re == NULL) {
+-LOGE("Regex compilation of \"%s\" failed: %s, offset %d",
+- rule->pattern, reerr, reerroffset);
++PCRE2_UCHAR buf[120];
++
++pcre2_get_error_message(reerr, buf, sizeof(buf));
++LOGE("Regex compilation of \"%s\" failed: %s, offset %zu",
++ rule->pattern, buf, reerroffset);
+ return 0;
+ }
+ }
+@@ -97,6 +101,7 @@
+ lookup_rule(const struct cork_dllist *rules, const char *name, size_t 
name_len)
+ {
+ struct cork_dllist_item *curr, *next;
++pcre2_match_data *md = NULL;
+ 
+ if (name == NULL) {
+ name = "";
+@@ -105,10 +110,15 @@
+ 
+ cork_dllist_foreach_void(rules, curr, next) {
+ rule_t *rule = cork_container_of(curr, rule_t, entries);
+-if (pcre_exec(rule->pattern_re, NULL,
+-  name, name_len, 0, 0, NULL, 0) >= 0)
++pcre2_match_data_free(md);
++md = pcre2_match_data_create_from_pattern(rule->pattern_re, NULL);
++if (pcre2_match(rule->pattern_re, (PCRE2_SPTR)name,
++name_len, 0, 0, md, NULL) >= 0) {
++pcre2_match_data_free(md);
+ return rule;
++}
+ }
++pcre2_match_data_free(md);
+ 
+ return NULL;
+ }
+@@ -128,6 +138,6 @@
+ 
+ ss_free(rule->pattern);
+ if (rule->pattern_re != NULL)
+-pcre_free(rule->pattern_re);
++pcre2_code_free(rule->pattern_re);
+ ss_free(rule);
+ }
+--- shadowsocks-libev.orig/src/rule.h
 shadowsocks-libev/src/rule.h
+@@ -33,17 +33,16 @@
+ 
+ #include 
+ 
+-#ifdef HAVE_PCRE_H
+-#include 
+-#elif HAVE_PCRE_PCRE_H
+-#include 
++#ifdef HAVE_PCRE2_H
++#define PCRE2_CODE_UNIT_WIDTH 8
++#include 
+ #endif
+ 
+ typedef struct rule {
+ char *pattern;
+ 
+ /* Runtime fields */
+-pcre *pattern_re;
++pcre2_code *pattern_re;
+ 
+ struct cork_dllist_item entries;
+ } rule_t;
+--- shadowsocks-libev.orig/m4/pcre.m4
 shadowsocks-libev/m4/pcre.m4
+@@ -82,12 +82,12 @@
+   fi
+ ],
+ [
+-  AC_CHECK_PROG(PCRE_CONFIG, pcre-config, pcre-config)
++  AC_CHECK_PROG(PCRE_CONFIG, pcre2-config, pcre2-config)
+   if test "x$PCRE_CONFIG" != "x"; then
+ enable_pcre=yes
+ pcre_base_dir="`$PCRE_CONFIG --prefix`"
+ pcre_include="`$PCRE_CONFIG --cflags | sed -es/-I//`"
+-pcre_ldflags="`$PCRE_CONFIG --libs | sed -es/-lpcre// -es/-L//`"
++pcre_ldflags="`$PCRE_CONFIG --libs8 | sed -es/-lpcre// -es/-L//`"
+   fi
+ ])
+ 
+@@ -95,7 +95,7 @@
+   AC_MSG_CHECKING([for pcre location])
+   AC_CACHE_VAL(ats_cv_pcre_dir,[
+   for dir in /usr/local /usr ; do
+-if test -d $dir && ( test -f $dir/include/pcre.h || test -f 
$dir/include/pcre/pcre.h ); then
++if test -d $dir && ( test -f $dir/include/pcre2.h ); then
+   ats_cv_pcre_dir=$dir
+

Processed: Re: Bug#999965: shadowsocks-libev: depends on obsolete pcre3 library

2023-12-17 Thread Debian Bug Tracking System

Processing control commands:

> tags -1 + patch
Bug #65 [src:shadowsocks-libev] shadowsocks-libev: depends on obsolete 
pcre3 library
Added tag(s) patch.

-- 
65: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=65
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

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

2023-12-17 Thread Dominique Martinet

Paul Eggert wrote on Fri, Dec 15, 2023 at 11:21:06AM -0800:
> The cat is to some extent out of the bag. Unless one insists on (FreeBSD |
> coreutils 9.2-9.4), or insist on coreutils 7.1-9.1, one should not rely on
> cp -n failing or silently succeeding when the destination already exists.
> This will remain true regardless of whether coreutils reverts to its 7.1-9.1
> behavior.

This. Scripts that want to be portable already can't assume cp -n will
do what they want, so at this point it doesn't really matter what
coreutils does in the grand scheme of things.

For distros like debian since even -testing hasn't seen coreutils 9.2,
there's still value in reverting locally (with a warning that it's not
reliable perhaps?), but in general coreutils 9.2 has been out for 9
months (2023 March 20), so many systems can already be considered
affected; but it's a disservice to users to just try to hide the problem
under the rug.


(To give a data point, this did bite us as well, and I was annoyed
enough that I went to look for the old bug report back in September, but
at that point 9.3 had already been out and I had given up without
reporting anything as nothing would change the fact that my scripts
would need updating. For the gory details I also need compatibility
with busybox cp (where -n silently ignores existing files), so
--update=none is not an option, but I for this particular usage I
settled for '-u' (--update=older, that busybox also support as short
option only...), and I since hurried to forget about it)

-- 
Dominique Martinet | Asmadeus

Bug#1057169: marked as done (pdftk-java: FTBFS with bouncycastle 1.77)

2023-12-17 Thread Debian Bug Tracking System

Your message dated Sun, 17 Dec 2023 11:34:25 +
with message-id 
and subject line Bug#1057169: fixed in pdftk-java 3.3.3-2
has caused the Debian Bug report #1057169,
regarding pdftk-java: FTBFS with bouncycastle 1.77
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.)


-- 
1057169: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1057169
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: pdftk-java
Version: 3.3.3-1
Severity: serious
Tags: ftbfs sid
User: a...@debian.org
Usertags: bouncycastle-1.77
X-Debbugs-Cc: a...@debian.org

Dear maintainer,

pdftk-java fails to build from source with bouncycastle 1.77. The reason
is the removal of long deprecated methods. The (hopefully) relevant
error message from the build log.

[javac]
/<>/java/com/gitlab/pdftk_java/com/lowagie/text/pdf/PdfPKCS7.java:
228: error: cannot find symbol
[javac] ASN1Sequence content =
(ASN1Sequence)((DERTaggedObject)signedData.getObjectAt(1)).getObject();
[javac]   
^
[javac]   symbol:   method getObject()
[javac]   location: class DERTaggedObject
[javac]
/<>/java/com/gitlab/pdftk_java/com/lowagie/text/pdf/PdfPKCS7.java:
261: error: cannot find symbol
[javac] DEROctetString rsaDataContent =
(DEROctetString)((DERTaggedObject)rsaData.getObjectAt(1)).getObject();
[javac]   
^
[javac]   symbol:   method getObject()
[javac]   location: class DERTaggedObject
[javac]
/<>/java/com/gitlab/pdftk_java/com/lowagie/text/pdf/PdfPKCS7.java:
297: error: cannot find symbol
[javac] ASN1Sequence sseq = (ASN1Sequence)tagsig.getObject();
[javac] ^
[javac]   symbol:   method getObject()
[javac]   location: variable tagsig of type ASN1TaggedObject
[javac] /<>/java/com/gitlab/pdftk_


signature.asc
Description: This is a digitally signed message part
--- End Message ---
--- Begin Message ---
Source: pdftk-java
Source-Version: 3.3.3-2
Done: Johann Felix Soden 

We believe that the bug you reported is fixed in the latest version of
pdftk-java, 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 1057...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Johann Felix Soden  (supplier of updated pdftk-java 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: Sun, 17 Dec 2023 11:57:07 +0100
Source: pdftk-java
Architecture: source
Version: 3.3.3-2
Distribution: unstable
Urgency: medium
Maintainer: Johann Felix Soden 
Changed-By: Johann Felix Soden 
Closes: 1057169
Changes:
 pdftk-java (3.3.3-2) unstable; urgency=medium
 .
   * Fix FTBFS with new version of bouncycastle.
 Thanks to Francois Mazen  (Closes: #1057169)
   * Update Standards-Version to 4.6.2. No changes needed.
Checksums-Sha1:
 eae2bdb9e632b06de0c540139c00d1b4b271966a 1900 pdftk-java_3.3.3-2.dsc
 08ac4f42484f4dc77537c299f76ace186daf0585 13808 pdftk-java_3.3.3-2.debian.tar.xz
Checksums-Sha256:
 b02f227ef5b065688739ee4da6d00c099eefd5ba43db869cff243cc0c3f1b379 1900 
pdftk-java_3.3.3-2.dsc
 6ba06919defdfef7add9e2f38bc92ec9650f6897716124d3c537574ae0dca764 13808 
pdftk-java_3.3.3-2.debian.tar.xz
Files:
 e9ff376cb692afd2980777d5abb2536e 1900 text optional pdftk-java_3.3.3-2.dsc
 fbb418f61eb30065c2094aa04c36f0ff 13808 text optional 
pdftk-java_3.3.3-2.debian.tar.xz

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEER3yDOdNtdm7YUyAcg1kZO/3LCcQFAmV+2dcACgkQg1kZO/3L
CcSuWQ/9FKwDZGOtbfZxAEEP2QTy8mQdUgfo0gZzxn5KwAPgpBBVTMwgciCszggZ
DLmairlbFTm/ZqlIMT2+SuXj1ZAPL2l7LPV6ddrBX9Ycm4c+aIYgtDs0h0ijWeZa
VIqJI9aMtnhVGzEqgYHU874E1C6WzepcQ/SnGEHrCsTIwLJMACqph6E8tDkm/IJp
1B5NlClOXPkjRjQWGME/dWdSDnZc7PnkWiXoNCGKFJCA8/Iz3mJzuN9wEaUzpauo
8DHMnJ25M317FdiDDk5N+4eFSxH/sSU0U/IQqMRBAiy50lACvk6I9+7JDuD3Vau2
YlJl2gMZJxQ7x4IptOIgC151sGmA0HVo8GrZrOcQi03JUgUeiMra6InlKlpnBerC
N0Ad8jPclKgEcUu7RGrt5MhE0h/e8wbFWOt+hiTWfkBE2PESKh47sj2fo4hEZr7G
t1EsnckeJeWlDE/XcbC67NzoMECMdk+Zpfx1yp4T00dkOsvOfP7JHDng31WTHFwi
IHah0dNaOVKul+0GM2nqRRqzIqRHx22fRCtTrWXgF3S66UWBPBaJuNYcXM7PVS/m

Bug#1058876: libopenmpi-dev: cmake builds do not find fortan mpimod in /usr/include

2023-12-17 Thread Drew Parsons

Package: libopenmpi-dev
Version: 4.1.6-2
Severity: serious
Justification: ftbfs (other)

openmpi 4.1.6-2 moved the fortran mod files from /usr/lib to
/usr/include.  This is probably correct, but has some consequences we
need to sort out. Applications using cmake for configuration are still
looking for the mod files in /usr/lib, so their builds now fail.

An example is adios2, with error message:

[384/1029] /usr/bin/gfortran 
-I/build/adios2-2.9.2+dfsg1/examples/hello/bpWriter 
-I/build/adios2-2.9.2+dfsg1/build-mpi/bindings/Fortran 
-I/usr/lib/x86_64-linux-gnu/fortran/gfortran-mod-15/openmpi -I/usr/lib/x86_
64-linux-gnu/openmpi/lib -g -O2 -ffile-prefix-map=/build/adios2-2.9.2+dfsg1=. 
-fstack-protector-strong -fstack-clash-protection -fcf-protection 
-Jexamples/hello/bpWriter -fpreprocessed -c examples/hello/bpWriter
/CMakeFiles/hello_bpWriter_f_mpi.dir/helloBPWriter.F90-pp.f90 -o 
examples/hello/bpWriter/CMakeFiles/hello_bpWriter_f_mpi.dir/helloBPWriter.F90.o
FAILED: 
examples/hello/bpWriter/CMakeFiles/hello_bpWriter_f_mpi.dir/helloBPWriter.F90.o 
/usr/bin/gfortran -I/build/adios2-2.9.2+dfsg1/examples/hello/bpWriter 
-I/build/adios2-2.9.2+dfsg1/build-mpi/bindings/Fortran 
-I/usr/lib/x86_64-linux-gnu/fortran/gfortran-mod-15/openmpi 
-I/usr/lib/x86_64-linux-gn
u/openmpi/lib -g -O2 -ffile-prefix-map=/build/adios2-2.9.2+dfsg1=. 
-fstack-protector-strong -fstack-clash-protection -fcf-protection 
-Jexamples/hello/bpWriter -fpreprocessed -c examples/hello/bpWriter/CMakeFiles
/hello_bpWriter_f_mpi.dir/helloBPWriter.F90-pp.f90 -o 
examples/hello/bpWriter/CMakeFiles/hello_bpWriter_f_mpi.dir/helloBPWriter.F90.o
/build/adios2-2.9.2+dfsg1/examples/hello/bpWriter/helloBPWriter.F90:3:9:

3 | use mpi
  | 1
Fatal Error: Cannot open module file ‘mpi.mod’ for reading at (1): No such file 
or directory
compilation terminated.

We can see that the compilation got configured to use
-I/usr/lib/x86_64-linux-gnu/fortran/gfortran-mod-15/openmpi
which would be why it can't find mpi.mod in /usr/include

As far as I can tell, adios2 is not making assumptions itself about
the location of the mod files.  I suspect the configuration is coming
from cmake's FindMPI.cmake

I guess we don't want openmpi 4.1.6-2 to migrate to testing until this
issue is resolved, which is why I've marked Severity: serious.

There are openmpi's pkgconfig files.
$ pkg-config --cflags mpi-fort
-I/usr/lib/x86_64-linux-gnu/openmpi/include 
-I/usr/lib/x86_64-linux-gnu/openmpi/include/openmpi 
-I/usr/lib/x86_64-linux-gnu/openmpi/lib 

The fortrandir variable set in ompi-fort.pc is also located in
/usr/lib (perhaps it should be so)

So /usr/include is not used in the include path flags. But /usr/lib is.
This must be the origin of the problem.  cmake's FindMPI.cmake does
indeed use pkgconfig to extract the paths:
"if(_MPI_PKG AND PKG_CONFIG_FOUND)"



-- System Information:
Debian Release: trixie/sid
  APT prefers unstable-debug
  APT policy: (500, 'unstable-debug'), (500, 'unstable'), (1, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 6.5.0-5-amd64 (SMP w/8 CPU threads; PREEMPT)
Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE
Locale: LANG=en_AU.UTF-8, LC_CTYPE=en_AU.UTF-8 (charmap=UTF-8), 
LANGUAGE=en_AU:en
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages libopenmpi-dev depends on:
ii  gfortran [gfortran-mod-15] 4:13.2.0-2
ii  gfortran-11 [gfortran-mod-15]  11.4.0-7
ii  gfortran-12 [gfortran-mod-15]  12.3.0-13
ii  gfortran-13 [gfortran-mod-15]  13.2.0-9
ii  libevent-dev   2.1.12-stable-8
ii  libhwloc-dev   2.10.0-1
ii  libibverbs-dev 48.0-1
ii  libjs-jquery   3.6.1+dfsg+~3.5.14-1
ii  libjs-jquery-ui1.13.2+dfsg-1
ii  libopenmpi34.1.6-2
ii  libpmix-dev5.0.1-4
ii  openmpi-bin4.1.6-2
ii  openmpi-common 4.1.6-2
ii  zlib1g-dev 1:1.3.dfsg-3

Versions of packages libopenmpi-dev recommends:
ii  libcoarrays-openmpi-dev  2.10.1-1+b1

Versions of packages libopenmpi-dev suggests:
pn  openmpi-doc  

-- no debconf information

Processed: Re: Bug#999968: sagan: depends on obsolete pcre3 library

2023-12-17 Thread Debian Bug Tracking System

Processing control commands:

> tags -1 + patch
Bug #68 [src:sagan] sagan: depends on obsolete pcre3 library
Added tag(s) patch.

-- 
68: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=68
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#999968: sagan: depends on obsolete pcre3 library

2023-12-17 Thread Yavor Doganov

Control: tags -1 + patch

Please find attached a patch, build-tested only.
Description: Port to PCRE2.
Bug-Debian: https://bugs.debian.org/68
Author: Yavor Doganov 
Forwarded: no
Last-Update: 2023-12-17
---

--- sagan-1.2.0.orig/configure.ac
+++ sagan-1.2.0/configure.ac
@@ -392,14 +392,25 @@
 CPPFLAGS="${CPPFLAGS} -I${with_libpcre_includes}"
 fi
 
-AC_CHECK_HEADER(pcre.h,,[AC_ERROR(pcre.h not found ...)])
+AC_CHECK_HEADER([pcre2.h], [], [AC_MSG_ERROR([pcre2.h not found ...])],
+[[#define PCRE2_CODE_UNIT_WIDTH 8
+]])
 
 if test "$with_libpcre_libraries" != "no"; then
 LDFLAGS="${LDFLAGS} -L${with_libpcre_libraries}"
 fi
 
 PCRE=""
-AC_CHECK_LIB(pcre, pcre_get_substring,, PCRE="no")
+LIBS="$LIBS -lpcre2-8"
+AC_MSG_CHECKING([for pcre library])
+AC_LINK_IFELSE(
+  [AC_LANG_PROGRAM([[#define PCRE2_CODE_UNIT_WIDTH 8
+#include 
+]],
+[[pcre2_match_data *md = pcre2_match_data_create(4, NULL);]])],
+  [AC_MSG_RESULT([yes])],
+  [AC_MSG_RESULT([no])
+   PCRE="no"])
 if test "$PCRE" = "no"; then
 echo
 echo "   ERROR!  pcre library not found, go get it"
@@ -408,98 +419,44 @@
 exit 1
 fi
 
-# libpcre 8.35 (especially on debian) has a known issue that results in 
segfaults
-if test "$with_libpcre_libraries" = "no"; then
-PKG_CHECK_MODULES(LIBPCREVERSION, [libpcre = 
8.35],[libpcre_buggy_found="yes"],[libprce_buggy_found="no"])
-if test "$libpcre_buggy_found" = "yes"; then
-echo
-echo "   Warning! vulnerable libpcre version 8.35 found"
-echo "   This version has a known issue that could result in segfaults"
-echo "   please upgrade to a newer version of pcre which you can get 
from"
-echo "   www.pcre.org. For more information, see issue #1693"
-echo
-echo "   Continuing for now with JIT disabled..."
-echo
-fi
-fi
-
-# To prevent duping the lib link we reset LIBS after this check. Setting 
action-if-found to NULL doesn't seem to work
-# see: http://blog.flameeyes.eu/2008/04/29/i-consider-ac_check_lib-harmful
-PCRE=""
-TMPLIBS="${LIBS}"
-AC_CHECK_LIB(pcre, pcre_dfa_exec,, PCRE="no")
-if test "$PCRE" = "no"; then
-echo
-echo "   ERROR!  pcre library was found but version was < 6.0"
-echo "   please upgrade to a newer version of pcre which you can get from"
-echo "   www.pcre.org."
-echo
-exit 1
-fi
-LIBS="${TMPLIBS}"
-
-AC_TRY_COMPILE([ #include  ],
-[ int eo = 0; eo |= PCRE_EXTRA_MATCH_LIMIT_RECURSION; ],
-[ pcre_match_limit_recursion_available=yes ], [:]
-)
-
-if test "$pcre_match_limit_recursion_available" != "yes"; then
-echo
-echo "   Warning! pcre extra opt PCRE_EXTRA_MATCH_LIMIT_RECURSION not 
found"
-echo "   This could lead to potential DoS please upgrade to pcre >= 6.5"
-echo "   from www.pcre.org."
-echo "   Continuing for now"
-echo
-AC_DEFINE([NO_PCRE_MATCH_RLIMIT],[1],[Pcre 
PCRE_EXTRA_MATCH_LIMIT_RECURSION not available])
-fi
-
-TMPCFLAGS="${CFLAGS}"
-CFLAGS="-O0 -g -Werror -Wall"
-AC_TRY_COMPILE([ #include  ],
-[ pcre_extra *extra = NULL; pcre_free_study(extra); ],
-[ AC_DEFINE([HAVE_PCRE_FREE_STUDY], [1], [Pcre pcre_free_study 
supported])], [:]
-)
-CFLAGS="${TMPCFLAGS}"
-
-
 #enable support for PCRE-jit available since pcre-8.20
 AC_MSG_CHECKING(for PCRE JIT support)
-AC_TRY_COMPILE([ #include  ],
-[
-int jit = 0;
-pcre_config(PCRE_CONFIG_JIT, );
-],
+AC_RUN_IFELSE(
+  [AC_LANG_PROGRAM([[#define PCRE2_CODE_UNIT_WIDTH 8
+#include 
+]],
+[[uint32_t jit = 0;
+  pcre2_config(PCRE2_CONFIG_JIT, );
+  if (jit)
+exit(EXIT_SUCCESS);
+  exit(EXIT_FAILURE);]])],
 [ pcre_jit_available=yes ], [ pcre_jit_available=no ]
 )
 
-# bug 1693, libpcre 8.35 is broken and debian jessie is still using that
-if test "$libpcre_buggy_found" = "yes"; then
-pcre_jit_available="no, libpcre 8.35 blacklisted"
-fi
-
 
 if test "x$pcre_jit_available" = "xyes"; then
AC_MSG_RESULT(yes)
AC_DEFINE([PCRE_HAVE_JIT], [1], [Pcre with JIT compiler support enabled])
 
AC_MSG_CHECKING(for PCRE JIT support usability)
-   AC_TRY_COMPILE([ #include  ],
-   [
-   const char* regexstr = "(a|b|c|d)";
-   pcre *re;
-   const char *error;
-   pcre_extra *extra;
-   int err_offset;
-   re = pcre_compile(regexstr,0, , _offset,NULL);
-   extra = pcre_study(re, PCRE_STUDY_JIT_COMPILE, );
-   if (extra == NULL)
-   exit(EXIT_FAILURE);
-   int jit = 0;
-   int ret = pcre_fullinfo(re, extra, PCRE_INFO_JIT, );
-   if (ret != 0 || jit != 1)
+   AC_RUN_IFELSE(
+ [AC_LANG_PROGRAM([[#define PCRE2_CODE_UNIT_WIDTH 8
+#include 
+]],
+   [[
+   PCRE2_SPTR regexstr = "(a|b|c|d)";
+   pcre2_code *re;
+   int error;
+   PCRE2_SIZE err_offset;
+   re = pcre2_compile(regexstr, PCRE2_ZERO_TERMINATED, 0,
+  , _offset, NULL);
+   pcre2_jit_compile(re, PCRE2_JIT_COMPLETE);
+   size_t jit = 0;
+   int ret = pcre2_pattern_info(re, PCRE2_INFO_JITSIZE,

Bug#1058367: marked as done (retroarch: FTBFS: SpirvIntrinsics.h:120:10: error: ‘variant’ in namespace ‘std’ does not name a template type)

2023-12-17 Thread Debian Bug Tracking System

Your message dated Sun, 17 Dec 2023 09:49:28 +
with message-id 
and subject line Bug#1058367: fixed in retroarch 1.16.0.3+dfsg-1
has caused the Debian Bug report #1058367,
regarding retroarch: FTBFS: SpirvIntrinsics.h:120:10: error: ‘variant’ in 
namespace ‘std’ does not name a template type
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.)


-- 
1058367: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1058367
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: retroarch
Version: 1.15.0+dfsg-1
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):
> /usr/bin/gcc -Wdate-time -D_FORTIFY_SOURCE=2 -g 
> -ffile-prefix-map=/<>=. -fstack-protector-strong 
> -fstack-clash-protection -Wformat -Werror=format-security -fcf-protection 
> -std=gnu99 -D_GNU_SOURCE -I. -ffast-math -Wall -Wno-unused-result 
> -Wno-unused-variable -finput-charset=UTF-8 -DQT_CORE_LIB 
> -I/usr/include/x86_64-linux-gnu/qt5/QtCore 
> -I/usr/include/x86_64-linux-gnu/qt5 -DQT_GUI_LIB 
> -I/usr/include/x86_64-linux-gnu/qt5/QtGui -I/usr/include/x86_64-linux-gnu/qt5 
> -DQT_CORE_LIB -I/usr/include/x86_64-linux-gnu/qt5/QtCore -DQT_WIDGETS_LIB 
> -I/usr/include/x86_64-linux-gnu/qt5/QtWidgets 
> -I/usr/include/x86_64-linux-gnu/qt5 
> -I/usr/include/x86_64-linux-gnu/qt5/QtCore -DQT_GUI_LIB 
> -I/usr/include/x86_64-linux-gnu/qt5/QtGui -DQT_CORE_LIB -DQT_CONCURRENT_LIB 
> -I/usr/include/x86_64-linux-gnu/qt5/QtConcurrent 
> -I/usr/include/x86_64-linux-gnu/qt5 -DQT_CORE_LIB 
> -I/usr/include/x86_64-linux-gnu/qt5/QtCore -DQT_NETWORK_LIB 
> -I/usr/include/x86_64-linux-gnu/qt5/QtNetwork 
> -I/usr/include/x86_64-linux-gnu/qt5 -DQT_CORE_LIB 
> -I/usr/include/x86_64-linux-gnu/qt5/QtCore -fPIC -msse -msse2 -D_REENTRANT 
> -I/usr/include/freetype2 -I/usr/include/libpng16   -I/usr/include/libdecor-0  
>-I/usr/include/dbus-1.0 -I/usr/lib/x86_64-linux-gnu/dbus-1.0/include  
> -I/usr/include/libdrm -I/usr/include/SDL2 -D_REENTRANT 
> -I/usr/include/x86_64-linux-gnu -I/usr/include/x86_64-linux-gnu 
> -I/usr/include/x86_64-linux-gnu -I/usr/include/x86_64-linux-gnu 
> -I/usr/include/x86_64-linux-gnu -Wno-deprecated-declarations -I./deps/7zip 
> -I./libretro-common/include -I./deps -I./deps  -Igfx/include 
> -I/usr/include/spirv_cross -I./deps/7zip -I./libretro-common/formats/libchdr 
> -Ideps/rcheevos/include -Ideps/discord-rpc/include -Iffmpeg 
> -I./deps/switchres -Ideps -Ideps/stb -DHAVE_CONFIG_H -DRARCH_INTERNAL 
> -D_FILE_OFFSET_BITS=64 -DGLOBAL_CONFIG_DIR='"/etc"' 
> -DASSETS_DIR='"/usr/share/retroarch"' -DFILTERS_DIR='"/usr/share/retroarch"' 
> -DCORE_INFO_DIR='"/usr/share/retroarch"' -DHAVE_LIBRETRODB -DHAVE_DYLIB 
> -DHAVE_FILE_LOGGER -DHAVE_SHADERPIPELINE -DHAVE_NETPLAYDISCOVERY 
> -DHAVE_GIT_VERSION -DGIT_VERSION='b2ceb50' -DHAVE_DR_MP3 -DHAVE_PATCH 
> -DHAVE_REWIND -DHAVE_CHEATS -DHAVE_CORE_INFO_CACHE -DHAVE_SCREENSHOTS 
> -DHAVE_VIDEO_FILTER -DHAVE_DSP_FILTER -DHAVE_NEAREST_RESAMPLER 
> -DHAVE_CONFIGFILE -DHAVE_AUDIOMIXER -DHAVE_BSV_MOVIE -DHAVE_RUNAHEAD 
> -DHAVE_CC_RESAMPLER -DHAVE_LANGEXTRA -DHAVE_IMAGEVIEWER -DHAVE_MAIN 
> -DHAVE_COMMAND -DHAVE_STDIN_CMD -DHAVE_TINYALSA -DHAVE_RWAV -DHAVE_MENU 
> -DHAVE_GFX_WIDGETS -DHAVE_RGUI -DHAVE_MATERIALUI -DHAVE_XMB -DHAVE_OZONE 
> -DHAVE_OVERLAY -DHAVE_STB_FONT -DHAVE_THREADS -DHAVE_THREAD_STORAGE 
> -DHAVE_LIBDECOR_H -DHAVE_X11 -DHAVE_OPENGL -DHAVE_OPENGL1 -DHAVE_GL_FFT 
> -DHAVE_GL_SYNC -DHAVE_EGL -DHAVE_VULKAN -DHAVE_OPENGL_CORE -DHAVE_GLSL 
> -DHAVE_SLANG -DHAVE_GLSLANG -DHAVE_SPIRV_CROSS -DHAVE_7ZIP -D_7ZIP_ST 
> -DHAVE_IBXM -DHAVE_FLAC -DHAVE_ZLIB -DHAVE_CHD -DWANT_SUBCODE 
> -DWANT_RAW_DATA_SECTOR -DHAVE_CDROM -DHAVE_RTGA -DHAVE_RPNG -DHAVE_RJPEG 
> -DHAVE_RBMP -DHAVE_VIDEOPROCESSOR -DHAVE_V4L2 -DHAVE_ACCESSIBILITY 
> -DHAVE_NETWORKING -DHAVE_IFINFO -DHAVE_NETWORK_CMD -DHAVE_CHEEVOS 
> -DRC_DISABLE_LUA -DHAVE_DISCORD -DHAVE_TRANSLATE -DHAVE_FFMPEG 
> -DSR_WITH_XRANDR -DHAVE_COMPRESSION -DHAVE_PRESENCE -MMD -c -o 
> obj-unix/release/./deps/7zip/Lzma2Dec.o deps/7zip/Lzma2Dec.c
> In file included from /usr/include/glslang/Include/Types.h:47,
>  from /usr/include/glslang/Include/intermediate.h:57,
>  from 
> /usr/include/glslang/MachineIndependent/localintermediate.h:42,
>  from /usr/include/glslang/SPIRV/SpvTools.h:50,
>  from /usr/include/glslang/SPIRV/GlslangToSpv.h:42,
>  from gfx/drivers_shader/glslang.cpp:25:
>

Bug#1058870: jq: Got illegal instruction in unit test in i386

2023-12-17 Thread 陳昌倬

Package: jq
Version: 1.7.1-1
Severity: serious
Tags: ftbfs
Justification: fails to build from source (but built successfully in the past)

jq failed to build in i386 with illegal instruction in unit test. The
following is build log


FAIL: tests/jqtest
FAIL: tests/mantest
FAIL: tests/utf8test
FAIL: tests/shtest
FAIL: tests/optionaltest
FAIL: tests/onigtest
FAIL: tests/base64test
FAIL: tests/manonigtest
==
   jq 1.7: ./test-suite.log
==

# TOTAL: 8
# PASS:  0
# SKIP:  0
# XFAIL: 0
# FAIL:  8
# XPASS: 0
# ERROR: 0

.. contents:: :depth: 2

FAIL: tests/mantest
===

==2576563== 
==2576563== Process terminating with default action of signal 4 (SIGILL)
==2576563==  Illegal opcode at address 0x40199A6
==2576563==at 0x40199A6: _dl_sysdep_parse_arguments (dl-sysdep.c:83)
==2576563==by 0x40199A6: _dl_sysdep_start (dl-sysdep.c:106)
==2576563==by 0x401B3C2: _dl_start_final (rtld.c:498)
==2576563==by 0x401B3C2: _dl_start (rtld.c:585)
==2576563==by 0x401A23A: ??? (in /usr/lib/i386-linux-gnu/ld-linux.so.2)
Illegal instruction
FAIL tests/mantest (exit status: 132)

FAIL: tests/jqtest
==

==2576560== 
==2576560== Process terminating with default action of signal 4 (SIGILL)
==2576560==  Illegal opcode at address 0x40199A6
==2576560==at 0x40199A6: _dl_sysdep_parse_arguments (dl-sysdep.c:83)
==2576560==by 0x40199A6: _dl_sysdep_start (dl-sysdep.c:106)
==2576560==by 0x401B3C2: _dl_start_final (rtld.c:498)
==2576560==by 0x401B3C2: _dl_start (rtld.c:585)
==2576560==by 0x401A23A: ??? (in /usr/lib/i386-linux-gnu/ld-linux.so.2)
Illegal instruction
FAIL tests/jqtest (exit status: 132)

FAIL: tests/shtest
==

+ . ./tests/setup
+ [ -n  ]
+ set -eu
+ dirname ./tests/shtest
+ cd ./tests
+ pwd
+ JQTESTDIR=/<>/tests
+ JQBASEDIR=/<>/tests/..
+ JQ=/<>/jq
+ [ -z  ]
+ which valgrind
+ VALGRIND=libtool --mode=execute -- valgrind --error-exitcode=1 
--leak-check=full
--suppressions=/<>/tests/onig.supp
--suppressions=/<>/tests/local.supp
+ VG_EXIT0=--error-exitcode=0
+ Q=-q
+ mods=/<>/tests/modules
+ clean=true
+ d=
+ trap clean EXIT
+ mktemp -d -t jqXX
+ d=/tmp/jqh5V7Wd
+ [ -z /tmp/jqh5V7Wd ]
+ msys=false
+ mingw=false
+ uname -s
+ JQ_NO_B=/<>/jq
+ JQ=/<>/jq -b
+ 
PATH=/<>/tests/..:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games
 /<>/tests/../tests/jq-f-test.sh
+ [ -f /<>/tests/../.libs/libinject_errors.so ]
+ printf a\0b\nc\0d\ne
+ libtool --mode=execute -- valgrind --error-exitcode=1 --leak-check=full 
--suppressions=/<>/tests/onig.supp 
--suppressions=/<>/tests/local.supp -q /<>/jq -b -Rse 
. == "a\ub\nc\ud\ne" /tmp/jqh5V7Wd/input
==2576629== 
==2576629== Process terminating with default action of signal 4 (SIGILL)
==2576629==  Illegal opcode at address 0x40199A6
==2576629==at 0x40199A6: _dl_sysdep_parse_arguments (dl-sysdep.c:83)
==2576629==by 0x40199A6: _dl_sysdep_start (dl-sysdep.c:106)
==2576629==by 0x401B3C2: _dl_start_final (rtld.c:498)
==2576629==by 0x401B3C2: _dl_start (rtld.c:585)
==2576629==by 0x401A23A: ??? (in /usr/lib/i386-linux-gnu/ld-linux.so.2)
Illegal instruction
+ clean
+ true
+ [ -n /tmp/jqh5V7Wd ]
+ rm -rf /tmp/jqh5V7Wd
FAIL tests/shtest (exit status: 132)

FAIL: tests/utf8test


==2576567== 
==2576567== Process terminating with default action of signal 4 (SIGILL)
==2576567==  Illegal opcode at address 0x40199A6
==2576567==at 0x40199A6: _dl_sysdep_parse_arguments (dl-sysdep.c:83)
==2576567==by 0x40199A6: _dl_sysdep_start (dl-sysdep.c:106)
==2576567==by 0x401B3C2: _dl_start_final (rtld.c:498)
==2576567==by 0x401B3C2: _dl_start (rtld.c:585)
==2576567==by 0x401A23A: ??? (in /usr/lib/i386-linux-gnu/ld-linux.so.2)
Illegal instruction
UTF-8 byte sequences that span the jv_load_file read buffer are mangled
FAIL tests/utf8test (exit status: 1)

FAIL: tests/base64test
==

==2576797== 
==2576797== Process terminating with default action of signal 4 (SIGILL)
==2576797==  Illegal opcode at address 0x40199A6
==2576797==at 0x40199A6: _dl_sysdep_parse_arguments (dl-sysdep.c:83)
==2576797==by 0x40199A6: _dl_sysdep_start (dl-sysdep.c:106)
==2576797==by 0x401B3C2: _dl_start_final (rtld.c:498)
==2576797==by 0x401B3C2: _dl_start (rtld.c:585)
==2576797==by 0x401A23A: ??? (in /usr/lib/i386-linux-gnu/ld-linux.so.2)
Illegal instruction
FAIL tests/base64test (exit status: 132)

FAIL: tests/optionaltest


==2576802== 
==2576802== Process terminating with default action of signal 4 (SIGILL)
==2576802==  Illegal opcode at address 0x40199A6
==2576802==at 0x40199A6: _dl_sysdep_parse_arguments (dl-sysdep.c:83)
==2576802==by 0x40199A6: _dl_sysdep_start (dl-sysdep.c:106)
==2576802==by 0x401B3C2: _dl_start_final (rtld.c:498)
==2576802==by 0x401B3C2: _dl_start (rtld.c:585)
==2576802==by

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

2023-12-17 Thread Debian Bug Tracking System

Your message dated Sun, 17 Dec 2023 08:49:37 +
with message-id 
and subject line Bug#1058413: fixed in python-pykka 4.0.1-1
has caused the Debian Bug report #1058413,
regarding python-pykka: FTBFS: dh_auto_test: error: pybuild --test 
--test-pytest -i python{version} -p "3.12 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.)


-- 
1058413: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1058413
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: python-pykka
Version: 4.0.0-1
Severity: serious
Justification: FTBFS
Tags: trixie sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20231212 ftbfs-trixie

Hi,

During a rebuild of all packages in sid, your package failed to build
on amd64.


Relevant part (hopefully):
>  debian/rules build
> dh build --with python3,sphinxdoc --buildsystem=pybuild
>dh_update_autotools_config -O--buildsystem=pybuild
>dh_autoreconf -O--buildsystem=pybuild
>dh_auto_configure -O--buildsystem=pybuild
>dh_auto_build -O--buildsystem=pybuild
> I: pybuild plugin_pyproject:110: Building wheel for python3.12 with "build" 
> module
> I: pybuild base:310: python3.12 -m build --skip-dependency-check 
> --no-isolation --wheel --outdir /<>/.pybuild/cpython3_3.12_pykka 
> * Building wheel...
> Successfully built pykka-4.0.0-py3-none-any.whl
> I: pybuild plugin_pyproject:122: Unpacking wheel built for python3.12 with 
> "installer" module
> I: pybuild plugin_pyproject:110: Building wheel for python3.11 with "build" 
> module
> I: pybuild base:310: python3.11 -m build --skip-dependency-check 
> --no-isolation --wheel --outdir /<>/.pybuild/cpython3_3.11_pykka 
> * Building wheel...
> Successfully built pykka-4.0.0-py3-none-any.whl
> I: pybuild plugin_pyproject:122: Unpacking wheel built for python3.11 with 
> "installer" module
>dh_auto_test -O--buildsystem=pybuild
> I: pybuild base:310: cd /<>/.pybuild/cpython3_3.12_pykka/build; 
> python3.12 -m pytest tests
> = test session starts 
> ==
> platform linux -- Python 3.12.1, pytest-7.4.3, pluggy-1.3.0
> rootdir: /<>/.pybuild/cpython3_3.12_pykka/build
> plugins: mock-3.12.0
> collected 148 items
> 
> tests/test_actor.py ...  [ 
> 12%]
> tests/test_future.py ...F[ 
> 29%]
> tests/test_logging.py ...[ 
> 33%]
> tests/test_ref.py ...[ 
> 49%]
> tests/test_registry.py   [ 
> 57%]
> tests/proxy/test_attribute_access.py [ 
> 62%]
> tests/proxy/test_dynamic_method_calls.py ..  [ 
> 64%]
> tests/proxy/test_mocking.py ...  [ 
> 66%]
> tests/proxy/test_proxy.py .  [ 
> 77%]
> tests/proxy/test_static_method_calls.py  [ 
> 83%]
> tests/proxy/test_traversable.py ..   [ 
> 87%]
> tests/proxy/test_typed_proxy.py  [ 
> 89%]
> tests/test_envelope.py . [ 
> 90%]
> tests/test_future.py ... [ 
> 92%]
> tests/test_logging.py .  [ 
> 93%]
> tests/test_messages.py   [ 
> 95%]
> tests/test_registry.py ..[ 
> 97%]
> tests/test_threading_actor.py ...[ 
> 99%]
> tests/proxy/test_traversable.py .
> [100%]
> 
> === FAILURES 
> ===
> __ test_future_supports_yield_from_syntax[threading] 
> ___
> 
> future = 
> 
> def test_future_supports_yield_from_syntax(
> future: Future[int],
> ) -> None:
> def get_value() -> Generator[None, None, int]:
> val = yield from future
> return val
> 
> future.set(1)
> >   assert run_async(get_value()) == 1
> 
> tests/test_future.py:153: 
> _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ 
> _ 
> tests/test_future.py:20: in run_async
> f = asyncio.ensure_future(coroutine, loop=loop)
> _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _

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

2023-12-17 Thread Paul Eggert


On 2023-12-16 13:46, Bernhard Voelker wrote:

Whether the implementation is race-prone or not is an internal thing.


I wasn't referring to the internal implementation. I was referring to cp 
users. With the newer Coreutils (FreeBSD) behavior, you can reliably 
write a script to do something if cp -n didn't copy the file because the 
destination already existed. With the older Coreutils behavior you 
cannot do that reliably; there will always be a race condition.

Processed: [python-multidict] Bug #1055717: forward to upstream issue with a commit that fix the failure

2023-12-17 Thread Debian Bug Tracking System

Processing commands for cont...@bugs.debian.org:

> forwarded 1055717 https://github.com/aio-libs/multidict/issues/868
Bug #1055717 [src:python-multidict] python-multidict ftbfs with Python 3.12
Set Bug forwarded-to-address to 
'https://github.com/aio-libs/multidict/issues/868'.
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
1055717: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1055717
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

68 matches

Mail list logo