date:20230204

Bug#1030480: puppetlabs-http-client-clojure: FTBFS: Cannot access clojars (https://repo.clojars.org/) in offline mode and the artifact compojure:compojure:jar:debian has not been downloaded from it be

2023-02-04 Thread Lucas Nussbaum

Source: puppetlabs-http-client-clojure
Version: 2.1.0-3
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20230203 ftbfs-bookworm

Hi,

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


Relevant part (hopefully):
> make[1]: Entering directory '/<>'
> ./dev-resources/gen-pki.sh
> 
> Generating primary self-signed CA
> ..++*+...+.+...+*++..++.++...+.+...+.+...+.+..+.+..+++..+..++..+..+..+.+++..+...+...++..+...+.+.++..+...++..+...+...++..++.+.+...+.+...+...+...++.+..+...+...+...++.+.+..+...+..+.+..+..+...+...+..+...+.+.+...+.++.+.+..+..+..+.+.+..+.+..+...+...+..+...+...+...+...+..+...++..+.+...++..+.+.+.+...+...+
> ...+...+.+...++.+*+..+.+..+.+...+..++*..+..+.+...+..+...+..+.+...+..++...++...+..+...+.+..+...+..+.+.+.+.+...+..+...+..+..++.+.+..+..++.+...++.+.+...+..+.+..+...+...+.+...+...+...+...+.+...+...+..+...++...+..+...+..+...+...+.+...+..+.+..+...+..+...+.+..+.++.+.+.+..+...+...+.+..+...+.+...+..++.+.++...+.+..++..++...++..+...+..+...+++...+..+..+.+.+...+...++...+...+...+..+...+...+.+..+..+...+..++...+..++.++...++...++...+
> -
> 
> Generating node cert
> 
> Creating node CSR
> 
> Signing node CSR
> Certificate request self-signature ok
> subject=C = US, ST = OR, L = Portland, O = "Puppet, Inc", CN = localhost
> 
> Generating alternate self-signed CA
> ..+..+..+*...+.+..+...+..+...+...+...+.+.+.+..+++...+..+*.++...+..+.+++.+.+.+..+...+.+...+...+..+.+.+..+.+..+.+..+.+..+...+.+.+.+...+..++..++...+..++.+..+.+..+...+.+.+..+..+..+.+...+...+.+.+.+.+.+..++.+.+.++...+++...++..+...+..+...+.+...+.++...+...+.+.+...++...+..+.++.+.+..+.+...++...+.+.+...+..+...+...++.+..+.+.+...+...++.+..+.+.+..+..+.+.++.+.+...+.+++...++..+..++..+...+.+...+...++...+.+...+...+..+...+...+...+.+.+..++
> ..+.+...+..+...++.+...++*.+.+...+.+.+..+.+.+.+...+.+..+...+..+...+++...+...++..+.+...+..+.+...+..+...+*.+.

Bug#1030481: scanmem: FTBFS: make: *** [debian/rules:6: binary] Error 25

2023-02-04 Thread Lucas Nussbaum

Source: scanmem
Version: 0.17-4
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20230203 ftbfs-bookworm

Hi,

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


Relevant part (hopefully):
> make[3]: Entering directory '/<>'
>  /bin/mkdir -p '/<>/debian/tmp/usr/lib/scanmem'
>  /bin/bash ./libtool   --mode=install /usr/bin/install -c   libscanmem.la 
> '/<>/debian/tmp/usr/lib/scanmem'
> libtool: install: /usr/bin/install -c .libs/libscanmem.so.1.0.0 
> /<>/debian/tmp/usr/lib/scanmem/libscanmem.so.1.0.0
> libtool: install: (cd /<>/debian/tmp/usr/lib/scanmem && { ln -s 
> -f libscanmem.so.1.0.0 libscanmem.so.1 || { rm -f libscanmem.so.1 && ln -s 
> libscanmem.so.1.0.0 libscanmem.so.1; }; })
> libtool: install: (cd /<>/debian/tmp/usr/lib/scanmem && { ln -s 
> -f libscanmem.so.1.0.0 libscanmem.so || { rm -f libscanmem.so && ln -s 
> libscanmem.so.1.0.0 libscanmem.so; }; })
> libtool: install: /usr/bin/install -c .libs/libscanmem.lai 
> /<>/debian/tmp/usr/lib/scanmem/libscanmem.la
> libtool: install: /usr/bin/install -c .libs/libscanmem.a 
> /<>/debian/tmp/usr/lib/scanmem/libscanmem.a
> libtool: install: chmod 644 
> /<>/debian/tmp/usr/lib/scanmem/libscanmem.a
> libtool: install: ranlib 
> /<>/debian/tmp/usr/lib/scanmem/libscanmem.a
> libtool: warning: remember to run 'libtool --finish /usr/lib/scanmem'
>  /bin/mkdir -p '/<>/debian/tmp/usr/bin'
>   /bin/bash ./libtool   --mode=install /usr/bin/install -c scanmem 
> '/<>/debian/tmp/usr/bin'
> libtool: warning: 'libscanmem.la' has not been installed in '/usr/lib/scanmem'
> libtool: install: /usr/bin/install -c .libs/scanmem 
> /<>/debian/tmp/usr/bin/scanmem
>  /bin/mkdir -p '/<>/debian/tmp/usr/share/doc/scanmem'
>  /usr/bin/install -c -m 644 README 
> '/<>/debian/tmp/usr/share/doc/scanmem'
>  /bin/mkdir -p '/<>/debian/tmp/usr/include/scanmem'
>  /usr/bin/install -c -m 644 commands.h list.h maps.h scanmem.h scanroutines.h 
> sets.h show_message.h targetmem.h value.h 
> '/<>/debian/tmp/usr/include/scanmem'
>  /bin/mkdir -p '/<>/debian/tmp/usr/share/man/man1'
>  /usr/bin/install -c -m 644 scanmem.1 
> '/<>/debian/tmp/usr/share/man/man1'
> make[3]: Leaving directory '/<>'
> make[2]: Leaving directory '/<>'
> make[1]: Leaving directory '/<>'
>dh_install
>dh_installdocs
>dh_installchangelogs
>dh_installman
>dh_python3
> I: dh_python3 tools:114: replacing shebang in 
> debian/gameconqueror/usr/share/gameconqueror/GameConqueror.py
>dh_icons
>dh_perl
>dh_link
>dh_strip_nondeterminism
>   Normalized 
> debian/gameconqueror/usr/share/locale/sr_ME/LC_MESSAGES/GameConqueror.mo
>   Normalized 
> debian/gameconqueror/usr/share/locale/it/LC_MESSAGES/GameConqueror.mo
>   Normalized 
> debian/gameconqueror/usr/share/locale/ja/LC_MESSAGES/GameConqueror.mo
>   Normalized 
> debian/gameconqueror/usr/share/locale/de/LC_MESSAGES/GameConqueror.mo
>   Normalized 
> debian/gameconqueror/usr/share/locale/ru/LC_MESSAGES/GameConqueror.mo
>   Normalized 
> debian/gameconqueror/usr/share/locale/es/LC_MESSAGES/GameConqueror.mo
>dh_compress
>dh_fixperms
>dh_missing
> dh_missing: warning: 
> usr/share/gameconqueror/__pycache__/GameConqueror.cpython-311.opt-1.pyc 
> exists in debian/tmp but is not installed to anywhere 
> dh_missing: warning: 
> usr/share/gameconqueror/__pycache__/GameConqueror.cpython-311.pyc exists in 
> debian/tmp but is not installed to anywhere 
> dh_missing: warning: 
> usr/share/gameconqueror/__pycache__/backend.cpython-311.opt-1.pyc exists in 
> debian/tmp but is not installed to anywhere 
> dh_missing: warning: 
> usr/share/gameconqueror/__pycache__/backend.cpython-311.pyc exists in 
> debian/tmp but is not installed to anywhere 
> dh_missing: warning: 
> usr/share/gameconqueror/__pycache__/consts.cpython-311.opt-1.pyc exists in 
> debian/tmp but is not installed to anywhere 
> dh_missing: warning: 
> usr/share/gameconqueror/__pycache__/consts.cpython-311.pyc exists in 
> debian/tmp but is not installed to anywhere 
> dh_missing: warning: 
> usr/share/gameconqueror/__pycache__/hexview.cpython-311.opt-1.pyc exists in 
> debian/tmp but is not installed to anywhere 
> dh_missing: warning: 
> usr/share/gameconqueror/__pycache__/hexview.cpython-311.pyc exists in 
> debian/tmp but is not installed to anywhere 
> dh_missing: warning: 
> usr/share/gameconqueror/__pycache__/misc.cpython-311.opt-1.pyc exists in 
> debian/tmp but is not installed to anywhere 
> dh_missing: warning: usr/share/gameconqueror/__pycache__/misc.cpython-311.pyc 
> exists in debian/tmp but is not installed to anywhere 
> dh_missing: error: missing files, aborting
>   The following debhelper tools have reported what they installed (with 
> files per package)
>* dh_install: gameconqueror (22), scanmem (4)
>* dh_installdocs: gameconqueror (0), scanmem (0)
>* dh_installman: gameconqueror (1), scanmem (1)
>   If the missing fil

Bug#1030482: python-grpc-tools: FTBFS: dpkg-buildpackage: error: dpkg-source -b . subprocess returned exit status 2

2023-02-04 Thread Lucas Nussbaum

Source: python-grpc-tools
Version: 1.14.1-5
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20230203 ftbfs-bookworm

Hi,

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


Relevant part (hopefully):
>  debian/rules clean
> dh clean  --with python3 --buildsystem=pybuild
>dh_auto_clean -O--buildsystem=pybuild
> I: pybuild base:240: python3.11 setup.py clean 
> /usr/lib/python3/dist-packages/Cython/Compiler/Main.py:369: FutureWarning: 
> Cython directive 'language_level' not set, using 2 for now (Py2). This will 
> change in a later release! File: 
> /<>/grpc_tools/_protoc_compiler.pyx
>   tree = Parsing.p_module(s, pxd, full_module_name)
> Compiling grpc_tools/_protoc_compiler.pyx because it depends on 
> /usr/lib/python3/dist-packages/Cython/Includes/libc/__init__.pxd.
> [1/1] Cythonizing grpc_tools/_protoc_compiler.pyx
> running clean
> removing '/<>/.pybuild/cpython3_3.11_grpcio-tools/build' (and 
> everything under it)
> 'build/bdist.linux-x86_64' does not exist -- can't clean it
> 'build/scripts-3.11' does not exist -- can't clean it
>dh_autoreconf_clean -O--buildsystem=pybuild
>dh_clean -O--buildsystem=pybuild
>  dpkg-source -b .
> dpkg-source: info: using source format '3.0 (quilt)'
> dpkg-source: info: building python-grpc-tools using existing 
> ./python-grpc-tools_1.14.1.orig.tar.gz
> dpkg-source: info: using patch list from debian/patches/series
> dpkg-source: info: local changes detected, the modified files are:
>  python-grpc-tools-1.14.1/grpc_tools/_protoc_compiler.cpp
> dpkg-source: error: aborting due to unexpected upstream changes, see 
> /tmp/python-grpc-tools_1.14.1-5.diff.3w6asb
> dpkg-source: info: Hint: make sure the version in debian/changelog matches 
> the unpacked source tree
> dpkg-source: info: you can integrate the local changes with dpkg-source 
> --commit
> dpkg-buildpackage: error: dpkg-source -b . subprocess returned exit status 2
> 
> Build finished at 2023-02-04T02:49:52Z


The full build log is available from:
http://qa-logs.debian.net/2023/02/03/python-grpc-tools_1.14.1-5_unstable.log

All bugs filed during this archive rebuild are listed at:
https://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=ftbfs-20230203;users=lu...@debian.org
or:
https://udd.debian.org/bugs/?release=na&merged=ign&fnewerval=7&flastmodval=7&fusertag=only&fusertagtag=ftbfs-20230203&fusertaguser=lu...@debian.org&allbugs=1&cseverity=1&ctags=1&caffected=1#results

A list of current common problems and possible solutions is available at
http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute!

If you reassign this bug to another package, please mark it as 'affects'-ing
this package. See https://www.debian.org/Bugs/server-control#affects

If you fail to reproduce this, please provide a build log and diff it with mine
so that we can identify if something relevant changed in the meantime.

Bug#1030483: beginend-el: FTBFS: error: (file-missing (lambda (arg72 &rest arg73) (let ((f #'message)) (apply f arg72 arg73))) "Setting current directory" "No such file or directory" "/tmp/temp-fs-MQA

2023-02-04 Thread Lucas Nussbaum

Source: beginend-el
Version: 2.3.0-1
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20230203 ftbfs-bookworm

Hi,

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


Relevant part (hopefully):
> make[1]: Entering directory '/<>'
> skipping upstream build
> make[1]: Leaving directory '/<>'
>dh_elpa_test
>   buttercup -L .
> Loading /etc/emacs/site-start.d/00debian.el (source)...
> Loading /etc/emacs/site-start.d/50autoconf.el (source)...
> Loading /<>/test/test-helper.el (source)...
> Loading /<>/test/test-helper.el (source)...
> Loading /<>/test/test-helper.el (source)...
> Loading /<>/test/test-helper.el (source)...
> Loading /<>/test/test-helper.el (source)...
> Running 40 specs.
> 
> beginend in a dired buffer
>   ignores . and .. at the beginningMark set
> 
> [32m  ignores . and .. at the beginning[0m (37.46ms)
>   ignores . and .. at the endMark set
> 
> [32m  ignores . and .. at the end[0m (7.07ms)
>   ignores . at the beginning and .. at the endMark set
> 
> [32m  ignores . at the beginning and .. at the end[0m (6.98ms)
>   ignores . and .. in the middleMark set
> 
> [32m  ignores . and .. in the middle[0m (6.22ms)
>   ignores . and .. when they are hiddenMark set
> 
> [32m  ignores . and .. when they are hidden[0m (5.17ms)
>   ignores . and .. when they are not hiddenMark set
> 
> [32m  ignores . and .. when they are not hidden[0m (10.38ms)
>   ignores . and .. when they are hidden and the directory is emptyMark set
> 
> [32m  ignores . and .. when they are hidden and the directory is empty[0m 
> (4.45ms)
>   ignores . and .. when they are not hidden and the directory is emptyMark set
> 
> [32m  ignores . and .. when they are not hidden and the directory is 
> empty[0m (4.19ms)
> 
> beginend
>   pushes mark
> when going to beginning
>   if point is not at beginningMark set
> 
> [31m  if point is not at beginning[0m[31m  FAILED[0m (71.18ms)
>   only onceMark set
> 
> [31m  only once[0m[31m  FAILED[0m (38.91ms)
> when going to end
>   if point is not at endMark set
> 
> [31m  if point is not at end[0m[31m  FAILED[0m (26.99ms)
>   only onceMark set
> 
> [31m  only once[0m[31m  FAILED[0m (25.86ms)
>   does not push mark
> when going to beginning
>   if point is already at beginning
> [31m  if point is already at beginning[0m[31m  FAILED[0m (3.40ms)
>   if point is at point-min
> [31m  if point is at point-min[0m[31m  FAILED[0m (25.63ms)
> when going to end
>   if point is already at end
> [31m  if point is already at end[0m[31m  FAILED[0m (25.09ms)
>   if point is at point-max
> [31m  if point is at point-max[0m[31m  FAILED[0m (26.64ms)
> 
> beginend, when narrowing is active,
>   goes to point-min if beginning is outside the narrowed region
> [31m  goes to point-min if beginning is outside the narrowed region[0m[31m 
>  FAILED[0m (3.86ms)
>   goes to beginning if beginning is inside the narrowed regionMark set
> 
> [31m  goes to beginning if beginning is inside the narrowed region[0m[31m  
> FAILED[0m (24.96ms)
>   goes to point-max if end is outside the narrowed region
> [31m  goes to point-max if end is outside the narrowed region[0m[31m  
> FAILED[0m (25.26ms)
>   goes to end if end is inside the narrowed region
> [31m  goes to end if end is inside the narrowed region[0m[31m  FAILED[0m 
> (29.04ms)
>   does not move point
> when going to beginning and beginning outside the narrowed region if 
> point is already at point-min
> [31mwhen going to beginning and beginning outside the narrowed region if 
> point is already at point-min[0m[31m  FAILED[0m (3.46ms)
> when going to end and end outside the narrowed region if point is already 
> at point-max
> [31mwhen going to end and end outside the narrowed region if point is 
> already at point-max[0m[31m  FAILED[0m (26.75ms)
>   does not mark
> when going to beginning and beginning outside the narrowed region if 
> point is already at point-min
> [31mwhen going to beginning and beginning outside the narrowed region if 
> point is already at point-min[0m[31m  FAILED[0m (25.69ms)
> when going to end and end outside the narrowed region if point is already 
> at point-max
> [31mwhen going to end and end outside the narrowed region if point is 
> already at point-max[0m[31m  FAILED[0m (25.68ms)
>   correctly detects out of bounds
> when point is before point-min
> [31mwhen point is before point-min[0m[31m  FAILED[0m (3.43ms)
> when point is after point-max
> [31mwhen point is after point-max[0m[31m  FAILED[0m (25.50ms)
> when point is between point-min point-max
> [31mwhen point is between point-min point-max[0m[31m  FAILED[0m 
> (32.25ms)
> 
> beginend
>   in org-mode
> goes back to position 0 if that's a headingMark set
> 
> [32mgoes

Bug#1030486: pytest-qt: FTBFS: dpkg-buildpackage: error: dpkg-source -b . subprocess returned exit status 2

2023-02-04 Thread Lucas Nussbaum

Source: pytest-qt
Version: 4.2.0-1
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20230203 ftbfs-bookworm

Hi,

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


Relevant part (hopefully):
> make[2]: Entering directory '/<>/docs'
> rm -rf _build/*
> make[2]: Leaving directory '/<>/docs'
> make[1]: Leaving directory '/<>'
>dh_autoreconf_clean -O--buildsystem=pybuild
>dh_clean -O--buildsystem=pybuild
>  dpkg-source -b .
> dpkg-source: info: using options from pytest-qt-4.2.0/debian/source/options: 
> --extend-diff-ignore=^[^/]+\.egg-info/
> dpkg-source: info: using source format '3.0 (quilt)'
> dpkg-source: info: building pytest-qt using existing 
> ./pytest-qt_4.2.0.orig.tar.gz
> dpkg-source: info: using patch list from debian/patches/series
> dpkg-source: info: local changes detected, the modified files are:
>  pytest-qt-4.2.0/src/pytestqt/_version.py
> dpkg-source: error: aborting due to unexpected upstream changes, see 
> /tmp/pytest-qt_4.2.0-1.diff.3bxLOS
> dpkg-source: info: Hint: make sure the version in debian/changelog matches 
> the unpacked source tree
> dpkg-source: info: you can integrate the local changes with dpkg-source 
> --commit
> dpkg-buildpackage: error: dpkg-source -b . subprocess returned exit status 2
> 
> Build finished at 2023-02-04T03:00:28Z


The full build log is available from:
http://qa-logs.debian.net/2023/02/03/pytest-qt_4.2.0-1_unstable.log

All bugs filed during this archive rebuild are listed at:
https://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=ftbfs-20230203;users=lu...@debian.org
or:
https://udd.debian.org/bugs/?release=na&merged=ign&fnewerval=7&flastmodval=7&fusertag=only&fusertagtag=ftbfs-20230203&fusertaguser=lu...@debian.org&allbugs=1&cseverity=1&ctags=1&caffected=1#results

A list of current common problems and possible solutions is available at
http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute!

If you reassign this bug to another package, please mark it as 'affects'-ing
this package. See https://www.debian.org/Bugs/server-control#affects

If you fail to reproduce this, please provide a build log and diff it with mine
so that we can identify if something relevant changed in the meantime.

Bug#1030487: python-trustme: FTBFS: dh_auto_test: error: pybuild --test --test-pytest -i python{version} -p 3.11 returned exit code 13

2023-02-04 Thread Lucas Nussbaum

Source: python-trustme
Version: 0.9.0-1.1
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20230203 ftbfs-bookworm

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 --buildsystem=pybuild
>dh_update_autotools_config -O--buildsystem=pybuild
>dh_autoreconf -O--buildsystem=pybuild
>dh_auto_configure -O--buildsystem=pybuild
> I: pybuild base:240: python3.11 setup.py config 
> running config
>dh_auto_build -O--buildsystem=pybuild
> I: pybuild base:240: /usr/bin/python3 setup.py build 
> running build
> running build_py
> creating /<>/.pybuild/cpython3_3.11/build/trustme
> copying trustme/__init__.py -> 
> /<>/.pybuild/cpython3_3.11/build/trustme
> copying trustme/__main__.py -> 
> /<>/.pybuild/cpython3_3.11/build/trustme
> copying trustme/_cli.py -> 
> /<>/.pybuild/cpython3_3.11/build/trustme
> copying trustme/_version.py -> 
> /<>/.pybuild/cpython3_3.11/build/trustme
> copying trustme/py.typed -> 
> /<>/.pybuild/cpython3_3.11/build/trustme
>dh_auto_test -O--buildsystem=pybuild
> I: pybuild base:240: cd /<>/.pybuild/cpython3_3.11/build; 
> python3.11 -m pytest tests
> = test session starts 
> ==
> platform linux -- Python 3.11.1, pytest-7.2.1, pluggy-1.0.0+repack
> rootdir: /<>
> collected 10 items / 1 error
> 
>  ERRORS 
> 
> _ ERROR collecting .pybuild/cpython3_3.11/build/tests/test_trustme.py 
> __
> ImportError while importing test module 
> '/<>/.pybuild/cpython3_3.11/build/tests/test_trustme.py'.
> Hint: make sure your test modules/packages have valid Python names.
> Traceback:
> /usr/lib/python3.11/importlib/__init__.py:126: in import_module
> return _bootstrap._gcd_import(name[level:], package, level)
> tests/test_trustme.py:21: in 
> import service_identity.pyopenssl  # type: ignore[import]
> /usr/lib/python3/dist-packages/service_identity/__init__.py:7: in 
> from . import cryptography, pyopenssl
> /usr/lib/python3/dist-packages/service_identity/pyopenssl.py:9: in 
> import six
> E   ModuleNotFoundError: No module named 'six'
> === short test summary info 
> 
> ERROR tests/test_trustme.py
>  Interrupted: 1 error during collection 
> 
> === 1 error in 0.18s 
> ===
> E: pybuild pybuild:388: test: plugin distutils failed with: exit code=2: cd 
> /<>/.pybuild/cpython3_3.11/build; python3.11 -m pytest tests
> dh_auto_test: error: pybuild --test --test-pytest -i python{version} -p 3.11 
> returned exit code 13


The full build log is available from:
http://qa-logs.debian.net/2023/02/03/python-trustme_0.9.0-1.1_unstable.log

All bugs filed during this archive rebuild are listed at:
https://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=ftbfs-20230203;users=lu...@debian.org
or:
https://udd.debian.org/bugs/?release=na&merged=ign&fnewerval=7&flastmodval=7&fusertag=only&fusertagtag=ftbfs-20230203&fusertaguser=lu...@debian.org&allbugs=1&cseverity=1&ctags=1&caffected=1#results

A list of current common problems and possible solutions is available at
http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute!

If you reassign this bug to another package, please mark it as 'affects'-ing
this package. See https://www.debian.org/Bugs/server-control#affects

If you fail to reproduce this, please provide a build log and diff it with mine
so that we can identify if something relevant changed in the meantime.

Bug#1030485: uima-as: FTBFS: [ERROR] Failed to execute goal on project uima-as: Could not resolve dependencies for project org.apache.uima:uima-as:pom:2.3.1: Cannot access eclipsePlugins (http://repo1

2023-02-04 Thread Lucas Nussbaum

Source: uima-as
Version: 2.3.1-9
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20230203 ftbfs-bookworm

Hi,

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


Relevant part (hopefully):
> make[1]: Entering directory '/<>'
> dh_auto_build -Duima-as
>   cd uima-as && /usr/lib/jvm/default-java/bin/java -noverify -cp 
> /usr/share/maven/boot/plexus-classworlds-2.x.jar 
> -Dmaven.home=/usr/share/maven 
> -Dmaven.multiModuleProjectDirectory=/<> 
> -Dclassworlds.conf=/etc/maven/m2-debian.conf 
> -Dproperties.file.manual=/<>/debian/maven.properties 
> org.codehaus.plexus.classworlds.launcher.Launcher 
> -s/etc/maven/settings-debian.xml -Ddebian.dir=/<>/debian 
> -Dmaven.repo.local=/<>/debian/maven-repo --batch-mode package 
> javadoc:jar javadoc:aggregate -DskipTests -Dnotimestamp=true -Dlocale=en_US
> OpenJDK 64-Bit Server VM warning: Options -Xverify:none and -noverify were 
> deprecated in JDK 13 and will likely be removed in a future release.
> [0m[0m[INFO] Scanning for projects...
> [INFO] 
> 
> [INFO] Reactor Build Order:
> [INFO] 
> [INFO] UIMA-AS: uima-as-parent
> [pom]
> [INFO] UIMA-AS: uimaj-as-core 
> [jar]
> [INFO] UIMA-AS: uimaj-as-jms  
> [jar]
> [INFO] UIMA-AS: uimaj-as-activemq 
> [jar]
> [INFO] UIMA AS: uimaj-as-osgi-runtime 
> [jar]
> [INFO] UIMA-AS Aggregate: aggregate-uima-as-eclipse-plugins   
> [pom]
> [INFO] UIMA-AS Aggregate: aggregate-uima-as   
> [pom]
> [INFO] UIMA-AS: uima-as   
> [pom]
> [WARNING] The artifact org.apache.maven.plugins:maven-clean-plugin:jar:2.5 
> has been relocated to org.apache.maven.plugins:maven-clean-plugin:jar:3.2.0
> [WARNING] The artifact org.apache.maven.plugins:maven-install-plugin:jar:2.4 
> has been relocated to org.apache.maven.plugins:maven-install-plugin:jar:3.1.0
> [WARNING] The artifact org.apache.maven.plugins:maven-deploy-plugin:jar:2.7 
> has been relocated to org.apache.maven.plugins:maven-deploy-plugin:jar:3.0.0
> [WARNING] The POM for org.apache.maven.plugins:maven-site-plugin:jar:3.3 is 
> missing, no dependency information available
> [WARNING] Failed to retrieve plugin descriptor for 
> org.apache.maven.plugins:maven-site-plugin:3.3: Plugin 
> org.apache.maven.plugins:maven-site-plugin:3.3 or one of its dependencies 
> could not be resolved: Cannot access central 
> (https://repo.maven.apache.org/maven2) in offline mode and the artifact 
> org.apache.maven.plugins:maven-site-plugin:jar:3.3 has not been downloaded 
> from it before.
> [WARNING] The artifact org.apache.maven.plugins:maven-antrun-plugin:jar:1.3 
> has been relocated to org.apache.maven.plugins:maven-antrun-plugin:jar:3.1.0
> [WARNING] The POM for 
> org.apache.maven.plugins:maven-assembly-plugin:jar:2.2-beta-5 is missing, no 
> dependency information available
> [WARNING] Failed to retrieve plugin descriptor for 
> org.apache.maven.plugins:maven-assembly-plugin:2.2-beta-5: Plugin 
> org.apache.maven.plugins:maven-assembly-plugin:2.2-beta-5 or one of its 
> dependencies could not be resolved: Cannot access central 
> (https://repo.maven.apache.org/maven2) in offline mode and the artifact 
> org.apache.maven.plugins:maven-assembly-plugin:jar:2.2-beta-5 has not been 
> downloaded from it before.
> [WARNING] The artifact 
> org.apache.maven.plugins:maven-dependency-plugin:jar:2.8 has been relocated 
> to org.apache.maven.plugins:maven-dependency-plugin:jar:3.5.0
> [WARNING] The POM for org.apache.maven.plugins:maven-release-plugin:jar:2.5.3 
> is missing, no dependency information available
> [WARNING] Failed to retrieve plugin descriptor for 
> org.apache.maven.plugins:maven-release-plugin:2.5.3: Plugin 
> org.apache.maven.plugins:maven-release-plugin:2.5.3 or one of its 
> dependencies could not be resolved: Cannot access central 
> (https://repo.maven.apache.org/maven2) in offline mode and the artifact 
> org.apache.maven.plugins:maven-release-plugin:jar:2.5.3 has not been 
> downloaded from it before.
> [WARNING] The POM for org.apache.maven.plugins:maven-site-plugin:jar:3.3 is 
> missing, no dependency information available
> [WARNING] Failed to retrieve plugin descriptor for 
> org.apache.maven.plugins:maven-site-plugin:3.3: Plugin 
> org.apache.maven.plugins:maven-site-plugin:3.3 or one of its dependencies 
> could not be resolved: Cannot access central 
> (https://repo.maven.apache.org/maven2) in offline mode and the artifact 
> org.apache.maven.plugins:maven-site-plugin:jar:3.3 has not been downloaded 
> from it before.
> [WARNING] The POM for 
> org.apache.maven.plugins:maven-assembly-plugin:jar:2.2-beta-5 is missing, n

Bug#1030488: trapperkeeper-webserver-jetty9-clojure: FTBFS: Cannot access clojars (https://repo.clojars.org/) in offline mode and the artifact puppetlabs:ring-middleware:jar:debian has not been downlo

2023-02-04 Thread Lucas Nussbaum

Source: trapperkeeper-webserver-jetty9-clojure
Version: 4.4.1-2
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20230203 ftbfs-bookworm

Hi,

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


Relevant part (hopefully):
> make[1]: Entering directory '/<>'
> lein test
> Cannot access central (https://repo1.maven.org/maven2/) in offline mode and 
> the artifact puppetlabs:trapperkeeper-webserver-jetty9:jar:debian has not 
> been downloaded from it before.
> Cannot access clojars (https://repo.clojars.org/) in offline mode and the 
> artifact puppetlabs:trapperkeeper-webserver-jetty9:jar:debian has not been 
> downloaded from it before.
> Cannot access central (https://repo1.maven.org/maven2/) in offline mode and 
> the artifact puppetlabs:trapperkeeper-webserver-jetty9:jar:test:debian has 
> not been downloaded from it before.
> Cannot access clojars (https://repo.clojars.org/) in offline mode and the 
> artifact puppetlabs:trapperkeeper-webserver-jetty9:jar:test:debian has not 
> been downloaded from it before.
> Cannot access central (https://repo1.maven.org/maven2/) in offline mode and 
> the artifact puppetlabs:ring-middleware:jar:debian has not been downloaded 
> from it before.
> Cannot access clojars (https://repo.clojars.org/) in offline mode and the 
> artifact puppetlabs:ring-middleware:jar:debian has not been downloaded from 
> it before.
> This could be due to a typo in :dependencies, file system permissions, or 
> network issues.
> If you are behind a proxy, try setting the 'http_proxy' environment variable.
> make[1]: *** [debian/rules:26: override_dh_auto_test] Error 1


The full build log is available from:
http://qa-logs.debian.net/2023/02/03/trapperkeeper-webserver-jetty9-clojure_4.4.1-2_unstable.log

All bugs filed during this archive rebuild are listed at:
https://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=ftbfs-20230203;users=lu...@debian.org
or:
https://udd.debian.org/bugs/?release=na&merged=ign&fnewerval=7&flastmodval=7&fusertag=only&fusertagtag=ftbfs-20230203&fusertaguser=lu...@debian.org&allbugs=1&cseverity=1&ctags=1&caffected=1#results

A list of current common problems and possible solutions is available at
http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute!

If you reassign this bug to another package, please mark it as 'affects'-ing
this package. See https://www.debian.org/Bugs/server-control#affects

If you fail to reproduce this, please provide a build log and diff it with mine
so that we can identify if something relevant changed in the meantime.

Bug#1030489: tiledb-py: FTBFS: tiledb/cc/array.cc:149:11: error: no matching function for call to ‘pybind11::class_::def(const char [13], )’

2023-02-04 Thread Lucas Nussbaum

Source: tiledb-py
Version: 0.19.1-1
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20230203 ftbfs-bookworm

Hi,

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


Relevant part (hopefully):
> x86_64-linux-gnu-gcc -Wsign-compare -DNDEBUG -g -fwrapv -O2 -Wall -g 
> -fstack-protector-strong -Wformat -Werror=format-security -g -fwrapv -O2 -g 
> -O2 -ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat 
> -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -fPIC 
> -I/usr/lib/python3/dist-packages/pybind11/include 
> -I/usr/lib/python3/dist-packages/numpy/core/include -I/usr/include/python3.11 
> -c tiledb/cc/array.cc -o 
> build/temp.linux-x86_64-cpython-311/tiledb/cc/array.o -fvisibility=hidden -g 
> -O2 -ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat 
> -Werror=format-security -std=c++17 -Wno-deprecated-declarations 
> -fvisibility=hidden
> tiledb/cc/array.cc: In function ‘void 
> libtiledbcpp::init_array(pybind11::module&)’:
> tiledb/cc/array.cc:149:11: error: no matching function for call to 
> ‘pybind11::class_::def(const char [13],  function type>)’
>15 |   py::class_(m, "Array")
>   |   ~
>16 |   //.def(py::init py::object,
>   |   
> ~
>17 |   //  py::object, py::object>())
>   |   ~~
>18 |   .def(
>   |   ~
>19 |   py::init tiledb_query_type_t>(),
>   |   
> ~~
>20 |   py::keep_alive<1, 2>() /* Array keeps Context alive */)
>   |   ~~~
>21 |   // TODO capsule Array(const Context& ctx, tiledb_array_t* 
> carray,
>   |   
> ~
>22 |   // tiledb_config_t* config)
>   |   ~~~
>23 |   .def("is_open", &Array::is_open)
>   |   
>24 |   .def("uri", &Array::uri)
>   |   
>25 |   .def("schema", &Array::schema)
>   |   ~~
>26 |   //.def("ptr", [](Array& arr){ return py::capsule(arr.ptr()); } )
>   |   
>27 |   // open with encryption key
>   |   ~~~
>28 |   .def("open",
>   |   
>29 |(void (Array::*)(tiledb_query_type_t, 
> tiledb_encryption_type_t,
>   |
> ~~~
>30 | const std::string &)) &
>   | ~~~
>31 |Array::open)
>   |
>32 |   // open with encryption key and timestamp
>   |   ~
>33 |   .def("open",
>   |   
>34 |(void (Array::*)(tiledb_query_type_t, 
> tiledb_encryption_type_t,
>   |
> ~~~
>35 | const std::string &, uint64_t)) &
>   | ~
>36 |Array::open)
>   |
>37 |   .def("reopen", &Array::reopen)
>   |   ~~
>38 |   .def("set_open_timestamp_start", 
> &Array::set_open_timestamp_start)
>   |   
> ~~
>39 |   .def("set_open_timestamp_end", &Array::set_open_timestamp_end)
>   |   ~~
>40 |   .def_property_readonly("open_timestamp_start",
>   |   ~~
>41 |  &Array::open_timestamp_start)
>   |  ~
>42 |   .def_property_readonly("open_timestamp_end", 
> &Array::open_timestamp_end)
>   |   
> 
>43 |   .def("set_config", &Array::set_config)
>   |   ~~
>44 |   .def("config", &Array::config)
>   |   ~~
>45 |   .def("close", &Array::close)
>   |   
>46 |   .def("consolidate",
>   |   ~~~
>47 |py::overload_cast   |~~~
>48 |

Bug#1030490: ndcube: FTBFS: dh_auto_test: error: pybuild --test -i python{version} -p 3.11 returned exit code 13

2023-02-04 Thread Lucas Nussbaum

Source: ndcube
Version: 2.0.2-2
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20230203 ftbfs-bookworm

Hi,

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


Relevant part (hopefully):
> make[1]: Entering directory '/<>'
> dh_auto_build
> I: pybuild base:240: /usr/bin/python3 setup.py build 
> /usr/lib/python3/dist-packages/setuptools/config/setupcfg.py:515: 
> SetuptoolsDeprecationWarning: The license_file parameter is deprecated, use 
> license_files instead.
>   warnings.warn(msg, warning_class)
> running build
> running build_py
> creating /<>/.pybuild/cpython3_3.11_ndcube/build/ndcube
> copying ndcube/__init__.py -> 
> /<>/.pybuild/cpython3_3.11_ndcube/build/ndcube
> copying ndcube/ndcube.py -> 
> /<>/.pybuild/cpython3_3.11_ndcube/build/ndcube
> copying ndcube/ndcube_sequence.py -> 
> /<>/.pybuild/cpython3_3.11_ndcube/build/ndcube
> copying ndcube/global_coords.py -> 
> /<>/.pybuild/cpython3_3.11_ndcube/build/ndcube
> copying ndcube/conftest.py -> 
> /<>/.pybuild/cpython3_3.11_ndcube/build/ndcube
> copying ndcube/_version.py -> 
> /<>/.pybuild/cpython3_3.11_ndcube/build/ndcube
> copying ndcube/version.py -> 
> /<>/.pybuild/cpython3_3.11_ndcube/build/ndcube
> copying ndcube/ndcollection.py -> 
> /<>/.pybuild/cpython3_3.11_ndcube/build/ndcube
> creating 
> /<>/.pybuild/cpython3_3.11_ndcube/build/ndcube/visualization
> copying ndcube/visualization/__init__.py -> 
> /<>/.pybuild/cpython3_3.11_ndcube/build/ndcube/visualization
> copying ndcube/visualization/base.py -> 
> /<>/.pybuild/cpython3_3.11_ndcube/build/ndcube/visualization
> copying ndcube/visualization/plotting_utils.py -> 
> /<>/.pybuild/cpython3_3.11_ndcube/build/ndcube/visualization
> copying ndcube/visualization/mpl_sequence_plotter.py -> 
> /<>/.pybuild/cpython3_3.11_ndcube/build/ndcube/visualization
> copying ndcube/visualization/mpl_plotter.py -> 
> /<>/.pybuild/cpython3_3.11_ndcube/build/ndcube/visualization
> copying ndcube/visualization/descriptor.py -> 
> /<>/.pybuild/cpython3_3.11_ndcube/build/ndcube/visualization
> creating /<>/.pybuild/cpython3_3.11_ndcube/build/ndcube/utils
> copying ndcube/utils/__init__.py -> 
> /<>/.pybuild/cpython3_3.11_ndcube/build/ndcube/utils
> copying ndcube/utils/wcs.py -> 
> /<>/.pybuild/cpython3_3.11_ndcube/build/ndcube/utils
> copying ndcube/utils/cube.py -> 
> /<>/.pybuild/cpython3_3.11_ndcube/build/ndcube/utils
> copying ndcube/utils/collection.py -> 
> /<>/.pybuild/cpython3_3.11_ndcube/build/ndcube/utils
> copying ndcube/utils/sequence.py -> 
> /<>/.pybuild/cpython3_3.11_ndcube/build/ndcube/utils
> copying ndcube/utils/misc.py -> 
> /<>/.pybuild/cpython3_3.11_ndcube/build/ndcube/utils
> copying ndcube/utils/wcs_high_level_conversion.py -> 
> /<>/.pybuild/cpython3_3.11_ndcube/build/ndcube/utils
> creating /<>/.pybuild/cpython3_3.11_ndcube/build/ndcube/wcs
> copying ndcube/wcs/__init__.py -> 
> /<>/.pybuild/cpython3_3.11_ndcube/build/ndcube/wcs
> creating /<>/.pybuild/cpython3_3.11_ndcube/build/ndcube/tests
> copying ndcube/tests/__init__.py -> 
> /<>/.pybuild/cpython3_3.11_ndcube/build/ndcube/tests
> copying ndcube/tests/test_sequence_plotting.py -> 
> /<>/.pybuild/cpython3_3.11_ndcube/build/ndcube/tests
> copying ndcube/tests/test_ndcube.py -> 
> /<>/.pybuild/cpython3_3.11_ndcube/build/ndcube/tests
> copying ndcube/tests/test_ndcollection.py -> 
> /<>/.pybuild/cpython3_3.11_ndcube/build/ndcube/tests
> copying ndcube/tests/test_ndcubesequence.py -> 
> /<>/.pybuild/cpython3_3.11_ndcube/build/ndcube/tests
> copying ndcube/tests/helpers.py -> 
> /<>/.pybuild/cpython3_3.11_ndcube/build/ndcube/tests
> copying ndcube/tests/test_global_coords.py -> 
> /<>/.pybuild/cpython3_3.11_ndcube/build/ndcube/tests
> creating 
> /<>/.pybuild/cpython3_3.11_ndcube/build/ndcube/extra_coords
> copying ndcube/extra_coords/__init__.py -> 
> /<>/.pybuild/cpython3_3.11_ndcube/build/ndcube/extra_coords
> copying ndcube/extra_coords/extra_coords.py -> 
> /<>/.pybuild/cpython3_3.11_ndcube/build/ndcube/extra_coords
> copying ndcube/extra_coords/table_coord.py -> 
> /<>/.pybuild/cpython3_3.11_ndcube/build/ndcube/extra_coords
> creating /<>/.pybuild/cpython3_3.11_ndcube/build/ndcube/mixins
> copying ndcube/mixins/__init__.py -> 
> /<>/.pybuild/cpython3_3.11_ndcube/build/ndcube/mixins
> copying ndcube/mixins/ndslicing.py -> 
> /<>/.pybuild/cpython3_3.11_ndcube/build/ndcube/mixins
> creating 
> /<>/.pybuild/cpython3_3.11_ndcube/build/ndcube/utils/tests
> copying ndcube/utils/tests/__init__.py -> 
> /<>/.pybuild/cpython3_3.11_ndcube/build/ndcube/utils/tests
> copying ndcube/utils/tests/test_utils_sequence.py -> 
> /<>/.pybuild/cpython3_3.11_ndcube/build/ndcube/utils/tests
> copying ndcube/utils/tests/test_utils_wcs.py -> 
> /<>/.pybuild/cpython3_3.11_ndcube/build/ndcube/utils/tests
> copying ndcube/utils/tests/test_utils_collection.py -> 
> /<>/.pybuild/cpython3_3.11_ndcube/build/ndcube/utils/tests
> creating 
> /<>/.pybuild/cpython3_3.11_ndcube/buil

Bug#1030492: pyorbital: FTBFS: AssertionError: 0.7875583269985472 != 0.7875583269985473

2023-02-04 Thread Lucas Nussbaum

Source: pyorbital
Version: 1.7.3-1
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20230203 ftbfs-bookworm

Hi,

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


Relevant part (hopefully):
> make[1]: Entering directory '/<>'
> dh_auto_build --buildsystem=pybuild
>   pybuild --build -i python{version} -p 3.11
> I: pybuild base:240: /usr/bin/python3 setup.py build 
> running build
> running build_py
> creating /<>/.pybuild/cpython3_3.11_pyorbital/build/pyorbital
> copying pyorbital/__init__.py -> 
> /<>/.pybuild/cpython3_3.11_pyorbital/build/pyorbital
> copying pyorbital/geoloc_example.py -> 
> /<>/.pybuild/cpython3_3.11_pyorbital/build/pyorbital
> copying pyorbital/tlefile.py -> 
> /<>/.pybuild/cpython3_3.11_pyorbital/build/pyorbital
> copying pyorbital/orbital.py -> 
> /<>/.pybuild/cpython3_3.11_pyorbital/build/pyorbital
> copying pyorbital/astronomy.py -> 
> /<>/.pybuild/cpython3_3.11_pyorbital/build/pyorbital
> copying pyorbital/geoloc.py -> 
> /<>/.pybuild/cpython3_3.11_pyorbital/build/pyorbital
> copying pyorbital/geoloc_instrument_definitions.py -> 
> /<>/.pybuild/cpython3_3.11_pyorbital/build/pyorbital
> copying pyorbital/version.py -> 
> /<>/.pybuild/cpython3_3.11_pyorbital/build/pyorbital
> creating 
> /<>/.pybuild/cpython3_3.11_pyorbital/build/pyorbital/tests
> copying pyorbital/tests/__init__.py -> 
> /<>/.pybuild/cpython3_3.11_pyorbital/build/pyorbital/tests
> copying pyorbital/tests/test_orbital.py -> 
> /<>/.pybuild/cpython3_3.11_pyorbital/build/pyorbital/tests
> copying pyorbital/tests/test_tlefile.py -> 
> /<>/.pybuild/cpython3_3.11_pyorbital/build/pyorbital/tests
> copying pyorbital/tests/test_astronomy.py -> 
> /<>/.pybuild/cpython3_3.11_pyorbital/build/pyorbital/tests
> copying pyorbital/tests/test_geoloc.py -> 
> /<>/.pybuild/cpython3_3.11_pyorbital/build/pyorbital/tests
> copying pyorbital/tests/test_aiaa.py -> 
> /<>/.pybuild/cpython3_3.11_pyorbital/build/pyorbital/tests
> creating /<>/.pybuild/cpython3_3.11_pyorbital/build/pyorbital/etc
> copying pyorbital/etc/platforms.txt -> 
> /<>/.pybuild/cpython3_3.11_pyorbital/build/pyorbital/etc
> running build_scripts
> creating build
> creating build/scripts-3.11
> copying and adjusting bin/fetch_tles.py -> build/scripts-3.11
> changing mode of build/scripts-3.11/fetch_tles.py from 644 to 755
> PYTHONPATH=. python3 -m sphinx -N -bhtml doc/source/ doc/build/html # HTML 
> generator
> Running Sphinx v5.3.0
> making output directory... done
> WARNING: html_static_path entry '.static' does not exist
> building [mo]: targets for 0 po files that are out of date
> building [html]: targets for 1 source files that are out of date
> updating environment: [new config] 1 added, 0 changed, 0 removed
> reading sources... [100%] index
> 
> /<>/pyorbital/orbital.py:docstring of 
> pyorbital.orbital.Orbital.get_equatorial_crossing_time:10: ERROR: Unexpected 
> indentation.
> /<>/pyorbital/orbital.py:docstring of 
> pyorbital.orbital.OrbitElements:3: WARNING: Block quote ends without a blank 
> line; unexpected unindent.
> /<>/pyorbital/tlefile.py:docstring of pyorbital.tlefile:1: 
> WARNING: Include file '/<>/etc/platforms.txt' not found or 
> reading it failed
> looking for now-outdated files... none found
> pickling environment... done
> checking consistency... done
> preparing documents... done
> writing output... [100%] index
> 
> generating indices... genindex py-modindex done
> writing additional pages... search done
> copying static files... done
> copying extra files... done
> dumping search index in English (code: en)... done
> dumping object inventory... done
> build succeeded, 4 warnings.
> 
> The HTML pages are in doc/build/html.
> make[1]: Leaving directory '/<>'
>dh_auto_test -O--buildsystem=pybuild
>   pybuild --test -i python{version} -p 3.11
> I: pybuild base:240: python3.11 setup.py test 
> running test
> WARNING: Testing via this command is deprecated and will be removed in a 
> future version. Users looking for a generic test entry point independent of 
> test runner are encouraged to use tox.
> running egg_info
> creating pyorbital.egg-info
> writing pyorbital.egg-info/PKG-INFO
> writing dependency_links to pyorbital.egg-info/dependency_links.txt
> writing requirements to pyorbital.egg-info/requires.txt
> writing top-level names to pyorbital.egg-info/top_level.txt
> writing manifest file 'pyorbital.egg-info/SOURCES.txt'
> reading manifest file 'pyorbital.egg-info/SOURCES.txt'
> reading manifest template 'MANIFEST.in'
> warning: no files found matching 'README'
> adding license file 'LICENSE.txt'
> writing manifest file 'pyorbital.egg-info/SOURCES.txt'
> running build_ext
> test_aiaa (pyorbital.tests.test_aiaa.AIAAIntegrationTest.test_aiaa)
> Do the tests against AIAA test cases. ... ok
> test_from_file (pyorbital.tests.test_tlefile.TLETest.test_from_file)
> Test reading and parsing from a file. ... 
> /<>/pyorbital/tlefile.py:284: ResourceW

Bug#1030493: python-inotify: FTBFS: dh_auto_test: error: pybuild --test --test-pytest -i python{version} -p 3.11 returned exit code 13

2023-02-04 Thread Lucas Nussbaum

Source: python-inotify
Version: 0.2.10-3
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20230203 ftbfs-bookworm

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:240: python3.11 setup.py config 
> running config
>dh_auto_build -O--buildsystem=pybuild
> I: pybuild base:240: /usr/bin/python3 setup.py build 
> running build
> running build_py
> creating /<>/.pybuild/cpython3_3.11_python-inotify/build/inotify
> copying inotify/__init__.py -> 
> /<>/.pybuild/cpython3_3.11_python-inotify/build/inotify
> copying inotify/test_support.py -> 
> /<>/.pybuild/cpython3_3.11_python-inotify/build/inotify
> copying inotify/adapters.py -> 
> /<>/.pybuild/cpython3_3.11_python-inotify/build/inotify
> copying inotify/constants.py -> 
> /<>/.pybuild/cpython3_3.11_python-inotify/build/inotify
> copying inotify/library.py -> 
> /<>/.pybuild/cpython3_3.11_python-inotify/build/inotify
> copying inotify/calls.py -> 
> /<>/.pybuild/cpython3_3.11_python-inotify/build/inotify
> running egg_info
> creating inotify.egg-info
> writing inotify.egg-info/PKG-INFO
> writing dependency_links to inotify.egg-info/dependency_links.txt
> writing top-level names to inotify.egg-info/top_level.txt
> writing manifest file 'inotify.egg-info/SOURCES.txt'
> reading manifest file 'inotify.egg-info/SOURCES.txt'
> reading manifest template 'MANIFEST.in'
> adding license file 'LICENSE'
> writing manifest file 'inotify.egg-info/SOURCES.txt'
> /usr/lib/python3/dist-packages/setuptools/command/build_py.py:202: 
> SetuptoolsDeprecationWarning: Installing 'inotify.resources' as data is 
> deprecated, please list it in `packages`.
> !!
> 
> 
> 
> # Package would be ignored #
> 
> Python recognizes 'inotify.resources' as an importable package,
> but it is not listed in the `packages` configuration of setuptools.
> 
> 'inotify.resources' has been automatically added to the distribution only
> because it may contain data files, but this behavior is likely to change
> in future versions of setuptools (and therefore is considered deprecated).
> 
> Please make sure that 'inotify.resources' is included as a package by 
> using
> the `packages` configuration field or the proper discovery methods
> (for example by using `find_namespace_packages(...)`/`find_namespace:`
> instead of `find_packages(...)`/`find:`).
> 
> You can read more about "package discovery" and "data files" on setuptools
> documentation page.
> 
> 
> !!
> 
>   check.warn(importable)
> creating 
> /<>/.pybuild/cpython3_3.11_python-inotify/build/inotify/resources
> copying inotify/resources/README.rst -> 
> /<>/.pybuild/cpython3_3.11_python-inotify/build/inotify/resources
> copying inotify/resources/requirements.txt -> 
> /<>/.pybuild/cpython3_3.11_python-inotify/build/inotify/resources
>dh_auto_test -O--buildsystem=pybuild
> I: pybuild base:240: cd 
> /<>/.pybuild/cpython3_3.11_python-inotify/build; python3.11 -m 
> pytest -k 'not test__cycle'
> = test session starts 
> ==
> platform linux -- Python 3.11.1, pytest-7.2.1, pluggy-1.0.0+repack
> rootdir: /<>
> collected 9 items / 3 deselected / 6 selected
> 
> tests/test_inotify.py .s...F 
> [100%]
> 
> === FAILURES 
> ===
>  TestInotifyTree.test__renames 
> _
> 
> self = 
> 
> def test__renames(self):
> 
> # Since we're not reading the events one at a time in a loop and
> # removing or renaming folders will flush any queued events, we have 
> to
> # group things in order to check things first before such operations.
> 
> with inotify.test_support.temp_path() as path:
> i = inotify.adapters.InotifyTree(path)
> 
> old_path = os.path.join(path, 'old_folder')
> new_path = os.path.join(path, 'new_folder')
> 
> os.mkdir(old_path)
> 
> events1 = self.__read_all_events(i)
> 
> expected = [
> (inotify.adapters._INOTIFY_EVENT(wd=1, mask=1073742080, 
> cookie=events1[0][0].cookie, len=16), ['IN_CREATE', 'IN_ISDIR'], path, 
> 'old_folder'),
> ]
> 
> self.assertEquals(events1, expected)
> 
> 
> os.rename(old_path, new_path)
> 
> events2 = self.__read_all_events(i)
> 
> expected = [
> (inotify.adapters._INOTIFY_EVENT(wd=1, mask=1073741888, 
> cook

Bug#1030494: cross-toolchain-base-mipsen: FTBFS: build-dependency not installable: linux-source-6.0 (>= 6.0.12)

2023-02-04 Thread Lucas Nussbaum

Source: cross-toolchain-base-mipsen
Version: 23
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20230203 ftbfs-bookworm

Hi,

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


Relevant part (hopefully):
> +--+
> | Install package build dependencies  
>  |
> +--+
> 
> 
> Setup apt archive
> -
> 
> Merged Build-Depends: binutils-multiarch, dpkg (>= 1.21.17), rdfind, 
> symlinks, lsb-release, binutils-source (>= 2.39-1~), glibc-source (>= 
> 2.36-7~), gcc-12-source (>= 12.2.0-7~), linux-source-6.0 (>= 6.0.12), 
> linux-libc-dev (>= 6.0.12), autoconf (>= 2.69), autoconf2.69, autogen, 
> automake, bison (>= 1:2.3), chrpath, debhelper-compat (= 13), dpkg-dev (>= 
> 1.15.3.1), fakeroot, file, flex, dwz, debugedit (>= 4.16), gawk, gettext, 
> gperf (>= 3.0.1), kernel-wedge (>= 2.24), libisl-dev, libmpc-dev, libelf-dev, 
> libmpfr-dev (>= 2.3.0), rsync, xmlto, libtool, lzma, m4, make (>= 3.81), kmod 
> | module-init-tools, patchutils, procps, quilt, coreutils (>= 2.26) | 
> realpath (>= 1.9.12), sed (>= 4.0.5-4), sharutils, tar (>= 1.22), xz-utils, 
> asciidoc, texinfo, cpio, python3, bc, time, libconfig-auto-perl, 
> libfile-temp-perl, libfile-homedir-perl, liblocale-gettext-perl, 
> libunwind-dev, libjansson-dev, pkg-config, build-essential, fakeroot
> Merged Build-Conflicts: binutils-mips-linux-gnu, 
> binutils-mips64-linux-gnuabi64, binutils-mips64-linux-gnuabin32, 
> binutils-mips64el-linux-gnuabi64, binutils-mips64el-linux-gnuabin32, 
> binutils-mipsel-linux-gnu, binutils-mipsisa32r6-linux-gnu, 
> binutils-mipsisa32r6el-linux-gnu, binutils-mipsisa64r6-linux-gnuabi64, 
> binutils-mipsisa64r6-linux-gnuabin32, binutils-mipsisa64r6el-linux-gnuabi64, 
> binutils-mipsisa64r6el-linux-gnuabin32, dpkg-cross, libc6-i386, 
> libc6-mips-cross, libc6-mips64-cross, libc6-mips64el-cross, 
> libc6-mips64r6-cross, libc6-mips64r6el-cross, libc6-mipsel-cross, 
> libc6-mipsn32-cross, libc6-mipsn32el-cross, libc6-mipsn32r6-cross, 
> libc6-mipsn32r6el-cross, libc6-mipsr6-cross, libc6-mipsr6el-cross, libc6-x32, 
> libdebian-dpkgcross-perl, linux-libc-dev-mips-cross, 
> linux-libc-dev-mips64-cross, linux-libc-dev-mips64el-cross, 
> linux-libc-dev-mips64r6-cross, linux-libc-dev-mips64r6el-cross, 
> linux-libc-dev-mipsel-cross, linux-libc-dev-mipsn32-cross, 
> linux-libc-dev-mipsn32el-cross, linux-libc-dev-mipsn32r6-cross, 
> linux-libc-dev-mipsn32r6el-cross, linux-libc-dev-mipsr6-cross, 
> linux-libc-dev-mipsr6el-cross
> Filtered Build-Depends: binutils-multiarch, dpkg (>= 1.21.17), rdfind, 
> symlinks, lsb-release, binutils-source (>= 2.39-1~), glibc-source (>= 
> 2.36-7~), gcc-12-source (>= 12.2.0-7~), linux-source-6.0 (>= 6.0.12), 
> linux-libc-dev (>= 6.0.12), autoconf (>= 2.69), autoconf2.69, autogen, 
> automake, bison (>= 1:2.3), chrpath, debhelper-compat (= 13), dpkg-dev (>= 
> 1.15.3.1), fakeroot, file, flex, dwz, debugedit (>= 4.16), gawk, gettext, 
> gperf (>= 3.0.1), kernel-wedge (>= 2.24), libisl-dev, libmpc-dev, libelf-dev, 
> libmpfr-dev (>= 2.3.0), rsync, xmlto, libtool, lzma, m4, make (>= 3.81), 
> kmod, patchutils, procps, quilt, coreutils (>= 2.26), sed (>= 4.0.5-4), 
> sharutils, tar (>= 1.22), xz-utils, asciidoc, texinfo, cpio, python3, bc, 
> time, libconfig-auto-perl, libfile-temp-perl, libfile-homedir-perl, 
> liblocale-gettext-perl, libunwind-dev, libjansson-dev, pkg-config, 
> build-essential, fakeroot
> Filtered Build-Conflicts: binutils-mips-linux-gnu, 
> binutils-mips64-linux-gnuabi64, binutils-mips64-linux-gnuabin32, 
> binutils-mips64el-linux-gnuabi64, binutils-mips64el-linux-gnuabin32, 
> binutils-mipsel-linux-gnu, binutils-mipsisa32r6-linux-gnu, 
> binutils-mipsisa32r6el-linux-gnu, binutils-mipsisa64r6-linux-gnuabi64, 
> binutils-mipsisa64r6-linux-gnuabin32, binutils-mipsisa64r6el-linux-gnuabi64, 
> binutils-mipsisa64r6el-linux-gnuabin32, dpkg-cross, libc6-i386, 
> libc6-mips-cross, libc6-mips64-cross, libc6-mips64el-cross, 
> libc6-mips64r6-cross, libc6-mips64r6el-cross, libc6-mipsel-cross, 
> libc6-mipsn32-cross, libc6-mipsn32el-cross, libc6-mipsn32r6-cross, 
> libc6-mipsn32r6el-cross, libc6-mipsr6-cross, libc6-mipsr6el-cross, libc6-x32, 
> libdebian-dpkgcross-perl, linux-libc-dev-mips-cross, 
> linux-libc-dev-mips64-cross, linux-libc-dev-mips64el-cross, 
> linux-libc-dev-mips64r6-cross, linux-libc-dev-mips64r6el-cross, 
> linux-libc-dev-mipsel-cross, linux-libc-dev-mipsn32-cross, 
> linux-libc-dev-mipsn32el-cross, linux-libc-dev-mipsn32r6-cross, 
> linux-libc-dev-mipsn32r6el-cross, linux-libc-dev-mipsr6-cross, 
> linux-libc-dev-mipsr6el-cross
> dpkg-deb: building package 'sbuild-build-depends-main-dummy' in 
> '/<>/apt_archive/sbuild-build-depends-main-dummy.deb'.
> Ign:1 copy:/<>/apt_archive ./ InRelease
> G

Bug#1030495: navarp: FTBFS: AttributeError: module 'numpy' has no attribute 'complex'

2023-02-04 Thread Lucas Nussbaum

Source: navarp
Version: 1.3.0-1
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20230203 ftbfs-bookworm

Hi,

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


Relevant part (hopefully):
> make[1]: Entering directory '/<>'
> dh_auto_build
> I: pybuild base:240: /usr/bin/python3 setup.py build 
> running build
> running build_py
> file navarp.py (for module navarp) not found
> creating /<>/.pybuild/cpython3_3.11_navarp/build/navarp
> copying navarp/__init__.py -> 
> /<>/.pybuild/cpython3_3.11_navarp/build/navarp
> copying navarp/navarp_gui.py -> 
> /<>/.pybuild/cpython3_3.11_navarp/build/navarp
> creating /<>/.pybuild/cpython3_3.11_navarp/build/navarp/utils
> copying navarp/utils/__init__.py -> 
> /<>/.pybuild/cpython3_3.11_navarp/build/navarp/utils
> copying navarp/utils/kinterp.py -> 
> /<>/.pybuild/cpython3_3.11_navarp/build/navarp/utils
> copying navarp/utils/navplt.py -> 
> /<>/.pybuild/cpython3_3.11_navarp/build/navarp/utils
> copying navarp/utils/navfile.py -> 
> /<>/.pybuild/cpython3_3.11_navarp/build/navarp/utils
> copying navarp/utils/isomclass.py -> 
> /<>/.pybuild/cpython3_3.11_navarp/build/navarp/utils
> copying navarp/utils/fermilevel.py -> 
> /<>/.pybuild/cpython3_3.11_navarp/build/navarp/utils
> copying navarp/utils/isocut.py -> 
> /<>/.pybuild/cpython3_3.11_navarp/build/navarp/utils
> copying navarp/utils/ktransf.py -> 
> /<>/.pybuild/cpython3_3.11_navarp/build/navarp/utils
> creating /<>/.pybuild/cpython3_3.11_navarp/build/navarp/extras
> copying navarp/extras/__init__.py -> 
> /<>/.pybuild/cpython3_3.11_navarp/build/navarp/extras
> copying navarp/extras/simulation.py -> 
> /<>/.pybuild/cpython3_3.11_navarp/build/navarp/extras
> running egg_info
> creating navarp.egg-info
> writing navarp.egg-info/PKG-INFO
> writing dependency_links to navarp.egg-info/dependency_links.txt
> writing entry points to navarp.egg-info/entry_points.txt
> writing requirements to navarp.egg-info/requires.txt
> writing top-level names to navarp.egg-info/top_level.txt
> writing manifest file 'navarp.egg-info/SOURCES.txt'
> file navarp.py (for module navarp) not found
> reading manifest file 'navarp.egg-info/SOURCES.txt'
> reading manifest template 'MANIFEST.in'
> adding license file 'LICENSE'
> adding license file 'AUTHORS.rst'
> writing manifest file 'navarp.egg-info/SOURCES.txt'
> /usr/lib/python3/dist-packages/setuptools/command/build_py.py:202: 
> SetuptoolsDeprecationWarning: Installing 'navarp.gui' as data is 
> deprecated, please list it in `packages`.
> !!
> 
> 
> 
> # Package would be ignored #
> 
> Python recognizes 'navarp.gui' as an importable package,
> but it is not listed in the `packages` configuration of setuptools.
> 
> 'navarp.gui' has been automatically added to the distribution only
> because it may contain data files, but this behavior is likely to change
> in future versions of setuptools (and therefore is considered deprecated).
> 
> Please make sure that 'navarp.gui' is included as a package by using
> the `packages` configuration field or the proper discovery methods
> (for example by using `find_namespace_packages(...)`/`find_namespace:`
> instead of `find_packages(...)`/`find:`).
> 
> You can read more about "package discovery" and "data files" on setuptools
> documentation page.
> 
> 
> !!
> 
>   check.warn(importable)
> /usr/lib/python3/dist-packages/setuptools/command/build_py.py:202: 
> SetuptoolsDeprecationWarning: Installing 'navarp.gui.icons' as data is 
> deprecated, please list it in `packages`.
> !!
> 
> 
> 
> # Package would be ignored #
> 
> Python recognizes 'navarp.gui.icons' as an importable package,
> but it is not listed in the `packages` configuration of setuptools.
> 
> 'navarp.gui.icons' has been automatically added to the distribution only
> because it may contain data files, but this behavior is likely to change
> in future versions of setuptools (and therefore is considered deprecated).
> 
> Please make sure that 'navarp.gui.icons' is included as a package by using
> the `packages` configuration field or the proper discovery methods
> (for example by using `find_namespace_packages(...)`/`find_namespace:`
> instead of `find_packages(...)`/`find:`).
> 
> You can read more about "package discovery" and "data files" on setuptools
> documentation page.
> 
> 
> !!
> 
>   check.warn(importable)
> creating /<>/.pybuild/cpython3_3.11_navarp/build/navarp/gui
> copying navarp/gui/about.ui -> 
> /<>/.pybuild/cpython3_3.11_navarp/build/navarp/gui
> copying navarp/gui/export.ui -> 
> /<>/.pybuild/cpython3_3.11_navarp/build/navarp/gui
> copying navarp/gui/main.ui -> 
> /<>/.pybuild/cpython3_3.11_navarp/build/navarp/gui
> creating /<>/.pybuild/cpython3_3.11_nav

Bug#1030496: fop: FTBFS: [javadoc] /<>/fop-core/src/main/java/org/apache/fop/servlet/FopServlet.java:29: error: package javax.servlet does not exist

2023-02-04 Thread Lucas Nussbaum

Source: fop
Version: 1:2.8-2
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20230203 ftbfs-bookworm

Hi,

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


Relevant part (hopefully):
> [INFO] ---
> [INFO]  T E S T S
> [INFO] ---
> [INFO] Running org.apache.fop.configuration.DefaultConfigurationTestCase
> [INFO] Tests run: 2, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.131 
> s - in org.apache.fop.configuration.DefaultConfigurationTestCase
> [INFO] Running org.apache.fop.HyphenationTestCase
> [INFO] Tests run: 3, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.162 
> s - in org.apache.fop.HyphenationTestCase
> [INFO] Running 
> org.apache.fop.layoutmgr.RetrieveTableMarkerLayoutManagerTestCase
> [INFO] Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 1.073 
> s - in org.apache.fop.layoutmgr.RetrieveTableMarkerLayoutManagerTestCase
> [INFO] Running org.apache.fop.layoutmgr.BreakElementTestCase
> [INFO] Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0 s - 
> in org.apache.fop.layoutmgr.BreakElementTestCase
> [INFO] Running 
> org.apache.fop.layoutmgr.table.TableContentLayoutManagerTestCase
> [INFO] Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.055 
> s - in org.apache.fop.layoutmgr.table.TableContentLayoutManagerTestCase
> [INFO] Running org.apache.fop.layoutmgr.table.TableCellLayoutManagerTestCase
> [INFO] Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.373 
> s - in org.apache.fop.layoutmgr.table.TableCellLayoutManagerTestCase
> [INFO] Running org.apache.fop.layoutmgr.table.TableLayoutManagerTestCase
> [INFO] Tests run: 2, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.139 
> s - in org.apache.fop.layoutmgr.table.TableLayoutManagerTestCase
> [INFO] Running org.apache.fop.layoutmgr.PageSequenceLayoutManagerTestCase
> [INFO] Tests run: 3, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.322 
> s - in org.apache.fop.layoutmgr.PageSequenceLayoutManagerTestCase
> [INFO] Running 
> org.apache.fop.layoutmgr.RetrieveTableMarkerLayoutManagerMakerTestCase
> [INFO] Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.009 
> s - in org.apache.fop.layoutmgr.RetrieveTableMarkerLayoutManagerMakerTestCase
> [INFO] Running org.apache.fop.intermediate.IFMimickingTestCase
> [INFO] Tests run: 3, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.304 
> s - in org.apache.fop.intermediate.IFMimickingTestCase
> [INFO] Running org.apache.fop.intermediate.AreaTreeParserTestCase
> [INFO] Tests run: 695, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 
> 18.284 s - in org.apache.fop.intermediate.AreaTreeParserTestCase
> [INFO] Running org.apache.fop.intermediate.IFTestCase
> [ERROR] Tests run: 13, Failures: 1, Errors: 0, Skipped: 0, Time elapsed: 
> 0.351 s <<< FAILURE! - in org.apache.fop.intermediate.IFTestCase
> [ERROR] runTest[3](org.apache.fop.intermediate.IFTestCase)  Time elapsed: 
> 0.015 s  <<< FAILURE!
> java.lang.AssertionError: Expected XPath expression to evaluate to 'true', 
> but got '' (XPath: /descendant::if:text[1]/@hyphenated)
>   at org.apache.fop.intermediate.IFTestCase.runTest(IFTestCase.java:103)
> 
> [INFO] Running org.apache.fop.intermediate.IFParserTestCase
> [INFO] Tests run: 695, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 
> 7.409 s - in org.apache.fop.intermediate.IFParserTestCase
> [INFO] Running org.apache.fop.pdf.PDFAttachmentTestCase
> [INFO] Tests run: 3, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.005 
> s - in org.apache.fop.pdf.PDFAttachmentTestCase
> [INFO] Running org.apache.fop.pdf.PDFReferenceTestCase
> [INFO] Tests run: 2, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0 s - 
> in org.apache.fop.pdf.PDFReferenceTestCase
> [INFO] Running org.apache.fop.pdf.PDFNumberTestCase
> [INFO] Tests run: 10, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.001 
> s - in org.apache.fop.pdf.PDFNumberTestCase
> [INFO] Running org.apache.fop.pdf.PDFPageLabelsTestCase
> [INFO] Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.041 
> s - in org.apache.fop.pdf.PDFPageLabelsTestCase
> [INFO] Running org.apache.fop.pdf.PDFImageXObjectTestCase
> [INFO] Tests run: 2, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.118 
> s - in org.apache.fop.pdf.PDFImageXObjectTestCase
> [INFO] Running org.apache.fop.pdf.PDFPagePieceTestCase
> [INFO] Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.018 
> s - in org.apache.fop.pdf.PDFPagePieceTestCase
> [INFO] Running org.apache.fop.pdf.ObjectStreamTestCase
> [INFO] Tests run: 4, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.002 
> s - in org.apache.fop.pdf.ObjectStreamTestCase
> [INFO] Running org.apache.fop.pdf.PDFJavaScriptLaunchActionTestCase
> [INFO] Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.02

Bug#1028863: python-aioice: FTBFS: dh_auto_test: error: pybuild --test --test-pytest -i python{version} -p 3.11 returned exit code 13

2023-02-04 Thread Lucas Nussbaum

On 01/02/23 at 11:59 +0100, Jonas Smedegaard wrote:
> [ sending once more, to bug-closure address this time ]
> 
> Version: 0.8.0-1
> 
> Quoting Lucas Nussbaum (2023-01-14 14:01:50)
> > During a rebuild of all packages in sid, your package failed to build
> > on amd64.
> 
> Evidently works again now.  Possibly due to upstream changes, but
> seemingly nothing changes specifically related to this, so I suspect the
> fix (and the bug) really was somewhere else in the tooling...

I confirm that it builds fine

Lucas


signature.asc
Description: PGP signature

Processed: Re: android-platform-frameworks-base: ftbfs with GCC-12

2023-02-04 Thread Debian Bug Tracking System

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

> fixed 1012890 1:10.0.0+r36-6
Bug #1012890 [src:android-platform-frameworks-base] 
android-platform-frameworks-base: ftbfs with GCC-12
Marked as fixed in versions android-platform-frameworks-base/1:10.0.0+r36-6.
> severity 1012890 serious
Bug #1012890 [src:android-platform-frameworks-base] 
android-platform-frameworks-base: ftbfs with GCC-12
Severity set to 'serious' from 'normal'
>
End of message, stopping processing here.

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

Processed: Re: Bug#1030306: simple-scan: Not a JPEG file: starts with 0x00 0x00

2023-02-04 Thread Debian Bug Tracking System

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

> severity 1030306 normal
Bug #1030306 [simple-scan] simple-scan: Not a JPEG file: starts with 0x00 0x00
Severity set to 'normal' from 'grave'
> tags 1030306 + moreinfo
Bug #1030306 [simple-scan] simple-scan: Not a JPEG file: starts with 0x00 0x00
Added tag(s) moreinfo.
> thanks
Stopping processing here.

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

Processed: bug 1030431 is forwarded to https://github.com/sphinx-contrib/autoprogram/issues/54

2023-02-04 Thread Debian Bug Tracking System

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

> forwarded 1030431 https://github.com/sphinx-contrib/autoprogram/issues/54
Bug #1030431 [src:sphinxcontrib-autoprogram] sphinxcontrib-autoprogram: FTBFS: 
AttributeError: 'NoneType' object has no attribute 'reporter'
Set Bug forwarded-to-address to 
'https://github.com/sphinx-contrib/autoprogram/issues/54'.
> thanks
Stopping processing here.

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

Bug#1030492: marked as done (pyorbital: FTBFS: AssertionError: 0.7875583269985472 != 0.7875583269985473)

2023-02-04 Thread Debian Bug Tracking System

Your message dated Sat, 04 Feb 2023 09:20:17 +
with message-id 
and subject line Bug#1030492: fixed in pyorbital 1.7.3-2
has caused the Debian Bug report #1030492,
regarding pyorbital: FTBFS: AssertionError: 0.7875583269985472 != 
0.7875583269985473
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.)


-- 
1030492: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1030492
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: pyorbital
Version: 1.7.3-1
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20230203 ftbfs-bookworm

Hi,

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


Relevant part (hopefully):
> make[1]: Entering directory '/<>'
> dh_auto_build --buildsystem=pybuild
>   pybuild --build -i python{version} -p 3.11
> I: pybuild base:240: /usr/bin/python3 setup.py build 
> running build
> running build_py
> creating /<>/.pybuild/cpython3_3.11_pyorbital/build/pyorbital
> copying pyorbital/__init__.py -> 
> /<>/.pybuild/cpython3_3.11_pyorbital/build/pyorbital
> copying pyorbital/geoloc_example.py -> 
> /<>/.pybuild/cpython3_3.11_pyorbital/build/pyorbital
> copying pyorbital/tlefile.py -> 
> /<>/.pybuild/cpython3_3.11_pyorbital/build/pyorbital
> copying pyorbital/orbital.py -> 
> /<>/.pybuild/cpython3_3.11_pyorbital/build/pyorbital
> copying pyorbital/astronomy.py -> 
> /<>/.pybuild/cpython3_3.11_pyorbital/build/pyorbital
> copying pyorbital/geoloc.py -> 
> /<>/.pybuild/cpython3_3.11_pyorbital/build/pyorbital
> copying pyorbital/geoloc_instrument_definitions.py -> 
> /<>/.pybuild/cpython3_3.11_pyorbital/build/pyorbital
> copying pyorbital/version.py -> 
> /<>/.pybuild/cpython3_3.11_pyorbital/build/pyorbital
> creating 
> /<>/.pybuild/cpython3_3.11_pyorbital/build/pyorbital/tests
> copying pyorbital/tests/__init__.py -> 
> /<>/.pybuild/cpython3_3.11_pyorbital/build/pyorbital/tests
> copying pyorbital/tests/test_orbital.py -> 
> /<>/.pybuild/cpython3_3.11_pyorbital/build/pyorbital/tests
> copying pyorbital/tests/test_tlefile.py -> 
> /<>/.pybuild/cpython3_3.11_pyorbital/build/pyorbital/tests
> copying pyorbital/tests/test_astronomy.py -> 
> /<>/.pybuild/cpython3_3.11_pyorbital/build/pyorbital/tests
> copying pyorbital/tests/test_geoloc.py -> 
> /<>/.pybuild/cpython3_3.11_pyorbital/build/pyorbital/tests
> copying pyorbital/tests/test_aiaa.py -> 
> /<>/.pybuild/cpython3_3.11_pyorbital/build/pyorbital/tests
> creating /<>/.pybuild/cpython3_3.11_pyorbital/build/pyorbital/etc
> copying pyorbital/etc/platforms.txt -> 
> /<>/.pybuild/cpython3_3.11_pyorbital/build/pyorbital/etc
> running build_scripts
> creating build
> creating build/scripts-3.11
> copying and adjusting bin/fetch_tles.py -> build/scripts-3.11
> changing mode of build/scripts-3.11/fetch_tles.py from 644 to 755
> PYTHONPATH=. python3 -m sphinx -N -bhtml doc/source/ doc/build/html # HTML 
> generator
> Running Sphinx v5.3.0
> making output directory... done
> WARNING: html_static_path entry '.static' does not exist
> building [mo]: targets for 0 po files that are out of date
> building [html]: targets for 1 source files that are out of date
> updating environment: [new config] 1 added, 0 changed, 0 removed
> reading sources... [100%] index
> 
> /<>/pyorbital/orbital.py:docstring of 
> pyorbital.orbital.Orbital.get_equatorial_crossing_time:10: ERROR: Unexpected 
> indentation.
> /<>/pyorbital/orbital.py:docstring of 
> pyorbital.orbital.OrbitElements:3: WARNING: Block quote ends without a blank 
> line; unexpected unindent.
> /<>/pyorbital/tlefile.py:docstring of pyorbital.tlefile:1: 
> WARNING: Include file '/<>/etc/platforms.txt' not found or 
> reading it failed
> looking for now-outdated files... none found
> pickling environment... done
> checking consistency... done
> preparing documents... done
> writing output... [100%] index
> 
> generating indices... genindex py-modindex done
> writing additional pages... search done
> copying static files... done
> copying extra files... done
> dumping search index in English (code: en)... done
> dumping object inventory... done
> build succeeded, 4 warnings.
> 
> The HTML pages are in doc/build/html.
> make[1]: Leaving directory '/<>'
>dh_auto_test -O--buildsystem=pybuild
>   pybuild --test -i python{version} -p 3.11
> I: pybuild base:240: python3.11 setup.py test 
> running test
> WARNING: Testing via this command is deprecated and will be removed in a 
> future version. Users looking for a generic test entry point independent of 
> test runner are encouraged to use tox.
> running egg_info

Bug#1026514: marked as done (python-param: FTBFS: TypeError: The only supported seed types are: None,)

2023-02-04 Thread Debian Bug Tracking System

Your message dated Sat, 04 Feb 2023 09:20:27 +
with message-id 
and subject line Bug#1026514: fixed in python-param 1.12.3-1
has caused the Debian Bug report #1026514,
regarding python-param: FTBFS: TypeError: The only supported seed types are: 
None,
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.)


-- 
1026514: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1026514
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: python-param
Version: 1.9.3-2
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20221220 ftbfs-bookworm

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 --buildsystem=pybuild
>dh_update_autotools_config -O--buildsystem=pybuild
>dh_autoreconf -O--buildsystem=pybuild
>dh_auto_configure -O--buildsystem=pybuild
> I: pybuild base:240: python3.11 setup.py config 
> /usr/lib/python3/dist-packages/setuptools/dist.py:544: UserWarning: The 
> version specified ('None') is an invalid version, this may not work as 
> expected with newer versions of setuptools, pip, and PyPI. Please see PEP 440 
> for more details.
>   warnings.warn(
> running config
> I: pybuild base:240: python3.10 setup.py config 
> /usr/lib/python3/dist-packages/setuptools/dist.py:544: UserWarning: The 
> version specified ('None') is an invalid version, this may not work as 
> expected with newer versions of setuptools, pip, and PyPI. Please see PEP 440 
> for more details.
>   warnings.warn(
> running config
>dh_auto_build -O--buildsystem=pybuild
> I: pybuild base:240: /usr/bin/python3.11 setup.py build 
> /usr/lib/python3/dist-packages/setuptools/dist.py:544: UserWarning: The 
> version specified ('None') is an invalid version, this may not work as 
> expected with newer versions of setuptools, pip, and PyPI. Please see PEP 440 
> for more details.
>   warnings.warn(
> running build
> running build_py
> creating /<>/.pybuild/cpython3_3.11_param/build/param
> copying param/parameterized.py -> 
> /<>/.pybuild/cpython3_3.11_param/build/param
> copying param/__init__.py -> 
> /<>/.pybuild/cpython3_3.11_param/build/param
> copying param/ipython.py -> 
> /<>/.pybuild/cpython3_3.11_param/build/param
> copying param/version.py -> 
> /<>/.pybuild/cpython3_3.11_param/build/param
> creating /<>/.pybuild/cpython3_3.11_param/build/numbergen
> copying numbergen/__init__.py -> 
> /<>/.pybuild/cpython3_3.11_param/build/numbergen
> running egg_info
> /usr/lib/python3/dist-packages/pkg_resources/__init__.py:123: 
> PkgResourcesDeprecationWarning: None is an invalid version and will not be 
> supported in a future release
>   warnings.warn(
> creating param.egg-info
> writing param.egg-info/PKG-INFO
> writing dependency_links to param.egg-info/dependency_links.txt
> writing requirements to param.egg-info/requires.txt
> writing top-level names to param.egg-info/top_level.txt
> writing manifest file 'param.egg-info/SOURCES.txt'
> reading manifest file 'param.egg-info/SOURCES.txt'
> reading manifest template 'MANIFEST.in'
> adding license file 'LICENSE.txt'
> writing manifest file 'param.egg-info/SOURCES.txt'
> copying param/.version -> 
> /<>/.pybuild/cpython3_3.11_param/build/param
> I: pybuild base:240: /usr/bin/python3 setup.py build 
> /usr/lib/python3/dist-packages/setuptools/dist.py:544: UserWarning: The 
> version specified ('None') is an invalid version, this may not work as 
> expected with newer versions of setuptools, pip, and PyPI. Please see PEP 440 
> for more details.
>   warnings.warn(
> running build
> running build_py
> creating /<>/.pybuild/cpython3_3.10_param/build/param
> copying param/parameterized.py -> 
> /<>/.pybuild/cpython3_3.10_param/build/param
> copying param/__init__.py -> 
> /<>/.pybuild/cpython3_3.10_param/build/param
> copying param/ipython.py -> 
> /<>/.pybuild/cpython3_3.10_param/build/param
> copying param/version.py -> 
> /<>/.pybuild/cpython3_3.10_param/build/param
> creating /<>/.pybuild/cpython3_3.10_param/build/numbergen
> copying numbergen/__init__.py -> 
> /<>/.pybuild/cpython3_3.10_param/build/numbergen
> running egg_info
> /usr/lib/python3/dist-packages/pkg_resources/__init__.py:123: 
> PkgResourcesDeprecationWarning: None is an invalid version and will not be 
> supported in a future release
>   warnings.warn(
> writing param.egg-info/PKG-INFO
> writing dependency_links to param.egg-info/dependency_links.txt
> writing requirements to param.egg-info/requires.txt
> writing top-level names to param.egg-i

Bug#1030424: marked as pending in recommonmark

2023-02-04 Thread Jochen Sprickerhof

Control: tag -1 pending

Hello,

Bug #1030424 in recommonmark 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/recommonmark/-/commit/aea1ec3124e77cbf74b16c7b6d0f29f646f6c5fc


Adopt test to new sphinx version

Closes: #1030424


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/1030424

Processed: Bug#1030424 marked as pending in recommonmark

2023-02-04 Thread Debian Bug Tracking System

Processing control commands:

> tag -1 pending
Bug #1030424 [src:recommonmark] recommonmark: FTBFS: AssertionError
Added tag(s) pending.

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

Bug#1030506: backintime-common: Version string ("1.3.3-dev") reported by backintime does not reflect the release

2023-02-04 Thread Christian Buhtz

Package: backintime-common
Version: 1.3.3-3
Severity: serious
Tags: upstream
Justification: Policy 3.2
X-Debbugs-Cc: fantonifa...@tiscali.it




-- System Information:
Debian Release: 11.6
  APT prefers stable-updates
  APT policy: (500, 'stable-updates'), (500, 'stable-security'), (500,
'stable')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 5.10.0-21-amd64 (SMP w/4 CPU threads)
Kernel taint flags: TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE
Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8), LANGUAGE not
set
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages backintime-common depends on:
ii  cron [cron-daemon]  3.0pl1-137
ii  openssh-client  1:8.4p1-5+deb11u1
ii  python3 3.9.2-3
ii  python3-dbus1.2.16-5
pn  python3-keyring 
ii  rsync   3.2.3-4+deb11u1

Versions of packages backintime-common recommends:
pn  backintime-qt  

Versions of packages backintime-common suggests:
ii  encfs   1.9.5-1+b2
ii  powermgmt-base  1.36

Dear Fabio,
dear Jonathan,

My apologize. Because of line 65 in "config.py" [1] the binary of backintime-
comman and backintime-qt will report "1.3.3-dev" as version number. The "-dev"
shouldn't be there.

The reasons is I misused the Release feature of GitHub.

In the upstream repo the git tag "v1.3.3" do reflect the latest stable release.
And that release do report the correct version string (without the "-dev" at
the end).

Only the source tarball in the GitHub-Release section does have the wrong
version number.

Please let us know how we could go on fixing this.
I assume the easiest would be to clone the upstream git repo at tag "v1.3.3"
and avoid using the source tarball.

Beside the version number none of the code has changed. So it is just a
cosmetic thing.

Apologize again. We learned from this and will do it better the next time.

[1] --

Bug#1028867: Rassign and close

2023-02-04 Thread Anton Gladky

reassign 1028867 php8.2 8.2.1-1
fixed 1028867 8.2.2-1
thanks


The problem not in php-sabre-vobject but in php itself [1].
Upstream fix [2] and is fixed in Debian already [3].


Thus - reassign and close.

[1] https://github.com/Shardj/zf1-future/issues/304
[2] 
https://github.com/php/php-src/commit/d12ba111e03fa4e6d76a66a029f5dbe6265b1ea9
[3] 
https://sources.debian.org/src/php8.2/8.2.2-1/ext/date/lib/parse_date.c/#L790


Best regards

Processed: Rassign and close

2023-02-04 Thread Debian Bug Tracking System

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

> reassign 1028867 php8.2 8.2.1-1
Bug #1028867 [src:php-sabre-vobject] php-sabre-vobject: FTBFS: make[1]: *** 
[debian/rules:13: override_dh_auto_test] Error 2
Bug reassigned from package 'src:php-sabre-vobject' to 'php8.2'.
No longer marked as found in versions php-sabre-vobject/2.1.7-6.1.
Ignoring request to alter fixed versions of bug #1028867 to the same values 
previously set
Bug #1028867 [php8.2] php-sabre-vobject: FTBFS: make[1]: *** [debian/rules:13: 
override_dh_auto_test] Error 2
Marked as found in versions php8.2/8.2.1-1.
> fixed 1028867 8.2.2-1
Bug #1028867 [php8.2] php-sabre-vobject: FTBFS: make[1]: *** [debian/rules:13: 
override_dh_auto_test] Error 2
Marked as fixed in versions php8.2/8.2.2-1.
> thanks
Stopping processing here.

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

Bug#1028867: marked as done (php-sabre-vobject: FTBFS: make[1]: *** [debian/rules:13: override_dh_auto_test] Error 2)

2023-02-04 Thread Debian Bug Tracking System

Your message dated Sat, 4 Feb 2023 10:29:10 +0100
with message-id 

and subject line Rassign and close
has caused the Debian Bug report #1028867,
regarding php-sabre-vobject: FTBFS: make[1]: *** [debian/rules:13: 
override_dh_auto_test] Error 2
to be marked as done.

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

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


-- 
1028867: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1028867
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: php-sabre-vobject
Version: 2.1.7-6.1
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20230113 ftbfs-bookworm

Hi,

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


Relevant part (hopefully):
> make[1]: Entering directory '/<>'
> phpunit --configuration tests/phpunit.xml
> PHPUnit 9.5.27 by Sebastian Bergmann and contributors.
> 
> Warning:   Your XML configuration validates against a deprecated schema.
> Suggestion:Migrate your XML configuration using "--migrate-configuration"!
> 
> ...  63 / 553 ( 
> 11%)
> ... 126 / 553 ( 
> 22%)
> ...R... 189 / 553 ( 
> 34%)
> .R. 252 / 553 ( 
> 45%)
> ..RR..RR..RRERR 315 / 553 ( 
> 56%)
> EER 378 / 553 ( 
> 68%)
> RRR 441 / 553 ( 
> 79%)
> RRR 504 / 553 ( 
> 91%)
> RRR..   553 / 553 
> (100%)
> 
> Time: 00:00.081, Memory: 12.00 MB
> 
> There were 3 errors:
> 
> 1) Sabre\VObject\TimezoneUtilTest::testCorrectTZ with data set "Dateline 
> Standard Time" ('Etc/GMT+12')
> Exception: DateTimeZone::__construct(): Unknown or bad timezone (Etc/GMT+12)
> 
> /<>/tests/Sabre/VObject/TimeZoneUtilTest.php:12
> 
> 2) Sabre\VObject\TimezoneUtilTest::testCorrectTZ with data set "UTC-02" 
> ('Etc/GMT+2')
> Exception: DateTimeZone::__construct(): Unknown or bad timezone (Etc/GMT+2)
> 
> /<>/tests/Sabre/VObject/TimeZoneUtilTest.php:12
> 
> 3) Sabre\VObject\TimezoneUtilTest::testCorrectTZ with data set "UTC-11" 
> ('Etc/GMT+11')
> Exception: DateTimeZone::__construct(): Unknown or bad timezone (Etc/GMT+11)
> 
> /<>/tests/Sabre/VObject/TimeZoneUtilTest.php:12
> 
> --
> 
> There were 280 risky tests:
> 
> 1) Sabre\VObject\PropertyTest::testParameterNotExists
> This test did not perform any assertions
> 
> /<>/tests/Sabre/VObject/PropertyTest.php:46
> 
> 2) Sabre\VObject\RecurrenceIteratorFifthTuesdayProblemTest::testGetDTEnd
> This test did not perform any assertions
> 
> /<>/tests/Sabre/VObject/RecurrenceIteratorFifthTuesdayProblemTest.php:7
> 
> 3) Sabre\VObject\Splitter\VCardSplitterTest::testVCardImportValidVCard
> This test did not perform any assertions
> 
> /<>/tests/Sabre/VObject/Splitter/VCardTest.php:18
> 
> 4) 
> Sabre\VObject\Splitter\VCardSplitterTest::testVCardImportValidVCardsWithCategories
> This test did not perform any assertions
> 
> /<>/tests/Sabre/VObject/Splitter/VCardTest.php:36
> 
> 5) 
> Sabre\VObject\Splitter\VCardSplitterTest::testVCardImportMultipleValidVCards
> This test did not perform any assertions
> 
> /<>/tests/Sabre/VObject/Splitter/VCardTest.php:100
> 
> 6) Sabre\VObject\Splitter\VCardSplitterTest::testVCardImportVCardWithoutUID
> This test did not perform any assertions
> 
> /<>/tests/Sabre/VObject/Splitter/VCardTest.php:121
> 
> 7) Sabre\VObject\TimezoneUtilTest::testCorrectTZ with data set "AUS Central 
> Standard Time" ('Australia/Darwin')
> This test did not perform any assertions
> 
> /<>/tests/Sabre/VObject/TimeZoneUtilTest.php:10
> 
> 8) Sabre\VObject\TimezoneUtilTest::testCorrectTZ with data set "AUS Eastern 
> Standard Time" ('Australia/Sydney')
> This test did not perform any assertions
> 
> /<>/tests/Sabre/VObject/TimeZoneUtilTest.php:10
> 
> 9) Sabre\VObject\TimezoneUtilTest::testCorrectTZ with data set "Afghanistan 
> Standard Time" ('Asia/Kabul')
> This test did not perform any assertions
> 
> /<>/tests/Sabre/VObject/TimeZoneUtilTest.php:10
> 
> 10) Sabre\VObject\TimezoneUtilTest::testCorrectTZ with data set "Alaskan 
> Standard Time" ('America/Anchorage')
> This test did not perform any assertions
> 
> /<>/tests/Sabre/VObject/TimeZoneUtilTest.php:10
> 
> 11) Sabre\VObject\TimezoneUtilTest::testCorrectTZ with

Bug#1030424: marked as done (recommonmark: FTBFS: AssertionError)

2023-02-04 Thread Debian Bug Tracking System

Your message dated Sat, 04 Feb 2023 09:34:35 +
with message-id 
and subject line Bug#1030424: fixed in recommonmark 0.7.1+ds-5
has caused the Debian Bug report #1030424,
regarding recommonmark: FTBFS: AssertionError
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.)


-- 
1030424: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1030424
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: recommonmark
Version: 0.7.1+ds-4
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20230203 ftbfs-bookworm

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:240: python3.11 setup.py config 
> running config
>dh_auto_build -O--buildsystem=pybuild
> I: pybuild base:240: /usr/bin/python3 setup.py build 
> running build
> running build_py
> creating /<>/.pybuild/cpython3_3.11/build/recommonmark
> copying recommonmark/__init__.py -> 
> /<>/.pybuild/cpython3_3.11/build/recommonmark
> copying recommonmark/parser.py -> 
> /<>/.pybuild/cpython3_3.11/build/recommonmark
> copying recommonmark/transform.py -> 
> /<>/.pybuild/cpython3_3.11/build/recommonmark
> copying recommonmark/states.py -> 
> /<>/.pybuild/cpython3_3.11/build/recommonmark
> copying recommonmark/scripts.py -> 
> /<>/.pybuild/cpython3_3.11/build/recommonmark
>dh_auto_test -O--buildsystem=pybuild
> I: pybuild base:240: cd /<>/.pybuild/cpython3_3.11/build; 
> python3.11 -m unittest discover -v 
> test_block_quote (tests.test_basic.TestParsing.test_block_quote) ... 
> /<>/.pybuild/cpython3_3.11/build/recommonmark/parser.py:117: 
> DeprecationWarning: nodes.Text: initialization argument "rawsource" is 
> ignored and will be removed in Docutils 2.0.
>   self.current_node.append(nodes.Text(mdnode.literal, mdnode.literal))
> /<>/.pybuild/cpython3_3.11/build/recommonmark/parser.py:75: 
> UserWarning: Container node skipped: type=document
>   warn("Container node skipped: type={0}".format(mdnode.t))
> ok
> test_bullet_list (tests.test_basic.TestParsing.test_bullet_list) ... 
> /<>/.pybuild/cpython3_3.11/build/recommonmark/parser.py:117: 
> DeprecationWarning: nodes.Text: initialization argument "rawsource" is 
> ignored and will be removed in Docutils 2.0.
>   self.current_node.append(nodes.Text(mdnode.literal, mdnode.literal))
> /<>/.pybuild/cpython3_3.11/build/recommonmark/parser.py:75: 
> UserWarning: Container node skipped: type=document
>   warn("Container node skipped: type={0}".format(mdnode.t))
> /<>/.pybuild/cpython3_3.11/build/recommonmark/parser.py:117: 
> DeprecationWarning: nodes.Text: initialization argument "rawsource" is 
> ignored and will be removed in Docutils 2.0.
>   self.current_node.append(nodes.Text(mdnode.literal, mdnode.literal))
> /<>/.pybuild/cpython3_3.11/build/recommonmark/parser.py:75: 
> UserWarning: Container node skipped: type=document
>   warn("Container node skipped: type={0}".format(mdnode.t))
> ok
> test_code (tests.test_basic.TestParsing.test_code) ... 
> /<>/.pybuild/cpython3_3.11/build/recommonmark/parser.py:117: 
> DeprecationWarning: nodes.Text: initialization argument "rawsource" is 
> ignored and will be removed in Docutils 2.0.
>   self.current_node.append(nodes.Text(mdnode.literal, mdnode.literal))
> /<>/.pybuild/cpython3_3.11/build/recommonmark/parser.py:75: 
> UserWarning: Container node skipped: type=document
>   warn("Container node skipped: type={0}".format(mdnode.t))
> ok
> test_entities (tests.test_basic.TestParsing.test_entities) ... 
> /<>/.pybuild/cpython3_3.11/build/recommonmark/parser.py:117: 
> DeprecationWarning: nodes.Text: initialization argument "rawsource" is 
> ignored and will be removed in Docutils 2.0.
>   self.current_node.append(nodes.Text(mdnode.literal, mdnode.literal))
> /<>/.pybuild/cpython3_3.11/build/recommonmark/parser.py:75: 
> UserWarning: Container node skipped: type=document
>   warn("Container node skipped: type={0}".format(mdnode.t))
> ok
> test_enumerated_list (tests.test_basic.TestParsing.test_enumerated_list) ... 
> /<>/.pybuild/cpython3_3.11/build/recommonmark/parser.py:117: 
> DeprecationWarning: nodes.Text: initialization argument "rawsource" is 
> ignored and will be removed in Docutils 2.0.
>   self.current_node.append(nodes.Text(mdnode.literal, mdnode.literal))
> /<>/.pybuild/cpython3_3.11/build/recommonmark/p

Bug#1030506: backintime-common: Version string ("1.3.3-dev") reported by backintime does not reflect the release

2023-02-04 Thread Fabio Fantoni


Il 04/02/2023 10:24, Christian Buhtz ha scritto:

Package: backintime-common
Version: 1.3.3-3
Severity: serious
Tags: upstream
Justification: Policy 3.2
X-Debbugs-Cc: fantonifa...@tiscali.it




-- System Information:
Debian Release: 11.6
   APT prefers stable-updates
   APT policy: (500, 'stable-updates'), (500, 'stable-security'), (500,
'stable')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 5.10.0-21-amd64 (SMP w/4 CPU threads)
Kernel taint flags: TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE
Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8), LANGUAGE not
set
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages backintime-common depends on:
ii  cron [cron-daemon]  3.0pl1-137
ii  openssh-client  1:8.4p1-5+deb11u1
ii  python3 3.9.2-3
ii  python3-dbus1.2.16-5
pn  python3-keyring 
ii  rsync   3.2.3-4+deb11u1

Versions of packages backintime-common recommends:
pn  backintime-qt  

Versions of packages backintime-common suggests:
ii  encfs   1.9.5-1+b2
ii  powermgmt-base  1.36

Dear Fabio,
dear Jonathan,

My apologize. Because of line 65 in "config.py" [1] the binary of backintime-
comman and backintime-qt will report "1.3.3-dev" as version number. The "-dev"
shouldn't be there.

The reasons is I misused the Release feature of GitHub.

In the upstream repo the git tag "v1.3.3" do reflect the latest stable release.
And that release do report the correct version string (without the "-dev" at
the end).

Only the source tarball in the GitHub-Release section does have the wrong
version number.

Please let us know how we could go on fixing this.
I assume the easiest would be to clone the upstream git repo at tag "v1.3.3"
and avoid using the source tarball.

Beside the version number none of the code has changed. So it is just a
cosmetic thing.

Apologize again. We learned from this and will do it better the next time.

[1] -- 


Hi, I already saw that the upstream source is correct based on release 
tag but upstream tag was create wrong excluding one commit that change 
version.


I didn't add a d/patches of that commit as only minor thing that change 
version only "aesthetic" but since it is considered important I'll add 
the "missed commit" in d/patches




OpenPGP_signature
Description: OpenPGP digital signature

Bug#1030506: marked as pending in backintime

2023-02-04 Thread Fabio Fantoni

Control: tag -1 pending

Hello,

Bug #1030506 in backintime 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/jmw/pkg-backintime/-/commit/c12e197ced44392e6636259012d41d3e285ad5ce


d/patches: add upstream commit "Release 1.3.3" that was missed in source tag

Closes: #1030506


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/1030506

Processed: Bug#1030506 marked as pending in backintime

2023-02-04 Thread Debian Bug Tracking System

Processing control commands:

> tag -1 pending
Bug #1030506 [backintime-common] backintime-common: Version string 
("1.3.3-dev") reported by backintime does not reflect the release
Added tag(s) pending.

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

Processed: closing 1030422

2023-02-04 Thread Debian Bug Tracking System

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

> close 1030422 0.2.2-3
Bug #1030422 [src:rust-oxiri] rust-oxiri: FTBFS: dh_auto_test: error: 
/<>/debian/dh-cargo/bin/cargo test returned exit code 101
Marked as fixed in versions rust-oxiri/0.2.2-3.
Bug #1030422 [src:rust-oxiri] rust-oxiri: FTBFS: dh_auto_test: error: 
/<>/debian/dh-cargo/bin/cargo test returned exit code 101
Marked Bug as done
> thanks
Stopping processing here.

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

Bug#1030510: mariadb: FTBFS on s390x: timeout

2023-02-04 Thread Sebastian Ramacher

Source: mariadb
Version: 1:10.11.1-2
Severity: serious
Tags: ftbfs
Justification: fails to build from source (but built successfully in the past)

https://buildd.debian.org/status/fetch.php?pkg=mariadb&arch=s390x&ver=1%3A10.11.1-2&stamp=1675466043&raw=0

main.win_insert_select   w2 [ pass ]  2
main.win_lead_lagw2 [ pass ]  1
main.win_min_max w2 [ pass ]  5
main.win_nth_value   w2 [ pass ]  1
main.win_ntile   w2 [ pass ]  3
main.win_orderby w2 [ pass ]  2
main.win_percent_cumew2 [ pass ]  1
main.win_percentile  w2 [ pass ]  8
main.win_rankw2 [ pass ]  1
main.win_std w2 [ pass ]  2
main.win_sum w2 [ pass ]  1
main.windows w2 [ skipped ]  Need windows
main.xa_sync w2 [ skipped ]  debug_sync is not 
available
main.xml w2 [ pass ] 15
E: Build killed with signal TERM after 150 minutes of inactivity

Cheers
-- 
Sebastian Ramacher

Bug#1030511: libguestfs: FTBFS on s390x: timeout

2023-02-04 Thread Sebastian Ramacher

Source: libguestfs
Version: 1:1.48.6-1
Severity: serious
Tags: ftbfs
Justification: fails to build from source (but built successfully in the past)

https://buildd.debian.org/status/fetch.php?pkg=libguestfs&arch=s390x&ver=1%3A1.48.6-1%2Bb3&stamp=1675413376&raw=0

cd ../../.. && /<>/debian/build-2/generator/generator
generated 555164 lines of code
touch stamp-generator
make[4]: Leaving directory '/<>/debian/build-2/generator'
Making all in test-data
make[4]: Entering directory '/<>/debian/build-2/test-data'
Making all in binaries
make[5]: Entering directory '/<>/debian/build-2/test-data/binaries'
make[5]: Nothing to be done for 'all'.
make[5]: Leaving directory '/<>/debian/build-2/test-data/binaries'
Making all in blank-disks
make[5]: Entering directory 
'/<>/debian/build-2/test-data/blank-disks'
qemu-img create -f raw blank-disk-1s.raw 512
qemu-img create -f qcow2 -o preallocation=metadata blank-disk-1s.qcow2 512
Formatting 'blank-disk-1s.raw', fmt=raw size=512
Formatting 'blank-disk-1s.qcow2', fmt=qcow2 cluster_size=65536 extended_l2=off 
preallocation=metadata compression_type=zlib size=512 lazy_refcounts=off 
refcount_bits=16
qemu-img create -f raw blank-disk-1K.raw 1K
Formatting 'blank-disk-1K.raw', fmt=raw size=1024
qemu-img create -f qcow2 -o preallocation=metadata blank-disk-1K.qcow2 1K
Formatting 'blank-disk-1K.qcow2', fmt=qcow2 cluster_size=65536 extended_l2=off 
preallocation=metadata compression_type=zlib size=1024 lazy_refcounts=off 
refcount_bits=16
qemu-img create -f raw blank-disk-1M.raw 1M
Formatting 'blank-disk-1M.raw', fmt=raw size=1048576
qemu-img create -f qcow2 -o preallocation=metadata blank-disk-1M.qcow2 1M
Formatting 'blank-disk-1M.qcow2', fmt=qcow2 cluster_size=65536 extended_l2=off 
preallocation=metadata compression_type=zlib size=1048576 lazy_refcounts=off 
refcount_bits=16
qemu-img create -f qcow2 -b blank-disk-1M.raw -F raw 
blank-disk-with-backing.qcow2
Formatting 'blank-disk-with-backing.qcow2', fmt=qcow2 cluster_size=65536 
extended_l2=off compression_type=zlib size=1048576 
backing_file=blank-disk-1M.raw backing_fmt=raw lazy_refcounts=off 
refcount_bits=16
E: Build killed with signal TERM after 150 minutes of inactivity

Cheers
-- 
Sebastian Ramacher

Processed: unarchiving 1016598

2023-02-04 Thread Debian Bug Tracking System

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

> unarchive 1016598
Bug #1016598 {Done: Picca Frédéric-Emmanuel } 
[src:binoculars] binoculars: vtk[6,7] removal
Unarchived Bug 1016598
> thanks
Stopping processing here.

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

Processed: tagging 1018018

2023-02-04 Thread Debian Bug Tracking System

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

> tags 1018018 + pending
Bug #1018018 [wmforkplop] wmforkplop: FTBFS with imlib2 1.9.1
Added tag(s) pending.
> thanks
Stopping processing here.

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

Bug#1030512: python3-anndata needs a source upload to fix the missing python3-h5py dependency

2023-02-04 Thread Adrian Bunk

Package: python3-anndata
Version: 0.8.0-3
Severity: serious

python3-anndata lacks a dependency on python3-h5py due to #1030274.

A no-change rebuild is sufficient, but since binNMUs are not possible
for binary-all this needs a source upload.

Bug#1030514: python3-mofapy needs a source upload to fix the missing python3-h5py dependency

2023-02-04 Thread Adrian Bunk

Package: python3-mofapy
Version: 1.6.1+dfsg-9
Severity: serious

python3-mofapy lacks a dependency on python3-h5py due to #1030274.

A no-change rebuild is sufficient, but since binNMUs are not possible
for binary-all this needs a source upload.

Bug#1016598: closed by Debian FTP Masters (reply to Picca Frédéric-Emmanuel ) (Bug#1016598: fixed in binoculars 0.0.11-2)

2023-02-04 Thread Adrian Bunk

Control: reopen -1

On Sun, Oct 16, 2022 at 09:51:03AM +, Debian Bug Tracking System wrote:
>...
>  binoculars (0.0.11-2) unstable; urgency=medium
>...
>* Switch from vtk7 to vtk9 (Closes: #1016598)
>...

This fixed the build dependency, but the runtime dependency is still 
on python3-vtk7.

cu
Adrian

Processed: Re: Bug#1016598 closed by Debian FTP Masters (reply to Picca Frédéric-Emmanuel ) (Bug#1016598: fixed in binoculars 0.0.11-2)

2023-02-04 Thread Debian Bug Tracking System

Processing control commands:

> reopen -1
Bug #1016598 {Done: Picca Frédéric-Emmanuel } 
[src:binoculars] binoculars: vtk[6,7] removal
'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 binoculars/0.0.11-2.

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

Bug#1030516: python3-hickle needs a source upload to fix the missing python3-h5py dependency

2023-02-04 Thread Adrian Bunk

Package: python3-hickle
Version: 5.0.2-4
Severity: serious

python3-hickle lacks a dependency on python3-h5py due to #1030274.

A no-change rebuild is sufficient, but since binNMUs are not possible
for binary-all this needs a source upload.

Bug#1030401: Many bugs about unsatisfiable build-dependencies

2023-02-04 Thread Stéphane Glondu


Hello,

These unsatisfiable build-dependencies are temporary and will be solved 
by properly sequenced binNMUs or sourceful uploads that I am currently 
dealing with.


I do not see the value of such bug reports. Packages with unsatisfiable 
build-dependencies do not migrate to testing nor are picked up by buildd 
daemons (so no actual FTBFS). They add burden and look like noise to me.



Cheers,

--
Stéphane

Bug#1024564: marked as done (django-assets FTBFS: re.error: global flags not at the start of the expression at position 6)

2023-02-04 Thread Debian Bug Tracking System

Your message dated Sat, 04 Feb 2023 12:04:30 +
with message-id 
and subject line Bug#1024287: fixed in django-assets 2.0-2.1
has caused the Debian Bug report #1024287,
regarding django-assets FTBFS: re.error: global flags not at the start of the 
expression at position 6
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.)


-- 
1024287: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1024287
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: django-assets
Severity: important
Tags: ftbfs
forwarded -1 https://github.com/miracle2k/django-assets/pull/104


Dear Maintainer,

Your package FTBFS because autopkgtests start failing with python3.11 as 
supported
version.
I can see the failure in a sid chroot environment and reproducible-builds 
confirms
the problem [1]

After applying aforementioned PR, your package builds fine and all test pass.

Kind Regards


[1] 
https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/django-assets.html
--- End Message ---
--- Begin Message ---
Source: django-assets
Source-Version: 2.0-2.1
Done: Adrian Bunk 

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

Debian distribution maintenance software
pp.
Adrian Bunk  (supplier of updated django-assets package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Sat, 28 Jan 2023 13:12:06 +0200
Source: django-assets
Architecture: source
Version: 2.0-2.1
Distribution: unstable
Urgency: low
Maintainer: Debian Python Team 
Changed-By: Adrian Bunk 
Closes: 1024287
Changes:
 django-assets (2.0-2.1) unstable; urgency=low
 .
   * Non-maintainer upload.
   * Add proposed fix for Python 3.11 compatibility. (Closes: #1024287)
Checksums-Sha1:
 014b51bc5cd34994c2b9e78eb8b06f0c01f1edd5 2298 django-assets_2.0-2.1.dsc
 d2ce01753e6572e3b46475f846bd493be387aadd 5556 
django-assets_2.0-2.1.debian.tar.xz
Checksums-Sha256:
 1fa61fb00d2ea317629873abd7ce8dcdab6a2142332a9ca51effd69199bfdc4d 2298 
django-assets_2.0-2.1.dsc
 a86729a10047ce04734c8f4ee025967e9c59ea0b5e706d0a87e1ee1ef16940ca 5556 
django-assets_2.0-2.1.debian.tar.xz
Files:
 8e398089864ee2f2a45e45ca7d143405 2298 python optional django-assets_2.0-2.1.dsc
 84a679ac4113c04aa967b4b8c06017a8 5556 python optional 
django-assets_2.0-2.1.debian.tar.xz

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEOvp1f6xuoR0v9F3wiNJCh6LYmLEFAmPVA7gACgkQiNJCh6LY
mLExgRAAhDsplCryMvNI+NpU+EmCadzNdMnx6S+s9UANNNJQwviTBvd2Wjd1TzDH
ub2MaiYnpEhBE2mEEK21/PV6hV/yvmJQaKbgs8+Q60w3DMgjflkU/lAXisNXQf5+
wkE0SFaI3Gr+rLHAu56u90RntR8QJRWqdls8fR039i9Ki8xOoIOsHD6fJqbaWC+s
Z9SBM69tmsT53UgiFsVtyB6ZhBlhXIwFXlEkOmSSclfn6/PWiFz8g21gtyZhMXZE
lRqGgq5wQEqWG22/mTWYNBZJ7etn798yWDZ+l9/fRTCiVuxHil2KSHu13/Wd6I0u
hun2Ec/AjcXL2UnrFSTPzvu5xVqM00m9deUStg8OLGqNBOBi5mNfKhPculLplic3
AVIb6ggj/vYmnvKInMqX5TVnY5ZGXyeLmSIkBN1MFdTnwCDLBV6lsKrJkKaIUckK
QmgfEeVaPCi4UtmTIvYcFpKwkVUJ/B2hbp/XfEKPQoS4B6vQ1/9FMvcOXfxXGeBi
YoVOIeUrG+qusczJNms6b5+qkF1ZJhT96/IY3zPas94OyvP2rJMn4Ryb+c42aIVd
tBZCH5pR/5Y3DBW8/C7MNZipIeq06DTkhWqPsqUcrM2WODcOyIWO08cY1ChtsE3S
ZYeofSD2eX0O7XekJScGQHOkvEZZ4QVeWRISt4Yoyj5/cBBxgqc=
=VJNZ
-END PGP SIGNATURE End Message ---

Bug#1024287: marked as done (django-assets: FTBFS against python 3.11)

2023-02-04 Thread Debian Bug Tracking System

Your message dated Sat, 04 Feb 2023 12:04:30 +
with message-id 
and subject line Bug#1024287: fixed in django-assets 2.0-2.1
has caused the Debian Bug report #1024287,
regarding django-assets: FTBFS against python 3.11
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.)


-- 
1024287: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1024287
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: django-assets
Severity: normal
User: ubuntu-de...@lists.ubuntu.com
Usertags: origin-ubuntu lunar

Dear Maintainer,

This bug report was also filed in Ubuntu and can be found at
https://launchpad.net/bugs/1996828

django-assets will FTBFS in tests with python 3.11:
https://autopkgtest.ubuntu.com/results/autopkgtest-lunar/lunar/amd64/d/django-assets/20221102_154051_2159f@/log.gz

A fix for this has been proposed upstream:
https://github.com/miracle2k/django-assets/pull/104

-Dan
--- End Message ---
--- Begin Message ---
Source: django-assets
Source-Version: 2.0-2.1
Done: Adrian Bunk 

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

Debian distribution maintenance software
pp.
Adrian Bunk  (supplier of updated django-assets package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Sat, 28 Jan 2023 13:12:06 +0200
Source: django-assets
Architecture: source
Version: 2.0-2.1
Distribution: unstable
Urgency: low
Maintainer: Debian Python Team 
Changed-By: Adrian Bunk 
Closes: 1024287
Changes:
 django-assets (2.0-2.1) unstable; urgency=low
 .
   * Non-maintainer upload.
   * Add proposed fix for Python 3.11 compatibility. (Closes: #1024287)
Checksums-Sha1:
 014b51bc5cd34994c2b9e78eb8b06f0c01f1edd5 2298 django-assets_2.0-2.1.dsc
 d2ce01753e6572e3b46475f846bd493be387aadd 5556 
django-assets_2.0-2.1.debian.tar.xz
Checksums-Sha256:
 1fa61fb00d2ea317629873abd7ce8dcdab6a2142332a9ca51effd69199bfdc4d 2298 
django-assets_2.0-2.1.dsc
 a86729a10047ce04734c8f4ee025967e9c59ea0b5e706d0a87e1ee1ef16940ca 5556 
django-assets_2.0-2.1.debian.tar.xz
Files:
 8e398089864ee2f2a45e45ca7d143405 2298 python optional django-assets_2.0-2.1.dsc
 84a679ac4113c04aa967b4b8c06017a8 5556 python optional 
django-assets_2.0-2.1.debian.tar.xz

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEOvp1f6xuoR0v9F3wiNJCh6LYmLEFAmPVA7gACgkQiNJCh6LY
mLExgRAAhDsplCryMvNI+NpU+EmCadzNdMnx6S+s9UANNNJQwviTBvd2Wjd1TzDH
ub2MaiYnpEhBE2mEEK21/PV6hV/yvmJQaKbgs8+Q60w3DMgjflkU/lAXisNXQf5+
wkE0SFaI3Gr+rLHAu56u90RntR8QJRWqdls8fR039i9Ki8xOoIOsHD6fJqbaWC+s
Z9SBM69tmsT53UgiFsVtyB6ZhBlhXIwFXlEkOmSSclfn6/PWiFz8g21gtyZhMXZE
lRqGgq5wQEqWG22/mTWYNBZJ7etn798yWDZ+l9/fRTCiVuxHil2KSHu13/Wd6I0u
hun2Ec/AjcXL2UnrFSTPzvu5xVqM00m9deUStg8OLGqNBOBi5mNfKhPculLplic3
AVIb6ggj/vYmnvKInMqX5TVnY5ZGXyeLmSIkBN1MFdTnwCDLBV6lsKrJkKaIUckK
QmgfEeVaPCi4UtmTIvYcFpKwkVUJ/B2hbp/XfEKPQoS4B6vQ1/9FMvcOXfxXGeBi
YoVOIeUrG+qusczJNms6b5+qkF1ZJhT96/IY3zPas94OyvP2rJMn4Ryb+c42aIVd
tBZCH5pR/5Y3DBW8/C7MNZipIeq06DTkhWqPsqUcrM2WODcOyIWO08cY1ChtsE3S
ZYeofSD2eX0O7XekJScGQHOkvEZZ4QVeWRISt4Yoyj5/cBBxgqc=
=VJNZ
-END PGP SIGNATURE End Message ---

Bug#1026496: marked as done (django-assets: FTBFS: dh_auto_test: error: pybuild --test --test-nose -i python{version} -p "3.11 3.10" returned exit code 13)

2023-02-04 Thread Debian Bug Tracking System

Your message dated Sat, 04 Feb 2023 12:04:30 +
with message-id 
and subject line Bug#1024287: fixed in django-assets 2.0-2.1
has caused the Debian Bug report #1024287,
regarding django-assets: FTBFS: dh_auto_test: error: pybuild --test --test-nose 
-i python{version} -p "3.11 3.10" 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.)


-- 
1024287: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1024287
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: django-assets
Version: 2.0-2
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20221220 ftbfs-bookworm

Hi,

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


Relevant part (hopefully):
> make[1]: Entering directory '/<>'
> dh_auto_build
> I: pybuild base:240: /usr/bin/python3.11 setup.py build 
> running build
> running build_py
> creating 
> /<>/.pybuild/cpython3_3.11_django-assets/build/django_assets
> copying django_assets/__init__.py -> 
> /<>/.pybuild/cpython3_3.11_django-assets/build/django_assets
> copying django_assets/glob.py -> 
> /<>/.pybuild/cpython3_3.11_django-assets/build/django_assets
> copying django_assets/models.py -> 
> /<>/.pybuild/cpython3_3.11_django-assets/build/django_assets
> copying django_assets/settings.py -> 
> /<>/.pybuild/cpython3_3.11_django-assets/build/django_assets
> copying django_assets/loaders.py -> 
> /<>/.pybuild/cpython3_3.11_django-assets/build/django_assets
> copying django_assets/manifest.py -> 
> /<>/.pybuild/cpython3_3.11_django-assets/build/django_assets
> copying django_assets/pytest_plugin.py -> 
> /<>/.pybuild/cpython3_3.11_django-assets/build/django_assets
> copying django_assets/env.py -> 
> /<>/.pybuild/cpython3_3.11_django-assets/build/django_assets
> copying django_assets/filter.py -> 
> /<>/.pybuild/cpython3_3.11_django-assets/build/django_assets
> copying django_assets/finders.py -> 
> /<>/.pybuild/cpython3_3.11_django-assets/build/django_assets
> creating 
> /<>/.pybuild/cpython3_3.11_django-assets/build/django_assets/management
> copying django_assets/management/__init__.py -> 
> /<>/.pybuild/cpython3_3.11_django-assets/build/django_assets/management
> creating 
> /<>/.pybuild/cpython3_3.11_django-assets/build/django_assets/templatetags
> copying django_assets/templatetags/__init__.py -> 
> /<>/.pybuild/cpython3_3.11_django-assets/build/django_assets/templatetags
> copying django_assets/templatetags/assets.py -> 
> /<>/.pybuild/cpython3_3.11_django-assets/build/django_assets/templatetags
> creating 
> /<>/.pybuild/cpython3_3.11_django-assets/build/django_assets/management/commands
> copying django_assets/management/commands/__init__.py -> 
> /<>/.pybuild/cpython3_3.11_django-assets/build/django_assets/management/commands
> copying django_assets/management/commands/assets.py -> 
> /<>/.pybuild/cpython3_3.11_django-assets/build/django_assets/management/commands
> I: pybuild base:240: /usr/bin/python3 setup.py build 
> running build
> running build_py
> creating 
> /<>/.pybuild/cpython3_3.10_django-assets/build/django_assets
> copying django_assets/__init__.py -> 
> /<>/.pybuild/cpython3_3.10_django-assets/build/django_assets
> copying django_assets/glob.py -> 
> /<>/.pybuild/cpython3_3.10_django-assets/build/django_assets
> copying django_assets/models.py -> 
> /<>/.pybuild/cpython3_3.10_django-assets/build/django_assets
> copying django_assets/settings.py -> 
> /<>/.pybuild/cpython3_3.10_django-assets/build/django_assets
> copying django_assets/loaders.py -> 
> /<>/.pybuild/cpython3_3.10_django-assets/build/django_assets
> copying django_assets/manifest.py -> 
> /<>/.pybuild/cpython3_3.10_django-assets/build/django_assets
> copying django_assets/pytest_plugin.py -> 
> /<>/.pybuild/cpython3_3.10_django-assets/build/django_assets
> copying django_assets/env.py -> 
> /<>/.pybuild/cpython3_3.10_django-assets/build/django_assets
> copying django_assets/filter.py -> 
> /<>/.pybuild/cpython3_3.10_django-assets/build/django_assets
> copying django_assets/finders.py -> 
> /<>/.pybuild/cpython3_3.10_django-assets/build/django_assets
> creating 
> /<>/.pybuild/cpython3_3.10_django-assets/build/django_assets/management
> copying django_assets/management/__init__.py -> 
> /<>/.pybuild/cpython3_3.10_django-assets/build/django_assets/management
> creating 
> /<>/.pybuild/cpython3_3.10_django-assets/build/django_assets/templatetags
> copying django_assets/templatetags/__init__.py -> 
> /<>/.pybuild/cpython3_3.10_django-assets/build/django_assets/templatetags
> copying django_assets/templa

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

2023-02-04 Thread Debian Bug Tracking System

Your message dated Sat, 04 Feb 2023 12:04:46 +
with message-id 
and subject line Bug#1026740: fixed in pyct 0.5.0-1
has caused the Debian Bug report #1026740,
regarding pyct: FTBFS: dh_auto_test: error: pybuild --test --test-pytest -i 
python{version} -p "3.11 3.10" 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.)


-- 
1026740: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1026740
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: pyct
Version: 0.4.7a3-2
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20221220 ftbfs-bookworm

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 --buildsystem=pybuild
>dh_update_autotools_config -O--buildsystem=pybuild
>dh_autoreconf -O--buildsystem=pybuild
>dh_auto_configure -O--buildsystem=pybuild
> I: pybuild base:240: python3.11 setup.py config 
> /usr/lib/python3/dist-packages/setuptools/config/setupcfg.py:508: 
> SetuptoolsDeprecationWarning: The license_file parameter is deprecated, use 
> license_files instead.
>   warnings.warn(msg, warning_class)
> running config
> I: pybuild base:240: python3.10 setup.py config 
> /usr/lib/python3/dist-packages/setuptools/config/setupcfg.py:508: 
> SetuptoolsDeprecationWarning: The license_file parameter is deprecated, use 
> license_files instead.
>   warnings.warn(msg, warning_class)
> running config
>dh_auto_build -O--buildsystem=pybuild
> I: pybuild base:240: /usr/bin/python3.11 setup.py build 
> /usr/lib/python3/dist-packages/setuptools/config/setupcfg.py:508: 
> SetuptoolsDeprecationWarning: The license_file parameter is deprecated, use 
> license_files instead.
>   warnings.warn(msg, warning_class)
> running build
> running build_py
> creating /<>/.pybuild/cpython3_3.11_pyct/build/pyct
> copying pyct/__init__.py -> 
> /<>/.pybuild/cpython3_3.11_pyct/build/pyct
> copying pyct/build.py -> 
> /<>/.pybuild/cpython3_3.11_pyct/build/pyct
> copying pyct/report.py -> 
> /<>/.pybuild/cpython3_3.11_pyct/build/pyct
> copying pyct/cmd.py -> /<>/.pybuild/cpython3_3.11_pyct/build/pyct
> creating /<>/.pybuild/cpython3_3.11_pyct/build/pyct/tests
> copying pyct/tests/__init__.py -> 
> /<>/.pybuild/cpython3_3.11_pyct/build/pyct/tests
> copying pyct/tests/test_cmd.py -> 
> /<>/.pybuild/cpython3_3.11_pyct/build/pyct/tests
> copying pyct/tests/test_report.py -> 
> /<>/.pybuild/cpython3_3.11_pyct/build/pyct/tests
> running egg_info
> creating pyct.egg-info
> writing pyct.egg-info/PKG-INFO
> writing dependency_links to pyct.egg-info/dependency_links.txt
> writing entry points to pyct.egg-info/entry_points.txt
> writing requirements to pyct.egg-info/requires.txt
> writing top-level names to pyct.egg-info/top_level.txt
> writing manifest file 'pyct.egg-info/SOURCES.txt'
> reading manifest file 'pyct.egg-info/SOURCES.txt'
> reading manifest template 'MANIFEST.in'
> adding license file 'LICENSE.txt'
> writing manifest file 'pyct.egg-info/SOURCES.txt'
> copying pyct/.version -> 
> /<>/.pybuild/cpython3_3.11_pyct/build/pyct
> I: pybuild base:240: /usr/bin/python3 setup.py build 
> /usr/lib/python3/dist-packages/setuptools/config/setupcfg.py:508: 
> SetuptoolsDeprecationWarning: The license_file parameter is deprecated, use 
> license_files instead.
>   warnings.warn(msg, warning_class)
> running build
> running build_py
> creating /<>/.pybuild/cpython3_3.10_pyct/build/pyct
> copying pyct/__init__.py -> 
> /<>/.pybuild/cpython3_3.10_pyct/build/pyct
> copying pyct/build.py -> 
> /<>/.pybuild/cpython3_3.10_pyct/build/pyct
> copying pyct/report.py -> 
> /<>/.pybuild/cpython3_3.10_pyct/build/pyct
> copying pyct/cmd.py -> /<>/.pybuild/cpython3_3.10_pyct/build/pyct
> creating /<>/.pybuild/cpython3_3.10_pyct/build/pyct/tests
> copying pyct/tests/__init__.py -> 
> /<>/.pybuild/cpython3_3.10_pyct/build/pyct/tests
> copying pyct/tests/test_cmd.py -> 
> /<>/.pybuild/cpython3_3.10_pyct/build/pyct/tests
> copying pyct/tests/test_report.py -> 
> /<>/.pybuild/cpython3_3.10_pyct/build/pyct/tests
> running egg_info
> writing pyct.egg-info/PKG-INFO
> writing dependency_links to pyct.egg-info/dependency_links.txt
> writing entry points to pyct.egg-info/entry_points.txt
> writing requirements to pyct.egg-info/requires.txt
> writing top-level names to pyct.egg-info/top_level.txt
> reading manifest file 'pyct.egg-info/SOURCES.txt'
> reading manifest template 'MANIFEST.in'
> adding license file 'LICENSE.txt'
> writing manifest file 'pyct.egg-info/SOU

Processed: retitle 1030447 to libgeo-distance-xs-perl: FTBFS: Failed test 'PP version loads XS'

2023-02-04 Thread Debian Bug Tracking System

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

> retitle 1030447 libgeo-distance-xs-perl: FTBFS: Failed test 'PP version loads 
> XS'
Bug #1030447 [src:libgeo-distance-xs-perl] libgeo-distance-xs-perl: FTBFS: 
make[1]: *** [Makefile:1020: test_dynamic] Error 255
Changed Bug title to 'libgeo-distance-xs-perl: FTBFS: Failed test 'PP version 
loads XS'' from 'libgeo-distance-xs-perl: FTBFS: make[1]: *** [Makefile:1020: 
test_dynamic] Error 255'.
> thanks
Stopping processing here.

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

Processed: Re: Bug#1030447: libgeo-distance-xs-perl: FTBFS: make[1]: *** [Makefile:1020: test_dynamic] Error 255

2023-02-04 Thread Debian Bug Tracking System

Processing control commands:

> tag -1 + confirmed
Bug #1030447 [src:libgeo-distance-xs-perl] libgeo-distance-xs-perl: FTBFS: 
Failed test 'PP version loads XS'
Added tag(s) confirmed.

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

Bug#1030447: libgeo-distance-xs-perl: FTBFS: make[1]: *** [Makefile:1020: test_dynamic] Error 255

2023-02-04 Thread gregor herrmann

Control: tag -1 + confirmed

On Sat, 04 Feb 2023 08:36:56 +0100, Lucas Nussbaum wrote:

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

> > #   Failed test 'PP version loads XS'
> > #   at t/02_new_pp.t line 11.
> > #  got: ''
> > # expected: '1'
> > # Looks like you failed 1 test of 1.
> > t/02_new_pp.t .. 
> > not ok 1 - PP version loads XS
> > 1..1
> > Dubious, test returned 1 (wstat 256, 0x100)
> > Failed 1/1 subtests 

> > Test Summary Report
> > ---
> > t/02_new_pp.t(Wstat: 256 (exited 1) Tests: 1 Failed: 1)
> >   Failed test:  1
> >   Non-zero exit status: 1
> > Files=5, Tests=20,  0 wallclock secs ( 0.04 usr  0.01 sys +  0.42 cusr  
> > 0.06 csys =  0.53 CPU)
> > Result: FAIL
> > Failed 1/5 test programs. 1/20 subtests failed.

libgeo-distance-perl 0.25-1 stopped loading Geo::Distance::XS which
is tested in t/02_new_pp.t:

#v+
# Tests that Geo::Distance automatically loads the XS version.
my $geo = Geo::Distance->new;
is defined $Geo::Distance::XS::VERSION, 1, 'PP version loads XS';
#v-

We can skip this test; or think about removing the package …

(The only reverse dependency is a Recommends in libgeo-distance-perl
which I'm about to remove now.)

Cheers,
gregor

-- 
 .''`.  https://info.comodo.priv.at -- Debian Developer https://www.debian.org
 : :' : OpenPGP fingerprint D1E1 316E 93A7 60A8 104D  85FA BB3A 6801 8649 AA06
 `. `'  Member VIBE!AT & SPI Inc. -- Supporter Free Software Foundation Europe
   `-   NP: Leonard Cohen: Take This Waltz


signature.asc
Description: Digital Signature

Bug#1030418: rust-protoc-rust: FTBFS

2023-02-04 Thread matthias . geiger1024

PS: both value-bag and serde-fmt are installable on my sid machine.

Matthias Geiger (werdahias)

Bug#1030486: marked as done (pytest-qt: FTBFS: dpkg-buildpackage: error: dpkg-source -b . subprocess returned exit status 2)

2023-02-04 Thread Debian Bug Tracking System

Your message dated Sat, 04 Feb 2023 13:50:19 +
with message-id 
and subject line Bug#1030486: fixed in pytest-qt 4.2.0+repack-1
has caused the Debian Bug report #1030486,
regarding pytest-qt: FTBFS: dpkg-buildpackage: error: dpkg-source -b . 
subprocess returned exit status 2
to be marked as done.

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

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


-- 
1030486: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1030486
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: pytest-qt
Version: 4.2.0-1
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20230203 ftbfs-bookworm

Hi,

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


Relevant part (hopefully):
> make[2]: Entering directory '/<>/docs'
> rm -rf _build/*
> make[2]: Leaving directory '/<>/docs'
> make[1]: Leaving directory '/<>'
>dh_autoreconf_clean -O--buildsystem=pybuild
>dh_clean -O--buildsystem=pybuild
>  dpkg-source -b .
> dpkg-source: info: using options from pytest-qt-4.2.0/debian/source/options: 
> --extend-diff-ignore=^[^/]+\.egg-info/
> dpkg-source: info: using source format '3.0 (quilt)'
> dpkg-source: info: building pytest-qt using existing 
> ./pytest-qt_4.2.0.orig.tar.gz
> dpkg-source: info: using patch list from debian/patches/series
> dpkg-source: info: local changes detected, the modified files are:
>  pytest-qt-4.2.0/src/pytestqt/_version.py
> dpkg-source: error: aborting due to unexpected upstream changes, see 
> /tmp/pytest-qt_4.2.0-1.diff.3bxLOS
> dpkg-source: info: Hint: make sure the version in debian/changelog matches 
> the unpacked source tree
> dpkg-source: info: you can integrate the local changes with dpkg-source 
> --commit
> dpkg-buildpackage: error: dpkg-source -b . subprocess returned exit status 2
> 
> Build finished at 2023-02-04T03:00:28Z


The full build log is available from:
http://qa-logs.debian.net/2023/02/03/pytest-qt_4.2.0-1_unstable.log

All bugs filed during this archive rebuild are listed at:
https://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=ftbfs-20230203;users=lu...@debian.org
or:
https://udd.debian.org/bugs/?release=na&merged=ign&fnewerval=7&flastmodval=7&fusertag=only&fusertagtag=ftbfs-20230203&fusertaguser=lu...@debian.org&allbugs=1&cseverity=1&ctags=1&caffected=1#results

A list of current common problems and possible solutions is available at
http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute!

If you reassign this bug to another package, please mark it as 'affects'-ing
this package. See https://www.debian.org/Bugs/server-control#affects

If you fail to reproduce this, please provide a build log and diff it with mine
so that we can identify if something relevant changed in the meantime.
--- End Message ---
--- Begin Message ---
Source: pytest-qt
Source-Version: 4.2.0+repack-1
Done: Timo Röhling 

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

Debian distribution maintenance software
pp.
Timo Röhling  (supplier of updated pytest-qt package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Sat, 04 Feb 2023 11:34:01 +0100
Source: pytest-qt
Architecture: source
Version: 4.2.0+repack-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Python Team 
Changed-By: Timo Röhling 
Closes: 1030486
Changes:
 pytest-qt (4.2.0+repack-1) unstable; urgency=medium
 .
   * Team upload.
   * Retarget d/watch to Github
   * Repack upstream source to remove the (now conflicting)
 auto-generated _version.py (Closes: #1030486)
   * Clean up d/rules
   * Bump Standards-Version to 4.6.2
   * Move to pybuild-autopkgtest
   * Drop ${sphinxdoc:Built-Using} from python-pytestqt-doc
Checksums-Sha1:
 417cdf5726b8be6ee4968d37d829f58932537acf 2286 pytest-qt_4.2.0+repack-1.dsc
 6260eea36953c90ea511015c9c7db9c2ce4d1b5e 101108 
pytest-qt_4.2.0+repack.orig.tar.xz
 0967a18bebf4aa589541aac50d0897205cef3b18 5548 
pytest-qt_4.2.0+repack-1.debian.tar.xz
 7884039388dcc

Bug#1030525: src:stockfish: fails to migrate to testing for too long: FTBFS on armel and mipsel

2023-02-04 Thread Paul Gevers


Source: stockfish
Version: 14.1-1
Severity: serious
Control: close -1 15.1-1
Tags: sid bookworm 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 60 days as having a Release Critical bug in 
testing [1]. Your package src:stockfish has been trying to migrate for 
61 days [2]. Hence, I am filing this bug. Your package failed to build 
from source on armel and mipsel, while it built there successfully in 
the past.


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 bookworm, 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/2020/02/msg5.html
[2] https://qa.debian.org/excuses.php?package=stockfish



OpenPGP_signature
Description: OpenPGP digital signature

Processed: src:stockfish: fails to migrate to testing for too long: FTBFS on armel and mipsel

2023-02-04 Thread Debian Bug Tracking System

Processing control commands:

> close -1 15.1-1
Bug #1030525 [src:stockfish] src:stockfish: fails to migrate to testing for too 
long: FTBFS on armel and mipsel
Marked as fixed in versions stockfish/15.1-1.
Bug #1030525 [src:stockfish] src:stockfish: fails to migrate to testing for too 
long: FTBFS on armel and mipsel
Marked Bug as done

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

Processed: Re: Bug#1030093: Info received (Bug#1030093: dgit: can't import python-coverage.)

2023-02-04 Thread Debian Bug Tracking System

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

> severity 1030093 serious
Bug #1030093 [dgit] dgit: can't import python-coverage.
Severity set to 'serious' from 'normal'
> --
Stopping processing here.

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

Processed: closing 1030220

2023-02-04 Thread Debian Bug Tracking System

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

> close 1030220
Bug #1030220 [src:xrayutilities] xrayutilities: missing dependency on 
python3-h5py breaks armel tests
Marked Bug as done
> thanks
Stopping processing here.

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

Bug#1030220: closing 1030220

2023-02-04 Thread Jochen Sprickerhof

close 1030220 
thanks

Fixed in 1.7.4-1+b3.

Bug#1004795: marked as done (gazebo: FTBFS with ffmpeg 5.0)

2023-02-04 Thread Debian Bug Tracking System

Your message dated Sat, 04 Feb 2023 15:13:21 +
with message-id 
and subject line Bug#1030508: Removed package(s) from unstable
has caused the Debian Bug report #1004795,
regarding gazebo: FTBFS with ffmpeg 5.0
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.)


-- 
1004795: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1004795
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: gazebo
Version: 11.9.1+dfsg-8
Severity: important
X-Debbugs-Cc: sramac...@debian.org
Tags: sid bookworm ftbfs
Usertags: ffmpeg5.0

gazebo FTBFS with ffmpeg 5.0 in experimental:

[  6%] Building CXX object 
gazebo/msgs/CMakeFiles/gazebomsgs_out.dir/generator/gazebo_generator.cc.o
cd /<>/obj-x86_64-linux-gnu/gazebo/msgs && /usr/lib/ccache/c++ 
-DBOOST_TEST_DYN_LINK -DBUILDING_DLL -DHAVE_OPENGL -DIGN_PROFILER_ENABLE=0 
-DLIBBULLET_VERSION=3.05 -DLIBBULLET_VERSION_GT_282 -I/<> 
-I/<>/obj-x86_64-linux-gnu 
-I/<>/obj-x86_64-linux-gnu/gazebo/msgs -I/usr/include/libusb-1.0 
-I/usr/include/ignition/transport8 -I/usr/include/ignition/common3 
-I/usr/include/ignition/fuel_tools4 -isystem /usr/include/ignition/msgs5 
-isystem /usr/include/ignition/math6 -isystem /usr/include/OGRE/RTShaderSystem 
-isystem /usr/include/OGRE -isystem /usr/include/OGRE/Terrain -isystem 
/usr/include/OGRE/Paging -isystem /usr/include/OGRE/Overlay -isystem 
/usr/include/sdformat-9.6 -g -O2 -ffile-prefix-map=/<>=. 
-fstack-protector-strong -Wformat -Werror=format-security -Wdate-time 
-D_FORTIFY_SOURCE=2   -Wall -Wextra -Wno-long-long -Wno-unused-value 
-Wfloat-equal -Wshadow -Wswitch-default -Wmissing-include-dirs -pedantic 
-fvisibility=hidden -fvisibility-inlines-hidden-fPIC -MD -MT 
gazebo/msgs/CMakeFiles/gazebomsgs_out.dir/generator/gazebo_generator.cc.o -MF 
CMakeFiles/gazebomsgs_out.dir/generator/gazebo_generator.cc.o.d -o 
CMakeFiles/gazebomsgs_out.dir/generator/gazebo_generator.cc.o -c 
/<>/gazebo/msgs/generator/gazebo_generator.cc
/<>/gazebo/common/AudioDecoder.cc: In member function ‘bool 
gazebo::common::AudioDecoder::Decode(uint8_t**, unsigned int*)’:
/<>/gazebo/common/AudioDecoder.cc:100:17: warning: ‘void 
av_init_packet(AVPacket*)’ is deprecated [-Wdeprecated-declarations]
  100 |   av_init_packet(&packet);
  |   ~~^
In file included from /usr/include/x86_64-linux-gnu/libavcodec/avcodec.h:45,
 from /<>/gazebo/common/ffmpeg_inc.h:32,
 from /<>/gazebo/common/AudioDecoder.cc:21:
/usr/include/x86_64-linux-gnu/libavcodec/packet.h:506:6: note: declared here
  506 | void av_init_packet(AVPacket *pkt);
  |  ^~
/<>/gazebo/common/AudioDecoder.cc:116:24: error: 
‘avcodec_decode_audio4’ was not declared in this scope; did you mean 
‘avcodec_decode_subtitle2’?
  116 | bytesDecoded = avcodec_decode_audio4(this->codecCtx, 
decodedFrame,
  |^
  |avcodec_decode_subtitle2
/<>/gazebo/common/AudioDecoder.cc: In member function ‘bool 
gazebo::common::AudioDecoder::SetFile(const string&)’:
/<>/gazebo/common/AudioDecoder.cc:217:38: error: ‘AVStream’ {aka 
‘struct AVStream’} has no member named ‘codec’
  217 | if (this->formatCtx->streams[i]->codec->codec_type == 
AVMEDIA_TYPE_AUDIO)
  |  ^
/<>/gazebo/common/AudioDecoder.cc:241:59: error: ‘AVStream’ {aka 
‘struct AVStream’} has no member named ‘codec’
  241 |   this->codecCtx = this->formatCtx->streams[audioStream]->codec;
  |   ^
/<>/gazebo/common/AudioDecoder.cc:247:37: error: invalid 
conversion from ‘const AVCodec*’ to ‘AVCodec*’ [-fpermissive]
  247 |   this->codec = avcodec_find_decoder(codecCtx->codec_id);
  | ^~~~
  | |
  | const AVCodec*
make[4]: *** [gazebo/common/CMakeFiles/gazebo_common.dir/build.make:107: 
gazebo/common/CMakeFiles/gazebo_common.dir/AudioDecoder.cc.o] Error 1

Cheers
-- 
Sebastian Ramacher


signature.asc
Description: PGP signature
--- End Message ---
--- Begin Message ---
Version: 11.10.1+dfsg-2+rm

Dear submitter,

as the package gazebo has just been removed from the Debian archive
unstable we hereby close the associated bug reports.  We are sorry
that we couldn't deal with your issue properly.

For details on the removal, please see https://bugs.debian.org/1030508

The version of this package that was in Debian prior to this removal
can still be found using http

Bug#1011657: marked as done (gazebo ftbfs: missing symbol from libtiff*)

2023-02-04 Thread Debian Bug Tracking System

Your message dated Sat, 04 Feb 2023 15:13:21 +
with message-id 
and subject line Bug#1030508: Removed package(s) from unstable
has caused the Debian Bug report #1011657,
regarding gazebo ftbfs: missing symbol from libtiff*
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.)


-- 
1011657: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1011657
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: gazebo
Version: 11.10.2+dfsg-1
Severity: serious

I was testing rdeps for onetbb transition but found this issue.
--- End Message ---
--- Begin Message ---
Version: 11.10.1+dfsg-2+rm

Dear submitter,

as the package gazebo has just been removed from the Debian archive
unstable we hereby close the associated bug reports.  We are sorry
that we couldn't deal with your issue properly.

For details on the removal, please see https://bugs.debian.org/1030508

The version of this package that was in Debian prior to this removal
can still be found using https://snapshot.debian.org/.

Please note that the changes have been done on the master archive and
will not propagate to any mirrors until the next dinstall run at the
earliest.

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

Debian distribution maintenance software
pp.
Scott Kitterman (the ftpmaster behind the curtain)--- End Message ---

Bug#1030359: marked as done (debian-edu-router-config fails to install)

2023-02-04 Thread Debian Bug Tracking System

Your message dated Sat, 04 Feb 2023 15:19:43 +
with message-id 
and subject line Bug#1030359: fixed in debian-edu-router 2.12.2
has caused the Debian Bug report #1030359,
regarding debian-edu-router-config fails to install
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.)


-- 
1030359: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1030359
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: debian-edu-router-config
Version: 2.12.1
Severity: serious

https://piuparts.debian.org/sid/fail/debian-edu-router-config_2.12.1.log

...
  Setting up debian-edu-router-config (2.12.1) ...
  cat: /sys/class/net/eth0/carrier: No such file or directory
  invoke-rc.d: could not determine current runlevel
  invoke-rc.d: policy-rc.d denied execution of stop.
  [ESC][33mWARNING: [ESC][1mSkipping network setup; not enough usable network 
interfaces available.[ESC][m
  Run 'dpkg-reconfigure debian-edu-router-config' to (re-)configure networking.
  invoke-rc.d: could not determine current runlevel
  invoke-rc.d: policy-rc.d denied execution of start.
  debian-edu-router-config: Networking 'ifupdown' reconfigured and restarted.
  invoke-rc.d: could not determine current runlevel
  invoke-rc.d: policy-rc.d denied execution of restart.
  debian-edu-router-config: Firewall 'uif' reconfigured and restarted.
  invoke-rc.d: unknown initscript, /etc/init.d/dnsmasq not found.
  invoke-rc.d: could not determine current runlevel
  debian-edu-router-config: DNS/DHCP service 'dnsmasq' reconfigured and 
restarted.
  /var/lib/dpkg/info/debian-edu-router-config.postinst: line 1358: 
/etc/sysctl.d/30-debian-edu-router-config.conf: No such file or directory
  dpkg: error processing package debian-edu-router-config (--configure):
   installed debian-edu-router-config package post-installation script 
subprocess returned error exit status 1
  Processing triggers for libc-bin (2.36-8) ...
  Errors were encountered while processing:
   debian-edu-router-config
  E: Sub-process /usr/bin/dpkg returned an error code (1)
--- End Message ---
--- Begin Message ---
Source: debian-edu-router
Source-Version: 2.12.2
Done: Mike Gabriel 

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

Debian distribution maintenance software
pp.
Mike Gabriel  (supplier of updated debian-edu-router 
package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Sat, 04 Feb 2023 15:33:09 +0100
Source: debian-edu-router
Architecture: source
Version: 2.12.2
Distribution: unstable
Urgency: medium
Maintainer: Debian Edu Developers 
Changed-By: Mike Gabriel 
Closes: 1030359
Changes:
 debian-edu-router (2.12.2) unstable; urgency=medium
 .
   * debian/debian-edu-router-config.postinst: Create directory /etc/sysctl.d
 before writing a file into it. (Closes: #1030359).
   * fai/config/files/lib/systemd/system/startup-shutdown-chiptune.service/
 GATEWAY: Add license header.
   * debian/copyright: Update copyright attributions.
   * debian/debian-edu-router-config.postrm: Assure purging of our sysctl config
 snippet.
   * lintian: Adjust line number in recursive-privilege-change override.
Checksums-Sha1:
 80a862a95a0646d82fe3ee2953ba85cdccefc575 1920 debian-edu-router_2.12.2.dsc
 5716946cde9554cc26ffea615c30ae51ddff7f65 101800 debian-edu-router_2.12.2.tar.xz
 7ea701823fc177fc63e67f864a01e4df57f264aa 6308 
debian-edu-router_2.12.2_source.buildinfo
Checksums-Sha256:
 741f15e7c21fc828e887744aeddb731ec0b6964763e265f7565b0c9d5ebce661 1920 
debian-edu-router_2.12.2.dsc
 3c7c70daa025543bd0728cbb5751f8bb19bb89d100a80b4d3b1c61f5a6fe6f0d 101800 
debian-edu-router_2.12.2.tar.xz
 f97669197df2da98ba946233ddf00b9a0257a27cf0eee6624088407ca8165906 6308 
debian-edu-router_2.12.2_source.buildinfo
Files:
 ed739cdb74eed1d2d2145ed598ffc4ad 1920 admin optional 
debian-edu-router_2.12.2.dsc
 984e0feacea268de5cc79a9d89d8ddf6 101800 admin optional 
debian-edu-router_2.12.2.tar.xz
 a427ead2a735b2d103f0d601d8372b4f 6308 admin optional 
debian-edu-router_2.12.2_source.buildinfo

-BEGIN PGP SIGNATUR

Bug#1030512: marked as done (python3-anndata needs a source upload to fix the missing python3-h5py dependency)

2023-02-04 Thread Debian Bug Tracking System

Your message dated Sat, 04 Feb 2023 15:24:46 +
with message-id 
and subject line Bug#1030512: fixed in python-anndata 0.8.0-4
has caused the Debian Bug report #1030512,
regarding python3-anndata needs a source upload to fix the missing python3-h5py 
dependency
to be marked as done.

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

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


-- 
1030512: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1030512
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: python3-anndata
Version: 0.8.0-3
Severity: serious

python3-anndata lacks a dependency on python3-h5py due to #1030274.

A no-change rebuild is sufficient, but since binNMUs are not possible
for binary-all this needs a source upload.
--- End Message ---
--- Begin Message ---
Source: python-anndata
Source-Version: 0.8.0-4
Done: Étienne Mollier 

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

Debian distribution maintenance software
pp.
Étienne Mollier  (supplier of updated python-anndata 
package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Sat, 04 Feb 2023 15:38:57 +0100
Source: python-anndata
Architecture: source
Version: 0.8.0-4
Distribution: unstable
Urgency: medium
Maintainer: Debian Med Packaging Team 

Changed-By: Étienne Mollier 
Closes: 1030512
Changes:
 python-anndata (0.8.0-4) unstable; urgency=medium
 .
   * Team upload.
   * Source only upload to fix missing dependency.  (Closes: #1030512)
Checksums-Sha1:
 82fc15a5b7ae70394c38f1baa7c52b1aca4fb1b1 2879 python-anndata_0.8.0-4.dsc
 f76969879664233f86ce6cf55911678e9b0ff16b 5892 
python-anndata_0.8.0-4.debian.tar.xz
Checksums-Sha256:
 a36f5b6c4a92b3a0bea27a2b2223082b01110c19864882aaa3c21f56c9f808ab 2879 
python-anndata_0.8.0-4.dsc
 d29daf1b0d43f7dd1d866c5bed99e58c60bac15cc6ca38dc40ee8d5a793d7849 5892 
python-anndata_0.8.0-4.debian.tar.xz
Files:
 0d60b89217cd735899ec5d90d6d154a4 2879 python optional 
python-anndata_0.8.0-4.dsc
 5a84cd5fe88ccad75ac2f97d26d16f4e 5892 python optional 
python-anndata_0.8.0-4.debian.tar.xz

-BEGIN PGP SIGNATURE-

iQJIBAEBCgAyFiEEj5GyJ8fW8rGUjII2eTz2fo8NEdoFAmPecGcUHGVtb2xsaWVy
QGRlYmlhbi5vcmcACgkQeTz2fo8NEdo/jQ/+ORhN8dYdND23cdqtTQl4m5NC+rzB
kiwjgfsnigC7Mbud68M8oWQjulVsz9Z3Z2XyAWDzcCSwEv4QImdMkukiLkaAagwi
La7ADXN27fzUQFBSnsdR0ey3RaenrXEg0U4gEDC+W+9dkCMpWg3pWXbhDSpF
2y9UVM/hvtDa/OnEy9iFNGwgglgA8N+1Ffg6G3gXAy4l2xP7NNkfhuSp7eToTji0
uFkUTTe307E33XwCVmlma6W6N2XAxQfP+9MFvgXHbsaUarTrGfckDzsF9qi8BEwJ
146bdq/f7R6+Ed9n5Q/C8voB4cOsseFay4nkcIpNYNmA5o6wVmHrJMvECfMJHtXm
Nj5RiewDr8IPLJ673Ht28W8wXx2OzkAZIfyx85QVbgVt0V7t5OJrjsRREw4gqCNR
3jE/SlVOCM3gF7ON4nz03COrmG+EXbyicrfEn7/0oFrngN2OIg3jNoawRoHmwYa3
ItzypZ2UMDwQ4dHy/OARvBkkWCOQly2ooMis34gRFlKbhjdNqQZjVQUxr2ujM/YF
hOdEKLmZuaIZMg2ps9Eqovia68ja5/oOEFEIB5aPWO2y5dm1rv3RyMkynEjwxyVU
f/T2+frOxoFuEVjMy2R8xhTDPgGvXkyoLQDb3eHjWg8yrU/jI0zN2Iu0Yyh+sjio
G/Qd0HVqcb3gbNc=
=KsTH
-END PGP SIGNATURE End Message ---

Bug#1030466: marked as forwarded (datalad-container: FTBFS: make[1]: *** [debian/rules:16: override_dh_auto_install] Error 2)

2023-02-04 Thread Debian Bug Tracking System

Your message dated Sat, 4 Feb 2023 10:17:06 -0500
with message-id 
has caused the   report #1030466,
regarding datalad-container: FTBFS: make[1]: *** [debian/rules:16: 
override_dh_auto_install] Error 2
to be marked as having been forwarded to the upstream software
author(s) 

(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.)


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

https://github.com/datalad/datalad-container/pull/192
and similar ones in (not in debian)
https://github.com/datalad/datalad-extension-template/pull/53
https://github.com/datalad/datalad-deprecated/pull/81

we will release -container asap and update the package

-- 
Yaroslav O. Halchenko
Center for Open Neuroscience http://centerforopenneuroscience.org
Dartmouth College, 419 Moore Hall, Hinman Box 6207, Hanover, NH 03755
WWW:   http://www.linkedin.com/in/yarik--- End Message ---

Processed: your mail

2023-02-04 Thread Debian Bug Tracking System

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

> tags 1030483 + confirmed
Bug #1030483 [src:beginend-el] beginend-el: FTBFS: error: (file-missing (lambda 
(arg72 &rest arg73) (let ((f #'message)) (apply f arg72 arg73))) "Setting 
current directory" "No such file or directory" "/tmp/temp-fs-MQAR3w")
Added tag(s) confirmed.
> tags 1030483 + upstream
Bug #1030483 [src:beginend-el] beginend-el: FTBFS: error: (file-missing (lambda 
(arg72 &rest arg73) (let ((f #'message)) (apply f arg72 arg73))) "Setting 
current directory" "No such file or directory" "/tmp/temp-fs-MQAR3w")
Added tag(s) upstream.
> thanks
Stopping processing here.

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

Bug#1030530: python3.10 should not be in bookworm

2023-02-04 Thread Adrian Bunk

Package: python3.10
Severity: serious

python3.10 should not be in bookworm.

This bug will bring python3.10 on the autoremoval list when no key
package in bookworm is using it anymore.

Processed: fixed 1025816 in 1.0.2-2+deb9u2, fixed 1025816 in 1.0.3-1+deb10u3

2023-02-04 Thread Debian Bug Tracking System

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

> fixed 1025816 1.0.2-2+deb9u2
Bug #1025816 {Done: Tobias Frost } [src:libde265] libde265: 
CVE-2022-43243 CVE-2022-43248 CVE-2022-43253
The source 'libde265' and version '1.0.2-2+deb9u2' do not appear to match any 
binary packages
Marked as fixed in versions libde265/1.0.2-2+deb9u2.
> fixed 1025816 1.0.3-1+deb10u3
Bug #1025816 {Done: Tobias Frost } [src:libde265] libde265: 
CVE-2022-43243 CVE-2022-43248 CVE-2022-43253
The source 'libde265' and version '1.0.3-1+deb10u3' do not appear to match any 
binary packages
Marked as fixed in versions libde265/1.0.3-1+deb10u3.
> thanks
Stopping processing here.

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

Processed: fixed 1014977 in 1.0.2-2+deb9u2

2023-02-04 Thread Debian Bug Tracking System

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

> fixed 1014977 1.0.2-2+deb9u2
Bug #1014977 {Done: Philipp Kern } [src:libde265] libde265: 
CVE-2022-1253 CVE-2021-36411 CVE-2021-36410 CVE-2021-36408 CVE-2021-35452
The source 'libde265' and version '1.0.2-2+deb9u2' do not appear to match any 
binary packages
Marked as fixed in versions libde265/1.0.2-2+deb9u2.
> thanks
Stopping processing here.

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

Processed: fixed 1004963 in 1.0.2-2+deb9u2

2023-02-04 Thread Debian Bug Tracking System

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

> fixed 1004963 1.0.2-2+deb9u2
Bug #1004963 {Done: Tobias Frost } [src:libde265] 
CVE-2020-21598 CVE-2020-21600 CVE-2020-21602
The source 'libde265' and version '1.0.2-2+deb9u2' do not appear to match any 
binary packages
Marked as fixed in versions libde265/1.0.2-2+deb9u2.
> thanks
Stopping processing here.

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

Bug#1030408: duecredit: FTBFS: pkg_resources.extern.packaging.version.InvalidVersion: Invalid version: '0.9.1.debian1'

2023-02-04 Thread Drew Parsons

Package: python3-duecredit
Followup-For: Bug #1030408
Control: forwarded -1 https://github.com/duecredit/duecredit/pull/184

This bug is affecting unrelated packages, confirming the Severity:serious.
For instance the new mp_api module tries to read its version using
pkg_resources.get_distribution, but fails with
  InvalidVersion: Invalid version: '0.9.1.debian1'
duecredit is the only package with version 0.9.1.debian1
(mp_api's version is 0.27.5)

Upstream has seen the issue and provided a patch, just released in
v0.9.2

Could upgrade to that version, or alternatively could pull in just the
patch from https://github.com/duecredit/duecredit/pull/184

Might as well upgrade to 0.9.2 since there is only one other
commit, it won't be disruptive.

Processed: Re: duecredit: FTBFS: pkg_resources.extern.packaging.version.InvalidVersion: Invalid version: '0.9.1.debian1'

2023-02-04 Thread Debian Bug Tracking System

Processing control commands:

> forwarded -1 https://github.com/duecredit/duecredit/pull/184
Bug #1030408 [src:duecredit] duecredit: FTBFS: 
pkg_resources.extern.packaging.version.InvalidVersion: Invalid version: 
'0.9.1.debian1'
Set Bug forwarded-to-address to 
'https://github.com/duecredit/duecredit/pull/184'.

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

Bug#1027361: marked as done (e2tools: FTBFS in bullseye (missing build-depends on e2fsprogs))

2023-02-04 Thread Debian Bug Tracking System

Your message dated Sat, 04 Feb 2023 17:17:10 +
with message-id 
and subject line Bug#1027361: fixed in e2tools 0.1.0-1+deb11u1
has caused the Debian Bug report #1027361,
regarding e2tools: FTBFS in bullseye (missing build-depends on e2fsprogs)
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.)


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

Package: src:e2tools
Version: 0.1.0-1
Severity: serious
Tags: ftbfs patch

Dear maintainer:

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


[...]
 debian/rules binary-arch
dh binary-arch
   dh_update_autotools_config -a
   dh_autoreconf -a
   dh_auto_configure -a
./configure --build=x86_64-linux-gnu --prefix=/usr 
--includedir=\${prefix}/include --mandir=\${prefix}/share/man 
--infodir=\${prefix}/share/info --sysconfdir=/etc --localstatedir=/var 
--disable-option-checking --disable-silent-rules 
--libdir=\${prefix}/lib/x86_64-linux-gnu --runstatedir=/run 
--disable-maintainer-mode --disable-dependency-tracking
checking for a BSD-compatible install... /usr/bin/install -c
checking whether build environment is sane... yes
checking for a thread-safe mkdir -p... /bin/mkdir -p
checking for gawk... no
checking for mawk... mawk
checking whether make sets $(MAKE)... yes
checking whether make supports nested variables... yes
checking for gcc... gcc
checking whether the C compiler works... yes
checking for C compiler default output file name... a.out
checking for suffix of executables...
checking whether we are cross compiling... no
checking for suffix of object files... o
checking whether we are using the GNU C compiler... yes
checking whether gcc accepts -g... yes
checking for gcc option to accept ISO C89... none needed
checking whether gcc understands -c and -o together... yes
checking whether make supports the include directive... yes (GNU style)
checking dependency style of gcc... none
checking how to run the C preprocessor... gcc -E
checking for grep that handles long lines and -e... /bin/grep
checking for egrep... /bin/grep -E
checking for Minix Amsterdam compiler... no
checking for ar... ar
checking for ranlib... ranlib
checking for ANSI C header files... yes
checking for sys/types.h... yes
checking for sys/stat.h... yes
checking for stdlib.h... yes
checking for string.h... yes
checking for memory.h... yes
checking for strings.h... yes
checking for inttypes.h... yes
checking for stdint.h... yes
checking for unistd.h... yes
checking minix/config.h usability... no
checking minix/config.h presence... no
checking for minix/config.h... no
checking whether it is safe to define __EXTENSIONS__... yes
checking whether _XOPEN_SOURCE should be defined... no
checking whether ln -s works... yes
checking for a sed that does not truncate output... /bin/sed
checking whether make sets $(MAKE)... (cached) yes
checking for chmod... /bin/chmod
checking for dd... /bin/dd
checking for mkfs.ext2... no
checking for unsigned long long int... yes
checking for long long int... yes
checking wchar.h usability... yes
checking wchar.h presence... yes
checking for wchar.h... yes
checking for stdint.h... (cached) yes
checking for inttypes.h... (cached) yes
checking utime.h usability... yes
checking utime.h presence... yes
checking for utime.h... yes
checking whether the preprocessor supports include_next... yes
checking whether system header files limit the line length... no
checking build system type... x86_64-pc-linux-gnu
checking host system type... x86_64-pc-linux-gnu
checking whether stdint.h conforms to C99... yes
checking whether imaxabs is declared without a macro... yes
checking whether imaxdiv is declared without a macro... yes
checking whether strtoimax is declared without a macro... yes
checking whether strtoumax is declared without a macro... yes
checking for inttypes.h... (cached) yes
checking whether the inttypes.h PRIxNN macros are broken... no
checking for pid_t... yes
checking for mode_t... yes
checking whether INT32_MAX < INTMAX_MAX... yes
checking whether INT64_MAX == LONG_MAX... yes
checking whether UINT32_MAX < UINTMAX_MAX... yes
checking whether UINT64_MAX == ULONG_MAX... yes
checking for ssize_t... yes
checking for pkg-config... /usr/bin/pkg-config
checking pkg-config is at least version 0.9.0... yes
checking for EXT2FS... yes
checking for COM_ERR... yes
checking for ANSI C header files... (cached) yes
checking errno.h usability... yes
checking errno.h presence... yes
checking

Bug#1029561: marked as done (CVE-2022-47951: vulnerability in VMDK image processing)

2023-02-04 Thread Debian Bug Tracking System

Your message dated Sat, 04 Feb 2023 17:17:11 +
with message-id 
and subject line Bug#1029561: fixed in nova 2:22.0.1-2+deb11u1
has caused the Debian Bug report #1029561,
regarding CVE-2022-47951: vulnerability in VMDK image processing
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.)


-- 
1029561: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1029561
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: nova-compute
Version: 2:26.0.0-5
Severity: grave
Tags: patch

This is an advance warning of a vulnerability discovered in
OpenStack, to give you, as downstream stakeholders, a chance to
coordinate the release of fixes and reduce the vulnerability window.
Please treat the following information as confidential until the
proposed public disclosure date.

Title: Arbitrary file access through custom VMDK flat descriptor
Reporter: Guillaume Espanel, Pierre Libeau, Arnaud Morin and Damien
  Rannou (OVH)
Products: Cinder, Glance, Nova
Affects: Cinder <19.1.2, >=20.0.0 <20.0.2, ==21.0.0;
 Glance <23.0.1, >=24.0.0 <24.1.1, ==25.0.0;
 Nova <24.1.2, >=25.0.0 <25.0.2, ==26.0.0

Description:
Guillaume Espanel, Pierre Libeau, Arnaud Morin and Damien Rannou
(OVH) reported a vulnerability in VMDK image processing for Cinder,
Glance and Nova. By supplying a specially created VMDK flat image
which references a specific backing file path, an authenticated user
may convince systems to return a copy of that file's contents from
the server resulting in unauthorized access to potentially sensitive
data. All Cinder deployments are affected; only Glance deployments
with image conversion enabled are affected; all Nova deployments are
affected.

Proposed patch:
See attached patches. Unless a flaw is discovered in them, these
patches will be merged to their corresponding branches on the public
disclosure date. Note that stable/wallaby and older branches are
under extended maintenance and will receive no new point releases,
but patches for some of them are provided as a courtesy.

CVE: CVE-2022-47951

Proposed public disclosure date/time:
2023-01-24, 1500UTC
Please do not make the issue public (or release public patches)
before this coordinated embargo date.

Original private report:
https://launchpad.net/bugs/1996188
For access to read and comment on this report, please reply to me
with your Launchpad username and I will subscribe you.
-- 
Jeremy Stanley
OpenStack Vulnerability Management Team
--- End Message ---
--- Begin Message ---
Source: nova
Source-Version: 2:22.0.1-2+deb11u1
Done: Thomas Goirand 

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

Debian distribution maintenance software
pp.
Thomas Goirand  (supplier of updated nova 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: Tue, 24 Jan 2023 11:31:25 +0100
Source: nova
Architecture: source
Version: 2:22.0.1-2+deb11u1
Distribution: bullseye-security
Urgency: medium
Maintainer: Debian OpenStack 
Changed-By: Thomas Goirand 
Closes: 1029561
Changes:
 nova (2:22.0.1-2+deb11u1) bullseye-security; urgency=medium
 .
   * CVE-2022-47951: By supplying a specially created VMDK flat image which
 references a specific backing file path, an authenticated user may convince
 systems to return a copy of that file's contents from the server resulting
 in unauthorized access to potentially sensitive data. Add upstream patch
 cve-2022-47951-glance-stable-victoria.patch (Closes: #1029561).
Checksums-Sha1:
 5b34041838c39107c06f2c2811399bfe5561f5e2 5339 nova_22.0.1-2+deb11u1.dsc
 00feb086c56c8df4d0d85c795e33878eea75766f 5900180 nova_22.0.1.orig.tar.xz
 4ff38fb907f356732392adc21e8dbc18040535e2 62092 
nova_22.0.1-2+deb11u1.debian.tar.xz
 20f5ca56aefae0fd497b1e1c5f0417d5b6c23be9 23807 
nova_22.0.1-2+deb11u1_amd64.buildinfo
Checksums-Sha256:
 7861752c0bcf3238e0751d838637098a4c3e75bf03687c6049e52de3cc42e9c1 5339 
nova_22.0.1-2+deb11u1.dsc
 8bfc2c8d721237ad67f2a15a2882f366f5423f30e2fda802b3234f4280c7a262 5900180 
nova_22.0.1.orig.tar.xz
 11f2390bfe1ba6bfa583ef95

Bug#1029562: marked as done (CVE-2022-47951: vulnerability in VMDK image processing)

2023-02-04 Thread Debian Bug Tracking System

Your message dated Sat, 04 Feb 2023 17:17:09 +
with message-id 
and subject line Bug#1029562: fixed in cinder 2:17.0.1-1+deb11u1
has caused the Debian Bug report #1029562,
regarding CVE-2022-47951: vulnerability in VMDK image processing
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.)


-- 
1029562: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1029562
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: python3-cinder
Version: 2:21.0.0-2
Severity: grave
Tags: patch

This is an advance warning of a vulnerability discovered in
OpenStack, to give you, as downstream stakeholders, a chance to
coordinate the release of fixes and reduce the vulnerability window.
Please treat the following information as confidential until the
proposed public disclosure date.

Title: Arbitrary file access through custom VMDK flat descriptor
Reporter: Guillaume Espanel, Pierre Libeau, Arnaud Morin and Damien
  Rannou (OVH)
Products: Cinder, Glance, Nova
Affects: Cinder <19.1.2, >=20.0.0 <20.0.2, ==21.0.0;
 Glance <23.0.1, >=24.0.0 <24.1.1, ==25.0.0;
 Nova <24.1.2, >=25.0.0 <25.0.2, ==26.0.0

Description:
Guillaume Espanel, Pierre Libeau, Arnaud Morin and Damien Rannou
(OVH) reported a vulnerability in VMDK image processing for Cinder,
Glance and Nova. By supplying a specially created VMDK flat image
which references a specific backing file path, an authenticated user
may convince systems to return a copy of that file's contents from
the server resulting in unauthorized access to potentially sensitive
data. All Cinder deployments are affected; only Glance deployments
with image conversion enabled are affected; all Nova deployments are
affected.

Proposed patch:
See attached patches. Unless a flaw is discovered in them, these
patches will be merged to their corresponding branches on the public
disclosure date. Note that stable/wallaby and older branches are
under extended maintenance and will receive no new point releases,
but patches for some of them are provided as a courtesy.

CVE: CVE-2022-47951

Proposed public disclosure date/time:
2023-01-24, 1500UTC
Please do not make the issue public (or release public patches)
before this coordinated embargo date.

Original private report:
https://launchpad.net/bugs/1996188
For access to read and comment on this report, please reply to me
with your Launchpad username and I will subscribe you.
-- 
Jeremy Stanley
OpenStack Vulnerability Management Team
--- End Message ---
--- Begin Message ---
Source: cinder
Source-Version: 2:17.0.1-1+deb11u1
Done: Thomas Goirand 

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

Debian distribution maintenance software
pp.
Thomas Goirand  (supplier of updated cinder 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: Wed, 18 Jan 2023 09:06:59 +0100
Source: cinder
Architecture: source
Version: 2:17.0.1-1+deb11u1
Distribution: bullseye-security
Urgency: high
Maintainer: Debian OpenStack 
Changed-By: Thomas Goirand 
Closes: 1029562
Changes:
 cinder (2:17.0.1-1+deb11u1) bullseye-security; urgency=high
 .
   * CVE-2022-47951: By supplying a specially created VMDK flat image which
 references a specific backing file path, an authenticated user may convince
 systems to return a copy of that file's contents from the server resulting
 in unauthorized access to potentially sensitive data. Add upstream patch
 cve-2022-47951-cinder-stable-victoria.patch (Closes: #1029562).
Checksums-Sha1:
 a746edeffab61559f6687a32cfd5b23726569cb1 4446 cinder_17.0.1-1+deb11u1.dsc
 bf3252756d954a9cc64397f5412a64ff4e416155 3944016 cinder_17.0.1.orig.tar.xz
 2c2c8632317b24dbdbbc08bb329af285f59d3f5e 49680 
cinder_17.0.1-1+deb11u1.debian.tar.xz
 a00e8535972e15460ec290a1d9f7b96ac2610021 19320 
cinder_17.0.1-1+deb11u1_amd64.buildinfo
Checksums-Sha256:
 99c03544f718fa3bfbace7933d3f48b57686b32055abdaad65ee7ec66ffa1857 4446 
cinder_17.0.1-1+deb11u1.dsc
 9079a000149f68dea0e26e0f4387a6e67299492271479e4cce47ac96ce463f70 3944016 
cinder_17.0.1.orig.tar.xz
 ca

Bug#1029563: marked as done (CVE-2022-47951: vulnerability in VMDK image processing)

2023-02-04 Thread Debian Bug Tracking System

Your message dated Sat, 04 Feb 2023 17:17:10 +
with message-id 
and subject line Bug#1029563: fixed in glance 2:21.0.0-2+deb11u1
has caused the Debian Bug report #1029563,
regarding CVE-2022-47951: vulnerability in VMDK image processing
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.)


-- 
1029563: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1029563
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: glance-api
Version: 2:25.0.0-1.1
Severity: grave
Tags: patch

This is an advance warning of a vulnerability discovered in
OpenStack, to give you, as downstream stakeholders, a chance to
coordinate the release of fixes and reduce the vulnerability window.
Please treat the following information as confidential until the
proposed public disclosure date.

Title: Arbitrary file access through custom VMDK flat descriptor
Reporter: Guillaume Espanel, Pierre Libeau, Arnaud Morin and Damien
  Rannou (OVH)
Products: Cinder, Glance, Nova
Affects: Cinder <19.1.2, >=20.0.0 <20.0.2, ==21.0.0;
 Glance <23.0.1, >=24.0.0 <24.1.1, ==25.0.0;
 Nova <24.1.2, >=25.0.0 <25.0.2, ==26.0.0

Description:
Guillaume Espanel, Pierre Libeau, Arnaud Morin and Damien Rannou
(OVH) reported a vulnerability in VMDK image processing for Cinder,
Glance and Nova. By supplying a specially created VMDK flat image
which references a specific backing file path, an authenticated user
may convince systems to return a copy of that file's contents from
the server resulting in unauthorized access to potentially sensitive
data. All Cinder deployments are affected; only Glance deployments
with image conversion enabled are affected; all Nova deployments are
affected.

Proposed patch:
See attached patches. Unless a flaw is discovered in them, these
patches will be merged to their corresponding branches on the public
disclosure date. Note that stable/wallaby and older branches are
under extended maintenance and will receive no new point releases,
but patches for some of them are provided as a courtesy.

CVE: CVE-2022-47951

Proposed public disclosure date/time:
2023-01-24, 1500UTC
Please do not make the issue public (or release public patches)
before this coordinated embargo date.

Original private report:
https://launchpad.net/bugs/1996188
For access to read and comment on this report, please reply to me
with your Launchpad username and I will subscribe you.
-- 
Jeremy Stanley
OpenStack Vulnerability Management Team
--- End Message ---
--- Begin Message ---
Source: glance
Source-Version: 2:21.0.0-2+deb11u1
Done: Thomas Goirand 

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

Debian distribution maintenance software
pp.
Thomas Goirand  (supplier of updated glance 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: Wed, 18 Jan 2023 10:14:44 +0100
Source: glance
Architecture: source
Version: 2:21.0.0-2+deb11u1
Distribution: bullseye-security
Urgency: medium
Maintainer: Debian OpenStack 
Changed-By: Thomas Goirand 
Closes: 1029563
Changes:
 glance (2:21.0.0-2+deb11u1) bullseye-security; urgency=medium
 .
   * CVE-2022-47951: By supplying a specially created VMDK flat image which
 references a specific backing file path, an authenticated user may convince
 systems to return a copy of that file's contents from the server resulting
 in unauthorized access to potentially sensitive data. Add upstream patch
 cve-2022-47951-glance-stable-victoria.patch (Closes: #1029563).
Checksums-Sha1:
 a55a859e2366820084168fa126fb8e887120c8c9 3768 glance_21.0.0-2+deb11u1.dsc
 5bc58570ac46747db867f53e6633bba8a68d2f0a 1471508 glance_21.0.0.orig.tar.xz
 c8ee1328ec0761ce296fe0fb83d1e7b4d11f25d2 18852 
glance_21.0.0-2+deb11u1.debian.tar.xz
 ffbc487672efc487022e797d9a5f96536ad56882 18111 
glance_21.0.0-2+deb11u1_amd64.buildinfo
Checksums-Sha256:
 738bf183334415d0c78e9546e1c395b225809bfa18b4fc800d6c37ab81ebbba2 3768 
glance_21.0.0-2+deb11u1.dsc
 7e9e96711ca27913cae31c0992a90edd4f572a66768162324ce8aa79ccc7820d 1471508 
glance_21.0.0.orig.tar.xz

Bug#1030533: qt5-avif-image-plugin: file conflict with kimageformat-plugins

2023-02-04 Thread Sebastian Ramacher

Package: qt5-avif-image-plugin
Version: 0.5.1+dfsg-1
Severity: serious

If kimageformat-plugins is installed:

$ apt install --no-install-recommends qt5-avif-image-plugin
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
The following NEW packages will be installed:
  qt5-avif-image-plugin
0 upgraded, 1 newly installed, 0 to remove and 51 not upgraded.
Need to get 17.1 kB of archives.
After this operation, 67.6 kB of additional disk space will be used.
Get:1 http://localhost:3142/debian unstable/main amd64 qt5-avif-image-plugin 
amd64 0.5.1+dfsg-1+b1 [17.1 kB]
Fetched 17.1 kB in 0s (240 kB/s)
debconf: delaying package configuration, since apt-utils is not installed
Selecting previously unselected package qt5-avif-image-plugin.
(Reading database ... 19742 files and directories currently installed.)
Preparing to unpack .../qt5-avif-image-plugin_0.5.1+dfsg-1+b1_amd64.deb ...
Unpacking qt5-avif-image-plugin (0.5.1+dfsg-1+b1) ...
dpkg: error processing archive 
/var/cache/apt/archives/qt5-avif-image-plugin_0.5.1+dfsg-1+b1_amd64.deb 
(--unpack):
 trying to overwrite '/usr/share/kservices5/qimageioplugins/avif.desktop', 
which is also in package kimageformat-plugins 5.102.0-2
Errors were encountered while processing:
 /var/cache/apt/archives/qt5-avif-image-plugin_0.5.1+dfsg-1+b1_amd64.deb
E: Sub-process /usr/bin/dpkg returned an error code (1)

Cheers
-- 
Sebastian Ramacher

Processed: owner 1030485

2023-02-04 Thread Debian Bug Tracking System

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

> owner 1030485 !
Bug #1030485 [src:uima-as] uima-as: FTBFS: [ERROR] Failed to execute goal on 
project uima-as: Could not resolve dependencies for project 
org.apache.uima:uima-as:pom:2.3.1: Cannot access eclipsePlugins 
(http://repo1.maven.org/eclipse) in offline mode and the artifact 
log4j:log4j:jar:1.2.x has not been downloaded from it before. -> [Help 1]
Owner recorded as tony mancill .
> thanks
Stopping processing here.

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

Bug#1030093: dgit: can't import python-coverage.

2023-02-04 Thread Ian Jackson

Ian Jackson writes ("Re: Bug#1030093: dgit: can't import python-coverage."):
> (Also probably gbp pq ought to cope natively, so I will file a bug
> about that.).

This is now
  #1030534: gbp pq import fails with series file containing form feed

-- 
Ian JacksonThese opinions are my own.  

Pronouns: they/he.  If I emailed you from @fyvzl.net or @evade.org.uk,
that is a private address which bypasses my fierce spamfilter.

Bug#1030535: python-pycdlib: FTBFS (AttributeError: module 'inspect' has no attribute 'getargspec')

2023-02-04 Thread Santiago Vila


Package: src:python-pycdlib
Version: 1.12.0+ds1-3
Severity: serious
Tags: ftbfs

Dear maintainer:

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


[...]
=== short test summary info 
===
FAILED tests/integration/test_parse.py::test_parse_write_with_progress - 
AttributeError: module 'inspect' has no attribute 'getargspec'
FAILED 
tests/integration/test_parse.py::test_parse_write_with_progress_three_arg - 
AttributeError: module 'inspect' has no attribute 'getargspec'
= 2 failed, 1702 passed, 17 skipped in 
13.87s =
make[1]: *** [debian/rules:19: override_dh_auto_install] Error 1
make[1]: Leaving directory '/home/sanvila/python-pycdlib-1.12.0+ds1'
make: *** [debian/rules:7: binary] Error 2
dpkg-buildpackage: error: debian/rules binary subprocess returned exit status 2


The above is just how the build ends and I believe it's also the most relevant 
part.

The failure also happens here with similar error message:

https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/python-pycdlib.html


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

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.

Bug#1030093: marked as done (dgit: can't import python-coverage.)

2023-02-04 Thread Debian Bug Tracking System

Your message dated Sat, 04 Feb 2023 18:19:02 +
with message-id 
and subject line Bug#1030093: fixed in dgit 10.6
has caused the Debian Bug report #1030093,
regarding dgit: can't import python-coverage.
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.)


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

Package: dgit

mkdir dgittest
cd dgittest
dget -d 
http://deb.debian.org/debian/pool/main/p/python-coverage/python-coverage_6.5.0+dfsg1-2.dsc
mkdir repo
cd repo
git init
dgit import-dsc ../python-coverage_6.5.0+dfsg1-2.dsc +workingbranch

Dgit metadata in .dsc: NO git hash
using existing python-coverage_6.5.0+dfsg1.orig.tar.xz
using existing python-coverage_6.5.0+dfsg1-2.debian.tar.xz
dpkg-source: info: extracting python-coverage in python-coverage-6.5.0+dfsg1
dpkg-source: info: unpacking python-coverage_6.5.0+dfsg1.orig.tar.xz
dpkg-source: info: unpacking python-coverage_6.5.0+dfsg1-2.debian.tar.xz
warning: gbp pq import failed: subprocess failed with error exit status 1
dgit: trying slow absurd-git-apply...
Traceback (most recent call last):
  File "/usr/bin/gbp", line 149, in 
sys.exit(supercommand())
  File "/usr/bin/gbp", line 145, in supercommand
return module.main(args)
  File "/usr/lib/python3/dist-packages/gbp/scripts/pq.py", line 488, in main
import_pq(repo, current, options)
  File "/usr/lib/python3/dist-packages/gbp/scripts/pq.py", line 374, in 
import_pq
options.upstream_tag)
  File "/usr/lib/python3/dist-packages/gbp/scripts/pq.py", line 335, in 
import_quilt_patches
apply_and_commit_patch(repo, patch, maintainer, patch.topic, name)
  File "/usr/lib/python3/dist-packages/gbp/scripts/common/pq.py", line 313, in 
apply_and_commit_patch
author = {'name': patch.author,
  File "/usr/lib/python3/dist-packages/gbp/patch_series.py", line 181, in author
return self._get_info_field('author')
  File "/usr/lib/python3/dist-packages/gbp/patch_series.py", line 164, in 
_get_info_field
self._read_info()
  File "/usr/lib/python3/dist-packages/gbp/patch_series.py", line 196, in 
_read_info
super(Dep3Patch, self)._read_info()
  File "/usr/lib/python3/dist-packages/gbp/patch_series.py", line 62, in 
_read_info
self._read_git_mailinfo()
  File "/usr/lib/python3/dist-packages/gbp/patch_series.py", line 81, in 
_read_git_mailinfo
for line in open(self.path, 'rb'):
IsADirectoryError: [Errno 21] Is a directory: 
'/home/plugwash/dgittest/repo/.git/dgit/unpack/python-coverage-6.5.0+dfsg1/debian/patches/'
gbp pq import failed: subprocess failed with error exit status 1

I noticed as weird character which mcedit shows as "^L" in 
debian/patches/series, perhaps this is related.

Tested both on my somewhat outdated laptop, and in an up to date sid chroot.
--- End Message ---
--- Begin Message ---
Source: dgit
Source-Version: 10.6
Done: Ian Jackson 

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

Debian distribution maintenance software
pp.
Ian Jackson  (supplier of updated dgit package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Sat, 04 Feb 2023 16:56:30 +
Source: dgit
Architecture: source
Version: 10.6
Distribution: unstable
Urgency: medium
Maintainer: Ian Jackson 
Changed-By: Ian Jackson 
Closes: 1030093
Changes:
 dgit (10.6) unstable; urgency=medium
 .
   Bugfix for handling some source packages:
   * dgit: dsc import: Launder the series file before feeding it to gbp,
 (in absurd git-apply mode) in case it contains strange things.
 Closes: #1030093.  [Report from Peter Green]
 .
   Minor improvements to git-debrebase:
   * git-debrebase(1): Add imprecation to call conclude or prepush, at top
   * git-debrebase(1): Remove launder-v0 from documentation
   * git-debrebase status: Print upstream commitid
 .
   Supporting chnages:
   * dgit: Fix confusing appending of gbp-pq-output in innards.
 (Conceivably this might fix wrong messages in very unusual situations.)
   * dgit: Fix a call to die to be confe

Bug#1030537: rust-reqwest: fails tests requiring network access

2023-02-04 Thread Jonas Smedegaard

Source: rust-reqwest
Version: 0.11.11-3
Severity: serious

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

autopkgtests fails some tests requiring network:

test_rustls_badssl_modern
test_allowed_methods

This was noticed in a migration test of rust-rustls:
https://ci.debian.net/data/autopkgtest/testing/amd64/r/rust-reqwest/31010872/log.gz

 - Jonas

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEn+Ppw2aRpp/1PMaELHwxRsGgASEFAmPeo2oACgkQLHwxRsGg
ASG9RA//X/0VzVbCTz+gn/BuvY+Nh1wJBX/3UJdhuQpuFS0CUlDAVyEe/Pz9mEvM
Fr7JbOHn6ouBlyGQXBM6s9RxJ63l0RxIi9u5cR8P92N2PiETxiGft6Jybkro42Zf
m1Q2Y442AIV+oqyt59Hks50BVBHLO2sj0xdwGB+hr5ZWJFie/FgwPrVf4981CWSI
PhC2zCVZMksSq/o7NGcRZ7P6ExV7aZMkmIGTp3csFyGbPnIYl3WxjIGArEsx2dql
vD9HeAyhR/6Jf4XlXeWUtPcxxeuhgTAwctNJ1NNFGQen9B8YG19hxsq6b+QpDk5U
Qt988Plov1ur7rRj5GqfjA/7IzaIFewBUClJqant09Ef0EwFal8LaxDdAF7kG3BS
UkkvThH8icJFbw+1F3OzrMlMY3lk/NVue9OwEMhKbbqSMdputlF1KDd/WKtgDwXa
lZDAnZEa9xASuY7xcmkjcr48JEKZPKj5y2pI9uMNTnn/gkKRGVrzft4mrpfvz214
W/lOoE+m+7tBmtRcLmEJ+x1L/CW2zYwqZZkSUePT1djkjmOmB2mczXVs3AOzGyll
w43nsPmB1pCwe123NFdMpGLlzICj4tBerbDhHx/KhQRA/u2HvN8GZqpAVL9VUDGG
H9yv9qLhppCO7QlMyGSmN1HXcXb01GXWXTmHCAz6US0/zciDJvo=
=7mfR
-END PGP SIGNATURE-

Bug#1030096: #1030096 dask.distributed autopkgtest fail

2023-02-04 Thread Rebecca N. Palmer

I have an attempt to fix this in Salsa now (in my fork), but it hasn't 
had time to run the tests yet, so I don't know whether it works.


Note the above mention that if we lose dask.distributed then we lose 
Spyder, which makes this a bigger issue than I initially thought.

Bug#1016744: Test failure has become significantly rarer

2023-02-04 Thread Nicholas Guriev

severity 1016744 minor
retitle 1016744 vim-ultisnips: flaky autopkgtest with-neovim
stop

I applied a patch [1] increasing attempts of tests with regular expressions.
And now probability of failure is far less.

Although, the initial issue with a race of I/O in tmux(1) was not completely
fixed. I daresay it does not block our release of the package.

If you still encounter failure of the with-neovim autopkgtest as of package
version 3.2-2, please retry the test and it should pass. Sorry for 
inconvenience.

 [1]: 
https://salsa.debian.org/mymedia/vim-ultisnips/-/commit/50df4908a8452042d358cce94527c22b4d253872


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

Processed: xrdesktop: diff for NMU version 0.15.1-5.1

2023-02-04 Thread Debian Bug Tracking System

Processing control commands:

> tags 997389 + patch
Bug #997389 [src:xrdesktop] xrdesktop: FTBFS: dh_install: error: missing files, 
aborting
Added tag(s) patch.

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

Bug#997389: xrdesktop: diff for NMU version 0.15.1-5.1

2023-02-04 Thread Adrian Bunk

Control: tags 997389 + patch

Dear maintainer,

I've prepared an NMU for xrdesktop (versioned as 0.15.1-5.1) and 
uploaded it to DELAYED/1. Please feel free to tell me if I should
cancel it.

cu
Adrian
diff -Nru xrdesktop-0.15.1/debian/changelog xrdesktop-0.15.1/debian/changelog
--- xrdesktop-0.15.1/debian/changelog	2020-12-03 13:57:21.0 +0200
+++ xrdesktop-0.15.1/debian/changelog	2023-02-04 20:37:39.0 +0200
@@ -1,3 +1,10 @@
+xrdesktop (0.15.1-5.1) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * Fix Python FTBFS. (Closes: #997389)
+
+ -- Adrian Bunk   Sat, 04 Feb 2023 20:37:39 +0200
+
 xrdesktop (0.15.1-5) unstable; urgency=medium
 
   * Add Breaks+Replaces for libxrdesktop-0.13-0. (Closes: #971997)
diff -Nru xrdesktop-0.15.1/debian/xrdesktop.install xrdesktop-0.15.1/debian/xrdesktop.install
--- xrdesktop-0.15.1/debian/xrdesktop.install	2020-07-22 13:41:47.0 +0300
+++ xrdesktop-0.15.1/debian/xrdesktop.install	2023-02-04 20:37:35.0 +0200
@@ -1,4 +1,4 @@
-usr/lib/python*/site-packages/xrdesktop/config.py
+usr/lib/python*/dist-packages/xrdesktop/config.py
 usr/bin/xrd-settings
 usr/share/applications/org.xrdesktop.settings.desktop
 usr/share/xrdesktop/org.xrdesktop.settings.gresource

Processed: Test failure has become significantly rarer

2023-02-04 Thread Debian Bug Tracking System

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

> severity 1016744 minor
Bug #1016744 [src:vim-ultisnips] vim-ultisnips: autopkgtest failure on arm64, 
i386 and ppc64el
Severity set to 'minor' from 'serious'
> retitle 1016744 vim-ultisnips: flaky autopkgtest with-neovim
Bug #1016744 [src:vim-ultisnips] vim-ultisnips: autopkgtest failure on arm64, 
i386 and ppc64el
Changed Bug title to 'vim-ultisnips: flaky autopkgtest with-neovim' from 
'vim-ultisnips: autopkgtest failure on arm64, i386 and ppc64el'.
> stop
Stopping processing here.

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

Processed: Re: android-platform-frameworks-base: ftbfs with GCC-12

2023-02-04 Thread Debian Bug Tracking System

Processing control commands:

> tags -1 +help
Bug #1012890 [src:android-platform-frameworks-base] 
android-platform-frameworks-base: ftbfs with GCC-12
Added tag(s) help.

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

Bug#1012890: android-platform-frameworks-base: ftbfs with GCC-12

2023-02-04 Thread Roger Shimizu

control: tags -1 +help

+ Hans-Christoph

Dear Hans-Christoph,

It'd be appreciated if you can help this ticket.
I tried a few ways, but it still doesn't work.

On Sat, Feb 4, 2023 at 12:09 AM Roger Shimizu  wrote:
>
> control: reopen -1
>
> Yes, it ftbfs on sid now.
> And I tried latest upstream 13.0.0_r24, result is the same.
> Have to fix this issue before we can migrate to sid.

Error log is not originally reported, for latest error log please refer to:
- https://bugs.debian.org/1012890#17

I guess the issue is caused due to upstream using clang stdc++ lib,
but we're using gcc/g++ one.
Those two have slight differences.

Cheers,
Roger

Bug#1030539: d/copyright is wrong

2023-02-04 Thread Paul R. Tagliamonte

Package: php-dompdf-svg-lib
Severity: serious
User: paul...@debian.org
Usertags: ftp
X-Debbugs-CC: ftpmas...@ftp-master.debian.org
thanks

As noted in :

This package is LGPLv3+ (LGPL-3.0+) not LGPLv3 (LGPL-3.0). Please
update your copyright file in another upload before it migrates to
testing/stable.

-- 
:wq

Processed: Re: android-platform-frameworks-base: ftbfs with GCC-12

2023-02-04 Thread Debian Bug Tracking System

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

> tags 1012890 +experimental +ftbfs
Bug #1012890 [src:android-platform-frameworks-base] 
android-platform-frameworks-base: ftbfs with GCC-12
Added tag(s) experimental.
Bug #1012890 [src:android-platform-frameworks-base] 
android-platform-frameworks-base: ftbfs with GCC-12
Added tag(s) ftbfs.
>
End of message, stopping processing here.

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

Bug#1004629: marked as done (motion: FTBFS with ffmpeg 5.0)

2023-02-04 Thread Debian Bug Tracking System

Your message dated Sat, 04 Feb 2023 19:05:01 +
with message-id 
and subject line Bug#1004629: fixed in motion 4.5.1-1
has caused the Debian Bug report #1004629,
regarding motion: FTBFS with ffmpeg 5.0
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.)


-- 
1004629: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1004629
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: motion
Version: 4.3.2-1
Severity: important
X-Debbugs-Cc: sramac...@debian.org
Tags: sid bookworm ftbfs
Usertags: ffmpeg5.0

motion FTBFS with ffmpeg 5.0 (available in experimental):
| gcc -DHAVE_CONFIG_H -I. -I..  -Dsysconfdir=\"/etc/motion\" 
-DLOCALEDIR=\"/usr/share/locale\" -Wdate-time -D_FORTIFY_SOURCE=2 
-D_THREAD_SAFE  -I/usr/include/p11-kit-1 -I/usr/include/x86_64-linux-gnu 
-I/usr/include/mariadb/ -I/usr/include/mariadb/ -I/usr/include/postgresql  -g 
-O2 -ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat 
-Werror=format-security -c -o webu_text.o webu_text.c
| ffmpeg.c: In function ‘ffmpeg_get_oformat’:
| ffmpeg.c:343:67: error: assignment of member ‘video_codec’ in read-only object
|   343 | if (ffmpeg->oc->oformat) ffmpeg->oc->oformat->video_codec = 
MY_CODEC_ID_MPEG2VIDEO;
|   |   ^
| ffmpeg.c:365:67: error: assignment of member ‘video_codec’ in read-only object
|   365 | if (ffmpeg->oc->oformat) ffmpeg->oc->oformat->video_codec = 
MY_CODEC_ID_MSMPEG4V2;
|   |   ^
| ffmpeg.c:376:67: error: assignment of member ‘video_codec’ in read-only object
|   376 | if (ffmpeg->oc->oformat) ffmpeg->oc->oformat->video_codec = 
MY_CODEC_ID_FLV1;
|   |   ^
| ffmpeg.c:382:67: error: assignment of member ‘video_codec’ in read-only object
|   382 | if (ffmpeg->oc->oformat) ffmpeg->oc->oformat->video_codec = 
MY_CODEC_ID_FFV1;
|   |   ^
| ffmpeg.c:393:67: error: assignment of member ‘video_codec’ in read-only object
|   393 | if (ffmpeg->oc->oformat) ffmpeg->oc->oformat->video_codec = 
MY_CODEC_ID_H264;
|   |   ^
| ffmpeg.c:399:67: error: assignment of member ‘video_codec’ in read-only object
|   399 | if (ffmpeg->oc->oformat) ffmpeg->oc->oformat->video_codec = 
MY_CODEC_ID_H264;
|   |   ^
| ffmpeg.c:405:67: error: assignment of member ‘video_codec’ in read-only object
|   405 | if (ffmpeg->oc->oformat) ffmpeg->oc->oformat->video_codec = 
MY_CODEC_ID_HEVC;
|   |   ^
| ffmpeg.c: In function ‘ffmpeg_set_codec_preferred’:
| ffmpeg.c:722:27: warning: assignment discards ‘const’ qualifier from pointer 
target type [-Wdiscarded-qualifiers]
|   722 | ffmpeg->codec = 
avcodec_find_encoder_by_name(&ffmpeg->codec_name[codec_name_len+1]);
|   |   ^
| ffmpeg.c:724:54: error: assignment of member ‘video_codec’ in read-only object
|   724 | ffmpeg->oc->oformat->video_codec = 
ffmpeg->codec->id;
|   |  ^
| ffmpeg.c:733:23: warning: assignment discards ‘const’ qualifier from pointer 
target type [-Wdiscarded-qualifiers]
|   733 | ffmpeg->codec = 
avcodec_find_encoder(ffmpeg->oc->oformat->video_codec);
|   |   ^
| ffmpeg.c: In function ‘ffmpeg_flush_codec’:
| ffmpeg.c:1089:13: warning: ‘av_init_packet’ is deprecated 
[-Wdeprecated-declarations]
|  1089 | av_init_packet(&ffmpeg->pkt);
|   | ^~
| In file included from /usr/include/x86_64-linux-gnu/libavcodec/avcodec.h:45,
|  from netcam_rtsp.h:21,
|  from motion.h:66,
|  from ffmpeg.c:25:
| /usr/include/x86_64-linux-gnu/libavcodec/packet.h:506:6: note: declared here
|   506 | void av_init_packet(AVPacket *pkt);
|   |  ^~
| ffmpeg.c: In function ‘ffmpeg_put_frame’:
| ffmpeg.c:1132:5: warning: ‘av_init_packet’ is deprecated 
[-Wdeprecated-declarations]
|  1132 | av_init_packet(&ffmpeg->pkt);
|   | ^~
| In file included from /usr/include/x86_64-linux-gnu/libavcodec/avcodec.h:45,
|  from netcam_rtsp.h:21,
|  from motion.h:66,
|  from ffmpeg.c:25:

Bug#1030401: Many bugs about unsatisfiable build-dependencies

2023-02-04 Thread Lucas Nussbaum

Hi,

On 04/02/23 at 12:17 +0100, Stéphane Glondu wrote:
> Hello,
> 
> These unsatisfiable build-dependencies are temporary and will be solved by
> properly sequenced binNMUs or sourceful uploads that I am currently dealing
> with.
> 
> I do not see the value of such bug reports. Packages with unsatisfiable
> build-dependencies do not migrate to testing nor are picked up by buildd
> daemons (so no actual FTBFS). They add burden and look like noise to me.

I agree in general (and usually exclude such classes of failures when
filing bugs).

However, given our state in the release preparation, I see some value in
stating "there's something fishy about those packages".

I'm of course fine if you prefer to mass-close those bugs.

Lucas

Bug#1030423: marked as done (ibus-typing-booster: FTBFS: AssertionError: Lists differ: [('ca[224 chars]ource file.', '10'), ('show-lookup', 'Show lookup table', '0')] != [('ca[224 chars]ource file.',

2023-02-04 Thread Debian Bug Tracking System

Your message dated Sat, 04 Feb 2023 19:19:28 +
with message-id 
and subject line Bug#1030423: fixed in ibus-typing-booster 2.20.0-2
has caused the Debian Bug report #1030423,
regarding ibus-typing-booster: FTBFS: AssertionError: Lists differ: [('ca[224 
chars]ource file.', '10'), ('show-lookup', 'Show lookup table', '0')] != 
[('ca[224 chars]ource file.', '10')]
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.)


-- 
1030423: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1030423
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: ibus-typing-booster
Version: 2.20.0-1
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20230203 ftbfs-bookworm

Hi,

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


Relevant part (hopefully):
> make[4]: Entering directory '/<>/tests'
> PASS: test_itb_util.py
> PASS: test_0_gtk.py
> PASS: test_keyvals_to_keycodes.py
> FAIL: test_m17n_translit.py
> PASS: test_m17n_db_info.py
> PASS: test_compose_sequences.py
> PASS: test_emoji_unicode_version.py
> PASS: test_tabsqlitedb.py
> PASS: test_itb.py
> PASS: test_emoji_similar.py
> PASS: test_hunspell_suggest.py
> PASS: test_emoji_candidates.py
> ==
>ibus-typing-booster 2.20.0: tests/test-suite.log
> ==
> 
> # TOTAL: 12
> # PASS:  11
> # SKIP:  0
> # XFAIL: 0
> # FAIL:  1
> # XPASS: 0
> # ERROR: 0
> 
> .. contents:: :depth: 2
> 
> FAIL: test_m17n_translit.py
> ===
> 
> test_NoIME (test_m17n_translit.M17nTranslitTestCase.test_NoIME) ... ok
> test_bn_national_jatiya 
> (test_m17n_translit.M17nTranslitTestCase.test_bn_national_jatiya)
> Test my new bn-national-jatiya.mim input method ... ime "bn-national-jatiya" 
> ... skipped 'minput_open_im() failed'
> test_dummy (test_m17n_translit.M17nTranslitTestCase.test_dummy) ... ok
> test_get_variables_ath_phonetic 
> (test_m17n_translit.M17nTranslitTestCase.test_get_variables_ath_phonetic) ... 
> ime "ath-phonetic" ... ok
> test_get_variables_bn_national_jatiya 
> (test_m17n_translit.M17nTranslitTestCase.test_get_variables_bn_national_jatiya)
>  ... ime "bn-national-jatiya" ... skipped 'minput_open_im() failed'
> test_get_variables_bo_ewts 
> (test_m17n_translit.M17nTranslitTestCase.test_get_variables_bo_ewts) ... ime 
> "bo-ewts" ... ok
> test_get_variables_hi_itrans 
> (test_m17n_translit.M17nTranslitTestCase.test_get_variables_hi_itrans) ... 
> ime "hi-itrans" ... ok
> test_get_variables_ja_anthy 
> (test_m17n_translit.M17nTranslitTestCase.test_get_variables_ja_anthy) ... ime 
> "ja-anthy" ... ok
> test_get_variables_ml_swanalekha 
> (test_m17n_translit.M17nTranslitTestCase.test_get_variables_ml_swanalekha) 
> ... ime "ml-swanalekha" ... FAIL
> test_get_variables_mr_gamabhana 
> (test_m17n_translit.M17nTranslitTestCase.test_get_variables_mr_gamabhana) ... 
> ime "mr-gamabhana" ... skipped 'minput_open_im() failed'
> test_get_variables_oj_phonetic 
> (test_m17n_translit.M17nTranslitTestCase.test_get_variables_oj_phonetic) ... 
> ime "oj-phonetic" ... ok
> test_get_variables_sa_itrans 
> (test_m17n_translit.M17nTranslitTestCase.test_get_variables_sa_itrans) ... 
> ime "sa-itrans" ... ok
> test_get_variables_si_wijesekera 
> (test_m17n_translit.M17nTranslitTestCase.test_get_variables_si_wijesekera) 
> ... ime "si-wijesekera" ... ok
> test_get_variables_t_unicode 
> (test_m17n_translit.M17nTranslitTestCase.test_get_variables_t_unicode) ... 
> ime "t-unicode" ... ok
> test_get_variables_ta_lk_renganathan 
> (test_m17n_translit.M17nTranslitTestCase.test_get_variables_ta_lk_renganathan)
>  ... ime "ta-lk-renganathan" ... ok
> test_get_variables_th_kesmanee 
> (test_m17n_translit.M17nTranslitTestCase.test_get_variables_th_kesmanee) ... 
> ime "th-kesmanee" ... ok
> test_get_variables_th_pattachote 
> (test_m17n_translit.M17nTranslitTestCase.test_get_variables_th_pattachote) 
> ... ime "th-pattachote" ... ok
> test_get_variables_th_tis820 
> (test_m17n_translit.M17nTranslitTestCase.test_get_variables_th_tis820) ... 
> ime "th-tis820" ... ok
> test_get_variables_vi_han 
> (test_m17n_translit.M17nTranslitTestCase.test_get_variables_vi_han) ... ime 
> "vi-han" ... ok
> test_get_variables_vi_nomtelex 
> (test_m17n_translit.M17nTranslitTestCase.test_get_variables_vi_nomtelex) ... 
> ime "vi-nomtelex" ... ok
> test_get_variables_vi_nomvni 
> (test_m17n_translit.M17nTranslitTestCase.test_get_variables_vi_nomvni) ... 
> ime "vi-nomvni" ... ok
> test_get_variables_vi_tcvn 
>

Bug#1030485: marked as done (uima-as: FTBFS: [ERROR] Failed to execute goal on project uima-as: Could not resolve dependencies for project org.apache.uima:uima-as:pom:2.3.1: Cannot access eclipsePlugi

2023-02-04 Thread Debian Bug Tracking System

Your message dated Sat, 04 Feb 2023 19:21:10 +
with message-id 
and subject line Bug#1030485: fixed in uima-as 2.3.1-10
has caused the Debian Bug report #1030485,
regarding uima-as: FTBFS: [ERROR] Failed to execute goal on project uima-as: 
Could not resolve dependencies for project org.apache.uima:uima-as:pom:2.3.1: 
Cannot access eclipsePlugins (http://repo1.maven.org/eclipse) in offline mode 
and the artifact log4j:log4j:jar:1.2.x has not been downloaded from it before. 
-> [Help 1]
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.)


-- 
1030485: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1030485
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: uima-as
Version: 2.3.1-9
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20230203 ftbfs-bookworm

Hi,

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


Relevant part (hopefully):
> make[1]: Entering directory '/<>'
> dh_auto_build -Duima-as
>   cd uima-as && /usr/lib/jvm/default-java/bin/java -noverify -cp 
> /usr/share/maven/boot/plexus-classworlds-2.x.jar 
> -Dmaven.home=/usr/share/maven 
> -Dmaven.multiModuleProjectDirectory=/<> 
> -Dclassworlds.conf=/etc/maven/m2-debian.conf 
> -Dproperties.file.manual=/<>/debian/maven.properties 
> org.codehaus.plexus.classworlds.launcher.Launcher 
> -s/etc/maven/settings-debian.xml -Ddebian.dir=/<>/debian 
> -Dmaven.repo.local=/<>/debian/maven-repo --batch-mode package 
> javadoc:jar javadoc:aggregate -DskipTests -Dnotimestamp=true -Dlocale=en_US
> OpenJDK 64-Bit Server VM warning: Options -Xverify:none and -noverify were 
> deprecated in JDK 13 and will likely be removed in a future release.
> [0m[0m[INFO] Scanning for projects...
> [INFO] 
> 
> [INFO] Reactor Build Order:
> [INFO] 
> [INFO] UIMA-AS: uima-as-parent
> [pom]
> [INFO] UIMA-AS: uimaj-as-core 
> [jar]
> [INFO] UIMA-AS: uimaj-as-jms  
> [jar]
> [INFO] UIMA-AS: uimaj-as-activemq 
> [jar]
> [INFO] UIMA AS: uimaj-as-osgi-runtime 
> [jar]
> [INFO] UIMA-AS Aggregate: aggregate-uima-as-eclipse-plugins   
> [pom]
> [INFO] UIMA-AS Aggregate: aggregate-uima-as   
> [pom]
> [INFO] UIMA-AS: uima-as   
> [pom]
> [WARNING] The artifact org.apache.maven.plugins:maven-clean-plugin:jar:2.5 
> has been relocated to org.apache.maven.plugins:maven-clean-plugin:jar:3.2.0
> [WARNING] The artifact org.apache.maven.plugins:maven-install-plugin:jar:2.4 
> has been relocated to org.apache.maven.plugins:maven-install-plugin:jar:3.1.0
> [WARNING] The artifact org.apache.maven.plugins:maven-deploy-plugin:jar:2.7 
> has been relocated to org.apache.maven.plugins:maven-deploy-plugin:jar:3.0.0
> [WARNING] The POM for org.apache.maven.plugins:maven-site-plugin:jar:3.3 is 
> missing, no dependency information available
> [WARNING] Failed to retrieve plugin descriptor for 
> org.apache.maven.plugins:maven-site-plugin:3.3: Plugin 
> org.apache.maven.plugins:maven-site-plugin:3.3 or one of its dependencies 
> could not be resolved: Cannot access central 
> (https://repo.maven.apache.org/maven2) in offline mode and the artifact 
> org.apache.maven.plugins:maven-site-plugin:jar:3.3 has not been downloaded 
> from it before.
> [WARNING] The artifact org.apache.maven.plugins:maven-antrun-plugin:jar:1.3 
> has been relocated to org.apache.maven.plugins:maven-antrun-plugin:jar:3.1.0
> [WARNING] The POM for 
> org.apache.maven.plugins:maven-assembly-plugin:jar:2.2-beta-5 is missing, no 
> dependency information available
> [WARNING] Failed to retrieve plugin descriptor for 
> org.apache.maven.plugins:maven-assembly-plugin:2.2-beta-5: Plugin 
> org.apache.maven.plugins:maven-assembly-plugin:2.2-beta-5 or one of its 
> dependencies could not be resolved: Cannot access central 
> (https://repo.maven.apache.org/maven2) in offline mode and the artifact 
> org.apache.maven.plugins:maven-assembly-plugin:jar:2.2-beta-5 has not been 
> downloaded from it before.
> [WARNING] The artifact 
> org.apache.maven.plugins:maven-dependency-plugin:jar:2.8 has been relocated 
> to org.apache.maven.plugins:maven-dependency-plugin:jar:3.5.0
> [WARNING] The POM for org.apache.maven.plugins:maven-release-plugin:jar:2.5.3 
> is missing, no depen

Bug#1030541: gap-browse: autopkgtest failure

2023-02-04 Thread Adrian Bunk

Source: gap-browse
Version: 1.8.18-1
Severity: serious
X-Debbugs-Cc: Bill Allombert 

https://ci.debian.net/data/autopkgtest/testing/amd64/g/gap-browse/31044433/log.gz

...
autopkgtest [15:59:11]: test test: [---

true
Architecture: x86_64-pc-linux-gnu-default64-kv8

testing: ./tst/test.tst
[34m> Diff in ./tst/test.tst:78[0m
[34m# Input is:[0m
NCurses.Alert( "Hello world!", 1000 );
[0m[2K[34m# Expected output:[0m
[30m[42mfail
[0m[2K[34m# But found:[0m
[37m[41m#I  NCurses.Alert: cannot switch to visual mode because of TERM = "d\
umb"
fail
...
autopkgtest [15:59:51]:  summary
test FAIL non-zero exit status 1

Processed: Fwd pending

2023-02-04 Thread Debian Bug Tracking System

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

> forwarded 1030539 https://github.com/dompdf/php-svg-lib/issues/104
Bug #1030539 [php-dompdf-svg-lib] d/copyright is wrong
Set Bug forwarded-to-address to 
'https://github.com/dompdf/php-svg-lib/issues/104'.
> tags 1030539 + pending
Bug #1030539 [php-dompdf-svg-lib] d/copyright is wrong
Added tag(s) pending.
> stop
Stopping processing here.

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

Bug#1030429: libervia-backend: FTBFS: InvalidVersion: Invalid version: '0.9.0-hg3993'

2023-02-04 Thread Martin

Control: retitle -1 libervia-backend: FTBFS: InvalidVersion: Invalid version: 
'0.9.0-hg3993'
Control: user debian-pyt...@lists.debian.org
Control: usertags -1 python3.11

The cause of the error is not the failing unit test (which is ignored as
"known broken"), but that Python 3.11 is more strict about version
numbers than Python 3.10. The tilde '~' is not valid in PEP 440, but
somehow replaced with a dash '-', which is invalid, too:


Traceback (most recent call last):
  File "/<>/setup.py", line 97, in 
setup(
  File "/usr/lib/python3/dist-packages/setuptools/__init__.py", line 108, in 
setup
return distutils.core.setup(**attrs)
   ^
  File "/usr/lib/python3/dist-packages/setuptools/_distutils/core.py", line 
185, in setup
return run_commands(dist)
   ^^
  File "/usr/lib/python3/dist-packages/setuptools/_distutils/core.py", line 
201, in run_commands
dist.run_commands()
  File "/usr/lib/python3/dist-packages/setuptools/_distutils/dist.py", line 
969, in run_commands
self.run_command(cmd)
  File "/usr/lib/python3/dist-packages/setuptools/dist.py", line 1213, in 
run_command
super().run_command(command)
  File "/usr/lib/python3/dist-packages/setuptools/_distutils/dist.py", line 
988, in run_command
cmd_obj.run()
  File "/usr/lib/python3/dist-packages/setuptools/command/install.py", line 68, 
in run
return orig.install.run(self)
   ^^
  File 
"/usr/lib/python3/dist-packages/setuptools/_distutils/command/install.py", line 
709, in run
self.run_command(cmd_name)
  File "/usr/lib/python3/dist-packages/setuptools/_distutils/cmd.py", line 318, 
in run_command
self.distribution.run_command(command)
  File "/usr/lib/python3/dist-packages/setuptools/dist.py", line 1213, in 
run_command
super().run_command(command)
  File "/usr/lib/python3/dist-packages/setuptools/_distutils/dist.py", line 
987, in run_command
cmd_obj.ensure_finalized()
  File "/usr/lib/python3/dist-packages/setuptools/_distutils/cmd.py", line 111, 
in ensure_finalized
self.finalize_options()
  File "/usr/lib/python3/dist-packages/setuptools/command/install_egg_info.py", 
line 31, in finalize_options
ei_cmd = self.get_finalized_command("egg_info")
 ^^
  File "/usr/lib/python3/dist-packages/setuptools/_distutils/cmd.py", line 305, 
in get_finalized_command
cmd_obj.ensure_finalized()
  File "/usr/lib/python3/dist-packages/setuptools/_distutils/cmd.py", line 111, 
in ensure_finalized
self.finalize_options()
  File "/usr/lib/python3/dist-packages/setuptools/command/egg_info.py", line 
219, in finalize_options
parsed_version = parse_version(self.egg_version)
 ^^^
  File 
"/usr/lib/python3/dist-packages/pkg_resources/_vendor/packaging/version.py", 
line 266, in __init__
raise InvalidVersion(f"Invalid version: '{version}'")
pkg_resources.extern.packaging.version.InvalidVersion: Invalid version: 
'0.9.0-hg3993'
E: pybuild pybuild:388: install: plugin distutils failed with: exit code=1: 
/usr/bin/python3 setup.py install --root '/<>/debian/tmp' 
--install-lib=/usr/share/libervia/ --install-scripts=/launchers/ --verbose
dh_auto_install: error: pybuild --install -i python{version} -p 3.11 --dest-dir 
/<>/libervia-backend-0.9.0\~hg3993/debian/tmp returned exit code 13
make: *** [debian/rules:18: binary] Error 25
dpkg-buildpackage: error: debian/rules binary subprocess returned exit status 2

Processed (with 2 errors): Re: Bug#1030429: libervia-backend: FTBFS: InvalidVersion: Invalid version: '0.9.0-hg3993'

2023-02-04 Thread Debian Bug Tracking System

Processing control commands:

> retitle -1 libervia-backend: FTBFS: InvalidVersion: Invalid version: 
> '0.9.0-hg3993'
Bug #1030429 [src:libervia-backend] libervia-backend: FTBFS: ImportError: 
Failed to import test module: sat.test.test_plugin_xep_0334
Changed Bug title to 'libervia-backend: FTBFS: InvalidVersion: Invalid version: 
'0.9.0-hg3993'' from 'libervia-backend: FTBFS: ImportError: Failed to import 
test module: sat.test.test_plugin_xep_0334'.
> user debian-pyt...@lists.debian.org
Unknown command or malformed arguments to command.

> usertags -1 python3.11
Unknown command or malformed arguments to command.


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

Bug#1030543: rust-dockerfile: autopkgtest failure

2023-02-04 Thread Adrian Bunk

Source: rust-dockerfile
Version: 0.2.1-1
Severity: serious

https://ci.debian.net/data/autopkgtest/testing/amd64/r/rust-dockerfile/30979620/log.gz

...
autopkgtest [03:52:12]: test rust-dockerfile:@: 
/usr/share/cargo/bin/cargo-auto-test dockerfile 0.2.1 --all-targets 
--all-features
autopkgtest [03:52:12]: test rust-dockerfile:@: [---
debian cargo wrapper: options, profiles, parallel: ['parallel=64'] [] ['-j64']
debian cargo wrapper: rust_type, gnu_type: x86_64-unknown-linux-gnu, 
x86_64-linux-gnu
debian cargo wrapper: linking /usr/share/cargo/registry/* into 
/tmp/tmp.CZI90S5IlT/registry/
debian cargo wrapper: options, profiles, parallel: ['parallel=64'] [] ['-j64']
debian cargo wrapper: rust_type, gnu_type: x86_64-unknown-linux-gnu, 
x86_64-linux-gnu
debian cargo wrapper: running subprocess (['env', 'RUST_BACKTRACE=1', 
'/usr/bin/cargo', '-Zavoid-dev-deps', 'test', '--verbose', '--verbose', '-j64', 
'--target', 'x86_64-unknown-linux-gnu', '--all-targets', '--all-features'],) {}
   Compiling dockerfile v0.2.1 (/usr/share/cargo/registry/dockerfile-0.2.1)
 Running `CARGO=/usr/bin/cargo CARGO_CRATE_NAME=dockerfile 
CARGO_MANIFEST_DIR=/usr/share/cargo/registry/dockerfile-0.2.1 
CARGO_PKG_AUTHORS='Anthony Dodd ' 
CARGO_PKG_DESCRIPTION='A Rust library for dynamically generating Dockerfiles.' 
CARGO_PKG_HOMEPAGE='https://github.com/thedodd/dockerfile' 
CARGO_PKG_LICENSE=Apache-2.0 CARGO_PKG_LICENSE_FILE='' 
CARGO_PKG_NAME=dockerfile 
CARGO_PKG_REPOSITORY='https://github.com/thedodd/dockerfile' 
CARGO_PKG_RUST_VERSION='' CARGO_PKG_VERSION=0.2.1 CARGO_PKG_VERSION_MAJOR=0 
CARGO_PKG_VERSION_MINOR=2 CARGO_PKG_VERSION_PATCH=1 CARGO_PKG_VERSION_PRE='' 
CARGO_PRIMARY_PACKAGE=1 
LD_LIBRARY_PATH='/tmp/tmp.CZI90S5IlT/target/debug/deps:/usr/lib' rustc 
--crate-name dockerfile --edition=2018 src/lib.rs --error-format=json 
--json=diagnostic-rendered-ansi,artifacts,future-incompat --emit=dep-info,link 
-C embed-bitcode=no -C debuginfo=2 --test --cfg 'feature="docinclude"' -C 
metadata=3260d957e4ef2b10 -C extra-filename=-3260d957e4ef2b10 --out-dir 
/tmp/tmp.CZI90S5IlT/target/x86_64-unknown-linux-gnu/debug/deps --target 
x86_64-unknown-linux-gnu -C 
incremental=/tmp/tmp.CZI90S5IlT/target/x86_64-unknown-linux-gnu/debug/incremental
 -L dependency=/tmp/tmp.CZI90S5IlT/target/x86_64-unknown-linux-gnu/debug/deps 
-L dependency=/tmp/tmp.CZI90S5IlT/target/debug/deps -C debuginfo=2 --cap-lints 
warn -C linker=x86_64-linux-gnu-gcc -C link-arg=-Wl,-z,relro 
--remap-path-prefix 
/usr/share/cargo/registry/dockerfile-0.2.1=/usr/share/cargo/registry/dockerfile-0.2.1
 --remap-path-prefix /tmp/tmp.CZI90S5IlT/registry=/usr/share/cargo/registry`
error[E0557]: feature has been removed
 --> src/lib.rs:1:43
  |
1 | #![cfg_attr(feature="docinclude", feature(external_doc))]
  |    feature has been 
removed
  |
  = note: use #[doc = include_str!("filename")] instead, which handles macro 
invocations

warning: unknown `doc` attribute `include`
 --> src/lib.rs:2:39
  |
2 | #![cfg_attr(feature="docinclude", doc(include="../README.md"))]
  |   ^^- help: use 
`doc = include_str!` instead: `#![doc = include_str!("../README.md")]`
  |
  = note: `#[warn(invalid_doc_attributes)]` on by default
  = warning: this was previously accepted by the compiler but is being phased 
out; it will become a hard error in a future release!
  = note: for more information, see issue #82730 


For more information about this error, try `rustc --explain E0557`.
warning: `dockerfile` (lib test) generated 1 warning
error: could not compile `dockerfile` due to previous error; 1 warning emitted

Caused by:
  process didn't exit successfully: `CARGO=/usr/bin/cargo 
CARGO_CRATE_NAME=dockerfile 
CARGO_MANIFEST_DIR=/usr/share/cargo/registry/dockerfile-0.2.1 
CARGO_PKG_AUTHORS='Anthony Dodd ' 
CARGO_PKG_DESCRIPTION='A Rust library for dynamically generating Dockerfiles.' 
CARGO_PKG_HOMEPAGE='https://github.com/thedodd/dockerfile' 
CARGO_PKG_LICENSE=Apache-2.0 CARGO_PKG_LICENSE_FILE='' 
CARGO_PKG_NAME=dockerfile 
CARGO_PKG_REPOSITORY='https://github.com/thedodd/dockerfile' 
CARGO_PKG_RUST_VERSION='' CARGO_PKG_VERSION=0.2.1 CARGO_PKG_VERSION_MAJOR=0 
CARGO_PKG_VERSION_MINOR=2 CARGO_PKG_VERSION_PATCH=1 CARGO_PKG_VERSION_PRE='' 
CARGO_PRIMARY_PACKAGE=1 
LD_LIBRARY_PATH='/tmp/tmp.CZI90S5IlT/target/debug/deps:/usr/lib' rustc 
--crate-name dockerfile --edition=2018 src/lib.rs --error-format=json 
--json=diagnostic-rendered-ansi,artifacts,future-incompat --emit=dep-info,link 
-C embed-bitcode=no -C debuginfo=2 --test --cfg 'feature="docinclude"' -C 
metadata=3260d957e4ef2b10 -C extra-filename=-3260d957e4ef2b10 --out-dir 
/tmp/tmp.CZI90S5IlT/target/x86_64-unknown-linux-gnu/debug/deps --target 
x86_64-unknown-linux-gnu -C 
incremental=/tmp/tmp.CZI90S5IlT/target/x86_64-unknown-linux-gnu/debug/incremental
 -L dependency=/t

Bug#1030544: rust-document-features: autopkgtest failure

2023-02-04 Thread Adrian Bunk

Source: rust-document-features
Version: 0.2.7-1
Severity: serious

https://ci.debian.net/data/autopkgtest/testing/amd64/r/rust-document-features/30989599/log.gz

...
error: The feature `default` must be enabled to ensure forward compatibility 
with future version of this crate
   --> lib.rs:153:1
|
153 | / compile_error!(
154 | | "The feature `default` must be enabled to ensure \
155 | | forward compatibility with future version of this crate"
156 | | );
| |_^

error: could not compile `document-features` due to previous error

Caused by:
  process didn't exit successfully: `CARGO=/usr/bin/cargo 
CARGO_CRATE_NAME=document_features 
CARGO_MANIFEST_DIR=/usr/share/cargo/registry/document-features-0.2.7 
CARGO_PKG_AUTHORS='Slint Developers ' 
CARGO_PKG_DESCRIPTION='Extract documentation for the feature flags from 
comments in Cargo.toml' CARGO_PKG_HOMEPAGE='https://slint-ui.com' 
CARGO_PKG_LICENSE='MIT OR Apache-2.0' CARGO_PKG_LICENSE_FILE='' 
CARGO_PKG_NAME=document-features 
CARGO_PKG_REPOSITORY='https://github.com/slint-ui/document-features' 
CARGO_PKG_RUST_VERSION='' CARGO_PKG_VERSION=0.2.7 CARGO_PKG_VERSION_MAJOR=0 
CARGO_PKG_VERSION_MINOR=2 CARGO_PKG_VERSION_PATCH=7 CARGO_PKG_VERSION_PRE='' 
CARGO_PRIMARY_PACKAGE=1 
LD_LIBRARY_PATH='/tmp/tmp.9SugApoBQC/target/debug/deps:/usr/lib' rustc 
--crate-name document_features --edition=2018 lib.rs --error-format=json 
--json=diagnostic-rendered-ansi,artifacts,future-incompat --crate-type 
proc-macro --emit=dep-info,link -C prefer-dynamic -C embed-bitcode=no -C 
debuginfo=2 -C metadata=9050631d527b1f34 -C extra-filename=-9050631d527b1f34 
--out-dir /tmp/tmp.9SugApoBQC/target/debug/deps -C 
incremental=/tmp/tmp.9SugApoBQC/target/debug/incremental -L 
dependency=/tmp/tmp.9SugApoBQC/target/debug/deps --extern 
litrs=/tmp/tmp.9SugApoBQC/target/debug/deps/liblitrs-a03c4a135dff2839.rlib 
--extern proc_macro` (exit status: 1)
warning: build failed, waiting for other jobs to finish...
error: could not compile `document-features` due to previous error

Caused by:
  process didn't exit successfully: `CARGO=/usr/bin/cargo 
CARGO_CRATE_NAME=document_features 
CARGO_MANIFEST_DIR=/usr/share/cargo/registry/document-features-0.2.7 
CARGO_PKG_AUTHORS='Slint Developers ' 
CARGO_PKG_DESCRIPTION='Extract documentation for the feature flags from 
comments in Cargo.toml' CARGO_PKG_HOMEPAGE='https://slint-ui.com' 
CARGO_PKG_LICENSE='MIT OR Apache-2.0' CARGO_PKG_LICENSE_FILE='' 
CARGO_PKG_NAME=document-features 
CARGO_PKG_REPOSITORY='https://github.com/slint-ui/document-features' 
CARGO_PKG_RUST_VERSION='' CARGO_PKG_VERSION=0.2.7 CARGO_PKG_VERSION_MAJOR=0 
CARGO_PKG_VERSION_MINOR=2 CARGO_PKG_VERSION_PATCH=7 CARGO_PKG_VERSION_PRE='' 
CARGO_PRIMARY_PACKAGE=1 
LD_LIBRARY_PATH='/tmp/tmp.9SugApoBQC/target/debug/deps:/usr/lib' rustc 
--crate-name document_features --edition=2018 lib.rs --error-format=json 
--json=diagnostic-rendered-ansi,artifacts,future-incompat --emit=dep-info,link 
-C prefer-dynamic -C embed-bitcode=no -C debuginfo=2 --test -C 
metadata=6b6f5d3fcfc82b5d -C extra-filename=-6b6f5d3fcfc82b5d --out-dir 
/tmp/tmp.9SugApoBQC/target/debug/deps -C 
incremental=/tmp/tmp.9SugApoBQC/target/debug/incremental -L 
dependency=/tmp/tmp.9SugApoBQC/target/debug/deps --extern 
litrs=/tmp/tmp.9SugApoBQC/target/debug/deps/liblitrs-a03c4a135dff2839.rlib 
--extern proc_macro` (exit status: 1)
autopkgtest [09:14:57]: test librust-document-features-dev:: 
---]
autopkgtest [09:14:58]: test librust-document-features-dev::  - - - - - - - - - 
- results - - - - - - - - - -
librust-document-features-dev: FAIL non-zero exit status 101
autopkgtest [09:14:58]:  summary
rust-document-features:@ PASS
librust-document-features-dev:default PASS
librust-document-features-dev:self-test FAIL non-zero exit status 101
librust-document-features-dev: FAIL non-zero exit status 101

Bug#1030545: qemu: qemu-img and qemu-system-s390x hang on s390x

2023-02-04 Thread Hilko Bengen

Package: src:qemu
Version: 1:7.2+dfsg-2
Severity: grave
X-Debbugs-Cc: none, Hilko Bengen 

Dear Maintainer,

While investigating recent s390x build failures of libguestfs, I noticed
that variants of 

qemu-img create -f qcow2 -o preallocation=metadata blank-disk-1s.qcow2 512

would hang in what appears a tight loop (100% CPU).

Calling strace on those hanging processes or sending them TSTP and CONT
signals causes them to continue.

Later in the build process, libguestfs-test-tool runs qemu-system-s390x
a few times. Those processes also hang and they can also be "cured" by
sending them TSTP and CONT signals.

Cheers,
-Hilko

Bug#1030545: qemu: qemu-img and qemu-system-s390x hang on s390x

2023-02-04 Thread Michael Tokarev


04.02.2023 23:19, Hilko Bengen wrote:

Package: src:qemu
Version: 1:7.2+dfsg-2

..

 qemu-img create -f qcow2 -o preallocation=metadata blank-disk-1s.qcow2 512

would hang in what appears a tight loop (100% CPU).


Does 7.2+dfsg-1 work?

I don't have s390x environment so have no way to deal with this one.

Thanks,

/mjt

Bug#1020576: please update sage for pari 2.15.0 and gap 4.12.0

2023-02-04 Thread Adrian Bunk

On Sat, Dec 24, 2022 at 09:13:35AM +, Tobias Hansen wrote:
>...
> Upstream has a (maybe unrelated?) problem with higher setuptools versions 
> described here:
> https://trac.sagemath.org/ticket/34442
> 
> Unfortunately I don't have much time to work on this. If someone can come up 
> with a patch, that would be highly appreciated.

The setuptools issue might have been fixed by #1025216.

I tried to reproduce this, but ran into several unrelated issues.

Patches I applied locally on top of what is already in git:
https://github.com/sagemath/sage/commit/de38bac21e276c6dba95b8b33f7457a0ac56bdeb
https://github.com/sagemath/sagetrac-mirror/commit/6f3b4556db746e6354d55d42eba5925be19a6cad

/usr/include/giac/plot.h needs a "typedef unsigned char uchar;" somewhere.

build/cythonized/sage/rings/polynomial/multi_polynomial_libsingular.cpp:36042:120:
 error: ‘pTakeOutComp1’ was not declared in this scope; did you mean 
‘pTakeOutComp’?

> Best wishes,
> 
> Tobias

cu
Adrian

1 2 >

1 - 100 of 168 matches

Mail list logo