Bug#1021857: llvm-14-dev: ClangConfig.cmake is still broken
Package: llvm-14-dev Followup-For: Bug #1021857 Hi, (sending properly again) 1:14.0.6-6 does some changes, however it does not fix all of it; this is while trying to build qtcreator: CMake Error at /usr/lib/llvm-14/lib/cmake/clang/ClangTargets.cmake:756 (message): The imported target "diagtool" references the file "/usr/lib/llvm-14/bin/diagtool" but this file does not exist. Possible reasons include: * The file was deleted, renamed, or moved to another location. * An install or uninstall procedure did not complete successfully. * The installation package was faulty and contained "/usr/lib/llvm-14/lib/cmake/clang/ClangTargets.cmake" but not all the files it references. Call Stack (most recent call first): /usr/lib/cmake/clang-14/ClangConfig.cmake:19 (include) cmake/FindClang.cmake:1 (find_package) CMakeLists.txt:100 (find_package) In practice, ClangTargets.cmake is still broken, as it tries to look for tools. I think that the "cmake-test" is incomplete, as it only tests the "LLVM" cmake module and not the "Clang" one; adding a new check for find_package(Clang) should help to make sure all the cmake bits are working as expected. Thanks, -- Pino
Processed: tagging 1022555, tagging 1022556, found 1022556 in 4.96-6, tagging 1022560
Processing commands for cont...@bugs.debian.org: > tags 1022555 + upstream Bug #1022555 [src:tiff] tiff: CVE-2022-3627 CVE-2022-3626 CVE-2022-3599 CVE-2022-3598 CVE-2022-3597 CVE-2022-3570 Added tag(s) upstream. > tags 1022556 + upstream Bug #1022556 [src:exim4] exim4: CVE-2022-3620 Added tag(s) upstream. > found 1022556 4.96-6 Bug #1022556 [src:exim4] exim4: CVE-2022-3620 Marked as found in versions exim4/4.96-6. > tags 1022560 + upstream Bug #1022560 [src:libx11] libx11: CVE-2022-3554 Added tag(s) upstream. > thanks Stopping processing here. Please contact me if you need assistance. -- 1022555: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1022555 1022556: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1022556 1022560: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1022560 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1020619: marked as done (libstdc++-arm-none-eabi-newlib: Fails to install because of incorrect versioned depency on gcc-arm-none-eabi)
Your message dated Sun, 23 Oct 2022 22:31:13 -0700 with message-id <87sfjdg53y@keithp.com> and subject line Re: libstdc++-arm-none-eabi-newlib: Fails to install because of incorrect versioned depency on gcc-arm-none-eabi has caused the Debian Bug report #1020619, regarding libstdc++-arm-none-eabi-newlib: Fails to install because of incorrect versioned depency on gcc-arm-none-eabi to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 1020619: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1020619 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: libstdc++-arm-none-eabi-newlib Version: 15:10.3-2021.07-4+20 Severity: serious Justification: Policy 2.2.1 This package depends on gcc-arm-none-eabi (= 15:10.3-2021.07-4), however the latter version does not exist in main because there has been a binNMU, so the version present is 15:10.3-2021.07-4+b1. -- System Information: Debian Release: bookworm/sid APT prefers unstable-debug APT policy: (500, 'unstable-debug'), (500, 'unstable'), (500, 'stable'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 5.18.0-4-amd64 (SMP w/24 CPU threads; PREEMPT) Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE Locale: LANG=C.UTF-8, LC_CTYPE=C.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 libstdc++-arm-none-eabi-newlib depends on: ii gcc-arm-none-eabi15:10.3-2021.07-4+b1 ii libnewlib-arm-none-eabi 3.3.0-1.3 ii libnewlib-dev3.3.0-1.3 pn libstdc++-arm-none-eabi-dev Versions of packages libstdc++-arm-none-eabi-newlib recommends: ii binutils-arm-none-eabi 2.38.90.20220713-2+17 ii gcc-arm-none-eabi 15:10.3-2021.07-4+b1 libstdc++-arm-none-eabi-newlib suggests no packages. --- End Message --- --- Begin Message --- Version 21 matches gcc-arm-none-eabi version 15:11.3.rel1-1. -- -keith signature.asc Description: PGP signature --- End Message ---
Bug#1022421: marked as done (node-sinon: FTBFS: undefined should allow a fake on the global if a fake on a customer target is already defined)
Your message dated Mon, 24 Oct 2022 05:36:27 +
with message-id
and subject line Bug#1022421: fixed in node-sinon 14.0.1+ds+~cs71.23.28-1
has caused the Debian Bug report #1022421,
regarding node-sinon: FTBFS: undefined should allow a fake on the global if
a fake on a customer target is already defined
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)
--
1022421: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1022421
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: node-sinon
Version: 14.0.0+ds+~cs71.22.25-4
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20221023 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
>dh_auto_configure --buildsystem=nodejs
> Link ./node_modules/diff -> /usr/share/nodejs/diff
> Link node_modules/bane -> ../bane
> Link node_modules/just-extend -> ../just-extend
> Link node_modules/nise -> ../nise
> Link node_modules/@sinonjs/commons -> ../../sinonjscommons
> Link node_modules/@sinonjs/fake-timers -> ../../sinonjsfake-timers
> Link node_modules/@sinonjs/formatio -> ../../sinonjsformatio
> Link node_modules/@sinonjs/referee -> ../../sinonjsreferee
> Link node_modules/@sinonjs/referee-sinon -> ../../sinonjsreferee-sinon
> Link node_modules/@sinonjs/samsam -> ../../sinonjssamsam
> Link node_modules/@sinonjs/text-encoding -> ../../sinonjstext-encoding
> Link node_modules/@types/sinon -> ../../typessinon
> Link node_modules/@types/sinonjs__fake-timers ->
> ../../typessinonjs-fake-timers
>dh_auto_build --buildsystem=nodejs
> No build command found, searching known files
> No build command found, searching known files
> No build command found, searching known files
> No build command found, searching known files
> No build command found, searching known files
> No build command found, searching known files
> Found debian/nodejs/./build
> cd ./. && sh -ex debian/nodejs/./build
> + mkdir -p pkg
> + export NODE_PATH=node_modules:/usr/share/nodejs
> + node build.cjs
>dh_auto_test --buildsystem=nodejs
> ln -s ../debian/tests/test_modules/jsdom-global
> node_modules/jsdom-global
> ln -s ../debian/tests/test_modules/jsverify node_modules/jsverify
> ln -s ../debian/tests/test_modules/knuth-shuffle
> node_modules/knuth-shuffle
> ln -s ../debian/tests/test_modules/lazy-seq node_modules/lazy-seq
> ln -s ../debian/tests/test_modules/native-promise-only
> node_modules/native-promise-only
> ln -s ../debian/tests/test_modules/rc4 node_modules/rc4
> ln -s ../debian/tests/test_modules/trampa node_modules/trampa
> ln -s ../debian/tests/test_modules/typify-parser
> node_modules/typify-parser
> ln -s ../. node_modules/sinon
> cd ./sinonjscommons && sh -ex ../debian/nodejs/sinonjscommons/test
> + mocha --recursive lib/**/*.test.js
>
>
> calledInOrder
> given single array argument
> when stubs were called in expected order
> undefined returns true
> when stubs were called in unexpected order
> undefined returns false
> given multiple arguments
> when stubs were called in expected order
> undefined returns true
> when stubs were called in unexpected order
> undefined returns false
>
> className
> undefined returns the class name of an instance
> undefined returns 'Object' for {}
> undefined returns null for an object that has no prototype
> undefined returns null for an object whose prototype was mangled
>
> deprecated
> defaultMsg
> undefined should return a string
> printWarning
> when `process.emitWarning` is defined
> undefined should call process.emitWarning with a msg
> when `process.emitWarning` is undefined
> when `console.info` is defined
> undefined should call `console.info` with a message
> when `console.info` is undefined
> undefined should call `console.log` with a message
> wrap
> undefined should return a wrapper function
> undefined should assign the prototype of the passed method
> w
Bug#1021857: reopening 1021857
reopen 1021857 thanks 1:14.0.6-6 does some changes, however it does not fix all of it; this is while trying to build qtcreator: CMake Error at /usr/lib/llvm-14/lib/cmake/clang/ClangTargets.cmake:756 (message): The imported target "diagtool" references the file "/usr/lib/llvm-14/bin/diagtool" but this file does not exist. Possible reasons include: * The file was deleted, renamed, or moved to another location. * An install or uninstall procedure did not complete successfully. * The installation package was faulty and contained "/usr/lib/llvm-14/lib/cmake/clang/ClangTargets.cmake" but not all the files it references. Call Stack (most recent call first): /usr/lib/cmake/clang-14/ClangConfig.cmake:19 (include) cmake/FindClang.cmake:1 (find_package) CMakeLists.txt:100 (find_package) Thanks, -- Pino
Processed: reopening 1021857
Processing commands for cont...@bugs.debian.org:
> reopen 1021857
Bug #1021857 {Done: Sylvestre Ledru } [llvm-14-dev]
llvm-14-dev: CMake Error in LLVMExports.cmake: The imported target "sancov"
references the file "/usr/lib/llvm-14/bin/sancov" but this file does not exist.
Bug #1022334 {Done: Sylvestre Ledru } [llvm-14-dev]
qtcreator: FTBFS: make[1]: *** [debian/rules:26: override_dh_auto_configure]
Error 2
Bug #1022337 {Done: Sylvestre Ledru } [llvm-14-dev]
qt6-tools: FTBFS: The imported target "sancov" references the file
"/usr/lib/llvm-14/bin/sancov" but this file does not exist.
Bug #1022409 {Done: Sylvestre Ledru } [llvm-14-dev] ccls:
FTBFS: make[1]: *** [debian/rules:18: override_dh_auto_configure] Error 2
Bug #1022414 {Done: Sylvestre Ledru } [llvm-14-dev]
bpftrace: FTBFS: make[1]: *** [debian/rules:7: override_dh_auto_configure]
Error 2
'reopen' may be inappropriate when a bug has been closed with a version;
all fixed versions will be cleared, and you may need to re-add them.
Bug reopened
No longer marked as fixed in versions llvm-toolchain-14/1:14.0.6-6.
No longer marked as fixed in versions llvm-toolchain-14/1:14.0.6-6.
No longer marked as fixed in versions llvm-toolchain-14/1:14.0.6-6.
No longer marked as fixed in versions llvm-toolchain-14/1:14.0.6-6.
No longer marked as fixed in versions llvm-toolchain-14/1:14.0.6-6.
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
1021857: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1021857
1022334: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1022334
1022337: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1022337
1022409: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1022409
1022414: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1022414
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Bug#1022428: marked as done (pdfkit: FTBFS: TypeError: dist must be a Distribution instance)
Your message dated Mon, 24 Oct 2022 04:04:14 +
with message-id
and subject line Bug#1022428: fixed in pdfkit 1.0.0-2
has caused the Debian Bug report #1022428,
regarding pdfkit: FTBFS: TypeError: dist must be a Distribution instance
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)
--
1022428: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1022428
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: pdfkit
Version: 1.0.0-1
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20221023 ftbfs-bookworm
Hi,
During a rebuild of all packages in sid, your package failed to build
on amd64.
Relevant part (hopefully):
> fakeroot debian/rules clean
> dh clean --with python3 --buildsystem=pybuild
>dh_auto_clean -O--buildsystem=pybuild
> I: pybuild base:240: python3.10 setup.py clean
> /<>/setup.py:1: DeprecationWarning: The distutils package is
> deprecated and slated for removal in Python 3.12. Use setuptools or check PEP
> 632 for potential alternatives
> from distutils.core import setup
> /usr/lib/python3/dist-packages/_distutils_hack/__init__.py:18: UserWarning:
> Distutils was imported before Setuptools, but importing Setuptools also
> replaces the `distutils` module in `sys.modules`. This may lead to
> undesirable behaviors or errors. To avoid these issues, avoid using distutils
> directly, ensure that setuptools is installed in the traditional way (e.g.
> not an editable install), and/or make sure that setuptools is always imported
> before distutils.
> warnings.warn(
> /usr/lib/python3/dist-packages/_distutils_hack/__init__.py:33: UserWarning:
> Setuptools is replacing distutils.
> warnings.warn("Setuptools is replacing distutils.")
> /usr/lib/python3.10/distutils/dist.py:274: UserWarning: Unknown distribution
> option: 'tests_require'
> warnings.warn(msg)
> running clean
> Traceback (most recent call last):
> File "/<>/setup.py", line 28, in
> setup(
> File "/usr/lib/python3.10/distutils/core.py", line 148, in setup
> dist.run_commands()
> File "/usr/lib/python3.10/distutils/dist.py", line 966, in run_commands
> self.run_command(cmd)
> File "/usr/lib/python3.10/distutils/dist.py", line 983, in run_command
> cmd_obj = self.get_command_obj(command)
> File "/usr/lib/python3.10/distutils/dist.py", line 858, in get_command_obj
> cmd_obj = self.command_obj[command] = klass(self)
> File "/usr/lib/python3/dist-packages/setuptools/__init__.py", line 158, in
> __init__
> super().__init__(dist)
> File "/usr/lib/python3/dist-packages/setuptools/_distutils/cmd.py", line
> 59, in __init__
> raise TypeError("dist must be a Distribution instance")
> TypeError: dist must be a Distribution instance
> E: pybuild pybuild:379: clean: plugin distutils failed with: exit code=1:
> python3.10 setup.py clean
> dh_auto_clean: error: pybuild --clean -i python{version} -p 3.10 returned
> exit code 13
> make: *** [debian/rules:6: clean] Error 25
The full build log is available from:
http://qa-logs.debian.net/2022/10/23/pdfkit_1.0.0-1_unstable.log
All bugs filed during this archive rebuild are listed at:
https://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=ftbfs-20221023;users=lu...@debian.org
or:
https://udd.debian.org/bugs/?release=na=ign=7=7=only=ftbfs-20221023=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 marking it as 'affects'-ing
this package. See https://www.debian.org/Bugs/server-control#affects
If you fail to reproduce this, please provide a build log and diff it with mine
so that we can identify if something relevant changed in the meantime.
--- End Message ---
--- Begin Message ---
Source: pdfkit
Source-Version: 1.0.0-2
Done: Scott Kitterman
We believe that the bug you reported is fixed in the latest version of
pdfkit, which is due to be installed in the Debian FTP archive.
A summary of the changes between this version and the previous one is
attached.
Thank you for reporting the bug, which will now be closed. If you
have further comments please address them to 1022...@bugs.debian.org,
and the maintainer will reopen the bug report if appropr
Processed: Re: Bug#1022291: hydrapaper: FTBFS: ModuleNotFoundError: No module named 'gi'
Processing commands for cont...@bugs.debian.org: > reassign 1022291 blueprint-compiler Bug #1022291 [src:hydrapaper] hydrapaper: FTBFS: ModuleNotFoundError: No module named 'gi' Bug reassigned from package 'src:hydrapaper' to 'blueprint-compiler'. No longer marked as found in versions hydrapaper/3.3.1-2. Ignoring request to alter fixed versions of bug #1022291 to the same values previously set > affects 1022291 + hydrapaper Bug #1022291 [blueprint-compiler] hydrapaper: FTBFS: ModuleNotFoundError: No module named 'gi' Added indication that 1022291 affects hydrapaper > thanks Stopping processing here. Please contact me if you need assistance. -- 1022291: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1022291 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1022291: hydrapaper: FTBFS: ModuleNotFoundError: No module named 'gi'
Control: reassign -1 blueprint-compiler affects -1 + hydrapaper -- Greetings, looking into the build log, I find this: > Traceback (most recent call last): > File "/usr/bin/blueprint-compiler", line 37, in > from blueprintcompiler import main > File "/usr/lib/python3/dist-packages/blueprintcompiler/main.py", line 25, in > from .lsp import LanguageServer > File "/usr/lib/python3/dist-packages/blueprintcompiler/lsp.py", line 24, in > from .completions import complete > File "/usr/lib/python3/dist-packages/blueprintcompiler/completions.py", line 22, in > from . import gir, language > File "/usr/lib/python3/dist-packages/blueprintcompiler/gir.py", line 24, in > import gi # type: ignore > ModuleNotFoundError: No module named 'gi' Looks like blueprint-compiler tries to import gi but is unable to. hydrapaper Build-Depends on python3-gi (and blueprint-compiler for that matter). It seems that blueprint-compiler should depend on python3-gi to funcion properly since it imports it when it's called. It's a run dependency for blueprint-compiler, and not a build-dependency for hydrapaper. I'm therefore reassigning to blueprint-compiler and tagging it as 'affects'-ing hydrapaper. Cheers, Francisco On 10/23/22 09:38, Lucas Nussbaum wrote: Source: hydrapaper Version: 3.3.1-2 Severity: serious Justification: FTBFS Tags: bookworm sid ftbfs User: lu...@debian.org Usertags: ftbfs-20221023 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 dh_update_autotools_config dh_autoreconf dh_auto_configure cd obj-x86_64-linux-gnu && LC_ALL=C.UTF-8 meson .. --wrap-mode=nodownload --buildtype=plain --prefix=/usr --sysconfdir=/etc --localstatedir=/var --libdir=lib/x86_64-linux-gnu The Meson build system Version: 0.63.3 Source dir: /<> Build dir: /<>/obj-x86_64-linux-gnu Build type: native build Project name: hydrapaper Project version: 3.3.1 Host machine cpu family: x86_64 Host machine cpu: x86_64 Message: Looking for dependencies Found pkg-config: /usr/bin/pkg-config (0.29.2) Run-time dependency glib-2.0 found: YES 2.74.0 Run-time dependency gobject-introspection-1.0 found: YES 1.74.0 Run-time dependency gtk4 found: YES 4.8.1 Run-time dependency libadwaita-1 found: YES 1.2.0 Program python3 found: YES (/usr/bin/python3) Run-time dependency dbus-1 found: YES 1.14.4 Message: Daemon Enabled: True Configuring hydrapaperd using configuration Configuring org.gabmus.hydrapaper.desktop.i18n.in using configuration Program msgfmt found: YES (/usr/bin/msgfmt) Configuring org.gabmus.hydrapaper.service using configuration Configuring org.gabmus.hydrapaper.Daemon.service using configuration Configuring org.gabmus.hydrapaperd.service using configuration Configuring org.gabmus.hydrapaper.Daemon.desktop.i18n.in using configuration Configuring org.gabmus.hydrapaper.gschema.xml using configuration Program blueprint-compiler found: YES (/usr/bin/blueprint-compiler) Configuring aboutdialog.ui using configuration Found pkg-config: /usr/bin/pkg-config (0.29.2) Program glib-compile-resources found: YES (/usr/bin/glib-compile-resources) Program glib-compile-schemas found: YES (/usr/bin/glib-compile-schemas) Program appstreamcli found: NO Configuring hydrapaper using configuration Message: Update translations Program msginit found: YES (/usr/bin/msginit) Program msgmerge found: YES (/usr/bin/msgmerge) Program xgettext found: YES (/usr/bin/xgettext) Program pandoc found: YES (/usr/bin/pandoc) Message: Compiling man page from markdown to groff WARNING: You should add the boolean check kwarg to the run_command call. It currently defaults to false, but it will default to true in future releases of meson. See also: https://github.com/mesonbuild/meson/issues/9300 Message: Man page compilation succeeded, installing Build targets in project: 16 hydrapaper 3.3.1 User defined options buildtype: plain libdir : lib/x86_64-linux-gnu localstatedir: /var prefix : /usr sysconfdir : /etc wrap_mode: nodownload Found ninja-1.11.1 at /usr/bin/ninja dh_auto_build cd obj-x86_64-linux-gnu && LC_ALL=C.UTF-8 ninja -j8 -v [1/12] /usr/bin/glib-compile-schemas --targetdir data ../data No schema files found: doing nothing. [2/12] /usr/bin/msgfmt ../po/es.po -o po/es/LC_MESSAGES/hydrapaper.mo [3/12] /usr/bin/msgfmt ../po/de.po -o po/de/LC_MESSAGES/hydrapaper.mo [4/12] /usr/bin/msgfmt ../po/it.po -o po/it/LC_MESSAGES/hydrapaper.mo [5/12] /usr/bin/msgfmt ../po/pt_BR.po -o po/pt_BR/LC_MESSAGES/hydrapaper.mo [6/12] /usr/bin/msgfmt ../po/sv.po -o po/sv/LC_MESSAGES/hydrapaper.mo [7/12] /usr/bin/msgfmt ../po/ru.po -o po/ru/LC_MESSAGES/hydrapaper.mo [8/12] /usr/bin/blueprin
Processed: closing 1021735
Processing commands for cont...@bugs.debian.org: > close 1021735 3.4.3-4 Bug #1021735 [src:libffi] libffi breaks python3.10 autopkgtest on arm64 (and 5 other packages) Marked as fixed in versions libffi/3.4.3-4. Bug #1021735 [src:libffi] libffi breaks python3.10 autopkgtest on arm64 (and 5 other packages) Marked Bug as done > thanks Stopping processing here. Please contact me if you need assistance. -- 1021735: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1021735 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1022364: marked as done (qutebrowser: FTBFS: dh_usrlocal: error: debian/qutebrowser/usr/local/bin/qutebrowser is not a directory)
Your message dated Mon, 24 Oct 2022 02:35:50 + with message-id and subject line Bug#1022364: fixed in qutebrowser 2.5.2-2 has caused the Debian Bug report #1022364, regarding qutebrowser: FTBFS: dh_usrlocal: error: debian/qutebrowser/usr/local/bin/qutebrowser is not a directory to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 1022364: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1022364 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: qutebrowser Version: 2.5.2-1 Severity: serious Justification: FTBFS Tags: bookworm sid ftbfs User: lu...@debian.org Usertags: ftbfs-20221023 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_installchangelogs doc/changelog.asciidoc > make[1]: Leaving directory '/<>' >dh_installman -O--buildsystem=pybuild -O--link-doc=qutebrowser >dh_python3 -O--buildsystem=pybuild -O--link-doc=qutebrowser > I: dh_python3 tools:114: replacing shebang in > debian/qutebrowser/usr/share/qutebrowser/scripts/dictcli.py > I: dh_python3 tools:114: replacing shebang in > debian/qutebrowser/usr/share/qutebrowser/scripts/hist_importer.py > I: dh_python3 tools:114: replacing shebang in > debian/qutebrowser/usr/share/qutebrowser/scripts/hostblock_blame.py > I: dh_python3 tools:114: replacing shebang in > debian/qutebrowser/usr/share/qutebrowser/scripts/importer.py > I: dh_python3 tools:114: replacing shebang in > debian/qutebrowser/usr/share/qutebrowser/scripts/keytester.py > I: dh_python3 tools:114: replacing shebang in > debian/qutebrowser/usr/share/qutebrowser/scripts/mkvenv.py > I: dh_python3 tools:114: replacing shebang in > debian/qutebrowser/usr/share/qutebrowser/scripts/opengl_info.py > I: dh_python3 tools:114: replacing shebang in > debian/qutebrowser/usr/share/qutebrowser/userscripts/add-nextcloud-bookmarks > I: dh_python3 tools:114: replacing shebang in > debian/qutebrowser/usr/share/qutebrowser/userscripts/add-nextcloud-cookbook > I: dh_python3 tools:114: replacing shebang in > debian/qutebrowser/usr/share/qutebrowser/userscripts/getbib > I: dh_python3 tools:114: replacing shebang in > debian/qutebrowser/usr/share/qutebrowser/userscripts/openfeeds > I: dh_python3 tools:114: replacing shebang in > debian/qutebrowser/usr/share/qutebrowser/userscripts/qute-bitwarden > I: dh_python3 tools:114: replacing shebang in > debian/qutebrowser/usr/share/qutebrowser/userscripts/qute-keepass > I: dh_python3 tools:114: replacing shebang in > debian/qutebrowser/usr/share/qutebrowser/userscripts/qute-keepassxc > I: dh_python3 tools:114: replacing shebang in > debian/qutebrowser/usr/share/qutebrowser/userscripts/qute-lastpass > I: dh_python3 tools:114: replacing shebang in > debian/qutebrowser/usr/share/qutebrowser/userscripts/qute-pass > I: dh_python3 tools:114: replacing shebang in > debian/qutebrowser/usr/share/qutebrowser/userscripts/readability > I: dh_python3 tools:114: replacing shebang in > debian/qutebrowser/usr/share/qutebrowser/userscripts/ripbang > I: dh_python3 tools:114: replacing shebang in > debian/qutebrowser/usr/share/qutebrowser/userscripts/tor_identity > I: dh_python3 pydist:302: Cannot find package that provides dataclasses. > Please add package that provides it to Build-Depends or add "dataclasses > python3-dataclasses" line to debian/py3dist-overrides or add proper > dependency to Depends by hand and ignore this info. > I: dh_python3 pydist:302: Cannot find package that provides dataclasses. > Please add package that provides it to Build-Depends or add "dataclasses > python3-dataclasses" line to debian/py3dist-overrides or add proper > dependency to Depends by hand and ignore this info. >dh_installsystemduser -O--buildsystem=pybuild -O--link-doc=qutebrowser >dh_installmenu -O--buildsystem=pybuild -O--link-doc=qutebrowser >dh_lintian -O--buildsystem=pybuild -O--link-doc=qutebrowser >dh_icons -O--buildsystem=pybuild -O--link-doc=qutebrowser >dh_perl -O--buildsystem=pybuild -O--link-doc=qutebrowser >dh_usrlocal -O--buildsystem=pybuild -O--link-doc=qutebrowser > dh_usrlocal: error: debian/qutebrowser/usr/local/bin/qutebrowser is not a > directory > make: *** [debian/rules:6: binary] Error 25 The full build log is available from: http://qa-logs.debian.net/2022/10/23
Bug#1022364: qutebrowser: FTBFS: dh_usrlocal: error: debian/qutebrowser/usr/local/bin/qutebrowser is not a directory
Control: tag -1 + pending Hi again, Axel Beckert wrote: > > >dh_usrlocal -O--buildsystem=pybuild -O--link-doc=qutebrowser > > > dh_usrlocal: error: debian/qutebrowser/usr/local/bin/qutebrowser is not a > > > directory > > This is clearly the one which makes the build stop at the end. > > Looks like something suddenly installs the qutebrowser binary _also_ > into /usr/local/bin/. I so far just have no idea yet what or why. > > Actually the following override in debian/rules would fix it and the > resulting .deb has no debdiff to 2.5.2-1 as in unstable/testing, but > I'd first like to understand what actually goes wrong instead of > fixing symptoms: > > override_dh_usrlocal: > rm -rvf debian/qutebrowser/usr/local/ I'm quite sure the culprit lies hidden somewhere in an python3-setuptools upstream release between probably 65.3.0 (seems to have worked for the past 5 weeks unless Lucas' rebuilds happen more seldom, in which case 59.6.0 would be the last known working version) and 65.5.0 (clearly broken, installs qutebrowser and only that file into /usr/bin/ _and_ /usr/local/bin/). Since the upstream changelog is rather terse about potential huge changes like e.g. … * #3576: Updated version of ``validate_pyproject``. * #3617: Merge with pypa/distutils@6852b20 including fix for pypa/distutils#181. … I have no idea which of the changes actually could have triggered this issue. So I'm going with the above mentioned hardball fix. Regards, Axel -- ,''`. | Axel Beckert , https://people.debian.org/~abe/ : :' : | Debian Developer, ftp.ch.debian.org Admin `. `' | 4096R: 2517 B724 C5F6 CA99 5329 6E61 2FF9 CD59 6126 16B5 `-| 1024D: F067 EA27 26B9 C3FC 1486 202E C09E 1D89 9593 0EDE
Processed: Re: Bug#1022364: qutebrowser: FTBFS: dh_usrlocal: error: debian/qutebrowser/usr/local/bin/qutebrowser is not a directory
Processing control commands: > tag -1 + pending Bug #1022364 [src:qutebrowser] qutebrowser: FTBFS: dh_usrlocal: error: debian/qutebrowser/usr/local/bin/qutebrowser is not a directory Added tag(s) pending. -- 1022364: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1022364 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1022431: marked as done (sasview: FTBFS: distutils.errors.DistutilsClassError: command class must subclass Command)
Your message dated Mon, 24 Oct 2022 11:30:02 +1100
with message-id <5396339.NICylAqOLd@simurgh>
and subject line Re: Bug#1022431: sasview: FTBFS:
distutils.errors.DistutilsClassError: command class must subclass Command
has caused the Debian Bug report #1022431,
regarding sasview: FTBFS: distutils.errors.DistutilsClassError: command class
must subclass Command
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)
--
1022431: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1022431
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: sasview
Version: 5.0.4-1
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20221023 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 '/<>'
> # build the arch-dep packages to be able to build the docs
> dh_auto_build
> I: pybuild base:240: /usr/bin/python3 setup.py build
> /<>/setup.py:12: DeprecationWarning: The distutils package is
> deprecated and slated for removal in Python 3.12. Use setuptools or check PEP
> 632 for potential alternatives
> from distutils.core import Command
> /usr/lib/python3/dist-packages/_distutils_hack/__init__.py:18: UserWarning:
> Distutils was imported before Setuptools, but importing Setuptools also
> replaces the `distutils` module in `sys.modules`. This may lead to
> undesirable behaviors or errors. To avoid these issues, avoid using distutils
> directly, ensure that setuptools is installed in the traditional way (e.g.
> not an editable install), and/or make sure that setuptools is always imported
> before distutils.
> warnings.warn(
> /usr/lib/python3/dist-packages/_distutils_hack/__init__.py:33: UserWarning:
> Setuptools is replacing distutils.
> warnings.warn("Setuptools is replacing distutils.")
> Generating ./src/sas/qtgui/Utilities/UI/PluginManagerUI.py ...
> Generating ./src/sas/qtgui/Utilities/UI/AddMultEditorUI.py ...
> Generating ./src/sas/qtgui/Utilities/UI/FileConverterUI.py ...
> Generating ./src/sas/qtgui/Utilities/UI/ImageViewerOptionsUI.py ...
> Generating ./src/sas/qtgui/Utilities/UI/TabbedModelEditor.py ...
> Generating ./src/sas/qtgui/Utilities/UI/ReportDialogUI.py ...
> Generating ./src/sas/qtgui/Utilities/UI/GridPanelUI.py ...
> Generating ./src/sas/qtgui/Utilities/UI/ModelEditor.py ...
> Generating ./src/sas/qtgui/Utilities/UI/PluginDefinitionUI.py ...
> Generating ./src/sas/qtgui/Utilities/UI/FrameSelectUI.py ...
> Generating ./src/sas/qtgui/Utilities/UI/ImageViewerUI.py ...
> Generating ./src/sas/qtgui/Perspectives/Invariant/UI/TabbedInvariantUI.py ...
> Generating ./src/sas/qtgui/Perspectives/Invariant/UI/InvariantDetailsUI.py ...
> Generating ./src/sas/qtgui/Perspectives/Corfunc/UI/CorfuncPanel.py ...
> Generating ./src/sas/qtgui/Perspectives/Inversion/UI/TabbedInversionUI.py ...
> Generating ./src/sas/qtgui/Perspectives/Inversion/UI/DMaxExplorer.py ...
> Generating ./src/sas/qtgui/Perspectives/Fitting/UI/ConstraintWidgetUI.py ...
> Generating ./src/sas/qtgui/Perspectives/Fitting/UI/ComplexConstraintUI.py ...
> Generating ./src/sas/qtgui/Perspectives/Fitting/UI/FittingOptionsUI.py ...
> Generating ./src/sas/qtgui/Perspectives/Fitting/UI/FittingWidgetUI.py ...
> Generating ./src/sas/qtgui/Perspectives/Fitting/UI/OptionsWidgetUI.py ...
> Generating ./src/sas/qtgui/Perspectives/Fitting/UI/GPUTestResultsUI.py ...
> Generating ./src/sas/qtgui/Perspectives/Fitting/UI/MultiConstraintUI.py ...
> Generating ./src/sas/qtgui/Perspectives/Fitting/UI/OrderWidgetUI.py ...
> Generating ./src/sas/qtgui/Perspectives/Fitting/UI/SmearingWidgetUI.py ...
> Generating ./src/sas/qtgui/Perspectives/Fitting/UI/GPUOptionsUI.py ...
> Generating ./src/sas/qtgui/MainWindow/UI/AboutUI.py ...
> Generating ./src/sas/qtgui/MainWindow/UI/CategoryManagerUI.py ...
> Generating ./src/sas/qtgui/MainWindow/UI/AcknowledgementsUI.py ...
> Generating ./src/sas/qtgui/MainWindow/UI/WelcomePanelUI.py ...
> Generating ./src/sas/qtgui/MainWindow/UI/ChangeCategoryUI.py ...
> Generating ./src/sas/qtgui/MainWindow/UI/MainWindowUI.py ...
> Generating ./src/sas/qtgui/MainWindow/UI/DataExplorerUI.py ...
> Generating ./src/sas/qtgui/MainWindow/UI/TabbedFileLoadUI.py ...
> Generating ./src/sas/qtgui/MainWindow/UI/ChangeNameUI.py ...
> Generating ./src/sas/qtgui/Plottin
Bug#1022363: marked as done (binutils-riscv64-unknown-elf: FTBFS: dh_auto_configure: error: invalid or non-existing path to the source directory: binutils-2.39-8+3)
Your message dated Sun, 23 Oct 2022 23:34:23 + with message-id and subject line Bug#1022363: fixed in binutils-riscv64-unknown-elf 4 has caused the Debian Bug report #1022363, regarding binutils-riscv64-unknown-elf: FTBFS: dh_auto_configure: error: invalid or non-existing path to the source directory: binutils-2.39-8+3 to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 1022363: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1022363 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: binutils-riscv64-unknown-elf Version: 3 Severity: serious Justification: FTBFS Tags: bookworm sid ftbfs User: lu...@debian.org Usertags: ftbfs-20221023 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 -Dbinutils-2.39-8+3 -Bbuild >dh_update_autotools_config -O-Dbinutils-2.39-8\+3 -O-Bbuild >dh_autoreconf -O-Dbinutils-2.39-8\+3 -O-Bbuild >debian/rules override_dh_auto_configure > make[1]: Entering directory '/<>' > tar xf /usr/src/binutils/binutils-*.tar.* > mkdir -p debian/stamp > cp /usr/share/doc/binutils-source/copyright debian/copyright > touch debian/stamp/tar > dh_auto_configure -Dbinutils-2.39-8+3 -Bbuild -- --target=riscv64-unknown-elf > --prefix=/usr/lib --bindir=/usr/bin --libdir=/usr/lib/riscv64-unknown-elf > --infodir=/usr/share/doc/binutils-riscv64-unknown-elf/info > --htmldir=/usr/share/doc/binutils-riscv64-unknown-elf/html > --pdfdir=/usr/share/doc/binutils-riscv64-unknown-elf/pdf > --mandir=/usr/share/man --disable-nls --disable-werror --enable-plugins > --enable-interwork --with-system-zlib "--with-pkgversion=2.39-8+3" > --enable-deterministic-archives ASFLAGS="" CFLAGS="-g -O2 > -ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat > -Werror=format-security" CPPFLAGS="-Wdate-time -D_FORTIFY_SOURCE=2" > CXXFLAGS="-g -O2 -ffile-prefix-map=/<>=. > -fstack-protector-strong -Wformat -Werror=format-security" DFLAGS="-frelease" > FCFLAGS="-g -O2 -ffile-prefix-map=/<>=. > -fstack-protector-strong" FFLAGS="-g -O2 -ffile-prefix-map=/<>=. > -fstack-protector-strong" GCJFLAGS="-g -O2 > -ffile-prefix-map=/<>=. -fstack-protector-strong" > LDFLAGS="-Wl,-z,relro -Wl,-z,now" OBJCFLAGS="-g -O2 > -ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat > -Werror=format-security" OBJCXXFLAGS="-g -O2 > -ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat > -Werror=format-security" > dh_auto_configure: error: invalid or non-existing path to the source > directory: binutils-2.39-8+3 > make[1]: *** [debian/rules:53: override_dh_auto_configure] Error 25 The full build log is available from: http://qa-logs.debian.net/2022/10/23/binutils-riscv64-unknown-elf_3_unstable.log All bugs filed during this archive rebuild are listed at: https://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=ftbfs-20221023;users=lu...@debian.org or: https://udd.debian.org/bugs/?release=na=ign=7=7=only=ftbfs-20221023=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 marking it as 'affects'-ing this package. See https://www.debian.org/Bugs/server-control#affects If you fail to reproduce this, please provide a build log and diff it with mine so that we can identify if something relevant changed in the meantime. --- End Message --- --- Begin Message --- Source: binutils-riscv64-unknown-elf Source-Version: 4 Done: Keith Packard We believe that the bug you reported is fixed in the latest version of binutils-riscv64-unknown-elf, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 1022...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Keith Packard (supplier of updated binutils-riscv64-unknown-elf package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by maili
Bug#1022343: [Pkg-pascal-devel] Bug#1022343: view3dscene: FTBFS: view3dscene.lpr(63, 17) Fatal: Can't find unit CastleCubeMaps used by view3dscene
The new CGE (Castle Game Engine) indeed broke compatibility in this regard: the unit has been renamed CastleCubeMaps->CastleInternalCubeMaps . There are likely other small incompatibilities -- view3dscene in general "exercises" a lot of obscure CGE API (where we don't care much about backward compat, because we predict almost nobody except view3dscene is using something), and upgrading view3dscene and CGE usually have to be done together. In this case, view3dscene 4.2.0, which was released along with CGE, contains a fixed (and generally better) view3dscene version. See - https://castle-engine.io/wp/2022/09/12/castle-game-engine-7-0-alpha-2-release-many-new-components-lights-primitives-fonts-sound-new-cameras-terrains-sprite-sheet-editor-delphi/ , - https://github.com/castle-engine/castle-engine/releases/tag/v7.0-alpha.2 , - https://github.com/castle-engine/view3dscene/releases/tag/v4.2.0 . So my preferred way to solve this would be to just have view3dscene 4.2.0 in Debian. Regards, Michalis niedz., 23 paź 2022 o 15:15 Lucas Nussbaum napisał(a): > > Source: view3dscene > Version: 4.0.0-3 > Severity: serious > Justification: FTBFS > Tags: bookworm sid ftbfs > User: lu...@debian.org > Usertags: ftbfs-20221023 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 '/<>/embedded_data/screen_effects' > > file_to_pascal_string flashlight.glsl screen_effects_flashlight.glsl.inc > > file_to_pascal_string edge_detect.glsl screen_effects_edge_detect.glsl.inc > > make[3]: Leaving directory '/<>/embedded_data/screen_effects' > > make[2]: Leaving directory '/<>' > > fpc -k"-z relro -z now" -dRELEASE -Mobjfpc -Sh -Ci -Sm -Sc -Sg -Si -O2 -Xs > > -Fu/usr/lib/x86_64-linux-gnu/fpc/3.2.2/units/castle-game-engine > > code/view3dscene.lpr > > Compiling Release Version > > Free Pascal Compiler version 3.2.2+dfsg-15 [2022/08/20] for x86_64 > > Copyright (c) 1993-2021 by Florian Klaempfl and others > > Target OS: Linux for x86-64 > > Compiling code/view3dscene.lpr > > view3dscene.lpr(60,21) Warning: Unit "CastleProgress" is deprecated: "use > > TUIState and WaitForRenderAndCall to display progress of loading operations" > > view3dscene.lpr(63,17) Fatal: Can't find unit CastleCubeMaps used by > > view3dscene > > Fatal: Compilation aborted > > Error: /usr/bin/ppcx64 returned an error exitcode > > make[1]: *** [debian/rules:53: override_dh_auto_build-arch] Error 1 > > > The full build log is available from: > http://qa-logs.debian.net/2022/10/23/view3dscene_4.0.0-3_unstable.log > > All bugs filed during this archive rebuild are listed at: > https://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=ftbfs-20221023;users=lu...@debian.org > or: > https://udd.debian.org/bugs/?release=na=ign=7=7=only=ftbfs-20221023=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 marking 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. > > ___ > Pkg-pascal-devel mailing list > pkg-pascal-de...@alioth-lists.debian.net > https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-pascal-devel
Processed: prometheus-openstack-exporter: diff for NMU version 0.1.4-2.2
Processing control commands:
> tags 1021925 + patch
Bug #1021925 [src:prometheus-openstack-exporter] prometheus-openstack-exporter:
FTBFS dh_auto_clean: error: pybuild --clean -i python{version} -p 3.10 returned
exit code 13
Added tag(s) patch.
> tags 1021925 + pending
Bug #1021925 [src:prometheus-openstack-exporter] prometheus-openstack-exporter:
FTBFS dh_auto_clean: error: pybuild --clean -i python{version} -p 3.10 returned
exit code 13
Added tag(s) pending.
--
1021925: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1021925
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Bug#1021925: prometheus-openstack-exporter: diff for NMU version 0.1.4-2.2
Control: tags 1021925 + patch Control: tags 1021925 + pending Dear maintainer, I've prepared an NMU for prometheus-openstack-exporter (versioned as 0.1.4-2.2). The diff is attached to this message. I require a sponsor to have it uploaded. Best wishes, -- Raúl Benencia diff -Nru prometheus-openstack-exporter-0.1.4/debian/changelog prometheus-openstack-exporter-0.1.4/debian/changelog --- prometheus-openstack-exporter-0.1.4/debian/changelog 2022-10-15 03:39:55.0 -0700 +++ prometheus-openstack-exporter-0.1.4/debian/changelog 2022-10-23 15:30:50.0 -0700 @@ -1,3 +1,10 @@ +prometheus-openstack-exporter (0.1.4-2.2) unstable; urgency=medium + + * Non-maintainer upload. + * Disable setuptools package automatic discovery (Closes: #1021925) + + -- Raúl Benencia Sun, 23 Oct 2022 15:30:50 -0700 + prometheus-openstack-exporter (0.1.4-2.1) unstable; urgency=medium * Non-maintainer upload. diff -Nru prometheus-openstack-exporter-0.1.4/debian/patches/disable-package-autodiscovery.patch prometheus-openstack-exporter-0.1.4/debian/patches/disable-package-autodiscovery.patch --- prometheus-openstack-exporter-0.1.4/debian/patches/disable-package-autodiscovery.patch 1969-12-31 16:00:00.0 -0800 +++ prometheus-openstack-exporter-0.1.4/debian/patches/disable-package-autodiscovery.patch 2022-10-23 15:30:50.0 -0700 @@ -0,0 +1,32 @@ +From: Raúl Benencia +Date: Sat, 22 Oct 2022 11:17:24 -0700 +X-Dgit-Generated: 0.1.4-2.1 d12f61eaa20032eb3b7aa86269b355eebd10f6c4 +Bug-Debian: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1021925 +Forwarded: https://github.com/canonical/prometheus-openstack-exporter/pull/122 +Subject: Disable package autodiscovery + +Due to a change in setuptools>v61, package autodiscovery causes Debian +builds to fail with: + + error: Multiple top-level packages discovered in a flat-layout: ['snap', 'debian']. + +This can be fixed by disabling package autodiscovery. More information +in: + +- https://setuptools.pypa.io/en/latest/history.html#v61-0-0 +- https://github.com/pypa/setuptools/issues/3227 + +--- + +diff --git a/setup.py b/setup.py +index 3f42480..0b14083 100644 +--- a/setup.py b/setup.py +@@ -15,6 +15,7 @@ setup( + keywords=["prometheus", "openstack", "exporter"], + url="https://github.com/CanonicalLtd/prometheus-openstack-exporter;, + scripts=["prometheus-openstack-exporter"], ++packages=[], + install_requires=[ + "prometheus_client", + "python-keystoneclient<=3.10.0", diff -Nru prometheus-openstack-exporter-0.1.4/debian/patches/series prometheus-openstack-exporter-0.1.4/debian/patches/series --- prometheus-openstack-exporter-0.1.4/debian/patches/series 2022-10-15 03:39:55.0 -0700 +++ prometheus-openstack-exporter-0.1.4/debian/patches/series 2022-10-23 15:30:50.0 -0700 @@ -1 +1,2 @@ python3-shebang.patch +disable-package-autodiscovery.patch signature.asc Description: PGP signature
Processed: block 991761 with 1022506 1022359 1022359 1022359 1022539 1022423 10225462 1022547 1022233 1013121
Processing commands for cont...@bugs.debian.org: > block 991761 with 1022506 1022359 1022359 1022359 1022539 1022423 10225462 > 1022547 1022233 1013121 Bug #991761 [wnpp] ITP: swc -- A super-fast typescript / javascript compiler written in rust 991761 was blocked by: 996644 996634 991761 was not blocking any bugs. Added blocking bug(s) of 991761: 1022359, 1022506, 1022423, 1022233, 1013121, 1022547, and 1022539 > thanks Stopping processing here. Please contact me if you need assistance. -- 991761: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=991761 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1018896: marked as done (grcompiler: FTBFS on big endian)
Your message dated Sun, 23 Oct 2022 22:34:14 + with message-id and subject line Bug#1018896: fixed in grcompiler 5.2.1-0.2 has caused the Debian Bug report #1018896, regarding grcompiler: FTBFS on big endian to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 1018896: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1018896 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: grcompiler Version: 5.2.1-0.1 Severity: serious Tags: ftbfs Control: forwarded -1 grcompiler fails to build from scratch on big endian systems, including s390x, because of test fails: https://buildd.debian.org/status/fetch.php?pkg=grcompiler=s390x=5.2.1-0.1=1661942327 test 1 Start 1: compile_SchTest 1: Test command: /<>/obj-s390x-linux-gnu/compiler/grcompiler "-D" "-v4" "-e" "/<>/obj-s390x-linux-gnu/test/GrcRegressionTest/SchTest.gdlerr.txt" "/<>/test/GrcRegressionTest/fonts/SchMain.gdl" "/<>/test/GrcRegressionTest/fonts/SchInput.ttf" "SchTest.ttf" 1: Working Directory: /<>/obj-s390x-linux-gnu/test/GrcRegressionTest 1: Environment variables: 1: GDLPP=/<>/obj-s390x-linux-gnu/preprocessor/gdlpp 1: LD_LIBRARY_PATH=$LD_LIBRARY_PATH:/usr/include/../lib 1: Test timeout computed to be: 1500 test 4 Start 4: compile_CharisTest 4: Test command: /<>/obj-s390x-linux-gnu/compiler/grcompiler "-D" "-v2" "-e" "/<>/obj-s390x-linux-gnu/test/GrcRegressionTest/CharisTest.gdlerr.txt" "/<>/test/GrcRegressionTest/fonts/CharisMain.gdl" "/<>/test/GrcRegressionTest/fonts/CharisInput.ttf" "CharisTest.ttf" 4: Working Directory: /<>/obj-s390x-linux-gnu/test/GrcRegressionTest 4: Environment variables: 4: GDLPP=/<>/obj-s390x-linux-gnu/preprocessor/gdlpp 4: LD_LIBRARY_PATH=$LD_LIBRARY_PATH:/usr/include/../lib 4: Test timeout computed to be: 1500 1: Frexx C Preprocessor v1.5 Copyright (C) by FrexxWare 1993 - 1997. 1: Revised by SIL International for Graphite Description Language, Aug 23 2022 1: Graphite Compiler Version 5.2.1 [release build] 1: Copyright (c) 2002-2021, by SIL International. All rights reserved. 1: Reading input font... 1: 1: GDL file: /<>/test/GrcRegressionTest/fonts/SchMain.gdl 1: PreProcessor: /<>/obj-s390x-linux-gnu/preprocessor/gdlpp 1: Input TT file: /<>/test/GrcRegressionTest/fonts/SchInput.ttf 1: Output TT file: SchTest.ttf 1: Output font name: Scheherazade GrcRegTest (unchanged) 1: Silf table version requested: 4.0 1: 1: Parsing file /<>/test/GrcRegressionTest/fonts/SchMain.gdl... 1: Initial processing... 1: Checking for errors... 1: Compiling... 1: [Generating FSMs: table 0 pass 0 1 (mc 4 fsm 5 5) 2 (mc 4 fsm 45 19) 3 (mc 2 fsm 3 3) 4 (mc 13 fsm 120 57) 5 (mc 15 fsm 41 15) 6 (mc 8 fsm 46 36); table 1 pass 0 1 (mc 21 fsm 235 64) 2 (mc 9 fsm 52 16) 3 (mc 32 fsm 1623 368); ] 1: Debug files generated. 1: Debugger XML file generated. 1: Compilation successful! 1: 1 warning has been output to /<>/obj-s390x-linux-gnu/test/GrcRegressionTest/SchTest.gdlerr.txt (121 warnings ignored). 1/15 Test #1: compile_SchTest . Passed0.22 sec test 7 Start 7: compile_PigLatinTest_v2 7: Test command: /<>/obj-s390x-linux-gnu/compiler/grcompiler "-D" "-v2" "-p" "-e" "/<>/obj-s390x-linux-gnu/test/GrcRegressionTest/PigLatinTest_v2.gdlerr.txt" "/<>/test/GrcRegressionTest/fonts/PigLatinMain.gdl" "/<>/test/GrcRegressionTest/fonts/PigLatinInput.ttf" "PigLatinTest_v2.ttf" "PigLatin GrRegTest V2" 7: Working Directory: /<>/obj-s390x-linux-gnu/test/GrcRegressionTest 7: Environment variables: 7: GDLPP=/<>/obj-s390x-linux-gnu/preprocessor/gdlpp 7: LD_LIBRARY_PATH=$LD_LIBRARY_PATH:/usr/include/../lib 7: Test timeout computed to be: 1500 7: Frexx C Preprocessor v1.5 Copyright (C) by FrexxWare 1993 - 1997. 7: Revised by SIL International for Graphite Description Language, Aug 23 2022 4: Frexx C Preprocessor v1.5 Copyright (C) by FrexxWare 1993 - 1997. 4: Revised by SIL International for Graphite Description Language, Aug 23 2022 4: Graphite Compiler Version 5.2.1 [release build] 4: Copyright (c) 2002-2021, by SIL International. All rights reserved. 4: Reading input font... 4: 4: GDL file: /<>/test/GrcRegressionTest/fonts/CharisMain.gdl 4: PreProcessor: /<>/obj-s390x-linux-gnu/preprocessor/gdlpp 4: Input TT file: /<>/test/GrcRegressionTest/fonts/CharisInput.ttf 4: Output TT file: CharisTest.ttf 4: Output font name: Charis GrcRegTest (unchanged) 4: Silf table version requested: 2.0 4: 4: Parsing file /<>/test/GrcRegressionTest/fonts/CharisMain.gdl... 4: Initial processing... 4: Checking for errors... 4: Compiling... 4: [Generating FSMs: table 0 pass 0 1 (mc 138 fsm 3349
Bug#1022352: lua-mode: FTBFS: tests failed
FTBFS confirmed with elpa-buttercup/1.26-{1,2,3}, tests work just fine
using elpa-buttercup/1.24-1.
Bug#1022360: activemq: FTBFS: make: *** [debian/rules:4: binary] Error 25
Control: tags -1 confirmed pending Hello, I am preparing an upload with the newest upstream version, which suppresses this bug. Cheers, -- Pierre OpenPGP_signature Description: OpenPGP digital signature
Processed: Re: activemq: FTBFS: make: *** [debian/rules:4: binary] Error 25
Processing control commands: > tags -1 confirmed pending Bug #1022360 [src:activemq] activemq: FTBFS: make: *** [debian/rules:4: binary] Error 25 Added tag(s) pending and confirmed. -- 1022360: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1022360 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1022306: marked as done (oclgrind: FTBFS: runtime.cpp:5299:49: error: expected initializer before ‘CL_EXT_SUFFIX__VERSION_1_1’)
Your message dated Sun, 23 Oct 2022 22:05:18 +
with message-id
and subject line Bug#1022306: fixed in oclgrind 21.10-2
has caused the Debian Bug report #1022306,
regarding oclgrind: FTBFS: runtime.cpp:5299:49: error: expected initializer
before ‘CL_EXT_SUFFIX__VERSION_1_1’
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)
--
1022306: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1022306
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: oclgrind
Version: 21.10-1
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20221023 ftbfs-bookworm
Hi,
During a rebuild of all packages in sid, your package failed to build
on amd64.
Relevant part (hopefully):
> /usr/bin/c++ -Doclgrind_rt_EXPORTS -I/usr/lib/llvm-13/include -I/include
> -I/<>/src -I/<>/obj-x86_64-linux-gnu -g -O2
> -ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat
> -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -fno-rtti -Wall
> -Wno-strict-aliasing -fPIC -D_GNU_SOURCE -D__STDC_CONSTANT_MACROS
> -D__STDC_FORMAT_MACROS -D__STDC_LIMIT_MACROS -std=gnu++14 -MD -MT
> CMakeFiles/oclgrind-rt.dir/src/runtime/runtime.cpp.o -MF
> CMakeFiles/oclgrind-rt.dir/src/runtime/runtime.cpp.o.d -o
> CMakeFiles/oclgrind-rt.dir/src/runtime/runtime.cpp.o -c
> /<>/src/runtime/runtime.cpp
> In file included from /<>/src/runtime/icd.h:133,
> from /<>/src/runtime/async_queue.h:9,
> from /<>/src/runtime/runtime.cpp:17:
> /usr/include/CL/cl_gl_ext.h:18:112: note: ‘#pragma message: All
> OpenGL-related extensions have been moved into cl_gl.h. Please include
> cl_gl.h directly.’
>18 | #pragma message("All OpenGL-related extensions have been moved into
> cl_gl.h. Please include cl_gl.h directly.")
> |
> ^
> In file included from /<>/src/runtime/icd.h:133,
> from /<>/src/runtime/async_queue.h:9,
> from /<>/src/runtime/async_queue.cpp:9:
> /usr/include/CL/cl_gl_ext.h:18:112: note: ‘#pragma message: All
> OpenGL-related extensions have been moved into cl_gl.h. Please include
> cl_gl.h directly.’
>18 | #pragma message("All OpenGL-related extensions have been moved into
> cl_gl.h. Please include cl_gl.h directly.")
> |
> ^
> In file included from /<>/src/runtime/icd.h:133,
> from /<>/src/runtime/async_queue.h:9,
> from /<>/src/runtime/async_queue.cpp:9:
> /usr/include/CL/cl_gl_ext.h:18:112: note: ‘#pragma message: All
> OpenGL-related extensions have been moved into cl_gl.h. Please include
> cl_gl.h directly.’
>18 | #pragma message("All OpenGL-related extensions have been moved into
> cl_gl.h. Please include cl_gl.h directly.")
> |
> ^
> In file included from /<>/src/runtime/icd.h:133,
> from /<>/src/runtime/async_queue.h:9,
> from /<>/src/runtime/runtime.cpp:17:
> /usr/include/CL/cl_gl_ext.h:18:112: note: ‘#pragma message: All
> OpenGL-related extensions have been moved into cl_gl.h. Please include
> cl_gl.h directly.’
>18 | #pragma message("All OpenGL-related extensions have been moved into
> cl_gl.h. Please include cl_gl.h directly.")
> |
> ^
> /<>/src/runtime/runtime.cpp: In function ‘cl_int
> _clEnqueueNDRangeKernel(cl_command_queue, cl_kernel, cl_uint, const size_t*,
> const size_t*, const size_t*, cl_uint, _cl_event* const*, _cl_event**)’:
> /<>/src/runtime/runtime.cpp:5001:9: warning: ‘void*
> memcpy(void*, const void*, size_t)’ copying an object of non-trivial type
> ‘struct oclgrind::Size3’ from an array of ‘const size_t’ {aka ‘const long
> unsigned int’} [-Wclass-memaccess]
> 5001 | memcpy(>globalSize, global_work_size, work_dim *
> sizeof(size_t));
> |
> ~~^~
Processed (with 1 error): reassign 1022551 to llvm-15-dev, forcibly merging 1021117 1022551
Processing commands for cont...@bugs.debian.org:
> reassign 1022551 llvm-15-dev
Bug #1022551 [src:llvm-toolchain-15] llvm-15's cmake now requires
clang-tools-15, clang-tidy-15, clangd-15, even if unused
Bug reassigned from package 'src:llvm-toolchain-15' to 'llvm-15-dev'.
No longer marked as found in versions llvm-toolchain-15/15.0.3-1.
Ignoring request to alter fixed versions of bug #1022551 to the same values
previously set
> forcemerge 1021117 1022551
Bug #1021117 {Done: Adrian Bunk } [llvm-15-dev] llvm-15-dev:
cmake fails on missing /usr/lib/llvm-15/bin/mlir-tblgen
Bug #1021117 {Done: Adrian Bunk } [llvm-15-dev] llvm-15-dev:
cmake fails on missing /usr/lib/llvm-15/bin/mlir-tblgen
Added tag(s) bookworm and sid.
Bug #1022551 [llvm-15-dev] llvm-15's cmake now requires clang-tools-15,
clang-tidy-15, clangd-15, even if unused
Severity set to 'serious' from 'important'
Marked Bug as done
Added indication that 1022551 affects
src:spirv-llvm-translator-15,src:opencl-clang-15
Marked as fixed in versions llvm-toolchain-15/1:15.0.2-2~exp4.
Marked as found in versions llvm-toolchain-15/1:15.0.1-1~exp2.
Added tag(s) ftbfs.
Bug #1022551 {Done: Adrian Bunk } [llvm-15-dev] llvm-15's
cmake now requires clang-tools-15, clang-tidy-15, clangd-15, even if unused
Ignoring request to alter fixed versions of bug #1022551 to the same values
previously set
Unable to complete merge on previous attempt; trying again (retry: 2)
Bug #1022551 {Done: Adrian Bunk } [llvm-15-dev] llvm-15's
cmake now requires clang-tools-15, clang-tidy-15, clangd-15, even if unused
Ignoring request to alter fixed versions of bug #1022551 to the same values
previously set
Unable to complete merge on previous attempt; trying again (retry: 3)
Bug #1022551 {Done: Adrian Bunk } [llvm-15-dev] llvm-15's
cmake now requires clang-tools-15, clang-tidy-15, clangd-15, even if unused
Ignoring request to alter fixed versions of bug #1022551 to the same values
previously set
After four attempts, the following changes were unable to be made:
fixed_versions of #1022551 is 'llvm-toolchain-15/1:15.0.2-2~exp4' not
'1:15.0.2-2~exp4'
Failed to forcibly merge 1021117: Unable to modify bugs so they could be merged.
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
1021117: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1021117
1022551: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1022551
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Bug#1022004: marked as done (pyasn1 please drop pypy-pyasn1 to support python2.7 removal)
Your message dated Sun, 23 Oct 2022 20:49:02 + with message-id and subject line Bug#1022004: fixed in pyasn1 0.4.8-2.1 has caused the Debian Bug report #1022004, regarding pyasn1 please drop pypy-pyasn1 to support python2.7 removal to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 1022004: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1022004 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: pyasn1 Version: 0.4.8-2 Severity: serious Justification: rt Dear maintainers, If I didn't make a mistake, pyasn1 is keeping pypy in the key package set because it (Build-)Depends on it. Again, if I didn't make a mistake, there are no reverse Build-Depends or Depends anymore of pypy-pyasn1, so I think the package can just be dropped. That would be another step in the python2.7 removal transition. I'll be preparing an NMU that does this after I submit this bug. When done with preparation, I'll upload to DELAYED/5 and update this bug report with the debdiff. Please let me know if you prefer to handle this by yourself and/or if I should cancel or delay the upload. Paul OpenPGP_signature Description: OpenPGP digital signature --- End Message --- --- Begin Message --- Source: pyasn1 Source-Version: 0.4.8-2.1 Done: Paul Gevers We believe that the bug you reported is fixed in the latest version of pyasn1, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 1022...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Paul Gevers (supplier of updated pyasn1 package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Tue, 18 Oct 2022 21:27:43 +0200 Source: pyasn1 Architecture: source Version: 0.4.8-2.1 Distribution: unstable Urgency: medium Maintainer: Jan Lübbe Changed-By: Paul Gevers Closes: 1022004 Changes: pyasn1 (0.4.8-2.1) unstable; urgency=medium . * Non-maintainer upload . [ Debian Janitor ] * Remove constraints unnecessary since buster: + python3-pyasn1: Drop versioned constraint on python3-pysnmp4 in Breaks. + python-pyasn1-doc: Drop versioned constraint on python-pyasn1 in Replaces. + python-pyasn1-doc: Drop versioned constraint on python-pyasn1 in Breaks. . [ Paul Gevers ] * Stop building pypy-pyasn1 (Closes: 1022004) Checksums-Sha1: 6716882af74b6760545287be612a1b28690737b6 1986 pyasn1_0.4.8-2.1.dsc 5a1e502e482d69b5e6e537345c234f61c9ff353b 5540 pyasn1_0.4.8-2.1.debian.tar.xz Checksums-Sha256: e4bc88c3117d86099e0d92be27bbd0d99273d2cf26ea24e301788388ba9d94ae 1986 pyasn1_0.4.8-2.1.dsc 7cd0aab84e14c683bd922092e7ea41548e4e29404b7d56c5289ff48f1266049a 5540 pyasn1_0.4.8-2.1.debian.tar.xz Files: 459decc75a43a3abcc7b08b3838320b4 1986 python optional pyasn1_0.4.8-2.1.dsc 278b45b0eeed6362ae5560a8023a527e 5540 python optional pyasn1_0.4.8-2.1.debian.tar.xz -BEGIN PGP SIGNATURE- iQEzBAEBCAAdFiEEWLZtSHNr6TsFLeZynFyZ6wW9dQoFAmNPARYACgkQnFyZ6wW9 dQotewgAw+zjN5BHjI4xPgVjiNzyei9ovk0PT2B/TRZ4uz1oo6ro0jlHIrwjGcpf vfCVRYkdt4sFnYfx6WmtQq0aBru+0E5AQe4VKj2ZSNsrHklO7YkJt5mQOzv4fT9l gx6tZrNontXCZJ2CsC4n1eLwoTw4PfU3iz9+HvUG8gVSPPwde4G4T4LaQDE1hAyO IiBJkHdqXHJRcwwjDCxsekAqrtvuvZG5sS7LeDAYr/BtVDHSOWBl9Lh4zfikq6k8 wQ2J7rEp4Msp3qdsYSDgd1m3ICGBKNsV6T3wZiGmskY0q7D0bJP/qujc7RAyuiT8 002SbD7VxeY069SuFQF3NGRsqwgbbA== =+zWz -END PGP SIGNATURE End Message ---
Bug#1022388: marked as done (jacoco: FTBFS: make: *** [debian/rules:4: build] Error 25)
Your message dated Sun, 23 Oct 2022 20:44:46 + with message-id and subject line Bug#1022388: fixed in jacoco 0.8.6-2 has caused the Debian Bug report #1022388, regarding jacoco: FTBFS: make: *** [debian/rules:4: build] Error 25 to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 1022388: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1022388 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: jacoco Version: 0.8.6-1 Severity: serious Justification: FTBFS Tags: bookworm sid ftbfs User: lu...@debian.org Usertags: ftbfs-20221023 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 javahelper >dh_update_autotools_config >dh_autoreconf >dh_auto_configure > mh_patchpoms -plibjacoco-java --debian-build --keep-pom-version > --maven-repo=/<>/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=/<> > -Dclassworlds.conf=/etc/maven/m2-debian.conf > -Dproperties.file.manual=/<>/debian/maven.properties > org.codehaus.plexus.classworlds.launcher.Launcher > -s/etc/maven/settings-debian.xml -Ddebian.dir=/<>/debian > -Dmaven.repo.local=/<>/debian/maven-repo --batch-mode package > -DskipTests -Dnotimestamp=true -Dlocale=en_US > [0m[0m[INFO] Scanning for projects... > [INFO] > > [INFO] Reactor Build Order: > [INFO] > [INFO] JaCoCo > [pom] > [INFO] JaCoCo :: Core > [jar] > [INFO] JaCoCo :: Report > [jar] > [INFO] JaCoCo :: Agent RT > [jar] > [INFO] JaCoCo :: Agent > [jar] > [INFO] JaCoCo :: Ant > [jar] > [INFO] root > [pom] > [INFO] > [INFO] < org.jacoco:org.jacoco.build > >- > [INFO] Building JaCoCo 0.8.6 > [1/7] > [INFO] [ pom > ]- > [INFO] > [INFO] --- maven-antrun-plugin:1.8:run (check-license-header) @ > org.jacoco.build --- > [INFO] Executing tasks > > main: > [INFO] Executed tasks > [INFO] > [INFO] --- build-helper-maven-plugin:3.3.0:parse-version (parse-version) @ > org.jacoco.build --- > [INFO] > [INFO] -< org.jacoco:org.jacoco.core > >- > [INFO] Building JaCoCo :: Core 0.8.6 > [2/7] > [INFO] [ jar > ]- > [INFO] > [INFO] --- maven-antrun-plugin:1.8:run (check-license-header) @ > org.jacoco.core --- > [INFO] Executing tasks > > main: > [INFO] Executed tasks > [INFO] > [INFO] --- build-helper-maven-plugin:3.3.0:parse-version (parse-version) @ > org.jacoco.core --- > [INFO] > [INFO] --- maven-resources-plugin:3.1.0:resources (default-resources) @ > org.jacoco.core --- > [INFO] Using 'UTF-8' encoding to copy filtered resources. > [INFO] Copying 0 resource > [INFO] Copying 1 resource > [INFO] Copying 0 resource > [INFO] Copying 1 resource > [INFO] > [INFO] --- maven-compiler-plugin:3.8.1:compile (default-compile) @ > org.jacoco.core --- > [INFO] Changes detected - recompiling the module! > [INFO] Compiling 123 source files to > /<>/org.jacoco.core/target/classes > Use of target 6 is no longer supported, switching to 7 > Use of source 6 is no longer supported, switching to 7 > [INFO] > [INFO] --- maven-bundle-plugin:3.5.1:manifest (default) @ org.jacoco.core --- > [INFO] > [INFO] --- maven-resources-plugin:3.1.0:testResources (default-testResources) > @ org.jacoco.core --- > [INFO] Using 'UTF-8' encoding to copy filtered resources. > [INFO] skip non existing resourceDirectory > /
Bug#1022279: marked as done (libbdplus: FTBFS: configure: error: gpg-error not found on system)
Your message dated Sun, 23 Oct 2022 20:45:04 + with message-id and subject line Bug#1022279: fixed in libbdplus 0.2.0-2 has caused the Debian Bug report #1022279, regarding libbdplus: FTBFS: configure: error: gpg-error not found on system to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 1022279: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1022279 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: libbdplus Version: 0.2.0-1 Severity: serious Justification: FTBFS Tags: bookworm sid ftbfs User: lu...@debian.org Usertags: ftbfs-20221023 ftbfs-bookworm Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > checking for libgcrypt-config... /usr/bin/libgcrypt-config > checking for gcc options needed to detect all undeclared functions... none > needed > checking whether strerror_r is declared... yes > checking whether strerror_r returns char *... no > checking for gpg-error-config... no > configure: error: gpg-error not found on system > tail -v -n \+0 config.log The full build log is available from: http://qa-logs.debian.net/2022/10/23/libbdplus_0.2.0-1_unstable.log All bugs filed during this archive rebuild are listed at: https://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=ftbfs-20221023;users=lu...@debian.org or: https://udd.debian.org/bugs/?release=na=ign=7=7=only=ftbfs-20221023=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 marking it as 'affects'-ing this package. See https://www.debian.org/Bugs/server-control#affects If you fail to reproduce this, please provide a build log and diff it with mine so that we can identify if something relevant changed in the meantime. --- End Message --- --- Begin Message --- Source: libbdplus Source-Version: 0.2.0-2 Done: Nilesh Patra We believe that the bug you reported is fixed in the latest version of libbdplus, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 1022...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Nilesh Patra (supplier of updated libbdplus package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Mon, 24 Oct 2022 01:38:56 +0530 Source: libbdplus Architecture: source Version: 0.2.0-2 Distribution: unstable Urgency: medium Maintainer: Debian Multimedia Maintainers Changed-By: Nilesh Patra Closes: 1022279 Changes: libbdplus (0.2.0-2) unstable; urgency=medium . * Team Upload. * d/p/update-gpg-error-call.patch: gpgerror lib has stopped vendoring a gpg-error-config binary, and hence instead detect gpg-error via a PKG_CHECK_MODULES call and choke if it is not found (Closes: #1022279) * Bump Standards-Version to 4.6.1 (no changes needed) Checksums-Sha1: 04b1cb949a7e11eefba63e6420e40760723d7283 2104 libbdplus_0.2.0-2.dsc 3231d3544c28f42b3d49a002c8bbe9f1d2b8c992 3588 libbdplus_0.2.0-2.debian.tar.xz ef32808059e5949fc30c12075b66dbed59b4021a 6438 libbdplus_0.2.0-2_amd64.buildinfo Checksums-Sha256: 094bea7b82a8424d04569933854f7ba1aa3ef930d29514951a3a15e99f11 2104 libbdplus_0.2.0-2.dsc 1863a2f040e766ef401e4fe24fc9af6d70f8cac09d4ed16d409158274ffbdece 3588 libbdplus_0.2.0-2.debian.tar.xz 5ae34fda362f8172d5c6a0bb1d95a55423168b4e1b6a74adf0b0b42fe15173a8 6438 libbdplus_0.2.0-2_amd64.buildinfo Files: 80fc53f15cf851ba73ecd72057ed2ed4 2104 libs optional libbdplus_0.2.0-2.dsc cf122bc115b1ddd541dceb7a61e469c8 3588 libs optional libbdplus_0.2.0-2.debian.tar.xz c75918abd7d1f1ff074b2df79c329bc9 6438 libs optional libbdplus_0.2.0-2_amd64.buildinfo -BEGIN PGP SIGNATURE- iQJGBAEBCgAwFiEEPpmlJvXcwMu/HO6mALrnSzQzafEFAmNVoZMSHG5pbGVzaEBk ZWJpYW4ub3JnAAoJEAC650s0M2nx3QIQALa14ueta+zGYabGmQgQkzVcdv2afV8D K8fk7FBjdJnJY93XQgzBldAOfM2Y0oGEX5zvvpDaLGVx9VjKlMMtdCF1tqhskxrv iUlYMS3b0dlUc+YrKt9Qj1CPvHlVsaTy7jrXrB0nyLpgEZUZXK0UjORWl/D4/op8 psL1GOagBPEKpPKjEkqVJ7TLjBMiJFY2nL/DOcWuD1aIeNV+jbY9a0LOzljkP6Ig EUHma06k8PLz6+xEwmolQsJ8vkEs0Olsjk+/+FHK
Bug#1022253: swi-prolog breaks logol autopkgtest on s390x
Le dim. 23 oct. 2022, 19:21, Lev Lamberov a écrit : > Hi Paul, > > Вс 23 окт 2022 @ 10:10 Paul Gevers : > > > Hi Lev, > > > > On 23-10-2022 09:40, Lev Lamberov wrote: > >> I'm not sure it is the solution, it needs testing. The change in > >> swi-prolog concerns pre-compiled prolog source code, when there is no > >> pre-complied prolog code rebuilt is not needed. SWI-Prolog supports > >> three different kinds of pre-compilation, at least one of them was > >> affected and another was not. The mentioned endiannes bug can be found > >> in BTS, #1006818 [bts]. > > > > I just ran the autopkgtest with a rebuild logol on s390x, see below. > > Does that help? > > > > @logol maintainers, those ERRORs look scary if the test passes with it. > > Is that just noise, or are real problems ignored? > Errors are "permission denied" related. Default package config expects to write in different dirs (temp and results dir), owned by root. If logol is to be executed as non root, a different config file should be used, specifying user writable directories. > Given the answer from Étienne looks like it *is* the solution. Thanks > for your work on it! > > Cheers! > Lev > >
Bug#1022555: tiff: CVE-2022-3627 CVE-2022-3626 CVE-2022-3599 CVE-2022-3598 CVE-2022-3597 CVE-2022-3570
Source: tiff X-Debbugs-CC: t...@security.debian.org Severity: grave Tags: security Hi, The following vulnerabilities were published for tiff. CVE-2022-3627[0]: | LibTIFF 4.4.0 has an out-of-bounds write in _TIFFmemcpy in | libtiff/tif_unix.c:346 when called from extractImageSection, | tools/tiffcrop.c:6860, allowing attackers to cause a denial-of-service | via a crafted tiff file. For users that compile libtiff from sources, | the fix is available with commit 236b7191. https://gitlab.com/libtiff/libtiff/-/commit/236b7191f04c60d09ee836ae13b50f812c841047 https://gitlab.com/libtiff/libtiff/-/issues/411 CVE-2022-3626[1]: | LibTIFF 4.4.0 has an out-of-bounds write in _TIFFmemset in | libtiff/tif_unix.c:340 when called from processCropSelections, | tools/tiffcrop.c:7619, allowing attackers to cause a denial-of-service | via a crafted tiff file. For users that compile libtiff from sources, | the fix is available with commit 236b7191. https://gitlab.com/libtiff/libtiff/-/commit/236b7191f04c60d09ee836ae13b50f812c841047 https://gitlab.com/libtiff/libtiff/-/issues/426 CVE-2022-3599[2]: | LibTIFF 4.4.0 has an out-of-bounds read in writeSingleSection in | tools/tiffcrop.c:7345, allowing attackers to cause a denial-of-service | via a crafted tiff file. For users that compile libtiff from sources, | the fix is available with commit e8131125. https://gitlab.com/libtiff/libtiff/-/commit/e813112545942107551433d61afd16ac094ff246 https://gitlab.com/libtiff/libtiff/-/issues/398 CVE-2022-3598[3]: | LibTIFF 4.4.0 has an out-of-bounds write in | extractContigSamplesShifted24bits in tools/tiffcrop.c:3604, allowing | attackers to cause a denial-of-service via a crafted tiff file. For | users that compile libtiff from sources, the fix is available with | commit cfbb883b. https://gitlab.com/libtiff/libtiff/-/commit/cfbb883bf6ea7bedcb04177cc4e52d304522fdff https://gitlab.com/libtiff/libtiff/-/issues/435 CVE-2022-3597[4]: | LibTIFF 4.4.0 has an out-of-bounds write in _TIFFmemcpy in | libtiff/tif_unix.c:346 when called from extractImageSection, | tools/tiffcrop.c:6826, allowing attackers to cause a denial-of-service | via a crafted tiff file. For users that compile libtiff from sources, | the fix is available with commit 236b7191. https://gitlab.com/libtiff/libtiff/-/commit/236b7191f04c60d09ee836ae13b50f812c841047 https://gitlab.com/libtiff/libtiff/-/issues/413 CVE-2022-3570[5]: | Multiple heap buffer overflows in tiffcrop.c utility in libtiff | library Version 4.4.0 allows attacker to trigger unsafe or out of | bounds memory access via crafted TIFF image file which could result | into application crash, potential information disclosure or any other | context-dependent impact https://gitlab.com/libtiff/libtiff/-/commit/bd94a9b383d8755a27b5a1bc27660b8ad10b094c https://gitlab.com/libtiff/libtiff/-/issues/381 https://gitlab.com/libtiff/libtiff/-/issues/386 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-2022-3627 https://www.cve.org/CVERecord?id=CVE-2022-3627 [1] https://security-tracker.debian.org/tracker/CVE-2022-3626 https://www.cve.org/CVERecord?id=CVE-2022-3626 [2] https://security-tracker.debian.org/tracker/CVE-2022-3599 https://www.cve.org/CVERecord?id=CVE-2022-3599 [3] https://security-tracker.debian.org/tracker/CVE-2022-3598 https://www.cve.org/CVERecord?id=CVE-2022-3598 [4] https://security-tracker.debian.org/tracker/CVE-2022-3597 https://www.cve.org/CVERecord?id=CVE-2022-3597 [5] https://security-tracker.debian.org/tracker/CVE-2022-3570 https://www.cve.org/CVERecord?id=CVE-2022-3570 Please adjust the affected versions in the BTS as needed.
Bug#1022548: marked as done (lokalize: text window does not repaint)
Your message dated Sun, 23 Oct 2022 21:43:46 +0200 with message-id <2132104.Icojqenx9y@treadstone-71> and subject line has caused the Debian Bug report #1022548, regarding lokalize: text window does not repaint to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 1022548: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1022548 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: lokalize Version: 4:22.08.2-1~np1 Severity: grave Justification: renders package unusable X-Debbugs-Cc: l...@castermans.org Dear Maintainer, *** Reporter, please consider answering these questions, where appropriate *** lokalize open correctly, the window with translation memory shows correctly as well. Each file to translate opens correctly as well in a seperate window. However the text in that window is NOT SHOWN at all. With this the application is not usable. *** End of the template - remove these template lines *** -- System Information: Debian Release: bookworm/sid APT prefers testing APT policy: (990, 'testing'), (500, 'experimental'), (500, 'unstable') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 6.0.0-2-amd64 (SMP w/4 CPU threads; PREEMPT) Locale: LANG=nl_NL.UTF-8, LC_CTYPE=nl_NL.UTF-8 (charmap=UTF-8), LANGUAGE=nl Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages lokalize depends on: ii kio5.98.0-1 ii libc6 2.36-1 ii libhunspell-1.7-0 1.7.1-1 ii libkf5completion5 5.98.0-1 ii libkf5configcore5 5.98.0-1 ii libkf5configgui5 5.98.0-1 ii libkf5configwidgets5 5.98.0-1 ii libkf5coreaddons5 5.98.0-1 ii libkf5crash5 5.98.0-1 ii libkf5dbusaddons5 5.98.0-1 ii libkf5i18n55.98.0-1+b1 ii libkf5itemviews5 5.98.0-1 ii libkf5kiocore5 5.98.0-1 ii libkf5kiofilewidgets5 5.98.0-1 ii libkf5kiowidgets5 5.98.0-1 ii libkf5notifications5 5.98.0-1 ii libkf5sonnetcore5 5.98.0-1 ii libkf5sonnetui55.98.0-1 ii libkf5textwidgets5 5.98.0-1 ii libkf5widgetsaddons5 5.98.0-1 ii libkf5xmlgui5 5.98.0-1+b1 ii libqt5core5a 5.15.6+dfsg-2 ii libqt5dbus55.15.6+dfsg-2 ii libqt5gui5 5.15.6+dfsg-2 ii libqt5network5 5.15.6+dfsg-2 ii libqt5sql5 5.15.6+dfsg-2 ii libqt5sql5-sqlite 5.15.6+dfsg-2 ii libqt5widgets5 5.15.6+dfsg-2 ii libqt5xml5 5.15.6+dfsg-2 ii libstdc++6 12.2.0-7 Versions of packages lokalize recommends: ii gettext0.21-9 ii sonnet-plugins 5.98.0-1 ii translate-toolkit 3.7.3-2 Versions of packages lokalize suggests: ii khelpcenter 4:22.08.2-1~np1 ii poxml4:22.08.2-1~np1 -- no debconf information --- End Message --- --- Begin Message --- Hi Luc, the version you have installed is not in Debian, hence we do not know how it is built or what it is built against etc. Therefore I'm closing the issue. -- Med vänliga hälsningar Patrick Franz--- End Message ---
Bug#1021117: marked as done (llvm-15-dev: cmake fails on missing /usr/lib/llvm-15/bin/mlir-tblgen)
Your message dated Sun, 23 Oct 2022 22:24:39 +0300
with message-id
and subject line Fixed since 1:15.0.2-2~exp4
has caused the Debian Bug report #1021117,
regarding llvm-15-dev: cmake fails on missing /usr/lib/llvm-15/bin/mlir-tblgen
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)
--
1021117: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1021117
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: llvm-15-dev
Version: 1:15.0.1-1~exp2
Severity: serious
Hi,
while trying to package spirv-llvm-translator-15, I encountred the
following cmake error:
dh_auto_configure -- \
-DCMAKE_SKIP_RPATH=ON \
-DLLVM_EXTERNAL_SPIRV_HEADERS_SOURCE_DIR=/usr/include \
-DBUILD_SHARED_LIBS=ON \
-DLLVM_SPIRV_INCLUDE_TESTS=ON \
-DLLVM_EXTERNAL_LIT=/usr/lib/llvm-15/build/utils/lit/lit.py \
-Wno-dev
cd build && cmake -DCMAKE_INSTALL_PREFIX=/usr -DCMAKE_BUILD_TYPE=None
-DCMAKE_INSTALL_SYSCONFDIR=/etc -DCMAKE_INSTALL_LOCALSTATEDIR=/var
-DCMAKE_EXPORT_NO_PACKAGE_REGISTRY=ON -DCMAKE_FIND_USE_PACKAGE_REGISTRY=OFF
-DCMAKE_FIND_PACKAGE_NO_PACKAGE_REGISTRY=ON
-DFETCHCONTENT_FULLY_DISCONNECTED=ON -DCMAKE_INSTALL_RUNSTATEDIR=/run
-DCMAKE_SKIP_INSTALL_ALL_DEPENDENCY=ON "-GUnix Makefiles"
-DCMAKE_VERBOSE_MAKEFILE=ON -DCMAKE_INSTALL_LIBDIR=lib/x86_64-linux-gnu
-DCMAKE_SKIP_RPATH=ON -DLLVM_EXTERNAL_SPIRV_HEADERS_SOURCE_DIR=/usr/include
-DBUILD_SHARED_LIBS=ON -DLLVM_SPIRV_INCLUDE_TESTS=ON
-DLLVM_EXTERNAL_LIT=/usr/lib/llvm-15/build/utils/lit/lit.py -Wno-dev ..
-- Found PkgConfig: /usr/bin/pkg-config (found version "1.8.0")
-- Using SPIR-V Headers from
/usr/include
-- The CXX compiler identification is GNU 12.2.0
-- The C compiler identification is GNU 12.2.0
-- Detecting CXX compiler ABI info
-- Detecting CXX compiler ABI info - done
-- Check for working CXX compiler: /usr/bin/c++ - skipped
-- Detecting CXX compile features
-- Detecting CXX compile features - done
-- Detecting C compiler ABI info
-- Detecting C compiler ABI info - done
-- Check for working C compiler: /usr/bin/cc - skipped
-- Detecting C compile features
-- Detecting C compile features - done
-- Performing Test HAVE_FFI_CALL
-- Performing Test HAVE_FFI_CALL - Success
-- Found FFI: /usr/lib/x86_64-linux-gnu/libffi.so
-- Performing Test Terminfo_LINKABLE
-- Performing Test Terminfo_LINKABLE - Success
-- Found Terminfo: /usr/lib/x86_64-linux-gnu/libtinfo.so
-- Could NOT find ZLIB (missing: ZLIB_LIBRARY ZLIB_INCLUDE_DIR)
-- Found LibXml2: /usr/lib/x86_64-linux-gnu/libxml2.so (found version "2.9.14")
CMake Error at /usr/lib/llvm-15/lib/cmake/llvm/LLVMExports.cmake:1634 (message):
The imported target "mlir-tblgen" references the file
"/usr/lib/llvm-15/bin/mlir-tblgen"
but this file does not exist. Possible reasons include:
* The file was deleted, renamed, or moved to another location.
* An install or uninstall procedure did not complete successfully.
* The installation package was faulty and contained
"/usr/lib/llvm-15/lib/cmake/llvm/LLVMExports.cmake"
but not all the files it references.
Call Stack (most recent call first):
/usr/lib/llvm-15/cmake/LLVMConfig.cmake:329 (include)
CMakeLists.txt:82 (find_package)
-- Configuring incomplete, errors occurred!
The corresponding find_package() call is
...
if(NOT DEFINED BASE_LLVM_VERSION)
set (BASE_LLVM_VERSION 15.0.0)
endif(NOT DEFINED BASE_LLVM_VERSION)
...
if(LLVM_SPIRV_INCLUDE_TESTS)
set(LLVM_TEST_COMPONENTS
llvm-as
llvm-dis
)
endif(LLVM_SPIRV_INCLUDE_TESTS)
find_package(LLVM ${BASE_LLVM_VERSION} REQUIRED
COMPONENTS
Analysis
BitReader
BitWriter
CodeGen
Core
Passes
Support
TransformUtils
${LLVM_TEST_COMPONENTS}
)
...
This works fine with llvm-14 and spirv-llvm-translator-14.
If I work around this by adding a B-D: mlir-15-tools, the next problem is
CMake Error at /usr/lib/llvm-15/lib/cmake/llvm/LLVMExports.cmake:1634 (message):
The imported target "MLIRSupportIndentedOstream" references the file
"/usr/lib/llvm-15/lib/libMLIRSupportIndentedOstream.a"
but this file does not exist. Possible reasons include:
* The file was deleted, renamed, or moved to another location.
* An install or uninstall procedure did not complete successfully.
* The installation package was faulty and contained
"/usr/lib/llvm-15/lib/cmake/llvm/LLVMExports.cmake"
but not all the files it references.
Call Stack (most recent call first):
/usr/lib/llvm-15/cmake/LLVMConfig.cmake:329 (include)
Processed: Bug#1022388 marked as pending in jacoco
Processing control commands: > tag -1 pending Bug #1022388 [src:jacoco] jacoco: FTBFS: make: *** [debian/rules:4: build] Error 25 Added tag(s) pending. -- 1022388: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1022388 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1022388: marked as pending in jacoco
Control: tag -1 pending Hello, Bug #1022388 in jacoco reported by you has been fixed in the Git repository and is awaiting an upload. You can see the commit message below and you can check the diff of the fix at: https://salsa.debian.org/java-team/jacoco/-/commit/8bebb2cfb6235a3ac2539fdef9de611680314be9 Add patch to skip license check for interim pom (Closes: #1022388) (this message was generated automatically) -- Greetings https://bugs.debian.org/1022388
Bug#1022531: marked as done (soundgrain: FTBFS: error: Multiple top-level packages discovered in a flat-layout: ['debian', 'Resources'].)
Your message dated Sun, 23 Oct 2022 19:12:05 +
with message-id
and subject line Bug#1022531: fixed in soundgrain 6.0.1-3
has caused the Debian Bug report #1022531,
regarding soundgrain: FTBFS: error: Multiple top-level packages discovered in a
flat-layout: ['debian', 'Resources'].
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)
--
1022531: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1022531
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: soundgrain
Version: 6.0.1-2
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20221023 ftbfs-bookworm
Hi,
During a rebuild of all packages in sid, your package failed to build
on amd64.
Relevant part (hopefully):
> debian/rules build
> dh build --with python3 --buildsystem=pybuild
>dh_update_autotools_config -O--buildsystem=pybuild
>dh_autoreconf -O--buildsystem=pybuild
>dh_auto_configure -O--buildsystem=pybuild
> I: pybuild base:240: python3.10 setup.py config
> error: Multiple top-level packages discovered in a flat-layout: ['debian',
> 'Resources'].
>
> To avoid accidental inclusion of unwanted files or directories,
> setuptools will not proceed with this build.
>
> If you are trying to create a single distribution with multiple packages
> on purpose, you should not rely on automatic discovery.
> Instead, consider the following options:
>
> 1. set up custom discovery (`find` directive with `include` or `exclude`)
> 2. use a `src-layout`
> 3. explicitly set `py_modules` or `packages` with a list of names
>
> To find more information, look for "package discovery" on setuptools docs.
> E: pybuild pybuild:379: configure: plugin distutils failed with: exit code=1:
> python3.10 setup.py config
> dh_auto_configure: error: pybuild --configure -i python{version} -p 3.10
> returned exit code 13
> make: *** [debian/rules:4: build] Error 25
The full build log is available from:
http://qa-logs.debian.net/2022/10/23/soundgrain_6.0.1-2_unstable.log
All bugs filed during this archive rebuild are listed at:
https://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=ftbfs-20221023;users=lu...@debian.org
or:
https://udd.debian.org/bugs/?release=na=ign=7=7=only=ftbfs-20221023=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 marking it as 'affects'-ing
this package. See https://www.debian.org/Bugs/server-control#affects
If you fail to reproduce this, please provide a build log and diff it with mine
so that we can identify if something relevant changed in the meantime.
--- End Message ---
--- Begin Message ---
Source: soundgrain
Source-Version: 6.0.1-3
Done: Nilesh Patra
We believe that the bug you reported is fixed in the latest version of
soundgrain, which is due to be installed in the Debian FTP archive.
A summary of the changes between this version and the previous one is
attached.
Thank you for reporting the bug, which will now be closed. If you
have further comments please address them to 1022...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Nilesh Patra (supplier of updated soundgrain package)
(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Format: 1.8
Date: Sun, 23 Oct 2022 23:45:11 +0530
Source: soundgrain
Architecture: source
Version: 6.0.1-3
Distribution: unstable
Urgency: medium
Maintainer: Debian Multimedia Maintainers
Changed-By: Nilesh Patra
Closes: 1022531
Changes:
soundgrain (6.0.1-3) unstable; urgency=medium
.
[ Debian Janitor ]
* Team Upload.
* Remove constraints unnecessary since buster:
+ soundgrain: Drop versioned constraint on python3-pyo in Depends.
.
[ Nilesh Patra ]
* Add patch to fix FTBFS (Closes: #1022531)
* Bump Standards-Version to 4.6.1 (no changes needed)
* Bump debhelper compatibility level to 13
* wrap-and-sort properly
Checksums-Sha1:
cb8c8472348da01455176372663bae078d6f6893 2031 soundgrain_6.0.1-3.dsc
44996f6a1f63ac2d41c015bb5a0905e1e1d570dc 6220 soundgrain_6.0.1-3.debian.tar.xz
ea8845394343330fb1fba4b76d4abf5391b70963 6307
soundgrain_6.0.1-3_amd64.buildinfo
Bug#1022417: marked as done (node-js-tokens: FTBFS: ln: failed to create symbolic link 'build/.': File exists)
Your message dated Sun, 23 Oct 2022 19:10:28 +
with message-id
and subject line Bug#1022417: fixed in node-js-tokens 8.0.0-2
has caused the Debian Bug report #1022417,
regarding node-js-tokens: FTBFS: ln: failed to create symbolic link 'build/.':
File exists
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)
--
1022417: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1022417
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: node-js-tokens
Version: 8.0.0-1
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20221023 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 '/<>'
> node build.js
> make[1]: Leaving directory '/<>'
>dh_auto_test --buildsystem=nodejs
> mkdir -p node_modules
> ln -s ../debian/tests/test_modules/test262-parser-tests
> node_modules/test262-parser-tests
> ln -s ../build node_modules/js-tokens
> /bin/sh -ex debian/tests/pkg-js/test
> + ln -s . build
> ln: failed to create symbolic link 'build/.': File exists
> + true
> + jest --ci -u
> FAIL test/nesting.test.js
> ● Test suite failed to run
>
> Jest: Couldn't locate all inline snapshots.
>
> 225 | });
> 226 | if (remainingSnapshots.size) {
> > 227 | throw new Error("Jest: Couldn't locate all inline
> snapshots.");
> | ^
> 228 | }
> 229 | };
> 230 | const runPrettier = (prettier, sourceFilePath,
> sourceFileWithSnapshots, snapshotMatcherNames) => {
>
> at traverseAst
> (../../../usr/share/nodejs/jest-snapshot/build/InlineSnapshots.js:227:11)
>
> FAIL test/template.test.js
> ● Test suite failed to run
>
> Jest: Couldn't locate all inline snapshots.
>
> 225 | });
> 226 | if (remainingSnapshots.size) {
> > 227 | throw new Error("Jest: Couldn't locate all inline
> snapshots.");
> | ^
> 228 | }
> 229 | };
> 230 | const runPrettier = (prettier, sourceFilePath,
> sourceFileWithSnapshots, snapshotMatcherNames) => {
>
> at traverseAst
> (../../../usr/share/nodejs/jest-snapshot/build/InlineSnapshots.js:227:11)
>
> FAIL test/example.test.js
> ● Test suite failed to run
>
> Jest: Couldn't locate all inline snapshots.
>
> 225 | });
> 226 | if (remainingSnapshots.size) {
> > 227 | throw new Error("Jest: Couldn't locate all inline
> snapshots.");
> | ^
> 228 | }
> 229 | };
> 230 | const runPrettier = (prettier, sourceFilePath,
> sourceFileWithSnapshots, snapshotMatcherNames) => {
>
> at traverseAst
> (../../../usr/share/nodejs/jest-snapshot/build/InlineSnapshots.js:227:11)
>
> FAIL test/jsx.test.js
> ● Test suite failed to run
>
> Jest: Couldn't locate all inline snapshots.
>
> 225 | });
> 226 | if (remainingSnapshots.size) {
> > 227 | throw new Error("Jest: Couldn't locate all inline
> snapshots.");
> | ^
> 228 | }
> 229 | };
> 230 | const runPrettier = (prettier, sourceFilePath,
> sourceFileWithSnapshots, snapshotMatcherNames) => {
>
> at traverseAst
> (../../../usr/share/nodejs/jest-snapshot/build/InlineSnapshots.js:227:11)
>
> PASS test/fixtures.test.js (5.723 s)
> PASS test/index.test.js (6.496 s)
> PASS test/expression-vs-operator.test.js (10.362 s)
>
> Test Suites: 4 failed, 3 passed, 7 total
> Tests: 25507 passed, 25507 total
> Snapshots: 0 total
> Time: 11.799 s
> Ran all test suites.
> dh_auto_test: error: /bin/sh -ex debian/tests/pkg-js/test returned exit code 1
The full build log is available from:
http://qa-logs.debian.net/2022/10/23/node-js-tokens_8.0.0-1_unstable.log
All bugs filed during this archive rebuild are listed at:
https://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=ftbfs-20221023;users=lu...@debian.org
or:
https://udd.debian.org/bugs/?release=na=ign=7=7=only=ftbfs-20221023=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.debia
Bug#1022401: marked as done (node-global-modules: FTBFS: dh_auto_test: error: /bin/sh -ex debian/tests/pkg-js/test returned exit code 1)
Your message dated Sun, 23 Oct 2022 19:10:06 + with message-id and subject line Bug#1022401: fixed in node-global-modules 2.0.0-3 has caused the Debian Bug report #1022401, regarding node-global-modules: FTBFS: dh_auto_test: error: /bin/sh -ex debian/tests/pkg-js/test returned exit code 1 to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 1022401: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1022401 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: node-global-modules Version: 2.0.0-2 Severity: serious Justification: FTBFS Tags: bookworm sid ftbfs User: lu...@debian.org Usertags: ftbfs-20221023 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 >dh_auto_configure --buildsystem=nodejs >dh_auto_build --buildsystem=nodejs > No build command found, searching known files >dh_auto_test --buildsystem=nodejs > mkdir -p node_modules > ln -s ../. node_modules/global-modules > /bin/sh -ex debian/tests/pkg-js/test > + mocha > > > global-modules > 1) should resolve the path to the global npm modules directory: > > > 0 passing (20ms) > 1 failing > > 1) global-modules >should resolve the path to the global npm modules directory:: > > AssertionError [ERR_ASSERTION]: The expression evaluated to a falsy > value: > > assert(fs.existsSync(gm)) > > + expected - actual > > -false > +true > > at Context. (test.js:17:5) > at callFn (/usr/share/nodejs/mocha/lib/runnable.js:366:21) > at Runnable.run (/usr/share/nodejs/mocha/lib/runnable.js:354:5) > at Runner.runTest (/usr/share/nodejs/mocha/lib/runner.js:666:10) > at /usr/share/nodejs/mocha/lib/runner.js:789:12 > at next (/usr/share/nodejs/mocha/lib/runner.js:581:14) > at /usr/share/nodejs/mocha/lib/runner.js:591:7 > at next (/usr/share/nodejs/mocha/lib/runner.js:474:14) > at Immediate._onImmediate (/usr/share/nodejs/mocha/lib/runner.js:559:5) > at process.processImmediate (node:internal/timers:471:21) > > > > dh_auto_test: error: /bin/sh -ex debian/tests/pkg-js/test returned exit code 1 The full build log is available from: http://qa-logs.debian.net/2022/10/23/node-global-modules_2.0.0-2_unstable.log All bugs filed during this archive rebuild are listed at: https://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=ftbfs-20221023;users=lu...@debian.org or: https://udd.debian.org/bugs/?release=na=ign=7=7=only=ftbfs-20221023=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 marking it as 'affects'-ing this package. See https://www.debian.org/Bugs/server-control#affects If you fail to reproduce this, please provide a build log and diff it with mine so that we can identify if something relevant changed in the meantime. --- End Message --- --- Begin Message --- Source: node-global-modules Source-Version: 2.0.0-3 Done: Yadd We believe that the bug you reported is fixed in the latest version of node-global-modules, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 1022...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Yadd (supplier of updated node-global-modules package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Sun, 23 Oct 2022 19:48:50 +0200 Source: node-global-modules Architecture: source Version: 2.0.0-3 Distribution: unstable Urgency: medium Maintainer: Debian Javascript Maintainers Changed-By: Yadd Closes: 1022401 Changes: node-global-modules (2.0.0-3) unstable; urgency=medium . * Team upload * Update standards version to 4.6.1, no changes needed. * Drop test: useless and rot relevant (Closes: #1022401
Processed: owner 1022388
Processing commands for cont...@bugs.debian.org: > owner 1022388 ! Bug #1022388 [src:jacoco] jacoco: FTBFS: make: *** [debian/rules:4: build] Error 25 Owner recorded as tony mancill . > thanks Stopping processing here. Please contact me if you need assistance. -- 1022388: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1022388 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1022422: marked as done (spirv-llvm-translator-14: FTBFS: make[1]: *** [debian/rules:13: override_dh_auto_configure] Error 2)
Your message dated Sun, 23 Oct 2022 21:05:53 +0200 with message-id <43076a4a-5912-56e9-72e1-70deaa2d3...@debian.org> and subject line Re: [Pkg-opencl-devel] Bug#1022422: spirv-llvm-translator-14: FTBFS: make[1]: *** [debian/rules:13: override_dh_auto_configure] Error 2 has caused the Debian Bug report #1022422, regarding spirv-llvm-translator-14: FTBFS: make[1]: *** [debian/rules:13: override_dh_auto_configure] Error 2 to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 1022422: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1022422 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: spirv-llvm-translator-14 Version: 14.0.0-3 Severity: serious Justification: FTBFS Tags: bookworm sid ftbfs User: lu...@debian.org Usertags: ftbfs-20221023 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_configure -- \ > -DCMAKE_SKIP_RPATH=ON \ > -DLLVM_EXTERNAL_SPIRV_HEADERS_SOURCE_DIR=/usr/include \ > -DBUILD_SHARED_LIBS=ON \ > -DLLVM_SPIRV_INCLUDE_TESTS=ON \ > -DLLVM_EXTERNAL_LIT=/usr/lib/llvm-14/build/utils/lit/lit.py \ > -Wno-dev > cd build && cmake -DCMAKE_INSTALL_PREFIX=/usr -DCMAKE_BUILD_TYPE=None > -DCMAKE_INSTALL_SYSCONFDIR=/etc -DCMAKE_INSTALL_LOCALSTATEDIR=/var > -DCMAKE_EXPORT_NO_PACKAGE_REGISTRY=ON -DCMAKE_FIND_USE_PACKAGE_REGISTRY=OFF > -DCMAKE_FIND_PACKAGE_NO_PACKAGE_REGISTRY=ON > -DFETCHCONTENT_FULLY_DISCONNECTED=ON -DCMAKE_INSTALL_RUNSTATEDIR=/run > -DCMAKE_SKIP_INSTALL_ALL_DEPENDENCY=ON "-GUnix Makefiles" > -DCMAKE_VERBOSE_MAKEFILE=ON -DCMAKE_INSTALL_LIBDIR=lib/x86_64-linux-gnu > -DCMAKE_SKIP_RPATH=ON -DLLVM_EXTERNAL_SPIRV_HEADERS_SOURCE_DIR=/usr/include > -DBUILD_SHARED_LIBS=ON -DLLVM_SPIRV_INCLUDE_TESTS=ON > -DLLVM_EXTERNAL_LIT=/usr/lib/llvm-14/build/utils/lit/lit.py -Wno-dev .. > -- Found PkgConfig: /usr/bin/pkg-config (found version "1.8.0") > -- Using SPIR-V Headers from > /usr/include > -- The CXX compiler identification is GNU 12.2.0 > -- The C compiler identification is GNU 12.2.0 > -- Detecting CXX compiler ABI info > -- Detecting CXX compiler ABI info - done > -- Check for working CXX compiler: /usr/bin/c++ - skipped > -- Detecting CXX compile features > -- Detecting CXX compile features - done > -- Detecting C compiler ABI info > -- Detecting C compiler ABI info - done > -- Check for working C compiler: /usr/bin/cc - skipped > -- Detecting C compile features > -- Detecting C compile features - done > -- Performing Test HAVE_FFI_CALL > -- Performing Test HAVE_FFI_CALL - Success > -- Found FFI: /usr/lib/x86_64-linux-gnu/libffi.so > -- Performing Test Terminfo_LINKABLE > -- Performing Test Terminfo_LINKABLE - Success > -- Found Terminfo: /usr/lib/x86_64-linux-gnu/libtinfo.so > -- Could NOT find ZLIB (missing: ZLIB_LIBRARY ZLIB_INCLUDE_DIR) > -- Found LibXml2: /usr/lib/x86_64-linux-gnu/libxml2.so (found version > "2.9.14") > CMake Error at /usr/lib/llvm-14/lib/cmake/llvm/LLVMExports.cmake:1598 > (message): > The imported target "sancov" references the file > > "/usr/lib/llvm-14/bin/sancov" > > but this file does not exist. Possible reasons include: > > * The file was deleted, renamed, or moved to another location. > > * An install or uninstall procedure did not complete successfully. > > * The installation package was faulty and contained > > "/usr/lib/llvm-14/lib/cmake/llvm/LLVMExports.cmake" > > but not all the files it references. > > Call Stack (most recent call first): > /usr/lib/llvm-14/cmake/LLVMConfig.cmake:323 (include) > CMakeLists.txt:82 (find_package) > > > -- Configuring incomplete, errors occurred! > See also "/<>/build/CMakeFiles/CMakeOutput.log". > cd build && tail -v -n \+0 CMakeCache.txt > ==> CMakeCache.txt <== > # This is the CMakeCache file. > # For build in directory: /<>/build > # It was generated by CMake: /usr/bin/cmake > # You can edit this file to change values found and used by cmake. > # If you do not want to change any of the values, simply exit the editor. > # If you do want to change a value, simply edit, save, and exit the editor. > # The syntax fo
Bug#1022370: marked as done (intel-vc-intrinsics: FTBFS: make[1]: *** [debian/rules:11: override_dh_auto_configure] Error 2)
Your message dated Sun, 23 Oct 2022 21:05:58 +0200 with message-id and subject line Re: [Pkg-opencl-devel] Bug#1022370: intel-vc-intrinsics: FTBFS: make[1]: *** [debian/rules:11: override_dh_auto_configure] Error 2 has caused the Debian Bug report #1022370, regarding intel-vc-intrinsics: FTBFS: make[1]: *** [debian/rules:11: override_dh_auto_configure] Error 2 to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 1022370: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1022370 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: intel-vc-intrinsics Version: 0.7.1-1 Severity: serious Justification: FTBFS Tags: bookworm sid ftbfs User: lu...@debian.org Usertags: ftbfs-20221023 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_configure -- \ > -DCMAKE_INSTALL_INCLUDEDIR=/usr/include/llvm-14/ \ > -DLLVM_DIR=/usr/lib/llvm-14/lib/cmake/llvm > cd obj-x86_64-linux-gnu && cmake -DCMAKE_INSTALL_PREFIX=/usr > -DCMAKE_BUILD_TYPE=None -DCMAKE_INSTALL_SYSCONFDIR=/etc > -DCMAKE_INSTALL_LOCALSTATEDIR=/var -DCMAKE_EXPORT_NO_PACKAGE_REGISTRY=ON > -DCMAKE_FIND_USE_PACKAGE_REGISTRY=OFF > -DCMAKE_FIND_PACKAGE_NO_PACKAGE_REGISTRY=ON > -DFETCHCONTENT_FULLY_DISCONNECTED=ON -DCMAKE_INSTALL_RUNSTATEDIR=/run > -DCMAKE_SKIP_INSTALL_ALL_DEPENDENCY=ON "-GUnix Makefiles" > -DCMAKE_VERBOSE_MAKEFILE=ON -DCMAKE_INSTALL_LIBDIR=lib/x86_64-linux-gnu > -DCMAKE_INSTALL_INCLUDEDIR=/usr/include/llvm-14/ > -DLLVM_DIR=/usr/lib/llvm-14/lib/cmake/llvm .. > -- 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/bin/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/bin/c++ - skipped > -- Detecting CXX compile features > -- Detecting CXX compile features - done > -- Performing Test HAVE_FFI_CALL > -- Performing Test HAVE_FFI_CALL - Success > -- Found FFI: /usr/lib/x86_64-linux-gnu/libffi.so > -- Performing Test Terminfo_LINKABLE > -- Performing Test Terminfo_LINKABLE - Success > -- Found Terminfo: /usr/lib/x86_64-linux-gnu/libtinfo.so > -- Found ZLIB: /usr/lib/x86_64-linux-gnu/libz.so (found version "1.2.11") > -- Found LibXml2: /usr/lib/x86_64-linux-gnu/libxml2.so (found version > "2.9.14") > CMake Error at /usr/lib/llvm-14/lib/cmake/llvm/LLVMExports.cmake:1598 > (message): > The imported target "sancov" references the file > > "/usr/lib/llvm-14/bin/sancov" > > but this file does not exist. Possible reasons include: > > * The file was deleted, renamed, or moved to another location. > > * An install or uninstall procedure did not complete successfully. > > * The installation package was faulty and contained > > "/usr/lib/llvm-14/lib/cmake/llvm/LLVMExports.cmake" > > but not all the files it references. > > Call Stack (most recent call first): > /usr/lib/llvm-14/lib/cmake/llvm/LLVMConfig.cmake:323 (include) > CMakeLists.txt:31 (find_package) > > > -- Configuring incomplete, errors occurred! > See also "/<>/obj-x86_64-linux-gnu/CMakeFiles/CMakeOutput.log". > cd obj-x86_64-linux-gnu && tail -v -n \+0 CMakeCache.txt > ==> CMakeCache.txt <== > # This is the CMakeCache file. > # For build in directory: /<>/obj-x86_64-linux-gnu > # It was generated by CMake: /usr/bin/cmake > # You can edit this file to change values found and used by cmake. > # If you do not want to change any of the values, simply exit the editor. > # If you do want to change a value, simply edit, save, and exit the editor. > # The syntax for the file is as follows: > # KEY:TYPE=VALUE > # KEY is the name of a variable in the cache. > # TYPE is a hint to GUIs for the type of VALUE, DO NOT EDIT TYPE!. > # VALUE is the current value for the KEY. > > > # EXTERNAL cache entries > > > //Path to a program. > CMAKE_ADDR2LINE:FILEPATH=/usr/bin/addr2line > >
Bug#1022380: marked as done (opencl-clang-14: FTBFS: make[1]: *** [debian/rules:14: override_dh_auto_configure] Error 2)
Your message dated Sun, 23 Oct 2022 21:04:50 +0200 with message-id <63cf551e-6797-3cc7-3b7a-06a51d0ec...@debian.org> and subject line Re: [Pkg-opencl-devel] Bug#1022380: opencl-clang-14: FTBFS: make[1]: *** [debian/rules:14: override_dh_auto_configure] Error 2 has caused the Debian Bug report #1022380, regarding opencl-clang-14: FTBFS: make[1]: *** [debian/rules:14: override_dh_auto_configure] Error 2 to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 1022380: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1022380 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: opencl-clang-14 Version: 14.0.0-3 Severity: serious Justification: FTBFS Tags: bookworm sid ftbfs User: lu...@debian.org Usertags: ftbfs-20221023 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_configure -- \ > -DLLVMSPIRV_INCLUDED_IN_LLVM=OFF \ > -DSPIRV_TRANSLATOR_DIR=/usr/lib \ > -DCOMMON_CLANG_LIBRARY_NAME=opencl-clang \ > -DCMAKE_SKIP_RPATH=true \ > -DPREFERRED_LLVM_VERSION=14.0.6 \ > -Wno-dev > cd build && cmake -DCMAKE_INSTALL_PREFIX=/usr -DCMAKE_BUILD_TYPE=None > -DCMAKE_INSTALL_SYSCONFDIR=/etc -DCMAKE_INSTALL_LOCALSTATEDIR=/var > -DCMAKE_EXPORT_NO_PACKAGE_REGISTRY=ON -DCMAKE_FIND_USE_PACKAGE_REGISTRY=OFF > -DCMAKE_FIND_PACKAGE_NO_PACKAGE_REGISTRY=ON > -DFETCHCONTENT_FULLY_DISCONNECTED=ON -DCMAKE_INSTALL_RUNSTATEDIR=/run > -DCMAKE_SKIP_INSTALL_ALL_DEPENDENCY=ON "-GUnix Makefiles" > -DCMAKE_VERBOSE_MAKEFILE=ON -DCMAKE_INSTALL_LIBDIR=lib/x86_64-linux-gnu > -DLLVMSPIRV_INCLUDED_IN_LLVM=OFF -DSPIRV_TRANSLATOR_DIR=/usr/lib > -DCOMMON_CLANG_LIBRARY_NAME=opencl-clang -DCMAKE_SKIP_RPATH=true > -DPREFERRED_LLVM_VERSION=14.0.6 -Wno-dev .. > -- 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/bin/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/bin/c++ - skipped > -- Detecting CXX compile features > -- Detecting CXX compile features - done > -- [OPENCL-CLANG] Looking for LLVM version 14.0.6 > -- Performing Test HAVE_FFI_CALL > -- Performing Test HAVE_FFI_CALL - Success > -- Found FFI: /usr/lib/x86_64-linux-gnu/libffi.so > -- Performing Test Terminfo_LINKABLE > -- Performing Test Terminfo_LINKABLE - Success > -- Found Terminfo: /usr/lib/x86_64-linux-gnu/libtinfo.so > -- Could NOT find ZLIB (missing: ZLIB_LIBRARY ZLIB_INCLUDE_DIR) > -- Found LibXml2: /usr/lib/x86_64-linux-gnu/libxml2.so (found version > "2.9.14") > CMake Error at /usr/lib/llvm-14/lib/cmake/llvm/LLVMExports.cmake:1598 > (message): > The imported target "sancov" references the file > > "/usr/lib/llvm-14/bin/sancov" > > but this file does not exist. Possible reasons include: > > * The file was deleted, renamed, or moved to another location. > > * An install or uninstall procedure did not complete successfully. > > * The installation package was faulty and contained > > "/usr/lib/llvm-14/lib/cmake/llvm/LLVMExports.cmake" > > but not all the files it references. > > Call Stack (most recent call first): > /usr/lib/llvm-14/cmake/LLVMConfig.cmake:323 (include) > CMakeLists.txt:26 (find_package) > > > -- Configuring incomplete, errors occurred! > See also "/<>/build/CMakeFiles/CMakeOutput.log". > cd build && tail -v -n \+0 CMakeCache.txt > ==> CMakeCache.txt <== > # This is the CMakeCache file. > # For build in directory: /<>/build > # It was generated by CMake: /usr/bin/cmake > # You can edit this file to change values found and used by cmake. > # If you do not want to change any of the values, simply exit the editor. > # If you do want to change a value, simply edit, save, and exit the editor. > # The syntax for the file is as follows: > # KEY:TYPE=VALUE > # KEY is the name of a variable in the cache. > # TYPE is a hint to GUIs for the type of VALUE, DO NOT EDIT TYPE!. > # VALUE is
Bug#1021817: marked as done (firebird3.0: undistributable source files)
Your message dated Sun, 23 Oct 2022 19:06:08 + with message-id and subject line Bug#1021817: fixed in firebird3.0 3.0.11.33637.ds4-1 has caused the Debian Bug report #1021817, regarding firebird3.0: undistributable source files to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 1021817: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1021817 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: firebird3.0 Version: 3.0.1.32609.ds4-14 Severity: serious Tags: upstream Justification: Policy 2.1 (DFSG) Forwarded: https://github.com/FirebirdSQL/firebird/issues/7349 Four files in src/intl/ contain contradictory statements from Unicode Inc, claiming that the file cannot be redistributed, and from Inprise Corporation, claiming it is licensed under the Interbase Public License (which allows redistribution; it is an MPL-like license). src/intl/charsets/cs_big5.h src/intl/charsets/cs_jis_0208_1990.h src/intl/charsets/cs_next.h src/intl/charsets/cs_sjis.h Hopefully this can be resolved upstream. Otherwise the four files above would need to be excluded from the sources used by the Debian package and therefore lose support for the corresponding national character sets. -- Damyan --- End Message --- --- Begin Message --- Source: firebird3.0 Source-Version: 3.0.11.33637.ds4-1 Done: Damyan Ivanov We believe that the bug you reported is fixed in the latest version of firebird3.0, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 1021...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Damyan Ivanov (supplier of updated firebird3.0 package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Sun, 23 Oct 2022 18:48:29 + Source: firebird3.0 Architecture: source Version: 3.0.11.33637.ds4-1 Distribution: unstable Urgency: medium Maintainer: Damyan Ivanov Changed-By: Damyan Ivanov Closes: 1021817 Changes: firebird3.0 (3.0.11.33637.ds4-1) unstable; urgency=medium . * add gbp.conf for DEP-14 git repository layout * switch debian/watch to releases published on firebirdsql.org the ones on github aren't always accessible (JavaScript) * pack-upstream-snapshot: use mk-origtargz for cleaning upstream sources single source of truth about what needs to be removed * add files to source repackaging exclusion list to match official releases when using git snapshots * New upstream snapshot 3.0.11.33637.ds4 Closes: #1021817 -- undistributable source files * drop two files from d/copyright that are not present in the source * adapt lintian overrides to version 2.115.3 * bump Standards-Version from 4.6.0 to 4.6.1 (no changes needed) * review debian/copyright, move files under right licensing stanza, update copyright years, drop additional files with missing/unclear licenses when repackaging Checksums-Sha1: cdb2da3ced69b502dca7c97a88c24f7d3bf12d34 2761 firebird3.0_3.0.11.33637.ds4-1.dsc 7984a888961123814f280ff119b5afef134420d1 3365564 firebird3.0_3.0.11.33637.ds4.orig.tar.xz e9501e39128b78f1f11b9c45b6c01147fffa6769 101560 firebird3.0_3.0.11.33637.ds4-1.debian.tar.xz Checksums-Sha256: 33a522ba1c6038dd5189295cc4a0e1869d6100699b112540a1d18258ba96ece5 2761 firebird3.0_3.0.11.33637.ds4-1.dsc efbd621b553acf3ebf7c314c9f02c2a8427989510ce34c9406122fcc967f5f1a 3365564 firebird3.0_3.0.11.33637.ds4.orig.tar.xz fdef2c5fa3bf0da28e6b5705be7ac847fe7fe9bf128bd8df4e8081ce3e35d8fb 101560 firebird3.0_3.0.11.33637.ds4-1.debian.tar.xz Files: abf7de2d83628c0f783ea8e8bec7f9d4 2761 database optional firebird3.0_3.0.11.33637.ds4-1.dsc de5cfc3c07ffecca3632eb9a2258a04a 3365564 database optional firebird3.0_3.0.11.33637.ds4.orig.tar.xz ceb7c833ae67ebd932737e9a2f9a955a 101560 database optional firebird3.0_3.0.11.33637.ds4-1.debian.tar.xz -BEGIN PGP SIGNATURE- iQIzBAEBCAAdFiEErqDETssFbpNjDZ0z276dTZnSoAQFAmNVjmoACgkQ276dTZnS oATwBQ/+NRoUp/VcJViXmxi9HAhIb5r+etQo2N6Acc1dtoYXr+Tdzds29fD2uqlI /KqB5uvOb2a8sVlAPoxA/ipnBy8FZzMyDK09kJOusZC7V4hJ2V6qn5bvABMAA0g2 qMLBOPVMv6Yi56QJ4LURO+cLidwn6dE5ODdSHlpFg7yE39lakAEex0STRprWO1y7
Processed: your mail
Processing commands for cont...@bugs.debian.org: > tags 1022300 pending Bug #1022300 [src:kleopatra] kleopatra: FTBFS: refreshcertificatecommand.cpp:22:10: fatal error: QGpgME/RefreshOpenPGPKeysJob: No such file or directory Added tag(s) pending. > End of message, stopping processing here. Please contact me if you need assistance. -- 1022300: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1022300 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1014966: onionshare: CVE-2021-41867 CVE-2021-41868 CVE-2022-21688 CVE-2022-21689 CVE-2022-21690 CVE-2022-21691 CVE-2022-21692 CVE-2022-21693 CVE-2022-21694 CVE-2022-21695 CVE-2022-21696
Hi Clément, On Sun, Oct 23, 2022 at 06:27:08PM +0200, Clément Hermann wrote: > Hi, > > Le 22/10/2022 à 15:01, Salvatore Bonaccorso a écrit : > > > Thanks for the quick reply! (much appreciated). I think it would be > > good to get a confirmation from upstream and if possible to have > > those advisories updates. E.g. > > https://github.com/onionshare/onionshare/security/advisories/GHSA-x7wr-283h-5h2v > > while mentioning "affected versions < 2.4" the patched version remains > > "none". this might be that the < 2.4 just reflects the point in time > > when the advisory was filled. OTOH you have arguments with the v2.5 > > release information that they might all be fixed. > > > > To be on safe side, explicitly confirming by upstream would be great. > > Agreed. And asked upstream: > https://github.com/onionshare/onionshare/issues/1633. Thank you! Regards, Salvatore
Bug#1022409: marked as done (ccls: FTBFS: make[1]: *** [debian/rules:18: override_dh_auto_configure] Error 2)
Your message dated Sun, 23 Oct 2022 18:37:16 + with message-id and subject line Bug#1022414: fixed in llvm-toolchain-14 1:14.0.6-6 has caused the Debian Bug report #1022414, regarding ccls: FTBFS: make[1]: *** [debian/rules:18: override_dh_auto_configure] Error 2 to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 1022414: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1022414 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: ccls Version: 0.20220729-1 Severity: serious Justification: FTBFS Tags: bookworm sid ftbfs User: lu...@debian.org Usertags: ftbfs-20221023 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_configure -- -DCCLS_VERSION=0.20220729-1 > -DCLANG_RESOURCE_DIR=/usr/include/clang/14 > cd obj-x86_64-linux-gnu && cmake -DCMAKE_INSTALL_PREFIX=/usr > -DCMAKE_BUILD_TYPE=None -DCMAKE_INSTALL_SYSCONFDIR=/etc > -DCMAKE_INSTALL_LOCALSTATEDIR=/var -DCMAKE_EXPORT_NO_PACKAGE_REGISTRY=ON > -DCMAKE_FIND_USE_PACKAGE_REGISTRY=OFF > -DCMAKE_FIND_PACKAGE_NO_PACKAGE_REGISTRY=ON > -DFETCHCONTENT_FULLY_DISCONNECTED=ON -DCMAKE_INSTALL_RUNSTATEDIR=/run > -DCMAKE_SKIP_INSTALL_ALL_DEPENDENCY=ON "-GUnix Makefiles" > -DCMAKE_VERBOSE_MAKEFILE=ON -DCMAKE_INSTALL_LIBDIR=lib/x86_64-linux-gnu > -DCCLS_VERSION=0.20220729-1 -DCLANG_RESOURCE_DIR=/usr/include/clang/14 .. > -- The CXX compiler identification is GNU 12.2.0 > -- The C compiler identification is GNU 12.2.0 > -- Detecting CXX compiler ABI info > -- Detecting CXX compiler ABI info - done > -- Check for working CXX compiler: /usr/bin/c++ - skipped > -- Detecting CXX compile features > -- Detecting CXX compile features - done > -- Detecting C compiler ABI info > -- Detecting C compiler ABI info - done > -- Check for working C compiler: /usr/bin/cc - skipped > -- Detecting C compile features > -- Detecting C compile features - done > -- Performing Test HAVE_FFI_CALL > -- Performing Test HAVE_FFI_CALL - Success > -- Found FFI: /usr/lib/x86_64-linux-gnu/libffi.so > -- Performing Test Terminfo_LINKABLE > -- Performing Test Terminfo_LINKABLE - Success > -- Found Terminfo: /usr/lib/x86_64-linux-gnu/libtinfo.so > -- Could NOT find ZLIB (missing: ZLIB_LIBRARY ZLIB_INCLUDE_DIR) > -- Found LibXml2: /usr/lib/x86_64-linux-gnu/libxml2.so (found version > "2.9.14") > CMake Error at /usr/lib/llvm-14/lib/cmake/llvm/LLVMExports.cmake:1598 > (message): > The imported target "sancov" references the file > > "/usr/lib/llvm-14/bin/sancov" > > but this file does not exist. Possible reasons include: > > * The file was deleted, renamed, or moved to another location. > > * An install or uninstall procedure did not complete successfully. > > * The installation package was faulty and contained > > "/usr/lib/llvm-14/lib/cmake/llvm/LLVMExports.cmake" > > but not all the files it references. > > Call Stack (most recent call first): > /usr/lib/llvm-14/lib/cmake/llvm/LLVMConfig.cmake:323 (include) > /usr/lib/cmake/clang-14/ClangConfig.cmake:10 (find_package) > CMakeLists.txt:72 (find_package) > > > -- Configuring incomplete, errors occurred! > See also "/<>/obj-x86_64-linux-gnu/CMakeFiles/CMakeOutput.log". > cd obj-x86_64-linux-gnu && tail -v -n \+0 CMakeCache.txt > ==> CMakeCache.txt <== > # This is the CMakeCache file. > # For build in directory: /<>/obj-x86_64-linux-gnu > # It was generated by CMake: /usr/bin/cmake > # You can edit this file to change values found and used by cmake. > # If you do not want to change any of the values, simply exit the editor. > # If you do want to change a value, simply edit, save, and exit the editor. > # The syntax for the file is as follows: > # KEY:TYPE=VALUE > # KEY is the name of a variable in the cache. > # TYPE is a hint to GUIs for the type of VALUE, DO NOT EDIT TYPE!. > # VALUE is the current value for the KEY. > > > # EXTERNAL cache entries > > > //No help, variable specified on the command line. > CCLS_VERSION:UNINITIALIZED=0.20220729-1 > > //No help, variable specified on the command line. > CLANG_RESOURCE_DIR:UNINITIALIZED=/usr/include/
Bug#1022337: marked as done (qt6-tools: FTBFS: The imported target "sancov" references the file "/usr/lib/llvm-14/bin/sancov" but this file does not exist.)
Your message dated Sun, 23 Oct 2022 18:37:16 + with message-id and subject line Bug#1022414: fixed in llvm-toolchain-14 1:14.0.6-6 has caused the Debian Bug report #1022414, regarding qt6-tools: FTBFS: The imported target "sancov" references the file "/usr/lib/llvm-14/bin/sancov" but this file does not exist. to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 1022414: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1022414 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: qt6-tools Version: 6.3.1-2 Severity: serious Justification: FTBFS Tags: bookworm sid ftbfs User: lu...@debian.org Usertags: ftbfs-20221023 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_configure -- \ > -DCMAKE_LIBRARY_PATH=x86_64-linux-gnu \ > -DCMAKE_SKIP_INSTALL_RPATH=ON > cd obj-x86_64-linux-gnu && cmake -DCMAKE_INSTALL_PREFIX=/usr > -DCMAKE_BUILD_TYPE=None -DCMAKE_INSTALL_SYSCONFDIR=/etc > -DCMAKE_INSTALL_LOCALSTATEDIR=/var -DCMAKE_EXPORT_NO_PACKAGE_REGISTRY=ON > -DCMAKE_FIND_USE_PACKAGE_REGISTRY=OFF > -DCMAKE_FIND_PACKAGE_NO_PACKAGE_REGISTRY=ON > -DFETCHCONTENT_FULLY_DISCONNECTED=ON -DCMAKE_INSTALL_RUNSTATEDIR=/run > -DCMAKE_SKIP_INSTALL_ALL_DEPENDENCY=ON -GNinja -DCMAKE_VERBOSE_MAKEFILE=ON > -DCMAKE_INSTALL_LIBDIR=lib/x86_64-linux-gnu > -DCMAKE_LIBRARY_PATH=x86_64-linux-gnu -DCMAKE_SKIP_INSTALL_RPATH=ON .. > -- The CXX compiler identification is GNU 12.2.0 > -- The C compiler identification is GNU 12.2.0 > -- Detecting CXX compiler ABI info > -- Detecting CXX compiler ABI info - done > -- Check for working CXX compiler: /usr/bin/c++ - skipped > -- Detecting CXX compile features > -- Detecting CXX compile features - done > -- Detecting C compiler ABI info > -- Detecting C compiler ABI info - done > -- Check for working C compiler: /usr/bin/cc - skipped > -- Detecting C compile features > -- Detecting C compile features - done > -- Performing Test CMAKE_HAVE_LIBC_PTHREAD > -- Performing Test CMAKE_HAVE_LIBC_PTHREAD - Success > -- Found Threads: TRUE > -- Performing Test HAVE_STDATOMIC > -- Performing Test HAVE_STDATOMIC - Success > -- Found WrapAtomic: TRUE > -- Found OpenGL: /usr/lib/x86_64-linux-gnu/libOpenGL.so > CMake Error at /usr/lib/llvm-14/lib/cmake/llvm/LLVMExports.cmake:1598 > (message): > The imported target "sancov" references the file > > "/usr/lib/llvm-14/bin/sancov" > > but this file does not exist. Possible reasons include: > > * The file was deleted, renamed, or moved to another location. > > * An install or uninstall procedure did not complete successfully. > > * The installation package was faulty and contained > > "/usr/lib/llvm-14/lib/cmake/llvm/LLVMExports.cmake" > > but not all the files it references. > > Call Stack (most recent call first): > /usr/lib/llvm-14/cmake/LLVMConfig.cmake:323 (include) > /usr/lib/llvm-14/lib/cmake/clang/ClangConfig.cmake:10 (find_package) > cmake/FindWrapLibClang.cmake:14 (find_package) > /usr/lib/x86_64-linux-gnu/cmake/Qt6/QtFindPackageHelpers.cmake:130 > (find_package) > configure.cmake:17 (qt_find_package) > /usr/lib/x86_64-linux-gnu/cmake/Qt6/QtFeature.cmake:573 (include) > src/CMakeLists.txt:21 (qt_feature_evaluate_features) > > > -- Configuring incomplete, errors occurred! > See also "/<>/obj-x86_64-linux-gnu/CMakeFiles/CMakeOutput.log". > cd obj-x86_64-linux-gnu && tail -v -n \+0 CMakeCache.txt > ==> CMakeCache.txt <== > # This is the CMakeCache file. > # For build in directory: /<>/obj-x86_64-linux-gnu > # It was generated by CMake: /usr/bin/cmake > # You can edit this file to change values found and used by cmake. > # If you do not want to change any of the values, simply exit the editor. > # If you do want to change a value, simply edit, save, and exit the editor. > # The syntax for the file is as follows: > # KEY:TYPE=VALUE > # KEY is the name of a variable in the cache. > # TYPE is a hint to GUIs for the type of VALUE, DO NOT EDIT TYPE!. > # VALUE is the current value for the KEY. > > > # EXTERNAL cache entries > > > //Build Q
Bug#1022414: marked as done (bpftrace: FTBFS: make[1]: *** [debian/rules:7: override_dh_auto_configure] Error 2)
Your message dated Sun, 23 Oct 2022 18:37:16 + with message-id and subject line Bug#1022414: fixed in llvm-toolchain-14 1:14.0.6-6 has caused the Debian Bug report #1022414, regarding bpftrace: FTBFS: make[1]: *** [debian/rules:7: override_dh_auto_configure] Error 2 to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 1022414: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1022414 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: bpftrace Version: 0.16.0-1 Severity: serious Justification: FTBFS Tags: bookworm sid ftbfs User: lu...@debian.org Usertags: ftbfs-20221023 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_configure -- -DBUILD_TESTING:BOOL=OFF > cd obj-x86_64-linux-gnu && cmake -DCMAKE_INSTALL_PREFIX=/usr > -DCMAKE_BUILD_TYPE=None -DCMAKE_INSTALL_SYSCONFDIR=/etc > -DCMAKE_INSTALL_LOCALSTATEDIR=/var -DCMAKE_EXPORT_NO_PACKAGE_REGISTRY=ON > -DCMAKE_FIND_USE_PACKAGE_REGISTRY=OFF > -DCMAKE_FIND_PACKAGE_NO_PACKAGE_REGISTRY=ON > -DFETCHCONTENT_FULLY_DISCONNECTED=ON -DCMAKE_INSTALL_RUNSTATEDIR=/run "-GUnix > Makefiles" -DCMAKE_VERBOSE_MAKEFILE=ON > -DCMAKE_INSTALL_LIBDIR=lib/x86_64-linux-gnu -DBUILD_TESTING:BOOL=OFF .. > -- 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/bin/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/bin/c++ - skipped > -- Detecting CXX compile features > -- Detecting CXX compile features - done > -- Found LibBcc: /usr/lib/x86_64-linux-gnu/libbcc.so > -- Performing Test LIBBCC_ATTACH_KPROBE_SIX_ARGS_SIGNATURE > -- Performing Test LIBBCC_ATTACH_KPROBE_SIX_ARGS_SIGNATURE - Success > -- Performing Test LIBBCC_ATTACH_UPROBE_SEVEN_ARGS_SIGNATURE > -- Performing Test LIBBCC_ATTACH_UPROBE_SEVEN_ARGS_SIGNATURE - Success > -- Looking for bcc_usdt_foreach > -- Looking for bcc_usdt_foreach - found > -- Found LibBpf: /usr/lib/x86_64-linux-gnu/libbpf.so > -- Looking for btf_dump__new > -- Looking for btf_dump__new - found > -- Looking for btf_dump__emit_type_decl > -- Looking for btf_dump__emit_type_decl - found > -- Looking for bpf_prog_load > -- Looking for bpf_prog_load - found > -- Looking for bpf_map_create > -- Looking for bpf_map_create - found > -- Looking for bpf_map_lookup_batch > -- Looking for bpf_map_lookup_batch - found > -- Looking for bpf_link_create > -- Looking for bpf_link_create - found > -- Looking for bpf_prog_test_run_opts > -- Looking for bpf_prog_test_run_opts - found > -- Performing Test HAVE_LIBBPF_BTF_TYPE_CNT > -- Performing Test HAVE_LIBBPF_BTF_TYPE_CNT - Success > -- Performing Test HAVE_LIBBPF_BTF_DUMP_NEW_V0_6_0 > -- Performing Test HAVE_LIBBPF_BTF_DUMP_NEW_V0_6_0 - Success > -- Performing Test HAVE_LIBBPF_BTF_DUMP_NEW_DEPRECATED > -- Performing Test HAVE_LIBBPF_BTF_DUMP_NEW_DEPRECATED - Success > -- Performing Test HAVE_LIBBPF_KPROBE_MULTI > -- Performing Test HAVE_LIBBPF_KPROBE_MULTI - Success > -- Found LibElf: /usr/lib/x86_64-linux-gnu/libelf.so > -- Found LibCereal: /usr/include > -- Found BISON: /usr/bin/bison (found version "3.8.2") > -- Found FLEX: /usr/bin/flex (found version "2.6.4") > -- Looking for name_to_handle_at > -- Looking for name_to_handle_at - found > -- Please install the libbfd development package (missing: LIBBFD_LIBRARIES > LIBBFD_INCLUDE_DIRS) > -- Please install the libopcodes development package (missing: > LIBOPCODES_LIBRARIES LIBOPCODES_INCLUDE_DIRS) > -- Found LibDw: /usr/lib/x86_64-linux-gnu/libdw.so > -- Please install the libcap development package (missing: LIBPCAP_LIBRARIES > LIBPCAP_INCLUDE_DIRS) > -- Looking for bcc_elf_foreach_sym > -- Looking for bcc_elf_foreach_sym - found > -- Looking for bpf_attach_kfunc > -- Looking for bpf_attach_kfunc - found > -- Looking for bcc_usdt_addsem_probe > -- Looking for bcc_usdt_addsem_probe - found > -- Looking for bcc_procutils_which_so > -- Looking for bcc_procutils_which_so - found > -- Looking for sys/sdt.h > -- Lo
Bug#1022414: marked as done (bpftrace: FTBFS: make[1]: *** [debian/rules:7: override_dh_auto_configure] Error 2)
Your message dated Sun, 23 Oct 2022 18:37:16 + with message-id and subject line Bug#1021857: fixed in llvm-toolchain-14 1:14.0.6-6 has caused the Debian Bug report #1021857, regarding bpftrace: FTBFS: make[1]: *** [debian/rules:7: override_dh_auto_configure] Error 2 to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 1021857: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1021857 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: bpftrace Version: 0.16.0-1 Severity: serious Justification: FTBFS Tags: bookworm sid ftbfs User: lu...@debian.org Usertags: ftbfs-20221023 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_configure -- -DBUILD_TESTING:BOOL=OFF > cd obj-x86_64-linux-gnu && cmake -DCMAKE_INSTALL_PREFIX=/usr > -DCMAKE_BUILD_TYPE=None -DCMAKE_INSTALL_SYSCONFDIR=/etc > -DCMAKE_INSTALL_LOCALSTATEDIR=/var -DCMAKE_EXPORT_NO_PACKAGE_REGISTRY=ON > -DCMAKE_FIND_USE_PACKAGE_REGISTRY=OFF > -DCMAKE_FIND_PACKAGE_NO_PACKAGE_REGISTRY=ON > -DFETCHCONTENT_FULLY_DISCONNECTED=ON -DCMAKE_INSTALL_RUNSTATEDIR=/run "-GUnix > Makefiles" -DCMAKE_VERBOSE_MAKEFILE=ON > -DCMAKE_INSTALL_LIBDIR=lib/x86_64-linux-gnu -DBUILD_TESTING:BOOL=OFF .. > -- 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/bin/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/bin/c++ - skipped > -- Detecting CXX compile features > -- Detecting CXX compile features - done > -- Found LibBcc: /usr/lib/x86_64-linux-gnu/libbcc.so > -- Performing Test LIBBCC_ATTACH_KPROBE_SIX_ARGS_SIGNATURE > -- Performing Test LIBBCC_ATTACH_KPROBE_SIX_ARGS_SIGNATURE - Success > -- Performing Test LIBBCC_ATTACH_UPROBE_SEVEN_ARGS_SIGNATURE > -- Performing Test LIBBCC_ATTACH_UPROBE_SEVEN_ARGS_SIGNATURE - Success > -- Looking for bcc_usdt_foreach > -- Looking for bcc_usdt_foreach - found > -- Found LibBpf: /usr/lib/x86_64-linux-gnu/libbpf.so > -- Looking for btf_dump__new > -- Looking for btf_dump__new - found > -- Looking for btf_dump__emit_type_decl > -- Looking for btf_dump__emit_type_decl - found > -- Looking for bpf_prog_load > -- Looking for bpf_prog_load - found > -- Looking for bpf_map_create > -- Looking for bpf_map_create - found > -- Looking for bpf_map_lookup_batch > -- Looking for bpf_map_lookup_batch - found > -- Looking for bpf_link_create > -- Looking for bpf_link_create - found > -- Looking for bpf_prog_test_run_opts > -- Looking for bpf_prog_test_run_opts - found > -- Performing Test HAVE_LIBBPF_BTF_TYPE_CNT > -- Performing Test HAVE_LIBBPF_BTF_TYPE_CNT - Success > -- Performing Test HAVE_LIBBPF_BTF_DUMP_NEW_V0_6_0 > -- Performing Test HAVE_LIBBPF_BTF_DUMP_NEW_V0_6_0 - Success > -- Performing Test HAVE_LIBBPF_BTF_DUMP_NEW_DEPRECATED > -- Performing Test HAVE_LIBBPF_BTF_DUMP_NEW_DEPRECATED - Success > -- Performing Test HAVE_LIBBPF_KPROBE_MULTI > -- Performing Test HAVE_LIBBPF_KPROBE_MULTI - Success > -- Found LibElf: /usr/lib/x86_64-linux-gnu/libelf.so > -- Found LibCereal: /usr/include > -- Found BISON: /usr/bin/bison (found version "3.8.2") > -- Found FLEX: /usr/bin/flex (found version "2.6.4") > -- Looking for name_to_handle_at > -- Looking for name_to_handle_at - found > -- Please install the libbfd development package (missing: LIBBFD_LIBRARIES > LIBBFD_INCLUDE_DIRS) > -- Please install the libopcodes development package (missing: > LIBOPCODES_LIBRARIES LIBOPCODES_INCLUDE_DIRS) > -- Found LibDw: /usr/lib/x86_64-linux-gnu/libdw.so > -- Please install the libcap development package (missing: LIBPCAP_LIBRARIES > LIBPCAP_INCLUDE_DIRS) > -- Looking for bcc_elf_foreach_sym > -- Looking for bcc_elf_foreach_sym - found > -- Looking for bpf_attach_kfunc > -- Looking for bpf_attach_kfunc - found > -- Looking for bcc_usdt_addsem_probe > -- Looking for bcc_usdt_addsem_probe - found > -- Looking for bcc_procutils_which_so > -- Looking for bcc_procutils_which_so - found > -- Looking for sys/sdt.h > -- Lo
Bug#1021857: marked as done (llvm-14-dev: CMake Error in LLVMExports.cmake: The imported target "sancov" references the file "/usr/lib/llvm-14/bin/sancov" but this file does not exist.)
Your message dated Sun, 23 Oct 2022 18:37:16 + with message-id and subject line Bug#1022414: fixed in llvm-toolchain-14 1:14.0.6-6 has caused the Debian Bug report #1022414, regarding llvm-14-dev: CMake Error in LLVMExports.cmake: The imported target "sancov" references the file "/usr/lib/llvm-14/bin/sancov" but this file does not exist. to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 1022414: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1022414 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: llvm-14-dev Version: 1:14.0.6-5 Severity: serious This is an autopkgtest regression, but also experienced e.g. while building spirv-llvm-translator-14: -- 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/bin/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/bin/c++ - skipped -- Detecting CXX compile features -- Detecting CXX compile features - done -- Performing Test HAVE_FFI_CALL -- Performing Test HAVE_FFI_CALL - Success -- Found FFI: /usr/lib/x86_64-linux-gnu/libffi.so -- Performing Test Terminfo_LINKABLE -- Performing Test Terminfo_LINKABLE - Success -- Found Terminfo: /usr/lib/x86_64-linux-gnu/libtinfo.so -- Could NOT find ZLIB (missing: ZLIB_LIBRARY ZLIB_INCLUDE_DIR) -- Found LibXml2: /usr/lib/x86_64-linux-gnu/libxml2.so (found version "2.9.14") CMake Error at /usr/lib/llvm-14/lib/cmake/llvm/LLVMExports.cmake:1598 (message): The imported target "sancov" references the file "/usr/lib/llvm-14/bin/sancov" but this file does not exist. Possible reasons include: * The file was deleted, renamed, or moved to another location. * An install or uninstall procedure did not complete successfully. * The installation package was faulty and contained "/usr/lib/llvm-14/lib/cmake/llvm/LLVMExports.cmake" but not all the files it references. Call Stack (most recent call first): /usr/lib/llvm-14/cmake/LLVMConfig.cmake:323 (include) CMakeLists.txt:3 (find_package) -- Configuring incomplete, errors occurred! Andreas --- End Message --- --- Begin Message --- Source: llvm-toolchain-14 Source-Version: 1:14.0.6-6 Done: Sylvestre Ledru We believe that the bug you reported is fixed in the latest version of llvm-toolchain-14, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 1022...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Sylvestre Ledru (supplier of updated llvm-toolchain-14 package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Sun, 23 Oct 2022 16:07:45 +0200 Source: llvm-toolchain-14 Architecture: source Version: 1:14.0.6-6 Distribution: unstable Urgency: medium Maintainer: LLVM Packaging Team Changed-By: Sylvestre Ledru Closes: 1021857 1022414 Changes: llvm-toolchain-14 (1:14.0.6-6) unstable; urgency=medium . * Unbreak the cmake detection (Closes: #1021857, #1022414) Checksums-Sha1: d85a31643f5f9b88be53fbd551987ea329476351 7208 llvm-toolchain-14_14.0.6-6.dsc ac2b1af5ded2c8b9b2ab7afb30b0e1e1f506cec6 154560 llvm-toolchain-14_14.0.6-6.debian.tar.xz b49b7830526029522bc38aef1f84165bfe3f0263 31017 llvm-toolchain-14_14.0.6-6_amd64.buildinfo Checksums-Sha256: b049642c5060562f0da889ba1ee1de39309b231194db274aeb3b0a84bb978686 7208 llvm-toolchain-14_14.0.6-6.dsc 7d93e23e63c74f14b18cabb7c992cd7e190181298beaa961d6216f2634d3b1d3 154560 llvm-toolchain-14_14.0.6-6.debian.tar.xz d5b8fb37801fdea9a1d63e73fb1b45999230c7114239a946647ad2e3a20f1255 31017 llvm-toolchain-14_14.0.6-6_amd64.buildinfo Files: dcc65e053373b2a96e8b1d6c49ec2ca8 7208 devel optional llvm-toolchain-14_14.0.6-6.dsc 25f1a9b74b1ae273fa134ce822531d89 154560 devel optional llvm-toolchain-14_14.0.6-6.debian.tar.xz ebf95d429e4735cd1ac6ed86f7e23ae7 31017 devel optional llvm-toolchain-14_14.0.6-6_amd64.buildinfo -BEGIN PGP SIGNATURE-
Bug#1022409: marked as done (ccls: FTBFS: make[1]: *** [debian/rules:18: override_dh_auto_configure] Error 2)
Your message dated Sun, 23 Oct 2022 18:37:16 + with message-id and subject line Bug#1021857: fixed in llvm-toolchain-14 1:14.0.6-6 has caused the Debian Bug report #1021857, regarding ccls: FTBFS: make[1]: *** [debian/rules:18: override_dh_auto_configure] Error 2 to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 1021857: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1021857 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: ccls Version: 0.20220729-1 Severity: serious Justification: FTBFS Tags: bookworm sid ftbfs User: lu...@debian.org Usertags: ftbfs-20221023 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_configure -- -DCCLS_VERSION=0.20220729-1 > -DCLANG_RESOURCE_DIR=/usr/include/clang/14 > cd obj-x86_64-linux-gnu && cmake -DCMAKE_INSTALL_PREFIX=/usr > -DCMAKE_BUILD_TYPE=None -DCMAKE_INSTALL_SYSCONFDIR=/etc > -DCMAKE_INSTALL_LOCALSTATEDIR=/var -DCMAKE_EXPORT_NO_PACKAGE_REGISTRY=ON > -DCMAKE_FIND_USE_PACKAGE_REGISTRY=OFF > -DCMAKE_FIND_PACKAGE_NO_PACKAGE_REGISTRY=ON > -DFETCHCONTENT_FULLY_DISCONNECTED=ON -DCMAKE_INSTALL_RUNSTATEDIR=/run > -DCMAKE_SKIP_INSTALL_ALL_DEPENDENCY=ON "-GUnix Makefiles" > -DCMAKE_VERBOSE_MAKEFILE=ON -DCMAKE_INSTALL_LIBDIR=lib/x86_64-linux-gnu > -DCCLS_VERSION=0.20220729-1 -DCLANG_RESOURCE_DIR=/usr/include/clang/14 .. > -- The CXX compiler identification is GNU 12.2.0 > -- The C compiler identification is GNU 12.2.0 > -- Detecting CXX compiler ABI info > -- Detecting CXX compiler ABI info - done > -- Check for working CXX compiler: /usr/bin/c++ - skipped > -- Detecting CXX compile features > -- Detecting CXX compile features - done > -- Detecting C compiler ABI info > -- Detecting C compiler ABI info - done > -- Check for working C compiler: /usr/bin/cc - skipped > -- Detecting C compile features > -- Detecting C compile features - done > -- Performing Test HAVE_FFI_CALL > -- Performing Test HAVE_FFI_CALL - Success > -- Found FFI: /usr/lib/x86_64-linux-gnu/libffi.so > -- Performing Test Terminfo_LINKABLE > -- Performing Test Terminfo_LINKABLE - Success > -- Found Terminfo: /usr/lib/x86_64-linux-gnu/libtinfo.so > -- Could NOT find ZLIB (missing: ZLIB_LIBRARY ZLIB_INCLUDE_DIR) > -- Found LibXml2: /usr/lib/x86_64-linux-gnu/libxml2.so (found version > "2.9.14") > CMake Error at /usr/lib/llvm-14/lib/cmake/llvm/LLVMExports.cmake:1598 > (message): > The imported target "sancov" references the file > > "/usr/lib/llvm-14/bin/sancov" > > but this file does not exist. Possible reasons include: > > * The file was deleted, renamed, or moved to another location. > > * An install or uninstall procedure did not complete successfully. > > * The installation package was faulty and contained > > "/usr/lib/llvm-14/lib/cmake/llvm/LLVMExports.cmake" > > but not all the files it references. > > Call Stack (most recent call first): > /usr/lib/llvm-14/lib/cmake/llvm/LLVMConfig.cmake:323 (include) > /usr/lib/cmake/clang-14/ClangConfig.cmake:10 (find_package) > CMakeLists.txt:72 (find_package) > > > -- Configuring incomplete, errors occurred! > See also "/<>/obj-x86_64-linux-gnu/CMakeFiles/CMakeOutput.log". > cd obj-x86_64-linux-gnu && tail -v -n \+0 CMakeCache.txt > ==> CMakeCache.txt <== > # This is the CMakeCache file. > # For build in directory: /<>/obj-x86_64-linux-gnu > # It was generated by CMake: /usr/bin/cmake > # You can edit this file to change values found and used by cmake. > # If you do not want to change any of the values, simply exit the editor. > # If you do want to change a value, simply edit, save, and exit the editor. > # The syntax for the file is as follows: > # KEY:TYPE=VALUE > # KEY is the name of a variable in the cache. > # TYPE is a hint to GUIs for the type of VALUE, DO NOT EDIT TYPE!. > # VALUE is the current value for the KEY. > > > # EXTERNAL cache entries > > > //No help, variable specified on the command line. > CCLS_VERSION:UNINITIALIZED=0.20220729-1 > > //No help, variable specified on the command line. > CLANG_RESOURCE_DIR:UNINITIALIZED=/usr/include/
Bug#1022337: marked as done (qt6-tools: FTBFS: The imported target "sancov" references the file "/usr/lib/llvm-14/bin/sancov" but this file does not exist.)
Your message dated Sun, 23 Oct 2022 18:37:16 + with message-id and subject line Bug#1021857: fixed in llvm-toolchain-14 1:14.0.6-6 has caused the Debian Bug report #1021857, regarding qt6-tools: FTBFS: The imported target "sancov" references the file "/usr/lib/llvm-14/bin/sancov" but this file does not exist. to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 1021857: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1021857 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: qt6-tools Version: 6.3.1-2 Severity: serious Justification: FTBFS Tags: bookworm sid ftbfs User: lu...@debian.org Usertags: ftbfs-20221023 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_configure -- \ > -DCMAKE_LIBRARY_PATH=x86_64-linux-gnu \ > -DCMAKE_SKIP_INSTALL_RPATH=ON > cd obj-x86_64-linux-gnu && cmake -DCMAKE_INSTALL_PREFIX=/usr > -DCMAKE_BUILD_TYPE=None -DCMAKE_INSTALL_SYSCONFDIR=/etc > -DCMAKE_INSTALL_LOCALSTATEDIR=/var -DCMAKE_EXPORT_NO_PACKAGE_REGISTRY=ON > -DCMAKE_FIND_USE_PACKAGE_REGISTRY=OFF > -DCMAKE_FIND_PACKAGE_NO_PACKAGE_REGISTRY=ON > -DFETCHCONTENT_FULLY_DISCONNECTED=ON -DCMAKE_INSTALL_RUNSTATEDIR=/run > -DCMAKE_SKIP_INSTALL_ALL_DEPENDENCY=ON -GNinja -DCMAKE_VERBOSE_MAKEFILE=ON > -DCMAKE_INSTALL_LIBDIR=lib/x86_64-linux-gnu > -DCMAKE_LIBRARY_PATH=x86_64-linux-gnu -DCMAKE_SKIP_INSTALL_RPATH=ON .. > -- The CXX compiler identification is GNU 12.2.0 > -- The C compiler identification is GNU 12.2.0 > -- Detecting CXX compiler ABI info > -- Detecting CXX compiler ABI info - done > -- Check for working CXX compiler: /usr/bin/c++ - skipped > -- Detecting CXX compile features > -- Detecting CXX compile features - done > -- Detecting C compiler ABI info > -- Detecting C compiler ABI info - done > -- Check for working C compiler: /usr/bin/cc - skipped > -- Detecting C compile features > -- Detecting C compile features - done > -- Performing Test CMAKE_HAVE_LIBC_PTHREAD > -- Performing Test CMAKE_HAVE_LIBC_PTHREAD - Success > -- Found Threads: TRUE > -- Performing Test HAVE_STDATOMIC > -- Performing Test HAVE_STDATOMIC - Success > -- Found WrapAtomic: TRUE > -- Found OpenGL: /usr/lib/x86_64-linux-gnu/libOpenGL.so > CMake Error at /usr/lib/llvm-14/lib/cmake/llvm/LLVMExports.cmake:1598 > (message): > The imported target "sancov" references the file > > "/usr/lib/llvm-14/bin/sancov" > > but this file does not exist. Possible reasons include: > > * The file was deleted, renamed, or moved to another location. > > * An install or uninstall procedure did not complete successfully. > > * The installation package was faulty and contained > > "/usr/lib/llvm-14/lib/cmake/llvm/LLVMExports.cmake" > > but not all the files it references. > > Call Stack (most recent call first): > /usr/lib/llvm-14/cmake/LLVMConfig.cmake:323 (include) > /usr/lib/llvm-14/lib/cmake/clang/ClangConfig.cmake:10 (find_package) > cmake/FindWrapLibClang.cmake:14 (find_package) > /usr/lib/x86_64-linux-gnu/cmake/Qt6/QtFindPackageHelpers.cmake:130 > (find_package) > configure.cmake:17 (qt_find_package) > /usr/lib/x86_64-linux-gnu/cmake/Qt6/QtFeature.cmake:573 (include) > src/CMakeLists.txt:21 (qt_feature_evaluate_features) > > > -- Configuring incomplete, errors occurred! > See also "/<>/obj-x86_64-linux-gnu/CMakeFiles/CMakeOutput.log". > cd obj-x86_64-linux-gnu && tail -v -n \+0 CMakeCache.txt > ==> CMakeCache.txt <== > # This is the CMakeCache file. > # For build in directory: /<>/obj-x86_64-linux-gnu > # It was generated by CMake: /usr/bin/cmake > # You can edit this file to change values found and used by cmake. > # If you do not want to change any of the values, simply exit the editor. > # If you do want to change a value, simply edit, save, and exit the editor. > # The syntax for the file is as follows: > # KEY:TYPE=VALUE > # KEY is the name of a variable in the cache. > # TYPE is a hint to GUIs for the type of VALUE, DO NOT EDIT TYPE!. > # VALUE is the current value for the KEY. > > > # EXTERNAL cache entries > > > //Build Q
Bug#1021857: marked as done (llvm-14-dev: CMake Error in LLVMExports.cmake: The imported target "sancov" references the file "/usr/lib/llvm-14/bin/sancov" but this file does not exist.)
Your message dated Sun, 23 Oct 2022 18:37:16 + with message-id and subject line Bug#1021857: fixed in llvm-toolchain-14 1:14.0.6-6 has caused the Debian Bug report #1021857, regarding llvm-14-dev: CMake Error in LLVMExports.cmake: The imported target "sancov" references the file "/usr/lib/llvm-14/bin/sancov" but this file does not exist. to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 1021857: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1021857 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: llvm-14-dev Version: 1:14.0.6-5 Severity: serious This is an autopkgtest regression, but also experienced e.g. while building spirv-llvm-translator-14: -- 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/bin/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/bin/c++ - skipped -- Detecting CXX compile features -- Detecting CXX compile features - done -- Performing Test HAVE_FFI_CALL -- Performing Test HAVE_FFI_CALL - Success -- Found FFI: /usr/lib/x86_64-linux-gnu/libffi.so -- Performing Test Terminfo_LINKABLE -- Performing Test Terminfo_LINKABLE - Success -- Found Terminfo: /usr/lib/x86_64-linux-gnu/libtinfo.so -- Could NOT find ZLIB (missing: ZLIB_LIBRARY ZLIB_INCLUDE_DIR) -- Found LibXml2: /usr/lib/x86_64-linux-gnu/libxml2.so (found version "2.9.14") CMake Error at /usr/lib/llvm-14/lib/cmake/llvm/LLVMExports.cmake:1598 (message): The imported target "sancov" references the file "/usr/lib/llvm-14/bin/sancov" but this file does not exist. Possible reasons include: * The file was deleted, renamed, or moved to another location. * An install or uninstall procedure did not complete successfully. * The installation package was faulty and contained "/usr/lib/llvm-14/lib/cmake/llvm/LLVMExports.cmake" but not all the files it references. Call Stack (most recent call first): /usr/lib/llvm-14/cmake/LLVMConfig.cmake:323 (include) CMakeLists.txt:3 (find_package) -- Configuring incomplete, errors occurred! Andreas --- End Message --- --- Begin Message --- Source: llvm-toolchain-14 Source-Version: 1:14.0.6-6 Done: Sylvestre Ledru We believe that the bug you reported is fixed in the latest version of llvm-toolchain-14, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 1021...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Sylvestre Ledru (supplier of updated llvm-toolchain-14 package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Sun, 23 Oct 2022 16:07:45 +0200 Source: llvm-toolchain-14 Architecture: source Version: 1:14.0.6-6 Distribution: unstable Urgency: medium Maintainer: LLVM Packaging Team Changed-By: Sylvestre Ledru Closes: 1021857 1022414 Changes: llvm-toolchain-14 (1:14.0.6-6) unstable; urgency=medium . * Unbreak the cmake detection (Closes: #1021857, #1022414) Checksums-Sha1: d85a31643f5f9b88be53fbd551987ea329476351 7208 llvm-toolchain-14_14.0.6-6.dsc ac2b1af5ded2c8b9b2ab7afb30b0e1e1f506cec6 154560 llvm-toolchain-14_14.0.6-6.debian.tar.xz b49b7830526029522bc38aef1f84165bfe3f0263 31017 llvm-toolchain-14_14.0.6-6_amd64.buildinfo Checksums-Sha256: b049642c5060562f0da889ba1ee1de39309b231194db274aeb3b0a84bb978686 7208 llvm-toolchain-14_14.0.6-6.dsc 7d93e23e63c74f14b18cabb7c992cd7e190181298beaa961d6216f2634d3b1d3 154560 llvm-toolchain-14_14.0.6-6.debian.tar.xz d5b8fb37801fdea9a1d63e73fb1b45999230c7114239a946647ad2e3a20f1255 31017 llvm-toolchain-14_14.0.6-6_amd64.buildinfo Files: dcc65e053373b2a96e8b1d6c49ec2ca8 7208 devel optional llvm-toolchain-14_14.0.6-6.dsc 25f1a9b74b1ae273fa134ce822531d89 154560 devel optional llvm-toolchain-14_14.0.6-6.debian.tar.xz ebf95d429e4735cd1ac6ed86f7e23ae7 31017 devel optional llvm-toolchain-14_14.0.6-6_amd64.buildinfo -BEGIN PGP SIGNATURE-
Bug#1022399: marked as done (liblrdf: FTBFS: make: *** [/usr/share/cdbs/1/class/autotools.mk:46: debian/stamp-autotools] Error 2)
Your message dated Sun, 23 Oct 2022 18:24:06 + with message-id and subject line Bug#1022399: fixed in liblrdf 0.6.1-3 has caused the Debian Bug report #1022399, regarding liblrdf: FTBFS: make: *** [/usr/share/cdbs/1/class/autotools.mk:46: debian/stamp-autotools] Error 2 to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 1022399: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1022399 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: liblrdf Version: 0.6.1-2 Severity: serious Justification: FTBFS Tags: bookworm sid ftbfs User: lu...@debian.org Usertags: ftbfs-20221023 ftbfs-bookworm Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > debian/rules build > test -x debian/rules > mkdir -p "." > > Scanning upstream source for new/changed copyright notices... > > set -e; LC_ALL=C.UTF-8 /usr/bin/licensecheck --check '.*' --recursive > --copyright --deb-fmt --ignore > '^(debian/(changelog|copyright(|_hints|_newhints)))$' --lines 0 -- * | > /usr/lib/cdbs/licensecheck2dep5 > debian/copyright_newhints > 5 combinations of copyright and licensing found. > WARNING: New or changed notices discovered: > > Format: https://www.debian.org/doc/packaging-manuals/copyright-format/1.0/ > examples/.gitignore > src/.gitignore > License: public-domain > License: GPL-2 > Copyright: 2003-2004, Robert Jordens > > To fix the situation please do the following: > 1) Examine debian/copyright_* and referenced files > 2) Update debian/copyright as needed > 3) Replace debian/copyright_hints with debian/copyright_newhints > touch debian/stamp-copyright-check > mkdir -p "debian/upstream-cruft" > mv "INSTALL" "debian/upstream-cruft/INSTALL"; > > touch debian/stamp-upstream-cruft > cd . && libtoolize -c -f > libtoolize: putting auxiliary files in '.'. > libtoolize: copying file './ltmain.sh' > libtoolize: putting macros in AC_CONFIG_MACRO_DIRS, 'm4'. > libtoolize: copying file 'm4/libtool.m4' > libtoolize: copying file 'm4/ltoptions.m4' > libtoolize: copying file 'm4/ltsugar.m4' > libtoolize: copying file 'm4/ltversion.m4' > libtoolize: copying file 'm4/lt~obsolete.m4' > cd . && aclocal -Im4 --install --force > cd . && autoconf > configure.ac:4: warning: 'AM_CONFIG_HEADER': this macro is obsolete. > configure.ac:4: You should use the 'AC_CONFIG_HEADERS' macro instead. > ./lib/autoconf/general.m4:2434: AC_DIAGNOSE is expanded from... > aclocal.m4:745: AM_CONFIG_HEADER is expanded from... > configure.ac:4: the top level > configure.ac:5: warning: AM_INIT_AUTOMAKE: two- and three-arguments forms are > deprecated. > ./lib/autoconf/general.m4:2434: AC_DIAGNOSE is expanded from... > aclocal.m4:429: AM_INIT_AUTOMAKE is expanded from... > configure.ac:5: the top level > configure.ac:16: warning: The macro `AM_PROG_LIBTOOL' is obsolete. > configure.ac:16: You should run autoupdate. > m4/libtool.m4:101: AM_PROG_LIBTOOL is expanded from... > configure.ac:16: the top level > configure.ac:19: warning: The macro `AC_HEADER_STDC' is obsolete. > configure.ac:19: You should run autoupdate. > ./lib/autoconf/headers.m4:704: AC_HEADER_STDC is expanded from... > configure.ac:19: the top level > configure.ac:41: warning: AC_OUTPUT should be used without arguments. > configure.ac:41: You should run autoupdate. > cd . && autoheader > cd . && automake --add-missing --copy --foreign --force > configure.ac:5: warning: AM_INIT_AUTOMAKE: two- and three-arguments forms are > deprecated. For more info, see: > configure.ac:5: > https://www.gnu.org/software/automake/manual/automake.html#Modernize-AM_005fINIT_005fAUTOMAKE-invocation > configure.ac:11: installing './compile' > configure.ac:16: installing './config.guess' > configure.ac:16: installing './config.sub' > configure.ac:5: installing './install-sh' > configure.ac:5: installing './missing' > examples/Makefile.am: installing './depcomp' > parallel-tests: installing './test-driver' > touch debian/stamp-autotools-files > chmod a+x /<>/./configure > mkdir -p . > cd . && CFLAGS="-g -O2 -ffile-prefix-map=/<>=. > -fstack-protector-strong -Wformat -Werror=format-security" CXXFLAGS=
Bug#1022548: lokalize: text window does not repaint
Package: lokalize Version: 4:22.08.2-1~np1 Severity: grave Justification: renders package unusable X-Debbugs-Cc: l...@castermans.org Dear Maintainer, *** Reporter, please consider answering these questions, where appropriate *** lokalize open correctly, the window with translation memory shows correctly as well. Each file to translate opens correctly as well in a seperate window. However the text in that window is NOT SHOWN at all. With this the application is not usable. *** End of the template - remove these template lines *** -- System Information: Debian Release: bookworm/sid APT prefers testing APT policy: (990, 'testing'), (500, 'experimental'), (500, 'unstable') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 6.0.0-2-amd64 (SMP w/4 CPU threads; PREEMPT) Locale: LANG=nl_NL.UTF-8, LC_CTYPE=nl_NL.UTF-8 (charmap=UTF-8), LANGUAGE=nl Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages lokalize depends on: ii kio5.98.0-1 ii libc6 2.36-1 ii libhunspell-1.7-0 1.7.1-1 ii libkf5completion5 5.98.0-1 ii libkf5configcore5 5.98.0-1 ii libkf5configgui5 5.98.0-1 ii libkf5configwidgets5 5.98.0-1 ii libkf5coreaddons5 5.98.0-1 ii libkf5crash5 5.98.0-1 ii libkf5dbusaddons5 5.98.0-1 ii libkf5i18n55.98.0-1+b1 ii libkf5itemviews5 5.98.0-1 ii libkf5kiocore5 5.98.0-1 ii libkf5kiofilewidgets5 5.98.0-1 ii libkf5kiowidgets5 5.98.0-1 ii libkf5notifications5 5.98.0-1 ii libkf5sonnetcore5 5.98.0-1 ii libkf5sonnetui55.98.0-1 ii libkf5textwidgets5 5.98.0-1 ii libkf5widgetsaddons5 5.98.0-1 ii libkf5xmlgui5 5.98.0-1+b1 ii libqt5core5a 5.15.6+dfsg-2 ii libqt5dbus55.15.6+dfsg-2 ii libqt5gui5 5.15.6+dfsg-2 ii libqt5network5 5.15.6+dfsg-2 ii libqt5sql5 5.15.6+dfsg-2 ii libqt5sql5-sqlite 5.15.6+dfsg-2 ii libqt5widgets5 5.15.6+dfsg-2 ii libqt5xml5 5.15.6+dfsg-2 ii libstdc++6 12.2.0-7 Versions of packages lokalize recommends: ii gettext0.21-9 ii sonnet-plugins 5.98.0-1 ii translate-toolkit 3.7.3-2 Versions of packages lokalize suggests: ii khelpcenter 4:22.08.2-1~np1 ii poxml4:22.08.2-1~np1 -- no debconf information
Bug#1022417: marked as pending in node-js-tokens
Control: tag -1 pending Hello, Bug #1022417 in node-js-tokens reported by you has been fixed in the Git repository and is awaiting an upload. You can see the commit message below and you can check the diff of the fix at: https://salsa.debian.org/js-team/node-js-tokens/-/commit/9a301f7e0745ccdf0e76c3dcfceed158ad1eff27 Add fix for jest >= 29 Closes: #1022417 (this message was generated automatically) -- Greetings https://bugs.debian.org/1022417
Processed: Bug#1022417 marked as pending in node-js-tokens
Processing control commands: > tag -1 pending Bug #1022417 [src:node-js-tokens] node-js-tokens: FTBFS: ln: failed to create symbolic link 'build/.': File exists Added tag(s) pending. -- 1022417: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1022417 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1022401: marked as pending in node-global-modules
Control: tag -1 pending Hello, Bug #1022401 in node-global-modules reported by you has been fixed in the Git repository and is awaiting an upload. You can see the commit message below and you can check the diff of the fix at: https://salsa.debian.org/js-team/node-global-modules/-/commit/6624fb774b48683939d4dc1475f8a0bc1358e1fb Drop test: useless and rot relevant Closes: #1022401 (this message was generated automatically) -- Greetings https://bugs.debian.org/1022401
Processed: Bug#1022401 marked as pending in node-global-modules
Processing control commands: > tag -1 pending Bug #1022401 [src:node-global-modules] node-global-modules: FTBFS: dh_auto_test: error: /bin/sh -ex debian/tests/pkg-js/test returned exit code 1 Added tag(s) pending. -- 1022401: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1022401 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1016744: marked as done (vim-ultisnips: autopkgtest failure on arm64, i386 and ppc64el)
Your message dated Sun, 23 Oct 2022 19:44:44 +0200 with message-id and subject line Re: vim-ultisnips: autopkgtest failure on arm64, i386 and ppc64el has caused the Debian Bug report #1016744, regarding vim-ultisnips: autopkgtest failure on arm64, i386 and ppc64el to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 1016744: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1016744 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: vim-ultisnips Version: 3.2-1 Severity: serious User: debian...@lists.debian.org Usertags: fails-always Dear maintainer(s), You recently added an autopkgtest to your package vim-ultisnips, great. However, it fails on arm64, i386 and ppc64el. Currently this failure is blocking the migration to testing [1]. Can you please investigate the situation and fix it? I copied some of the output at the bottom of this report. More information about this bug and the reason for filing it can be found on https://wiki.debian.org/ContinuousIntegration/RegressionEmailInformation Paul [1] https://qa.debian.org/excuses.php?package=vim-ultisnips https://ci.debian.net/data/autopkgtest/testing/arm64/v/vim-ultisnips/23984911/log.gz == FAIL: runTest (test_ParseSnippets.ParseSnippets_ExtendsWithoutFiletype) -- Traceback (most recent call last): File "/tmp/autopkgtest-lxc.p149hn5f/downtmp/build.kSM/src/test/vim_test_case.py", line 53, in runTest self.assertRegexpMatches(self.output, self.expected_error) AssertionError: Regex didn't match: "'extends' without file types in \\S+:2" not found in 'An error occured. This is either a bug in UltiSnips or a bug in a\nsnippet definition. If you think this is a bug, please report it to\nhttps://github.com/SirVer/ultisnips/issues/new\nPlease read and follow:\nhttps://github.com/SirVer/ultisnips/blob/master/CONTRIBUTING.md#reproducing-bugs\n\nFollowing is the full stack trace:\nTraceback (most recent call last):\n File "/usr/share/nvim/site/pack/dist-bundle/opt/ultisnips/pythonx/UltiSnips/err_to_scratch_buffer.py", line 18, in wrapper\nreturn func(self, *args, **kwds)\n File "/usr/share/nvim/site/pack/dist-bundle/opt/ultisnips/pythonx/UltiSnips/snippet_manager.py", line 905, in _track_change\n self._try_expand(autotrigger_only=True)\n File "/usr/share/nvim/site/pack/dist-bundle/opt/ultisnips/pythonx/UltiSnips/snippet_manager.py", line 749, in _try_expand\nsnippets = self._snips(before, False, autotrigger_only)\n File "/usr/share/nvim/site/pack/dist-bundle/opt/ultisnips/pythonx/UltiSnips/snippet_manager.py", line 629, in _snips\nsource.ensure(filetypes)\n File "/usr/share/nvim/site/pack/dist-bundle/opt/ultisnips/pythonx/UltiSnips/snippet/source/file/base.py", line 31, in ensure\nself._load_snippets_for(ft)\n File "/usr/share/nvim/site/pack/dist-bundle/opt/ultisnips/pythonx/UltiSnips/snippet/source/file/base.py", line 53, in _load_snippets_for\nself._parse_snippets(ft, fn)\n File "/usr/share/nvim/site/pack/dist-bundle/opt/ultisnips/pythonx/UltiSnips/snippet/source/file/base.py", line 69, in _parse_snippets\nraise SnippetSyntaxError(filename, line_index, msg)\nUltiSnips.snippet.source.file.base.SnippetSyntaxError: \'extends\' without file types in /tmp/p\tautopkgtest-lxc.p149hn5f/downtmp/autopkgtest_tmp/UltiSnipsTest_Casenir0duuw/us/all.snippets:2' -- Ran 560 tests in 1259.152s FAILED (failures=1, skipped=4) autopkgtest [05:49:55]: test with-neovim OpenPGP_signature Description: OpenPGP digital signature --- End Message --- --- Begin Message --- Control: notfound -1 3.2-1 This was resolved in the mean time by some other package upload.--- End Message ---
Bug#1022309: marked as done (spades: FTBFS: CheckIncludeFile.c:1:10: fatal error: cxxabi.h: No such file or directory)
Your message dated Sun, 23 Oct 2022 17:34:42 + with message-id and subject line Bug#1022309: fixed in spades 3.15.5+dfsg-2 has caused the Debian Bug report #1022309, regarding spades: FTBFS: CheckIncludeFile.c:1:10: fatal error: cxxabi.h: No such file or directory to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 1022309: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1022309 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: spades Version: 3.15.5+dfsg-1 Severity: serious Justification: FTBFS Tags: bookworm sid ftbfs User: lu...@debian.org Usertags: ftbfs-20221023 ftbfs-bookworm Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > /usr/bin/cc -g -O2 -ffile-prefix-map=/<>=. > -fstack-protector-strong -Wformat -Werror=format-security -Wdate-time > -D_FORTIFY_SOURCE=2 -fopenmp -o > CMakeFiles/cmTC_d9a5b.dir/CheckIncludeFile.c.o -c > /<>/obj-x86_64-linux-gnu/CMakeFiles/CMakeTmp/CheckIncludeFile.c > /<>/obj-x86_64-linux-gnu/CMakeFiles/CMakeTmp/CheckIncludeFile.c:1:10: > fatal error: cxxabi.h: No such file or directory > 1 | #include > | ^~ > compilation terminated. > gmake[3]: *** [CMakeFiles/cmTC_d9a5b.dir/build.make:78: > CMakeFiles/cmTC_d9a5b.dir/CheckIncludeFile.c.o] Error 1 > gmake[3]: Leaving directory > '/<>/obj-x86_64-linux-gnu/CMakeFiles/CMakeTmp' > gmake[2]: *** [Makefile:127: cmTC_d9a5b/fast] Error 2 > gmake[2]: Leaving directory > '/<>/obj-x86_64-linux-gnu/CMakeFiles/CMakeTmp' > > > > Determining if the include file mach/mach.h exists failed with the following > output: > Change Dir: /<>/obj-x86_64-linux-gnu/CMakeFiles/CMakeTmp > > Run Build Command(s):/usr/bin/gmake -f Makefile cmTC_17e7d/fast && gmake[2]: > Entering directory '/<>/obj-x86_64-linux-gnu/CMakeFiles/CMakeTmp' > /usr/bin/gmake -f CMakeFiles/cmTC_17e7d.dir/build.make > CMakeFiles/cmTC_17e7d.dir/build > gmake[3]: Entering directory > '/<>/obj-x86_64-linux-gnu/CMakeFiles/CMakeTmp' > Building C object CMakeFiles/cmTC_17e7d.dir/CheckIncludeFile.c.o > /usr/bin/cc -g -O2 -ffile-prefix-map=/<>=. > -fstack-protector-strong -Wformat -Werror=format-security -Wdate-time > -D_FORTIFY_SOURCE=2 -fopenmp -o > CMakeFiles/cmTC_17e7d.dir/CheckIncludeFile.c.o -c > /<>/obj-x86_64-linux-gnu/CMakeFiles/CMakeTmp/CheckIncludeFile.c > /<>/obj-x86_64-linux-gnu/CMakeFiles/CMakeTmp/CheckIncludeFile.c:1:10: > fatal error: mach/mach.h: No such file or directory > 1 | #include > | ^ > compilation terminated. > gmake[3]: *** [CMakeFiles/cmTC_17e7d.dir/build.make:78: > CMakeFiles/cmTC_17e7d.dir/CheckIncludeFile.c.o] Error 1 > gmake[3]: Leaving directory > '/<>/obj-x86_64-linux-gnu/CMakeFiles/CMakeTmp' > gmake[2]: *** [Makefile:127: cmTC_17e7d/fast] Error 2 > gmake[2]: Leaving directory > '/<>/obj-x86_64-linux-gnu/CMakeFiles/CMakeTmp' > > > > Determining if the include file malloc/malloc.h exists failed with the > following output: > Change Dir: /<>/obj-x86_64-linux-gnu/CMakeFiles/CMakeTmp > > Run Build Command(s):/usr/bin/gmake -f Makefile cmTC_40da2/fast && gmake[2]: > Entering directory '/<>/obj-x86_64-linux-gnu/CMakeFiles/CMakeTmp' > /usr/bin/gmake -f CMakeFiles/cmTC_40da2.dir/build.make > CMakeFiles/cmTC_40da2.dir/build > gmake[3]: Entering directory > '/<>/obj-x86_64-linux-gnu/CMakeFiles/CMakeTmp' > Building C object CMakeFiles/cmTC_40da2.dir/CheckIncludeFile.c.o > /usr/bin/cc -g -O2 -ffile-prefix-map=/<>=. > -fstack-protector-strong -Wformat -Werror=format-security -Wdate-time > -D_FORTIFY_SOURCE=2 -fopenmp -o > CMakeFiles/cmTC_40da2.dir/CheckIncludeFile.c.o -c > /<>/obj-x86_64-linux-gnu/CMakeFiles/CMakeTmp/CheckIncludeFile.c > /<>/obj-x86_64-linux-gnu/CMakeFiles/CMakeTmp/CheckIncludeFile.c:1:10: > fatal error: malloc/malloc.h: No such file or directory > 1 | #include > | ^ > compilation terminated. > gmake[3]: *** [CMakeFiles/cmTC_40da2.dir/build.make:78: > CMakeFiles/cmTC_40da2.dir/CheckIncludeFile.c.o] Error 1 > gmake[3]: Leaving directory > '/<>/obj-x86_64-linux-gnu/CMakeFiles/CMakeTmp' > gmake[2]: *** [Makefile:127: cmTC_40da2/fast] Error 2 > gmake[2]: Le
Bug#1020046: marked as done (slimit: FTBFS: ModuleNotFoundError: No module named 'minifier')
Your message dated Sun, 23 Oct 2022 17:33:53 + with message-id and subject line Bug#1020046: fixed in slimit 0.8.1-6 has caused the Debian Bug report #1020046, regarding slimit: FTBFS: ModuleNotFoundError: No module named 'minifier' to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 1020046: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1020046 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: slimit Version: 0.8.1-5 Severity: serious Justification: FTBFS Tags: bookworm sid ftbfs User: lu...@debian.org Usertags: ftbfs-20220917 ftbfs-bookworm Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > debian/rules build > dh build --with python3 --buildsystem=pybuild >dh_update_autotools_config -O--buildsystem=pybuild >dh_autoreconf -O--buildsystem=pybuild >dh_auto_configure -O--buildsystem=pybuild > I: pybuild base:240: python3.10 setup.py config > Warning: 'classifiers' should be a list, got type 'filter' > running config >dh_auto_build -O--buildsystem=pybuild > I: pybuild base:240: /usr/bin/python3 setup.py build > Warning: 'classifiers' should be a list, got type 'filter' > running build > running build_py > creating /<>/.pybuild/cpython3_3.10_slimit/build/slimit > copying src/slimit/__init__.py -> > /<>/.pybuild/cpython3_3.10_slimit/build/slimit > copying src/slimit/parser.py -> > /<>/.pybuild/cpython3_3.10_slimit/build/slimit > copying src/slimit/mangler.py -> > /<>/.pybuild/cpython3_3.10_slimit/build/slimit > copying src/slimit/ast.py -> > /<>/.pybuild/cpython3_3.10_slimit/build/slimit > copying src/slimit/unicode_chars.py -> > /<>/.pybuild/cpython3_3.10_slimit/build/slimit > copying src/slimit/lexer.py -> > /<>/.pybuild/cpython3_3.10_slimit/build/slimit > copying src/slimit/scope.py -> > /<>/.pybuild/cpython3_3.10_slimit/build/slimit > copying src/slimit/yacctab.py -> > /<>/.pybuild/cpython3_3.10_slimit/build/slimit > copying src/slimit/lextab.py -> > /<>/.pybuild/cpython3_3.10_slimit/build/slimit > copying src/slimit/minifier.py -> > /<>/.pybuild/cpython3_3.10_slimit/build/slimit > creating /<>/.pybuild/cpython3_3.10_slimit/build/slimit/visitors > copying src/slimit/visitors/__init__.py -> > /<>/.pybuild/cpython3_3.10_slimit/build/slimit/visitors > copying src/slimit/visitors/minvisitor.py -> > /<>/.pybuild/cpython3_3.10_slimit/build/slimit/visitors > copying src/slimit/visitors/nodevisitor.py -> > /<>/.pybuild/cpython3_3.10_slimit/build/slimit/visitors > copying src/slimit/visitors/ecmavisitor.py -> > /<>/.pybuild/cpython3_3.10_slimit/build/slimit/visitors > copying src/slimit/visitors/scopevisitor.py -> > /<>/.pybuild/cpython3_3.10_slimit/build/slimit/visitors > creating /<>/.pybuild/cpython3_3.10_slimit/build/slimit/tests > copying src/slimit/tests/__init__.py -> > /<>/.pybuild/cpython3_3.10_slimit/build/slimit/tests > copying src/slimit/tests/test_nodevisitor.py -> > /<>/.pybuild/cpython3_3.10_slimit/build/slimit/tests > copying src/slimit/tests/test_ecmavisitor.py -> > /<>/.pybuild/cpython3_3.10_slimit/build/slimit/tests > copying src/slimit/tests/test_mangler.py -> > /<>/.pybuild/cpython3_3.10_slimit/build/slimit/tests > copying src/slimit/tests/test_cmd.py -> > /<>/.pybuild/cpython3_3.10_slimit/build/slimit/tests > copying src/slimit/tests/test_lexer.py -> > /<>/.pybuild/cpython3_3.10_slimit/build/slimit/tests > copying src/slimit/tests/test_minifier.py -> > /<>/.pybuild/cpython3_3.10_slimit/build/slimit/tests > copying src/slimit/tests/test_parser.py -> > /<>/.pybuild/cpython3_3.10_slimit/build/slimit/tests >dh_auto_test -O--buildsystem=pybuild > I: pybuild base:240: cd /<>/.pybuild/cpython3_3.10_slimit/build; > python3.10 -m unittest discover -v > slimit (unittest.loader._FailedTest) ... ERROR > > == > ERROR: slimit (unittest.loader._FailedTest) > -- > ImportError: Failed to import test module: slimit > Traceback (most recent call last): > File "/usr/lib/python3.10/unittest/loader.py", line 470, in _find_test_path > package = self._get_module_from_name(name) > File "/usr/lib/python3.10/unittest/loader.py", line 377, in > _get_module_from_name > __import__(name) > File > "/<>/.pybuild/cpython3_3.10_slimit/build/slimit/__init__.py", > line 27, in > from minifier import minify > ModuleNotFoundError: No module named 'minifier' > > >
Bug#1022410: marked as done (node-eslint-plugin-html: FTBFS: make[1]: *** [debian/rules:26: override_dh_auto_test] Error 1)
Your message dated Sun, 23 Oct 2022 17:27:17 + with message-id and subject line Bug#1022410: fixed in node-eslint-plugin-html 6.2.0-3 has caused the Debian Bug report #1022410, regarding node-eslint-plugin-html: FTBFS: make[1]: *** [debian/rules:26: override_dh_auto_test] Error 1 to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 1022410: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1022410 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: node-eslint-plugin-html Version: 6.2.0-2 Severity: serious Justification: FTBFS Tags: bookworm sid ftbfs User: lu...@debian.org Usertags: ftbfs-20221023 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 '/<>' > jest --no-color --verbose > PASS src/__tests__/getFileMode.js > ✓ undefined if filename is empty (4 ms) > ✓ 'html' if filename matches an HTML extension (1 ms) > ✓ 'html' if filename matches an HTML and an XML extension > ✓ 'xml' if filename matches an XML extension > ✓ undefined if filename ends with extension without dot > ✓ works with extensions starting with a dot > ✓ works with extensions containgin a dot (1 ms) > > PASS src/__tests__/TransformableString.js > ✓ should be a function (4 ms) > toString > ✓ should return the original string if no transform are made (1 ms) > replace > ✓ should replace a slice (1 ms) > ✓ should throw if trying to replace the same thing twice (28 ms) > ✓ should replace adjacent slices > originalIndex > ✓ should return the same index if nothing changed > ✓ should throw if the index is invalid (2 ms) > ✓ should return the original index of a string with removed parts (2 ms) > ✓ should return the original index of a string with added parts (3 ms) > ✓ should return the original index of a string with added parts (2) (2 ms) > ✓ should return the last index of the last block if the index is after > the end (1 ms) > originalLocation > ✓ should return the same location if nothing changed (3 ms) > ✓ should return the original location of a string with removed parts (2 > ms) > ✓ should return the original location of a string with added parts (2 ms) > getOriginalLine > ✓ returns original lines (3 ms) > > FAIL src/__tests__/extract.js > ✕ extract simple javascript (14 ms) > ✕ extract indented javascript (2 ms) > ✕ extract javascript with first line next to the script tag (2 ms) > ✕ extract javascript with last line next to the script tag (1 ms) > ✕ extract multiple script tags (1 ms) > ✕ trim last line spaces (1 ms) > ✕ trim last line spaces ignoring CDATA (1 ms) > ✕ extract script containing 'lower than' characters correctly (#1) (1 ms) > ✕ extract empty script tag (#7) (2 ms) > ✕ extracts a script tag with type=text/javascript (2 ms) > ✕ extracts a script tag with type=text/babel (2 ms) > ✕ extracts a script tag with type=text/x-javascript (1 ms) > ✕ extracts a script tag with type=text/x-babel (1 ms) > ✕ extracts a script tag with type=application/javascript (2 ms) > ✕ extracts a script tag with type=application/babel (1 ms) > ✕ extracts a script tag with type=application/x-javascript (1 ms) > ✕ extracts a script tag with type=application/x-babel (1 ms) > ✕ collects bad indentations (2 ms) > ✕ works with crlf new lines (1 ms) > ✕ works with CDATA (1 ms) > ✕ handles the isJavaScriptMIMEType option (1 ms) > ✕ keeps empty lines after the last html tags > ✕ handles empty input > ✕ handles self closing script tags in xhtml mode (1 ms) > ✕ skips script with src attributes (1 ms) > indent option > ✕ absolute indent with spaces (2 ms) > ✕ relative indent with spaces (1 ms) > ✕ absolute indent with tabs (1 ms) > ✕ relative indent with tabs (1 ms) > > ● extract simple javascript > > expect(received).toMatchSnapshot() > > Snapshot name: `extract simple javascript 1` > > - Snapshot - 1 > + Received + 1 > > - Array [ > + [ > "var foo = 1;", > ] > > 28 | params.isJavaScriptMIMEType > 29 | ) > > 30 | expect(infos.code.map((code) => > code.toString())).toMatchSnapshot() > |
Bug#1022407: marked as done (node-url-loader: FTBFS: dh_auto_test: error: /bin/sh -ex debian/tests/pkg-js/test returned exit code 1)
Your message dated Sun, 23 Oct 2022 17:27:41 +
with message-id
and subject line Bug#1022407: fixed in node-url-loader 4.1.1-5
has caused the Debian Bug report #1022407,
regarding node-url-loader: FTBFS: dh_auto_test: error: /bin/sh -ex
debian/tests/pkg-js/test returned exit code 1
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)
--
1022407: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1022407
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: node-url-loader
Version: 4.1.1-4
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20221023 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 '/<>'
> babeljs src -d dist --ignore \"src/**/*.test.js\" --copy-files
> Successfully compiled 3 files with Babel (409ms).
> make[1]: Leaving directory '/<>'
>dh_auto_test --buildsystem=nodejs
> mkdir -p node_modules
> ln -s ../. node_modules/url-loader
> /bin/sh -ex debian/tests/pkg-js/test
> + NODE_ENV=test jest --ci test/cjs.test.js
> test/utils/normalizeFallback.test.js
> FAIL test/utils/normalizeFallback.test.js
> ● normalizeFallback › undefined
>
> expect(received).toMatchSnapshot()
>
> Snapshot name: `normalizeFallback undefined 1`
>
> - Snapshot - 2
> + Received + 2
>
> - Object {
> + {
> "loader": "file-loader",
> - "options": Object {
> + "options": {
> "limit": 8192,
> "name": "name-for-url-loader.[ext]",
> },
> }
>
> 12 | });
> 13 |
> > 14 | expect(result).toMatchSnapshot();
> |^
> 15 | });
> 16 |
> 17 | test('string', () => {
>
> at Object. (test/utils/normalizeFallback.test.js:14:20)
>
> ● normalizeFallback › string
>
> expect(received).toMatchSnapshot()
>
> Snapshot name: `normalizeFallback string 1`
>
> - Snapshot - 2
> + Received + 2
>
> - Object {
> + {
> "loader": "file-loader",
> - "options": Object {
> + "options": {
> "limit": 8192,
> "name": "name-for-url-loader.[ext]",
> },
> }
>
> 21 | });
> 22 |
> > 23 | expect(result).toMatchSnapshot();
> |^
> 24 | });
> 25 |
> 26 | test('string-with-query', () => {
>
> at Object. (test/utils/normalizeFallback.test.js:23:20)
>
> ● normalizeFallback › string-with-query
>
> expect(received).toMatchSnapshot()
>
> Snapshot name: `normalizeFallback string-with-query 1`
>
> - Snapshot - 2
> + Received + 2
>
> - Object {
> + {
> "loader": "file-loader",
> - "options": Object {
> + "options": {
> "limit": 8192,
> "name": "name-for-file-loader.[ext]",
> },
> }
>
> 30 | );
> 31 |
> > 32 | expect(result).toMatchSnapshot();
> |^
> 33 | });
> 34 |
> 35 | test('object', () => {
>
> at Object. (test/utils/normalizeFallback.test.js:32:20)
>
> ● normalizeFallback › object
>
> expect(received).toMatchSnapshot()
>
> Snapshot name: `normalizeFallback object 1`
>
> - Snapshot - 2
> + Received + 2
>
> - Object {
> + {
> "loader": "file-loader",
> - "options": Object {
> + "options": {
> "limit": 8192,
> "name": "name-for-url-loader.[ext]",
> },
> }
>
> 39 | );
> 40 |
> > 41 | expect(result).toMatchSnapshot();
> |^
> 42 | });
> 43 |
> 44 | test('object-with-options', () => {
>
> at Object. (test/utils/normalizeFallbac
Bug#1022406: marked as done (node-graphlibrary: FTBFS: make[1]: *** [debian/rules:11: override_dh_auto_build] Error 1)
Your message dated Sun, 23 Oct 2022 17:27:25 + with message-id and subject line Bug#1022406: fixed in node-graphlibrary 2.2.0+really2.1.8+repack-2 has caused the Debian Bug report #1022406, regarding node-graphlibrary: FTBFS: make[1]: *** [debian/rules:11: override_dh_auto_build] Error 1 to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 1022406: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1022406 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: node-graphlibrary Version: 2.2.0+really2.1.8+repack-1 Severity: serious Justification: FTBFS Tags: bookworm sid ftbfs User: lu...@debian.org Usertags: ftbfs-20221023 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 '/<>' > rollup -c debian/rollup.config.js lib/index.js -n graphlib -f umd -o > dist/graphlib.js > [1m[31m[!] [1mError: `moduleDirectories` option must only contain > directory names. If you want to load modules from somewhere not supported by > the default module resolution algorithm, see `modulePaths`.[22m[1m[39m[22m > [2mError: `moduleDirectories` option must only contain directory names. If > you want to load modules from somewhere not supported by the default module > resolution algorithm, see `modulePaths`. > at nodeResolve > (/usr/share/nodejs/@rollup/plugin-node-resolve/dist/cjs/index.js:980:11) > at Object. (/<>/debian/rollup.config.js:16:5) > at Module._compile (node:internal/modules/cjs/loader:1149:14) > at require.extensions. [as .js] > (/usr/share/nodejs/rollup/dist/shared/loadConfigFile.js:621:20) > at Module.load (node:internal/modules/cjs/loader:1027:32) > at Module._load (node:internal/modules/cjs/loader:868:12) > at Module.require (node:internal/modules/cjs/loader:1051:19) > at require (node:internal/modules/cjs/helpers:103:18) > at loadConfigFromBundledFile > (/usr/share/nodejs/rollup/dist/shared/loadConfigFile.js:631:42) > at getDefaultFromTranspiledConfigFile > (/usr/share/nodejs/rollup/dist/shared/loadConfigFile.js:613:12)[22m > > make[1]: *** [debian/rules:11: override_dh_auto_build] Error 1 The full build log is available from: http://qa-logs.debian.net/2022/10/23/node-graphlibrary_2.2.0+really2.1.8+repack-1_unstable.log All bugs filed during this archive rebuild are listed at: https://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=ftbfs-20221023;users=lu...@debian.org or: https://udd.debian.org/bugs/?release=na=ign=7=7=only=ftbfs-20221023=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 marking it as 'affects'-ing this package. See https://www.debian.org/Bugs/server-control#affects If you fail to reproduce this, please provide a build log and diff it with mine so that we can identify if something relevant changed in the meantime. --- End Message --- --- Begin Message --- Source: node-graphlibrary Source-Version: 2.2.0+really2.1.8+repack-2 Done: Yadd We believe that the bug you reported is fixed in the latest version of node-graphlibrary, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 1022...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Yadd (supplier of updated node-graphlibrary package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Sun, 23 Oct 2022 18:38:39 +0200 Source: node-graphlibrary Architecture: source Version: 2.2.0+really2.1.8+repack-2 Distribution: unstable Urgency: medium Maintainer: Debian Javascript Maintainers Changed-By: Yadd Closes: 1022406 Changes: node-graphlibrary (2.2.0+really2.1.8+repack-2) unstable; urgency=medium . * Team upload * Fix rollup configuration for recent @rollup/plugin-node-resolve (Closes: #1022406) Checksums-Sha1: 81fbdf3c735f9522e38126f7f1bb9db47eae75f1 2763 node-graphlibrary_2.2.0+really2.1.8+repack-2.
Bug#1022403: marked as done (node-cli-cursor: FTBFS: make[1]: *** [debian/rules:11: override_dh_auto_build] Error 1)
Your message dated Sun, 23 Oct 2022 17:27:05 + with message-id and subject line Bug#1022403: fixed in node-cli-cursor 4.0.0-2 has caused the Debian Bug report #1022403, regarding node-cli-cursor: FTBFS: make[1]: *** [debian/rules:11: override_dh_auto_build] Error 1 to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 1022403: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1022403 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: node-cli-cursor Version: 4.0.0-1 Severity: serious Justification: FTBFS Tags: bookworm sid ftbfs User: lu...@debian.org Usertags: ftbfs-20221023 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 '/<>' > START_FILE=index.js DEST_FILE=index.cjs rollup -c debian/rollup.config.js > [1m[31m[!] [1mError: `moduleDirectories` option must only contain > directory names. If you want to load modules from somewhere not supported by > the default module resolution algorithm, see `modulePaths`.[22m[1m[39m[22m > [2mError: `moduleDirectories` option must only contain directory names. If > you want to load modules from somewhere not supported by the default module > resolution algorithm, see `modulePaths`. > at Object.nodeResolve > (/usr/share/nodejs/@rollup/plugin-node-resolve/dist/cjs/index.js:980:11) > at Object. (/<>/debian/rollup.config.js:31:27) > at Module._compile (node:internal/modules/cjs/loader:1149:14) > at Object.require.extensions. [as .js] > (/usr/share/nodejs/rollup/dist/shared/loadConfigFile.js:621:20) > at Module.load (node:internal/modules/cjs/loader:1027:32) > at Function.Module._load (node:internal/modules/cjs/loader:868:12) > at Module.require (node:internal/modules/cjs/loader:1051:19) > at require (node:internal/modules/cjs/helpers:103:18) > at loadConfigFromBundledFile > (/usr/share/nodejs/rollup/dist/shared/loadConfigFile.js:631:42) > at getDefaultFromTranspiledConfigFile > (/usr/share/nodejs/rollup/dist/shared/loadConfigFile.js:613:12)[22m > > make[1]: *** [debian/rules:11: override_dh_auto_build] Error 1 The full build log is available from: http://qa-logs.debian.net/2022/10/23/node-cli-cursor_4.0.0-1_unstable.log All bugs filed during this archive rebuild are listed at: https://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=ftbfs-20221023;users=lu...@debian.org or: https://udd.debian.org/bugs/?release=na=ign=7=7=only=ftbfs-20221023=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 marking it as 'affects'-ing this package. See https://www.debian.org/Bugs/server-control#affects If you fail to reproduce this, please provide a build log and diff it with mine so that we can identify if something relevant changed in the meantime. --- End Message --- --- Begin Message --- Source: node-cli-cursor Source-Version: 4.0.0-2 Done: Yadd We believe that the bug you reported is fixed in the latest version of node-cli-cursor, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 1022...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Yadd (supplier of updated node-cli-cursor package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Sun, 23 Oct 2022 18:37:41 +0200 Source: node-cli-cursor Architecture: source Version: 4.0.0-2 Distribution: unstable Urgency: medium Maintainer: Debian Javascript Maintainers Changed-By: Yadd Closes: 1022403 Changes: node-cli-cursor (4.0.0-2) unstable; urgency=medium . * Team upload * Fix rollup configuration for recent @rollup/plugin-node-resolve (Closes: #1022403) Checksums-Sha1: e9bade517855b5416b90c0caaa142a62f3303734 2174 node-cli-cursor_4.0.0-2.dsc 15c0a4362127a006689f45e23bf94b439d3a0c2e 4332 node-cli-cursor_4.0.0-2.debian.tar.xz Checksums-Sha256: 7b83f71b79e2ec
Bug#1022396: marked as done (node-webpack-sources: FTBFS: dh_auto_test: error: /bin/sh -ex debian/tests/pkg-js/test returned exit code 1)
Your message dated Sun, 23 Oct 2022 17:27:48 +
with message-id
and subject line Bug#1022396: fixed in node-webpack-sources 3.2.3+~3.2.0-2
has caused the Debian Bug report #1022396,
regarding node-webpack-sources: FTBFS: dh_auto_test: error: /bin/sh -ex
debian/tests/pkg-js/test returned exit code 1
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)
--
1022396: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1022396
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: node-webpack-sources
Version: 3.2.3+~3.2.0-1
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20221023 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
>dh_auto_configure --buildsystem=nodejs
> Link node_modules/@types/webpack-sources -> ../../types-webpack-sources
>dh_auto_build --buildsystem=nodejs
> No build command found, searching known files
> No build command found, searching known files
>dh_auto_test --buildsystem=nodejs
> ln -s ../debian/tests/test_modules/sourcemap-validator
> node_modules/sourcemap-validator
> ln -s ../. node_modules/webpack-sources
> /bin/sh -ex debian/tests/pkg-js/test
> + jest --ci -u --testPathIgnorePatterns test/Fuzzy.js
> PASS test/helpers.js
> PASS test/PrefixSource.js
> PASS test/OriginalSource.js
> PASS test/CachedSource.js
> FAIL test/ConcatSource.js
> ● Test suite failed to run
>
> Jest: Couldn't locate all inline snapshots.
>
> 225 | });
> 226 | if (remainingSnapshots.size) {
> > 227 | throw new Error("Jest: Couldn't locate all inline
> snapshots.");
> | ^
> 228 | }
> 229 | };
> 230 | const runPrettier = (prettier, sourceFilePath,
> sourceFileWithSnapshots, snapshotMatcherNames) => {
>
> at traverseAst
> (../../../usr/share/nodejs/jest-snapshot/build/InlineSnapshots.js:227:11)
>
> PASS test/CompatSource.js
> PASS test/package-entry.js
> PASS test/SizeOnlySource.js
> FAIL test/SourceMapSource.js
> ● Test suite failed to run
>
> Jest: Couldn't locate all inline snapshots.
>
> 225 | });
> 226 | if (remainingSnapshots.size) {
> > 227 | throw new Error("Jest: Couldn't locate all inline
> snapshots.");
> | ^
> 228 | }
> 229 | };
> 230 | const runPrettier = (prettier, sourceFilePath,
> sourceFileWithSnapshots, snapshotMatcherNames) => {
>
> at traverseAst
> (../../../usr/share/nodejs/jest-snapshot/build/InlineSnapshots.js:227:11)
>
> FAIL test/ReplaceSource.js
> ● Test suite failed to run
>
> Jest: Couldn't locate all inline snapshots.
>
> 225 | });
> 226 | if (remainingSnapshots.size) {
> > 227 | throw new Error("Jest: Couldn't locate all inline
> snapshots.");
> | ^
> 228 | }
> 229 | };
> 230 | const runPrettier = (prettier, sourceFilePath,
> sourceFileWithSnapshots, snapshotMatcherNames) => {
>
> at traverseAst
> (../../../usr/share/nodejs/jest-snapshot/build/InlineSnapshots.js:227:11)
>
> Test Suites: 3 failed, 7 passed, 10 total
> Tests: 36 passed, 36 total
> Snapshots: 0 total
> Time:2.764 s
> Ran all test suites.
> Force exiting Jest: Have you considered using `--detectOpenHandles` to detect
> async operations that kept running after all tests finished?
> dh_auto_test: error: /bin/sh -ex debian/tests/pkg-js/test returned exit code 1
The full build log is available from:
http://qa-logs.debian.net/2022/10/23/node-webpack-sources_3.2.3+~3.2.0-1_unstable.log
All bugs filed during this archive rebuild are listed at:
https://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=ftbfs-20221023;users=lu...@debian.org
or:
https://udd.debian.org/bugs/?release=na=ign=7=7=only=ftbfs-20221023=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 marking it as 'affects'-ing
this package. See https://www.debian.org/Bu
Bug#1022367: marked as done (node-deep-for-each: FTBFS: dh_auto_test: error: /bin/sh -ex debian/tests/pkg-js/test returned exit code 1)
Your message dated Sun, 23 Oct 2022 17:27:11 +
with message-id
and subject line Bug#1022367: fixed in node-deep-for-each 3.0.0-5
has caused the Debian Bug report #1022367,
regarding node-deep-for-each: FTBFS: dh_auto_test: error: /bin/sh -ex
debian/tests/pkg-js/test returned exit code 1
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)
--
1022367: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1022367
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: node-deep-for-each
Version: 3.0.0-4
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20221023 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 '/<>'
> BABEL_ENV=commonjs babeljs-7 --presets '@babel/preset-env' --plugins
> 'babel-plugin-add-module-exports' src -d lib
> Successfully compiled 1 file with Babel (565ms).
> BABEL_ENV=es babeljs-7 src -d es
> Successfully compiled 1 file with Babel (354ms).
> make[1]: Leaving directory '/<>'
>dh_auto_test --buildsystem=nodejs
> mkdir -p node_modules
> ln -s ../. node_modules/deep-for-each
> /bin/sh -ex debian/tests/pkg-js/test
> + jest --ci
> FAIL test/test.js
> ✓ should not call fn on primitive input (3 ms)
> ✕ should iterate object entries recursively (11 ms)
> ✕ should iterate arrays recursively (2 ms)
> ✕ should iterate array/objects recursively (4 ms)
> ✕ should use the up to date value (in case the forEach callback modified
> it) (2 ms)
> ✓ should make `this` equal to the subject on the iterator (1 ms)
>
> ● should iterate object entries recursively
>
> expect(received).toMatchSnapshot()
>
> Snapshot name: `should iterate object entries recursively 1`
>
> - Snapshot - 3
> + Received + 3
>
> - Array [
> - Array [
> + [
> + [
> null,
> "foo",
> - Object {
> + {
> "foo": null,
> },
> "foo",
> ],
> ]
>
>6 |
>7 | function takeSnapshot() {
> > 8 | expect(iterator.mock.calls).toMatchSnapshot();
> | ^
>9 | jest.resetAllMocks();
> 10 | }
> 11 |
>
> at takeSnapshot (test/test.js:8:33)
> at Object. (test/test.js:31:5)
>
> ● should iterate object entries recursively
>
> expect(received).toMatchSnapshot()
>
> Snapshot name: `should iterate object entries recursively 2`
>
> - Snapshot - 3
> + Received + 3
>
> - Array [
> - Array [
> + [
> + [
> undefined,
> "foo",
> - Object {
> + {
> "foo": undefined,
> },
> "foo",
> ],
> ]
>
>6 |
>7 | function takeSnapshot() {
> > 8 | expect(iterator.mock.calls).toMatchSnapshot();
> | ^
>9 | jest.resetAllMocks();
> 10 | }
> 11 |
>
> at takeSnapshot (test/test.js:8:33)
> at Object. (test/test.js:34:5)
>
> ● should iterate object entries recursively
>
> expect(received).toMatchSnapshot()
>
> Snapshot name: `should iterate object entries recursively 3`
>
> - Snapshot - 7
> + Received + 7
>
> - Array [
> - Array [
> - Object {
> + [
> + [
> + {
> "bar": null,
> },
> "foo",
> - Object {
> - "foo": Object {
> + {
> + "foo": {
> "bar": null,
> },
> },
> "foo",
> ],
> - Array [
> + [
> null,
> "bar",
> - Object {
> + {
> "bar": null,
> },
> "foo.bar",
> ],
> ]
>
>6 |
>7 | function takeSnapshot() {
> > 8 | expect(iterator.mock.calls).toMatchSnapshot();
>
Bug#1022342: marked as done (node-zrender: FTBFS: make: *** [debian/rules:8: binary] Error 25)
Your message dated Sun, 23 Oct 2022 17:27:57 +
with message-id
and subject line Bug#1022342: fixed in node-zrender 5.4.0+dfsg-2
has caused the Debian Bug report #1022342,
regarding node-zrender: FTBFS: make: *** [debian/rules:8: binary] Error 25
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)
--
1022342: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1022342
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: node-zrender
Version: 5.4.0+dfsg-1
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20221023 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
>dh_auto_configure --buildsystem=nodejs
> Link ./node_modules/ts-jest -> /usr/share/nodejs/ts-jest
> Link ./node_modules/tslib -> /usr/share/nodejs/tslib
> Link ./node_modules/@types/istanbul-lib-coverage ->
> /usr/share/nodejs/@types/istanbul-lib-coverage
> Link ./node_modules/@types/istanbul-lib-report ->
> /usr/share/nodejs/@types/istanbul-lib-report
> Link ./node_modules/@types/jest -> /usr/share/nodejs/@types/jest
> Link ./node_modules/@types/node -> /usr/share/nodejs/@types/node
>dh_auto_build --buildsystem=nodejs
> Found debian/nodejs/./build
> cd ./. && sh -ex debian/nodejs/./build
> + set -e
> + node build/build.js
> [1/1]: index.ts
> [2/2]: src/all.ts
> [3/6]: src/zrender.ts
> [4/15]: src/canvas/Painter.ts
> [5/20]: src/export.ts
> [6/26]: src/svg/Painter.ts
> [7/27]: src/core/env.ts
> [8/28]: src/core/util.ts
> [9/29]: src/Handler.ts
> [10/30]: src/Storage.ts
> [11/31]: src/animation/Animation.ts
> [12/32]: src/dom/HandlerProxy.ts
> [13/33]: src/tool/color.ts
> [14/34]: src/config.ts
> [15/35]: src/graphic/Group.ts
> [16/36]: src/canvas/Layer.ts
> [17/37]: src/canvas/graphic.ts
> [18/38]: src/graphic/constants.ts
> [19/39]: src/animation/requestAnimationFrame.ts
> [20/40]: src/canvas/helper.ts
> [21/41]: src/core/matrix.ts
> [22/42]: src/core/vector.ts
> [23/43]: src/tool/path.ts
> [24/44]: src/tool/parseSVG.ts
>
> /usr/share/nodejs/rollup/dist/shared/rollup.js:198
> base = Object.assign(new Error(base.message), base);
> ^
>
> Error: [96msrc/tool/morphPath.ts[0m:[93m348[0m:[93m51[0m -
> [91merror[0m[90m TS2469: [0mThe '+' operator cannot be applied to type
> 'symbol'.
>
> [7m348[0m const savedMethodName = SAVED_METHOD_PREFIX + methodName;
> [7m [0m [91m
> ~~[0m
> [96msrc/tool/morphPath.ts[0m:[93m376[0m:[93m51[0m - [91merror[0m[90m
> TS2469: [0mThe '+' operator cannot be applied to type 'symbol'.
>
> [7m376[0m const savedMethodName = SAVED_METHOD_PREFIX + methodName;
> [7m [0m [91m
> ~~[0m
>
> at error (/usr/share/nodejs/rollup/dist/shared/rollup.js:198:30)
> at throwPluginError
> (/usr/share/nodejs/rollup/dist/shared/rollup.js:21696:12)
> at Object.error (/usr/share/nodejs/rollup/dist/shared/rollup.js:22651:20)
> at Object.error (/usr/share/nodejs/rollup/dist/shared/rollup.js:21873:42)
> at RollupContext.error
> (/usr/share/nodejs/rollup-plugin-typescript2/dist/rollup-plugin-typescript2.cjs.js:876:30)
> at
> /usr/share/nodejs/rollup-plugin-typescript2/dist/rollup-plugin-typescript2.cjs.js:1374:19
> at Array.forEach ()
> at printDiagnostics
> (/usr/share/nodejs/rollup-plugin-typescript2/dist/rollup-plugin-typescript2.cjs.js:1350:17)
> at Object.transform
> (/usr/share/nodejs/rollup-plugin-typescript2/dist/rollup-plugin-typescript2.cjs.js:1636:17)
> at /usr/share/nodejs/rollup/dist/shared/rollup.js:22858:40 {
> id: '/<>/src/tool/morphPath.ts',
> hook: 'transform',
> code: 'PLUGIN_ERROR',
> plugin: 'rpt2',
> watchFiles: [
> '/<>/index.ts',
> '/<>/src/all.ts',
> '/<>/src/zrender.ts',
> '/<>/src/export.ts',
> '/<>/src/canvas/Painter.ts',
> '/<>/src/svg/Painter.ts',
> '/<>/src/core/env.ts',
> '/<>/src/core/util.ts',
> '/<>/src/Handler.ts',
> '/&l
Bug#1022365: confirmed
Weird, tests pass for me locally. Will look into it.
Bug#1022364: qutebrowser: FTBFS: dh_usrlocal: error: debian/qutebrowser/usr/local/bin/qutebrowser is not a directory
Control: tag -1 + confirmed Hi Lucas, Lucas Nussbaum wrote: > During a rebuild of all packages in sid, your package failed to build > on amd64. Thanks for the bug report. Can reproduce it here. > Relevant part (hopefully): […] > > I: dh_python3 pydist:302: Cannot find package that provides dataclasses. > > Please add package that provides it to Build-Depends or add "dataclasses > > python3-dataclasses" line to debian/py3dist-overrides or add proper > > dependency to Depends by hand and ignore this info. > > I: dh_python3 pydist:302: Cannot find package that provides dataclasses. > > Please add package that provides it to Build-Depends or add "dataclasses > > python3-dataclasses" line to debian/py3dist-overrides or add proper > > dependency to Depends by hand and ignore this info. I first thought that this is the relevant hint. But it also showed up in previous successful builds, e.g. 2.5.2-1, so it was a red herring: https://buildd.debian.org/status/fetch.php?pkg=qutebrowser=all=2.5.2-1=1655941699=0 > >dh_usrlocal -O--buildsystem=pybuild -O--link-doc=qutebrowser > > dh_usrlocal: error: debian/qutebrowser/usr/local/bin/qutebrowser is not a > > directory This is clearly the one which makes the build stop at the end. Looks like something suddenly installs the qutebrowser binary _also_ into /usr/local/bin/. I so far just have no idea yet what or why. Actually the following override in debian/rules would fix it and the resulting .deb has no debdiff to 2.5.2-1 as in unstable/testing, but I'd first like to understand what actually goes wrong instead of fixing symptoms: override_dh_usrlocal: rm -rvf debian/qutebrowser/usr/local/ Regards, Axel -- ,''`. | Axel Beckert , https://people.debian.org/~abe/ : :' : | Debian Developer, ftp.ch.debian.org Admin `. `' | 4096R: 2517 B724 C5F6 CA99 5329 6E61 2FF9 CD59 6126 16B5 `-| 1024D: F067 EA27 26B9 C3FC 1486 202E C09E 1D89 9593 0EDE
Processed: Re: Bug#1022364: qutebrowser: FTBFS: dh_usrlocal: error: debian/qutebrowser/usr/local/bin/qutebrowser is not a directory
Processing control commands: > tag -1 + confirmed Bug #1022364 [src:qutebrowser] qutebrowser: FTBFS: dh_usrlocal: error: debian/qutebrowser/usr/local/bin/qutebrowser is not a directory Added tag(s) confirmed. -- 1022364: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1022364 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1022042: kernel 5.10.149-2 does not help
On zondag 23 oktober 2022 19:01:06 CEST Andreas Wirooks wrote: > Am 23.10.22 um 14:27 schrieb Diederik de Haas: > > On zondag 23 oktober 2022 14:10:11 CEST Andreas Wirooks wrote: > >>> You both have kernel parameters like these. Can you explain why? > >>> I have an AMD GPU on a machine and I have never set parameters like > >>> these. > >> > >> These are parameters for Southern Islands (si) and Sea Islands (cik) AMD > >> GPUs: > > I see you're already 'in' > > https://gitlab.freedesktop.org/drm/amd/-/issues/2216 and that seems like > > an important distinction to mention (to me). > > All the other cases for where this issue was fixed, seem to have (much) > > newer generation of GPUs. > > I will write an update in the drm issue too. > > I tested the old radeon driver by removing all si/cki options with > kernel 5.10.149-2 and it boots ok and uses drm 2 instead drm 3. Excellent. I saw you already added that info to the upstream bug :-) > The debian 11/bullseye backport kernel 5.19.11-1~bpo11+1 boots ok with > the amdgpu driver too using drm 3. Alex Deucher (@agd5f) indicated the problem was caused by an incorrect backport to 5.10 and maybe the 2 identified ones aren't the only ones. On zondag 23 oktober 2022 17:44:17 CEST inasprec...@disroot.org wrote: > I tried booting 5.10.0-19 with an empty command line string and it > worked > > I don’t know if this an entirely separate issue, however. I can > file a separate bug if you think it is appropriate. Given that switching to the radeon driver fixed the issue for you both, then I guess it's the same issue. So let's keep it to this bug, at least for now. signature.asc Description: This is a digitally signed message part.
Bug#1022298: marked as done (gpa: FTBFS: configure: error: You need libgpg-error to build this program.)
Your message dated Sun, 23 Oct 2022 17:16:46 + with message-id and subject line Bug#1022298: fixed in gpa 0.10.0-4 has caused the Debian Bug report #1022298, regarding gpa: FTBFS: configure: error: You need libgpg-error to build this program. to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 1022298: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1022298 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: gpa Version: 0.10.0-3 Severity: serious Justification: FTBFS Tags: bookworm sid ftbfs User: lu...@debian.org Usertags: ftbfs-20221023 ftbfs-bookworm Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > *** You need libgpg-error to build this program. > ** This library is for example available at > *** ftp://ftp.gnupg.org/gcrypt/libgpg-error > *** (at least version 1.27 is required.) > *** > configure: error: > *** > *** Required libraries not found. Please consult the above messages > *** and install them before running configure again. > *** > tail -v -n \+0 config.log The full build log is available from: http://qa-logs.debian.net/2022/10/23/gpa_0.10.0-3_unstable.log All bugs filed during this archive rebuild are listed at: https://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=ftbfs-20221023;users=lu...@debian.org or: https://udd.debian.org/bugs/?release=na=ign=7=7=only=ftbfs-20221023=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 marking it as 'affects'-ing this package. See https://www.debian.org/Bugs/server-control#affects If you fail to reproduce this, please provide a build log and diff it with mine so that we can identify if something relevant changed in the meantime. --- End Message --- --- Begin Message --- Source: gpa Source-Version: 0.10.0-4 Done: Andreas Rönnquist We believe that the bug you reported is fixed in the latest version of gpa, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 1022...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Andreas Rönnquist (supplier of updated gpa package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Sun, 23 Oct 2022 18:11:05 +0200 Source: gpa Architecture: source Version: 0.10.0-4 Distribution: unstable Urgency: medium Maintainer: Debian GnuPG-Maintainers Changed-By: Andreas Rönnquist Closes: 1022298 Changes: gpa (0.10.0-4) unstable; urgency=medium . [ Andreas Rönnquist ] * Add patch cherry-picked from upstream to build with gpgrt-config instead of gpg-error-config (Closes: #1022298) * Upgrade to Standards-Version 4.6.1.0 (No changes required) * Add repository information to metadata * Use debhelper compat 13 * Update debian packaging copyright years . [ Debian Janitor ] * Remove constraints unnecessary since buster (oldstable) Checksums-Sha1: 1bbf97506823ce09bca27754efce20450c0e 2033 gpa_0.10.0-4.dsc c756e85272759fbdfcd76150daa318a07de84d61 10428 gpa_0.10.0-4.debian.tar.xz 464d6b36bac0ac0e7377f7a1ced9ddfa1383aaa4 13680 gpa_0.10.0-4_source.buildinfo Checksums-Sha256: 31955164180af269c50c80ebd928a5411b3ec26ea953850e2bf53653d9a24119 2033 gpa_0.10.0-4.dsc 871009e088be3ca02e3dc8bbead1dfd0d0b5ab89570e4b20f86bffe3d6e4a9ce 10428 gpa_0.10.0-4.debian.tar.xz 51a5ec81b7a5ac085f8e9d9c9e4810b8f25bb377da8783ea03fd64ece4c090c6 13680 gpa_0.10.0-4_source.buildinfo Files: 631692b78c794c1e6beb3df675b12181 2033 utils optional gpa_0.10.0-4.dsc 66383772a3118683a1e32b6539ecf96f 10428 utils optional gpa_0.10.0-4.debian.tar.xz d41755a3d05e0668877429aabc5c0225 13680 utils optional gpa_0.10.0-4_source.buildinfo -BEGIN PGP SIGNATURE- iQJFBAEBCAAvFiEE2zBuSxD/2Y7021XXGUtjGrLaKIgFAmNVbXIRHGd1c25hbkBn dXNuYW4uc2UACgkQGUtjGrLaKIjbsg//ffz2OyqePLYMr5NKqoualF8szZpZUNd0 eRXcHh2pFT9Xpwlg2R34DuduCkTYQzUtZwc6SclLnZrumArFpXZBXsNxYzuQrUYu ty8MzmBHppMJZNaxZkZoLLtSHriPFfzJOMd3A9nqjzjsejH+MIQo1Ev+Fs3fZnab MlL42a
Bug#1022253: swi-prolog breaks logol autopkgtest on s390x
Hi Paul, Вс 23 окт 2022 @ 10:10 Paul Gevers : > Hi Lev, > > On 23-10-2022 09:40, Lev Lamberov wrote: >> I'm not sure it is the solution, it needs testing. The change in >> swi-prolog concerns pre-compiled prolog source code, when there is no >> pre-complied prolog code rebuilt is not needed. SWI-Prolog supports >> three different kinds of pre-compilation, at least one of them was >> affected and another was not. The mentioned endiannes bug can be found >> in BTS, #1006818 [bts]. > > I just ran the autopkgtest with a rebuild logol on s390x, see below. > Does that help? > > @logol maintainers, those ERRORs look scary if the test passes with it. > Is that just noise, or are real problems ignored? Given the answer from Étienne looks like it *is* the solution. Thanks for your work on it! Cheers! Lev
Processed: Re: Bug#1022286: gnome-shell-extension-manager: FTBFS: ModuleNotFoundError: No module named 'gi'
Processing control commands: > reassign -1 blueprint-compiler 0.4.0-3 Bug #1022286 [src:gnome-shell-extension-manager] gnome-shell-extension-manager: FTBFS: ModuleNotFoundError: No module named 'gi' Bug reassigned from package 'src:gnome-shell-extension-manager' to 'blueprint-compiler'. No longer marked as found in versions gnome-shell-extension-manager/0.2.3-2. Ignoring request to alter fixed versions of bug #1022286 to the same values previously set Bug #1022286 [blueprint-compiler] gnome-shell-extension-manager: FTBFS: ModuleNotFoundError: No module named 'gi' Marked as found in versions blueprint-compiler/0.4.0-3. > affects -1 + src:gnome-shell-extension-manager Bug #1022286 [blueprint-compiler] gnome-shell-extension-manager: FTBFS: ModuleNotFoundError: No module named 'gi' Added indication that 1022286 affects src:gnome-shell-extension-manager -- 1022286: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1022286 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1022286: gnome-shell-extension-manager: FTBFS: ModuleNotFoundError: No module named 'gi'
Control: reassign -1 blueprint-compiler 0.4.0-3 Control: affects -1 + src:gnome-shell-extension-manager On Sun, 23 Oct 2022 at 14:38:05 +0200, Lucas Nussbaum wrote: > > Program blueprint-compiler found: YES (/usr/bin/blueprint-compiler) ... > > Traceback (most recent call last): > > File "/usr/bin/blueprint-compiler", line 37, in > > from blueprintcompiler import main ... > > File "/usr/lib/python3/dist-packages/blueprintcompiler/gir.py", line 24, > > in > > import gi # type: ignore > > ModuleNotFoundError: No module named 'gi' This looks like a missing dependency in blueprint-compiler. >From a brief look at the package, it seems like python3-gi might have been added to debian/control, instead of adding it to debian/control.in and then regenerating debian/control with `make -f debian/rules clean`. This effectively results in the change being reverted whenever the package is rebuilt. smcv
Bug#1022042: kernel 5.10.149-2 does not help
Am 23.10.22 um 14:27 schrieb Diederik de Haas: On zondag 23 oktober 2022 14:10:11 CEST Andreas Wirooks wrote: You both have kernel parameters like these. Can you explain why? I have an AMD GPU on a machine and I have never set parameters like these. These are parameters for Southern Islands (si) and Sea Islands (cik) AMD GPUs: I see you're already 'in' https://gitlab.freedesktop.org/drm/amd/-/issues/2216 and that seems like an important distinction to mention (to me). All the other cases for where this issue was fixed, seem to have (much) newer generation of GPUs. I will write an update in the drm issue too. I tested the old radeon driver by removing all si/cki options with kernel 5.10.149-2 and it boots ok and uses drm 2 instead drm 3. But of course i added these options again and rebooted with 5.10.140-1 because of Vulkan support in the amdgpu driver using drm 3. The debian 11/bullseye backport kernel 5.19.11-1~bpo11+1 boots ok with the amdgpu driver too using drm 3.
Bug#1022396: marked as pending in node-webpack-sources
Control: tag -1 pending Hello, Bug #1022396 in node-webpack-sources reported by you has been fixed in the Git repository and is awaiting an upload. You can see the commit message below and you can check the diff of the fix at: https://salsa.debian.org/js-team/node-webpack-sources/-/commit/d9422fb8e033aadcdb259d85f7698c320d143704 Add patch for jest >= 29 Closes: #1022396 (this message was generated automatically) -- Greetings https://bugs.debian.org/1022396
Processed: Bug#1022396 marked as pending in node-webpack-sources
Processing control commands: > tag -1 pending Bug #1022396 [src:node-webpack-sources] node-webpack-sources: FTBFS: dh_auto_test: error: /bin/sh -ex debian/tests/pkg-js/test returned exit code 1 Added tag(s) pending. -- 1022396: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1022396 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1022289: libassuan: FTBFS: configure: error: libgpg-error was not found
On 2022-10-23 Lucas Nussbaum wrote: > Source: libassuan > Version: 2.5.5-4 > Severity: serious > Justification: FTBFS > Tags: bookworm sid ftbfs > User: lu...@debian.org > Usertags: ftbfs-20221023 ftbfs-bookworm > Hi, > During a rebuild of all packages in sid, your package failed to build > on amd64. > Relevant part (hopefully): > > ../configure: line 15745: /usr/i686-w64-mingw32/bin/gpg-error-config: No > > such file or directory [...] Hello, Caused by new gpg-error dropping gpg-error-config, this works for me: --- libassuan-2.5.5/debian/rules2022-04-30 17:47:12.0 +0200 +++ patched/libassuan-2.5.5.patched/debian/rules2022-10-23 18:23:40.505849321 +0200 @@ -27,7 +27,6 @@ for cpu in i686 x86_64; do \ mkdir -p build-$$cpu-w64-mingw32 && \ cd build-$$cpu-w64-mingw32 && $(WIN_FLAGS) ../configure \ - --with-libgpg-error-prefix=/usr/$$cpu-w64-mingw32 \ --prefix=/usr/$$cpu-w64-mingw32 \ --enable-static \ --host $$cpu-w64-mingw32 && \ and a successful build with gpg-error 1.46 and a patched build with 1.47 look almost identical except for configure messages changing: -checking for gpg-error-config... /usr/x86_64-w64-mingw32/bin/gpg-error-config +checking for gpg-error-config... no checking for gpgrt-config... /usr/bin/gpgrt-config configure: Use gpgrt-config with /usr/x86_64-w64-mingw32/lib as gpg-error-config -checking for GPG Error - version >= 1.17... yes (1.45) +checking for GPG Error - version >= 1.17... yes (1.46) cu Andreas -- `What a good friend you are to him, Dr. Maturin. His other friends are so grateful to you.' `I sew his ears on from time to time, sure'
Bug#1009031: possible workaround for libgit-raw-perl FTBFS with libgit2 1.3.0
Control: tag -1 + fixed-upstream On Sun, 23 Oct 2022 17:17:22 +0200, gregor herrmann wrote: > On Sat, 22 Oct 2022 18:48:31 +0200, Étienne Mollier wrote: > > > Taking the approach of refreshing the test suite to match the > > output produced by the new libgit2 seems to do the job to > > address the test suite failure. I also checked this has no > > adverse effects on reverse dependencies. Variations between the > > reference and the new update are also minimal and seem to make > > sense. > > Interesting finding! > The last time I looked I had the impression that this needs more > changes / changes in the actual code but obviously I was wrong. And now this is apparently fixed upstream in the 0.89 release: https://github.com/jacquesg/p5-Git-Raw/issues/222#issuecomment-1288150066 Cheers, gregor -- .''`. https://info.comodo.priv.at -- Debian Developer https://www.debian.org : :' : OpenPGP fingerprint D1E1 316E 93A7 60A8 104D 85FA BB3A 6801 8649 AA06 `. `' Member VIBE!AT & SPI Inc. -- Supporter Free Software Foundation Europe `- signature.asc Description: Digital Signature
Processed: Re: Bug#1009031: possible workaround for libgit-raw-perl FTBFS with libgit2 1.3.0
Processing control commands: > tag -1 + fixed-upstream Bug #1009031 [libgit-raw-perl] libgit-raw-perl: FTBFS with libgit2 1.3.0 Added tag(s) fixed-upstream. -- 1009031: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1009031 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1022410: marked as pending in node-eslint-plugin-html
Control: tag -1 pending Hello, Bug #1022410 in node-eslint-plugin-html reported by you has been fixed in the Git repository and is awaiting an upload. You can see the commit message below and you can check the diff of the fix at: https://salsa.debian.org/js-team/node-eslint-plugin-html/-/commit/5c02ee7f8eb34b771bcf3de1dbaea267e8378b8d Add fix for jest >= 29 Closes: #1022410 (this message was generated automatically) -- Greetings https://bugs.debian.org/1022410
Processed: Bug#1022410 marked as pending in node-eslint-plugin-html
Processing control commands: > tag -1 pending Bug #1022410 [src:node-eslint-plugin-html] node-eslint-plugin-html: FTBFS: make[1]: *** [debian/rules:26: override_dh_auto_test] Error 1 Added tag(s) pending. -- 1022410: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1022410 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: Bug#1022367 marked as pending in node-deep-for-each
Processing control commands: > tag -1 pending Bug #1022367 [src:node-deep-for-each] node-deep-for-each: FTBFS: dh_auto_test: error: /bin/sh -ex debian/tests/pkg-js/test returned exit code 1 Added tag(s) pending. -- 1022367: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1022367 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: Bug#1020046 marked as pending in slimit
Processing control commands: > tag -1 pending Bug #1020046 [src:slimit] slimit: FTBFS: ModuleNotFoundError: No module named 'minifier' Ignoring request to alter tags of bug #1020046 to the same tags previously set -- 1020046: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1020046 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1022367: marked as pending in node-deep-for-each
Control: tag -1 pending Hello, Bug #1022367 in node-deep-for-each reported by you has been fixed in the Git repository and is awaiting an upload. You can see the commit message below and you can check the diff of the fix at: https://salsa.debian.org/js-team/node-deep-for-each/-/commit/a42bdf38141d183537741d694500cb05af301973 Add fix for jest >= 29 Closes: #1022367 (this message was generated automatically) -- Greetings https://bugs.debian.org/1022367
Bug#1020046: marked as pending in slimit
Control: tag -1 pending Hello, Bug #1020046 in slimit reported by you has been fixed in the Git repository and is awaiting an upload. You can see the commit message below and you can check the diff of the fix at: https://salsa.debian.org/python-team/packages/slimit/-/commit/6ca361ea3686553d7f20220356c67308901dd7b2 Replace python3 patch with upstream's patch (Closes: #1020046) (this message was generated automatically) -- Greetings https://bugs.debian.org/1020046
Bug#1014966: onionshare: CVE-2021-41867 CVE-2021-41868 CVE-2022-21688 CVE-2022-21689 CVE-2022-21690 CVE-2022-21691 CVE-2022-21692 CVE-2022-21693 CVE-2022-21694 CVE-2022-21695 CVE-2022-21696
Hi, Le 22/10/2022 à 15:01, Salvatore Bonaccorso a écrit : Thanks for the quick reply! (much appreciated). I think it would be good to get a confirmation from upstream and if possible to have those advisories updates. E.g. https://github.com/onionshare/onionshare/security/advisories/GHSA-x7wr-283h-5h2v while mentioning "affected versions < 2.4" the patched version remains "none". this might be that the < 2.4 just reflects the point in time when the advisory was filled. OTOH you have arguments with the v2.5 release information that they might all be fixed. To be on safe side, explicitly confirming by upstream would be great. Agreed. And asked upstream: https://github.com/onionshare/onionshare/issues/1633. Cheers, -- nodens
Bug#1022316: marked as done (rr: FTBFS: ethtool.h:778:17: error: flexible array member ‘ethtool_sset_info::data’ not at end of ‘struct rr::get_ethtool_gstrings_arch(RecordTask*)::SingleString
Your message dated Sun, 23 Oct 2022 16:13:55 +
with message-id
and subject line Bug#1022316: fixed in rr 5.6.0-3
has caused the Debian Bug report #1022316,
regarding rr: FTBFS: ethtool.h:778:17: error: flexible array member
‘ethtool_sset_info::data’ not at end of ‘struct
rr::get_ethtool_gstrings_arch(RecordTask*)::SingleStringSet’
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)
--
1022316: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1022316
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: rr
Version: 5.6.0-2
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20221023 ftbfs-bookworm
Hi,
During a rebuild of all packages in sid, your package failed to build
on amd64.
Relevant part (hopefully):
> /usr/bin/c++ -DEXECINFO_H=1 -DFANOTIFY_H=1 -DMQUEUE_H=1 -DPROC_SERVICE_H=1
> -DRR_VERSION=\"5.6.0\" -Drr_EXPORTS -I/<>/include
> -I/<>/third-party/proc-service
> -I/<>/third-party/brotli/include -I/<>/build -g -O2
> -ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat
> -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -D__USE_LARGEFILE64
> -pthread -msse2 -D__MMX__ -D__SSE__ -D__SSE2__
> -fmacro-prefix-map=/<>/= -D__STDC_LIMIT_MACROS
> -D__STDC_FORMAT_MACROS -std=c++14 -pthread -Wall -Wextra -UDEBUG -DNDEBUG
> -MD -MT CMakeFiles/rr.dir/src/replay_syscall.cc.o -MF
> CMakeFiles/rr.dir/src/replay_syscall.cc.o.d -o
> CMakeFiles/rr.dir/src/replay_syscall.cc.o -c
> /<>/src/replay_syscall.cc
> In file included from /<>/src/record_syscall.cc:12:
> /<>/src/record_syscall.cc: In instantiation of ‘struct
> rr::get_ethtool_gstrings_arch(RecordTask*)::SingleStringSet’:
> /<>/src/record_syscall.cc:1456:3: required from ‘void
> rr::get_ethtool_gstrings_arch(RecordTask*) [with Arch = X86Arch]’
> /<>/src/record_syscall.cc:1486:3: required from here
> /usr/include/linux/ethtool.h:778:17: error: flexible array member
> ‘ethtool_sset_info::data’ not at end of ‘struct
> rr::get_ethtool_gstrings_arch(RecordTask*)::SingleStringSet’
> 778 | __u32 data[];
> | ^~~~
> /<>/src/record_syscall.cc:1455:14: note: next member ‘uint32_t
> rr::get_ethtool_gstrings_arch(RecordTask*)::SingleStringSet::data’
> declared here
> 1455 | uint32_t data;
> | ^~~~
> /<>/src/record_syscall.cc:1453:10: note: in the definition of
> ‘struct rr::get_ethtool_gstrings_arch(RecordTask*)::SingleStringSet’
> 1453 | struct SingleStringSet {
> | ^~~
> /<>/src/record_syscall.cc: In instantiation of ‘struct
> rr::get_ethtool_gstrings_arch(RecordTask*)::SingleStringSet’:
> /<>/src/record_syscall.cc:1456:3: required from ‘void
> rr::get_ethtool_gstrings_arch(RecordTask*) [with Arch = X64Arch]’
> /<>/src/record_syscall.cc:1486:3: required from here
> /usr/include/linux/ethtool.h:778:17: error: flexible array member
> ‘ethtool_sset_info::data’ not at end of ‘struct
> rr::get_ethtool_gstrings_arch(RecordTask*)::SingleStringSet’
> 778 | __u32 data[];
> | ^~~~
> /<>/src/record_syscall.cc:1455:14: note: next member ‘uint32_t
> rr::get_ethtool_gstrings_arch(RecordTask*)::SingleStringSet::data’
> declared here
> 1455 | uint32_t data;
> | ^~~~
> /<>/src/record_syscall.cc:1453:10: note: in the definition of
> ‘struct rr::get_ethtool_gstrings_arch(RecordTask*)::SingleStringSet’
> 1453 | struct SingleStringSet {
> | ^~~
> /<>/src/record_syscall.cc: In instantiation of ‘struct
> rr::get_ethtool_gstrings_arch(RecordTask*)::SingleStringSet’:
> /<>/src/record_syscall.cc:1456:3: required from ‘void
> rr::get_ethtool_gstrings_arch(RecordTask*) [with Arch = ARM64Arch]’
> /<>/src/record_syscall.cc:1486:3: required from here
> /usr/include/linux/ethtool.h:778:17: error: flexible array member
> ‘ethtool_sset_info::data’ not at end of ‘struct
> rr::get_ethtool_gstrings_arch(RecordTask*)::SingleStringSet’
> 778 | __u32 data[];
> | ^~~~
> /<>/src/record_syscall.cc:1455:14: note: next member ‘uint32_t
> rr::get_ethtool_gstrings_arch(RecordTask*)::SingleStringSet::data’
> declared here
> 1455 | uint32_t d
Bug#1022042: linux-image-amd64: linux-image-5.10.0-19-amd64 fails to boot on machines with AMD integrated graphics
Diederik de Haas writes: > Then I'm inclined to think this *is* a separate issue, which is > due to the upgrade to -19, but that you happen to have an AMD > GPU is 'not' relevant. > > I realize it's not what you want, but may result in an useful > extra data point if you (for this test) switch those parameters > to enable radeon support and disable amdgpu support. Can you try > that? > > If that test does not make a difference, then I'm quite sure > it's a separate issue and it would be best to open a new bug > report for that. I tried booting 5.10.0-19 with an empty command line string and it worked, although it’s now using the "radeon" gpu driver while I’d like to use the "amdgpu" driver instead, mainly for better Vulkan support. Booting with command line options to disable "radeon" and enable "amdgpu" works for 5.10.0-18 and earlier. I don’t know if this an entirely separate issue, however. I can file a separate bug if you think it is appropriate. Best regards. -- inasprecali
Bug#1022042: linux-image-amd64: linux-image-5.10.0-19-amd64 fails to boot on machines with AMD integrated graphics
Diederik de Haas writes: > Then I'm inclined to think this *is* a separate issue, which is > due to the upgrade to -19, but that you happen to have an AMD > GPU is 'not' relevant. > I realize it's not what you want, but may result in an useful > extra data point if you (for this test) switch those parameters > to enable radeon support and disable amdgpu support. Can you try > that? > > If that test does not make a difference, then I'm quite sure > it's a separate issue and it would be best to open a new bug > report for that.
Processed: Close
Processing commands for cont...@bugs.debian.org: > fixed 1022519 0.0.3-4 Bug #1022519 [src:readucks] readucks: FTBFS: distutils.errors.DistutilsClassError: command class must subclass Command The source 'readucks' and version '0.0.3-4' do not appear to match any binary packages Marked as fixed in versions readucks/0.0.3-4. > close 1022519 Bug #1022519 [src:readucks] readucks: FTBFS: distutils.errors.DistutilsClassError: command class must subclass Command Marked Bug as done > stop Stopping processing here. Please contact me if you need assistance. -- 1022519: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1022519 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1009031: possible workaround for libgit-raw-perl FTBFS with libgit2 1.3.0
On Sat, 22 Oct 2022 18:48:31 +0200, Étienne Mollier wrote: > Taking the approach of refreshing the test suite to match the > output produced by the new libgit2 seems to do the job to > address the test suite failure. I also checked this has no > adverse effects on reverse dependencies. Variations between the > reference and the new update are also minimal and seem to make > sense. Interesting finding! The last time I looked I had the impression that this needs more changes / changes in the actual code but obviously I was wrong. The only additional remark I have is: - libgit2-dev (>= 1.1.0), + libgit2-dev (>= 1.5.0), as with your patch the tests fail in stable/bullseye. Cheers, gregor -- .''`. https://info.comodo.priv.at -- Debian Developer https://www.debian.org : :' : OpenPGP fingerprint D1E1 316E 93A7 60A8 104D 85FA BB3A 6801 8649 AA06 `. `' Member VIBE!AT & SPI Inc. -- Supporter Free Software Foundation Europe `- signature.asc Description: Digital Signature
Bug#1022447: marked as done (sorted-nearest: FTBFS: TypeError: dist must be a Distribution instance)
Your message dated Sun, 23 Oct 2022 15:10:51 +
with message-id
and subject line Bug#1022447: fixed in sorted-nearest 0.0.31+dfsg-2
has caused the Debian Bug report #1022447,
regarding sorted-nearest: FTBFS: TypeError: dist must be a Distribution instance
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)
--
1022447: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1022447
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: sorted-nearest
Version: 0.0.31+dfsg-1
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20221023 ftbfs-bookworm
Hi,
During a rebuild of all packages in sid, your package failed to build
on amd64.
Relevant part (hopefully):
> debian/rules clean
> dh clean --with python3 --buildsystem=pybuild
>dh_auto_clean -O--buildsystem=pybuild
> I: pybuild base:240: python3.10 setup.py clean
> /<>/setup.py:1: DeprecationWarning: The distutils package is
> deprecated and slated for removal in Python 3.12. Use setuptools or check PEP
> 632 for potential alternatives
> from distutils.core import setup
> /usr/lib/python3/dist-packages/_distutils_hack/__init__.py:18: UserWarning:
> Distutils was imported before Setuptools, but importing Setuptools also
> replaces the `distutils` module in `sys.modules`. This may lead to
> undesirable behaviors or errors. To avoid these issues, avoid using distutils
> directly, ensure that setuptools is installed in the traditional way (e.g.
> not an editable install), and/or make sure that setuptools is always imported
> before distutils.
> warnings.warn(
> /usr/lib/python3/dist-packages/_distutils_hack/__init__.py:33: UserWarning:
> Setuptools is replacing distutils.
> warnings.warn("Setuptools is replacing distutils.")
> /usr/lib/python3.10/distutils/dist.py:274: UserWarning: Unknown distribution
> option: 'install_requires'
> warnings.warn(msg)
> running clean
> Traceback (most recent call last):
> File "/<>/setup.py", line 75, in
> setup(
> File "/usr/lib/python3.10/distutils/core.py", line 148, in setup
> dist.run_commands()
> File "/usr/lib/python3.10/distutils/dist.py", line 966, in run_commands
> self.run_command(cmd)
> File "/usr/lib/python3.10/distutils/dist.py", line 983, in run_command
> cmd_obj = self.get_command_obj(command)
> File "/usr/lib/python3.10/distutils/dist.py", line 858, in get_command_obj
> cmd_obj = self.command_obj[command] = klass(self)
> File "/usr/lib/python3/dist-packages/setuptools/__init__.py", line 158, in
> __init__
> super().__init__(dist)
> File "/usr/lib/python3/dist-packages/setuptools/_distutils/cmd.py", line
> 59, in __init__
> raise TypeError("dist must be a Distribution instance")
> TypeError: dist must be a Distribution instance
> E: pybuild pybuild:379: clean: plugin distutils failed with: exit code=1:
> python3.10 setup.py clean
> dh_auto_clean: error: pybuild --clean -i python{version} -p 3.10 returned
> exit code 13
> make: *** [debian/rules:10: clean] Error 25
The full build log is available from:
http://qa-logs.debian.net/2022/10/23/sorted-nearest_0.0.31+dfsg-1_unstable.log
All bugs filed during this archive rebuild are listed at:
https://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=ftbfs-20221023;users=lu...@debian.org
or:
https://udd.debian.org/bugs/?release=na=ign=7=7=only=ftbfs-20221023=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 marking it as 'affects'-ing
this package. See https://www.debian.org/Bugs/server-control#affects
If you fail to reproduce this, please provide a build log and diff it with mine
so that we can identify if something relevant changed in the meantime.
--- End Message ---
--- Begin Message ---
Source: sorted-nearest
Source-Version: 0.0.31+dfsg-2
Done: Nilesh Patra
We believe that the bug you reported is fixed in the latest version of
sorted-nearest, which is due to be installed in the Debian FTP archive.
A summary of the changes between this version and the previous one is
attached.
Thank you for reporting the bug, which will now be closed. If you
have further comments please address them to 1022...@bugs.debian.org,
an
Bug#1022498: marked as done (python-pcl: FTBFS: distutils.errors.DistutilsSetupError: each element of 'ext_modules' option must be an Extension instance or 2-tuple)
Your message dated Sun, 23 Oct 2022 15:09:38 +
with message-id
and subject line Bug#1022498: fixed in python-pcl 0.3.0~rc1+dfsg-13
has caused the Debian Bug report #1022498,
regarding python-pcl: FTBFS: distutils.errors.DistutilsSetupError: each element
of 'ext_modules' option must be an Extension instance or 2-tuple
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)
--
1022498: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1022498
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: python-pcl
Version: 0.3.0~rc1+dfsg-12
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20221023 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=pybuild
>dh_update_autotools_config -O--buildsystem=pybuild
>dh_autoreconf -O--buildsystem=pybuild
>dh_auto_configure -O--buildsystem=pybuild
> I: pybuild base:240: python3.10 setup.py config
> /usr/lib/python3/dist-packages/_distutils_hack/__init__.py:18: UserWarning:
> Distutils was imported before Setuptools, but importing Setuptools also
> replaces the `distutils` module in `sys.modules`. This may lead to
> undesirable behaviors or errors. To avoid these issues, avoid using distutils
> directly, ensure that setuptools is installed in the traditional way (e.g.
> not an editable install), and/or make sure that setuptools is always imported
> before distutils.
> warnings.warn(
> /usr/lib/python3/dist-packages/_distutils_hack/__init__.py:33: UserWarning:
> Setuptools is replacing distutils.
> warnings.warn("Setuptools is replacing distutils.")
> running config
>dh_auto_build -O--buildsystem=pybuild
> I: pybuild base:240: /usr/bin/python3 setup.py build
> /usr/lib/python3/dist-packages/_distutils_hack/__init__.py:18: UserWarning:
> Distutils was imported before Setuptools, but importing Setuptools also
> replaces the `distutils` module in `sys.modules`. This may lead to
> undesirable behaviors or errors. To avoid these issues, avoid using distutils
> directly, ensure that setuptools is installed in the traditional way (e.g.
> not an editable install), and/or make sure that setuptools is always imported
> before distutils.
> warnings.warn(
> /usr/lib/python3/dist-packages/_distutils_hack/__init__.py:33: UserWarning:
> Setuptools is replacing distutils.
> warnings.warn("Setuptools is replacing distutils.")
> running build
> running build_py
> creating /<>/.pybuild/cpython3_3.10/build/pcl
> copying pcl/__init__.py -> /<>/.pybuild/cpython3_3.10/build/pcl
> running build_ext
> Traceback (most recent call last):
> File "/<>/setup.py", line 632, in
> setup(name='python-pcl',
> File "/usr/lib/python3/dist-packages/setuptools/__init__.py", line 87, in
> setup
> return distutils.core.setup(**attrs)
> File "/usr/lib/python3/dist-packages/setuptools/_distutils/core.py", line
> 185, in setup
> return run_commands(dist)
> File "/usr/lib/python3/dist-packages/setuptools/_distutils/core.py", line
> 201, in run_commands
> dist.run_commands()
> File "/usr/lib/python3/dist-packages/setuptools/_distutils/dist.py", line
> 968, in run_commands
> self.run_command(cmd)
> File "/usr/lib/python3/dist-packages/setuptools/dist.py", line 1217, in
> run_command
> super().run_command(command)
> File "/usr/lib/python3/dist-packages/setuptools/_distutils/dist.py", line
> 987, in run_command
> cmd_obj.run()
> File
> "/usr/lib/python3/dist-packages/setuptools/_distutils/command/build.py", line
> 132, in run
> self.run_command(cmd_name)
> File "/usr/lib/python3/dist-packages/setuptools/_distutils/cmd.py", line
> 319, in run_command
> self.distribution.run_command(command)
> File "/usr/lib/python3/dist-packages/setuptools/dist.py", line 1217, in
> run_command
> super().run_command(command)
> File "/usr/lib/python3/dist-packages/setuptools/_distutils/dist.py", line
> 987, in run_command
> cmd_obj.run()
> File "/usr/lib/python3/dist-packages/Cython/Distutils/old_build_ext.py",
> line 186, in run
> _build_ext.build_ext.
Bug#1013888: marked as done (libvmod-re2: Fails to build in Ubuntu (incompatible with Varnish 7.x.y), unsatisfiable dependency)
Your message dated Sun, 23 Oct 2022 15:07:43 + with message-id and subject line Bug#1013888: fixed in libvmod-re2 2.0.0-2 has caused the Debian Bug report #1013888, regarding libvmod-re2: Fails to build in Ubuntu (incompatible with Varnish 7.x.y), unsatisfiable dependency to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 1013888: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1013888 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: libvmod-re2 Version: 2.0.0-1 Severity: grave Tags: ftbfs Justification: renders package unusable Dear Maintainer, This source package requires Varnish below 7.0.0. Therefore, it fails to build in Ubuntu on all architectures: https://launchpad.net/~luis220413/+archive/ubuntu/test-builds/+packages In Debian, the binary package built from this source package has an unsatisfiable dependency on libvarnishapi2, that was replaced in version 7.1.0-5 with libvarnishapi3. --- End Message --- --- Begin Message --- Source: libvmod-re2 Source-Version: 2.0.0-2 Done: Michael Fladischer We believe that the bug you reported is fixed in the latest version of libvmod-re2, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 1013...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Michael Fladischer (supplier of updated libvmod-re2 package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Sun, 23 Oct 2022 14:36:29 + Source: libvmod-re2 Architecture: source Version: 2.0.0-2 Distribution: unstable Urgency: medium Maintainer: Varnish Package Maintainers Changed-By: Michael Fladischer Closes: 1013888 Changes: libvmod-re2 (2.0.0-2) unstable; urgency=medium . * Add debian/gbp.conf. * Add patches from upstream for Varnish 7.1 compatibility (Closes: #1013888). * Remove dh_auto_test override because libnss-wrapper is not needed. * Fix expected output for varnishadm vcl.load in autopkgtests. * Bump dependency on varnish to (>= 7.1~). * Bump Standards-Version to 4.6.1.0. * Add patch to fix upstream documentation. Checksums-Sha1: 73217fd1f063fd63201615608f3feb91779e7b71 1795 libvmod-re2_2.0.0-2.dsc 0f295d955666a3b6955aaa7f28b6d6f8973a70da 6472 libvmod-re2_2.0.0-2.debian.tar.xz 26a1a11fa4de5bea868b93cafeac43ae308fdaf4 7080 libvmod-re2_2.0.0-2_arm64.buildinfo Checksums-Sha256: 34fa74384a7f2766ecdbdd8ad49985870af534c1387641c3cc4ea329e3bdb1b2 1795 libvmod-re2_2.0.0-2.dsc c36fb9aedbef54c7f87deec69fa9ca378ddc8e985c877c5f3528766266235cd3 6472 libvmod-re2_2.0.0-2.debian.tar.xz c833b4120e38b6dba127f08d9e81284efdcd4aa9a3f5e957dc1db7551a6d4a3f 7080 libvmod-re2_2.0.0-2_arm64.buildinfo Files: 4a6980f60e35026f049e7e319da5a6b9 1795 web optional libvmod-re2_2.0.0-2.dsc d65f9a90b357c8013d93464a7b7ca440 6472 web optional libvmod-re2_2.0.0-2.debian.tar.xz 15a5c7f60112c36aeff31b903d07726d 7080 web optional libvmod-re2_2.0.0-2_arm64.buildinfo -BEGIN PGP SIGNATURE- iQEzBAEBCgAdFiEEqVSlRXW87UkkCnJc/9PIi5l90WoFAmNVVHQACgkQ/9PIi5l9 0Wox2wf7BlEhDinjMFRALvRV0B5C333Bq3y+WbSZcIkgNDdB0rYKyXUC0q8tl+8V f8cqEDmaaHZOZZFf/r2Pl1aUdit7541Qst8RCZmB6kUh+GOidouaAxHss8Jr0h6m +vi+FcUYa9pEqL0RWcvsyl2qyD71sj4eQvCbUog41o0giYps+J4S9VjnKYocNLm/ fqESZ5y8x72QBOzH/VKf8gJCnNvkxc548Wf/ID2W6/P4tE+FNJ24k7HYJWOI5qlt DxK2NG80U6agUWN07b63kvTLobtHQTVgxpUpDczBATGnYu2HaLQh65gaujHJssls oHZhgvIM+9rlCOxJo8K/3sE4fGEXdQ== =NWcI -END PGP SIGNATURE End Message ---
Bug#1022309: marked as pending in spades
Control: tag -1 pending Hello, Bug #1022309 in spades reported by you has been fixed in the Git repository and is awaiting an upload. You can see the commit message below and you can check the diff of the fix at: https://salsa.debian.org/med-team/spades/-/commit/95cf2c9e1f583160ee49aeeb0b5d82dedba98394 d/control: add missing build-deps following llvm reorganization. This fixes failure to build from source caught by archive rebuild. Closes: #1022309 (this message was generated automatically) -- Greetings https://bugs.debian.org/1022309
Processed: Bug#1022309 marked as pending in spades
Processing control commands: > tag -1 pending Bug #1022309 [src:spades] spades: FTBFS: CheckIncludeFile.c:1:10: fatal error: cxxabi.h: No such file or directory Added tag(s) pending. -- 1022309: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1022309 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1022320: marked as done (ruby-puppet-syntax: FTBFS: ERROR: Test "ruby3.1" failed: Failure/Error: expect(res[:warnings]).to match([]))
Your message dated Sun, 23 Oct 2022 14:53:26 + with message-id and subject line Bug#1022320: fixed in ruby-puppet-syntax 3.2.1-1 has caused the Debian Bug report #1022320, regarding ruby-puppet-syntax: FTBFS: ERROR: Test "ruby3.1" failed: Failure/Error: expect(res[:warnings]).to match([]) to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 1022320: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1022320 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: ruby-puppet-syntax Version: 3.1.0-1 Severity: serious Justification: FTBFS Tags: bookworm sid ftbfs User: lu...@debian.org Usertags: ftbfs-20221023 ftbfs-bookworm Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > Failure/Error: expect(res[:warnings]).to match([]) > >expected ["/<>/lib/puppet-syntax/templates.rb:72: > warnin...gument of ERB.new is deprecated. Use keyword argument like > ERB.new(str, trim_mode: ...) instead.\n"] to match [] >Diff: >@@ -1 +1,2 @@ >+/<>/lib/puppet-syntax/templates.rb:72: warning: Passing > safe_level with the 2nd argument of ERB.new is deprecated. Do not use it, and > specify other arguments as keyword > arguments.\n/<>/lib/puppet-syntax/templates.rb:72: warning: > Passing trim_mode with the 3rd argument of ERB.new is deprecated. Use keyword > argument like ERB.new(str, trim_mode: ...) instead.\n > # ./spec/puppet-syntax/templates_spec.rb:71:in `block (2 levels) in (required)>' > > Finished in 0.25139 seconds (files took 1.18 seconds to load) > 40 examples, 4 failures > > Failed examples: > > rspec ./spec/puppet-syntax/templates_spec.rb:17 # PuppetSyntax::Templates > should return nothing from a valid file > rspec ./spec/puppet-syntax/templates_spec.rb:25 # PuppetSyntax::Templates > should ignore NameErrors from unbound variables > rspec ./spec/puppet-syntax/templates_spec.rb:49 # PuppetSyntax::Templates > should read more than one valid file > rspec ./spec/puppet-syntax/templates_spec.rb:67 # PuppetSyntax::Templates > should ignore a TypeError > > /usr/bin/ruby3.1 > -I/usr/share/rubygems-integration/all/gems/rspec-support-3.10.3/lib:/usr/share/rubygems-integration/all/gems/rspec-core-3.10.1/lib > /usr/share/rubygems-integration/all/gems/rspec-core-3.10.1/exe/rspec > --pattern ./spec/\*\*/\*_spec.rb --format documentation failed > ERROR: Test "ruby3.1" failed: The full build log is available from: http://qa-logs.debian.net/2022/10/23/ruby-puppet-syntax_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-20221023;users=lu...@debian.org or: https://udd.debian.org/bugs/?release=na=ign=7=7=only=ftbfs-20221023=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 marking it as 'affects'-ing this package. See https://www.debian.org/Bugs/server-control#affects If you fail to reproduce this, please provide a build log and diff it with mine so that we can identify if something relevant changed in the meantime. --- End Message --- --- Begin Message --- Source: ruby-puppet-syntax Source-Version: 3.2.1-1 Done: Georg Faerber We believe that the bug you reported is fixed in the latest version of ruby-puppet-syntax, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 1022...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Georg Faerber (supplier of updated ruby-puppet-syntax package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Sun, 23 Oct 2022 14:08:53 + Source: ruby-puppet-syntax Architecture: source Version: 3.2.1-1 Distribution: unstable Urgency: medium Maintainer: Debian Ruby Team Changed-By: Georg Faerber Closes: 1022320 Changes: ruby-puppet-syntax (3.2.1-1) unstabl
