Bug#1030697: libjs-bootstrap5: not co-installable with libjs-bootstrap4

[Damyan Ivanov]

Package: libjs-bootstrap5
Version: 5.2.3+dfsg-7
Followup-For: Bug #1030697

Control: found -1 5.2.3+dfsg-7

Still can't install the package with libjs-bootstrap4 installed:

 Preparing to unpack .../libjs-bootstrap5_5.2.3+dfsg-7_all.deb ...
 Unpacking libjs-bootstrap5 (5.2.3+dfsg-7) ...
 dpkg: error processing archive 
/var/cache/apt/archives/libjs-bootstrap5_5.2.3+dfsg-7_all.deb (--unpack):
  trying to overwrite '/usr/share/nodejs/bootstrap/package.json', which is also 
in package libjs-bootstrap4 4.6.1+dfsg1-4
 Errors were encountered while processing:
  /var/cache/apt/archives/libjs-bootstrap5_5.2.3+dfsg-7_all.deb


-- Damyan

-- System Information:
Debian Release: bookworm/sid
  APT prefers unstable-debug
  APT policy: (500, 'unstable-debug'), (500, 'unstable'), (500, 'stable')
Architecture: amd64 (x86_64)

Kernel: Linux 6.1.0-4-amd64 (SMP w/24 CPU threads; PREEMPT)
Kernel taint flags: TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE
Locale: LANG=bg_BG.UTF-8, LC_CTYPE=bg_BG.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages libjs-bootstrap5 depends on:
ii  libjs-popper.js  1.16.1+ds-6

libjs-bootstrap5 recommends no packages.

Versions of packages libjs-bootstrap5 suggests:
ii  bootstrap-icons   1.10.3+dfsg-1
ii  libjs-bootstrap5-doc  5.2.3+dfsg-7

Bug#1031487: devscripts: FTBFS: AssertionError: black found code that needs reformatting:

[Lucas Nussbaum]

Source: devscripts
Version: 2.23.1
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20230216 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 '/<>/scripts'
> perl -I ../lib -c bts; \
> 
> perl -I ../lib -c build-rdeps; \
> 
> perl -I ../lib -c chdist; \
> 
> perl -I ../lib -c checkbashisms; \
> 
> perl -I ../lib -c cvs-debuild; \
> 
> perl -I ../lib -c dd-list; \
> 
> perl -I ../lib -c deb-why-removed; \
> 
> perl -I ../lib -c debc; \
> 
> cvs-debuild syntax OK
> perl -I ../lib -c debchange; \
> 
> build-rdeps syntax OK
> perl -I ../lib -c debcheckout; \
> 
> debc syntax OK
> perl -I ../lib -c debcommit; \
> 
> chdist syntax OK
> perl -I ../lib -c debdiff; \
> 
> deb-why-removed syntax OK
> perl -I ../lib -c debi; \
> 
> debcommit syntax OK
> perl -I ../lib -c debpkg; \
> 
> debchange syntax OK
> perl -I ../lib -c debrebuild; \
> 
> debpkg syntax OK
> perl -I ../lib -c debsnap; \
> 
> checkbashisms syntax OK
> perl -I ../lib -c debuild; \
> 
> debcheckout syntax OK
> perl -I ../lib -c dep3changelog; \
> 
> debdiff syntax OK
> debi syntax OK
> perl -I ../lib -c desktop2menu; \
> 
> perl -I ../lib -c dget; \
> 
> bts syntax OK
> perl -I ../lib -c dpkg-depcheck; \
> 
> dd-list syntax OK
> perl -I ../lib -c dscverify; \
> 
> dep3changelog syntax OK
> perl -I ../lib -c git-deborig; \
> 
> debsnap syntax OK
> perl -I ../lib -c grep-excuses; \
> 
> debuild syntax OK
> perl -I ../lib -c hardening-check; \
> 
> desktop2menu syntax OK
> perl -I ../lib -c mass-bug; \
> 
> grep-excuses syntax OK
> perl -I ../lib -c mk-build-deps; \
> 
> dget syntax OK
> dpkg-depcheck syntax OK
> perl -I ../lib -c mk-origtargz; \
> 
> mass-bug syntax OK
> perl -I ../lib -c namecheck; \
> 
> perl -I ../lib -c origtargz; \
> 
> dscverify syntax OK
> perl -I ../lib -c plotchangelog; \
> 
> hardening-check syntax OK
> perl -I ../lib -c rc-alert; \
> 
> git-deborig syntax OK
> perl -I ../lib -c rmadison; \
> 
> debrebuild syntax OK
> namecheck syntax OK
> perl -I ../lib -c salsa; \
> 
> perl -I ../lib -c svnpath; \
> 
> plotchangelog syntax OK
> perl -I ../lib -c tagpending; \
> 
> rmadison syntax OK
> perl -I ../lib -c transition-check; \
> 
> svnpath syntax OK
> perl -I ../lib -c uscan; \
> 
> origtargz syntax OK
> perl -I ../lib -c who-permits-upload; \
> 
> mk-build-deps syntax OK
> bash -n annotate-output
> bash -n archpath
> transition-check syntax OK
> bash -n cowpoke
> bash -n cvs-debi
> bash -n cvs-debrelease
> bash -n dcmd
> bash -n deb-reversion
> bash -n debclean
> bash -n debrelease
> bash -n debrepro
> bash -n debrsign
> bash -n debsign
> bash -n diff2patches
> bash -n dpkg-genbuilddeps
> bash -n dscextract
> bash -n edit-patch
> bash -n getbuildlog
> bash -n list-unreleased
> bash -n ltnu
> rc-alert syntax OK
> bash -n manpage-alert
> bash -n mergechanges
> tagpending syntax OK
> bash -n nmudiff
> bash -n pts-subscribe
> bash -n run_bisect
> bash -n run_bisect_qemu
> bash -n uupdate
> bash -n what-patch
> bash -n who-uploads
> bash -n whodepends
> bash -n wnpp-alert
> bash -n wnpp-check
> mk-origtargz syntax OK
> who-permits-upload syntax OK
> py3versions: no X-Python3-Version in control file, using supported versions
> python3.11 setup.py test
> salsa syntax OK
> uscan syntax OK
> 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 devscripts.egg-info
> writing devscripts.egg-info/PKG-INFO
> writing dependency_links to devscripts.egg-info/dependency_links.txt
> writing top-level names to devscripts.egg-info/top_level.txt
> writing manifest file 'devscripts.egg-info/SOURCES.txt'
> reading manifest file 'devscripts.egg-info/SOURCES.txt'
> writing manifest file 'devscripts.egg-info/SOURCES.txt'
> running build_ext
> test_black (devscripts.test.test_black.BlackTestCase.test_black)
> Test: Run black code formatter on Python source code. ... Running following 
> command:
> black --check --diff debbisect debdiff-apply debootsnap deb-janitor 
> reproducible-check sadt suspicious-source wrap-and-sort devscripts setup.py
> FAIL
> test_flake8 (devscripts.test.test_flake8.Flake8TestCase.test_flake8)
> Test: Run flake8 on Python sou

Bug#1031452: *: FTBFS: java.util.MissingResourceException: Can't find bundle for base name com.google.javascript.rhino.head.resources.Messages, locale en

[Yadd]

Control: reassign -1 closure-compiler

On 2/17/23 10:49, Lucas Nussbaum wrote:

java.util.MissingResourceException: Can't find bundle for base name 
com.google.javascript.rhino.head.resources.Messages, locale en
at 
java.base/java.util.ResourceBundle.throwMissingResourceException(ResourceBundle.java:2045)
at 
java.base/java.util.ResourceBundle.getBundleImpl(ResourceBundle.java:1683)
at 
java.base/java.util.ResourceBundle.getBundleImpl(ResourceBundle.java:1586)
at 
java.base/java.util.ResourceBundle.getBundleImpl(ResourceBundle.java:1549)
at java.base/java.util.ResourceBundle.getBundle(ResourceBundle.java:932)
at 
com.google.javascript.rhino.head.ScriptRuntime$DefaultMessageProvider.getMessage(ScriptRuntime.java:4521)
at 
com.google.javascript.rhino.head.ScriptRuntime.getMessage(ScriptRuntime.java:4501)
at 
com.google.javascript.rhino.head.ScriptRuntime.getMessage0(ScriptRuntime.java:4446)
at 
com.google.javascript.jscomp.RhinoErrorReporter.(RhinoErrorReporter.java:84)
at 
com.google.javascript.jscomp.RhinoErrorReporter.(RhinoErrorReporter.java:32)
at 
com.google.javascript.jscomp.RhinoErrorReporter$OldRhinoErrorReporter.(RhinoErrorReporter.java:162)
at 
com.google.javascript.jscomp.RhinoErrorReporter$OldRhinoErrorReporter.(RhinoErrorReporter.java:158)
at 
com.google.javascript.jscomp.RhinoErrorReporter.forOldRhino(RhinoErrorReporter.java:119)
at com.google.javascript.jscomp.Compiler.(Compiler.java:176)
at 
com.google.javascript.jscomp.CommandLineRunner.createCompiler(CommandLineRunner.java:858)
at 
com.google.javascript.jscomp.AbstractCommandLineRunner.doRun(AbstractCommandLineRunner.java:741)
at 
com.google.javascript.jscomp.AbstractCommandLineRunner.run(AbstractCommandLineRunner.java:380)
at 
com.google.javascript.jscomp.CommandLineRunner.main(CommandLineRunner.java:980)


Same error displayed on 4 packages using closure-compiler, looks like a 
bug in closure-compiler itself

Bug#1031486: ckeditor: FTBFS: make[1]: *** [debian/rules:24: debian/builddir/core/ckeditor_base.min.js] Error 254

[Lucas Nussbaum]

Source: ckeditor
Version: 4.19.1+dfsg-1
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20230216 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 '/<>'
> mkdir debian/builddir
> rsync -a . debian/builddir --exclude debian --exclude .git
> rm -f debian/builddir/ckeditor.js
> touch debian/builddir/build.stamp
> cd debian/builddir && closure-compiler --js core/ckeditor_base.js 
> --js_output_file core/ckeditor_base.min.js
> java.util.MissingResourceException: Can't find bundle for base name 
> com.google.javascript.rhino.head.resources.Messages, locale en
>   at 
> java.base/java.util.ResourceBundle.throwMissingResourceException(ResourceBundle.java:2045)
>   at 
> java.base/java.util.ResourceBundle.getBundleImpl(ResourceBundle.java:1683)
>   at 
> java.base/java.util.ResourceBundle.getBundleImpl(ResourceBundle.java:1586)
>   at 
> java.base/java.util.ResourceBundle.getBundleImpl(ResourceBundle.java:1549)
>   at java.base/java.util.ResourceBundle.getBundle(ResourceBundle.java:932)
>   at 
> com.google.javascript.rhino.head.ScriptRuntime$DefaultMessageProvider.getMessage(ScriptRuntime.java:4521)
>   at 
> com.google.javascript.rhino.head.ScriptRuntime.getMessage(ScriptRuntime.java:4501)
>   at 
> com.google.javascript.rhino.head.ScriptRuntime.getMessage0(ScriptRuntime.java:4446)
>   at 
> com.google.javascript.jscomp.RhinoErrorReporter.(RhinoErrorReporter.java:84)
>   at 
> com.google.javascript.jscomp.RhinoErrorReporter.(RhinoErrorReporter.java:32)
>   at 
> com.google.javascript.jscomp.RhinoErrorReporter$OldRhinoErrorReporter.(RhinoErrorReporter.java:162)
>   at 
> com.google.javascript.jscomp.RhinoErrorReporter$OldRhinoErrorReporter.(RhinoErrorReporter.java:158)
>   at 
> com.google.javascript.jscomp.RhinoErrorReporter.forOldRhino(RhinoErrorReporter.java:119)
>   at com.google.javascript.jscomp.Compiler.(Compiler.java:176)
>   at 
> com.google.javascript.jscomp.CommandLineRunner.createCompiler(CommandLineRunner.java:858)
>   at 
> com.google.javascript.jscomp.AbstractCommandLineRunner.doRun(AbstractCommandLineRunner.java:741)
>   at 
> com.google.javascript.jscomp.AbstractCommandLineRunner.run(AbstractCommandLineRunner.java:380)
>   at 
> com.google.javascript.jscomp.CommandLineRunner.main(CommandLineRunner.java:980)
> make[1]: *** [debian/rules:24: debian/builddir/core/ckeditor_base.min.js] 
> Error 254


The full build log is available from:
http://qa-logs.debian.net/2023/02/16/ckeditor_4.19.1+dfsg-1_unstable.log

All bugs filed during this archive rebuild are listed at:
https://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=ftbfs-20230216;users=lu...@debian.org
or:
https://udd.debian.org/bugs/?release=na=ign=7=7=only=ftbfs-20230216=lu...@debian.org=1=1=1=1#results

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

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

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

Bug#1031477: python-oslo.concurrency: FTBFS: FileNotFoundError: [Errno 2] No such file or directory: '/tmp/tmpxztykbsm/tmpyb1wyys0/file-0'

[Lucas Nussbaum]

Source: python-oslo.concurrency
Version: 5.0.1-3
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20230216 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 '/<>'
> make[1]: pyversions: No such file or directory
> py3versions: no X-Python3-Version in control file, using supported versions
> pkgos-dh_auto_install --no-py2 --in-tmp
> + PKGOS_IN_TMP=no
> + echo WARNING: --no-py2 is deprecated and always on.
> WARNING: --no-py2 is deprecated and always on.
> + shift
> + PKGOS_IN_TMP=yes
> + shift
> + dpkg-parsechangelog -SSource
> + SRC_PKG_NAME=python-oslo.concurrency
> + echo python-oslo.concurrency
> + sed s/python-//
> + PY_MODULE_NAME=oslo.concurrency
> + py3versions -vr
> + PYTHON3S=3.11
> + [ yes = yes ]
> + TARGET_DIR=tmp
> + pwd
> + python3.11 setup.py install --install-layout=deb --root 
> /<>/debian/tmp
> /usr/lib/python3/dist-packages/setuptools/command/easy_install.py:146: 
> EasyInstallDeprecationWarning: easy_install command is deprecated. Use build 
> and pip and other standards-based tools.
>   warnings.warn(
> /usr/lib/python3/dist-packages/setuptools/command/install.py:34: 
> SetuptoolsDeprecationWarning: setup.py install is deprecated. Use build and 
> pip and other standards-based tools.
>   warnings.warn(
> running install
> [pbr] Generating AUTHORS
> [pbr] AUTHORS complete (0.0s)
> running build
> running build_py
> creating build
> creating build/lib
> creating build/lib/oslo_concurrency
> creating build/lib/oslo_concurrency/fixture
> copying oslo_concurrency/fixture/__init__.py -> 
> build/lib/oslo_concurrency/fixture
> copying oslo_concurrency/fixture/lockutils.py -> 
> build/lib/oslo_concurrency/fixture
> creating build/lib/oslo_concurrency/tests
> creating build/lib/oslo_concurrency/tests/unit
> copying oslo_concurrency/tests/unit/__init__.py -> 
> build/lib/oslo_concurrency/tests/unit
> copying oslo_concurrency/tests/unit/test_lockutils.py -> 
> build/lib/oslo_concurrency/tests/unit
> copying oslo_concurrency/tests/unit/test_lockutils_eventlet.py -> 
> build/lib/oslo_concurrency/tests/unit
> copying oslo_concurrency/tests/unit/test_processutils.py -> 
> build/lib/oslo_concurrency/tests/unit
> copying oslo_concurrency/tests/__init__.py -> build/lib/oslo_concurrency/tests
> copying oslo_concurrency/__init__.py -> build/lib/oslo_concurrency
> copying oslo_concurrency/lockutils.py -> build/lib/oslo_concurrency
> copying oslo_concurrency/prlimit.py -> build/lib/oslo_concurrency
> copying oslo_concurrency/opts.py -> build/lib/oslo_concurrency
> copying oslo_concurrency/processutils.py -> build/lib/oslo_concurrency
> copying oslo_concurrency/_i18n.py -> build/lib/oslo_concurrency
> copying oslo_concurrency/watchdog.py -> build/lib/oslo_concurrency
> copying oslo_concurrency/version.py -> build/lib/oslo_concurrency
> running egg_info
> creating oslo.concurrency.egg-info
> writing oslo.concurrency.egg-info/PKG-INFO
> writing dependency_links to oslo.concurrency.egg-info/dependency_links.txt
> writing entry points to oslo.concurrency.egg-info/entry_points.txt
> writing requirements to oslo.concurrency.egg-info/requires.txt
> writing top-level names to oslo.concurrency.egg-info/top_level.txt
> [pbr] Processing SOURCES.txt
> writing manifest file 'oslo.concurrency.egg-info/SOURCES.txt'
> warning: no files found matching 'AUTHORS'
> warning: no files found matching 'ChangeLog'
> warning: no previously-included files found matching '.gitignore'
> warning: no previously-included files found matching '.gitreview'
> warning: no previously-included files matching '*.pyc' found anywhere in 
> distribution
> adding license file 'LICENSE'
> writing manifest file 'oslo.concurrency.egg-info/SOURCES.txt'
> running install_lib
> creating /<>/debian/tmp
> creating /<>/debian/tmp/usr
> creating /<>/debian/tmp/usr/lib
> creating /<>/debian/tmp/usr/lib/python3
> creating /<>/debian/tmp/usr/lib/python3/dist-packages
> creating 
> /<>/debian/tmp/usr/lib/python3/dist-packages/oslo_concurrency
> copying build/lib/oslo_concurrency/__init__.py -> 
> /<>/debian/tmp/usr/lib/python3/dist-packages/oslo_concurrency
> copying build/lib/oslo_concurrency/lockutils.py -> 
> /<>/debian/tmp/usr/lib/python3/dist-packages/oslo_concurrency
> copying build/lib/oslo_concurrency/prlimit.py -> 
> /<>/debian/tmp/usr/lib/python3/dist-packages/oslo_concurrency
> copying build/lib/oslo_concurrency/opts.py -> 
> /<>/debian/tmp/usr/lib/python3/dist-packages/oslo_concurre

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

[Lucas Nussbaum]

Source: augur
Version: 20.0.0-1
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20230216 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/augur
> copying augur/__init__.py -> 
> /<>/.pybuild/cpython3_3.11/build/augur
> copying augur/dates.py -> /<>/.pybuild/cpython3_3.11/build/augur
> copying augur/frequencies.py -> 
> /<>/.pybuild/cpython3_3.11/build/augur
> copying augur/titer_model.py -> 
> /<>/.pybuild/cpython3_3.11/build/augur
> copying augur/__main__.py -> 
> /<>/.pybuild/cpython3_3.11/build/augur
> copying augur/errors.py -> /<>/.pybuild/cpython3_3.11/build/augur
> copying augur/align.py -> /<>/.pybuild/cpython3_3.11/build/augur
> copying augur/export.py -> /<>/.pybuild/cpython3_3.11/build/augur
> copying augur/parse.py -> /<>/.pybuild/cpython3_3.11/build/augur
> copying augur/refine.py -> /<>/.pybuild/cpython3_3.11/build/augur
> copying augur/export_v1.py -> 
> /<>/.pybuild/cpython3_3.11/build/augur
> copying augur/argparse_.py -> 
> /<>/.pybuild/cpython3_3.11/build/augur
> copying augur/mask.py -> /<>/.pybuild/cpython3_3.11/build/augur
> copying augur/clades.py -> /<>/.pybuild/cpython3_3.11/build/augur
> copying augur/traits.py -> /<>/.pybuild/cpython3_3.11/build/augur
> copying augur/sequence_traits.py -> 
> /<>/.pybuild/cpython3_3.11/build/augur
> copying augur/ancestral.py -> 
> /<>/.pybuild/cpython3_3.11/build/augur
> copying augur/index.py -> /<>/.pybuild/cpython3_3.11/build/augur
> copying augur/tree.py -> /<>/.pybuild/cpython3_3.11/build/augur
> copying augur/__version__.py -> 
> /<>/.pybuild/cpython3_3.11/build/augur
> copying augur/distance.py -> 
> /<>/.pybuild/cpython3_3.11/build/augur
> copying augur/validate_export.py -> 
> /<>/.pybuild/cpython3_3.11/build/augur
> copying augur/titers.py -> /<>/.pybuild/cpython3_3.11/build/augur
> copying augur/translate.py -> 
> /<>/.pybuild/cpython3_3.11/build/augur
> copying augur/validate.py -> 
> /<>/.pybuild/cpython3_3.11/build/augur
> copying augur/filenames.py -> 
> /<>/.pybuild/cpython3_3.11/build/augur
> copying augur/export_v2.py -> 
> /<>/.pybuild/cpython3_3.11/build/augur
> copying augur/lbi.py -> /<>/.pybuild/cpython3_3.11/build/augur
> copying augur/frequency_estimators.py -> 
> /<>/.pybuild/cpython3_3.11/build/augur
> copying augur/version.py -> 
> /<>/.pybuild/cpython3_3.11/build/augur
> copying augur/reconstruct_sequences.py -> 
> /<>/.pybuild/cpython3_3.11/build/augur
> copying augur/types.py -> /<>/.pybuild/cpython3_3.11/build/augur
> copying augur/utils.py -> /<>/.pybuild/cpython3_3.11/build/augur
> creating /<>/.pybuild/cpython3_3.11/build/augur/filter
> copying augur/filter/__init__.py -> 
> /<>/.pybuild/cpython3_3.11/build/augur/filter
> copying augur/filter/include_exclude_rules.py -> 
> /<>/.pybuild/cpython3_3.11/build/augur/filter
> copying augur/filter/io.py -> 
> /<>/.pybuild/cpython3_3.11/build/augur/filter
> copying augur/filter/_run.py -> 
> /<>/.pybuild/cpython3_3.11/build/augur/filter
> copying augur/filter/subsample.py -> 
> /<>/.pybuild/cpython3_3.11/build/augur/filter
> copying augur/filter/validate_arguments.py -> 
> /<>/.pybuild/cpython3_3.11/build/augur/filter
> creating /<>/.pybuild/cpython3_3.11/build/augur/measurements
> copying augur/measurements/__init__.py -> 
> /<>/.pybuild/cpython3_3.11/build/augur/measurements
> copying augur/measurements/export.py -> 
> /<>/.pybuild/cpython3_3.11/build/augur/measurements
> copying augur/measurements/concat.py -> 
> /<>/.pybuild/cpython3_3.11/build/augur/measurements
> creating /<>/.pybuild/cpython3_3.11/build/augur/curate
> copying augur/curate/__init__.py -> 
> /<>/.pybuild/cpython3_3.11/build/augur/curate
> copying augur/curate/passthru.py -> 
> /<>/.pybuild/cpython3_3.11/build/augur/curate
> copying 

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

[Lucas Nussbaum]

Source: python-confluent-kafka
Version: 1.7.0-2
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20230216 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
>   pybuild --configure -i python{version} -p 3.11
> I: pybuild base:240: python3.11 setup.py config 
> running config
>dh_auto_build -O--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_confluent-kafka/build/confluent_kafka
> copying src/confluent_kafka/__init__.py -> 
> /<>/.pybuild/cpython3_3.11_confluent-kafka/build/confluent_kafka
> copying src/confluent_kafka/serializing_producer.py -> 
> /<>/.pybuild/cpython3_3.11_confluent-kafka/build/confluent_kafka
> copying src/confluent_kafka/deserializing_consumer.py -> 
> /<>/.pybuild/cpython3_3.11_confluent-kafka/build/confluent_kafka
> copying src/confluent_kafka/error.py -> 
> /<>/.pybuild/cpython3_3.11_confluent-kafka/build/confluent_kafka
> creating 
> /<>/.pybuild/cpython3_3.11_confluent-kafka/build/confluent_kafka/serialization
> copying src/confluent_kafka/serialization/__init__.py -> 
> /<>/.pybuild/cpython3_3.11_confluent-kafka/build/confluent_kafka/serialization
> creating 
> /<>/.pybuild/cpython3_3.11_confluent-kafka/build/confluent_kafka/admin
> copying src/confluent_kafka/admin/__init__.py -> 
> /<>/.pybuild/cpython3_3.11_confluent-kafka/build/confluent_kafka/admin
> creating 
> /<>/.pybuild/cpython3_3.11_confluent-kafka/build/confluent_kafka/avro
> copying src/confluent_kafka/avro/load.py -> 
> /<>/.pybuild/cpython3_3.11_confluent-kafka/build/confluent_kafka/avro
> copying src/confluent_kafka/avro/__init__.py -> 
> /<>/.pybuild/cpython3_3.11_confluent-kafka/build/confluent_kafka/avro
> copying src/confluent_kafka/avro/cached_schema_registry_client.py -> 
> /<>/.pybuild/cpython3_3.11_confluent-kafka/build/confluent_kafka/avro
> copying src/confluent_kafka/avro/error.py -> 
> /<>/.pybuild/cpython3_3.11_confluent-kafka/build/confluent_kafka/avro
> creating 
> /<>/.pybuild/cpython3_3.11_confluent-kafka/build/confluent_kafka/schema_registry
> copying src/confluent_kafka/schema_registry/__init__.py -> 
> /<>/.pybuild/cpython3_3.11_confluent-kafka/build/confluent_kafka/schema_registry
> copying src/confluent_kafka/schema_registry/protobuf.py -> 
> /<>/.pybuild/cpython3_3.11_confluent-kafka/build/confluent_kafka/schema_registry
> copying src/confluent_kafka/schema_registry/schema_registry_client.py -> 
> /<>/.pybuild/cpython3_3.11_confluent-kafka/build/confluent_kafka/schema_registry
> copying src/confluent_kafka/schema_registry/avro.py -> 
> /<>/.pybuild/cpython3_3.11_confluent-kafka/build/confluent_kafka/schema_registry
> copying src/confluent_kafka/schema_registry/json_schema.py -> 
> /<>/.pybuild/cpython3_3.11_confluent-kafka/build/confluent_kafka/schema_registry
> copying src/confluent_kafka/schema_registry/error.py -> 
> /<>/.pybuild/cpython3_3.11_confluent-kafka/build/confluent_kafka/schema_registry
> creating 
> /<>/.pybuild/cpython3_3.11_confluent-kafka/build/confluent_kafka/kafkatest
> copying src/confluent_kafka/kafkatest/__init__.py -> 
> /<>/.pybuild/cpython3_3.11_confluent-kafka/build/confluent_kafka/kafkatest
> copying src/confluent_kafka/kafkatest/verifiable_consumer.py -> 
> /<>/.pybuild/cpython3_3.11_confluent-kafka/build/confluent_kafka/kafkatest
> copying src/confluent_kafka/kafkatest/verifiable_producer.py -> 
> /<>/.pybuild/cpython3_3.11_confluent-kafka/build/confluent_kafka/kafkatest
> copying src/confluent_kafka/kafkatest/verifiable_client.py -> 
> /<>/.pybuild/cpython3_3.11_confluent-kafka/build/confluent_kafka/kafkatest
> creating 
> /<>/.pybuild/cpython3_3.11_confluent-kafka/build/confluent_kafka/avro/serializer
> copying src/confluent_kafka/avro/serializer/__init__.py -> 
> /<>/.pybuild/cpython3_3.11_confluent-kafka/build/confluent_kafka/avro/serializer
> copying src/confluent_kafka/avro/serializer/message_serializer.py -> 
> /<>/.pybuild/cpython3_3.11_confluent-kafka/build/confluent_kafka/avro/serializer
> running build_ext
> building 'confluent_kafka.cimpl' extension
> creating build
> creating build/tem

Bug#1031482: soundmanager2: FTBFS: make[1]: *** [debian/rules:8: override_dh_auto_build] Error 25

[Lucas Nussbaum]

Source: soundmanager2
Version: 2.97a.20150601+dfsg2-2
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20230216 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 -- \
>   -Dmtasc=/bin/true \
>   -Dmxmlc=/bin/true \
>   -Dclosure-compiler.jar=/usr/share/java/closure-compiler.jar
> dh_auto_build: warning: Compatibility levels before 10 are deprecated (level 
> 9 in use)
>   ant -Duser.name debian -Dmtasc=/bin/true -Dmxmlc=/bin/true 
> -Dclosure-compiler.jar=/usr/share/java/closure-compiler.jar
> Buildfile: /<>/build.xml
>  [echo] /usr/share/java/closure-compiler.jar
> 
> build:
>  [echo] Removing existing JS builds...
>  [echo] Compressing minified JS...
> [mkdir] Created dir: /<>/tmp
> 
> BUILD FAILED
> /<>/build.xml:75: java.util.MissingResourceException: Can't find 
> bundle for base name com.google.javascript.rhino.head.resources.Messages, 
> locale en
>   at 
> java.base/java.util.ResourceBundle.throwMissingResourceException(ResourceBundle.java:2045)
>   at 
> java.base/java.util.ResourceBundle.getBundleImpl(ResourceBundle.java:1683)
>   at 
> java.base/java.util.ResourceBundle.getBundleImpl(ResourceBundle.java:1586)
>   at 
> java.base/java.util.ResourceBundle.getBundleImpl(ResourceBundle.java:1549)
>   at java.base/java.util.ResourceBundle.getBundle(ResourceBundle.java:932)
>   at 
> com.google.javascript.rhino.head.ScriptRuntime$DefaultMessageProvider.getMessage(ScriptRuntime.java:4521)
>   at 
> com.google.javascript.rhino.head.ScriptRuntime.getMessage(ScriptRuntime.java:4501)
>   at 
> com.google.javascript.rhino.head.ScriptRuntime.getMessage0(ScriptRuntime.java:4446)
>   at 
> com.google.javascript.jscomp.RhinoErrorReporter.(RhinoErrorReporter.java:84)
>   at 
> com.google.javascript.jscomp.RhinoErrorReporter.(RhinoErrorReporter.java:32)
>   at 
> com.google.javascript.jscomp.RhinoErrorReporter$OldRhinoErrorReporter.(RhinoErrorReporter.java:162)
>   at 
> com.google.javascript.jscomp.RhinoErrorReporter$OldRhinoErrorReporter.(RhinoErrorReporter.java:158)
>   at 
> com.google.javascript.jscomp.RhinoErrorReporter.forOldRhino(RhinoErrorReporter.java:119)
>   at com.google.javascript.jscomp.Compiler.(Compiler.java:176)
>   at com.google.javascript.jscomp.Compiler.(Compiler.java:237)
>   at 
> com.google.javascript.jscomp.ant.CompileTask.createCompiler(CompileTask.java:459)
>   at 
> com.google.javascript.jscomp.ant.CompileTask.execute(CompileTask.java:283)
>   at org.apache.tools.ant.UnknownElement.execute(UnknownElement.java:299)
>   at 
> java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>   at 
> java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:77)
>   at 
> java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
>   at java.base/java.lang.reflect.Method.invoke(Method.java:568)
>   at 
> org.apache.tools.ant.dispatch.DispatchUtils.execute(DispatchUtils.java:99)
>   at org.apache.tools.ant.Task.perform(Task.java:350)
>   at org.apache.tools.ant.Target.execute(Target.java:449)
>   at org.apache.tools.ant.Target.performTasks(Target.java:470)
>   at org.apache.tools.ant.Project.executeSortedTargets(Project.java:1401)
>   at org.apache.tools.ant.Project.executeTarget(Project.java:1374)
>   at 
> org.apache.tools.ant.helper.DefaultExecutor.executeTargets(DefaultExecutor.java:41)
>   at org.apache.tools.ant.Project.executeTargets(Project.java:1264)
>   at org.apache.tools.ant.Main.runBuild(Main.java:818)
>   at org.apache.tools.ant.Main.startAnt(Main.java:223)
>   at org.apache.tools.ant.launch.Launcher.run(Launcher.java:284)
>   at org.apache.tools.ant.launch.Launcher.main(Launcher.java:101)
> 
> Total time: 0 seconds
> dh_auto_build: error: ant -Duser.name debian -Dmtasc=/bin/true 
> -Dmxmlc=/bin/true -Dclosure-compiler.jar=/usr/share/java/closure-compiler.jar 
> returned exit code 1
> make[1]: *** [debian/rules:8: override_dh_auto_build] Error 25


The full build log is available from:
http://qa-logs.debian.net/2023/02/16/soundmanager2_2.97a.20150601+dfsg2-2_unstable.log

All bugs filed during this archive rebuild are listed at:
https://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=ftbfs-20230216;users=lu...@debian.org
or:
https://udd.debian.org/bugs/?release=na=ign=7=7=only=ftbfs-20230216=lu...@debian.org=1=1=1=1#results

A list of current common problems and possible solutions

Bug#1031481: python-oslo.db: FTBFS: E: Build killed with signal TERM after 150 minutes of inactivity

[Lucas Nussbaum]

Source: python-oslo.db
Version: 12.1.0-2
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20230216 ftbfs-bookworm

Hi,

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


Relevant part (hopefully):
> oslo_db.tests.test_api.DBRetryRequestCase.test_retry_wrapper_succeeds
> oslo_db.tests.test_api.DBRetryRequestCase.test_retry_wrapper_succeeds ... ok
> oslo_db.tests.test_api.DBRetryRequestCase.test_wrap_db_retry_get_interval
> oslo_db.tests.test_api.DBRetryRequestCase.test_wrap_db_retry_get_interval ... 
> ok
> oslo_db.tests.test_concurrency.TpoolDbapiWrapperTestCase.test_db_api_common
> oslo_db.tests.test_concurrency.TpoolDbapiWrapperTestCase.test_db_api_common 
> ... ok
> oslo_db.tests.test_concurrency.TpoolDbapiWrapperTestCase.test_db_api_config_change
> oslo_db.tests.test_concurrency.TpoolDbapiWrapperTestCase.test_db_api_config_change
>  ... ok
>ERROR [oslo_db.concurrency] 'eventlet' is required for TpoolDbapiWrapper.
> Traceback (most recent call last):
>   File "/<>/oslo_db/concurrency.py", line 78, in _api
> from eventlet import tpool
> ModuleNotFoundError: import of eventlet halted; None in sys.modules
> oslo_db.tests.test_concurrency.TpoolDbapiWrapperTestCase.test_db_api_without_installed_eventlet
> oslo_db.tests.test_concurrency.TpoolDbapiWrapperTestCase.test_db_api_without_installed_eventlet
>  ... ok
> E: Build killed with signal TERM after 150 minutes of inactivity


The full build log is available from:
http://qa-logs.debian.net/2023/02/16/python-oslo.db_12.1.0-2_unstable.log

All bugs filed during this archive rebuild are listed at:
https://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=ftbfs-20230216;users=lu...@debian.org
or:
https://udd.debian.org/bugs/?release=na=ign=7=7=only=ftbfs-20230216=lu...@debian.org=1=1=1=1#results

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

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

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

Bug#1031480: libreflectasm-java: FTBFS: make: *** [debian/rules:4: binary] Error 25

[Lucas Nussbaum]

Source: libreflectasm-java
Version: 1.11.9+dfsg-3
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20230216 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 javahelper
>dh_update_autotools_config
>dh_autoreconf
>dh_auto_configure
>   mh_patchpoms -plibreflectasm-java --debian-build --keep-pom-version 
> --maven-repo=/<>/libreflectasm-java-1.11.9\+dfsg/debian/maven-repo
>jh_linkjars
>dh_auto_build
>   /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=/<>/libreflectasm-java-1.11.9\+dfsg
>  -Dclassworlds.conf=/etc/maven/m2-debian.conf 
> org.codehaus.plexus.classworlds.launcher.Launcher 
> -s/etc/maven/settings-debian.xml 
> -Ddebian.dir=/<>/libreflectasm-java-1.11.9\+dfsg/debian 
> -Dmaven.repo.local=/<>/libreflectasm-java-1.11.9\+dfsg/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.
> [INFO] Scanning for projects...
> [INFO] 
> [INFO] --< com.esotericsoftware:reflectasm 
> >---
> [INFO] Building ReflectASM 1.11.9
> [INFO] ---[ bundle 
> ]---
> [INFO] 
> [INFO] --- maven-compiler-plugin:3.10.1:compile (default-compile) @ 
> reflectasm ---
> [INFO] Changes detected - recompiling the module!
> [INFO] Compiling 5 source files to /<>/target/classes
> Use of target 1.5 is no longer supported, switching to 7
> Use of source 1.5 is no longer supported, switching to 7
> [INFO] 
> /<>/src/com/esotericsoftware/reflectasm/ConstructorAccess.java: 
> Some input files use or override a deprecated API.
> [INFO] 
> /<>/src/com/esotericsoftware/reflectasm/ConstructorAccess.java: 
> Recompile with -Xlint:deprecation for details.
> [INFO] 
> /<>/src/com/esotericsoftware/reflectasm/AccessClassLoader.java: 
> Some input files use unchecked or unsafe operations.
> [INFO] 
> /<>/src/com/esotericsoftware/reflectasm/AccessClassLoader.java: 
> Recompile with -Xlint:unchecked for details.
> [INFO] 
> [INFO] --- maven-compiler-plugin:3.10.1:testCompile (default-testCompile) @ 
> reflectasm ---
> [INFO] Changes detected - recompiling the module!
> [INFO] Compiling 8 source files to /<>/target/test-classes
> Use of target 1.5 is no longer supported, switching to 7
> Use of source 1.5 is no longer supported, switching to 7
> [INFO] 
> /<>/test/com/esotericsoftware/reflectasm/MethodAccessTest.java: 
> Some input files use or override a deprecated API.
> [INFO] 
> /<>/test/com/esotericsoftware/reflectasm/MethodAccessTest.java: 
> Recompile with -Xlint:deprecation for details.
> [INFO] 
> /<>/test/com/esotericsoftware/reflectasm/benchmark/Benchmark.java:
>  Some input files use unchecked or unsafe operations.
> [INFO] 
> /<>/test/com/esotericsoftware/reflectasm/benchmark/Benchmark.java:
>  Recompile with -Xlint:unchecked for details.
> [INFO] 
> [INFO] --- maven-surefire-plugin:2.22.3:test (default-test) @ reflectasm ---
> [INFO] Tests are skipped.
> [INFO] 
> [INFO] --- maven-bundle-plugin:3.5.1:bundle (default-bundle) @ reflectasm ---
> [INFO] 
> [INFO] --- maven-javadoc-plugin:3.4.1:jar (default-cli) @ reflectasm ---
> [INFO] Adding the --ignore-source-errors option
> [INFO] No previous run data found, generating javadoc.
> [INFO] Building jar: /<>/target/reflectasm-1.11.9-javadoc.jar
> [INFO] 
> [INFO] --< com.esotericsoftware:reflectasm 
> >---
> [INFO] Building ReflectASM 1.11.9
> [INFO] ---[ bundle 
> ]---
> [INFO] 
> [INFO] >>> maven-javadoc-plugin:3.4.1:aggregate (default-cli) > compile @ 
> reflectasm >>>
> [INFO] 
> [INFO] --- maven-compiler-plugin:3.10.1:compile (default-compile) @ 
> reflectasm ---
> [INFO] Changes detected - recompiling the module!
> [INFO] Compiling 5 source files to /<>/target/classes
> Use of target 1.5 is no longer supported, switching to 7
> Use of source 1.5 is no longer supported, switching to 7
> [INFO] 
> /<>/src/com/esotericsoftware/reflectasm/ConstructorAccess.java: 
> Some input files use or override a deprecated API.
> [INFO] 
> /<>/src/com/esoter

Bug#1031479: ruby-eye: FTBFS: ERROR: Test "ruby3.1" failed: /usr/lib/ruby/vendor_ruby/rubygems/specification.rb:1413:in `rescue in block in activate_dependencies': Could not find 'celluloid' (~> 0.16.

[Lucas Nussbaum]

Source: ruby-eye
Version: 0.7-5.1
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20230216 ftbfs-bookworm

Hi,

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


Relevant part (hopefully):
> /usr/lib/ruby/vendor_ruby/rubygems/specification.rb:1413:in `rescue in block 
> in activate_dependencies': Could not find 'celluloid' (~> 0.16.0) among 108 
> total gem(s) (Gem::MissingSpecError)
> Checked in 
> 'GEM_PATH=/<>/debian/ruby-eye/usr/share/rubygems-integration/all:/var/lib/gems/3.1.0:/usr/local/lib/ruby/gems/3.1.0:/usr/lib/ruby/gems/3.1.0:/usr/lib/x86_64-linux-gnu/ruby/gems/3.1.0:/usr/share/rubygems-integration/3.1.0:/usr/share/rubygems-integration/all:/usr/lib/x86_64-linux-gnu/rubygems-integration/3.1.0'
>  at: 
> /<>/debian/ruby-eye/usr/share/rubygems-integration/all/specifications/eye-0.7.gemspec,
>  execute `gem env` for more information
>   from /usr/lib/ruby/vendor_ruby/rubygems/specification.rb:1410:in `block 
> in activate_dependencies'
>   from /usr/lib/ruby/vendor_ruby/rubygems/specification.rb:1399:in `each'
>   from /usr/lib/ruby/vendor_ruby/rubygems/specification.rb:1399:in 
> `activate_dependencies'
>   from /usr/lib/ruby/vendor_ruby/rubygems/specification.rb:1381:in 
> `activate'
>   from /usr/lib/ruby/vendor_ruby/rubygems/core_ext/kernel_gem.rb:68:in 
> `block in gem'
>   from /usr/lib/ruby/vendor_ruby/rubygems/core_ext/kernel_gem.rb:68:in 
> `synchronize'
>   from /usr/lib/ruby/vendor_ruby/rubygems/core_ext/kernel_gem.rb:68:in 
> `gem'
>   from -e:1:in `'
> /usr/lib/ruby/vendor_ruby/rubygems/dependency.rb:313:in `to_specs': Could not 
> find 'celluloid' (~> 0.16.0) - did find: [celluloid-0.18.0] 
> (Gem::MissingSpecVersionError)
> Checked in 
> 'GEM_PATH=/<>/debian/ruby-eye/usr/share/rubygems-integration/all:/var/lib/gems/3.1.0:/usr/local/lib/ruby/gems/3.1.0:/usr/lib/ruby/gems/3.1.0:/usr/lib/x86_64-linux-gnu/ruby/gems/3.1.0:/usr/share/rubygems-integration/3.1.0:/usr/share/rubygems-integration/all:/usr/lib/x86_64-linux-gnu/rubygems-integration/3.1.0'
>  , execute `gem env` for more information
>   from /usr/lib/ruby/vendor_ruby/rubygems/specification.rb:1411:in `block 
> in activate_dependencies'
>   from /usr/lib/ruby/vendor_ruby/rubygems/specification.rb:1399:in `each'
>   from /usr/lib/ruby/vendor_ruby/rubygems/specification.rb:1399:in 
> `activate_dependencies'
>   from /usr/lib/ruby/vendor_ruby/rubygems/specification.rb:1381:in 
> `activate'
>   from /usr/lib/ruby/vendor_ruby/rubygems/core_ext/kernel_gem.rb:68:in 
> `block in gem'
>   from /usr/lib/ruby/vendor_ruby/rubygems/core_ext/kernel_gem.rb:68:in 
> `synchronize'
>   from /usr/lib/ruby/vendor_ruby/rubygems/core_ext/kernel_gem.rb:68:in 
> `gem'
>   from -e:1:in `'
> abbrev (default: 0.1.0)
> base64 (default: 0.1.1)
> benchmark (default: 0.2.0)
> bigdecimal (default: 3.1.1)
> bundler (2.3.15, default: 2.3.7)
> celluloid (0.18.0)
> celluloid-essentials (0.20.5)
> celluloid-extras (0.20.5)
> celluloid-fsm (0.20.5)
> celluloid-io (0.16.2)
> celluloid-pool (0.20.5)
> celluloid-supervision (0.20.5)
> cgi (default: 0.3.5)
> csv (default: 3.2.2)
> date (default: 3.2.2)
> debug (1.4.0)
> delegate (default: 0.2.0)
> did_you_mean (default: 1.6.1)
> digest (default: 3.1.0)
> dotenv (2.4.0)
> drb (default: 2.1.0)
> english (default: 0.7.1)
> erb (default: 2.2.3)
> error_highlight (default: 0.3.0)
> etc (default: 1.3.0)
> fcntl (default: 1.0.1)
> fiddle (default: 1.1.0)
> fileutils (default: 1.6.0)
> find (default: 0.1.1)
> forwardable (default: 1.3.2)
> getoptlong (default: 0.1.1)
> hitimes (1.3.1)
> io-console (default: 0.5.11)
> io-nonblock (default: 0.1.0)
> io-wait (default: 0.2.1)
> ipaddr (default: 1.2.4)
> irb (default: 1.4.1)
> json (default: 2.6.1)
> logger (default: 1.5.0)
> matrix (0.4.2)
> minitest (5.15.0)
> mutex_m (default: 0.1.1)
> nenv (0.3.0)
> net-ftp (0.1.3)
> net-http (default: 0.2.0)
> net-imap (0.2.3)
> net-pop (0.1.1)
> net-protocol (default: 0.1.2)
> net-smtp (0.3.1)
> net-telnet (0.2.0)
> nio4r (2.5.8)
> nkf (default: 0.1.1)
> observer (default: 0.1.1)
> open-uri (default: 0.2.0)
> open3 (default: 0.1.1)
> openssl (default: 3.0.0)
> optparse (default: 0.2.0)
> ostruct (default: 0.5.2)
> pathname (default: 0.2.0)
> power_assert (2.0.1)
> pp (default: 0.3.0)
> prettyprint (default: 0.1.1)
> prime (0.1.2)
> pstore (default: 0.1.1)
> psych (default: 4.0.3)
> racc (default: 1.6.0)
> rake (13.0.6)
> rbs (2.1.0)
> rdoc (default: 6.4.0)
> readline (default: 0.0.3)
> readline-ext (default: 0.1.4)
> reline (default: 0.3

Bug#1031478: nrepl-clojure: FTBFS: E: Build killed with signal TERM after 150 minutes of inactivity

[Lucas Nussbaum]

Source: nrepl-clojure
Version: 1.0.0-4
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20230216 ftbfs-bookworm

Hi,

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


Relevant part (hopefully):
> Clojure 1.11.1
> OpenJDK 64-Bit Server VM 17.0.6+10-Debian-1
> Interrupt: Control+C
> Exit:  Control+D or (exit) or (quit)
> 
> lein test nrepl.cmdline-tty-test
> 
> lein test nrepl.core-test
> 
> lein test :only nrepl.core-test/dynamic-middleware+sideloading-interleaved
> 
> FAIL in (dynamic-middleware+sideloading-interleaved) (core_test.clj:1066)
> bencode transport sideloader state persists across middleware changes
> expected: (= [:added-middleware :provided-ns :provided-ns [:eval-ok 
> "\"Hello!\""]] (reduce (fn [result {:keys [id status type name value], :as 
> msg}] (cond (status? :unexpected-provide status) (throw (ex-info "Unexpected 
> provide" msg)) (and (= name (str "foo/" ns ".clj")) (status? 
> :sideloader-lookup status) (not (some #{:added-middleware} result))) (do 
> (send {:id 3, :op "add-middleware", :session sl-session, :middleware []}) 
> (conj result :added-middleware)) (or (and (= 3 id) (status? :done status)) 
> (and (= name (str "foo/" ns ".clj")) (status? :sideloader-lookup status))) 
> (do (send {:session sl-session, :id 1, :op "sideloader-provide", :content 
> (string->content (str "(prn 'xx) (ns foo." ns ") (prn 'yy) (defn hello [] 
> \"Hello!\")")), :type "resource", :name (str "foo/" ns ".clj")}) (conj result 
> :provided-ns)) (status? :sideloader-lookup status) (do (send {:session 
> sl-session, :id 1, :op "sideloader-provide", :content "", :type type, :name 
> name}) result) (and (= 2 id) (status? :done status)) (do (send {:id 4, :op 
> "eval", :session sl-session, :code (str "(foo." ns "/hello)")}) result) (and 
> (= 4 id) value) (conj result [:eval-ok value]) (and (= 4 id) (status? :done 
> status)) (reduced result) :else result)) [] res))
>   actual: (not (= [:added-middleware :provided-ns :provided-ns [:eval-ok 
> "\"Hello!\""]] []))
> E: Build killed with signal TERM after 150 minutes of inactivity


The full build log is available from:
http://qa-logs.debian.net/2023/02/16/nrepl-clojure_1.0.0-4_unstable.log

All bugs filed during this archive rebuild are listed at:
https://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=ftbfs-20230216;users=lu...@debian.org
or:
https://udd.debian.org/bugs/?release=na=ign=7=7=only=ftbfs-20230216=lu...@debian.org=1=1=1=1#results

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

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

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

Bug#1031474: datatables-extensions: FTBFS: make[1]: *** [debian/rules:10: override_dh_install] Error 254

[Lucas Nussbaum]

Source: datatables-extensions
Version: 0.0+git20150910.28fd64e+dfsg-5
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20230216 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_install
> for min in `find debian -name "*.min.js"` ; do \
> closure-compiler --language_in ECMASCRIPT5 --charset 'utf-8' --js `echo 
> ${min} | sed 's/\.min//'` --js_output_file ${min} ; \
> done
> java.util.MissingResourceException: Can't find bundle for base name 
> com.google.javascript.rhino.head.resources.Messages, locale en
>   at 
> java.base/java.util.ResourceBundle.throwMissingResourceException(ResourceBundle.java:2045)
>   at 
> java.base/java.util.ResourceBundle.getBundleImpl(ResourceBundle.java:1683)
>   at 
> java.base/java.util.ResourceBundle.getBundleImpl(ResourceBundle.java:1586)
>   at 
> java.base/java.util.ResourceBundle.getBundleImpl(ResourceBundle.java:1549)
>   at java.base/java.util.ResourceBundle.getBundle(ResourceBundle.java:932)
>   at 
> com.google.javascript.rhino.head.ScriptRuntime$DefaultMessageProvider.getMessage(ScriptRuntime.java:4521)
>   at 
> com.google.javascript.rhino.head.ScriptRuntime.getMessage(ScriptRuntime.java:4501)
>   at 
> com.google.javascript.rhino.head.ScriptRuntime.getMessage0(ScriptRuntime.java:4446)
>   at 
> com.google.javascript.jscomp.RhinoErrorReporter.(RhinoErrorReporter.java:84)
>   at 
> com.google.javascript.jscomp.RhinoErrorReporter.(RhinoErrorReporter.java:32)
>   at 
> com.google.javascript.jscomp.RhinoErrorReporter$OldRhinoErrorReporter.(RhinoErrorReporter.java:162)
>   at 
> com.google.javascript.jscomp.RhinoErrorReporter$OldRhinoErrorReporter.(RhinoErrorReporter.java:158)
>   at 
> com.google.javascript.jscomp.RhinoErrorReporter.forOldRhino(RhinoErrorReporter.java:119)
>   at com.google.javascript.jscomp.Compiler.(Compiler.java:176)
>   at 
> com.google.javascript.jscomp.CommandLineRunner.createCompiler(CommandLineRunner.java:858)
>   at 
> com.google.javascript.jscomp.AbstractCommandLineRunner.doRun(AbstractCommandLineRunner.java:741)
>   at 
> com.google.javascript.jscomp.AbstractCommandLineRunner.run(AbstractCommandLineRunner.java:380)
>   at 
> com.google.javascript.jscomp.CommandLineRunner.main(CommandLineRunner.java:980)
> java.util.MissingResourceException: Can't find bundle for base name 
> com.google.javascript.rhino.head.resources.Messages, locale en
>   at 
> java.base/java.util.ResourceBundle.throwMissingResourceException(ResourceBundle.java:2045)
>   at 
> java.base/java.util.ResourceBundle.getBundleImpl(ResourceBundle.java:1683)
>   at 
> java.base/java.util.ResourceBundle.getBundleImpl(ResourceBundle.java:1586)
>   at 
> java.base/java.util.ResourceBundle.getBundleImpl(ResourceBundle.java:1549)
>   at java.base/java.util.ResourceBundle.getBundle(ResourceBundle.java:932)
>   at 
> com.google.javascript.rhino.head.ScriptRuntime$DefaultMessageProvider.getMessage(ScriptRuntime.java:4521)
>   at 
> com.google.javascript.rhino.head.ScriptRuntime.getMessage(ScriptRuntime.java:4501)
>   at 
> com.google.javascript.rhino.head.ScriptRuntime.getMessage0(ScriptRuntime.java:4446)
>   at 
> com.google.javascript.jscomp.RhinoErrorReporter.(RhinoErrorReporter.java:84)
>   at 
> com.google.javascript.jscomp.RhinoErrorReporter.(RhinoErrorReporter.java:32)
>   at 
> com.google.javascript.jscomp.RhinoErrorReporter$OldRhinoErrorReporter.(RhinoErrorReporter.java:162)
>   at 
> com.google.javascript.jscomp.RhinoErrorReporter$OldRhinoErrorReporter.(RhinoErrorReporter.java:158)
>   at 
> com.google.javascript.jscomp.RhinoErrorReporter.forOldRhino(RhinoErrorReporter.java:119)
>   at com.google.javascript.jscomp.Compiler.(Compiler.java:176)
>   at 
> com.google.javascript.jscomp.CommandLineRunner.createCompiler(CommandLineRunner.java:858)
>   at 
> com.google.javascript.jscomp.AbstractCommandLineRunner.doRun(AbstractCommandLineRunner.java:741)
>   at 
> com.google.javascript.jscomp.AbstractCommandLineRunner.run(AbstractCommandLineRunner.java:380)
>   at 
> com.google.javascript.jscomp.CommandLineRunner.main(CommandLineRunner.java:980)
> java.util.MissingResourceException: Can't find bundle for base name 
> com.google.javascript.rhino.head.resources.Messages, locale en
>   at 
> java.base/java.util.ResourceBundle.throwMissingResourceException(ResourceBundle.java:2045)
>   at 
> java.base/java.util.ResourceBundle.getBundleImpl(ResourceBundle.

Bug#1031476: ruby-celluloid-io: FTBFS: ERROR: Test "ruby3.1" failed: Failure/Error:

[Lucas Nussbaum]

Source: ruby-celluloid-io
Version: 0.16.2-5
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20230216 ftbfs-bookworm

Hi,

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


Relevant part (hopefully):
> Failure/Error:
>   class Mailbox < Celluloid::EventedMailbox
> def initialize
>   super(Reactor)
> end
> 
> NameError:
>   uninitialized constant Celluloid::EventedMailbox
> 
>   class Mailbox < Celluloid::EventedMailbox
>
> # ./lib/celluloid/io/mailbox.rb:4:in `'
> # ./lib/celluloid/io/mailbox.rb:2:in `'
> # ./lib/celluloid/io/mailbox.rb:1:in `'
> # ./lib/celluloid/io.rb:5:in `'
> # ./spec/spec_helper.rb:1:in `'
> # ./spec/celluloid/io_spec.rb:1:in `'
> # 
> /usr/share/rubygems-integration/all/gems/rspec-core-3.12.0/lib/rspec/core/configuration.rb:2117:in
>  `load'
> # 
> /usr/share/rubygems-integration/all/gems/rspec-core-3.12.0/lib/rspec/core/configuration.rb:2117:in
>  `load_file_handling_errors'
> # 
> /usr/share/rubygems-integration/all/gems/rspec-core-3.12.0/lib/rspec/core/configuration.rb:1617:in
>  `block in load_spec_files'
> # 
> /usr/share/rubygems-integration/all/gems/rspec-core-3.12.0/lib/rspec/core/configuration.rb:1615:in
>  `each'
> # 
> /usr/share/rubygems-integration/all/gems/rspec-core-3.12.0/lib/rspec/core/configuration.rb:1615:in
>  `load_spec_files'
> # 
> /usr/share/rubygems-integration/all/gems/rspec-core-3.12.0/lib/rspec/core/runner.rb:102:in
>  `setup'
> # 
> /usr/share/rubygems-integration/all/gems/rspec-core-3.12.0/lib/rspec/core/runner.rb:86:in
>  `run'
> # 
> /usr/share/rubygems-integration/all/gems/rspec-core-3.12.0/lib/rspec/core/runner.rb:71:in
>  `run'
> # 
> /usr/share/rubygems-integration/all/gems/rspec-core-3.12.0/lib/rspec/core/runner.rb:45:in
>  `invoke'
> # /usr/share/rubygems-integration/all/gems/rspec-core-3.12.0/exe/rspec:4:in 
> `'
> No examples found.
> 
> Finished in 0.4 seconds (files took 0.1943 seconds to load)
> 0 examples, 0 failures, 8 errors occurred outside of examples
> 
> /usr/bin/ruby3.1 
> -I/usr/share/rubygems-integration/all/gems/rspec-support-3.12.0/lib:/usr/share/rubygems-integration/all/gems/rspec-core-3.12.0/lib
>  /usr/share/rubygems-integration/all/gems/rspec-core-3.12.0/exe/rspec 
> ./spec/celluloid/io/actor_spec.rb ./spec/celluloid/io/dns_resolver_spec.rb 
> ./spec/celluloid/io/ssl_server_spec.rb ./spec/celluloid/io/ssl_socket_spec.rb 
> ./spec/celluloid/io/tcp_server_spec.rb ./spec/celluloid/io/udp_socket_spec.rb 
> ./spec/celluloid/io/unix_server_spec.rb ./spec/celluloid/io_spec.rb --format 
> documentation failed
> ERROR: Test "ruby3.1" failed: 


The full build log is available from:
http://qa-logs.debian.net/2023/02/16/ruby-celluloid-io_0.16.2-5_unstable.log

All bugs filed during this archive rebuild are listed at:
https://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=ftbfs-20230216;users=lu...@debian.org
or:
https://udd.debian.org/bugs/?release=na=ign=7=7=only=ftbfs-20230216=lu...@debian.org=1=1=1=1#results

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

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

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

Bug#1031475: conda-package-streaming: FTBFS: dh_auto_test: error: pybuild --test --test-pytest -i python{version} -p 3.11 returned exit code 13

[Lucas Nussbaum]

Source: conda-package-streaming
Version: 0.7.0-4
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20230216 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
>dh_auto_build -O--buildsystem=pybuild
> I: pybuild plugin_pyproject:107: Building wheel for python3.11 with "build" 
> module
> I: pybuild base:240: python3.11 -m build --skip-dependency-check 
> --no-isolation --wheel --outdir /<>/.pybuild/cpython3_3.11 
> * Building wheel...
> Successfully built conda_package_streaming-0.7.0-py3-none-any.whl
> I: pybuild plugin_pyproject:119: Unpacking wheel built for python3.11 with 
> "installer" module
>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.2, pytest-7.2.1, pluggy-1.0.0+repack
> rootdir: /<>, configfile: pyproject.toml
> plugins: mock-3.8.2, cov-4.0.0
> collected 15 items / 1 error
> 
>  ERRORS 
> 
>  ERROR collecting .pybuild/cpython3_3.11/build/tests/test_transmute.py 
> _
> ImportError while importing test module 
> '/<>/.pybuild/cpython3_3.11/build/tests/test_transmute.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_transmute.py:14: in 
> from conda_package_streaming.transmute import transmute, transmute_tar_bz2
> conda_package_streaming/transmute.py:23: in 
> import zstandard
> /usr/lib/python3/dist-packages/zstandard/__init__.py:39: in 
> from .backend_c import *  # type: ignore
> E   ImportError: zstd C API versions mismatch; Python bindings were not 
> compiled/linked against expected zstd version (10504 returned by the lib, 
> 10502 hardcoded in zstd headers, 10502 hardcoded in the cext)
> === warnings summary 
> ===
> ../../../../../../usr/lib/python3/dist-packages/bottle.py:38
>   /usr/lib/python3/dist-packages/bottle.py:38: DeprecationWarning: 'cgi' is 
> deprecated and slated for removal in Python 3.13
> import base64, cgi, email.utils, functools, hmac, itertools, mimetypes,\
> 
> conda_package_streaming/package_streaming.py:19
>   
> /<>/.pybuild/cpython3_3.11/build/conda_package_streaming/package_streaming.py:19:
>  UserWarning: zstandard could not be imported. Running without .conda support.
> warnings.warn("zstandard could not be imported. Running without .conda 
> support.")
> 
> -- Docs: https://docs.pytest.org/en/stable/how-to/capture-warnings.html
> 
> -- coverage: platform linux, python 3.11.2-final-0 ---
> Name   Stmts   Miss  Cover
> --
> conda_package_streaming/__init__.py1  0   100%
> conda_package_streaming/exceptions.py  9  456%
> conda_package_streaming/extract.py42 3224%
> conda_package_streaming/lazy_wheel.py131 9131%
> conda_package_streaming/package_streaming.py  47 2547%
> conda_package_streaming/s3.py 39 1854%
> conda_package_streaming/transmute.py  52 4415%
> conda_package_streaming/url.py39 2536%
> --
> TOTAL36023934%
> 
> === short test summary info 
> 
> ERROR tests/test_transmute.py
>  Interrupted: 1 error during collection 
> 
> = 2 warnings, 1 error in 0.37s 
> =
> E: pybuild pybuild:388: test: plugin pyproject 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/16/conda-package-streaming_0.7.0-4_unstable.log

All

Bug#1031473: freebayes: FTBFS: Variant.h:36:10: fatal error: wavefront/wfa.hpp: No such file or directory

[Lucas Nussbaum]

Source: freebayes
Version: 1.3.6-2
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20230216 ftbfs-bookworm

Hi,

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


Relevant part (hopefully):
> c++ -Ilibfreebayes_common.a.p -I. -I.. -I../src -I../ttmath 
> -I/usr/include/vcflib -I/usr/include/smithwaterman -I/usr/include/fastahack 
> -I/usr/include/SeqLib -I/usr/include/jsoncpp -fdiagnostics-color=always 
> -D_FILE_OFFSET_BITS=64 -Wall -Winvalid-pch -std=c++14 -g -O2 
> -ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat 
> -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -fPIC -pthread 
> -fpermissive -Wno-reorder -Wno-sign-compare -Wno-unused-variable 
> -Wno-unused-but-set-variable -MD -MQ 
> libfreebayes_common.a.p/src_DataLikelihood.cpp.o -MF 
> libfreebayes_common.a.p/src_DataLikelihood.cpp.o.d -o 
> libfreebayes_common.a.p/src_DataLikelihood.cpp.o -c ../src/DataLikelihood.cpp
> In file included from ../src/AlleleParser.h:32,
>  from ../src/DataLikelihood.h:20,
>  from ../src/DataLikelihood.cpp:1:
> /usr/include/vcflib/Variant.h:36:10: fatal error: wavefront/wfa.hpp: No such 
> file or directory
>36 | #include "wavefront/wfa.hpp"
>   |  ^~~
> compilation terminated.
> [2/27] c++ -Ilibfreebayes_common.a.p -I. -I.. -I../src -I../ttmath 
> -I/usr/include/vcflib -I/usr/include/smithwaterman -I/usr/include/fastahack 
> -I/usr/include/SeqLib -I/usr/include/jsoncpp -fdiagnostics-color=always 
> -D_FILE_OFFSET_BITS=64 -Wall -Winvalid-pch -std=c++14 -g -O2 
> -ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat 
> -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -fPIC -pthread 
> -fpermissive -Wno-reorder -Wno-sign-compare -Wno-unused-variable 
> -Wno-unused-but-set-variable -MD -MQ 
> libfreebayes_common.a.p/src_AlleleParser.cpp.o -MF 
> libfreebayes_common.a.p/src_AlleleParser.cpp.o.d -o 
> libfreebayes_common.a.p/src_AlleleParser.cpp.o -c ../src/AlleleParser.cpp
> FAILED: libfreebayes_common.a.p/src_AlleleParser.cpp.o 
> c++ -Ilibfreebayes_common.a.p -I. -I.. -I../src -I../ttmath 
> -I/usr/include/vcflib -I/usr/include/smithwaterman -I/usr/include/fastahack 
> -I/usr/include/SeqLib -I/usr/include/jsoncpp -fdiagnostics-color=always 
> -D_FILE_OFFSET_BITS=64 -Wall -Winvalid-pch -std=c++14 -g -O2 
> -ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat 
> -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -fPIC -pthread 
> -fpermissive -Wno-reorder -Wno-sign-compare -Wno-unused-variable 
> -Wno-unused-but-set-variable -MD -MQ 
> libfreebayes_common.a.p/src_AlleleParser.cpp.o -MF 
> libfreebayes_common.a.p/src_AlleleParser.cpp.o.d -o 
> libfreebayes_common.a.p/src_AlleleParser.cpp.o -c ../src/AlleleParser.cpp
> In file included from ../src/AlleleParser.h:32,
>  from ../src/AlleleParser.cpp:1:
> /usr/include/vcflib/Variant.h:36:10: fatal error: wavefront/wfa.hpp: No such 
> file or directory
>36 | #include "wavefront/wfa.hpp"
>   |  ^~~
> compilation terminated.
> [3/27] c++ -Ilibfreebayes_common.a.p -I. -I.. -I../src -I../ttmath 
> -I/usr/include/vcflib -I/usr/include/smithwaterman -I/usr/include/fastahack 
> -I/usr/include/SeqLib -I/usr/include/jsoncpp -fdiagnostics-color=always 
> -D_FILE_OFFSET_BITS=64 -Wall -Winvalid-pch -std=c++14 -g -O2 
> -ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat 
> -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -fPIC -pthread 
> -fpermissive -Wno-reorder -Wno-sign-compare -Wno-unused-variable 
> -Wno-unused-but-set-variable -MD -MQ 
> libfreebayes_common.a.p/src_Contamination.cpp.o -MF 
> libfreebayes_common.a.p/src_Contamination.cpp.o.d -o 
> libfreebayes_common.a.p/src_Contamination.cpp.o -c ../src/Contamination.cpp
> [4/27] c++ -Ilibfreebayes_common.a.p -I. -I.. -I../src -I../ttmath 
> -I/usr/include/vcflib -I/usr/include/smithwaterman -I/usr/include/fastahack 
> -I/usr/include/SeqLib -I/usr/include/jsoncpp -fdiagnostics-color=always 
> -D_FILE_OFFSET_BITS=64 -Wall -Winvalid-pch -std=c++14 -g -O2 
> -ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat 
> -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -fPIC -pthread 
> -fpermissive -Wno-reorder -Wno-sign-compare -Wno-unused-variable 
> -Wno-unused-but-set-variable -MD -MQ libfreebayes_common.a.p/src_Bias.cpp.o 
> -MF libfreebayes_common.a.p/src_Bias.cpp.o.d -o 
> libfreebayes_common.a.p/src_Bias.cpp.o -c ../src/Bias.cpp
> [5/27] c++ -Ilibfreebayes_common.a.p -I. -I.. -I../src -I../ttmath 
> -I/usr/include/vcflib -I/usr/include/smithwaterman -I/usr/include/fastahack 
> -I/usr/include/SeqLib -I/usr/includ

Bug#1031472: ruby-omniauth-facebook: FTBFS: ERROR: Test "ruby3.1" failed.

[Lucas Nussbaum]

Source: ruby-omniauth-facebook
Version: 4.0.0-2.1
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20230216 ftbfs-bookworm

Hi,

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


Relevant part (hopefully):
> /usr/bin/ruby3.1 /usr/bin/gem2deb-test-runner
> 
> ┌──┐
> │ Checking Rubygems dependency resolution on ruby3.1  
>  │
> └──┘
> 
> GEM_PATH=/<>/debian/ruby-omniauth-facebook/usr/share/rubygems-integration/all:/var/lib/gems/3.1.0:/usr/local/lib/ruby/gems/3.1.0:/usr/lib/ruby/gems/3.1.0:/usr/lib/x86_64-linux-gnu/ruby/gems/3.1.0:/usr/share/rubygems-integration/3.1.0:/usr/share/rubygems-integration/all:/usr/lib/x86_64-linux-gnu/rubygems-integration/3.1.0
>  ruby3.1 -e gem\ \"omniauth-facebook\"
> 
> ┌──┐
> │ Run tests for ruby3.1 from debian/ruby-tests.rb 
>  │
> └──┘
> 
> RUBYLIB=/<>/debian/ruby-omniauth-facebook/usr/lib/ruby/vendor_ruby:.
>  
> GEM_PATH=/<>/debian/ruby-omniauth-facebook/usr/share/rubygems-integration/all:/var/lib/gems/3.1.0:/usr/local/lib/ruby/gems/3.1.0:/usr/lib/ruby/gems/3.1.0:/usr/lib/x86_64-linux-gnu/ruby/gems/3.1.0:/usr/share/rubygems-integration/3.1.0:/usr/share/rubygems-integration/all:/usr/lib/x86_64-linux-gnu/rubygems-integration/3.1.0
>  ruby3.1 debian/ruby-tests.rb
> mv example/Gemfile.lock example/.gem2deb.Gemfile.lock
> Mocha deprecation warning at 
> :160:in
>  `require': Require 'mocha/test_unit', 'mocha/minitest' or 'mocha/api' 
> instead of 'mocha/setup'.
> Run options: --seed 19466
> 
> # Running:
> 
> EE...E..DEPRECATED: Use assert_nil if expecting nil 
> from /<>/test/strategy_test.rb:455. This will fail in Minitest 6.
> .EE.E
> 
> Finished in 0.091243s, 800.0599 runs/s, 1183.6503 assertions/s.
> 
>   1) Error:
> SignedRequestTests::CookiePresentTest#test_parses_the_access_code_out_from_the_cookie:
> NameError: uninitialized constant SignedRequestHelpers::MultiJson
> 
> encoded_payload = base64_encode_url(MultiJson.encode(payload))
> ^
> Did you mean?  MultiXml
> /<>/test/strategy_test.rb:396:in `signed_request'
> /<>/test/strategy_test.rb:435:in `setup'
> 
>   2) Error:
> SignedRequestTests::CookiePresentTest#test_throws_an_error_if_the_algorithm_is_unknown:
> NameError: uninitialized constant SignedRequestHelpers::MultiJson
> 
> encoded_payload = base64_encode_url(MultiJson.encode(payload))
> ^
> Did you mean?  MultiXml
> /<>/test/strategy_test.rb:396:in `signed_request'
> /<>/test/strategy_test.rb:435:in `setup'
> 
>   3) Error:
> SignedRequestTests::MissingCodeInCookieRequestTest#test_calls_fail!_when_a_code_is_not_included_in_the_cookie:
> NameError: uninitialized constant SignedRequestHelpers::MultiJson
> 
> encoded_payload = base64_encode_url(MultiJson.encode(payload))
> ^
> Did you mean?  MultiXml
> /<>/test/strategy_test.rb:396:in `signed_request'
> /<>/test/strategy_test.rb:481:in `setup'
> 
>   4) Error:
> SignedRequestTest#test_signed_request_parse:
> NameError: uninitialized constant SignedRequestTest::MultiJson
> 
> @expected_payload = MultiJson.decode(fixture('payload.json'))
> ^
> Did you mean?  MultiXml
> /<>/test/signed_request_test.rb:8:in `setup'
> 
>   5) Error:
> SignedRequestTest#test_signed_request_payload:
> NameError: uninitialized constant SignedRequestTest::MultiJson
> 
> @expected_payload = MultiJson.decode(fixture('payload.json'))
> ^
> Did you mean?  MultiXml
> /<>/test/signed_request_test.rb:8:in `setup'
> 
>   6) Error:
> SignedRequestTests::UnknownAlgorithmInCookieRequestTest#test_calls_fail!_when_an_algorithm_is_unknown:
> NameError: uninitialized constant SignedRequestHelpers::MultiJson
> 
> encoded_payload = base64_encode_url(MultiJson.encode(payload))
> ^
> Did you mean?  MultiXml
> /<>/test/strategy_test.rb:396:in `signed_request'
> /<>/test/strategy_test.rb:500:in `setup'
> 
> 73 runs, 108 assertions, 0 failures, 6 errors, 0 skips
> mv example/.gem2deb.

Bug#1031469: botch: FTBFS: make[2]: *** [Makefile:339: test-python] Error 1

[Lucas Nussbaum]

Source: botch
Version: 0.24-1
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20230216 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 '/<>'
> # FIXME: add more tests
> #./tests.py
> #OCAMLPATH=/<>/dose/_build ocamlbuild -classic-display 
> -use-ocamlfind -cflags "-w +a-4-9-24" tests.native
> #./tests.native
> pyflakes3 tools/*.py
> # E402 is triggered by the sys.path.append() statement in front of import of 
> utils
> # see https://github.com/PyCQA/pycodestyle/issues/264
> # W503 is not PEP8 compliant
> # E203 is not PEP8 compliant
> pycodestyle --max-line-length=88 --ignore=E402,E203,W503 tools/*.py
> black --check tools/*.py
> would reformat tools/packages-diff.py
> 
> Oh no!   
> 1 file would be reformatted, 38 files would be left unchanged.
> make[2]: *** [Makefile:339: test-python] Error 1


The full build log is available from:
http://qa-logs.debian.net/2023/02/16/botch_0.24-1_unstable.log

All bugs filed during this archive rebuild are listed at:
https://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=ftbfs-20230216;users=lu...@debian.org
or:
https://udd.debian.org/bugs/?release=na=ign=7=7=only=ftbfs-20230216=lu...@debian.org=1=1=1=1#results

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

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

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

Bug#1031471: guestfs-tools: FTBFS: make[5]: *** [Makefile:1073: test-suite.log] Error 1

[Lucas Nussbaum]

Source: guestfs-tools
Version: 1.48.3-1
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20230216 ftbfs-bookworm

Hi,

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


Relevant part (hopefully):
> make[5]: Entering directory '/<>/resize'
> SKIP: rhbz1285847.sh
> PASS: test-virt-resize-docs.sh
> FAIL: test-virt-resize.pl
> 
> Testsuite summary for guestfs-tools 1.48.3
> 
> # TOTAL: 3
> # PASS:  1
> # SKIP:  1
> # XFAIL: 0
> # FAIL:  1
> # XPASS: 0
> # ERROR: 0
> 
> See resize/test-suite.log
> 
> make[5]: *** [Makefile:1073: test-suite.log] Error 1


The full build log is available from:
http://qa-logs.debian.net/2023/02/16/guestfs-tools_1.48.3-1_unstable.log

All bugs filed during this archive rebuild are listed at:
https://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=ftbfs-20230216;users=lu...@debian.org
or:
https://udd.debian.org/bugs/?release=na=ign=7=7=only=ftbfs-20230216=lu...@debian.org=1=1=1=1#results

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

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

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

Bug#1031470: jquery-i18n-properties: FTBFS: make[1]: *** [debian/rules:15: override_dh_auto_build] Error 254

[Lucas Nussbaum]

Source: jquery-i18n-properties
Version: 1.2.7+dfsg1-4
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20230216 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 '/<>'
> closure-compiler --js jquery.i18n.properties.js --js_output_file 
> jquery.i18n.properties-min.js
> java.util.MissingResourceException: Can't find bundle for base name 
> com.google.javascript.rhino.head.resources.Messages, locale en
>   at 
> java.base/java.util.ResourceBundle.throwMissingResourceException(ResourceBundle.java:2045)
>   at 
> java.base/java.util.ResourceBundle.getBundleImpl(ResourceBundle.java:1683)
>   at 
> java.base/java.util.ResourceBundle.getBundleImpl(ResourceBundle.java:1586)
>   at 
> java.base/java.util.ResourceBundle.getBundleImpl(ResourceBundle.java:1549)
>   at java.base/java.util.ResourceBundle.getBundle(ResourceBundle.java:932)
>   at 
> com.google.javascript.rhino.head.ScriptRuntime$DefaultMessageProvider.getMessage(ScriptRuntime.java:4521)
>   at 
> com.google.javascript.rhino.head.ScriptRuntime.getMessage(ScriptRuntime.java:4501)
>   at 
> com.google.javascript.rhino.head.ScriptRuntime.getMessage0(ScriptRuntime.java:4446)
>   at 
> com.google.javascript.jscomp.RhinoErrorReporter.(RhinoErrorReporter.java:84)
>   at 
> com.google.javascript.jscomp.RhinoErrorReporter.(RhinoErrorReporter.java:32)
>   at 
> com.google.javascript.jscomp.RhinoErrorReporter$OldRhinoErrorReporter.(RhinoErrorReporter.java:162)
>   at 
> com.google.javascript.jscomp.RhinoErrorReporter$OldRhinoErrorReporter.(RhinoErrorReporter.java:158)
>   at 
> com.google.javascript.jscomp.RhinoErrorReporter.forOldRhino(RhinoErrorReporter.java:119)
>   at com.google.javascript.jscomp.Compiler.(Compiler.java:176)
>   at 
> com.google.javascript.jscomp.CommandLineRunner.createCompiler(CommandLineRunner.java:858)
>   at 
> com.google.javascript.jscomp.AbstractCommandLineRunner.doRun(AbstractCommandLineRunner.java:741)
>   at 
> com.google.javascript.jscomp.AbstractCommandLineRunner.run(AbstractCommandLineRunner.java:380)
>   at 
> com.google.javascript.jscomp.CommandLineRunner.main(CommandLineRunner.java:980)
> make[1]: *** [debian/rules:15: override_dh_auto_build] Error 254


The full build log is available from:
http://qa-logs.debian.net/2023/02/16/jquery-i18n-properties_1.2.7+dfsg1-4_unstable.log

All bugs filed during this archive rebuild are listed at:
https://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=ftbfs-20230216;users=lu...@debian.org
or:
https://udd.debian.org/bugs/?release=na=ign=7=7=only=ftbfs-20230216=lu...@debian.org=1=1=1=1#results

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

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

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

Bug#1031468: ruby-rubydns: FTBFS: ERROR: Test "ruby3.1" failed: /usr/lib/ruby/vendor_ruby/rubygems/specification.rb:1413:in `rescue in block in activate_dependencies': Could not find 'celluloid' (= 0.

[Lucas Nussbaum]

Source: ruby-rubydns
Version: 1.0.3-3
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20230216 ftbfs-bookworm

Hi,

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


Relevant part (hopefully):
> /usr/lib/ruby/vendor_ruby/rubygems/specification.rb:1413:in `rescue in block 
> in activate_dependencies': Could not find 'celluloid' (= 0.16.0) among 111 
> total gem(s) (Gem::MissingSpecError)
> Checked in 
> 'GEM_PATH=/<>/debian/ruby-rubydns/usr/share/rubygems-integration/all:/var/lib/gems/3.1.0:/usr/local/lib/ruby/gems/3.1.0:/usr/lib/ruby/gems/3.1.0:/usr/lib/x86_64-linux-gnu/ruby/gems/3.1.0:/usr/share/rubygems-integration/3.1.0:/usr/share/rubygems-integration/all:/usr/lib/x86_64-linux-gnu/rubygems-integration/3.1.0'
>  at: 
> /<>/debian/ruby-rubydns/usr/share/rubygems-integration/all/specifications/rubydns-1.0.3.gemspec,
>  execute `gem env` for more information
>   from /usr/lib/ruby/vendor_ruby/rubygems/specification.rb:1410:in `block 
> in activate_dependencies'
>   from /usr/lib/ruby/vendor_ruby/rubygems/specification.rb:1399:in `each'
>   from /usr/lib/ruby/vendor_ruby/rubygems/specification.rb:1399:in 
> `activate_dependencies'
>   from /usr/lib/ruby/vendor_ruby/rubygems/specification.rb:1381:in 
> `activate'
>   from /usr/lib/ruby/vendor_ruby/rubygems/core_ext/kernel_gem.rb:68:in 
> `block in gem'
>   from /usr/lib/ruby/vendor_ruby/rubygems/core_ext/kernel_gem.rb:68:in 
> `synchronize'
>   from /usr/lib/ruby/vendor_ruby/rubygems/core_ext/kernel_gem.rb:68:in 
> `gem'
>   from -e:1:in `'
> /usr/lib/ruby/vendor_ruby/rubygems/dependency.rb:313:in `to_specs': Could not 
> find 'celluloid' (= 0.16.0) - did find: [celluloid-0.18.0] 
> (Gem::MissingSpecVersionError)
> Checked in 
> 'GEM_PATH=/<>/debian/ruby-rubydns/usr/share/rubygems-integration/all:/var/lib/gems/3.1.0:/usr/local/lib/ruby/gems/3.1.0:/usr/lib/ruby/gems/3.1.0:/usr/lib/x86_64-linux-gnu/ruby/gems/3.1.0:/usr/share/rubygems-integration/3.1.0:/usr/share/rubygems-integration/all:/usr/lib/x86_64-linux-gnu/rubygems-integration/3.1.0'
>  , execute `gem env` for more information
>   from /usr/lib/ruby/vendor_ruby/rubygems/specification.rb:1411:in `block 
> in activate_dependencies'
>   from /usr/lib/ruby/vendor_ruby/rubygems/specification.rb:1399:in `each'
>   from /usr/lib/ruby/vendor_ruby/rubygems/specification.rb:1399:in 
> `activate_dependencies'
>   from /usr/lib/ruby/vendor_ruby/rubygems/specification.rb:1381:in 
> `activate'
>   from /usr/lib/ruby/vendor_ruby/rubygems/core_ext/kernel_gem.rb:68:in 
> `block in gem'
>   from /usr/lib/ruby/vendor_ruby/rubygems/core_ext/kernel_gem.rb:68:in 
> `synchronize'
>   from /usr/lib/ruby/vendor_ruby/rubygems/core_ext/kernel_gem.rb:68:in 
> `gem'
>   from -e:1:in `'
> abbrev (default: 0.1.0)
> base64 (default: 0.1.1)
> benchmark (default: 0.2.0)
> bigdecimal (default: 3.1.1)
> bundler (2.3.15, default: 2.3.7)
> celluloid (0.18.0)
> celluloid-essentials (0.20.5)
> celluloid-extras (0.20.5)
> celluloid-fsm (0.20.5)
> celluloid-io (0.16.2)
> celluloid-pool (0.20.5)
> celluloid-supervision (0.20.5)
> cgi (default: 0.3.5)
> csv (default: 3.2.2)
> date (default: 3.2.2)
> debug (1.4.0)
> delegate (default: 0.2.0)
> did_you_mean (default: 1.6.1)
> diff-lcs (1.5.0)
> digest (default: 3.1.0)
> dotenv (2.4.0)
> drb (default: 2.1.0)
> english (default: 0.7.1)
> erb (default: 2.2.3)
> error_highlight (default: 0.3.0)
> etc (default: 1.3.0)
> fcntl (default: 1.0.1)
> fiddle (default: 1.1.0)
> fileutils (default: 1.6.0)
> find (default: 0.1.1)
> forwardable (default: 1.3.2)
> getoptlong (default: 0.1.1)
> hitimes (1.3.1)
> io-console (default: 0.5.11)
> io-nonblock (default: 0.1.0)
> io-wait (default: 0.2.1)
> ipaddr (default: 1.2.4)
> irb (default: 1.4.1)
> json (default: 2.6.1)
> logger (default: 1.5.0)
> matrix (0.4.2)
> minitest (5.15.0)
> mutex_m (default: 0.1.1)
> nenv (0.3.0)
> net-ftp (0.1.3)
> net-http (default: 0.2.0)
> net-imap (0.2.3)
> net-pop (0.1.1)
> net-protocol (default: 0.1.2)
> net-smtp (0.3.1)
> net-telnet (0.2.0)
> nio4r (2.5.8)
> nkf (default: 0.1.1)
> observer (default: 0.1.1)
> open-uri (default: 0.2.0)
> open3 (default: 0.1.1)
> openssl (default: 3.0.0)
> optparse (default: 0.2.0)
> ostruct (default: 0.5.2)
> pathname (default: 0.2.0)
> power_assert (2.0.1)
> pp (default: 0.3.0)
> prettyprint (default: 0.1.1)
> prime (0.1.2)
> pstore (default: 0.1.1)
> psych (default: 4.0.3)
> racc (default: 1.6.0)
> rake (13.0.6)
> rbs (2.1.0)
> rdoc (default: 6.4.0)
> readline (default: 0.0.3)
> readline-ext (defaul

Bug#1031467: eclipse-collections: FTBFS: build-dependency not installable: libeclipse-osgi-util-java

[Lucas Nussbaum]

Source: eclipse-collections
Version: 11.0.0.M3-3
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20230216 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: debhelper-compat (= 13), junit4, 
> libmaven-dependency-plugin-java, libmaven-jar-plugin-java, 
> libmaven-javadoc-plugin-java, libmaven-shade-plugin-java, 
> libmaven3-core-java, libslf4j-java, libstringtemplate4-java, libtycho-java, 
> maven-debian-helper, build-essential, fakeroot
> Filtered Build-Depends: debhelper-compat (= 13), junit4, 
> libmaven-dependency-plugin-java, libmaven-jar-plugin-java, 
> libmaven-javadoc-plugin-java, libmaven-shade-plugin-java, 
> libmaven3-core-java, libslf4j-java, libstringtemplate4-java, libtycho-java, 
> maven-debian-helper, build-essential, fakeroot
> dpkg-deb: building package 'sbuild-build-depends-main-dummy' in 
> '/<>/apt_archive/sbuild-build-depends-main-dummy.deb'.
> Ign:1 copy:/<>/apt_archive ./ InRelease
> Get:2 copy:/<>/apt_archive ./ Release [957 B]
> Ign:3 copy:/<>/apt_archive ./ Release.gpg
> Get:4 copy:/<>/apt_archive ./ Sources [451 B]
> Get:5 copy:/<>/apt_archive ./ Packages [533 B]
> Fetched 1941 B in 0s (145 kB/s)
> Reading package lists...
> Reading package lists...
> 
> Install main build dependencies (apt-based resolver)
> 
> 
> Installing build dependencies
> Reading package lists...
> Building dependency tree...
> Some packages could not be installed. This may mean that you have
> requested an impossible situation or if you are using the unstable
> distribution that some required packages have not yet been created
> or been moved out of Incoming.
> The following information may help to resolve the situation:
> 
> The following packages have unmet dependencies:
>  libtycho-java : Depends: libeclipse-osgi-util-java but it is not installable
> E: Unable to correct problems, you have held broken packages.
> apt-get failed.


The full build log is available from:
http://qa-logs.debian.net/2023/02/16/eclipse-collections_11.0.0.M3-3_unstable.log

All bugs filed during this archive rebuild are listed at:
https://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=ftbfs-20230216;users=lu...@debian.org
or:
https://udd.debian.org/bugs/?release=na=ign=7=7=only=ftbfs-20230216=lu...@debian.org=1=1=1=1#results

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

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

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

Bug#1031465: snippy: FTBFS: make[2]: *** [Makefile:32: S1/snps.tab] Error 2

[Lucas Nussbaum]

Source: snippy
Version: 4.6.0+dfsg-3
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20230216 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 '/<>/test'
> mkdir -p S1
> wgsim -S 1 \
>-h -r 0.005 -N 12000 -1 100 -2 100 -d 200 \
>example.fna S1/R2.fq S1/R1.fq > S1/dwgsim.tab
> [wgsim] seed = 1
> [wgsim_core] calculating the total length of the reference sequence...
> [wgsim_core] 3 sequences, total length: 317336
> mkdir -p S2
> wgsim -S 2 \
>-h -r 0.005 -N 12000 -1 100 -2 100 -d 200 \
>example.fna S2/R2.fq S2/R1.fq > S2/dwgsim.tab
> [wgsim] seed = 2
> [wgsim_core] calculating the total length of the reference sequence...
> [wgsim_core] 3 sequences, total length: 317336
> mkdir -p S3
> wgsim -S 3 \
>-h -r 0.005 -N 12000 -1 100 -2 100 -d 200 \
>example.fna S3/R2.fq S3/R1.fq > S3/dwgsim.tab
> [wgsim] seed = 3
> [wgsim_core] calculating the total length of the reference sequence...
> [wgsim_core] 3 sequences, total length: 317336
> mkdir -p S4
> wgsim -S 4 \
>-h -r 0.005 -N 12000 -1 100 -2 100 -d 200 \
>example.fna S4/R2.fq S4/R1.fq > S4/dwgsim.tab
> [wgsim] seed = 4
> [wgsim_core] calculating the total length of the reference sequence...
> [wgsim_core] 3 sequences, total length: 317336
> ../bin/snippy --cpus 2 --ram 2 --force --ref example.fna --outdir S1 --R1 
> S1/R1.fq --R2 S1/R2.fq
> [01:21:32] This is snippy 4.6.0
> [01:21:32] Written by Torsten Seemann
> [01:21:32] Obtained from https://github.com/tseemann/snippy
> [01:21:32] Detected operating system: linux
> [01:21:32] Enabling bundled linux tools.
> [01:21:32] Found bwa - /usr/bin/bwa
> [01:21:32] Found bcftools - /usr/bin/bcftools
> [01:21:32] Found samtools - /usr/bin/samtools
> [01:21:32] Found java - /usr/bin/java
> [01:21:32] Found snpEff - /usr/bin/snpEff
> [01:21:32] Found samclip - /usr/bin/samclip
> [01:21:32] Found seqtk - /usr/bin/seqtk
> [01:21:32] Found parallel - /usr/bin/parallel
> [01:21:32] Found freebayes - /usr/bin/freebayes
> [01:21:32] Found freebayes-parallel - 
> /usr/share/freebayes/scripts/freebayes-parallel
> [01:21:32] Found fasta_generate_regions.py - 
> /usr/share/freebayes/scripts/fasta_generate_regions.py
> [01:21:32] Found vcfstreamsort - /usr/bin/vcfstreamsort
> [01:21:32] Found vcfuniq - /usr/bin/vcfuniq
> [01:21:32] Found vcffirstheader - /usr/share/freebayes/scripts/vcffirstheader
> [01:21:32] Found gzip - /bin/gzip
> [01:21:32] Found vt - /usr/bin/vt
> [01:21:32] Found snippy-vcf_to_tab - /<>/bin/snippy-vcf_to_tab
> [01:21:32] Found snippy-vcf_report - /<>/bin/snippy-vcf_report
> [01:21:32] Checking version: samtools --version is >= 1.7 - ok, have 1.16
> [01:21:32] Checking version: bcftools --version is >= 1.7 - ok, have 1.16
> [01:21:32] Need freebayes --version >= 1.1 but you have 0 - please upgrade it.
> make[2]: *** [Makefile:32: S1/snps.tab] Error 2


The full build log is available from:
http://qa-logs.debian.net/2023/02/16/snippy_4.6.0+dfsg-3_unstable.log

All bugs filed during this archive rebuild are listed at:
https://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=ftbfs-20230216;users=lu...@debian.org
or:
https://udd.debian.org/bugs/?release=na=ign=7=7=only=ftbfs-20230216=lu...@debian.org=1=1=1=1#results

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

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

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

Bug#1031466: grml2usb: FTBFS: make[2]: *** [Makefile:44: codecheck] Error 1

[Lucas Nussbaum]

Source: grml2usb
Version: 0.19.1
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20230216 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 '/<>'
> flake8 grml2usb
> isort --check-only grml2usb
> black --check grml2usb
> would reformat grml2usb
> 
> Oh no!   
> 1 file would be reformatted.
> make[2]: *** [Makefile:44: codecheck] Error 1


The full build log is available from:
http://qa-logs.debian.net/2023/02/16/grml2usb_0.19.1_unstable.log

All bugs filed during this archive rebuild are listed at:
https://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=ftbfs-20230216;users=lu...@debian.org
or:
https://udd.debian.org/bugs/?release=na=ign=7=7=only=ftbfs-20230216=lu...@debian.org=1=1=1=1#results

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

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

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

Bug#1031462: libmemcached-libmemcached-perl: FTBFS: dh_auto_test: error: make -j8 test TEST_VERBOSE=1 returned exit code 2

[Lucas Nussbaum]

Source: libmemcached-libmemcached-perl
Version: 1.001801+dfsg-3
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20230216 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 '/<>'
> "/usr/bin/perl" -MExtUtils::Command::MM -e 'cp_nonempty' -- libmemcached.bs 
> blib/arch/auto/Memcached/libmemcached/libmemcached.bs 644
> PERL_DL_NONLAZY=1 "/usr/bin/perl" "-MExtUtils::Command::MM" "-MTest::Harness" 
> "-e" "undef *Test::Harness::Switches; test_harness(1, 'blib/lib', 
> 'blib/arch')" t/*.t
> # Testing Memcached::libmemcached 1.001801, Perl 5.036000, linux, 
> /usr/bin/perl
> 
> #   Failed test '1.001801 should be 1.0103 with two digits appended'
> #   at t/00-load.t line 27.
> #   '1.001801'
> # doesn't match '(?^:^1\.0103\d\d)'
> # Looks like you failed 1 test of 5.
> t/00-load.t .. 
> 1..5
> ok 1 - use Memcached::libmemcached;
> ok 2 - $Memcached::libmemcached::VERSION should be defined
> ok 3 - ::libmemcached::memcached_lib_version should be defined
> ok 4
> not ok 5 - 1.001801 should be 1.0103 with two digits appended
> Dubious, test returned 1 (wstat 256, 0x100)
> Failed 1/5 subtests 
> t/01-import.t  
> 1..16
> ok 1 - use Memcached::libmemcached;
> ok 2 - should not import func by default
> ok 3 - should import func on demand
> ok 4 - should not import MEMCACHED_SUCCESS by default
> ok 5 - should not import MEMCACHED_FAILURE by default
> ok 6 - should import MEMCACHED_SUCCESS on demand
> ok 7 - should not import MEMCACHED_FAILURE when importing MEMCACHED_SUCCESSi
> ok 8
> ok 9 - should not import MEMCACHED_HASH_MD5 by default
> ok 10 - should not import MEMCACHED_HASH_CRC by default
> ok 11 - should import MEMCACHED_HASH_MD5 by :memcached_hash tag
> ok 12 - should import MEMCACHED_HASH_CRC by :memcached_hash tag
> ok 13
> ok 14
> ok 15
> ok 16
> ok
> t/02-create.t  
> 1..5
> ok 1 - use Memcached::libmemcached;
> ok 2
> ok 3
> ok 4
> duplicate memcached_free
> ok 5
> ok
> t/02-subclass.t .. 
> 1..6
> ok 1 - use Memcached::libmemcached;
> ok 2
> ok 3
> ok 4
> ok 5
> ok 6
> ok
> t/03-servers.t ... 
> 1..10
> ok 1 - use Memcached::libmemcached;
> ok 2
> ok 3 - should have 0 elements
> ok 4
> ok 5 - should have 1 element
> ok 6
> ok 7 - should have 2 elements
> ok 8
> ok 9 - should have 3 elements
> ok 10
> ok
> t/04-strerror.t .. 
> 1..6
> ok 1
> ok 2
> ok 3 - rc should not be defined
> ok 4 - should be MEMCACHED_INVALID_ARGUMENTS integer in numeric context
> ok 5 - should be "INVALID ARGUMENTS" string in string context
> ok 6
> ok
> t/05-behavior.t .. 
> 1..6
> ok 1
> ok 2
> ok 3
> ok 4
> ok 5
> ok 6
> ok
> t/06-verbosity.t . 
> 1..1
> ok 1
> ok
> # Testing using memcached version 1.6.18
> t/10-set-get.t ... 
> 1..14
> ok 1 - should not exist yet and so should return undef
> ok 2
> ok 3
> ok 4
> ok 5
> ok 6 - flags should be unchanged
> ok 7
> ok 8
> ok 9
> ok 10
> ok 11 - utf8 arg length should not be altered
> ok 12 - utf8 arg should not be altered
> ok 13
> ok 14 - no inbuilt utf8 support # TODO support utf8
> # 
> ok
> t/11-set-get-by-key.t  
> 1..13
> memcached_get the not yet stored value
> ok 1 - should not exist yet and so should return undef
> ok 2
> ok 3
> ok 4
> ok 5 - flags should be unchanged
> ok 6
> ok 7
> ok 8
> ok 9
> ok 10 - utf8 arg length should not be altered
> ok 11 - utf8 arg should not be altered
> ok 12
> ok 13 - no inbuilt utf8 support # TODO support utf8
> # 
> ok
> t/12-set-get-binary.t  
> 1..5
> ok 1
> ok 2
> ok 3
> ok 4
> ok 5
> ok
> t/15-auto.t .. 
> 1..9
> memcached_increment the not yet stored value
> ok 1 - should not exist yet and so should return false
> ok 2 - should not exist yet and so should return false but defined
> memcached_set
> ok 3
> memcached_increment the just stored value
> ok 4 - should increment existing value
> ok 5
> ok 6 - should increment existing value
> ok 7
> ok 8 - should increment existing value
> ok 9
> ok
> t/20-set.t ... 
> 1..1
> ok 1
> ok
> t/21-set-by-key.t  
> 1..1
> ok 1
> ok
> t/25-get.t ... 
> 1..66
> ok 1
> ok 2
> ok 3
> ok 4
> ok

Bug#1031464: python-schema-salad: FTBFS: schema_salad/ref_resolver.py:845: error: Unused "type: ignore" comment

[Lucas Nussbaum]

Source: python-schema-salad
Version: 8.4.20230201194352-2
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20230216 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 plugin_pyproject:107: Building wheel for python3.11 with "build" 
> module
> I: pybuild base:240: python3.11 -m build --skip-dependency-check 
> --no-isolation --wheel --outdir 
> /<>/.pybuild/cpython3_3.11_schema-salad 
> * Building wheel...
> schema_salad/ref_resolver.py:845: error: Unused "type: ignore" comment
> elif isinstance(document, (list, dict)):  # type: 
> ignore[unreachable]
> 
> ^~~~
> 
> ERROR Backend subprocess exited when trying to invoke build_wheel
> E: pybuild pybuild:388: build: plugin pyproject failed with: exit code=1: 
> python3.11 -m build --skip-dependency-check --no-isolation --wheel --outdir 
> /<>/.pybuild/cpython3_3.11_schema-salad 
> dh_auto_build: error: pybuild --build -i python{version} -p 3.11 returned 
> exit code 13
> make[1]: *** [debian/rules:16: override_dh_auto_build] Error 25


The full build log is available from:
http://qa-logs.debian.net/2023/02/16/python-schema-salad_8.4.20230201194352-2_unstable.log

All bugs filed during this archive rebuild are listed at:
https://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=ftbfs-20230216;users=lu...@debian.org
or:
https://udd.debian.org/bugs/?release=na=ign=7=7=only=ftbfs-20230216=lu...@debian.org=1=1=1=1#results

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

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

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

Bug#1031463: golang-github-prometheus-exporter-toolkit: FTBFS: dh_auto_test: error: cd _build && go test -vet=off -v -p 8 github.com/prometheus/exporter-toolkit/web github.com/prometheus/exporter-tool

[Lucas Nussbaum]

Source: golang-github-prometheus-exporter-toolkit
Version: 0.8.2-1
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20230216 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 --buildsystem=golang --builddirectory=_build
>dh_update_autotools_config -O--buildsystem=golang -O--builddirectory=_build
>dh_autoreconf -O--buildsystem=golang -O--builddirectory=_build
>dh_auto_configure -O--buildsystem=golang -O--builddirectory=_build
>dh_auto_build -O--buildsystem=golang -O--builddirectory=_build
>   cd _build && go install -trimpath -v -p 8 
> github.com/prometheus/exporter-toolkit/web 
> github.com/prometheus/exporter-toolkit/web/kingpinflag
> internal/goarch
> internal/goos
> internal/unsafeheader
> internal/goexperiment
> internal/race
> internal/cpu
> runtime/internal/syscall
> runtime/internal/atomic
> sync/atomic
> unicode
> unicode/utf8
> internal/abi
> runtime/internal/math
> runtime/internal/sys
> container/list
> internal/itoa
> internal/bytealg
> math/bits
> crypto/internal/subtle
> crypto/subtle
> crypto/internal/boring/sig
> unicode/utf16
> vendor/golang.org/x/crypto/cryptobyte/asn1
> internal/nettrace
> vendor/golang.org/x/crypto/internal/subtle
> encoding
> math
> google.golang.org/protobuf/internal/flags
> google.golang.org/protobuf/internal/set
> runtime
> runtime/metrics
> sync
> internal/reflectlite
> internal/testlog
> math/rand
> internal/singleflight
> google.golang.org/protobuf/internal/pragma
> runtime/cgo
> errors
> sort
> io
> internal/oserror
> strconv
> path
> internal/safefilepath
> crypto/internal/nistec/fiat
> syscall
> vendor/golang.org/x/net/dns/dnsmessage
> github.com/beorn7/perks/quantile
> hash
> bytes
> strings
> crypto/internal/randutil
> hash/crc32
> vendor/golang.org/x/text/transform
> hash/fnv
> bufio
> crypto
> reflect
> crypto/rc4
> regexp/syntax
> net/http/internal/ascii
> github.com/prometheus/common/internal/bitbucket.org/ww/goautoneg
> html
> text/tabwriter
> golang.org/x/text/transform
> golang.org/x/crypto/blowfish
> internal/syscall/execenv
> internal/syscall/unix
> time
> regexp
> context
> io/fs
> github.com/jpillora/backoff
> internal/poll
> embed
> os
> internal/fmtsort
> encoding/binary
> crypto/cipher
> crypto/internal/edwards25519/field
> crypto/internal/nistec
> crypto/md5
> encoding/base64
> vendor/golang.org/x/crypto/internal/poly1305
> vendor/golang.org/x/crypto/curve25519/internal/field
> encoding/pem
> fmt
> internal/godebug
> internal/intern
> path/filepath
> crypto/internal/boring
> crypto/des
> crypto/internal/edwards25519
> vendor/golang.org/x/crypto/chacha20
> crypto/aes
> crypto/sha512
> crypto/hmac
> crypto/sha1
> crypto/sha256
> net/netip
> io/ioutil
> vendor/golang.org/x/sys/cpu
> vendor/golang.org/x/crypto/hkdf
> github.com/cespare/xxhash
> google.golang.org/protobuf/internal/detrand
> github.com/prometheus/procfs/internal/util
> golang.org/x/sys/unix
> internal/lazyregexp
> vendor/golang.org/x/crypto/chacha20poly1305
> net/url
> encoding/hex
> math/big
> vendor/golang.org/x/crypto/curve25519
> encoding/json
> github.com/go-logfmt/logfmt
> log
> net
> compress/flate
> vendor/golang.org/x/text/unicode/bidi
> vendor/golang.org/x/text/unicode/norm
> vendor/golang.org/x/net/http2/hpack
> mime
> compress/gzip
> github.com/go-kit/log
> vendor/golang.org/x/text/secure/bidirule
> mime/quotedprintable
> net/http/internal
> github.com/golang/protobuf/proto
> github.com/prometheus/common/model
> google.golang.org/protobuf/internal/errors
> github.com/go-kit/log/level
> google.golang.org/protobuf/encoding/protowire
> vendor/golang.org/x/net/idna
> crypto/elliptic
> crypto/internal/boring/bbig
> encoding/asn1
> crypto/rand
> crypto/dsa
> google.golang.org/protobuf/reflect/protoreflect
> crypto/ed25519
> crypto/rsa
> go/token
> google.golang.org/protobuf/internal/version
> github.com/prometheus/procfs/internal/fs
> runtime/debug
> golang.org/x/net/internal/timeseries
> text/template/parse
> vendor/golang.org/x/crypto/cryptobyte
> crypto/x509/pkix
> golang.org/x/text/unicode/bidi
> golang.org/x/text/unicode/norm
> google.golang.org/protobuf/internal/descfmt
> google.golang.org/protobuf/internal/descopts
> google.golang.org/protobuf/internal/strs
> crypto/ecdsa
> google.golang.org/protobuf/internal/encoding/messageset
> google.golang.org/protobuf/internal/encoding/text
&

Bug#1031460: enlighten: FTBFS: AssertionError: '1.00[31 chars]0.00 s/B | 128.00 KiB | 896.00 KiB | 512.00 K[105 chars] s/B' != '1.00[31 chars]0.00 s/B | 128.00 KiB | 896.00 KiB | 512.00 Ki[101 chars]

[Lucas Nussbaum]

Source: enlighten
Version: 1.11.1-1
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20230216 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/build/enlighten
> copying enlighten/__init__.py -> 
> /<>/.pybuild/cpython3_3.11/build/enlighten
> copying enlighten/counter.py -> 
> /<>/.pybuild/cpython3_3.11/build/enlighten
> copying enlighten/manager.py -> 
> /<>/.pybuild/cpython3_3.11/build/enlighten
> copying enlighten/_counter.py -> 
> /<>/.pybuild/cpython3_3.11/build/enlighten
> copying enlighten/_basemanager.py -> 
> /<>/.pybuild/cpython3_3.11/build/enlighten
> copying enlighten/_statusbar.py -> 
> /<>/.pybuild/cpython3_3.11/build/enlighten
> copying enlighten/_basecounter.py -> 
> /<>/.pybuild/cpython3_3.11/build/enlighten
> copying enlighten/_util.py -> 
> /<>/.pybuild/cpython3_3.11/build/enlighten
> copying enlighten/_notebook_manager.py -> 
> /<>/.pybuild/cpython3_3.11/build/enlighten
> copying enlighten/_manager.py -> 
> /<>/.pybuild/cpython3_3.11/build/enlighten
> PYTHONPATH=. python3 -m sphinx -N -bhtml doc/ build/html # HTML generator
> Running Sphinx v5.3.0
> Initializing Spelling Checker 7.7.0
> making output directory... done
> loading intersphinx inventory from https://docs.python.org/3/objects.inv...
> loading intersphinx inventory from 
> https://prefixed.readthedocs.io/en/stable/objects.inv...
> WARNING: failed to reach any of the inventories with the following issues:
> intersphinx inventory 'https://docs.python.org/3/objects.inv' not fetchable 
> due to : 
> HTTPSConnectionPool(host='docs.python.org', port=443): Max retries exceeded 
> with url: /3/objects.inv (Caused by ProxyError('Cannot connect to proxy.', 
> NewConnectionError(' 0x7f8203179b50>: Failed to establish a new connection: [Errno 111] Connection 
> refused')))
> WARNING: failed to reach any of the inventories with the following issues:
> intersphinx inventory 'https://prefixed.readthedocs.io/en/stable/objects.inv' 
> not fetchable due to : 
> HTTPSConnectionPool(host='prefixed.readthedocs.io', port=443): Max retries 
> exceeded with url: /en/stable/objects.inv (Caused by ProxyError('Cannot 
> connect to proxy.', NewConnectionError(' object at 0x7f820317a190>: Failed to establish a new connection: [Errno 111] 
> Connection refused')))
> building [mo]: targets for 0 po files that are out of date
> building [html]: targets for 6 source files that are out of date
> updating environment: [new config] 6 added, 0 changed, 0 removed
> reading sources... [ 16%] api
> direct use of the spelling directive is deprecated, replace ".. spelling::" 
> with ".. spelling:word-list::"
> reading sources... [ 33%] examples
> reading sources... [ 50%] faq
> direct use of the spelling directive is deprecated, replace ".. spelling::" 
> with ".. spelling:word-list::"
> reading sources... [ 66%] index
> reading sources... [ 83%] install
> reading sources... [100%] patterns
> 
> looking for now-outdated files... none found
> pickling environment... done
> checking consistency... done
> preparing documents... done
> writing output... [ 16%] api
> writing output... [ 33%] examples
> writing output... [ 50%] faq
> writing output... [ 66%] index
> writing output... [ 83%] install
> writing output... [100%] patterns
> 
> /<>/enlighten/_manager.py:docstring of 
> enlighten._manager.Manager:1: WARNING: term not in glossary: 'file object'
> /<>/enlighten/_manager.py:docstring of 
> enlighten._manager.Manager:1: WARNING: term not in glossary: 'class'
> /<>/enlighten/_manager.py:docstring of 
> enlighten._manager.Manager:2: WARNING: term not in glossary: 'class'
> /<>/enlighten/_manager.py:docstring of 
> enlighten._manager.Manager:7: WARNING: term not in glossary: 'file object'
> /<>/enlighten/_manager.py:docstring of 
> enlighten._manager.Manager:17: WARNING: term not in glossary: 'keyword 
> argument'
> /<>/enlighten/_manager.py:docstring of 
> enlighten._manager.Manager:30: WARNING: term not in glossary: 'file object'
> /<>/enlighten/_manager.py:docstring of 
> enlighten._manager

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

[Lucas Nussbaum]

Source: django-axes
Version: 5.39.0-1
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20230216 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 '/<>'
> PYBUILD_SYSTEM=custom \
> PYBUILD_TEST_ARGS="py.test-3" \
> PYTHONPATH=. dh_auto_test
>   pybuild --test --test-pytest -i python{version} -p 3.11
> I: pybuild base:240: py.test-3
> = test session starts 
> ==
> platform linux -- Python 3.11.2, pytest-7.2.1, pluggy-1.0.0+repack
> django: settings: tests.settings (from ini)
> rootdir: /<>, configfile: pyproject.toml, testpaths: tests
> plugins: django-4.5.2, cov-4.0.0
> collected 293 items
> 
> tests/test_admin.py ..   [  
> 0%]
> tests/test_attempts.py . [  
> 7%]
> tests/test_backends.py ..[  
> 8%]
> tests/test_checks.py .   [ 
> 11%]
> tests/test_decorators.py [ 
> 12%]
> tests/test_failures.py ..[ 
> 13%]
> tests/test_handlers.py . [ 
> 30%]
> .[ 
> 32%]
> tests/test_helpers.py .. [ 
> 49%]
> ..   [ 
> 56%]
> tests/test_logging.py ...F   [ 
> 60%]
> tests/test_login.py  [ 
> 78%]
> ...  [ 
> 93%]
> tests/test_management.py ... [ 
> 96%]
> tests/test_middleware.py [ 
> 98%]
> tests/test_models.py [ 
> 99%]
> tests/test_signals.py .  
> [100%]
> 
> === FAILURES 
> ===
> __ AccessLogTestCase.test_log_data_truncated 
> ___
> 
> self =  testMethod=test_log_data_truncated>
> 
> def test_log_data_truncated(self):
> """
> Test that get_query_str properly truncates data to the max_length 
> (default 1024).
> """
> 
> # An impossibly large post dict
> extra_data = {"a" * x: x for x in range(1024)}
> self.login(**extra_data)
> >   self.assertEqual(len(AccessAttempt.objects.latest("id").post_data), 
> > 1024)
> 
> tests/test_logging.py:80: 
> _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ 
> _ 
> /usr/lib/python3/dist-packages/django/db/models/manager.py:85: in 
> manager_method
> return getattr(self.get_queryset(), name)(*args, **kwargs)
> /usr/lib/python3/dist-packages/django/db/models/query.py:670: in latest
> return self.reverse()._earliest(*fields)
> /usr/lib/python3/dist-packages/django/db/models/query.py:664: in _earliest
> return obj.get()
> _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ 
> _ 
> 
> self = , args = (), kwargs = {}, clone = , limit = 
> 21
> num = 0
> 
> def get(self, *args, **kwargs):
> """
> Perform the query and return a single object matching the given
> keyword arguments.
> """
> if self.query.combinator and (args or kwargs):
> raise NotSupportedError(
> 'Calling QuerySet.get(...) with filters after %s() is not '
> 'supported.' % self.query.combinator
> )
> clone = self._chain() if self.query.combinator else 
> self.filter(*args, **kwargs)
> if self.query.can_filter() and not self.query.distinct_fields:
> clone = clone.order_by()
> limit = None
> if not clone.query.select_for_update or 
> connections[clone.db].features.supports_select_for_update_with_limit:
> limit = MAX_GET_RESULTS
> clone.query.set_limits(high=limit)
> num = len(clone)
> if num == 1:
> return clone._result_cache[0]
> if not num:
> >   raise self.model.DoesNotExist(
>

Bug#1031459: pcb-rnd: FTBFS: unsatisfiable build-dependencies: librnd4-dev, librnd4-cloud, librnd4-lib-gui

[Lucas Nussbaum]

Source: pcb-rnd
Version: 3.1.0-1
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20230216 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: debhelper (>= 11), librnd4-dev, librnd4-cloud, 
> librnd4-lib-gui, imagemagick, libgd-dev, libgtkglext1-dev, libmotif-dev, 
> libstroke0-dev, libxml2-dev, libgenht1-dev, libfungw-dev, build-essential, 
> fakeroot
> Filtered Build-Depends: debhelper (>= 11), librnd4-dev, librnd4-cloud, 
> librnd4-lib-gui, imagemagick, libgd-dev, libgtkglext1-dev, libmotif-dev, 
> libstroke0-dev, libxml2-dev, libgenht1-dev, libfungw-dev, build-essential, 
> fakeroot
> dpkg-deb: building package 'sbuild-build-depends-main-dummy' in 
> '/<>/apt_archive/sbuild-build-depends-main-dummy.deb'.
> Ign:1 copy:/<>/apt_archive ./ InRelease
> Get:2 copy:/<>/apt_archive ./ Release [957 B]
> Ign:3 copy:/<>/apt_archive ./ Release.gpg
> Get:4 copy:/<>/apt_archive ./ Sources [433 B]
> Get:5 copy:/<>/apt_archive ./ Packages [515 B]
> Fetched 1905 B in 0s (154 kB/s)
> Reading package lists...
> Reading package lists...
> 
> Install main build dependencies (apt-based resolver)
> 
> 
> Installing build dependencies
> Reading package lists...
> Building dependency tree...
> Some packages could not be installed. This may mean that you have
> requested an impossible situation or if you are using the unstable
> distribution that some required packages have not yet been created
> or been moved out of Incoming.
> The following information may help to resolve the situation:
> 
> The following packages have unmet dependencies:
>  sbuild-build-depends-main-dummy : Depends: librnd4-dev but it is not 
> installable
>Depends: librnd4-cloud but it is not 
> installable
>Depends: librnd4-lib-gui but it is not 
> installable
> E: Unable to correct problems, you have held broken packages.
> apt-get failed.


The full build log is available from:
http://qa-logs.debian.net/2023/02/16/pcb-rnd_3.1.0-1_unstable.log

All bugs filed during this archive rebuild are listed at:
https://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=ftbfs-20230216;users=lu...@debian.org
or:
https://udd.debian.org/bugs/?release=na=ign=7=7=only=ftbfs-20230216=lu...@debian.org=1=1=1=1#results

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

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

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

Bug#1031458: dojo: FTBFS: make[1]: *** [debian/rules:48: override_dh_auto_test] Error 1

[Lucas Nussbaum]

Source: dojo
Version: 1.17.2+dfsg1-2
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20230216 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 '/<>'
> cd util/shrinksafe/tests && ./runner.sh
> Exception in thread "main" java.util.MissingResourceException: Can't find 
> bundle for base name org.mozilla.javascript.resources.Messages, locale en
>   at 
> java.base/java.util.ResourceBundle.throwMissingResourceException(ResourceBundle.java:2045)
>   at 
> java.base/java.util.ResourceBundle.getBundleImpl(ResourceBundle.java:1683)
>   at 
> java.base/java.util.ResourceBundle.getBundleImpl(ResourceBundle.java:1586)
>   at 
> java.base/java.util.ResourceBundle.getBundleImpl(ResourceBundle.java:1549)
>   at java.base/java.util.ResourceBundle.getBundle(ResourceBundle.java:932)
>   at 
> org.mozilla.javascript.ScriptRuntime$DefaultMessageProvider.getMessage(ScriptRuntime.java:4521)
>   at 
> org.mozilla.javascript.ScriptRuntime.getMessageById(ScriptRuntime.java:4505)
>   at 
> org.mozilla.javascript.ScriptRuntime.notFoundError(ScriptRuntime.java:4631)
>   at 
> org.mozilla.javascript.ScriptRuntime.nameOrFunction(ScriptRuntime.java:2019)
>   at org.mozilla.javascript.ScriptRuntime.name(ScriptRuntime.java:1957)
>   at 
> org.mozilla.javascript.Interpreter.interpretLoop(Interpreter.java:1972)
>   at org.mozilla.javascript.Interpreter.interpret(Interpreter.java:1053)
>   at 
> org.mozilla.javascript.InterpretedFunction.call(InterpretedFunction.java:90)
>   at org.mozilla.javascript.optimizer.OptRuntime.callN(OptRuntime.java:52)
>   at 
> org.mozilla.javascript.gen.__dojo_dojo_js_1._c_anonymous_13(Unknown 
> Source)
>   at org.mozilla.javascript.gen.__dojo_dojo_js_1.call(Unknown Source)
>   at 
> org.mozilla.javascript.Interpreter.interpretLoop(Interpreter.java:1871)
>   at org.mozilla.javascript.Interpreter.interpret(Interpreter.java:1053)
>   at 
> org.mozilla.javascript.InterpretedFunction.call(InterpretedFunction.java:90)
>   at 
> org.mozilla.javascript.ScriptRuntime.applyOrCall(ScriptRuntime.java:2766)
>   at org.mozilla.javascript.BaseFunction.execIdCall(BaseFunction.java:327)
>   at 
> org.mozilla.javascript.IdFunctionObject.call(IdFunctionObject.java:100)
>   at org.mozilla.javascript.optimizer.OptRuntime.call2(OptRuntime.java:46)
>   at 
> org.mozilla.javascript.gen.__dojo_dojo_js_1._c_anonymous_68(Unknown 
> Source)
>   at org.mozilla.javascript.gen.__dojo_dojo_js_1.call(Unknown Source)
>   at 
> org.mozilla.javascript.optimizer.OptRuntime.callName(OptRuntime.java:59)
>   at 
> org.mozilla.javascript.gen.__dojo_dojo_js_1._c_anonymous_75(Unknown 
> Source)
>   at org.mozilla.javascript.gen.__dojo_dojo_js_1.call(Unknown Source)
>   at 
> org.mozilla.javascript.optimizer.OptRuntime.callName(OptRuntime.java:59)
>   at 
> org.mozilla.javascript.gen.__dojo_dojo_js_1._c_anonymous_75(Unknown 
> Source)
>   at org.mozilla.javascript.gen.__dojo_dojo_js_1.call(Unknown Source)
>   at 
> org.mozilla.javascript.optimizer.OptRuntime.callName(OptRuntime.java:59)
>   at 
> org.mozilla.javascript.gen.__dojo_dojo_js_1._c_anonymous_75(Unknown 
> Source)
>   at org.mozilla.javascript.gen.__dojo_dojo_js_1.call(Unknown Source)
>   at 
> org.mozilla.javascript.optimizer.OptRuntime.callName(OptRuntime.java:59)
>   at 
> org.mozilla.javascript.gen.__dojo_dojo_js_1._c_anonymous_45(Unknown 
> Source)
>   at org.mozilla.javascript.gen.__dojo_dojo_js_1.call(Unknown Source)
>   at 
> org.mozilla.javascript.optimizer.OptRuntime.callName0(OptRuntime.java:66)
>   at 
> org.mozilla.javascript.gen.__dojo_dojo_js_1._c_anonymous_76(Unknown 
> Source)
>   at org.mozilla.javascript.gen.__dojo_dojo_js_1.call(Unknown Source)
>   at 
> org.mozilla.javascript.optimizer.OptRuntime.callName(OptRuntime.java:59)
>   at 
> org.mozilla.javascript.gen.__dojo_dojo_js_1._c_anonymous_44(Unknown 
> Source)
>   at org.mozilla.javascript.gen.__dojo_dojo_js_1.call(Unknown Source)
>   at 
> org.mozilla.javascript.optimizer.OptRuntime.callName(OptRuntime.java:59)
>   at 
> org.mozilla.javascript.gen.__dojo_dojo_js_1._c_anonymous_12(Unknown 
> Source)
>   at org.mozilla.javascript.gen.__dojo_dojo_js_1.call(Unknown Source)
>   at 
> org.mozilla.javascript.optimizer.OptRuntime.callName(OptRuntime.java:59)
>   at 
> org.mozilla.javascript.ge

Bug#1031457: ruby-redis: FTBFS: ERROR: Test "ruby3.1" failed.

[Lucas Nussbaum]

Source: ruby-redis
Version: 4.8.0-1
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20230216 ftbfs-bookworm

Hi,

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


Relevant part (hopefully):
> /usr/bin/ruby3.1 /usr/bin/gem2deb-test-runner
> 
> ┌──┐
> │ Checking Rubygems dependency resolution on ruby3.1  
>  │
> └──┘
> 
> GEM_PATH=/<>/debian/ruby-redis/usr/share/rubygems-integration/all:/<>/debian/.debhelper/generated/_source/home/.local/share/gem/ruby/3.1.0:/var/lib/gems/3.1.0:/usr/local/lib/ruby/gems/3.1.0:/usr/lib/ruby/gems/3.1.0:/usr/lib/x86_64-linux-gnu/ruby/gems/3.1.0:/usr/share/rubygems-integration/3.1.0:/usr/share/rubygems-integration/all:/usr/lib/x86_64-linux-gnu/rubygems-integration/3.1.0
>  ruby3.1 -e gem\ \"redis\"
> 
> ┌──┐
> │ Run tests for ruby3.1 from debian/ruby-tests.rake   
>  │
> └──┘
> 
> RUBYLIB=. 
> GEM_PATH=/<>/debian/ruby-redis/usr/share/rubygems-integration/all:/<>/debian/.debhelper/generated/_source/home/.local/share/gem/ruby/3.1.0:/var/lib/gems/3.1.0:/usr/local/lib/ruby/gems/3.1.0:/usr/lib/ruby/gems/3.1.0:/usr/lib/x86_64-linux-gnu/ruby/gems/3.1.0:/usr/share/rubygems-integration/3.1.0:/usr/share/rubygems-integration/all:/usr/lib/x86_64-linux-gnu/rubygems-integration/3.1.0
>  ruby3.1 -S rake -f debian/ruby-tests.rake
> /<>/lib/redis/client.rb:398:in `rescue in establish_connection': 
> Error connecting to Redis on 127.0.0.1:7000 (Errno::ECONNREFUSED) 
> (Redis::CannotConnectError)
>   from /<>/lib/redis/client.rb:379:in `establish_connection'
>   from /<>/lib/redis/client.rb:115:in `block in connect'
>   from /<>/lib/redis/client.rb:344:in `with_reconnect'
>   from /<>/lib/redis/client.rb:114:in `connect'
>   from /<>/lib/redis/client.rb:417:in `ensure_connected'
>   from /<>/lib/redis/client.rb:269:in `block in process'
>   from /<>/lib/redis/client.rb:356:in `logging'
>   from /<>/lib/redis/client.rb:268:in `process'
>   from /<>/lib/redis/client.rb:161:in `call'
>   from /<>/lib/redis.rb:270:in `block in send_command'
>   from /<>/lib/redis.rb:269:in `synchronize'
>   from /<>/lib/redis.rb:269:in `send_command'
>   from /<>/lib/redis/commands/server.rb:68:in `flushall'
>   from /<>/test/support/cluster/orchestrator.rb:112:in 
> `block in flush_all_data'
>   from /<>/test/support/cluster/orchestrator.rb:110:in `each'
>   from /<>/test/support/cluster/orchestrator.rb:110:in 
> `flush_all_data'
>   from /<>/test/support/cluster/orchestrator.rb:26:in 
> `rebuild'
>   from bin/cluster_creator:10:in `'
> /usr/lib/ruby/3.1.0/socket.rb:1214:in `__connect_nonblock': Connection 
> refused - connect(2) for 127.0.0.1:7000 (Errno::ECONNREFUSED)
>   from /usr/lib/ruby/3.1.0/socket.rb:1214:in `connect_nonblock'
>   from /<>/lib/redis/connection/ruby.rb:163:in `rescue in 
> connect_addrinfo'
>   from /<>/lib/redis/connection/ruby.rb:157:in 
> `connect_addrinfo'
>   from /<>/lib/redis/connection/ruby.rb:196:in `block in 
> connect'
>   from /<>/lib/redis/connection/ruby.rb:194:in `each'
>   from /<>/lib/redis/connection/ruby.rb:194:in 
> `each_with_index'
>   from /<>/lib/redis/connection/ruby.rb:194:in `connect'
>   from /<>/lib/redis/connection/ruby.rb:308:in `connect'
>   from /<>/lib/redis/client.rb:385:in `establish_connection'
>   from /<>/lib/redis/client.rb:115:in `block in connect'
>   from /<>/lib/redis/client.rb:344:in `with_reconnect'
>   from /<>/lib/redis/client.rb:114:in `connect'
>   from /<>/lib/redis/client.rb:417:in `ensure_connected'
>   from /<>/lib/redis/client.rb:269:in `block in process'
>   from /<>/lib/redis/client.rb:356:in `logging'
>   from /<>/lib/redis/client.rb:268:in `process'
>   from /<>/lib/redis/client.rb:161:in `call'
>   from /<>/lib/redis.rb:270:in `block in send_command'
>   from /<>/lib/redis.rb:269:in `synchronize'
>   from /<>/lib/redis.rb:269:in `send_command'
>   from /<>/lib/redis/commands/server.rb:68:in `flushall'
>   from /<>/test/support/cluster/orchestrator.rb:112:in 
> `b

Bug#1031456: r-cran-shiny: FTBFS: make[1]: *** [debian/rules:28: override_dh_install] Error 254

[Lucas Nussbaum]

Source: r-cran-shiny
Version: 1.7.4+dfsg-1
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20230216 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_install
> find debian -name "LICENSE*" -delete
> rm -rf 
> /<>/debian/r-cran-shiny/usr/lib/R/site-library/shiny/www/shared/showdown/license.txt
> mkdir -p 
> /<>/debian/r-cran-shiny/usr/lib/R/site-library/shiny/www/shared/bootstrap/shim
> cp -a debian/missing-sources/respond/respond.min.js 
> /<>/debian/r-cran-shiny/usr/lib/R/site-library/shiny/www/shared/bootstrap/shim/
> mkdir -p 
> /<>/debian/r-cran-shiny/usr/lib/R/site-library/shiny/www/shared/strftime
> cp -a debian/missing-sources/strftime/strftime.min.js 
> /<>/debian/r-cran-shiny/usr/lib/R/site-library/shiny/www/shared/strftime
> # this fails: yui-compressor 
> debian/missing-sources/babel-polyfill/babel-polyfill.js > 
> /<>/debian/r-cran-shiny/usr/lib/R/site-library/shiny/www/shared/babel-polyfill.min.js
> # see https://lists.debian.org/debian-mentors/2016/11/msg00102.html
> cp -a debian/missing-sources/babel-polyfill/babel-polyfill.min.js 
> /<>/debian/r-cran-shiny/usr/lib/R/site-library/shiny/www/shared/babel-polyfill.min.js
> # see debian/README.source
> mkdir -p 
> /<>/debian/r-cran-shiny/usr/lib/R/site-library/shiny/www/shared/selectize/js/
> cp -a debian/missing-sources/selectize-0.12.1/selectize.min.shiny.js 
> /<>/debian/r-cran-shiny/usr/lib/R/site-library/shiny/www/shared/selectize/js/selectize.min.js
> # For some very strange reason a symlink leads to unexpected results in shiny 
> apps.
> # Thus a real copy of font-awesome.min.css from fonts-font-awesome package is 
> created.
> mkdir -p 
> /<>/debian/r-cran-shiny/usr/lib/R/site-library/shiny/www/shared/font-awesome/css/
> cp -a /usr/share/fonts-font-awesome/css/font-awesome.min.css 
> /<>/debian/r-cran-shiny/usr/lib/R/site-library/shiny/www/shared/font-awesome/css/
> # datepicker is only non-minimized.  Do the minimisation here
> mkdir -p 
> /<>/debian/r-cran-shiny/usr/lib/R/site-library/shiny/www/shared/datepicker/js
> closure-compiler  --charset 'utf-8' --js 
> /usr/share/javascript/bootstrap/files/js/bootstrap-datepicker.js 
> --js_output_file 
> /<>/debian/r-cran-shiny/usr/lib/R/site-library/shiny/www/shared/datepicker/js/bootstrap-datepicker.min.js
> java.util.MissingResourceException: Can't find bundle for base name 
> com.google.javascript.rhino.head.resources.Messages, locale en
>   at 
> java.base/java.util.ResourceBundle.throwMissingResourceException(ResourceBundle.java:2045)
>   at 
> java.base/java.util.ResourceBundle.getBundleImpl(ResourceBundle.java:1683)
>   at 
> java.base/java.util.ResourceBundle.getBundleImpl(ResourceBundle.java:1586)
>   at 
> java.base/java.util.ResourceBundle.getBundleImpl(ResourceBundle.java:1549)
>   at java.base/java.util.ResourceBundle.getBundle(ResourceBundle.java:932)
>   at 
> com.google.javascript.rhino.head.ScriptRuntime$DefaultMessageProvider.getMessage(ScriptRuntime.java:4521)
>   at 
> com.google.javascript.rhino.head.ScriptRuntime.getMessage(ScriptRuntime.java:4501)
>   at 
> com.google.javascript.rhino.head.ScriptRuntime.getMessage0(ScriptRuntime.java:4446)
>   at 
> com.google.javascript.jscomp.RhinoErrorReporter.(RhinoErrorReporter.java:84)
>   at 
> com.google.javascript.jscomp.RhinoErrorReporter.(RhinoErrorReporter.java:32)
>   at 
> com.google.javascript.jscomp.RhinoErrorReporter$OldRhinoErrorReporter.(RhinoErrorReporter.java:162)
>   at 
> com.google.javascript.jscomp.RhinoErrorReporter$OldRhinoErrorReporter.(RhinoErrorReporter.java:158)
>   at 
> com.google.javascript.jscomp.RhinoErrorReporter.forOldRhino(RhinoErrorReporter.java:119)
>   at com.google.javascript.jscomp.Compiler.(Compiler.java:176)
>   at 
> com.google.javascript.jscomp.CommandLineRunner.createCompiler(CommandLineRunner.java:858)
>   at 
> com.google.javascript.jscomp.AbstractCommandLineRunner.doRun(AbstractCommandLineRunner.java:741)
>   at 
> com.google.javascript.jscomp.AbstractCommandLineRunner.run(AbstractCommandLineRunner.java:380)
>   at 
> com.google.javascript.jscomp.CommandLineRunner.main(CommandLineRunner.java:980)
> make[1]: *** [debian/rules:28: override_dh_install] Error 254


The full build log is available from:
http://qa-logs.debian.net/2023/02/16/r-cran-shiny_1.7.4+dfsg-1_unstable.log

All bugs filed during this archive rebuild are listed at:
https://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=ftbfs-20230216;users=lu...@debian.org
o

Bug#1031455: charliecloud: FTBFS: config.h:38: error: "PACKAGE_VERSION" redefined [-Werror]

[Lucas Nussbaum]

Source: charliecloud
Version: 0.31-1
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20230216 ftbfs-bookworm

Hi,

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


Relevant part (hopefully):
> gcc -DHAVE_CONFIG_H -I.   -Wdate-time -D_FORTIFY_SOURCE=2  -g -O2 
> -ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat 
> -Werror=format-security -std=c99 -Wall -Werror -c -o ch-ssh.o ch-ssh.c
> rm -f ch-run-oci
> sed -E 's|%PYTHON_SHEBANG%|/usr/bin/env python3|' < ch-run-oci.py.in > 
> ch-run-oci
> chmod +rx,-w ch-run-oci  # respects umask
> rm -f ch-image
> sed -E 's|%PYTHON_SHEBANG%|/usr/bin/env python3|' < ch-image.py.in > ch-image
> chmod +rx,-w ch-image  # respects umask
> In file included from ch_fuse.c:33:
> config.h:38: error: "PACKAGE_VERSION" redefined [-Werror]
>38 | #define PACKAGE_VERSION "0.31"
>   | 
> In file included from /usr/include/fuse3/fuse_common.h:17,
>  from /usr/include/fuse3/fuse_lowlevel.h:25,
>  from /usr/include/squashfuse/ll.h:31,
>  from ch_fuse.c:31:
> /usr/include/fuse3/fuse_config.h:42: note: this is the location of the 
> previous definition
>42 | #define PACKAGE_VERSION "3.13.1"
>   | 
> cc1: all warnings being treated as errors
> make[3]: *** [Makefile:638: ch_run-ch_fuse.o] Error 1


The full build log is available from:
http://qa-logs.debian.net/2023/02/16/charliecloud_0.31-1_unstable.log

All bugs filed during this archive rebuild are listed at:
https://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=ftbfs-20230216;users=lu...@debian.org
or:
https://udd.debian.org/bugs/?release=na=ign=7=7=only=ftbfs-20230216=lu...@debian.org=1=1=1=1#results

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

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

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

Bug#1031453: sane-frontends: FTBFS: dh_install: error: missing files, aborting

[Lucas Nussbaum]

Source: sane-frontends
Version: 1.0.14-16
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20230216 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
>dh_update_autotools_config
>dh_autoreconf
> autoreconf: warning: autoconf input should be named 'configure.ac', not 
> 'configure.in'
> aclocal: warning: autoconf input should be named 'configure.ac', not 
> 'configure.in'
> acinclude.m4:13: warning: underquoted definition of AM_PATH_GTK
> acinclude.m4:13:   run info Automake 'Extending aclocal'
> acinclude.m4:13:   or see 
> https://www.gnu.org/software/automake/manual/automake.html#Extending-aclocal
> configure.in:3: warning: The macro `AC_CONFIG_HEADER' is obsolete.
> configure.in:3: You should run autoupdate.
> ./lib/autoconf/status.m4:719: AC_CONFIG_HEADER is expanded from...
> configure.in:3: the top level
> configure.in:53: warning: The macro `AC_AIX' is obsolete.
> configure.in:53: You should run autoupdate.
> ./lib/autoconf/specific.m4:540: AC_AIX is expanded from...
> configure.in:53: the top level
> configure.in:54: warning: The macro `AC_MINIX' is obsolete.
> configure.in:54: You should run autoupdate.
> ./lib/autoconf/specific.m4:545: AC_MINIX is expanded from...
> configure.in:54: the top level
> configure.in:55: warning: The macro `AC_ISC_POSIX' is obsolete.
> configure.in:55: You should run autoupdate.
> ./lib/autoconf/specific.m4:550: AC_ISC_POSIX is expanded from...
> configure.in:55: the top level
> configure.in:56: warning: 'AM_PROG_CC_STDC': this macro is obsolete.
> configure.in:56: You should simply use the 'AC_PROG_CC' macro instead.
> configure.in:56: Also, your code should no longer depend upon 
> 'am_cv_prog_cc_stdc',
> configure.in:56: but upon 'ac_cv_prog_cc_stdc'.
> ./lib/autoconf/general.m4:2434: AC_DIAGNOSE is expanded from...
> aclocal.m4:746: AM_PROG_CC_STDC is expanded from...
> configure.in:56: the top level
> configure.in:64: warning: The macro `ac_cv_prog_gcc' is obsolete.
> configure.in:64: You should run autoupdate.
> ./lib/autoconf/c.m4:440: ac_cv_prog_gcc is expanded from...
> configure.in:64: the top level
> configure.in:77: warning: The macro `AC_HEADER_STDC' is obsolete.
> configure.in:77: You should run autoupdate.
> ./lib/autoconf/headers.m4:704: AC_HEADER_STDC is expanded from...
> configure.in:77: the top level
> configure.in:83: warning: The macro `AC_TYPE_SIGNAL' is obsolete.
> configure.in:83: You should run autoupdate.
> ./lib/autoconf/types.m4:776: AC_TYPE_SIGNAL is expanded from...
> configure.in:83: the top level
> configure.in:138: warning: The macro `AC_TRY_RUN' is obsolete.
> configure.in:138: You should run autoupdate.
> ./lib/autoconf/general.m4:2997: AC_TRY_RUN is expanded from...
> aclocal.m4:207: AM_PATH_GTK_2_0 is expanded from...
> configure.in:138: the top level
> configure.in:138: warning: The macro `AC_TRY_LINK' is obsolete.
> configure.in:138: You should run autoupdate.
> ./lib/autoconf/general.m4:2920: AC_TRY_LINK is expanded from...
> aclocal.m4:207: AM_PATH_GTK_2_0 is expanded from...
> configure.in:138: the top level
> configure.in:150: warning: The macro `AC_TRY_RUN' is obsolete.
> configure.in:150: You should run autoupdate.
> ./lib/autoconf/general.m4:2997: AC_TRY_RUN is expanded from...
> acinclude.m4:13: AM_PATH_GTK is expanded from...
> configure.in:150: the top level
> configure.in:150: warning: The macro `AC_TRY_LINK' is obsolete.
> configure.in:150: You should run autoupdate.
> ./lib/autoconf/general.m4:2920: AC_TRY_LINK is expanded from...
> acinclude.m4:13: AM_PATH_GTK is expanded from...
> configure.in:150: the top level
> configure.in:154: warning: The macro `AC_TRY_RUN' is obsolete.
> configure.in:154: You should run autoupdate.
> ./lib/autoconf/general.m4:2997: AC_TRY_RUN is expanded from...
> acinclude.m4:185: AM_PATH_GIMP is expanded from...
> configure.in:154: the top level
> configure.in:154: warning: The macro `AC_TRY_LINK' is obsolete.
> configure.in:154: You should run autoupdate.
> ./lib/autoconf/general.m4:2920: AC_TRY_LINK is expanded from...
> acinclude.m4:185: AM_PATH_GIMP is expanded from...
> configure.in:154: the top level
> configure.in:161: warning: The macro `AC_TRY_RUN' is obsolete.
> configure.in:161: You should run autoupdate.
> ./lib/autoconf/general.m4:2997: AC_TRY_RUN is expanded from...
> aclocal.m4:22: AM_PATH_GIMP_2_0 is expanded from...
> configure.in:161: the top level
> configure.in:161: warning: The macro `AC_TRY_LINK' is obsolete.
> configure.in:161: You should run autoupdate.
> ./lib/autoconf/general.m4:2920: AC_TRY_LINK is expanded from...
> aclocal.m4:2

Bug#1031454: r-cran-pander: FTBFS: make[1]: *** [debian/rules:9: override_dh_auto_build] Error 254

[Lucas Nussbaum]

Source: r-cran-pander
Version: 0.6.5+dfsg-1
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20230216 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 '/<>'
> closure-compiler  --charset 'utf-8' --js 
> debian/missing-sources/jcaption/jcaption.js --js_output_file 
> debian/missing-sources/jcaption/jcaption.min.js
> java.util.MissingResourceException: Can't find bundle for base name 
> com.google.javascript.rhino.head.resources.Messages, locale en
>   at 
> java.base/java.util.ResourceBundle.throwMissingResourceException(ResourceBundle.java:2045)
>   at 
> java.base/java.util.ResourceBundle.getBundleImpl(ResourceBundle.java:1683)
>   at 
> java.base/java.util.ResourceBundle.getBundleImpl(ResourceBundle.java:1586)
>   at 
> java.base/java.util.ResourceBundle.getBundleImpl(ResourceBundle.java:1549)
>   at java.base/java.util.ResourceBundle.getBundle(ResourceBundle.java:932)
>   at 
> com.google.javascript.rhino.head.ScriptRuntime$DefaultMessageProvider.getMessage(ScriptRuntime.java:4521)
>   at 
> com.google.javascript.rhino.head.ScriptRuntime.getMessage(ScriptRuntime.java:4501)
>   at 
> com.google.javascript.rhino.head.ScriptRuntime.getMessage0(ScriptRuntime.java:4446)
>   at 
> com.google.javascript.jscomp.RhinoErrorReporter.(RhinoErrorReporter.java:84)
>   at 
> com.google.javascript.jscomp.RhinoErrorReporter.(RhinoErrorReporter.java:32)
>   at 
> com.google.javascript.jscomp.RhinoErrorReporter$OldRhinoErrorReporter.(RhinoErrorReporter.java:162)
>   at 
> com.google.javascript.jscomp.RhinoErrorReporter$OldRhinoErrorReporter.(RhinoErrorReporter.java:158)
>   at 
> com.google.javascript.jscomp.RhinoErrorReporter.forOldRhino(RhinoErrorReporter.java:119)
>   at com.google.javascript.jscomp.Compiler.(Compiler.java:176)
>   at 
> com.google.javascript.jscomp.CommandLineRunner.createCompiler(CommandLineRunner.java:858)
>   at 
> com.google.javascript.jscomp.AbstractCommandLineRunner.doRun(AbstractCommandLineRunner.java:741)
>   at 
> com.google.javascript.jscomp.AbstractCommandLineRunner.run(AbstractCommandLineRunner.java:380)
>   at 
> com.google.javascript.jscomp.CommandLineRunner.main(CommandLineRunner.java:980)
> make[1]: *** [debian/rules:9: override_dh_auto_build] Error 254


The full build log is available from:
http://qa-logs.debian.net/2023/02/16/r-cran-pander_0.6.5+dfsg-1_unstable.log

All bugs filed during this archive rebuild are listed at:
https://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=ftbfs-20230216;users=lu...@debian.org
or:
https://udd.debian.org/bugs/?release=na=ign=7=7=only=ftbfs-20230216=lu...@debian.org=1=1=1=1#results

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

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

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

Bug#994072: simplescreenrecorder: Please ask upstream to support VP9 and Opus

[Petter Reinholdtsen]

Control: forwarded -1 https://github.com/MaartenBaert/ssr/issues/634

As far as I can tell, the issue is already reported upstream, and some
ffmpeg instructions are provided in this ticket.
-- 
Happy hacking
Petter Reinholdtsen

Bug#1031325: e2fsprogs 1.47.0 introduces a breaking change into Bookworm, breaking grub and making installations of Ubuntu and Debian releases via debootstrap impossible

[Adrian Bunk]

On Thu, Feb 16, 2023 at 03:05:06PM -0800, Russ Allbery wrote:
>...
> Each time you change the defaults in a way that could be
> backward-incompatible, you could capture those new defaults in a
> permanently-fixed label of, say, 20230616, which is the defaults on that
> date.  Probably in the default /etc/mke2fs.conf.  I don't expect you to
> care about what systems they work with, what distributions they work with,
> or anything else other than the timeline of when you decided to change the
> defaults, something you're presumably already doing as a maintainer.  The
> only additional work would be to update these labels with the settings
> required to make mke2fs with its current defaults behave compatibly with
> whatever the defaults had been at each of those captured points in time.
> 
> (And obviously eventually you could drop the really old ones if it made no
> sense to keep supporting them, or have some single really-ancient fallback
> for really old systems, etc.)
> 
> Then, image creators can look in /etc/mke2fs.conf for the timestamp that
> most closely aligns with the target system they want to create and use
> that group of settings.  If that turns out to be inadequate, they can go
> back to a previous date.

The image creators could just set the features they enable to what they 
copied from /etc/mke2fs.conf from the target distribution, a label with 
a timestamp wouldn'tbring much benefit here.

We are talking about tools for creating filesystems and their authors,
users of these tools don't have to know anything about all that.

> Some work on their part is still required, but
> from their perspective I think this would have the advantage of not having
> to do research to reconstruct what all the options could be and how they
> changed and which ones were potentially backward-incompatible, which are
> all things you would generally already know and have in mind when you
> changed the defaults and thus could capture for them.
>...

Image creators usually support several different filesystems.

There is also the point that a tool in bookworm that supports creating 
bullseye images will also support creating bookworm images, so when 
there is a difference in the settings for bullseye and bookworm images
it should anyway be updated for the difference. Setting a new default
for bookworm or disabling a new feature for <= bullseye, the work is
trivial in any case and the hard part is all image creators being aware
that there is a difference.

cu
Adrian

Bug#1031451: poliastro: FTBFS: make[1]: *** [debian/rules:9: override_dh_auto_test] Error 1

[Lucas Nussbaum]

Source: poliastro
Version: 0.17.0-1
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20230216 ftbfs-bookworm

Hi,

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


Relevant part (hopefully):
> === FAILURES 
> ===
> __ test_maneuver_constructor_raises_error_if_invalid_delta_v 
> ___
> 
> def test_maneuver_constructor_raises_error_if_invalid_delta_v():
> dv1 = np.zeros(3) * u.km / u.s
> dv2 = np.ones(2) * u.km / u.s  # Incorrect dv
> with pytest.raises(ValueError) as excinfo:
> with warnings.catch_warnings():
> # Different length numpy arrays generate a deprecation 
> warning.
> warnings.simplefilter(
> "ignore", category=np.VisibleDeprecationWarning
> )
> Maneuver((0 * u.s, dv1), (2 * u.s, dv2))
> >   assert "Delta-V must be three dimensions vectors" in excinfo.exconly()
> E   AssertionError: assert 'Delta-V must be three dimensions vectors' in 
> 'ValueError: setting an array element with a sequence. The requested array 
> has an inhomogeneous shape after 1 dimensions. The detected shape was (2,) + 
> inhomogeneous part.'
> E+  where 'ValueError: setting an array element with a sequence. The 
> requested array has an inhomogeneous shape after 1 dimensions. The detected 
> shape was (2,) + inhomogeneous part.' =  of  requested array has an inhomogeneous shape after 1 dimensions. The detected 
> shape was (2,) + inhomogeneous part.') tblen=4>>()
> E+where  ValueError('setting an array element with a sequence. The requested array has 
> an inhomogeneous shape after 1 dimensions. The detected shape was (2,) + 
> inhomogeneous part.') tblen=4>> =  element with a sequence. The requested array has an inhomogeneous shape after 
> 1 dimensions. The detected shape was (2,) + inhomogeneous part.') 
> tblen=4>.exconly
> 
> tests/test_maneuver.py:26: AssertionError
> __ test_stumpff_functions_above_zero 
> ___
> 
> def test_stumpff_functions_above_zero():
> psi = 3.0
> expected_c2 = (1 - cos(psi**0.5)) / psi
> expected_c3 = (psi**0.5 - sin(psi**0.5)) / psi**1.5
> 
> assert_equal(c2(psi), expected_c2)
> >   assert_equal(c3(psi), expected_c3)
> E   AssertionError: 
> E   Items are not equal:
> EACTUAL: 0.143379966939162
> EDESIRED: 0.14337996693916197
> 
> tests/test_stumpff.py:22: AssertionError
> __ test_stumpff_functions_under_zero 
> ___
> 
> def test_stumpff_functions_under_zero():
> psi = -3.0
> expected_c2 = (cosh((-psi) ** 0.5) - 1) / (-psi)
> expected_c3 = (sinh((-psi) ** 0.5) - (-psi) ** 0.5) / (-psi) ** 1.5
> 
> >   assert_equal(c2(psi), expected_c2)
> E   AssertionError: 
> E   Items are not equal:
> EACTUAL: 0.6381924800586426
> EDESIRED: 0.6381924800586427
> 
> tests/test_stumpff.py:30: AssertionError
> === warnings summary 
> ===
> ../../../usr/lib/python3/dist-packages/llvmlite/binding/ffi.py:159
>   /usr/lib/python3/dist-packages/llvmlite/binding/ffi.py:159: 
> DeprecationWarning: path is deprecated. Use files() instead. Refer to 
> https://importlib-resources.readthedocs.io/en/latest/using.html#migrating-from-legacy
>  for migration advice.
> _lib_handle = importlib.resources.path(pkgname, _lib_name)
> 
> tests/test_frames.py::test_round_trip_from_GeocentricSolarEcliptic_gives_same_results
> tests/test_frames.py::test_GeocentricSolarEcliptic_against_data
>   /<>/src/poliastro/frames/ecliptic.py:78: 
> AstropyDeprecationWarning: The matrix_product function is deprecated and may 
> be removed in a future version.
>   Use @ instead.
> return matrix_product(rot_matrix, _earth_detilt_matrix)
> 
> tests/test_maneuver.py::test_hohmann_maneuver[nu0]
>   /<>/src/poliastro/core/maneuver.py:49: 
> NumbaPerformanceWarning: '@' is faster on contiguous arrays, called on 
> (array(float64, 1d, A), array(float64, 1d, A))
> r_i = norm(r_i)
> 
> tests/tests_plotting/test_gabbard.py::test_static_gabbard_plotting
>   /usr/lib/python3/dist-packages/_pytest/python.py:199: 
> PytestReturnNotNoneWarning:
>   
>   Expected None, but 
> tests/tests_plotting/test_gabbard.py::test_static_gabbard_plotting returned 
> , which will be an error in a future 
> version of pytest.  Did you mean to use `assert` i

Bug#1031452: prettify.js: FTBFS: java.util.MissingResourceException: Can't find bundle for base name com.google.javascript.rhino.head.resources.Messages, locale en

[Lucas Nussbaum]

Source: prettify.js
Version: 2015.12.04+dfsg-1.1
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20230216 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 '/<>'
> Compiling
> 1570 src/prettify.css
>  675 distrib/google-code-prettify/prettify.css
> java.util.MissingResourceException: Can't find bundle for base name 
> com.google.javascript.rhino.head.resources.Messages, locale en
>   at 
> java.base/java.util.ResourceBundle.throwMissingResourceException(ResourceBundle.java:2045)
>   at 
> java.base/java.util.ResourceBundle.getBundleImpl(ResourceBundle.java:1683)
>   at 
> java.base/java.util.ResourceBundle.getBundleImpl(ResourceBundle.java:1586)
>   at 
> java.base/java.util.ResourceBundle.getBundleImpl(ResourceBundle.java:1549)
>   at java.base/java.util.ResourceBundle.getBundle(ResourceBundle.java:932)
>   at 
> com.google.javascript.rhino.head.ScriptRuntime$DefaultMessageProvider.getMessage(ScriptRuntime.java:4521)
>   at 
> com.google.javascript.rhino.head.ScriptRuntime.getMessage(ScriptRuntime.java:4501)
>   at 
> com.google.javascript.rhino.head.ScriptRuntime.getMessage0(ScriptRuntime.java:4446)
>   at 
> com.google.javascript.jscomp.RhinoErrorReporter.(RhinoErrorReporter.java:84)
>   at 
> com.google.javascript.jscomp.RhinoErrorReporter.(RhinoErrorReporter.java:32)
>   at 
> com.google.javascript.jscomp.RhinoErrorReporter$OldRhinoErrorReporter.(RhinoErrorReporter.java:162)
>   at 
> com.google.javascript.jscomp.RhinoErrorReporter$OldRhinoErrorReporter.(RhinoErrorReporter.java:158)
>   at 
> com.google.javascript.jscomp.RhinoErrorReporter.forOldRhino(RhinoErrorReporter.java:119)
>   at com.google.javascript.jscomp.Compiler.(Compiler.java:176)
>   at 
> com.google.javascript.jscomp.CommandLineRunner.createCompiler(CommandLineRunner.java:858)
>   at 
> com.google.javascript.jscomp.AbstractCommandLineRunner.doRun(AbstractCommandLineRunner.java:741)
>   at 
> com.google.javascript.jscomp.AbstractCommandLineRunner.run(AbstractCommandLineRunner.java:380)
>   at 
> com.google.javascript.jscomp.CommandLineRunner.main(CommandLineRunner.java:980)
> make[2]: *** [Makefile:40: distrib.tstamp] Error 254


The full build log is available from:
http://qa-logs.debian.net/2023/02/16/prettify.js_2015.12.04+dfsg-1.1_unstable.log

All bugs filed during this archive rebuild are listed at:
https://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=ftbfs-20230216;users=lu...@debian.org
or:
https://udd.debian.org/bugs/?release=na=ign=7=7=only=ftbfs-20230216=lu...@debian.org=1=1=1=1#results

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

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

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

Bug#1031449: python-scrapy: FTBFS: ImportError: zstd C API versions mismatch; Python bindings were not compiled/linked against expected zstd version (10504 returned by the lib, 10502 hardcoded in zstd

[Lucas Nussbaum]

Source: python-scrapy
Version: 2.8.0-1
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20230216 ftbfs-bookworm

Hi,

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


Relevant part (hopefully):
> === FAILURES 
> ===
>  ProxyConnectTestCase.test_https_connect_tunnel 
> 
> 
> self =  testMethod=test_https_connect_tunnel>
> 
> def setUp(self):
> try:
> import mitmproxy  # noqa: F401
> except ImportError:
> self.skipTest("mitmproxy is not installed")
> 
> self.mockserver = MockServer()
> self.mockserver.__enter__()
> self._oldenv = os.environ.copy()
> 
> self._proxy = MitmProxy()
> >   proxy_url = self._proxy.start()
> 
> /<>/.pybuild/cpython3_3.11_scrapy/build/tests/test_proxy_connect.py:79:
>  
> _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ 
> _ 
> 
> self = 
> 
> def start(self):
> from scrapy.utils.test import get_testenv
> 
> script = """
> import sys
> from mitmproxy.tools.main import mitmdump
> sys.argv[0] = "mitmdump"
> sys.exit(mitmdump())
> """
> cert_path = Path(__file__).parent.resolve() / "keys" / 
> "mitmproxy-ca.pem"
> self.proc = Popen(
> [
> sys.executable,
> "-c",
> script,
> "--listen-host",
> "127.0.0.1",
> "--listen-port",
> "0",
> "--proxyauth",
> f"{self.auth_user}:{self.auth_pass}",
> "--certs",
> str(cert_path),
> "--ssl-insecure",
> ],
> stdout=PIPE,
> env=get_testenv(),
> )
> line = self.proc.stdout.readline().decode("utf-8")
> >   host_port = re.search(r"listening at http://([^:]+:\d+)", 
> > line).group(1)
> E   AttributeError: 'NoneType' object has no attribute 'group'
> 
> /<>/.pybuild/cpython3_3.11_scrapy/build/tests/test_proxy_connect.py:52:
>  AttributeError
> - Captured stderr call 
> -
> Traceback (most recent call last):
>   File "", line 3, in 
>   File "/usr/lib/python3/dist-packages/mitmproxy/tools/main.py", line 9, in 
> 
> from mitmproxy import exceptions, master
>   File "/usr/lib/python3/dist-packages/mitmproxy/master.py", line 7, in 
> 
> from mitmproxy import eventsequence
>   File "/usr/lib/python3/dist-packages/mitmproxy/eventsequence.py", line 6, 
> in 
> from mitmproxy import http
>   File "/usr/lib/python3/dist-packages/mitmproxy/http.py", line 26, in 
> 
> from mitmproxy.net import encoding
>   File "/usr/lib/python3/dist-packages/mitmproxy/net/encoding.py", line 13, 
> in 
> import zstandard as zstd
>   File "/usr/lib/python3/dist-packages/zstandard/__init__.py", line 39, in 
> 
> from .backend_c import *  # type: ignore
> 
> ImportError: zstd C API versions mismatch; Python bindings were not 
> compiled/linked against expected zstd version (10504 returned by the lib, 
> 10502 hardcoded in zstd headers, 10502 hardcoded in the cext)
> __ ProxyConnectTestCase.test_https_tunnel_auth_error 
> ___
> 
> self =  testMethod=test_https_tunnel_auth_error>
> 
> def setUp(self):
> try:
> import mitmproxy  # noqa: F401
> except ImportError:
> self.skipTest("mitmproxy is not installed")
> 
> self.mockserver = MockServer()
> self.mockserver.__enter__()
> self._oldenv = os.environ.copy()
> 
> self._proxy = MitmProxy()
> >   proxy_url = self._proxy.start()
> 
> /<>/.pybuild/cpython3_3.11_scrapy/build/tests/test_proxy_connect.py:79:
>  
> _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ 
> _ 
> 
> self = 
> 
> def start(self):
> from scrapy.utils.test import get_testenv
> 
> script = """
> import sys
&

Bug#1031450: gearmand: FTBFS: ld: /usr/lib/gcc/x86_64-linux-gnu/12/../../../x86_64-linux-gnu/libmemcachedutil.so: undefined reference to `memcached_server_minor_version'

[Lucas Nussbaum]

Source: gearmand
Version: 1.1.19.1+ds-2
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20230216 ftbfs-bookworm

Hi,

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


Relevant part (hopefully):
> /bin/bash ./libtool  --tag=CXX   --mode=link c++  -g -O2 
> -ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat 
> -Werror=format-security -Wno-unknown-pragmas -Wno-pragmas -Wall -Wextra 
> -Wno-attributes -Wvarargs -Waddress -Warray-bounds -Wchar-subscripts 
> -Wcomment -Wctor-dtor-privacy -Wfloat-equal -Wformat=2 -Wformat-y2k 
> -Wmaybe-uninitialized -Wmissing-field-initializers -Wlogical-op 
> -Wnon-virtual-dtor -Wnormalized=id -Woverloaded-virtual -Wpointer-arith 
> -Wredundant-decls -Wshadow -Wsign-compare -Wstrict-overflow=1 -Wswitch-enum 
> -Wtrampolines -Wundef -funsafe-loop-optimizations -Wc++11-compat -Wclobbered 
> -Wunused -Wunused-result -Wunused-variable -Wunused-parameter 
> -Wunused-local-typedefs -Wwrite-strings -Wformat-security -fwrapv -pipe -fPIE 
> -pie -Wsizeof-pointer-memaccess -Wpacked -std=c++0x  -Wl,-z,relro -Wl,-z,now 
> -Wl,--as-needed -o t/httpd tests/httpd_test.o libgearman/libgearman.la 
> libtest/libtest.la tests/libstartworker.la 
> /usr/bin/ld: 
> /usr/lib/gcc/x86_64-linux-gnu/12/../../../x86_64-linux-gnu/libmemcachedutil.so:
>  undefined reference to `memcached_server_minor_version'
> /usr/bin/ld: 
> /usr/lib/gcc/x86_64-linux-gnu/12/../../../x86_64-linux-gnu/libmemcachedutil.so:
>  undefined reference to `memcached_server_instance_by_position'
> /usr/bin/ld: 
> /usr/lib/gcc/x86_64-linux-gnu/12/../../../x86_64-linux-gnu/libmemcachedutil.so:
>  undefined reference to `memcached_behavior_set'
> /usr/bin/ld: 
> /usr/lib/gcc/x86_64-linux-gnu/12/../../../x86_64-linux-gnu/libmemcachedutil.so:
>  undefined reference to `memcached_set_sasl_auth_data'
> /usr/bin/ld: 
> /usr/lib/gcc/x86_64-linux-gnu/12/../../../x86_64-linux-gnu/libmemcachedutil.so:
>  undefined reference to `memcached_free'
> /usr/bin/ld: 
> /usr/lib/gcc/x86_64-linux-gnu/12/../../../x86_64-linux-gnu/libmemcachedutil.so:
>  undefined reference to `memcached_flush'
> /usr/bin/ld: 
> /usr/lib/gcc/x86_64-linux-gnu/12/../../../x86_64-linux-gnu/libmemcachedutil.so:
>  undefined reference to `memcached_clone'
> /usr/bin/ld: 
> /usr/lib/gcc/x86_64-linux-gnu/12/../../../x86_64-linux-gnu/libmemcachedutil.so:
>  undefined reference to `memcached_server_major_version'
> /usr/bin/ld: 
> /usr/lib/gcc/x86_64-linux-gnu/12/../../../x86_64-linux-gnu/libmemcachedutil.so:
>  undefined reference to `memcached_version'
> /usr/bin/ld: 
> /usr/lib/gcc/x86_64-linux-gnu/12/../../../x86_64-linux-gnu/libmemcachedutil.so:
>  undefined reference to `memcached_behavior_get'
> /usr/bin/ld: 
> /usr/lib/gcc/x86_64-linux-gnu/12/../../../x86_64-linux-gnu/libmemcachedutil.so:
>  undefined reference to `memcached_server_micro_version'
> /usr/bin/ld: 
> /usr/lib/gcc/x86_64-linux-gnu/12/../../../x86_64-linux-gnu/libmemcachedutil.so:
>  undefined reference to `memcached_server_cursor'
> /usr/bin/ld: 
> /usr/lib/gcc/x86_64-linux-gnu/12/../../../x86_64-linux-gnu/libmemcachedutil.so:
>  undefined reference to `memcached_server_error_return'
> /usr/bin/ld: 
> /usr/lib/gcc/x86_64-linux-gnu/12/../../../x86_64-linux-gnu/libmemcachedutil.so:
>  undefined reference to `memcached'
> /usr/bin/ld: 
> /usr/lib/gcc/x86_64-linux-gnu/12/../../../x86_64-linux-gnu/libmemcachedutil.so:
>  undefined reference to `memcached_stat_free'
> /usr/bin/ld: 
> /usr/lib/gcc/x86_64-linux-gnu/12/../../../x86_64-linux-gnu/libmemcachedutil.so:
>  undefined reference to `memcached_server_error'
> /usr/bin/ld: 
> /usr/lib/gcc/x86_64-linux-gnu/12/../../../x86_64-linux-gnu/libmemcachedutil.so:
>  undefined reference to `memcached_create'
> /usr/bin/ld: 
> /usr/lib/gcc/x86_64-linux-gnu/12/../../../x86_64-linux-gnu/libmemcachedutil.so:
>  undefined reference to `memcached_stat'
> /usr/bin/ld: 
> /usr/lib/gcc/x86_64-linux-gnu/12/../../../x86_64-linux-gnu/libmemcachedutil.so:
>  undefined reference to `memcached_server_add'
> collect2: error: ld returned 1 exit status


The full build log is available from:
http://qa-logs.debian.net/2023/02/16/gearmand_1.1.19.1+ds-2_unstable.log

All bugs filed during this archive rebuild are listed at:
https://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=ftbfs-20230216;users=lu...@debian.org
or:
https://udd.debian.org/bugs/?release=na=ign=7=7=only=ftbfs-20230216=lu...@debian.org=1=1=1=1#results

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

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

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

Bug#1031447: ffmpeg: FTBFS: src/libavutil/hwcontext_vulkan.c:363:7: error: ‘VK_EXT_VIDEO_DECODE_H264_EXTENSION_NAME’ undeclared here (not in a function); did you mean ‘VK_EXT_VIDEO_ENCODE_H264_EXTENSI

[Lucas Nussbaum]

Source: ffmpeg
Version: 7:5.1.2-2
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20230216 ftbfs-bookworm

Hi,

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


Relevant part (hopefully):
> gcc -I. -Isrc/ -Wdate-time -D_FORTIFY_SOURCE=2 -U_FORTIFY_SOURCE 
> -D_FORTIFY_SOURCE=2 -D_ISOC99_SOURCE -D_FILE_OFFSET_BITS=64 
> -D_LARGEFILE_SOURCE -D_POSIX_C_SOURCE=200112 -D_XOPEN_SOURCE=600 -DPIC 
> -DZLIB_CONST -DHAVE_AV_CONFIG_H -DBUILDING_avutil -g -O2 
> -ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat 
> -Werror=format-security -fno-strict-overflow -fstack-protector-all -fPIE   
> -std=c11 -fomit-frame-pointer -fPIC -pthread  -I/usr/include/p11-kit-1  
> -I/usr/include/lilv-0 -I/usr/include/serd-0 -I/usr/include/sord-0 
> -I/usr/include/sratom-0 -I/usr/include/freetype2 -I/usr/include/libpng16 
> -I/usr/include/harfbuzz -I/usr/include/glib-2.0 
> -I/usr/lib/x86_64-linux-gnu/glib-2.0/include -I/usr/include/fribidi 
> -I/usr/include/libxml2 -I/usr/include/freetype2 -I/usr/include/libpng16 
> -I/usr/include/bs2b-I/usr/include/libdrm -I/usr/include/freetype2 
> -I/usr/include/libpng16 -I/usr/include/freetype2 -I/usr/include/libpng16 
> -I/usr/include/fribidi  -DHWY_SHARED_DEFINE  -I/usr/include/mfx  
> -I/usr/include/openjpeg-2.5 -I/usr/include/x86_64-linux-gnu 
> -I/usr/include/opus -I/usr/include/opus  -D_REENTRANT  -I/usr/include/rav1e  
> -I/usr/include/librsvg-2.0 -I/usr/include/glib-2.0 
> -I/usr/lib/x86_64-linux-gnu/glib-2.0/include -I/usr/include/libmount 
> -I/usr/include/blkid -I/usr/include/gdk-pixbuf-2.0 -I/usr/include/libpng16 
> -I/usr/include/x86_64-linux-gnu -pthread -I/usr/include/cairo 
> -I/usr/include/pixman-1 -I/usr/include/freetype2 -I/usr/include/srt 
> -I/usr/include/p11-kit-1 -I/usr/include/svt-av1 -DEB_DLL  
> -DX264_API_IMPORTS   -isystem /usr/include/mit-krb5 -I/usr/include/pgm-5.3 
> -I/usr/include/libxml2  -I/usr/include/libxml2  -I/usr/include/sphinxbase 
> -I/usr/include/pocketsphinx -I/usr/include/x86_64-linux-gnu 
> -I/usr/include/x86_64-linux-gnu/sphinxbase-I/usr/include/libdrm 
> -g -Wdeclaration-after-statement -Wall -Wdisabled-optimization 
> -Wpointer-arith -Wredundant-decls -Wwrite-strings -Wtype-limits -Wundef 
> -Wmissing-prototypes -Wstrict-prototypes -Wempty-body -Wno-parentheses 
> -Wno-switch -Wno-format-zero-length -Wno-pointer-sign 
> -Wno-unused-const-variable -Wno-bool-operation -Wno-char-subscripts -O3 
> -fno-math-errno -fno-signed-zeros -fno-tree-vectorize -Werror=format-security 
> -Werror=implicit-function-declaration -Werror=missing-prototypes 
> -Werror=return-type -Werror=vla -Wformat -fdiagnostics-color=auto 
> -Wno-maybe-uninitialized -I/usr/include/SDL2 -D_REENTRANT   -MMD -MF 
> libavutil/imgutils.d -MT libavutil/imgutils.o -c -o libavutil/imgutils.o 
> src/libavutil/imgutils.c
> src/libavutil/hwcontext_vulkan.c:363:7: error: 
> ‘VK_EXT_VIDEO_DECODE_H264_EXTENSION_NAME’ undeclared here (not in a 
> function); did you mean ‘VK_EXT_VIDEO_ENCODE_H264_EXTENSION_NAME’?
>   363 | { VK_EXT_VIDEO_DECODE_H264_EXTENSION_NAME,
> FF_VK_EXT_NO_FLAG},
>   |   ^~~
>   |   VK_EXT_VIDEO_ENCODE_H264_EXTENSION_NAME
> src/libavutil/hwcontext_vulkan.c:364:7: error: 
> ‘VK_EXT_VIDEO_DECODE_H265_EXTENSION_NAME’ undeclared here (not in a 
> function); did you mean ‘VK_EXT_VIDEO_ENCODE_H265_EXTENSION_NAME’?
>   364 | { VK_EXT_VIDEO_DECODE_H265_EXTENSION_NAME,
> FF_VK_EXT_NO_FLAG},
>   |   ^~~
>   |   VK_EXT_VIDEO_ENCODE_H265_EXTENSION_NAME
> gcc -I. -Isrc/ -Wdate-time -D_FORTIFY_SOURCE=2 -U_FORTIFY_SOURCE 
> -D_FORTIFY_SOURCE=2 -D_ISOC99_SOURCE -D_FILE_OFFSET_BITS=64 
> -D_LARGEFILE_SOURCE -D_POSIX_C_SOURCE=200112 -D_XOPEN_SOURCE=600 -DPIC 
> -DZLIB_CONST -DHAVE_AV_CONFIG_H -DBUILDING_avutil -g -O2 
> -ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat 
> -Werror=format-security -fno-strict-overflow -fstack-protector-all -fPIE   
> -std=c11 -fomit-frame-pointer -fPIC -pthread  -I/usr/include/p11-kit-1  
> -I/usr/include/lilv-0 -I/usr/include/serd-0 -I/usr/include/sord-0 
> -I/usr/include/sratom-0 -I/usr/include/freetype2 -I/usr/include/libpng16 
> -I/usr/include/harfbuzz -I/usr/include/glib-2.0 
> -I/usr/lib/x86_64-linux-gnu/glib-2.0/include -I/usr/include/fribidi 
> -I/usr/include/libxml2 -I/usr/include/freetype2 -I/usr/include/libpng16 
> -I/usr/include/bs2b-I/usr/include/libdrm -I/usr/include/freetype2 
> -I/usr/include/libpng16 -I/usr/include/freetype2 -I/usr/include/libpng16 
> -I/usr/include/fribidi  -DHWY_SHARED_DEFINE  -I/usr/include/mfx  
>

Bug#1031448: fwupd: FTBFS: ./obj-x86_64-linux-gnu/meson-private/tmp7p7957mh/./obj-x86_64-linux-gnu/meson-private/tmp7p7957mh/testfile.c:17: undefined reference to `gcab_cabinet_add_allowed_compression

[Lucas Nussbaum]

Source: fwupd
Version: 1.8.10-2
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20230216 ftbfs-bookworm

Hi,

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


Relevant part (hopefully):
>  /usr/bin/ld: /tmp/ccLdacAo.o: in function `main':
> ./obj-x86_64-linux-gnu/meson-private/tmp7p7957mh/./obj-x86_64-linux-gnu/meson-private/tmp7p7957mh/testfile.c:17:
>  undefined reference to `gcab_cabinet_add_allowed_compression'
> collect2: error: ld returned 1 exit status


The full build log is available from:
http://qa-logs.debian.net/2023/02/16/fwupd_1.8.10-2_unstable.log

All bugs filed during this archive rebuild are listed at:
https://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=ftbfs-20230216;users=lu...@debian.org
or:
https://udd.debian.org/bugs/?release=na=ign=7=7=only=ftbfs-20230216=lu...@debian.org=1=1=1=1#results

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

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

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

Bug#1031446: lomiri-ui-toolkit: FTBFS: QWARN : components::UnknownTestFunc() file:///usr/lib/x86_64-linux-gnu/qt5/qml/QtTest/SignalSpy.qml:258: Error: Invalid write to global property "qtest_count"

[Lucas Nussbaum]

Source: lomiri-ui-toolkit
Version: 1.3.5000+dfsg-1
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20230216 ftbfs-bookworm

Hi,

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


Relevant part (hopefully):
> Creating QML component for Lomiri.Metrics
> Failed to load Lomiri.Metrics
> import QtQuick 2.0
> import Lomiri.Metrics 0.1 as ALomiri_Metrics_0_1
> QtObject { }
> 
> file:///<>/qml/Lomiri/Metrics/qmldir:2:1: plugin cannot be 
> loaded for module "Lomiri.Metrics": Cannot protect module Lomiri.Metrics 0 as 
> it was never registered
> make[3]: *** [Makefile:745: check] Error 1


The full build log is available from:
http://qa-logs.debian.net/2023/02/16/lomiri-ui-toolkit_1.3.5000+dfsg-1_unstable.log

All bugs filed during this archive rebuild are listed at:
https://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=ftbfs-20230216;users=lu...@debian.org
or:
https://udd.debian.org/bugs/?release=na=ign=7=7=only=ftbfs-20230216=lu...@debian.org=1=1=1=1#results

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

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

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

Bug#1031443: python-zstandard: FTBFS: ImportError: zstd C API versions mismatch; Python bindings were not compiled/linked against expected zstd version (10504 returned by the lib, 10504 hardcoded in z

[Lucas Nussbaum]

Source: python-zstandard
Version: 0.19.0-3
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20230216 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 '/<>'
> cd docs; LC_ALL=C.UTF-8 LANGUAGE=C.UTF-8 sphinx-build -bhtml . _build/html
> Running Sphinx v5.3.0
> making output directory... done
> building [mo]: targets for 0 po files that are out of date
> building [html]: targets for 14 source files that are out of date
> updating environment: [new config] 14 added, 0 changed, 0 removed
> reading sources... [  7%] api_usage
> reading sources... [ 14%] buffer
> reading sources... [ 21%] compression_parameters
> reading sources... [ 28%] compressor
> reading sources... [ 35%] concepts
> reading sources... [ 42%] contributing
> reading sources... [ 50%] decompressor
> reading sources... [ 57%] dictionaries
> reading sources... [ 64%] index
> reading sources... [ 71%] installing
> reading sources... [ 78%] misc_apis
> reading sources... [ 85%] multithreaded
> reading sources... [ 92%] news
> reading sources... [100%] projectinfo
> 
> WARNING: autodoc: failed to import class 'BufferSegment' from module 
> 'zstandard'; the following exception was raised:
> No module named 'zstandard'
> WARNING: autodoc: failed to import class 'BufferSegments' from module 
> 'zstandard'; the following exception was raised:
> No module named 'zstandard'
> WARNING: autodoc: failed to import class 'BufferWithSegments' from module 
> 'zstandard'; the following exception was raised:
> No module named 'zstandard'
> WARNING: autodoc: failed to import class 'BufferWithSegmentsCollection' from 
> module 'zstandard'; the following exception was raised:
> No module named 'zstandard'
> WARNING: autodoc: failed to import class 'ZstdCompressionParameters' from 
> module 'zstandard'; the following exception was raised:
> No module named 'zstandard'
> WARNING: autodoc: failed to import class 'ZstdCompressor' from module 
> 'zstandard'; the following exception was raised:
> No module named 'zstandard'
> WARNING: autodoc: failed to import class 'ZstdCompressionWriter' from module 
> 'zstandard'; the following exception was raised:
> No module named 'zstandard'
> WARNING: autodoc: failed to import class 'ZstdCompressionReader' from module 
> 'zstandard'; the following exception was raised:
> No module named 'zstandard'
> WARNING: autodoc: failed to import class 'ZstdCompressionObj' from module 
> 'zstandard'; the following exception was raised:
> No module named 'zstandard'
> WARNING: autodoc: failed to import class 'ZstdCompressionChunker' from module 
> 'zstandard'; the following exception was raised:
> No module named 'zstandard'
> WARNING: autodoc: failed to import class 'ZstdDecompressor' from module 
> 'zstandard'; the following exception was raised:
> No module named 'zstandard'
> WARNING: autodoc: failed to import class 'ZstdDecompressionWriter' from 
> module 'zstandard'; the following exception was raised:
> No module named 'zstandard'
> WARNING: autodoc: failed to import class 'ZstdDecompressionReader' from 
> module 'zstandard'; the following exception was raised:
> No module named 'zstandard'
> WARNING: autodoc: failed to import class 'ZstdDecompressionObj' from module 
> 'zstandard'; the following exception was raised:
> No module named 'zstandard'
> WARNING: autodoc: failed to import class 'ZstdCompressionDict' from module 
> 'zstandard'; the following exception was raised:
> No module named 'zstandard'
> WARNING: autodoc: failed to import function 'train_dictionary' from module 
> 'zstandard'; the following exception was raised:
> No module named 'zstandard'
> WARNING: autodoc: failed to import function 'get_frame_parameters' from 
> module 'zstandard'; the following exception was raised:
> No module named 'zstandard'
> WARNING: autodoc: failed to import function 'frame_header_size' from module 
> 'zstandard'; the following exception was raised:
> No module named 'zstandard'
> WARNING: autodoc: failed to import function 'frame_content_size' from module 
> 'zstandard'; the following exception was raised:
> No module named 'zstandard'
> WARNING: autodoc: failed to import class 'FrameParameters' from module 
> 'zstandard'; the following exception was raised:
> No module named 'zstandard'
> WARNING: autodoc: failed to import function 
> 'estimate_decompression_context_size' from module 'zstandard'; the following 
> exception was raised:
> No module named 'zstandard'
> WARNING: autodoc: failed to import function 'open' from module 'zstandard'; 
> the following exception was raised:
> No module named 

Bug#1031445: camv-rnd: FTBFS: build-dependency not installable: librnd4-dev (>= 3.2.0)

[Lucas Nussbaum]

Source: camv-rnd
Version: 1.1.1-1
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20230216 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: debhelper (>= 11), librnd4-dev (>= 3.2.0), libgd-dev, 
> libgtkglext1-dev, build-essential, fakeroot
> Filtered Build-Depends: debhelper (>= 11), librnd4-dev (>= 3.2.0), libgd-dev, 
> libgtkglext1-dev, build-essential, fakeroot
> dpkg-deb: building package 'sbuild-build-depends-main-dummy' in 
> '/<>/apt_archive/sbuild-build-depends-main-dummy.deb'.
> Ign:1 copy:/<>/apt_archive ./ InRelease
> Get:2 copy:/<>/apt_archive ./ Release [957 B]
> Ign:3 copy:/<>/apt_archive ./ Release.gpg
> Get:4 copy:/<>/apt_archive ./ Sources [394 B]
> Get:5 copy:/<>/apt_archive ./ Packages [474 B]
> Fetched 1825 B in 0s (139 kB/s)
> Reading package lists...
> Reading package lists...
> 
> Install main build dependencies (apt-based resolver)
> 
> 
> Installing build dependencies
> Reading package lists...
> Building dependency tree...
> Some packages could not be installed. This may mean that you have
> requested an impossible situation or if you are using the unstable
> distribution that some required packages have not yet been created
> or been moved out of Incoming.
> The following information may help to resolve the situation:
> 
> The following packages have unmet dependencies:
>  sbuild-build-depends-main-dummy : Depends: librnd4-dev (>= 3.2.0) but it is 
> not installable
> E: Unable to correct problems, you have held broken packages.
> apt-get failed.


The full build log is available from:
http://qa-logs.debian.net/2023/02/16/camv-rnd_1.1.1-1_unstable.log

All bugs filed during this archive rebuild are listed at:
https://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=ftbfs-20230216;users=lu...@debian.org
or:
https://udd.debian.org/bugs/?release=na=ign=7=7=only=ftbfs-20230216=lu...@debian.org=1=1=1=1#results

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

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

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

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

[Lucas Nussbaum]

Source: poetry
Version: 1.3.2+dfsg-3
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20230216 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
>dh_auto_build -O--buildsystem=pybuild
> I: pybuild plugin_pyproject:107: Building wheel for python3.11 with "build" 
> module
> I: pybuild base:240: python3.11 -m build --skip-dependency-check 
> --no-isolation --wheel --outdir 
> /<>/.pybuild/cpython3_3.11_poetry 
> * Building wheel...
> Successfully built poetry-1.3.2-py3-none-any.whl
> I: pybuild plugin_pyproject:119: Unpacking wheel built for python3.11 with 
> "installer" module
>dh_auto_test -O--buildsystem=pybuild
> I: pybuild base:240: cd /<>/.pybuild/cpython3_3.11_poetry/build; 
> python3.11 -m pytest --ignore=tests/console/commands/env/test_list.py 
> --ignore=tests/console/commands/env/test_remove.py 
> --ignore=tests/console/commands/env/test_use.py 
> --ignore=tests/utils/test_env.py --ignore=tests/config/test_config.py 
> --ignore=tests/utils/test_helpers.py -k 'not 
> test_self_update_should_install_all_necessary_elements and not 
> test_add_file_constraint_sdist and not 
> test_add_file_constraint_sdist_old_installer and not test_publish_dry_run and 
> not test_info_from_sdist and not 
> test_installer_can_install_dependencies_from_forced_source and not 
> test_search_for_file_sdist and not test_search_for_file_sdist_with_extras and 
> not test_solver_can_resolve_sdist_dependencies and not 
> test_solver_can_resolve_sdist_dependencies_with_extras and not 
> test_solver_chooses_from_correct_repository_if_forced and not 
> test_solver_chooses_from_correct_repository_if_forced_and_transitive_dependency
>  and not test_solver_does_not_choose_from_secondary_repository_by_default and 
> not test_solver_chooses_from_secondary_if_explicit and not 
> test_get_package_information_fallback_read_setup and not 
> test_get_package_information_skips_dependencies_with_invalid_constraints and 
> not test_get_package_retrieves_packages_with_no_hashes and not 
> test_fallback_can_read_setup_to_get_dependencies and not 
> test_exporter_can_export_requirements_txt_with_file_packages and not 
> test_exporter_can_export_requirements_txt_with_file_packages_and_markers and 
> not test_lock_no_update and not 
> test_locker_dumps_dependency_information_correctly and not 
> test_package_partial_yank and not 
> test_run_installs_with_same_version_url_files and not 
> test_env_info_displays_complete_info and not test_skip_existing_output and 
> not 
> test_installer_should_use_the_locked_version_of_git_dependencies_with_extras 
> and not 
> test_installer_should_use_the_locked_version_of_git_dependencies_without_reference
>  and not test_installer_uses_prereleases_if_they_are_compatible and not 
> test_requirement_git_subdirectory and not test_check_valid and not 
> test_check_invalid and not test_packages_property_returns_empty_list and not 
> test_parse_dependency_specification and not 
> test_info_setup_missing_mandatory_should_trigger_pep517 and not 
> test_uninstall_git_package_nspkg_pth_cleanup and not 
> test_executor_should_write_pep610_url_references_for_directories and not 
> test_executor_should_write_pep610_url_references_for_git and not 
> test_executor_should_write_pep610_url_references_for_git_with_subdirectories'
> = test session starts 
> ==
> platform linux -- Python 3.11.2, pytest-7.2.1, pluggy-1.0.0+repack
> rootdir: /<>, configfile: pyproject.toml
> plugins: xdist-3.1.0, mock-3.8.2
> gw0 I / gw1 I / gw2 I / gw3 I / gw4 I / gw5 I / gw6 I / gw7 I
> gw0 [1051] / gw1 [1051] / gw2 [1051] / gw3 [1051] / gw4 [1051] / gw5 [1051] / 
> gw6 [1051] / gw7 [1051]
> 
>  [  
> 6%]
>  [ 
> 13%]
> . [ 
> 20%]
> s [ 
> 27%]
>  [ 
> 34%]
> ..F.. [ 
> 41%]
> ..s. [ 
> 48%]
> ...

Bug#1031438: qca2: FTBFS: dh_auto_test: error: cd build && make -j8 test ARGS\+=--verbose ARGS\+=-j8 returned exit code 2

[Lucas Nussbaum]

Source: qca2
Version: 2.3.5-1
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20230216 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 '/<>/build'
> Running tests...
> /usr/bin/ctest --force-new-ctest-process --verbose -j8
> UpdateCTestConfiguration  from :/<>/build/DartConfiguration.tcl
> UpdateCTestConfiguration  from :/<>/build/DartConfiguration.tcl
> Test project /<>/build
> Constructing a list of tests
> Done constructing a list of tests
> Updating test list for fixtures
> Added 0 tests to meet fixture requirements
> Checking test dependency graph...
> Checking test dependency graph end
> test 1
>   Start  1: Base64
> 
> 1: Test command: /<>/build/bin/base64unittest
> 1: Working Directory: /<>/build/bin
> 1: Test timeout computed to be: 1000
> test 2
>   Start  2: BigInteger
> 
> 2: Test command: /<>/build/bin/bigintunittest
> 2: Working Directory: /<>/build/bin
> 2: Test timeout computed to be: 1000
> test 3
>   Start  3: Certificate
> 
> 3: Test command: /<>/build/bin/certunittest
> 3: Working Directory: /<>/build/bin
> 3: Test timeout computed to be: 1000
> test 4
>   Start  4: SymmetricCipher
> 
> 4: Test command: /<>/build/bin/cipherunittest
> 4: Working Directory: /<>/build/bin
> 4: Test timeout computed to be: 1000
> test 5
>   Start  5: ClientSidePlugin
> 
> 5: Test command: /<>/build/bin/clientplugin
> 5: Working Directory: /<>/build/bin
> 5: Test timeout computed to be: 1000
> test 6
>   Start  6: DigitalSignatureAlgorithm
> 
> 6: Test command: /<>/build/bin/dsaunittest
> 6: Working Directory: /<>/build/bin
> 6: Test timeout computed to be: 1000
> test 7
>   Start  7: FileWatch
> 
> 7: Test command: /<>/build/bin/filewatchunittest
> 7: Working Directory: /<>/build/bin
> 7: Test timeout computed to be: 1000
> test 8
>   Start  8: Hashing
> 
> 8: Test command: /<>/build/bin/hashunittest
> 8: Working Directory: /<>/build/bin
> 8: Test timeout computed to be: 1000
> 1: * Start testing of Base64UnitTest *
> 1: Config: Using QtTest library 5.15.8, Qt 5.15.8 (x86_64-little_endian-lp64 
> shared (dynamic) release build; by GCC 12.2.0), debian unknown
> 1: PASS   : Base64UnitTest::initTestCase()
> 1: PASS   : Base64UnitTest::test1(31)
> 1: PASS   : Base64UnitTest::test1(235c91)
> 1: PASS   : Base64UnitTest::test1(414)
> 1: PASS   : Base64UnitTest::test1(241)
> 1: PASS   : Base64UnitTest::test1(313)
> 1: PASS   : Base64UnitTest::test1(60e)
> 1: PASS   : Base64UnitTest::test1(3134)
> 1: PASS   : Base64UnitTest::test2(www.python.org)
> 1: PASS   : Base64UnitTest::test2(a)
> 1: PASS   : Base64UnitTest::test2(ab)
> 1: PASS   : Base64UnitTest::test2(abc)
> 1: PASS   : Base64UnitTest::test2(empty)
> 1: PASS   : Base64UnitTest::test2(a-Z)
> 1: PASS   : Base64UnitTest::test2(31)
> 1: PASS   : Base64UnitTest::test2(QCA_2.0)
> 1: PASS   : Base64UnitTest::test2(j-0)
> 1: PASS   : Base64UnitTest::cleanupTestCase()
> 1: Totals: 18 passed, 0 failed, 0 skipped, 0 blacklisted, 1ms
> 1: * Finished testing of Base64UnitTest *
> 2: * Start testing of BigIntUnitTest *
> 2: Config: Using QtTest library 5.15.8, Qt 5.15.8 (x86_64-little_endian-lp64 
> shared (dynamic) release build; by GCC 12.2.0), debian unknown
> 2: PASS   : BigIntUnitTest::initTestCase()
> 3: * Start testing of CertUnitTest *
> 3: Config: Using QtTest library 5.15.8, Qt 5.15.8 (x86_64-little_endian-lp64 
> shared (dynamic) release build; by GCC 12.2.0), debian unknown
> 3: PASS   : CertUnitTest::initTestCase()
> 4: * Start testing of CipherUnitTest *
> 4: Config: Using QtTest library 5.15.8, Qt 5.15.8 (x86_64-little_endian-lp64 
> shared (dynamic) release build; by GCC 12.2.0), debian unknown
> 4: PASS   : CipherUnitTest::initTestCase()
> 5: * Start testing of ClientPlugin *
> 5: Config: Using QtTest library 5.15.8, Qt 5.15.8 (x86_64-little_endian-lp64 
> shared (dynamic) release build; by GCC 12.2.0), debian unknown
> 5: PASS   : ClientPlugin::initTestCase()
> 5: PASS   : ClientPlugin::testInsertRemovePlugin()
> 5: PASS   : ClientPlugin::cleanupTestCase()
> 6: * Start testing of DSAUnitTest *
> 6: Config: Using QtTest library 5.15.8, Qt 5.15.8 (x86_64-little_endian-lp64 
> shared (dynamic) release build; by GCC 12.2.0), debian unknown
> 6: PASS   : DSAUnitTest::initTestCase()
>

Bug#1031442: gnustep-base: FTBFS: dh_auto_test: error: make -j8 check "TESTSUITEFLAGS=-j8 --verbose" VERBOSE=1 messages=yes returned exit code 2

[Lucas Nussbaum]

Source: gnustep-base
Version: 1.28.1+really1.28.0-5
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20230216 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 '/<>/Tests'
> (\
> GNUSTEP_LOCAL_ADDITIONAL_MAKEFILES="/<>/base.make";\
> ADDITIONAL_INCLUDE_DIRS="-I/<>/Headers 
> -I/<>/Source/.";\
> ADDITIONAL_LIB_DIRS="-L/<>/Source/./obj";\
> ADDITIONAL_LDFLAGS="-Wl,-rpath,/<>/Source/./obj";\
> LD_LIBRARY_PATH="/<>/Source/./obj:";\
> PATH="/<>/Tools/./obj:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games";\
> export GNUSTEP_LOCAL_ADDITIONAL_MAKEFILES;\
> export ADDITIONAL_INCLUDE_DIRS;\
> export ADDITIONAL_LDFLAGS;\
> export ADDITIONAL_LIB_DIRS;\
> export LD_LIBRARY_PATH;\
> export PATH;\
> if [ "no" = "yes" ]; then \
>   gnustep-tests --debug 'base/';\
> else \
>   gnustep-tests 'base/';\
> fi; \
> )
> --- Running tests in base/Functions ---
> --- Running tests in base/GSMime ---
> --- Running tests in base/GSTLS ---
> --- Running tests in base/GSXML ---
> --- Running tests in base/GarbageCollection ---
> --- Running tests in base/KVC ---
> --- Running tests in base/NSAffineTransform ---
> --- Running tests in base/NSArchiver ---
> --- Running tests in base/NSArray ---
> 
> base/NSArray/basic.m:
> Skipped set:   basic.m 46 ... No collection subscripting support in the 
> compiler.
> 
> base/NSArray/blocks.m:
> Skipped set:   blocks.m 76 ... No Blocks support in the compiler.
> --- Running tests in base/NSAttributedString ---
> --- Running tests in base/NSAutoreleasePool ---
> --- Running tests in base/NSBundle ---
> 
> base/NSBundle/general.m:
> Skipped set: general.m 25 ... it looks like GNUstep-base is not yet 
> installed
> 
> base/NSBundle/resources.m:
> Skipped set:   resources.m 48 ... it looks like GNUstep-base is not yet 
> installed
> --- Running tests in base/NSCache ---
> --- Running tests in base/NSCalendar ---
> --- Running tests in base/NSCalendarDate ---
> 
> base/NSCalendarDate/test00.m:
> Failed file: test00.m aborted without running all tests!
> --- Running tests in base/NSCharacterSet ---
> --- Running tests in base/NSConnection ---
> --- Running tests in base/NSCountedSet ---
> --- Running tests in base/NSData ---
> 
> base/NSData/general.m:
> Skipped set:   general.m 128 ... No Blocks support in the compiler.
> --- Running tests in base/NSDate ---
> --- Running tests in base/NSDateFormatter ---
> --- Running tests in base/NSDictionary ---
> 
> base/NSDictionary/basic.m:
> Skipped set:   basic.m 41 ... No dictionary subscripting support in the 
> compiler.
> 
> base/NSDictionary/blocks.m:
> Skipped set:   blocks.m 49 ... No Blocks support in the compiler.
> 
> base/NSDictionary/sort.m:
> Skipped set:   sort.m 54 ... No Blocks support in the compiler.
> --- Running tests in base/NSDistributedLock ---
> --- Running tests in base/NSException ---
> --- Running tests in base/NSFileHandle ---
> --- Running tests in base/NSFileManager ---
> --- Running tests in base/NSHTTPCookie ---
> --- Running tests in base/NSHashTable ---
> 
> base/NSHashTable/weakObjects.m:
> Skipped set:   weakObjects.m 15 ... ARC support unavailable
> --- Running tests in base/NSHost ---
> --- Running tests in base/NSIndexPath ---
> --- Running tests in base/NSInvocation ---
> --- Running tests in base/NSInvocationOperation ---
> --- Running tests in base/NSJSONSerialization ---
> --- Running tests in base/NSKeyedArchiver ---
> --- Running tests in base/NSLocale ---
> --- Running tests in base/NSLock ---
> --- Running tests in base/NSMapTable ---
> 
> base/NSMapTable/weakObjects.m:
> Skipped set:   weakObjects.m 15 ... ARC support unavailable
> --- Running tests in base/NSMethodSignature ---
> --- Running tests in base/NSMutableArray ---
> --- Running tests in base/NSMutableAttributedString ---
> --- Running tests in base/NSMutableCharacterSet ---
> --- Running tests in base/NSMutableData ---
> --- Running tests in base/NSMutableDictionary ---
> --- Running tests in base/NSMutableIndexSet ---
> 
> base/NSMutableIndexSet/blocks.m:
> Skipped set:   blocks.m 83 ... No Blocks support in the compiler.
> --- Running tests in base/NSMutableSet ---
> --- Running tests in base/NSMutableString ---
> --- Running tests in base/NSNotification ---
> --- Running tests in base/NSNumber ---
> --- Running tests in base/NSNumberFormatter -

Bug#1031441: ruby-github-api: FTBFS: ERROR: Test "ruby3.1" failed: /usr/lib/ruby/vendor_ruby/rubygems/specification.rb:1413:in `rescue in block in activate_dependencies': Could not find 'oauth2' (~> 1

[Lucas Nussbaum]

Source: ruby-github-api
Version: 0.19.0-2
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20230216 ftbfs-bookworm

Hi,

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


Relevant part (hopefully):
> /usr/lib/ruby/vendor_ruby/rubygems/specification.rb:1413:in `rescue in block 
> in activate_dependencies': Could not find 'oauth2' (~> 1.0) among 106 total 
> gem(s) (Gem::MissingSpecError)
> Checked in 
> 'GEM_PATH=/<>/debian/ruby-github-api/usr/share/rubygems-integration/all:/<>/debian/.debhelper/generated/_source/home/.local/share/gem/ruby/3.1.0:/var/lib/gems/3.1.0:/usr/local/lib/ruby/gems/3.1.0:/usr/lib/ruby/gems/3.1.0:/usr/lib/x86_64-linux-gnu/ruby/gems/3.1.0:/usr/share/rubygems-integration/3.1.0:/usr/share/rubygems-integration/all:/usr/lib/x86_64-linux-gnu/rubygems-integration/3.1.0'
>  at: 
> /<>/debian/ruby-github-api/usr/share/rubygems-integration/all/specifications/github_api-0.19.0.gemspec,
>  execute `gem env` for more information
>   from /usr/lib/ruby/vendor_ruby/rubygems/specification.rb:1410:in `block 
> in activate_dependencies'
>   from /usr/lib/ruby/vendor_ruby/rubygems/specification.rb:1399:in `each'
>   from /usr/lib/ruby/vendor_ruby/rubygems/specification.rb:1399:in 
> `activate_dependencies'
>   from /usr/lib/ruby/vendor_ruby/rubygems/specification.rb:1381:in 
> `activate'
>   from /usr/lib/ruby/vendor_ruby/rubygems/core_ext/kernel_gem.rb:68:in 
> `block in gem'
>   from /usr/lib/ruby/vendor_ruby/rubygems/core_ext/kernel_gem.rb:68:in 
> `synchronize'
>   from /usr/lib/ruby/vendor_ruby/rubygems/core_ext/kernel_gem.rb:68:in 
> `gem'
>   from -e:1:in `'
> /usr/lib/ruby/vendor_ruby/rubygems/dependency.rb:313:in `to_specs': Could not 
> find 'oauth2' (~> 1.0) - did find: [oauth2-2.0.7] 
> (Gem::MissingSpecVersionError)
> Checked in 
> 'GEM_PATH=/<>/debian/ruby-github-api/usr/share/rubygems-integration/all:/<>/debian/.debhelper/generated/_source/home/.local/share/gem/ruby/3.1.0:/var/lib/gems/3.1.0:/usr/local/lib/ruby/gems/3.1.0:/usr/lib/ruby/gems/3.1.0:/usr/lib/x86_64-linux-gnu/ruby/gems/3.1.0:/usr/share/rubygems-integration/3.1.0:/usr/share/rubygems-integration/all:/usr/lib/x86_64-linux-gnu/rubygems-integration/3.1.0'
>  , execute `gem env` for more information
>   from /usr/lib/ruby/vendor_ruby/rubygems/specification.rb:1411:in `block 
> in activate_dependencies'
>   from /usr/lib/ruby/vendor_ruby/rubygems/specification.rb:1399:in `each'
>   from /usr/lib/ruby/vendor_ruby/rubygems/specification.rb:1399:in 
> `activate_dependencies'
>   from /usr/lib/ruby/vendor_ruby/rubygems/specification.rb:1381:in 
> `activate'
>   from /usr/lib/ruby/vendor_ruby/rubygems/core_ext/kernel_gem.rb:68:in 
> `block in gem'
>   from /usr/lib/ruby/vendor_ruby/rubygems/core_ext/kernel_gem.rb:68:in 
> `synchronize'
>   from /usr/lib/ruby/vendor_ruby/rubygems/core_ext/kernel_gem.rb:68:in 
> `gem'
>   from -e:1:in `'
> abbrev (default: 0.1.0)
> addressable (2.8.1)
> atomic (1.1.16)
> base64 (default: 0.1.1)
> benchmark (default: 0.2.0)
> bigdecimal (default: 3.1.1)
> bundler (default: 2.3.7)
> cgi (default: 0.3.5)
> csv (default: 3.2.2)
> date (default: 3.2.2)
> debug (1.4.0)
> delegate (default: 0.2.0)
> descendants_tracker (0.0.4)
> did_you_mean (default: 1.6.1)
> digest (default: 3.1.0)
> drb (default: 2.1.0)
> english (default: 0.7.1)
> erb (default: 2.2.3)
> error_highlight (default: 0.3.0)
> etc (default: 1.3.0)
> faraday (1.1.0)
> fcntl (default: 1.0.1)
> fiddle (default: 1.1.0)
> fileutils (default: 1.6.0)
> find (default: 0.1.1)
> forwardable (default: 1.3.2)
> getoptlong (default: 0.1.1)
> hashie (5.0.0)
> io-console (default: 0.5.11)
> io-nonblock (default: 0.1.0)
> io-wait (default: 0.2.1)
> ipaddr (default: 1.2.4)
> irb (default: 1.4.1)
> json (default: 2.6.1)
> jwt (2.5.0)
> logger (default: 1.5.0)
> matrix (0.4.2)
> minitest (5.15.0)
> multi_json (1.14.1)
> multi_xml (0.6.0)
> multipart-post (2.0.0)
> mutex_m (default: 0.1.1)
> net-ftp (0.1.3)
> net-http (default: 0.2.0)
> net-imap (0.2.3)
> net-pop (0.1.1)
> net-protocol (default: 0.1.2)
> net-smtp (0.3.1)
> net-telnet (0.2.0)
> nkf (default: 0.1.1)
> oauth2 (2.0.7)
> observer (default: 0.1.1)
> open-uri (default: 0.2.0)
> open3 (default: 0.1.1)
> openssl (default: 3.0.0)
> optparse (default: 0.2.0)
> ostruct (default: 0.5.2)
> pathname (default: 0.2.0)
> power_assert (2.0.1)
> pp (default: 0.3.0)
> prettyprint (default: 0.1.1)
> prime (0.1.2)
> pstore (default: 0.1.1)
> psych (default: 4.0.3)
> public_suffix (4.0.6)
> racc (default: 1.

Bug#1031440: open-vm-tools: FTBFS: fuse_config.h:42: error: "PACKAGE_VERSION" redefined [-Werror]

[Lucas Nussbaum]

Source: open-vm-tools
Version: 2:12.1.5-3
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20230216 ftbfs-bookworm

Hi,

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


Relevant part (hopefully):
> gcc -DPACKAGE_NAME=\"open-vm-tools\" -DPACKAGE_TARNAME=\"open-vm-tools\" 
> -DPACKAGE_VERSION=\"12.1.5\" -DPACKAGE_STRING=\"open-vm-tools\ 12.1.5\" 
> -DPACKAGE_BUGREPORT=\"open-vm-tools-de...@lists.sourceforge.net\" 
> -DPACKAGE_URL=\"\" -DHAVE_STDIO_H=1 -DHAVE_STDLIB_H=1 -DHAVE_STRING_H=1 
> -DHAVE_INTTYPES_H=1 -DHAVE_STDINT_H=1 -DHAVE_STRINGS_H=1 -DHAVE_SYS_STAT_H=1 
> -DHAVE_SYS_TYPES_H=1 -DHAVE_UNISTD_H=1 -DHAVE_SYS_TIME_H=1 -DSTDC_HEADERS=1 
> -DPACKAGE=\"open-vm-tools\" -DVERSION=\"12.1.5\" -DHAVE_DLFCN_H=1 
> -DLT_OBJDIR=\".libs/\" -DHAVE_FUSE3=1 -DFUSE_USE_VERSION=35 
> -DHAVE_X11_SM_SMLIB_H=1 -DHAVE_X11_ICE_ICELIB_H=1 
> -DHAVE_X11_EXTENSIONS_XCOMPOSITE_H=1 -DHAVE_DLOPEN=1 -DHAVE_ECVT=1 
> -DHAVE_FCVT=1 -DNO_DNET=1 -DHAVE_CRYPT_H=1 -DHAVE_INTTYPES_H=1 
> -DHAVE_STDINT_H=1 -DHAVE_STDLIB_H=1 -DHAVE_WCHAR_H=1 -DHAVE_SYS_IO_H=1 
> -DHAVE_SYS_PARAM_H=1 -DHAVE_SYS_SYSINFO_H=1 -DHAVE_SYS_TYPES_H=1 
> -DHAVE_SYS_USER_H=1 -DHAVE_SYS_VFS_H=1 -DHAVE_UNWIND_H=1 -DHAVE__BOOL=1 
> -DHAVE_STDBOOL_H=1 -DHAVE_STRUCT_STAT_ST_RDEV=1 -DTIME_WITH_SYS_TIME=1 -I.   
> -I/<>/open-vm-tools/lib/include 
> -I/<>/open-vm-tools/lib/include -Wdate-time -D_FORTIFY_SOURCE=2 
> -DUSING_AUTOCONF=1 -DOPEN_VM_TOOLS -DUSE_VGAUTH  -DNO_ICU -DVMX86_TOOLS 
> -D_FILE_OFFSET_BITS=64 -D_LARGEFILE64_SOURCE -D_XOPEN_SOURCE=500 
> -D_BSD_SOURCE -D_SVID_SOURCE -D_DEFAULT_SOURCE -DENABLE_RESOLUTIONKMS 
> -Dvmblock_fuse -U_XOPEN_SOURCE -D_XOPEN_SOURCE=600 -DUSERLEVEL 
> -D_FILE_OFFSET_BITS=64 -I/usr/include/fuse3  -I/usr/include/glib-2.0 
> -I/usr/lib/x86_64-linux-gnu/glib-2.0/include -I../modules/shared/vmblock -I. 
> -fPIC -Wno-error=deprecated-declarations -Wno-error=address-of-packed-member 
> -Wno-nonnull -g -O2 -ffile-prefix-map=/<>=. 
> -fstack-protector-strong -Wformat -Werror=format-security -Wall -Werror 
> -Wno-pointer-sign -Wno-unused-value -fno-strict-aliasing -Wno-unknown-pragmas 
> -Wno-uninitialized -Wno-deprecated-declarations -Wno-unused-const-variable 
> -Wno-unused-but-set-variable -c -o stubs.o `test -f 
> '../modules/shared/vmblock/stubs.c' || echo 
> './'`../modules/shared/vmblock/stubs.c
> In file included from /usr/include/fuse3/fuse_common.h:17,
>  from /usr/include/fuse3/fuse.h:19,
>  from fsops.h:46,
>  from main.c:28:
> /usr/include/fuse3/fuse_config.h:42: error: "PACKAGE_VERSION" redefined 
> [-Werror]
>42 | #define PACKAGE_VERSION "3.13.1"
>   | 
> : note: this is the location of the previous definition
> cc1: all warnings being treated as errors
> make[2]: *** [Makefile:582: main.o] Error 1


The full build log is available from:
http://qa-logs.debian.net/2023/02/16/open-vm-tools_12.1.5-3_unstable.log

All bugs filed during this archive rebuild are listed at:
https://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=ftbfs-20230216;users=lu...@debian.org
or:
https://udd.debian.org/bugs/?release=na=ign=7=7=only=ftbfs-20230216=lu...@debian.org=1=1=1=1#results

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

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

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

Bug#1031439: gcc-sh-elf: FTBFS: make[6]: *** No rule to make target '../libsframe/libsframe.la', needed by 'libbfd.la'. Stop.

[Lucas Nussbaum]

Source: gcc-sh-elf
Version: 4
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20230216 ftbfs-bookworm

Hi,

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


Relevant part (hopefully):
> make[6]: Entering directory '/<>/bld/bfd/po'
> make[6]: Nothing to be done for 'all'.
> make[6]: Leaving directory '/<>/bld/bfd/po'
> /bin/sh ./libtool --tag=CC --tag=disable-static  --mode=link 
> x86_64-linux-gnu-gcc -Wall -fcf-protection -g -O2 
> -ffile-prefix-map=/<>=. -fstack-protector-strong 
> -Wc,-static-libgcc  -module -avoid-version -bindir /usr/libexec/gcc/sh-elf/12 
> -Wl,--version-script=../../src/lto-plugin/lto-plugin.map-Xcompiler 
> '-static-libstdc++' -Xcompiler '-static-libgcc' '-Wl,-z,relro' '-Wl,-z,now' 
> -o liblto_plugin.la -rpath /usr/libexec/gcc/sh-elf/12 lto-plugin.lo  
> -Wc,../libiberty/pic/libiberty.a 
> yes
> checking whether the compiler supports the __inline keyword... make[6]: 
> Entering directory '/<>/bld/bfd'
> rm -f bfd-tmp.h
> cp bfd-in3.h bfd-tmp.h
> /bin/sh ../../src/bfd/../move-if-change bfd-tmp.h bfd.h
> rm -f bfd-tmp.h
> touch stmp-bfd-h
> rm -f tofiles
> make[6]: *** No rule to make target '../libsframe/libsframe.la', needed by 
> 'libbfd.la'.  Stop.
> make[6]: *** Waiting for unfinished jobs
> f=""; \
> for i in elf32-sh.lo elf-vxworks.lo elf32.lo elf.lo elflink.lo elf-attrs.lo 
> elf-strtab.lo elf-eh-frame.lo elf-sframe.lo dwarf1.lo dwarf2.lo coff-sh.lo 
> cofflink.lo coffgen.lo elf32-gen.lo plugin.lo cpu-sh.lo  archive64.lo ; do \
>   case " $f " in \
> *" $i "*) ;; \
> *) f="$f $i" ;; \
>   esac ; \
> done ; \
> echo $f > tofiles
> /bin/sh ../../src/bfd/../move-if-change tofiles ofiles
> libtool: link: x86_64-linux-gnu-gcc -shared  -fPIC -DPIC  .libs/lto-plugin.o  
>   -static-libgcc -Wl,--version-script=../../src/lto-plugin/lto-plugin.map 
> -static-libstdc++ -static-libgcc -Wl,-z -Wl,relro -Wl,-z -Wl,now 
> ../libiberty/pic/libiberty.a   -Wl,-soname -Wl,liblto_plugin.so -o 
> .libs/liblto_plugin.so
> touch stamp-ofiles
> rm -f libcpp.a
> make[6]: Leaving directory '/<>/bld/bfd'
> x86_64-linux-gnu-ar cru libcpp.a charset.o directives.o errors.o expr.o 
> files.o identifiers.o init.o lex.o line-map.o macro.o mkdeps.o pch.o symtab.o 
> traditional.o
> make[5]: *** [Makefile:1955: all-recursive] Error 1


The full build log is available from:
http://qa-logs.debian.net/2023/02/16/gcc-sh-elf_4_unstable.log

All bugs filed during this archive rebuild are listed at:
https://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=ftbfs-20230216;users=lu...@debian.org
or:
https://udd.debian.org/bugs/?release=na=ign=7=7=only=ftbfs-20230216=lu...@debian.org=1=1=1=1#results

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

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

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

Bug#1031437: pandas: FTBFS: /usr/lib/python3/dist-packages/dateutil/zoneinfo/__init__.py:26: UserWarning: I/O error(2): No such file or directory

[Lucas Nussbaum]

Source: pandas
Version: 1.5.3+dfsg-1
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20230216 ftbfs-bookworm

Hi,

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


Relevant part (hopefully):
> _ test_expanding_apply_consistency_sum_nans[all_data17-2-sum] 
> __
> request =  test_expanding_apply_consistency_sum_nans[all_data17-2-sum]>>
> all_data =  0
> 0  NaN
> 1  1.0
> 2  NaN
> 3  3.0
> 4  2.0, min_periods = 2
> f = 
> 
> @pytest.mark.parametrize("f", [lambda v: Series(v).sum(), np.nansum, 
> np.sum])
> def test_expanding_apply_consistency_sum_nans(request, all_data, 
> min_periods, f):
> if f is np.sum:
> if not no_nans(all_data) and not (
> all_na(all_data) and not all_data.empty and min_periods > 0
> ):
> request.node.add_marker(
> pytest.mark.xfail(reason="np.sum has different behavior 
> with NaNs")
> )
> expanding_f_result = all_data.expanding(min_periods=min_periods).sum()
> expanding_apply_f_result = 
> all_data.expanding(min_periods=min_periods).apply(
> func=f, raw=True
> )
> >   tm.assert_equal(expanding_f_result, expanding_apply_f_result)
> 
> pandas/tests/window/moments/test_moments_consistency_expanding.py:29: 
> _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ 
> _ 
> pandas/_libs/testing.pyx:52: in pandas._libs.testing.assert_almost_equal
> cpdef assert_almost_equal(a, b,
> _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ 
> _ 
> 
> >   raise_assert_detail(obj, msg, lobj, robj, index_values=index_values)
> E   AssertionError: DataFrame.iloc[:, 0] (column name="0") are different
> E   
> E   DataFrame.iloc[:, 0] (column name="0") values are different (40.0 %)
> E   [index]: [0, 1, 2, 3, 4]
> E   [left]:  [nan, nan, nan, 4.0, 6.0]
> E   [right]: [nan, nan, nan, nan, nan]
> 
> pandas/_libs/testing.pyx:167: AssertionError
> - generated xml file: 
> /<>/.pybuild/cpython3_3.11/build/test-data.xml -
> = slowest 30 durations 
> =
> 0.69s call 
> .pybuild/cpython3_3.11/build/pandas/tests/window/test_apply.py::test_center_reindex_frame[False]
> 0.32s call 
> .pybuild/cpython3_3.11/build/pandas/tests/groupby/test_timegrouper.py::TestGroupBy::test_timegrouper_with_reg_groups
> 0.24s call 
> .pybuild/cpython3_3.11/build/pandas/tests/window/test_apply.py::test_time_rule_frame[False]
> 0.18s call 
> .pybuild/cpython3_3.11/build/pandas/tests/window/test_apply.py::test_frame[False]
> 0.12s call 
> .pybuild/cpython3_3.11/build/pandas/tests/groupby/test_timegrouper.py::TestGroupBy::test_groupby_with_timegrouper
> 0.07s call 
> .pybuild/cpython3_3.11/build/pandas/tests/groupby/test_timegrouper.py::TestGroupBy::test_groupby_apply_timegrouper_with_nat_apply_squeeze
> 0.07s call 
> .pybuild/cpython3_3.11/build/pandas/tests/window/test_apply.py::test_center_reindex_series[False]
> 0.06s call 
> .pybuild/cpython3_3.11/build/pandas/tests/window/test_apply.py::test_min_periods[False-None-0]
> 0.06s call 
> .pybuild/cpython3_3.11/build/pandas/tests/window/test_apply.py::test_min_periods[False-1-0]
> 0.05s call 
> .pybuild/cpython3_3.11/build/pandas/tests/window/test_apply.py::test_nans[False]
> 0.04s call 
> .pybuild/cpython3_3.11/build/pandas/tests/window/test_apply.py::test_time_rule_frame[True]
> 0.04s call 
> .pybuild/cpython3_3.11/build/pandas/tests/window/test_apply.py::test_center_reindex_frame[True]
> 0.04s call 
> .pybuild/cpython3_3.11/build/pandas/tests/groupby/test_timegrouper.py::TestGroupBy::test_timegrouper_get_group
> 0.03s call 
> .pybuild/cpython3_3.11/build/pandas/tests/window/test_apply.py::test_min_periods[False-2-0]
> 0.03s call 
> .pybuild/cpython3_3.11/build/pandas/tests/groupby/test_timegrouper.py::TestGroupBy::test_timegrouper_with_reg_groups_freq[A]
> 0.03s call 
> .pybuild/cpython3_3.11/build/pandas/tests/groupby/test_timegrouper.py::TestGroupBy::test_timegrouper_with_reg_groups_freq[D]
> 0.03s call 
> .pybuild/cpython3_3.11/build/pandas/tests/groupby/test_timegrouper.py::TestGroupBy::test_timegrouper_with_reg_groups_freq[M]
> 0.03s call 
> .pybuild/cpython3_3.11/build/pandas/tests/groupby/test_timegrouper.py::TestGroupBy::test_groupby_groups_datetimeindex_tz
> 0.03s setup
> .pybuild/cpython3_3.11/build/pandas/tests/groupby/test_timegrouper.py::TestGroupBy::test_groupby_apply_timegrouper_with_nat_dict_returns
> 0.03s cal

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

[Lucas Nussbaum]

Source: diffoscope
Version: 235
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20230216 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 '/<>/doc'
> { cat diffoscope.h2m.0; cat ../README.rst | \
>   sed -e '/^\.\. raw:: /d' -e '/^\.\. image:: /d' -e '/ :target: /d' | tee 
> out.txt | \
>   rst2man -q --no-doc-title | \
>   sed -e 's,^ \\- ,,' -e 's,^\[,\\[char91],g' -e 's,\.TH *"" "" "",,g' \
>   -e 's,bin/diffoscope,diffoscope,g' \
>   -e 's,\.SH \(.*\),[\1],g' -e 's,\[diffoscope\],[DESCRIPTION],gi'; } > 
> "diffoscope.h2m"
> help2man --version-string=$(cd .. && python3 setup.py -V) ../bin/diffoscope 
> -N --include="diffoscope.h2m" | \
>   sed -e '/end_of_description_header/,/positional arguments/{d}' > 
> "diffoscope.1"
> make[2]: Leaving directory '/<>/doc'
> make[1]: Leaving directory '/<>'
>dh_auto_test -O--buildsystem=pybuild
> I: pybuild pybuild:307: flake8 --config=/dev/null --select=F821
> I: pybuild base:240: cd /<>/.pybuild/cpython3_3.11/build; 
> python3.11 -m pytest -vv -r sxX -l --cov=diffoscope --cov-report=term-missing 
> --cov-report=html
> = test session starts 
> ==
> platform linux -- Python 3.11.2, pytest-7.2.1, pluggy-1.0.0+repack -- 
> /usr/bin/python3.11
> cachedir: .pytest_cache
> rootdir: /<>, configfile: pytest.ini
> plugins: cov-4.0.0
> collecting ... collected 711 items / 1 skipped
> 
> tests/test_diff_mask.py::test_none PASSED[  
> 0%]
> tests/test_diff_mask.py::test_all PASSED [  
> 0%]
> tests/test_diff_mask.py::test_specific PASSED[  
> 0%]
> tests/test_difference.py::test_too_much_input_for_diff PASSED[  
> 0%]
> tests/test_difference.py::test_too_long_diff_block_lines PASSED  [  
> 0%]
> tests/test_difference.py::test_size_updates PASSED   [  
> 0%]
> tests/test_difference.py::test_traverse_heapq PASSED [  
> 0%]
> tests/test_difference.py::test_non_str_arguments_to_source1_source2 PASSED [  
> 1%]
> tests/test_difference.py::test_adjust_diff_context PASSED[  
> 1%]
> tests/test_excludes.py::test_none PASSED [  
> 1%]
> tests/test_excludes.py::test_all PASSED  [  
> 1%]
> tests/test_excludes.py::test_specific PASSED [  
> 1%]
> tests/test_excludes.py::test_specific_case PASSED[  
> 1%]
> tests/test_excludes.py::test_multiple PASSED [  
> 1%]
> tests/test_excludes.py::test_nomatch PASSED  [  
> 2%]
> tests/test_excludes.py::test_wildcard PASSED [  
> 2%]
> tests/test_main.py::test_non_existing_files PASSED   [  
> 2%]
> tests/test_main.py::test_non_existing_left_with_new_file PASSED  [  
> 2%]
> tests/test_main.py::test_non_existing_right_with_new_file PASSED [  
> 2%]
> tests/test_main.py::test_non_existing_files_with_new_file PASSED [  
> 2%]
> tests/test_main.py::test_remove_temp_files_on_sigterm PASSED [  
> 2%]
> tests/test_main.py::test_ctrl_c_handling PASSED  [  
> 3%]
> tests/test_main.py::test_no_differences PASSED   [  
> 3%]
> tests/test_main.py::test_no_differences_directories PASSED   [  
> 3%]
> tests/test_main.py::test_list_tools PASSED   [  
> 3%]
> tests/test_main.py::test_list_missing_tools PASSED   [  
> 3%]
> tests/test_main.py::test_profiling PASSED[  
> 3%]
> tests/test_main.py::test_non_unicode_filename PASSED [  
> 3%]
> tests/test_main.py::test_help PASSED [  
> 4%]
> tests/test_main.py::test_usage PASSED[  
> 4%]
> tests/test_presenters.py::test_text_option_is_default PASSED [  
> 4%]
> tests/test_presenters.py::test_text_proper_indentation PASSED[  
> 4%]
> tests/test_presenters.py::test_text_option_color PASSED  [  
> 4%]
> tests/test_presenters.py::test_text_option_with_file PASSED  [  
> 4%]
> tests/test_presenters.py::test_text_option_with_stdout PASSED[  
> 4%]
> tests/test_presenters.py::

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

[Lucas Nussbaum]

Source: python-inotify
Version: 0.2.10-4
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20230216 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' --reruns 3 --reruns-delay 1
> = test session starts 
> ==
> platform linux -- Python 3.11.2, pytest-7.2.1, pluggy-1.0.0+repack
> rootdir: /<>
> plugins: rerunfailures-10.2
> collected 9 items / 3 deselected / 6 selected
> 
> tests/test_inotify.py .s...R 
> [100%]R [100%]R [100%]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.__rea

Bug#1031436: ubuntu-dev-tools: FTBFS: make[1]: *** [debian/rules:10: override_dh_auto_test] Error 1

[Lucas Nussbaum]

Source: ubuntu-dev-tools
Version: 0.192
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20230216 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 '/<>'
> ./run-linters
> Running black...
> --- build/scripts-3.11/grep-merges2023-02-17 01:30:48.860507 +
> +++ build/scripts-3.11/grep-merges2023-02-17 01:30:49.805230 +
> @@ -52,11 +52,10 @@
>  "universe",
>  "universe-manual",
>  "multiverse",
>  "multiverse-manual",
>  ):
> -
>  url = f"https://merges.ubuntu.com/{component}.json;
>  try:
>  headers, page = Http().request(url)
>  except HttpLib2Error as e:
>  Logger.exception(e)
> would reformat build/scripts-3.11/grep-merges
> --- /<>/ubuntutools/misc.py  2023-02-01 11:45:15 +
> +++ /<>/ubuntutools/misc.py  2023-02-17 01:30:49.837949 +
> @@ -242,11 +242,11 @@
>  filesize = path.stat().st_size
>  if size and size != filesize:
>  Logger.error("File %s incorrect size, got %s expected %s", path, 
> filesize, size)
>  return False
>  
> -for (alg, checksum) in checksums.items():
> +for alg, checksum in checksums.items():
>  hash_ = hashlib.new(alg)
>  with path.open("rb") as f:
>  while True:
>  block = f.read(hash_.block_size)
>  if len(block) == 0:
> would reformat /<>/ubuntutools/misc.py
> --- grep-merges   2023-02-01 11:45:15 +
> +++ grep-merges   2023-02-17 01:30:50.160956 +
> @@ -52,11 +52,10 @@
>  "universe",
>  "universe-manual",
>  "multiverse",
>  "multiverse-manual",
>  ):
> -
>  url = f"https://merges.ubuntu.com/{component}.json;
>  try:
>  headers, page = Http().request(url)
>  except HttpLib2Error as e:
>  Logger.exception(e)
> would reformat grep-merges
> --- build/scripts-3.11/ubuntu-upload-permission   2023-02-17 
> 01:30:48.864507 +
> +++ build/scripts-3.11/ubuntu-upload-permission   2023-02-17 
> 01:30:50.219040 +
> @@ -89,11 +89,10 @@
>  component = spph.getComponent()
>  if args.list_uploaders and (
>  pocket != "Release"
>  or series.status in ("Experimental", "Active Development", 
> "Pre-release Freeze")
>  ):
> -
>  component_uploader = 
> archive.getUploadersForComponent(component_name=component)[0]
>  Logger.info("All upload permissions for %s:", args.package)
>  Logger.info("")
>  Logger.info("Component (%s)", component)
>  Logger.info("%s", "=" * len(component))
> would reformat build/scripts-3.11/ubuntu-upload-permission
> --- ubuntu-upload-permission  2023-02-01 11:45:15 +
> +++ ubuntu-upload-permission  2023-02-17 01:30:50.476410 +
> @@ -89,11 +89,10 @@
>  component = spph.getComponent()
>  if args.list_uploaders and (
>  pocket != "Release"
>  or series.status in ("Experimental", "Active Development", 
> "Pre-release Freeze")
>  ):
> -
>  component_uploader = 
> archive.getUploadersForComponent(component_name=component)[0]
>  Logger.info("All upload permissions for %s:", args.package)
>  Logger.info("")
>  Logger.info("Component (%s)", component)
>  Logger.info("%s", "=" * len(component))
> would reformat ubuntu-upload-permission
> --- /<>/ubuntutools/lp/lpapicache.py 2023-02-01 11:45:15 
> +
> +++ /<>/ubuntutools/lp/lpapicache.py 2023-02-17 
> 01:30:50.905615 +
> @@ -410,11 +410,11 @@
>  def binaryFileProperties(self, filename_or_url):
>  if not self._binary_prop_dict:
>  urls = self.binaryFileUrls()
>  props = self.getBinaryProperties()
>  self._binary_prop_dict = dict(zip(urls, props))
> -for (key, value) in copy(self._binary_prop_dict).items():
> +for key, value in copy(self._binary_prop_dict).items():
>      filename = os.path.basename(urlparse(key).path)
>  self._binary_prop_dict[filename] = value
>  return self._binary_prop_dict.get(filename_or_url, {})
>  
>  
> w

Bug#1031434: conda-package-handling: FTBFS: dh_auto_test: error: pybuild --test --test-pytest -i python{version} -p 3.11 returned exit code 13

[Lucas Nussbaum]

Source: conda-package-handling
Version: 2.0.1-2
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20230216 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/conda_package_handling
> copying src/conda_package_handling/__init__.py -> 
> /<>/.pybuild/cpython3_3.11/build/conda_package_handling
> copying src/conda_package_handling/tarball.py -> 
> /<>/.pybuild/cpython3_3.11/build/conda_package_handling
> copying src/conda_package_handling/cli.py -> 
> /<>/.pybuild/cpython3_3.11/build/conda_package_handling
> copying src/conda_package_handling/__main__.py -> 
> /<>/.pybuild/cpython3_3.11/build/conda_package_handling
> copying src/conda_package_handling/api.py -> 
> /<>/.pybuild/cpython3_3.11/build/conda_package_handling
> copying src/conda_package_handling/interface.py -> 
> /<>/.pybuild/cpython3_3.11/build/conda_package_handling
> copying src/conda_package_handling/exceptions.py -> 
> /<>/.pybuild/cpython3_3.11/build/conda_package_handling
> copying src/conda_package_handling/conda_fmt.py -> 
> /<>/.pybuild/cpython3_3.11/build/conda_package_handling
> copying src/conda_package_handling/validate.py -> 
> /<>/.pybuild/cpython3_3.11/build/conda_package_handling
> copying src/conda_package_handling/streaming.py -> 
> /<>/.pybuild/cpython3_3.11/build/conda_package_handling
> copying src/conda_package_handling/utils.py -> 
> /<>/.pybuild/cpython3_3.11/build/conda_package_handling
>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.2, pytest-7.2.1, pluggy-1.0.0+repack
> rootdir: /<>, configfile: setup.cfg
> plugins: mock-3.8.2
> collected 39 items / 1 error
> 
>  ERRORS 
> 
>  ERROR collecting .pybuild/cpython3_3.11/build/tests/test_interface.py 
> _
> ImportError while importing test module 
> '/<>/.pybuild/cpython3_3.11/build/tests/test_interface.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_interface.py:12: in 
> from conda_package_handling.conda_fmt import CondaFormat_v2
> conda_package_handling/conda_fmt.py:15: in 
> import zstandard
> /usr/lib/python3/dist-packages/zstandard/__init__.py:39: in 
> from .backend_c import *  # type: ignore
> E   ImportError: zstd C API versions mismatch; Python bindings were not 
> compiled/linked against expected zstd version (10504 returned by the lib, 
> 10502 hardcoded in zstd headers, 10502 hardcoded in the cext)
> === warnings summary 
> ===
> ../../../../../../usr/lib/python3/dist-packages/_pytest/config/__init__.py:1294
>   /usr/lib/python3/dist-packages/_pytest/config/__init__.py:1294: 
> PytestConfigWarning: Unknown config option: env
>   
> self._warn_or_fail_if_strict(f"Unknown config option: {key}\n")
> 
> ../../../../../../usr/lib/python3/dist-packages/conda_package_streaming/package_streaming.py:19
>   
> /usr/lib/python3/dist-packages/conda_package_streaming/package_streaming.py:19:
>  UserWarning: zstandard could not be imported. Running without .conda support.
> warnings.warn("zstandard could not be imported. Running without .conda 
> support.")
> 
> conda_package_handling/api.py:29
>   
> /<>/.pybuild/cpython3_3.11/build/conda_package_handling/api.py:29:
>  UserWarning: Install zstandard Python bindings for .conda support
> _warnings.warn("Install zstandard Python bindings for .conda support")
> 
> -- Docs: https://docs.pytest.org/en/stable/how-to/capture-warnings.html
> - generated xml file: /<>/.pybuild/cpython3_3.11/build/junit.xml 
> -
> === short test summary info 
> =

Bug#1031432: mediaelement: FTBFS: FileNotFoundError: [Errno 2] No such file or directory: '../build/mediaelement.min.js'

[Lucas Nussbaum]

Source: mediaelement
Version: 2.15.1+dfsg-3
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20230216 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 '/<>'
> cd /<>/src && python3 ./Builder.py
> java.util.MissingResourceException: Can't find bundle for base name 
> com.google.javascript.rhino.head.resources.Messages, locale en
>   at 
> java.base/java.util.ResourceBundle.throwMissingResourceException(ResourceBundle.java:2045)
>   at 
> java.base/java.util.ResourceBundle.getBundleImpl(ResourceBundle.java:1683)
>   at 
> java.base/java.util.ResourceBundle.getBundleImpl(ResourceBundle.java:1586)
>   at 
> java.base/java.util.ResourceBundle.getBundleImpl(ResourceBundle.java:1549)
>   at java.base/java.util.ResourceBundle.getBundle(ResourceBundle.java:932)
>   at 
> com.google.javascript.rhino.head.ScriptRuntime$DefaultMessageProvider.getMessage(ScriptRuntime.java:4521)
>   at 
> com.google.javascript.rhino.head.ScriptRuntime.getMessage(ScriptRuntime.java:4501)
>   at 
> com.google.javascript.rhino.head.ScriptRuntime.getMessage0(ScriptRuntime.java:4446)
>   at 
> com.google.javascript.jscomp.RhinoErrorReporter.(RhinoErrorReporter.java:84)
>   at 
> com.google.javascript.jscomp.RhinoErrorReporter.(RhinoErrorReporter.java:32)
>   at 
> com.google.javascript.jscomp.RhinoErrorReporter$OldRhinoErrorReporter.(RhinoErrorReporter.java:162)
>   at 
> com.google.javascript.jscomp.RhinoErrorReporter$OldRhinoErrorReporter.(RhinoErrorReporter.java:158)
>   at 
> com.google.javascript.jscomp.RhinoErrorReporter.forOldRhino(RhinoErrorReporter.java:119)
>   at com.google.javascript.jscomp.Compiler.(Compiler.java:176)
>   at 
> com.google.javascript.jscomp.CommandLineRunner.createCompiler(CommandLineRunner.java:858)
>   at 
> com.google.javascript.jscomp.AbstractCommandLineRunner.doRun(AbstractCommandLineRunner.java:741)
>   at 
> com.google.javascript.jscomp.AbstractCommandLineRunner.run(AbstractCommandLineRunner.java:380)
>   at 
> com.google.javascript.jscomp.CommandLineRunner.main(CommandLineRunner.java:980)
> java.util.MissingResourceException: Can't find bundle for base name 
> com.google.javascript.rhino.head.resources.Messages, locale en
>   at 
> java.base/java.util.ResourceBundle.throwMissingResourceException(ResourceBundle.java:2045)
>   at 
> java.base/java.util.ResourceBundle.getBundleImpl(ResourceBundle.java:1683)
>   at 
> java.base/java.util.ResourceBundle.getBundleImpl(ResourceBundle.java:1586)
>   at 
> java.base/java.util.ResourceBundle.getBundleImpl(ResourceBundle.java:1549)
>   at java.base/java.util.ResourceBundle.getBundle(ResourceBundle.java:932)
>   at 
> com.google.javascript.rhino.head.ScriptRuntime$DefaultMessageProvider.getMessage(ScriptRuntime.java:4521)
>   at 
> com.google.javascript.rhino.head.ScriptRuntime.getMessage(ScriptRuntime.java:4501)
>   at 
> com.google.javascript.rhino.head.ScriptRuntime.getMessage0(ScriptRuntime.java:4446)
>   at 
> com.google.javascript.jscomp.RhinoErrorReporter.(RhinoErrorReporter.java:84)
>   at 
> com.google.javascript.jscomp.RhinoErrorReporter.(RhinoErrorReporter.java:32)
>   at 
> com.google.javascript.jscomp.RhinoErrorReporter$OldRhinoErrorReporter.(RhinoErrorReporter.java:162)
>   at 
> com.google.javascript.jscomp.RhinoErrorReporter$OldRhinoErrorReporter.(RhinoErrorReporter.java:158)
>   at 
> com.google.javascript.jscomp.RhinoErrorReporter.forOldRhino(RhinoErrorReporter.java:119)
>   at com.google.javascript.jscomp.Compiler.(Compiler.java:176)
>   at 
> com.google.javascript.jscomp.CommandLineRunner.createCompiler(CommandLineRunner.java:858)
>   at 
> com.google.javascript.jscomp.AbstractCommandLineRunner.doRun(AbstractCommandLineRunner.java:741)
>   at 
> com.google.javascript.jscomp.AbstractCommandLineRunner.run(AbstractCommandLineRunner.java:380)
>   at 
> com.google.javascript.jscomp.CommandLineRunner.main(CommandLineRunner.java:980)
> building MediaElement.js
> building MediaElementPlayer.js
> Minifying JavaScript
> Traceback (most recent call last):
>   File "/<>/src/./Builder.py", line 101, in 
> addHeader('js/me-header.js', '../build/' + me_filename + '.min.js')
>   File "/<>/src/./Builder.py", line 89, in addHeader
> tmp_file = open(filename)
>^^
> FileNotFoundError: [Errno 2] No such file or directory: 
> '../build/mediaelement.min.js'
> make[1]: *** [debian/rules:6: execute_before_dh_auto_build] Error

Bug#1031431: debian-installer-netboot-images: FTBFS: Building 20220917, but bookworm has 20230207, failing the build

[Lucas Nussbaum]

Source: debian-installer-netboot-images
Version: 20220917+rebuild1
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20230216 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 '/<>'
> if ! ./get-images.sh amd64; then \
>   if [ -n "" ]; then \
>   echo; echo; echo; \
>   echo "Version not found in bookworm, falling back to "; \
>   echo; echo; echo; \
>   sleep 5; \
>   DISTRIBUTION= ./get-images.sh amd64; \
>   else \
>   echo "Version not found in bookworm, no fallback defined"; \
>   exit 1; \
>   fi \
> fi
> --2023-02-17 01:24:15--  
> http://127.0.0.1:12990/debian/dists/bookworm/Release.gpg
> Connecting to 127.0.0.1:12990... connected.
> HTTP request sent, awaiting response... 200 OK
> Length: 1601 (1.6K) [text/plain]
> Saving to: ‘/<>/Release.gpg’
> 
>  0K . 100%  177M=0s
> 
> 2023-02-17 01:24:15 (177 MB/s) - ‘/<>/Release.gpg’ saved 
> [1601/1601]
> 
> --2023-02-17 01:24:15--  http://127.0.0.1:12990/debian/dists/bookworm/Release
> Connecting to 127.0.0.1:12990... connected.
> HTTP request sent, awaiting response... 200 OK
> Length: 171552 (168K) [text/plain]
> Saving to: ‘/<>/Release’
> 
>  0K .. .. .. .. .. 29%  329M 0s
> 50K .. .. .. .. .. 59%  276M 0s
>100K .. .. .. .. .. 89% 60.2M 0s
>150K .. ...100% 
> 13.9M=0.002s
> 
> 2023-02-17 01:24:15 (69.1 MB/s) - ‘/<>/Release’ saved 
> [171552/171552]
> 
> gpgv: Signature made Thu Feb 16 20:13:29 2023 UTC
> gpgv:using RSA key 0146DC6D4A0B2914BDED34DB648ACFD622F3D138
> gpgv: Good signature from "Debian Archive Automatic Signing Key (10/buster) 
> "
> gpgv: Signature made Thu Feb 16 20:14:07 2023 UTC
> gpgv:using RSA key A7236886F3CCCAAD148A27F80E98404D386FA1D9
> gpgv: Good signature from "Debian Archive Automatic Signing Key (11/bullseye) 
> "
> --2023-02-17 01:24:15--  
> http://127.0.0.1:12990/debian/dists/bookworm/main/binary-amd64/Packages.xz
> Connecting to 127.0.0.1:12990... connected.
> HTTP request sent, awaiting response... 200 OK
> Length: 9040064 (8.6M) [text/plain]
> Saving to: ‘amd64.Packages.xz’
> 
>  0K .. .. .. .. ..  0%  191M 0s
> 50K .. .. .. .. ..  1% 83.8M 0s
>100K .. .. .. .. ..  1%  109M 0s
>150K .. .. .. .. ..  2% 21.6M 0s
>200K .. .. .. .. ..  2% 51.3M 0s
>250K .. .. .. .. ..  3%  110M 0s
>300K .. .. .. .. ..  3%  113M 0s
>350K .. .. .. .. ..  4%  114M 0s
>400K .. .. .. .. ..  5%  100M 0s
>450K .. .. .. .. ..  5% 89.4M 0s
>500K .. .. .. .. ..  6% 99.9M 0s
>550K .. .. .. .. ..  6% 73.4M 0s
>600K .. .. .. .. ..  7%  174M 0s
>650K .. .. .. .. ..  7%  120M 0s
>700K .. .. .. .. ..  8%  133M 0s
>750K .. .. .. .. ..  9% 13.4M 0s
>800K .. .. .. .. ..  9%  102M 0s
>850K .. .. .. .. .. 10%  141M 0s
>900K .. .. .. .. .. 10%  106M 0s
>950K .. .. .. .. .. 11%  161M 0s
>   1000K .. .. .. .. .. 11% 47.5M 0s
>   1050K .. .. .. .. .. 12%  132M 0s
>   1100K .. .. .. .. .. 13% 23.4M 0s
>   1150K .. .. .. .. .. 13%  118M 0s
>   1200K .. .. .. .. .. 14%  124M 0s
>   1250K .. .. .. .. .. 14% 36.5M 0s
>   1300K .. .. .. .. .. 15% 29.8

Bug#1031399: rsyslog: Log rotation broken on non-systemd systems

[Matthew Vernon]

Hi,

I've provided a minimal patch; given this is a Debian-specific file and 
not something you're going to have to deal with upstream about, is there 
any chance of you applying it for bookworm, please?


Log rotation isn't just about disk filling, other systems rely on its 
correct operation (hence my view this is RC) - I picked up on this when 
I realised that fail2ban had stopped working for ssh! It looks in 
/var/log/auth.log for entries, and that file was empty because of this 
failure.


Thank you for your consideration,

Matthew

From 4f17fb24be2d1f34a772298258f2352d864e7a75 Mon Sep 17 00:00:00 2001
From: Matthew Vernon 
Date: Fri, 17 Feb 2023 06:39:43 +
Subject: [PATCH] attempt to rotate on non-systemd systems (Closes: #1031399)

On non-systemd systems, /etc/init.d/rsyslog is sometimes available; in
those cases, use it (via invoke-rc.d) to do log rotation.
---
 debian/rsyslog-rotate | 2 ++
 1 file changed, 2 insertions(+)

diff --git a/debian/rsyslog-rotate b/debian/rsyslog-rotate
index ef3954b1..143523ab 100755
--- a/debian/rsyslog-rotate
+++ b/debian/rsyslog-rotate
@@ -2,4 +2,6 @@
 
 if [ -d /run/systemd/system ]; then
 systemctl kill -s HUP rsyslog.service
+elif [ -x /etc/init.d/rsyslog ]; then
+invoke-rc.d rsyslog rotate > /dev/null
 fi
-- 
2.39.1

Bug#1020387: dictionaries-common: Consensus regarding the packaging of the Qt WebEngine hunspell binary dictionaries

[Rene Engelhard]

Am 16.02.23 um 21:37 schrieb Soren Stoutner:

It would be fine with me if Chromium provided the virtual package and symlink
used to build the .bdic files.  My only concern is that it is important that
these always exist in Stable and Old Stable going forward.


Yes. Not only for backporting but as soon as e.g. scowl will use it the 
whole thing will be in a key package build-dependency chain 
(libreoffice) as hunspell-en-us is used as part of its tests. Probably 
even more.


Basically any hunspell dictionary then requires chromium to be there.


On and off ("shipping dictionaries whether chromium is in a good state 
or not") is bad.




   Otherwise, it
makes backporting Hunspell language packages more difficult (not impossible,
just more time consuming for the language package maintainers).


No hunspell package really needs backporting at all, they are arch all 
and can just be installed. :)


And be it with dpkg -i :-)


Regards,


Rene



On Thursday, February 16, 2023 1:19:45 PM MST Andres Salomon wrote:

Related to this - we got approval for chromium to ship in bookworm
(#1004441). That doesn't necessarily mean it'll be in future releases
(trixie or whatever), of course, but if it's easier for the dependency
chain; I'm open to discussing having chromium provide it.

I haven't followed all of this very long thread, so it may be
irrelevant at this point. :)

Bug#1031430: golang-github-iovisor-gobpf-dev: error: argument 1 has incompatible type

[Petter Reinholdtsen]

Package: golang-github-iovisor-gobpf-dev
Version: 0.2.0-5
Affects: opensnitch

The opensnitch package fail to build in experimental on arm64.  The
build log for the latter can be found in
https://buildd.debian.org/status/fetch.php?pkg=opensnitch=arm64=1.5.7-3=1676588327=0
 >
and this is the failure:

github.com/google/gopacket/layers
# github.com/iovisor/gobpf/elf
src/github.com/iovisor/gobpf/elf/kernel_version.go:61:61: error: argument 1 has 
incompatible type
   61 | releaseString := strings.Trim(utsnameStr(buf.Release[:]), 
"\x00")
  | ^
golang.org/x/net/internal/timeseries

I am not sure, but this seem to be a problem with
golang-github-iovisor-gobpf-dev.  Please reassign if it is the wrong
package.

-- 
Happy hacking
Petter Reinholdtsen

Bug#1031429: golang-google-grpc-dev: error: reference to undefined identifier 'syscall.SO_SNDTIMEO'

[Petter Reinholdtsen]

Package: golang-google-grpc-dev
Version: 1.33.3-2
Affects: opensnitch

The opensnitch package fail to build in experimental on armhf.  The
build log for the latter can be found in
https://buildd.debian.org/status/fetch.php?pkg=opensnitch=armhf=1.5.7-3=1676591279=0
 >
and this is the failure:

google.golang.org/grpc/internal/binarylog
# google.golang.org/grpc/internal/channelz
src/google.golang.org/grpc/internal/channelz/types_linux.go:47:82: error: 
reference to undefined identifier 'syscall.SO_SNDTIMEO'
   47 | if v, err := unix.GetsockoptTimeval(int(fd), 
syscall.SOL_SOCKET, syscall.SO_SNDTIMEO); err == nil {
  | 
 ^
google.golang.org/grpc/balancer/grpclb/state

I am not sure, but this seem to be a problem with
golang-google-grpc-dev.  Please reassign if it is the wrong package.
-- 
Happy hacking
Petter Reinholdtsen

Bug#1031428: repowerd: FTBFS with LTO enabled

[Steve Langasek]

Package: repowerd
Version: 2022.01-3
Severity: normal
Tags: patch
User: ubuntu-de...@lists.ubuntu.com
Usertags: origin-ubuntu lunar ubuntu-patch

Hi Mike,

The repowerd package fails to build from source when LTO is enabled, as seen
in Ubuntu on those archs that use LTO:

[...]
/usr/bin/c++ -g -O2 -ffile-prefix-map=/<>=. -flto=auto 
-ffat-lto-objects -fstack-protector-strong -Wformat -Werror=format-security 
-fdebug-prefix-map=/<>=/usr/src/repowerd-2022.01-3 -Wdate-time 
-D_FORTIFY_SOURCE=2 -g -pthread -std=c++14 -Werror -Wall -Wnon-virtual-dtor 
-Wextra -pedantic -Wl,-Bsymbolic-functions -flto=auto -ffat-lto-objects 
-Wl,-z,relro -Wl,-z,now -rdynamic CMakeFiles/repowerd.dir/main.cpp.o -o 
../bin/repowerd  core/librepowerd-core.a adapters/librepowerd-adapters.a 
librepowerd-default-daemon-config.a core/librepowerd-core.a 
adapters/librepowerd-adapters.a adapters/libsuspend/libsuspend.a 
-L/usr/lib/x86_64-linux-gnu -lgio-2.0 -lgobject-2.0 -lglib-2.0 -lgio-2.0 
-lgobject-2.0 -lglib-2.0 -lgio-2.0 -lgobject-2.0 -lglib-2.0 -lgio-2.0 
-lgobject-2.0 -lglib-2.0 
[...]
In member function ‘__ct ’,
inlined from ‘__ct ’ at 
/usr/src/repowerd-2022.01-3/src/core/handler_registration.cpp:32:7,
inlined from ‘__ct ’ at 
/usr/src/repowerd-2022.01-3/src/default_daemon_config.cpp:65:57,
inlined from ‘register_proximity_handler’ at 
/usr/src/repowerd-2022.01-3/src/default_daemon_config.cpp:116:16:
/usr/include/c++/12/bits/std_function.h:391:17: error: ‘’ may be 
used uninitialized [-Werror=maybe-uninitialized]
  391 | __x._M_manager(_M_functor, __x._M_functor, __clone_functor);
  | ^
[...]

  (https://launchpad.net/ubuntu/+source/repowerd/2022.01-3/+build/24577522)

I have uploaded the attached patch in Ubuntu to fix the build failure there. 
Debian does not yet use LTO by default but it is being discussed, so I'm
upstreaming this patch for your consideration.

Cheers,
-- 
Steve Langasek   Give me a lever long enough and a Free OS
Debian Developer   to set it on, and I can move the world.
Ubuntu Developer   https://www.debian.org/
slanga...@ubuntu.com vor...@debian.org
diff -Nru repowerd-2022.01/debian/rules repowerd-2022.01/debian/rules
--- repowerd-2022.01/debian/rules   2022-07-19 15:23:13.0 -0700
+++ repowerd-2022.01/debian/rules   2023-02-16 21:08:12.0 -0800
@@ -6,7 +6,7 @@
 
 include /usr/share/dpkg/buildflags.mk
 # see FEATURE AREAS in dpkg-buildflags(1)
-export DEB_BUILD_MAINT_OPTIONS = hardening=+all
+export DEB_BUILD_MAINT_OPTIONS = hardening=+all optimize=-lto
 
 %:
dh $@

Bug#1031427: libomemo-c-dev: No version in pkgconf

[Stefan Kropp]

Package: libomemo-c-dev
Version: 0.5.0-2
Severity: normal
X-Debbugs-Cc: stefan.kr...@posteo.de

Dear Maintainer,

libomemo-c doesn't provide a modversion for pkg-config.

--
$ pkg-config --modversion libsignal-protocol-c
2.3.3
$ pkg-config --modversion libomemo-c

--

It seems the reason is Version: @SIGNAL_PROTOCOL_C_VERSION@ here:
https://sources.debian.org/src/libomemo-c/0.5.0-3/src/libomemo-c.pc.in/#L9

--
$ grep ^Version /usr/lib/x86_64-linux-gnu/pkgconfig/libsignal-protocol-c.pc 
Version: 2.3.3
$ grep ^Version /usr/lib/x86_64-linux-gnu/pkgconfig/libomemo-c.pc
Version:
--

The patch should fix the problem:

Index: libomemo-c/src/libomemo-c.pc.in
===
--- libomemo-c.orig/src/libomemo-c.pc.in
+++ libomemo-c/src/libomemo-c.pc.in
@@ -6,7 +6,7 @@ includedir=@INCLUDE_INSTALL_DIR@

 Name: @PROJECT_NAME@
 Description: OMEMO C Library
-Version: @SIGNAL_PROTOCOL_C_VERSION@
+Version: @OMEMO_C_VERSION@

 Requires:
 Libs: -L${libdir} -L${sharedlibdir} -l@PROJECT_NAME@


debuild with patch:
$ grep ^Version 
debian/libomemo-c-dev/usr/lib/x86_64-linux-gnu/pkgconfig/libomemo-c.pc
Version: 0.5.0

I will upload a patch on salsa.

-- System Information:
Debian Release: bookworm/sid
  APT prefers testing-debug
  APT policy: (500, 'testing-debug'), (500, 'unstable'), (500, 'testing'), (1, 
'experimental')
Architecture: amd64 (x86_64)

Kernel: Linux 6.1.0-4-amd64 (SMP w/2 CPU threads; PREEMPT)
Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages libomemo-c-dev depends on:
ii  libomemo-c0  0.5.0-2

libomemo-c-dev recommends no packages.

libomemo-c-dev suggests no packages.

-- no debconf information
Thank you for using reportbug

Bug#1031426: reprepro: update with a pair of components doesn't work as expected

[Arnaud Rebillout]

Package: reprepro
Version: 5.3.1-1
Severity: normal

Dear Maintainer,

Here's a minimal example to demonstrate the problem:

 $ cat conf/distributions
 Codename: my-distro
 Architectures: amd64 source
 Components: non-free
 Update: - update-sid
 Log: my-distro.log
 # don't pack indices for this example
 DebIndices: Packages Release .
 DscIndices: Sources Release .

 $ cat conf/updates
 Name: update-sid
 VerifyRelease: blindtrust
 Method: http://deb.debian.org/debian/
 Suite: unstable
 Components: non-free non-free-firmware>non-free
 FilterSrcList: deinstall updates-filter

 $ cat conf/updates-filter
 atmel-firmware install

In the example above, I create 'my-distro', it has only one component
named 'non-free'. my-distro gets its updates from Debian unstable, from
the two components non-free and non-free-firmware, that are merged into
one component using "non-free-firmware>non-free".

For the sake of the example, my-distro has only one package, it's
atmel-firmware, that comes from the non-free-firmware component in
Debian.

This setup seems to work, at least on the surface:

 $ reprepro update
 Calculating packages to get...
 Getting packages...
 Installing (and possibly deleting) packages...
 Exporting indices...

However, looking a bit deeper, there are 2 things that are not correct:

 $ grep -E -rni '(Package-List|non-free-firmware)' dists/
 dists/my-distro/non-free/binary-amd64/Packages:19:Section: 
non-free-firmware/kernel
 dists/my-distro/non-free/source/Sources:24:Package-List: 
 dists/my-distro/non-free/source/Sources:25: atmel-firmware deb 
non-free-firmware/kernel optional arch=all
 dists/my-distro/non-free/source/Sources:28:Section: non-free-firmware/misc

In the snippet above, we can see that the name of the component is not
updated in the Section and in the Package-List fields (it should be
non-free).

If we decide to also create a Contents file, ie. we add the line:

 Contents: percomponent .

to conf/distributions, then the name of the component is also wrong in
the Contents file:

 $ cat dists/my-distro/non-free/Contents-amd64
 etc/pcmcia/atmel.conf  non-free-firmware/kernel/atmel-firmware
 lib/firmware/atmel_at76c502-wpa.bin
non-free-firmware/kernel/atmel-firmware
 [...]

The issue is for real. I used 'non-free-firmware>non-free' in order to
delay the addition of the new non-free-firmware component in Kali Linux.
However it broke command-not-found, a program that parses the Contents
files and crashes when it encounters an unknown component. Since
command-not-found is run after "apt update" (as a hook or something like
that), in practice it means that "apt update" failed for every Kali
Linux users...

As a quick fix, I could workaround the issue by using this reprepro
trick in conf/updates:

 ListShellHook: sed -e '/^Section: /s/non-free-firmware/non-free/' -e '/^ /s/ 
deb non-free-firmware\// deb non-free\//'

However it's sloppy, I think the issue should be fixed in reprepro.
reprepro should take care of renaming the component in the Sources and
Packages index files, for the fields Section and Package-List. That is
enough to also fix the Contents files.

I can come up with a patch, would you be willing to review it?

Thanks!

Arnaud

Bug#1031425: git-annex-remote-rclone: Update to latest 0.7 release

[James Tocknell]

Package: git-annex-remote-rclone
Version: 0.6-1
Severity: wishlist

Hi, it appears there's a new 0.7 release with a bunch of bug fixes, could it be
included before the freeze?

Thanks!

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

Kernel: Linux 6.1.0-4-amd64 (SMP w/12 CPU threads; PREEMPT)
Locale: LANG=en_AU.UTF-8, LC_CTYPE=en_AU.UTF-8 (charmap=UTF-8) (ignored: LC_ALL 
set to en_AU.UTF-8), LANGUAGE=en_AU:en
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages git-annex-remote-rclone depends on:
ii  git-annex  10.20230126-1
ii  rclone 1.60.1+dfsg-2+b1

git-annex-remote-rclone recommends no packages.

git-annex-remote-rclone suggests no packages.

-- no debconf information

Bug#1031424: add config option to control mixed-mode EFI on x86

[Steve McIntyre]

Package: debian-cd
Version: 3.1.36
Severity: normal

[ Reminder for me ]

I've added support for mixed-mode EFI stuff on amd64 builds. Add an
option to enable/disable it, so that local hack builds don't need both
amd64 and i386 d-i builds to function.

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

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

Versions of packages debian-cd depends on:
ii  apt2.2.4
ii  bc 1.07.1-2+b2
ii  bzip2  1.0.8-4
ii  cpp4:10.2.1-1
ii  curl   7.74.0-1.3+deb11u5
ii  dctrl-tools [grep-dctrl]   2.24-3+b1
ii  dpkg-dev   1.20.12
ii  genisoimage9:1.1.11-3.2
pn  libcompress-zlib-perl  
pn  libdigest-md5-perl 
ii  libdigest-sha-perl 6.02-1+b3
ii  libdpkg-perl   1.20.12
ii  libfile-slurp-perl .32-1
ii  libyaml-libyaml-perl   0.82+repack-1+b1
ii  lynx   2.9.0dev.6-3~deb11u1
ii  make   4.3-4.1
ii  perl [libdigest-sha-perl]  5.32.1-4+deb11u2
ii  tofrodos   1.7.13+ds-5
ii  wget   1.21-1+deb11u1
ii  xorriso1.5.2-1

Versions of packages debian-cd recommends:
ii  dosfstools   4.2-1
ii  hfsutils 3.2.6-15
ii  isolinux 3:6.04~git20190206.bf6db5b4+dfsg1-3
ii  mtools   4.0.26-1
ii  syslinux-common  3:6.04~git20190206.bf6db5b4+dfsg1-3

debian-cd suggests no packages.

-- no debconf information

Bug#802301: dbtoepub: New upstream version available, please update

[Borden]

I think this project is now at github: https://github.com/docbook/xslTNG seems 
Sourceforge has been abandoned for over 17 years.

Bug#1031325: e2fsprogs 1.47.0 introduces a breaking change into Bookworm, breaking grub and making installations of Ubuntu and Debian releases via debootstrap impossible

[Adrian Bunk]

On Thu, Feb 16, 2023 at 05:24:04PM -0500, Theodore Ts'o wrote:
>...
> and that moving forward, we make it the image building tools
> problem if they want to support this highly dubious practice of using
> Debian N+X's mkfs to build images for Debian N.
>...

That's what they already have to do for many years.

But it is also our problem when we ship these image building tools,
to ensure that there are bugs against all of them that get fixed
before the release where the change is present.

> Best release engineering practice is that you use a known, controlled
> build environment, and not whatever random package versions might be
> on your desktop.  While that might be "inconvenient" when building
> packages, we've learned to live with it.  I use sbuild; others might
> use pbuild, or their own custom schroot setup.  But I dare say all
> responsible people doing release engineering use a known build
> environment.  Why should this be any different if you are building
> images --- especially images that you expect *your* users or customers
> to be depending on?
>...

controlled != identical to the target

There are different approaches to this problem with different advantages 
and disadvantages.

It is not unreasonable for an image building tool we ship in bookworm to 
use the host tools of a bookworm x86 server to create a Debian image for 
a buster ARM target.

>   - Ted

cu
Adrian

Bug#1031420: Acknowledgement (libgoogle-glog-dev: CMake config doesn't work out of the box)

[Dima Kogan]

Sorry for the repeated emails. I figured out the problem and fixed it.
This is a bug introduced by usrmerge. The necessary module path was
already being set, but it was trying to find /usr/share/. by a
relative traversal from /lib/. It was expecting /usr/lib, not /lib,
so the relative path had the wrong number of ../ in it. The attached
patch fixes the issue for us: Debian can just use the correct absolute
path. Upstream would presumably need to do something else, but they can
figure it out. Thanks.

--- a/CMakeLists.txt.original	2023-02-16 16:14:41.891485974 -0800
+++ b/CMakeLists.txt	2023-02-16 16:15:57.970855143 -0800
@@ -1034,24 +1034,14 @@
 
 get_filename_component (_PREFIX "${CMAKE_INSTALL_PREFIX}" ABSOLUTE)
 
-# Directory containing the find modules relative to the config install
-# directory.
-file (RELATIVE_PATH glog_REL_CMake_MODULES
-  ${_PREFIX}/${_glog_CMake_INSTALLDIR}
-  ${_PREFIX}/${_glog_CMake_DATADIR}/glog-modules.cmake)
-
-get_filename_component (glog_REL_CMake_DATADIR ${glog_REL_CMake_MODULES}
-  DIRECTORY)
-
-set (glog_FULL_CMake_DATADIR
-  ${CMAKE_CURRENT_BINARY_DIR}/${_glog_CMake_DATADIR})
+set (glog_FULL_CMake_DATADIR /usr/share/glog/cmake)
 
 configure_file (glog-modules.cmake.in
   ${CMAKE_CURRENT_BINARY_DIR}/glog-modules.cmake @ONLY)
 
 install (CODE
 "
-set (glog_FULL_CMake_DATADIR \"\\\${CMAKE_CURRENT_LIST_DIR}/${glog_REL_CMake_DATADIR}\")
+set (glog_FULL_CMake_DATADIR \"/usr/share/glog/cmake\")
 set (glog_DATADIR_DESTINATION ${_glog_CMake_INSTALLDIR})
 
 if (NOT IS_ABSOLUTE ${_glog_CMake_INSTALLDIR})

Bug#1031420: Acknowledgement (libgoogle-glog-dev: CMake config doesn't work out of the box)

[Dima Kogan]

I can "fix" this by adding to the top of
/usr/lib/x86_64-linux-gnu/cmake/glog/glog-config.cmake:

set(CMAKE_MODULE_PATH ${CMAKE_MODULE_PATH} /usr/share/glog/cmake/)

But this doesn't sound right. Maybe we should be shipping
/usr/share/glog/cmake/* someplace else?

Bug#1031330: [pre-approval] unblock: golang-1.19/1.19.6-2

[Sebastian Ramacher]

On 2023-02-15 11:58:54 +0800, Shengjing Zhu wrote:
> Package: release.debian.org
> Severity: normal
> User: release.debian@packages.debian.org
> Usertags: unblock
> X-Debbugs-Cc: golang-1...@packages.debian.org, z...@debian.org
> Control: affects -1 + src:golang-1.19
> 
> Please unblock package golang-1.19

Please go ahead with the upload.

> 
> [ Reason ]
> A new upstream release that addresses 4 CVE in Go standard library.
> 
> [ Impact ]
> CVE in Go standard library and the Go packages that have statically
> linked with it.
> 
> [ Tests ]
> The fixes are covered by new unit tests.
> 
> [ Risks ]
> The package is in the toolchain set.
> 
> [ Checklist ]
>   [x] all changes are documented in the d/changelog
>   [x] I reviewed all changes and I approve them
>   [x] attach debdiff against the package in testing
> 
>   The diff is for golang-1.19/1.19.6-1, which I have uploaded to
>   experimental first. -2 should be no-change rebuild on unstable.
> 
> [ Other info ]
> So same as previous unblock request #1028452
> + This package doesn't have autopkgtest.
> + The upload will trigger Release Team to perform a new round of rebuilding
>   outdated Built-Using for all Go packages.
> 
> The Go upstream usually has one minor version (may or may not carry CVE
> fixes) release every month.
> I'm wondering what Release Team thinks how often we should update
> during the freeze periods. Some options are:
> + Only ask pre-approval for minor versions with CVE
> + Don't update any (probably at late freeze period, like hard/full-freeze).

I would suggest to stick to versions fixing CVEs for now. If there is a
no-CVE releases between the last update and the start of the hard
freeze, we can revisit a final update and rebuild of the golang-world.

Cheers

> 
> The package currently FTBFS on i386/experimental but it won't be problem on
> unstable.
> The dep-resolver (aspcud) in experimental chooses gccgo to bootstrap,
> which has a bug https://github.com/golang/go/issues/51850.
> But on unstable the dep-resolver is apt, and will choose old golang-go to
> bootstrap.
> 
> unblock golang-1.19/1.19.6-2

> diff -Nru golang-1.19-1.19.5/debian/changelog 
> golang-1.19-1.19.6/debian/changelog
> --- golang-1.19-1.19.5/debian/changelog   2023-01-11 15:35:00.0 
> +0800
> +++ golang-1.19-1.19.6/debian/changelog   2023-02-15 10:09:02.0 
> +0800
> @@ -1,3 +1,16 @@
> +golang-1.19 (1.19.6-1) experimental; urgency=medium
> +
> +  * Team upload
> +  * New upstream version 1.19.6
> ++ CVE-2022-41722: path/filepath: path traversal in filepath.Clean on
> +  Windows
> ++ CVE-2022-41725: net/http, mime/multipart: denial of service from
> +  excessive resource consumption
> ++ CVE-2022-41724: crypto/tls: large handshake records may cause panics
> ++ CVE-2022-41723: net/http: avoid quadratic complexity in HPACK decoding
> +
> + -- Shengjing Zhu   Wed, 15 Feb 2023 10:09:02 +0800
> +
>  golang-1.19 (1.19.5-1) unstable; urgency=medium
>  
>* Team upload
> diff -Nru golang-1.19-1.19.5/src/cmd/go/internal/modfetch/coderepo_test.go 
> golang-1.19-1.19.6/src/cmd/go/internal/modfetch/coderepo_test.go
> --- golang-1.19-1.19.5/src/cmd/go/internal/modfetch/coderepo_test.go  
> 2023-01-10 06:38:03.0 +0800
> +++ golang-1.19-1.19.6/src/cmd/go/internal/modfetch/coderepo_test.go  
> 2023-02-14 01:38:43.0 +0800
> @@ -379,18 +379,6 @@
>   zipFileHash: 
> "c15e49d58b7a4c37966cbe5bc01a0330cd5f2927e990e1839bda1d407766d9c5",
>   },
>   {
> - vcs: "git",
> - path:"gopkg.in/natefinch/lumberjack.v2",
> - rev: "latest",
> - version: "v2.0.0-20170531160350-a96e63847dc3",
> - name:"a96e63847dc3c67d17befa69c303767e2f84e54f",
> - short:   "a96e63847dc3",
> - time:time.Date(2017, 5, 31, 16, 3, 50, 0, time.UTC),
> - gomod:   "module gopkg.in/natefinch/lumberjack.v2\n",
> - zipSum:  "h1:AFxeG48hTWHhDTQDk/m2gorfVHUEa9vo3tp3D7TzwjI=",
> - zipFileHash: 
> "b5de0da7bbbec76709eef1ac71b6c9ff423b9fbf3bb97b56743450d4937b06d5",
> - },
> - {
>   vcs:  "git",
>   path: "gopkg.in/natefinch/lumberjack.v2",
>   // This repo has a v2.1 tag.
> @@ -578,6 +566,10 @@
>   for _, tt := range codeRepoTests {
>   f := func(tt codeRepoTest) func(t *testing.T) {
>   return func(t *testing.T) {
> + if strings.Contains(tt.path, "gopkg.in") {
> + testenv.SkipFlaky(t, 54503)
> + }
> +
>   t.Parallel()
>   if tt.vcs != "mod" {
>   testenv.MustHaveExecPath(t, tt.vcs)
> @@ -790,11 +782,6 @@
>   },
>   {
>   vcs:  "git",
> - path: 

Bug#1031325: e2fsprogs 1.47.0 introduces a breaking change into Bookworm, breaking grub and making installations of Ubuntu and Debian releases via debootstrap impossible

[Russ Allbery]

"Theodore Ts'o"  writes:

> As a long-term solution, one could image changing the various image
> creation tools to do something like "mfks.ext4 -T grub2_dumbdown
> /dev/XXX", and then have something like the following in
> /etc/mke2fs.conf:

> [fs_types]
> grub2_dumbdown = {
> features = ^metadata_csum_seed,^casefold
> }

This is considerably more specific than what I had in mind, but maybe I'm
misunderstanding the problem.  Here's a slightly more fleshed out version
of what I was thinking:

mke2fs when run without any options has some default upstream-shipped set
of options that it enables (possibly via the upstream-shipped mke2fs.conf,
possibly in the binary, however it works).  Those defaults presumably work
with the kernel and other system tools shipped at the time, due to the
normal compatibility due diligence that you'd naturally do while doing
file system development.

When you make changes to the *defaults* (not just the addition of any
options in general), this presumably is also aligned with what you think
is generally supported by other system tools at the time.

Each time you change the defaults in a way that could be
backward-incompatible, you could capture those new defaults in a
permanently-fixed label of, say, 20230616, which is the defaults on that
date.  Probably in the default /etc/mke2fs.conf.  I don't expect you to
care about what systems they work with, what distributions they work with,
or anything else other than the timeline of when you decided to change the
defaults, something you're presumably already doing as a maintainer.  The
only additional work would be to update these labels with the settings
required to make mke2fs with its current defaults behave compatibly with
whatever the defaults had been at each of those captured points in time.

(And obviously eventually you could drop the really old ones if it made no
sense to keep supporting them, or have some single really-ancient fallback
for really old systems, etc.)

Then, image creators can look in /etc/mke2fs.conf for the timestamp that
most closely aligns with the target system they want to create and use
that group of settings.  If that turns out to be inadequate, they can go
back to a previous date.  Some work on their part is still required, but
from their perspective I think this would have the advantage of not having
to do research to reconstruct what all the options could be and how they
changed and which ones were potentially backward-incompatible, which are
all things you would generally already know and have in mind when you
changed the defaults and thus could capture for them.

That said, this is an architectural stab in the dark and I obviously don't
work on file system development, so maybe this isn't viable for some
reason that I'm not seeing.

-- 
Russ Allbery (r...@debian.org)  

Bug#1031422: gnumeric: Included documentation of python use in gnumeric is incorrect

[Alex King]

Package: gnumeric
Version: 1.12.48-1+b2
Severity: normal

Dear Maintainer,

I was looking to do some python scripting in gnumeric.

I checked the documentation (in the gnumeric-doc package in bullseye) for
how to do it.  In "The Python Console" section of the documentation, it
mentions editing a file in ~/.gnumeric/$version/plugins/.  This doesn't
exist.  It appears this type of configuration is now in dconf instead.

Under the "Installing and Building Gnumeric for Python" section, it is
mentioned to "apt-get install gnumeric gnumeric-python python".
gnumeric-python does not exist in the archive, and likely the bulk of these
instructons are obselete since the transition to python3.

It would be nice to have instructons that tell me how to use python3 with
gnumeric.  If that isn't available (a google search didn't turn up much
promising), at least the obsolete stuff should be removed from the
documentation.

I downloaded the testing version of gnumeric (gnumeric_1.12.55-1), and
looked in /usr/share/doc/gnumeric/README.Debian (it has not changed since
stable).  It includes the obsolete text:

Q: Where is the  plugin?
A: Plugins that require additional libraries or programs are packaged 
   separately (e.g. "gnumeric-python"). Do "apt-cache search gnumeric" to
   find them.

As already mentioned, the gnumeric-python package no longer exists, and the
only relevant plugins package seems to be gnumeric-plugins-extra.

It would be better if the obsolete documentation was removed.

It would be ideal if it were possible to use python3 with gnumeric, and if
instructions for doing so were included in a README.

Thanks,
Alex

-- System Information:
Debian Release: 11.5
  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/8 CPU threads)
Locale: LANG=en_NZ.UTF-8, LC_CTYPE=en_NZ.UTF-8 (charmap=UTF-8), 
LANGUAGE=en_NZ:en
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages gnumeric depends on:
ii  debconf [debconf-2.0]  1.5.77
ii  gnumeric-common1.12.48-1
ii  gsfonts1:8.11+urwcyr1.0.7~pre44-4.5
ii  libatk1.0-02.36.0-2
ii  libc6  2.31-13+deb11u5
ii  libcairo2  1.16.0-5
ii  libgdk-pixbuf2.0-0 2.40.2-2
ii  libglib2.0-0   2.66.8-1
ii  libgoffice-0.10-10 0.10.48-1
ii  libgsf-1-114   1.14.47-1
ii  libgtk-3-0 3.24.24-4+deb11u2
ii  libpango-1.0-0 1.46.2-3
ii  libpangocairo-1.0-01.46.2-3
ii  libxml22.9.10+dfsg-6.7+deb11u3
ii  procps 2:3.3.17-5
ii  pxlib1 0.6.8-1+b1
ii  zlib1g 1:1.2.11.dfsg-2+deb11u2

Versions of packages gnumeric recommends:
ii  evince3.38.2-1
ii  gnumeric-doc  1.12.48-1
ii  lp-solve  5.5.2.5-2

Versions of packages gnumeric suggests:
ii  fonts-liberation1:1.07.4-11
ii  gnumeric-plugins-extra  1.12.48-1+b2
pn  libgsf-1-dev

-- debconf information:
  gnumeric/existing-process-title:
  gnumeric/existing-process: false

Bug#1031423: rocminfo: rocm_agent_enumerator PermissionError in readFromKFD

[Cordell Bloor]

Package: rocminfo
Version: 5.2.3-2
Severity: normal
X-Debbugs-Cc: c...@slerp.xyz

Dear Maintainer,

When a user invokes rocm_agent_enumerator but does not have sufficient
permissions to read /sys/class/kfd/kfd/topology/nodes/*/properties,
the program will crash with the error

Traceback (most recent call last):
  File "/usr/bin/rocm_agent_enumerator", line 257, in 
main()
  File "/usr/bin/rocm_agent_enumerator", line 241, in main
target_list = readFromKFD()
  ^
  File "/usr/bin/rocm_agent_enumerator", line 200, in readFromKFD
line = f.readline()
   
PermissionError: [Errno 1] Operation not permitted

I tried adding a try/except for OSError exceptions around the file
open/read in readFromKFD and this allowed the script to continue. It
then attempted to identify the GPU using fallback methods (lspci and
rocminfo). In my case, the fallbacks were successful.

Perhaps this condition should not be a fatal error?

-- System Information:
Debian Release: bookworm/sid
  APT prefers unstable
  APT policy: (500, 'unstable')
Architecture: amd64 (x86_64)

Kernel: Linux 6.1.0-3-amd64 (SMP w/32 CPU threads; PREEMPT)
Locale: LANG=C, LC_CTYPE=C.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /usr/bin/dash
Init: unable to detect

Versions of packages rocminfo depends on:
ii  kmod30+20221128-1
ii  libc6   2.36-8
ii  libgcc-s1   12.2.0-14
ii  libhsa-runtime64-1  5.2.3-2
ii  libstdc++6  12.2.0-14
ii  pciutils1:3.9.0-4
ii  python3 3.11.2-1

rocminfo recommends no packages.

rocminfo suggests no packages.

-- no debconf information

Bug#1031420: libgoogle-glog-dev: CMake config doesn't work out of the box

[Dima Kogan]

Package: libgoogle-glog-dev
Version: 0.6.0-1
Severity: normal
X-Debbugs-Cc: none, Dima Kogan 

Hi. I'm not a cmake expert, so this might not be a bug. It might also
not be a bug in THIS package. Apologies if that is the case.

The libgoogle-glog-dev package includes cmake scripts in

  /lib/ARCH/cmake/glog/

But they don't work by default. I have a tiny CMakeLists.txt:

  cmake_minimum_required(VERSION 3.14)
  project(test)
  find_package(glog REQUIRED)

This happens:

  /tmp/glog-test$ cmake .

  -- The C compiler identification is GNU 12.2.0
  -- The CXX compiler identification is GNU 12.2.0
  -- Detecting C compiler ABI info
  -- Detecting C compiler ABI info - done
  -- Check for working C compiler: /usr/lib/ccache/cc - skipped
  -- Detecting C compile features
  -- Detecting C compile features - done
  -- Detecting CXX compiler ABI info
  -- Detecting CXX compiler ABI info - done
  -- Check for working CXX compiler: /usr/lib/ccache/c++ - skipped
  -- Detecting CXX compile features
  -- Detecting CXX compile features - done
  CMake Error at 
/usr/share/cmake-3.25/Modules/CMakeFindDependencyMacro.cmake:47 (find_package):
By not providing "FindUnwind.cmake" in CMAKE_MODULE_PATH this project has
asked CMake to find a package configuration file provided by "Unwind", but
CMake did not find one.

Could not find a package configuration file provided by "Unwind" (requested
version 1.3.2) with any of the following names:

  UnwindConfig.cmake
  unwind-config.cmake

Add the installation prefix of "Unwind" to CMAKE_PREFIX_PATH or set
"Unwind_DIR" to a directory containing one of the above files.  If "Unwind"
provides a separate development package or SDK, be sure it has been
installed.
  Call Stack (most recent call first):
/lib/x86_64-linux-gnu/cmake/glog/glog-config.cmake:35 (find_dependency)
CMakeLists.txt:3 (find_package)


  -- Configuring incomplete, errors occurred!
  See also "/tmp/glog-test/CMakeFiles/CMakeOutput.log".

It DOES work if I invoke it like this:

  $ cmake -DCMAKE_MODULE_PATH=/usr/share/glog/cmake/ .

I shouldn't need to do that. The package should configure everything by
itself.

Thanks!




-- System Information:
Debian Release: bookworm/sid
  APT prefers unstable
  APT policy: (800, 'unstable'), (700, 'testing'), (500, 'unstable-debug'), 
(500, 'stable')
merged-usr: no
Architecture: amd64 (x86_64)
Foreign Architectures: armhf, armel

Kernel: Linux 6.1.0-2-amd64 (SMP w/4 CPU threads; PREEMPT)
Kernel taint flags: TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE
Locale: LANG=C, LC_CTYPE=C.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages libgoogle-glog-dev depends on:
ii  libgflags-dev  2.2.2-2
ii  libgoogle-glog0v6  0.6.0-1
ii  libunwind-dev  1.3.2-2

libgoogle-glog-dev recommends no packages.

libgoogle-glog-dev suggests no packages.

-- no debconf information

Bug#1031421: caja: 0 ignored at beginning of filename in sorting

[Leonardo Boselli]

Source: caja
Version: MATE caja 1.24.0
Severity: normal

Dear Maintainer,

when sorting files aphabetically 0nov is displayed before 000nop and before 
00noW .
In short it ignores leading zeroes, so list is different than you would expect 
on ls.
No known way to ask to ignore it and do a strict binary ordering.
--
Leonardo 

Bug#972146: /usr/share/applications/mono-runtime-common.desktop: should not handle MIME type by executing arbitrary code

[Gabriel Corona]

Hi,

Thanks for the patch!

This has been fixed in Debian testing and sid. However, stable is still 
affected. I believe it would make sense to port the patch to stable and 
allocate a CVE for this.


Regards,

Gabriel

Bug#1031414: clinfo breaks libgpuarray autopkgtest on i386: numerical deltas

[Andreas Beckmann]

Control: forwarded -1 https://github.com/pocl/pocl/issues/1176

@elbrus: Why does britney try to migrate clinfo together with pocl?
IMO clinfo should be able to migrate on its own without causing new 
regressions in testing. It does not have any (transitive) dependency on 
pocl.


On Thu, 16 Feb 2023 21:46:31 + "Rebecca N. Palmer" 
 wrote:
The trigger is probably pocl, not clinfo.  I don't yet know whether the 
bug is in pocl or libgpuarray.

or llvm-15

pocl/sid is built against llvm-15, pocl/testing against llvm-14

This also causes a test regression in pyopencl due to numerical 
differences (#1030298). This was attempted to be fixed in pyopencl 
upstream by requiring the numerical difference to be below some 
tolerance level instead of requiring equality, but the numerical delta 
is too large to hide behind that ...


I'm currently trying to debug the code generation delta between llvm-14 
and llvm-15 ...


There could still be a bug in libgpuarray if the failing test is too 
strict by requiring equality of some floating point computations. (Not 
checked.)


Andreas

Bug#1031325: e2fsprogs 1.47.0 introduces a breaking change into Bookworm, breaking grub and making installations of Ubuntu and Debian releases via debootstrap impossible

[Theodore Ts'o]

On Thu, Feb 16, 2023 at 11:45:23AM -0800, Russ Allbery wrote:
> 
> Yes, I'm probably understating the difficulty of making this change in
> practice inside image building software as it's currently constructed.
> 
> My concern about changing mkfs options is that I worry that this would be
> a constantly-changing target that has to be synchronized across multiple
> pieces of software that are not currently well-aligned with file system
> development.  One thing that would make this much easier would be for mkfs
> to support some sort of compatibility level flag that sets all of the
> options, whatever they may be, to their defaults as of some point in the
> past.  Image building software could then pick a conservative default set
> point when building images for older distributions.  That change still has
> to be added to all of the image building software, but it might be easier
> than building a local chroot of the target distribution before using it to
> build the file system the actual installation is going into.

As a long-term solution, one could image changing the various image
creation tools to do something like "mfks.ext4 -T grub2_dumbdown
/dev/XXX", and then have something like the following in
/etc/mke2fs.conf:

[fs_types]
grub2_dumbdown = {
features = ^metadata_csum_seed,^casefold
}

If you care about being able to run fsck.ext4 on really old
distributions, one could even add things like

[fs_types]
jessie_dumbdown = {
features = ^metadata_csum_seed,^metadata_csum
}

etc.

Maintaining this would be a nightmare, and I'd want to ask for help,
since this would be change if we also want to add dumbdown file system
usage types for Ubuntu, and potentially, other Debian derivitives.

Even if we stick with grub2_dumbdown, again, how far back do we go?
Some people have said, "just one release", but I bet there will be
people wanting to create Stretch installer images using a sid
userspace.  So I'd want to have some kind of formal understanding
about what it is that we feel obliged to support.

Given the number of users of the iamge building tools, it's a pretty
specialized use case with not a lot of users, and they can also just
edit /etc/mke2fs.conf to have their favored default.  From my
e2fsprogs maintainers hat on, that's my position --- I interpret
"users" in the Debian Social Contract for the general users, and not
necessarily something that needs to work for every single exotic use
case, especially if they tend to be more of the power users.

If we're not allowed to inconvenience *any* users, then it's hard to
make forward progress.  Certainly some people (including myself) were
inconvenienced for things like /usr-unification and the transition to
systemd.  We went ahead with the transition even though some users
were inconvenienced.  And quite honestly, if a few power users need to
edit /etc/mke2fs.conf to remove metadata_csum_seed because they want
to do something which is *REALLY* not a good idea (using Debian M to
build a file system meant for use on Debian M-X) --- for *ALL* file
systems, not just ext4.  It may be that some users have gotten lucky,
and it mostly works.  But it's a bad idea, and encouraging this bad
practice is eventually going to lead to tears.

But, if the Debian Release team would like to override my position, my
suggestion would be to just change the default for /etc/mke2fs.conf
for *everyone* running Debian bookworm, and with the understanding
that this will be reverted in Debian testing after the next stable
release, and that moving forward, we make it the image building tools
problem if they want to support this highly dubious practice of using
Debian N+X's mkfs to build images for Debian N.  I would strongly
suggest that they figure out which file system features they need to
explicitly turn off for ext4, xfs, btrfs, etc., if they want to build
old distro versions using whatever random software they have installed
on their desktop.

Best release engineering practice is that you use a known, controlled
build environment, and not whatever random package versions might be
on your desktop.  While that might be "inconvenient" when building
packages, we've learned to live with it.  I use sbuild; others might
use pbuild, or their own custom schroot setup.  But I dare say all
responsible people doing release engineering use a known build
environment.  Why should this be any different if you are building
images --- especially images that you expect *your* users or customers
to be depending on?  What are your responsibilities to them?  (Whether
or not the Debian Social contract applies to them or not.)

- Ted

Bug#1026027: graphical installer: using nano in a installer shell fails

[Cyril Brulebois]

cc += nano maintainers

Long story short: nano no longer starts in the graphical installer when
started from the menu (meaning integrated via VTE), but does start fine
when started from a console.

Any insight welcome.

Below, latest message on the bug report:

Philip Hands  (2022-12-15):
> Holger Wansing  writes:
> 
> > Hi,
> >
> > Philip Hands  wrote (Tue, 13 Dec 2022 20:34:17 +0100):
> >> On the 11.5 netinst I just tried out, in the Graphical Install's shell,
> >> TERM=xterm so that's obviously not the cause of the issue, but the
> >> difference would appear to be that it has:
> >> 
> >>   /usr/share/vte/termcap-0.0/xterm
> >> 
> >> So I guess the fix for this is either to make sure that that termcap
> >> file gets installed again, or to set TERM in the Graphical Install's
> >> shell to something like 'bterm' or 'vt102'.
> >> 
> >> I suspect restoring the termcap file is the correct fix.
> >
> > /usr/share/vte/termcap-0.0/xterm is there on dailies.
> 
> Oh, so it is.  Hmm, I seem not to have checked that bit, sorry.
> 
> Perhaps the presence of the termcap file is irrelevant, or could it be
> that nano used to be able to make use of that, and more recently only
> supports terminfo?
> 
> > Hmm. Kibi mentioned that this bug comes from ncurses (however I fail to
> > see any details here), should this be redirected to ncurses then?
> 
> Well, ncurses-base provides /lib/terminfo/x/xterm (in normal .deb
> packages), so perhaps that's why, although AFAICS it wasn't including
> that file in the udeb, even when things were working.
> 
> Making it ship a terminfo for xterm in the udeb would probably fix
> things, but I think it would also be quite nice to know why it broke.


Cheers,
-- 
Cyril Brulebois (k...@debian.org)
D-I release manager -- Release team member -- Freelance Consultant


signature.asc
Description: PGP signature

Bug#1006529: mariadb fails on hppa

[Helge Deller]

Hi Otto,

Just FYI:
mariadb fails on the hppa architecture, because there is a kernel bug
(on parisc and probably other architectures) in the io_uring syscall.
This is worked on upstream, e.g. this mail thread:
https://lore.kernel.org/io-uring/507c7873--dbcb-c512-4659af486...@bell.net/T/#t
We hope to get the kernel fixed in upcoming versions.

Other buildds which run on qemu-user emulation will probably never support
the io_uring syscall...

Helge

Bug#1031419: libclang-rt-14-dev: trying to overwrite '.../libclang_rt.builtins-wasm32.a', which is also in package libclang-rt-14-dev-wasm32

[Witold Baryluk]

Package: libclang-rt-14-dev
Version: 1:14.0.6-11
Severity: normal
X-Debbugs-Cc: witold.bary...@gmail.com

Preparing to unpack .../libclang-rt-14-dev_1%3a14.0.6-11_amd64.deb ...
Unpacking libclang-rt-14-dev:amd64 (1:14.0.6-11) over (1:14.0.6-10+b1) ...
dpkg: error processing archive 
/var/cache/apt/archives/libclang-rt-14-dev_1%3a14.0.6-11_amd64.deb (--unpack):
 trying to overwrite 
'/usr/lib/llvm-14/lib/clang/14.0.6/lib/wasi/libclang_rt.builtins-wasm32.a', 
which is also in package libclang-rt-14-dev-wasm32 1:14.0.6-11
Errors were encountered while processing:
 /var/cache/apt/archives/libclang-rt-14-dev_1%3a14.0.6-11_amd64.deb


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

Kernel: Linux 6.2.0-rc5 (SMP w/32 CPU threads; PREEMPT)
Kernel taint flags: TAINT_UNSIGNED_MODULE
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages libclang-rt-14-dev depends on:
ii  lib32gcc-s1   12.2.0-14
ii  lib32stdc++6  12.2.0-14
ii  libc6 2.36-8
ii  libc6-i3862.36-8
ii  libgcc-s1 12.2.0-14
ii  libstdc++612.2.0-14

libclang-rt-14-dev recommends no packages.

libclang-rt-14-dev suggests no packages.

-- no debconf information

Bug#1031325: e2fsprogs 1.47.0 introduces a breaking change into Bookworm, breaking grub and making installations of Ubuntu and Debian releases via debootstrap impossible

[Sebastian Ramacher]

On 2023-02-16 11:44:25 -0700, Sam Hartman wrote:
> > "Adrian" == Adrian Bunk  writes:
> 
> Adrian> On Thu, Feb 16, 2023 at 05:48:22PM +0100, Daniel Leidert wrote:
> >> Am Donnerstag, dem 16.02.2023 um 18:37 +0200 schrieb Adrian Bunk:
> >> > On Wed, Feb 15, 2023 at 12:05:41AM +0100, Daniel Leidert wrote:
> >> > > ...  > > Reasons: > > ...  > > - - the change makes it
> >> impossible to create filesystems with this version of > >  
> >> e2fsprogs and then run a grub-install from a target system that
> >> does not cope > >   with that feature; basically breaking the
> >> debootstrap method of installing > >   Debian or Ubuntu onto a
> >> server (violating #4 of the Debian social contract) > > ...  > >
> >> Instead, turning on this feature should be postponed for the next
> >> release cycle > > where a proper transition can be done.  > > ...
> >> > 
> >> > Daniel, you are contradicting yourself when claiming that a
> >> change that > would allegedly violate the Debian social contract
> >> could be done in the > next release cycle.
> >> 
> >> Actually, I'm not.  ...
> 
> Adrian> If not being able to install bullseye from bookworm is a
> Adrian> violation of the Debian social contract, then the same
> Adrian> rationale applies to not being able to install bullseye from
> Adrian> trixie being a violation of the Debian social contract.
> 
> I don't think that arguing about whether this is a social contract
> violation makes a lot of sense.
> It seems fairly clear there is not a consensus about that.
> 
> But if we're going to do that, I suggest that Adrian is putting words
> into Daniel's mouth a bit.
> Daniel has said he believes this situation violates the Social Contract
> #4, but has not explained why.
> Adrian has taken one interpretation.
> I'll propose another: "This violates the social contract because we are
> not prioritizing our users.  Prioritizing users requires that we give
> them notice of incompatible changes."
> I personally think that prioritizing users requires no such thing, and
> that this change is not a violation of the SC.
> But you don't need to take the straw man position Adrian is assuming
> Daniel implies to believe this is a SC violation.
> 
> But seriously, let's give up the whole is this an SC violation part of
> the discussion and move on with constructive aspects:
> 
> * The RT has asked to understand the impact of the change.
> 
> * Several people have proposed better documentation because it's clear
>   that user (and image builder) expectations are not aligned with
>   filesystem maintainer expectations.
> 
> * Anyone could prepare patches to image building software to use mkfs
>   options that will work with bullseye.  You could also try to prepare
>   patches to run mkfs out of a chroot or container of the guest OS for
>   the image.  I appreciate Russ strongly favors this solution, but as
>   someone who has dug into image building tools a fair bit over the
>   years, I think there are significant complexity and performance
>   downsides to that approach.  I also think that changing the mkfs
>   options is more likely to get an unblock than changing the structure
>   of how the tool works.
>   
>   
>   
> * People could try to judge consensus on debian-devel or debian-policy
>   about whether we want a stability guarantee ?+/- 1 release on issues
>   like this.  My suspicion is that you will not find a consensus, and
>   that if the RT decides they don't want this change in bookworm, Ted
>   will change the defaults, and if the RT is unwilling to block, we're
>   left with documentation.
> 
> I think all the above is more productive than arguing about whether this
> is or is not an SC violation.

Thanks for this mail. The discussion on SC#4 is not helping us to reach
a decission on this issue.

Cheers
-- 
Sebastian Ramacher

Bug#1029499: php-guzzlehttp-psr7: Build killed with signal TERM after 150 minutes of inactivity

[Santiago Vila]

tags 1029499 + patch
thanks

Hello.

Please consider the attached patch, as I don't really think this
package is suitable for release in its current state. I would agree
that the proposed patch is not perfect, but I also think that
it's a lot better than nothing.

To reproduce the problem, please do this:

sbuild -d sid php-guzzlehttp-psr7

(where "sid" is a configured chroot for sid).

Thanks.diff -Nru php-guzzlehttp-psr7-2.4.3/debian/changelog 
php-guzzlehttp-psr7-2.4.3/debian/changelog
--- php-guzzlehttp-psr7-2.4.3/debian/changelog  2022-10-29 11:19:43.0 
+0200
+++ php-guzzlehttp-psr7-2.4.3/debian/changelog  2023-02-16 22:20:00.0 
+0100
@@ -1,3 +1,9 @@
+php-guzzlehttp-psr7 (2.4.3-2) unstable; urgency=medium
+
+  * Kill php process after running unit tests. Closes: #1029499.
+
+ -- David Prévot   Thu, 16 Feb 2023 22:20:00 +0100
+
 php-guzzlehttp-psr7 (2.4.3-1) unstable; urgency=medium
 
   [ Tim Düsterhus ]
diff -Nru php-guzzlehttp-psr7-2.4.3/debian/control 
php-guzzlehttp-psr7-2.4.3/debian/control
--- php-guzzlehttp-psr7-2.4.3/debian/control2022-08-30 15:32:27.0 
+0200
+++ php-guzzlehttp-psr7-2.4.3/debian/control2023-02-16 22:18:17.0 
+0100
@@ -11,7 +11,8 @@
php-psr-http-factory,
php-psr-http-message,
phpab,
-   phpunit
+   phpunit,
+   psmisc
 Standards-Version: 4.6.1
 Homepage: https://github.com/guzzle/psr7
 Vcs-Git: https://salsa.debian.org/php-team/pear/php-guzzlehttp-psr7.git
diff -Nru php-guzzlehttp-psr7-2.4.3/debian/rules 
php-guzzlehttp-psr7-2.4.3/debian/rules
--- php-guzzlehttp-psr7-2.4.3/debian/rules  2022-08-30 15:16:24.0 
+0200
+++ php-guzzlehttp-psr7-2.4.3/debian/rules  2023-02-16 22:18:36.0 
+0100
@@ -22,3 +22,4 @@
 override_dh_auto_test:
php -S 127.0.0.1:10002 tests/Integration/server.php &
TEST_SERVER=127.0.0.1:10002 phpunit -v
+   killall php

Bug#1031418: node-undici: CVE-2023-23936 CVE-2023-24807

[Salvatore Bonaccorso]

Source: node-undici
Version: 5.15.0+dfsg1+~cs20.10.9.3-1
Severity: important
Tags: security upstream
X-Debbugs-Cc: car...@debian.org, Debian Security Team 

Hi,

The following vulnerabilities were published for node-undici.

CVE-2023-23936[0]:
| Undici is an HTTP/1.1 client for Node.js. Starting with version 2.0.0
| and prior to version 5.19.1, the undici library does not protect
| `host` HTTP header from CRLF injection vulnerabilities. This issue is
| patched in Undici v5.19.1. As a workaround, sanitize the
| `headers.host` string before passing to undici.


CVE-2023-24807[1]:
| Undici is an HTTP/1.1 client for Node.js. Prior to version 5.19.1, the
| `Headers.set()` and `Headers.append()` methods are vulnerable to
| Regular Expression Denial of Service (ReDoS) attacks when untrusted
| values are passed into the functions. This is due to the inefficient
| regular expression used to normalize the values in the
| `headerValueNormalize()` utility function. This vulnerability was
| patched in v5.19.1. No known workarounds are available.


If you fix the vulnerabilities please also make sure to include the
CVE (Common Vulnerabilities & Exposures) ids in your changelog entry.

For further information see:

[0] https://security-tracker.debian.org/tracker/CVE-2023-23936
https://www.cve.org/CVERecord?id=CVE-2023-23936
[1] https://security-tracker.debian.org/tracker/CVE-2023-24807
https://www.cve.org/CVERecord?id=CVE-2023-24807

Regards,
Salvatore

Bug#1031414: clinfo breaks libgpuarray autopkgtest on i386: numerical deltas

[Rebecca N. Palmer]

Control: reassign -1 src:pocl,src:libgpuarray
Control: found -1 pocl/3.1-3
Control: found -1 libgpuarray/0.7.6-13
Control: retitle -1 libgpuarray: i386 test fail with new pocl

The trigger is probably pocl, not clinfo.  I don't yet know whether the 
bug is in pocl or libgpuarray.

Bug#1031293: python3-zstandard 0.19.0-3 supports only libzstd 1.5.2

[James Addison]

Package: python3-zstandard
Followup-For: Bug #1031293
X-Debbugs-Cc: b...@debian.org, gregory.sz...@gmail.com

Hi Adrian, Gregory,

Reading the comment above the version check, it seems to indicate that Gregory
isn't particularly enthusiastic to provide support for environments where
there's a mismatch between the python-zstandard module and an unbundled system
zstd library.

Although it 'might work' in practice -- and even though users may be careful
enough to figure out the correct place to complain to even if problems did
occur -- I reckon we should default to upstream's preferences unless there are
good reasons not to (and there might be; they're just not clear to me, if so).

(not only could complaints cause nuisance for upstream, but divergence could,
in my opinion, mean that Debian maintainers would take on more responsibility;
again fine if it makes sense to do that, but it might be helpful to agree why)

Thanks,
James

Bug#1028250: debian-installer: broken cryptsetup support

[Nem Jojic]

I haven’t look at cryptsetup.  What is the purpose?

Get Outlook for iOS


From: Cyril Brulebois 
Sent: Thursday, February 16, 2023 14:21
To: 1028...@bugs.debian.org <1028...@bugs.debian.org>
Cc: cryptse...@packages.debian.org 
Subject: Bug#1028250: debian-installer: broken cryptsetup support

cc += cryptsetup maintainers (hi, long time no see!)

Cyril Brulebois  (2023-01-09):
> Cyril Brulebois  (2023-01-08):
> > I'm seeing at least two problems with cryptsetup while testing daily
> > builds:
> > - with 6.1.0-1 (currently getting into the archive), my very usual 1G
> > RAM / 5G storage setup can no longer get an automated encrypted LVM
> > setup created: cryptsetup triggers the OOMK while creating the
> > encrypted storage; that doesn't happen with 6.0.0-6. Not sure
> > cryptsetup itself is the culprit, it might just be more components or
> > heavier components on the kernel side, pushing memory to the limit.
> > - with either kernel (and 1G RAM for 6.0.0-6, 2G RAM for 6.1.0-1 due
> > to the first point), I cannot boot into the installed system: I'm not
> > getting the LVM passphrase prompt, and the root device is therefore
> > missing.
> >
> > I haven't investigated either issue, and I'm not sure when I'll be able
> > to. Help welcome.
> >
> > The first point could be waved aside with an errata entry; the second
> > point is going to be a blocker for the next release.
>
> Trying to investigate the second one, I cannot replicate my earlier
> results, with either a clean unstable daily build using 6.1.0-1 or with
> D-I Bookworm Alpha 1; and besides cryptsetup uploads in early December,
> I must admit a quick look around didn't suggest anything obvious that
> could explain what I were getting… Bad luck, maybe; lowering severity
> accordingly for the time being.

Testing d-i built against testing udebs again, I can replicate this
issue now. I suppose this might be some component getting bigger over
time, and pushing the limit somehow. And the various builds I tried back
in January might have been tiptoeing around that limit…

Looking at `free` with this netboot-gtk mini.iso build, inside kvm, with
1G RAM, `used` is ~100M, `free` is 500+ M, and yet, cryptsetup gets
OOMK'd.

Is cryptsetup being stupid and miscomputing RAM requirements for that
setup? (ISTR LUKS2 means heavier computation, tweaked depending on
hardware, but I haven't followed that closely.)

The memory pressure at this particular point of the installation process
seems quite low, so crashing with free at 50% feels very wrong to me…


Cheers,
--
Cyril Brulebois (k...@debian.org) 
D-I release manager -- Release team member -- Freelance Consultant

Bug#1031417: spamass-milter tags all DKIM signed mails as DKIM_INVALID due to CRLF issue in headers (working patch available)

[Matthieu Schapranow]

Package: spamass-milter
Version: 0.4.0-2

Referring to the discussion at 
https://bz.apache.org/SpamAssassin/show_bug.cgi?id=7785, it is still unclear 
whether this bug will be fixed in Mail::DKIM or in spamassassin 4.0.

For the time being, I have tested the patch provided by Henrik Krohns 
(https://savannah.nongnu.org/bugs/download.php?file_id=48244) attached to bug 
report "#57626: Folded headers not keeping CRLF newlines” 
(https://savannah.nongnu.org/bugs/index.php?57626) to spamass-milter 0.4.0-2. 
It works and the milter reports DKIM status correctly.

Would be great if you could integrate the patch “header_crlf” to 
debian/patches/series.

header_crlf:



Description: Spamass-milter doesn't properly maintain CRLF in folded header 
newlines.
Origin: https://bz.apache.org/SpamAssassin/show_bug.cgi?id=7785
Bug: #7785
Author: Henrik Krohns, Matthieu Schapranow 
mailto:schapra...@hpi.de>>
Forwarded: no
--- a/spamass-milter.cpp
+++ b/spamass-milter.cpp
@@ -1206,7 +1206,23 @@ mlfi_header(SMFICTX* ctx, char* headerf,
 assassin->set_subject(headerv);

   // assemble header to be written to SpamAssassin
-  string header = string(headerf) + ": " + headerv + "\r\n";
+  string header = headerv;
+
+  // Replace all LF with CRLF
+  // As milter documentation says:
+  // headervHeader field value.  The content of the header may
+  //   include folded white space, i.e., multiple lines with following
+  //   white space where lines are separated by LF (not CR/LF).  The
+  //   trailing line terminator (CR/LF) is removed.
+  // Need to make sure folded header line breaks are sent to SA as CRLF
+  string::size_type idx = header.size();
+  while ( (idx = header.rfind("\n", idx)) != string::npos )
+  {
+ header.replace(idx,1,"\r\n");
+  }
+
+  // final assembly
+  header = string(headerf) + ": " + header + "\r\n";

   try {
 // write to SpamAssassin client



Thanks,

Matthieu Schapranow

Bug#1030939: e2fsprogs: generates filesystems that grub-install doesn't recognize

[Sebastian Ramacher]

Control: clone -1 -2
Control: reassign -2 fai 6.0
Control: clone -1 -3
Control: reassign -3 grml-debootstrap 0.102

On 2023-02-15 21:04:36 +0100, Sebastian Ramacher wrote:
> Control: clone -1 -2
> Control: reassign -2 vmdb2 0.26-2
> 
> On 2023-02-14 01:01:38 +0100, Daniel Leidert wrote:
> > Hi Steve,
> > 
> > I believe that your fix to grub2 in Sid is not enough to handle
> > #1030939/#1030846.
> > 
> > This problem breaks e.g. vmdb2. I can no longer create a Bullseye
> > system image with vmdb2 on Sid, because the grub-install step in the
> > Bullseye chroot now fails, because the created filesystem (created with
> > e2fsprogs on Sid) cannot be recognized by grub. I have to downgrade
> > e2fsprogs to the version in Testing to get the build going again. It
> > also means that a Bookworm system can never be used to format and
> > debootstrap a Bullseye or Buster system that requires a grub
> > installation.
> > 
> > I guess that the fix applied to grub2 in Sid would have to be applied
> > to grub2 in Bullseye as well (and basically to any grub2 package in any
> > Debian or Ubuntu or Raspbian release supported by debootstrap).
> > 
> > This situation is really messy. It breaks basically all my image builds
> > with vmdb2.
> 
> Regardless of the outcome of #1031325, this issue will need to be fixed
> in vmdb2 eventually. vmdb2, similar to other bootstraping tools, has to
> account for the feature and disable it if necessary for older
> distributions.
> 
> Cloning and reassign to vmdb2.

Based on more feedback from #10313225, I am also cloning and reassigning
this issue to fai and grml-debootstrap. Dear maintainers, please check
whether this issue is relevant for your packages.

Cheers
-- 
Sebastian Ramacher

Bug#1031325: e2fsprogs 1.47.0 introduces a breaking change into Bookworm, breaking grub and making installations of Ubuntu and Debian releases via debootstrap impossible

[Sebastian Ramacher]

On 2023-02-16 07:54:52 -0700, Sam Hartman wrote:
> > "Sebastian" == Sebastian Ramacher  writes:
> 
> Sebastian> To better understand the impact of this change, I was
> Sebastian> wondering which tools / image builders in the archive
> Sebastian> would be affected by this change.  I've cloned the bug to
> Sebastian> vmdb2, but what about others?
> 
> It will affect fai-diskimage in the fai package..
> I believe that's used by the cloud team (or was) to create cloud images;
> I don't know if their use case is affected, because I don't know what OS
> they use to create what images.

Also cloned/reassigned the bug to fai, thanks.

Cheers
-- 
Sebastian Ramacher

Bug#1031325: e2fsprogs 1.47.0 introduces a breaking change into Bookworm, breaking grub and making installations of Ubuntu and Debian releases via debootstrap impossible

[Sebastian Ramacher]

On 2023-02-16 12:24:01 +0100, Michael Prokop wrote:
> * Sebastian Ramacher [Thu Feb 16, 2023 at 09:09:08AM +0100]:
> > On 2023-02-15 13:17:38 -0700, Sam Hartman wrote:
> 
> > > But for example you're not leaving a lot of time for asking programs
> > > like vmdb2 or fai-diskimage to adjust how they call fsck.
> > > If you made this change a few months ago, it would be reasonable to file
> > > bugs against those packages and ask them to adjust how they call
> > > mkfs.ext4.
> 
> > To better understand the impact of this change, I was wondering which
> > tools / image builders in the archive would be affected by this change.
> > I've cloned the bug to vmdb2, but what about others?
> 
> I didn't verify it yet, but AFAICT grml-debootstrap is affected as
> well, since it supports installing older Debian releases from within
> more recent Debian/Grml environments and uses mkfs.ext4 as default.

Thanks, cloned/reassigned the bug also to grml-debootstrap to check
whether it's an issue.

Cheers

> 
> BTW, we had a similar situation already in the past when mkfs.ext4
> of e2fsprogs >=1.43~WIP.2015.05.18-1 enabled the "metadata_csum"
> feature, while this was unsupported on jessie and older releases.
> (grml-debootstrap provides a workaround for this.)
> 
> regards
> -mika-



-- 
Sebastian Ramacher

Bug#1031414: clinfo breaks libgpuarray autopkgtest on i386: numerical deltas

[Paul Gevers]

Source: clinfo, libgpuarray
Control: found -1 clinfo/3.0.23.01.25-1
Control: found -1 libgpuarray/0.7.6-13
Severity: serious
Tags: sid bookworm
User: debian...@lists.debian.org
Usertags: breaks needs-update

Dear maintainer(s),

With a recent upload of clinfo the autopkgtest of libgpuarray fails in 
testing when that autopkgtest is run with the binary packages of clinfo 
from unstable. It passes when run with only packages from testing. In 
tabular form:


   passfail
clinfo from testing3.0.23.01.25-1
libgpuarrayfrom testing0.7.6-13
versioned deps [0] from testingfrom unstable
all others from testingfrom testing

I copied some of the output at the bottom of this report.

Currently this regression is blocking the migration of clinfo to testing 
[1]. Due to the nature of this issue, I filed this bug report against 
both packages. Can you please investigate the situation and reassign the 
bug to the right package?


More information about this bug and the reason for filing it can be found on
https://wiki.debian.org/ContinuousIntegration/RegressionEmailInformation

Paul

[0] You can see what packages were added from the second line of the log 
file quoted below. The migration software adds source package from 
unstable to the list if they are needed to install packages from 
clinfo/3.0.23.01.25-1. I.e. due to versioned dependencies or 
breaks/conflicts.

[1] https://qa.debian.org/excuses.php?package=clinfo

https://ci.debian.net/data/autopkgtest/testing/i386/libg/libgpuarray/31439784/log.gz

=== FAILURES 
===
__ test_ielemwise2_ops_mixed 
___


def test_ielemwise2_ops_mixed():
for op in ioperators2:
for dtype in dtypes_test:
for elem in elems:

  ielemwise2_ops_mixed(op, dtype, (50,), elem)


/usr/lib/python3/dist-packages/pygpu/tests/test_elemwise.py:173: _ _ _ _ 
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ 
/usr/lib/python3/dist-packages/pygpu/tests/support.py:44: in f

func(*args, **kwargs)
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ 
_ _ _ _

op = , dtype = 'float32', shape = (50,), elem = 0.3

@guard_devsup
def ielemwise2_ops_mixed(op, dtype, shape, elem):
incr = 0
if op == operator.isub and dtype[0] == 'u':
# array elements are smaller than 10 by default, so we 
avoid underflow

incr = 10
c, g = gen_gpuarray(shape, dtype, incr=incr, ctx=context,
cls=elemary)
try:
out_c = op(c, elem)
except TypeError:
# TODO: currently, we use old Numpy semantic and tolerate 
more case.

# So we can't test that we raise the same error
return
out_g = op(g, elem)
assert out_g is g
assert out_c.shape == out_g.shape
assert out_c.dtype == out_g.dtype

  assert numpy.allclose(out_c, numpy.asarray(out_g))

E   assert False
E+  where False = 0xf3ad35c8>(array([0.16798985, 0.10199559, 0.00094628, 0.284034  , 
0.00356799,\n   0.18276209, 0.06017095, 0.12363595, 0.14555043, 
0.06383288,\n   0.27849692, 0.23479545, 0.1120947 , 0.03348678, 
0.17435497,\n   0.10784233, 0.15038443, 0.08132076, 0.26949704, 
0.28150958,\n   0.08847237, 0.07874835, 0.14240652, 0.22457486, 
0.02050698,\n   0.24944574, 0.29784787, 0.03708786, 0.23751181, 
0.26554942,\n   0.26809436, 0.02403933, 0.23044948, 0.13133025, 
0.29589295,\n   0.05166197, 0.07869713, 0.10319626, 0.07735932, 
0.241211  ,\n   0.27668405, 0.16557133, 0.26950228, 0.230201  , 
0.2993518 ,\n   0.0713675 , 0.02841425, 0.04263723, 0.194592  , 
0.2564727 ],\n  dtype=float32), array([0.16798979, 0.10199571, 
0.00094652, 0.28403443, 0.00356805,\n   0.1827622 , 0.06017077, 
0.12363613, 0.14555037, 0.063833  ,\n   0.2784968 , 0.23479551, 
0.11209452, 0.03348672, 0.17435497,\n   0.10784221, 0.1503846 , 
0.08132076, 0.26949698, 0.28150946,\n   0.08847237, 0.07874823, 
0.14240658, 0.22457486, 0.0205071 ,\n   0.24944574, 0.29784793, 
0.0370878 , 0.2375117 , 0.26554942,\n   0.26809436, 0.02403933, 
0.23044948, 0.13133001, 0.29589337,\n   0.05166197, 0.07869713, 
0.10319638, 0.07735932, 0.24121124,\n   0.276684  , 0.16557115, 
0.26950234, 0.230201  , 0.29935163,\n   0.07136726, 0.02841425, 
0.04263711, 0.19459194, 0.25647253],\n  dtype=float32))

E+where  = numpy.allclose
E+and   array([0.16798979, 0.10199571, 0.00094652, 
0.28403443, 0.00356805,\n   0.1827622 , 0.06017077, 0.12363613, 
0.14555037, 0.063833  ,\n   0.2784968 , 0.23479551, 0.11209452, 
0.03348672, 0.17435497,\n   0.10784221, 0.1503846 , 0.08132076, 
0.26949698, 0.28150946,\n   0.08847237, 0.07874823, 

Bug#1031391: /lib/modules/6.0.0-12parrot1-amd64/kernel/drivers/net/wireless/ath/ath10k/ath10k_core.ko: Firmware crashed

[Salvatore Bonaccorso]

Control: tags -1 + moreinfo

On Thu, Feb 16, 2023 at 12:38:03PM +0100, Marek Küthe wrote:
> Package: src:linux
> Version: 6.0.12-1parrot1
> Severity: important
> File: 
> /lib/modules/6.0.0-12parrot1-amd64/kernel/drivers/net/wireless/ath/ath10k/ath10k_core.ko
> X-Debbugs-Cc: m...@mk16.de
> 
> Dear Maintainer,
> 
>* What led up to the situation?
> I have no idea how this situation comes about. 
> * What exactly did you do (or not do) that was effective (or
>  ineffective)
>* What was the outcome of this action?
>* What outcome did you expect instead?
> 
> The firmware crashes (judging by the log). After that, the computer becomes 
> enormously slow, the mouse does not move for a few seconds. After that it 
> works again. After that, Network Manager says "disconnect". When I restart 
> the Network Manager, "Device not available" appears.
> 
> -- Package-specific info:
> ** Version:
> Linux version 6.0.0-12parrot1-amd64 (t...@parrotsec.org) (gcc-10 (Debian 
> 10.2.1-6) 10.2.1 20210110, GNU ld (GNU Binutils for Parrot) 2.37.90.20220130) 
> #1 SMP PREEMPT_DYNAMIC Debian 6.0.12-1parrot1 (2023-01-12)
> 
> ** Command line:
> BOOT_IMAGE=/@/boot/vmlinuz-6.0.0-12parrot1-amd64 
> root=UUID=4c28bef4-77fd-4464-9cd5-5b0bcc104742 ro rootflags=subvol=@ quiet 
> cryptdevice=UUID=fed0c2db-58a8-4f7b-9ba2-9321b4f7a550:luks-fed0c2db-58a8-4f7b-9ba2-9321b4f7a550
>  root=/dev/mapper/luks-fed0c2db-58a8-4f7b-9ba2-9321b4f7a550 splash 
> resume=/dev/mapper/luks-5090abc4-1254-4f9f-8ae8-2f7e0cd2bd55
> 
> ** Tainted: PWO (4609)
>  * proprietary module was loaded
>  * kernel issued warning
>  * externally-built ("out-of-tree") module was loaded

While this might not be the issue, two observation: does this happens
with the Debian kernel? Otherwise report it please to the derivative.
There are proprietary out of tree modules loaded, does that happens
as well without? 

In any case can you please if you can reproduce this with plain Debian
unstable (upate as well the firmware packages to their current versions)?

Regards,
Salvatore

Bug#1031376: tzdata 2022g-3 removed /etc/timezone without a proper transition, breaking multiple packages

[Sebastian Ramacher]

On 2023-02-16 20:22:15 +, Benjamin Drung wrote:
> On Thu, 2023-02-16 at 13:59 +0100, Michael Biebl wrote:
> > [Looping Benjamin in]
> > 
> > Hi everyone,
> > 
> > the removal of /etc/timezone was discussed in the context of a systemd 
> > upload targeting experimental, where I suggested this should be handled 
> > by the tzdata package and not by systemd, as I considered tzdata the 
> > "primary" owner of that file [1]. systemd-localed also handles that file 
> > currently via a Debian specific patch, which we'd like to get rid of.
> > The information in /etc/timezone is basically redundant as you can just 
> > as easily get the information from looking where the /etc/localtime 
> > symlink points at. It also avoids that /etc/localtime and /etc/timezone 
> > get out-of-sync.
> > /etc/timezone is mostly a Debianism afaiu.
> > 
> > Benjamin was so kind to implement this suggestion swiftly and uploaded 
> > this to unstable.
> > If this is now causing regressions in several packages, it's probably ok 
> > to revert this change for bookworm.
> > I did briefly skim over the codesearch list, and found a lot of false 
> > positives and fixes for this issue are usually pretty simple, but yes, 
> > I'd say this could be done early in the trixie release cycle as well 
> > with an accompanying MBF.
> > 
> > Benjamin, would it cause a lot of trouble to revert this change again or 
> > how would you prefer to proceed?
> 
> I agree that restoring /etc/timezone is the right solution for the
> bookworm. I'll prepare a tzdata upload for it.

Thanks, much appreciated! As there is no other action required from the
release team, I am closing the RT bug.

Cheers

> 
> > [1] https://salsa.debian.org/systemd-team/systemd/-/merge_requests/189
> > 
> > Am 16.02.23 um 13:30 schrieb Sebastian Ramacher:
> > > On 2023-02-16 12:34:29 +0100, Daniel Leidert wrote:
> > > > Am Donnerstag, dem 16.02.2023 um 08:41 +0100 schrieb Paul Gevers:
> > > > > Control: tags -1 moreinfo
> > > > > Control: severity -1 normal
> > > > > 
> > > > > Hi Daniel,
> > > > > 
> > > > > On 16-02-2023 01:11, Daniel Leidert wrote:
> > > > > > I ask you to
> > > > > > find a reasonable approach to deal with this for the Bookworm
> > > > > > release.
> > > > > 
> > > > > That's not how we normally work. Please come with concrete proposals 
> > > > > and
> > > > > we can evaluate them.
> > > > 
> > > > Hi Paul. That is the release team's job. Your team should be on top of
> > > > that situation and control that. There is already a freeze in process.
> > > > You made that very clear. New transitions are not allowed. The date has
> > > > passed that re-introductions into Testing are not allowed anymore. And
> > > > people break other packages just like that? It is my expectation that
> > > > your team evaluates the situation together with the maintainer of
> > > > tzdata now, and then comes to a conclusion and a decision, how this
> > > > should be handled. codesearch.d.o proves that multiple packages use
> > > > code that relies on the existence of /etc/timezone. So, its removal
> > > > should have been handled in a coordinated way in the first place.
> > > > Either the maintainer of tzdata does a mass-bug filing, or this change
> > > > should be reverted.
> > > 
> > > I suggest you file a bug with the package that introduced any
> > > breakage first. I see no such bug against tzdata.
> > > 
> > > Cheers
> > > 
> > > > 
> > > > I have already spent two dozen unpaid hours of tracking down and
> > > > handling breakages introduced since February 7th(!!) by fellow DDs. I
> > > > spent multiple dozen hours of bug-fixing and uploading since the new
> > > > year started, to make sure users will get the software they expect in
> > > > Bookworm, also unpaid of course. And now I have to evaluate the impact
> > > > of the change in tzdata as well and create proposals? No. I'm not the
> > > > tzdata maintainer and I'm not a member of the release team. It is your
> > > > job to handle transitions.
> > > > 
> > > > 
> > > > And I suggest that you finally do your job and make sure that people
> > > > stop uploading breaking changes, so the work for Bookworm gets less and
> > > > not constantly more.
> > > > 
> > > > 
> > > > Daniel
> > > > 
> > > 
> > 
> 
> -- 
> Benjamin Drung
> Debian & Ubuntu Developer
> 

-- 
Sebastian Ramacher

Bug#1031360: rsyslog: SEGV on startup with truncated files in spool

[Matthew Vernon]

Hi,

On 16/02/2023 20:48, Michael Biebl wrote:

The important bits were in 30-remote-syslog.conf indeed. With that the 
issue was reproducible and I therefor forwarded this to upstream. See

https://github.com/rsyslog/rsyslog/issues/5085


Great, thank you.

I didn't explicitly ask you, if I could attach your config files/spool 
files there, but I assumed as you attached it to the Debian bug tracker, 
that this is ok. If not, please let me know.


Yes, that's fine.

Regards,

Matthew

Bug#1031413: Slow backward search in long lines

[Robert Alm Nilsson]

Package: w3m
Version: 0.5.3+git20230121-2
Severity: minor

When I search backward in w3m by using the '?' command, the program
freezes with high CPU usage for a bit of time if the found text is near
the end of a very long line.

How to reproduce the issue:

printf 'first line\nsecond line is %*s a long line\nthird line\n' 1 '' 
> test.txt
w3m test.txt

Run those commands and then go to the third line and search backward for
the word "line".  Now the program will freeze for a second.  If you
increase the number 1, the freezing time will increase with the
square of that number.

The reason that this happens when searching backward but not forward is
that in the function `backwardSearch` in search.c there is this loop:

while (regexMatch(...) == 1)

but in `forwardSearch` it's just an if statement:

if (regexMatch(...) == 1)

That means that when searching backward, we do one regexMatch for each
character on the line and since the regexMatch itself already searches
through the characters, that's pretty wasteful and that's what gives us
the squared times.

It should be possible to change this so that an if statement is used in
`backwardSearch` just like in `forwardSearch`.  Maybe there could be two
versions of `regexMatch` where one of them searches backwards or just
returns the last match instead of the first one so that we don't have to
call it in a loop.