Processed: Bug#1015103 marked as pending in lomiri-ui-extras
Processing control commands: > tag -1 pending Bug #1015103 [src:lomiri-ui-extras] lomiri-ui-extras: FTBFS: dh_auto_test: error: cd obj-x86_64-linux-gnu && make -j8 test ARGS\+=--verbose ARGS\+=-j8 returned exit code 2 Added tag(s) pending. -- 1015103: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1015103 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1015103: marked as pending in lomiri-ui-extras
Control: tag -1 pending Hello, Bug #1015103 in lomiri-ui-extras 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/ubports-team/lomiri-ui-extras/-/commit/282f186494d31d546336365dbb9805731e268eb8 Disable tst_printers test. (Closes: #1015103) (this message was generated automatically) -- Greetings https://bugs.debian.org/1015103
Bug#1013034: Bug fix now in sane-backends
Hi, Upstream now has a fix for this issue: https://gitlab.com/sane-project/backends/-/merge_requests/757 You may perhaps pull this change and drop the patch. Thanks for the report! Cheers, Ralph Little
Bug#1020456: cypari2 FTBFS with PARI 2.15.0
On Wed, Sep 21, 2022 at 11:57:40PM +0300, Adrian Bunk wrote: > Testing cypari2.gen > ** > File > "/<>/.pybuild/cpython3_3.10_cypari2/build/cypari2/gen.cpython-310-x86_64-linux-gnu.so", > line ?, in cypari2.gen.Gen.__complex__ > Failed example: > complex(g) > Differences (ndiff with -expected +actual): > - (2.2847006554165614+0j) > + (1.118033988749895+0j) > ** > File > "/<>/.pybuild/cpython3_3.10_cypari2/build/cypari2/gen.cpython-310-x86_64-linux-gnu.so", > line ?, in cypari2.gen.__test__.Gen.__complex__ (line 2006) > Failed example: > complex(g) > Differences (ndiff with -expected +actual): > - (2.2847006554165614+0j) > + (1.118033988749895+0j) > ** > 2 items had failures: >1 of 13 in cypari2.gen.Gen.__complex__ >1 of 13 in cypari2.gen.__test__.Gen.__complex__ (line 2006) This one is a bug in PARI/GP, that has been fixed in master. Once we get to the point it is the only remaining show stopper, I will update PARI/GP in sid. Cheers, -- Bill. Imagine a large red swirl here.
Bug#1020567: marked as done (meson's autopkg tests fail with setuptools 65)
Your message dated Wed, 05 Oct 2022 22:19:43 +
with message-id
and subject line Bug#1020567: fixed in meson 0.63.3-1
has caused the Debian Bug report #1020567,
regarding meson's autopkg tests fail with setuptools 65
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.)
--
1020567: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1020567
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:meson
Version: 0.63.2-1
Severity: serious
Tags: sid bookworm
https://ci.debian.net/data/autopkgtest/testing/amd64/m/meson/26322073/log.gz
[...]
autopkgtest [07:51:16]: test exhaustive: [---
Meson build system 0.63.2 Project and Unit Tests
System information.
Architecture: ('64bit', 'ELF')
Machine: x86_64
Platform: Linux
Processor:
System: Linux
test_meson_exe_windows (__main__.CommandTests) ... skipped 'NOT IMPLEMENTED'
test_meson_installed (__main__.CommandTests) ...
/usr/lib/python3/dist-packages/setuptools/config/expand.py:65: EncodingWarning:
'encoding' argument not specified
with open(spec.origin) as strm: # type: ignore
/usr/lib/python3/dist-packages/setuptools/config/setupcfg.py:508:
SetuptoolsDeprecationWarning: The license_file parameter is deprecated, use
license_files instead.
warnings.warn(msg, warning_class)
/usr/lib/python3/dist-packages/setuptools/command/install.py:34:
SetuptoolsDeprecationWarning: setup.py install is deprecated. Use build and pip
and other standards-based tools.
warnings.warn(
/usr/lib/python3/dist-packages/setuptools/command/easy_install.py:146:
EasyInstallDeprecationWarning: easy_install command is deprecated. Use build and
pip and other standards-based tools.
warnings.warn(
/usr/lib/python3/dist-packages/setuptools/command/easy_install.py:584:
EncodingWarning: 'encoding' argument not specified
f = open(pth_file, 'w')
TEST FAILED: /tmp/tmprcqr8ahm/prefix/local/lib/python3.10/dist-packages/ does
NOT support .pth files
bad install directory or PYTHONPATH
You are attempting to install a package to a directory that is not
on PYTHONPATH and which Python does not read ".pth" files from. The
installation directory you specified (via --install-dir, --prefix, or
the distutils default setting) was:
/tmp/tmprcqr8ahm/prefix/local/lib/python3.10/dist-packages/
and your PYTHONPATH environment variable currently contains:
'/tmp/tmprcqr8ahm/prefix/lib/python3.10/site-packages/'
Here are some of your options for correcting the problem:
* You can choose a different installation directory, i.e., one that is
on PYTHONPATH or supports .pth files
* You can add the installation directory to the PYTHONPATH environment
variable. (It must then also be on PYTHONPATH whenever you run
Python and want to use the package(s) you are installing.)
* You can set up the installation directory to support ".pth" files by
using one of the approaches described here:
https://setuptools.pypa.io/en/latest/deprecated/easy_install.html#custom-installation-locations
Please make the appropriate changes for your system and try again.
/usr/lib/python3/dist-packages/setuptools/_distutils/text_file.py:118:
EncodingWarning: 'encoding' argument not specified
self.file = open(self.filename, errors=self.errors)
zip_safe flag not set; analyzing archive contents...
mesonbuild.__pycache__.mdevenv.cpython-310: module references __file__
mesonbuild.__pycache__.minstall.cpython-310: module references __file__
/usr/lib/python3/dist-packages/setuptools/command/bdist_egg.py:352:
EncodingWarning: 'encoding' argument not specified
f = open(fn, 'wt')
/usr/lib/python3/dist-packages/setuptools/command/easy_install.py:871:
EncodingWarning: 'encoding' argument not specified
with open(target, "w" + mode) as f:
FAIL
--- End Message ---
--- Begin Message ---
Source: meson
Source-Version: 0.63.3-1
Done: Jussi Pakkanen
We believe that the bug you reported is fixed in the latest version of
meson, 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 1020...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Jussi Pakkanen (supplier of updated meson 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
Bug#1013012: marked as done (persistent-cache-cpp: ftbfs with GCC-12)
Your message dated Wed, 05 Oct 2022 21:20:58 + with message-id and subject line Bug#1013012: fixed in persistent-cache-cpp 1.0.5-4 has caused the Debian Bug report #1013012, regarding persistent-cache-cpp: ftbfs with GCC-12 to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 1013012: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1013012 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: src:persistent-cache-cpp Version: 1.0.5-3 Severity: normal Tags: sid bookworm User: debian-...@lists.debian.org Usertags: ftbfs-gcc-12 [This bug is targeted to the upcoming bookworm release] Please keep this issue open in the bug tracker for the package it was filed for. If a fix in another package is required, please file a bug for the other package (or clone), and add a block in this package. Please keep the issue open until the package can be built in a follow-up test rebuild. The package fails to build in a test rebuild on at least amd64 with gcc-12/g++-12, but succeeds to build with gcc-11/g++-11. The severity of this report will be raised before the bookworm release. The full build log can be found at: http://qa-logs.debian.net/2022/06/09/gcc12/persistent-cache-cpp_1.0.5-3_unstable_gcc12.log The last lines of the build log are at the end of this report. To build with GCC 11, either set CC=gcc-11 CXX=g++-11 explicitly, or install the gcc, g++, gfortran, ... packages from experimental. apt-get -t=experimental install g++ Common build failures are new warnings resulting in build failures with -Werror turned on, or new/dropped symbols in Debian symbols files. For other C/C++ related build failures see the porting guide at http://gcc.gnu.org/gcc-11/porting_to.html GCC 11 defaults to the GNU++17 standard. If your package installs header files in /usr/include, please don't work around C++17 issues by choosing a lower C++ standard for the package build, but fix these issues to build with the C++17 standard. [...] cd /<>/obj-x86_64-linux-gnu/tests/core/googletest && /usr/bin/cmake -P CMakeFiles/gtest.dir/cmake_clean_target.cmake cd /<>/obj-x86_64-linux-gnu/tests/core/googletest && /usr/bin/cmake -E cmake_link_script CMakeFiles/gtest.dir/link.txt --verbose=1 /usr/bin/ar qc /<>/obj-x86_64-linux-gnu/tests/core/gmock/lib/libgtest.a "CMakeFiles/gtest.dir/src/gtest-all.cc.o" /usr/bin/ranlib /<>/obj-x86_64-linux-gnu/tests/core/gmock/lib/libgtest.a make[6]: Leaving directory '/<>/obj-x86_64-linux-gnu/tests/core/gmock' [ 25%] Built target gtest make -f CMakeFiles/gmock.dir/build.make CMakeFiles/gmock.dir/depend make -f /<>/obj-x86_64-linux-gnu/tests/core/googletest/CMakeFiles/gtest_main.dir/build.make /<>/obj-x86_64-linux-gnu/tests/core/googletest/CMakeFiles/gtest_main.dir/depend make[6]: Entering directory '/<>/obj-x86_64-linux-gnu/tests/core/gmock' cd /<>/obj-x86_64-linux-gnu/tests/core/gmock && /usr/bin/cmake -E cmake_depends "Unix Makefiles" /usr/src/googletest/googlemock /usr/src/googletest/googlemock /<>/obj-x86_64-linux-gnu/tests/core/gmock /<>/obj-x86_64-linux-gnu/tests/core/gmock /<>/obj-x86_64-linux-gnu/tests/core/gmock/CMakeFiles/gmock.dir/DependInfo.cmake --color= make[6]: Entering directory '/<>/obj-x86_64-linux-gnu/tests/core/gmock' cd /<>/obj-x86_64-linux-gnu/tests/core/gmock && /usr/bin/cmake -E cmake_depends "Unix Makefiles" /usr/src/googletest/googlemock /usr/src/googletest/googletest /<>/obj-x86_64-linux-gnu/tests/core/gmock /<>/obj-x86_64-linux-gnu/tests/core/googletest /<>/obj-x86_64-linux-gnu/tests/core/googletest/CMakeFiles/gtest_main.dir/DependInfo.cmake --color= make[6]: Leaving directory '/<>/obj-x86_64-linux-gnu/tests/core/gmock' make -f CMakeFiles/gmock.dir/build.make CMakeFiles/gmock.dir/build make[6]: Leaving directory '/<>/obj-x86_64-linux-gnu/tests/core/gmock' make -f /<>/obj-x86_64-linux-gnu/tests/core/googletest/CMakeFiles/gtest_main.dir/build.make /<>/obj-x86_64-linux-gnu/tests/core/googletest/CMakeFiles/gtest_main.dir/build make[6]: Entering directory '/<>/obj-x86_64-linux-gnu/tests/core/gmock' make[6]: Entering directory '/<>/obj-x86_64-linux-gnu/tests/core/gmock' [ 37%] Building CXX object CMakeFiles/gmock.dir/src/gmock-all.cc.o /usr/bin/c++ -I/usr/src/googletest/googlemock/include -I/usr/src/googletest/googlemock -isystem /usr/src/googletest/googletest/include -isystem /usr/src/googletest/googletest -g -O2 -ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 --std=c++11 -Wall -pedantic -Wextra -Wcast-align -Wcast-qual -Wformat -Wredundant-decls
Bug#1015133: marked as done (qtmir: FTBFS: gmock_fixes.h:49:7: error: ‘ActionResultHolder’ is not a class template)
Your message dated Wed, 05 Oct 2022 20:57:45 +
with message-id
and subject line Bug#1015133: fixed in qtmir 0.7.0-3
has caused the Debian Bug report #1015133,
regarding qtmir: FTBFS: gmock_fixes.h:49:7: error: ‘ActionResultHolder’ is not
a class template
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.)
--
1015133: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1015133
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: qtmir
Version: 0.7.0-2
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20220716 ftbfs-bookworm
Hi,
During a rebuild of all packages in sid, your package failed to build
on amd64.
Relevant part (hopefully):
> /usr/bin/c++ -g -O2 -ffile-prefix-map=/<>=.
> -fstack-protector-strong -Wformat -Werror=format-security -Wdate-time
> -D_FORTIFY_SOURCE=2 -fPIC -Wall -fno-strict-aliasing -Wextra -Wl,-z,relro
> -Wl,-z,now -rdynamic
> CMakeFiles/general_test.dir/general_test_autogen/mocs_compilation.cpp.o
> CMakeFiles/general_test.dir/objectlistmodel_test.cpp.o
> CMakeFiles/general_test.dir/timestamp_test.cpp.o
> CMakeFiles/general_test.dir/__/__/__/src/common/timestamp.cpp.o -o
> general_test /usr/lib/x86_64-linux-gnu/libQt5Gui.so.5.15.4
> ../../gmock/lib/libgtest.a ../../gmock/lib/libgtest_main.a
> ../../gmock/lib/libgmock_main.a ../../gmock/lib/libgmock.a
> /usr/lib/x86_64-linux-gnu/libQt5Core.so.5.15.4 ../../gmock/lib/libgtest.a
> -lpthread
> In file included from /<>/tests/framework/mock_main_loop.h:21,
> from /<>/tests/framework/mock_main_loop.cpp:17:
> /<>/tests/framework/gmock_fixes.h:49:7: error:
> ‘ActionResultHolder’ is not a class template
>49 | class ActionResultHolder>
> | ^~
> /<>/tests/framework/gmock_fixes.h:50:40: error: expected
> class-name before ‘{’ token
>50 | : public UntypedActionResultHolderBase {
> |^
> /<>/tests/framework/gmock_fixes.h:104:3: error: ISO C++ forbids
> declaration of ‘GTEST_DISALLOW_ASSIGN_’ with no type [-fpermissive]
> 104 | GTEST_DISALLOW_ASSIGN_(ActionResultHolder);
> | ^~
> [ 74%] Building CXX object
> tests/framework/CMakeFiles/qtmir-test-framework-static.dir/mock_mir_session.cpp.o
> [ 74%] Linking CXX executable MirALTests
> cd /<>/obj-x86_64-linux-gnu/tests/framework && /usr/bin/c++
> -DGTEST_VERSION_MAJOR=1 -DGTEST_VERSION_MINOR=12 -DGTEST_VERSION_PATCH=1
> -DQT_CORE_LIB -DQT_DBUS_LIB -DQT_DISABLE_DEPRECATED_BEFORE=0x050900
> -DQT_GUI_LIB -DQT_NETWORK_LIB -DQT_NO_DEBUG -DQT_NO_KEYWORDS
> -DQT_QMLMODELS_LIB -DQT_QML_LIB -DQT_QUICK_LIB -DQT_USE_QSTRINGBUILDER
> -DWITH_VALGRIND -I/<>/obj-x86_64-linux-gnu/tests/framework
> -I/<>/tests/framework
> -I/<>/obj-x86_64-linux-gnu/tests/framework/qtmir-test-framework-static_autogen/include
> -I/<>/tests/include -I/<>/src/common
> -I/<>/src/platforms/mirserver -I/<>/src/modules
> -isystem /usr/include/x86_64-linux-gnu/qt5/QtCore -isystem
> /usr/include/x86_64-linux-gnu/qt5 -isystem /usr/include/miral -isystem
> /usr/include/mirclient -isystem /usr/include/mircookie -isystem
> /usr/include/mircore -isystem /usr/include/mirserver -isystem
> /usr/include/mirplatform -isystem /usr/include/mircommon -isystem
> /usr/include/uuid -isystem /usr/include/mirrenderer -isystem
> /usr/include/mirtest -isystem /usr/include/x86_64-linux-gnu/qt5/QtQuick
> -isystem /usr/include/x86_64-linux-gnu/qt5/QtQmlModels -isystem
> /usr/include/x86_64-linux-gnu/qt5/QtQml -isystem
> /usr/include/x86_64-linux-gnu/qt5/QtNetwork -isystem
> /usr/lib/x86_64-linux-gnu/qt5/mkspecs/linux-g++ -isystem
> /usr/include/x86_64-linux-gnu/qt5/QtGui -isystem
> /usr/include/x86_64-linux-gnu/qt5/QtDBus -isystem
> /usr/src/googletest/googletest/include -isystem
> /usr/src/googletest/googlemock/include -g -O2
> -ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat
> -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -fPIC -Wall
> -fno-strict-aliasing -Wextra -fPIC -std=gnu++14 -MD -MT
> tests/framework/CMakeFiles/qtmir-test-framework-static.dir/mock_mir_session.cpp.o
> -MF CMakeFiles/qtmir-test-framework-static.dir/mock_mir_session.cpp.o.d -o
> CMakeFiles/qtmir-test-framework-static.dir/mock_mir_session.cpp.o -c
> /<>/tests/framework/mock_mir_session.cpp
> cd /<>/obj-x86_64-linux-gnu/tests/mirserver/miral &&
> /usr/bin/cmake -E cmake_link_script CMakeFiles/MirALTests.dir/link.txt
> --verbose=1
> /usr/bin/c++ -g -O2 -ffile-prefix-map=/<>=.
> -fstack-protector-strong -Wformat
Bug#1013564: marked as done (python-django-health-check: FTBFS: dh_auto_test: error: pybuild --test --test-pytest -i python{version} -p "3.9 3.10" returned exit code 13)
Your message dated Wed, 05 Oct 2022 20:57:35 +
with message-id
and subject line Bug#1013564: fixed in python-django-health-check 3.17.0-1
has caused the Debian Bug report #1013564,
regarding python-django-health-check: FTBFS: dh_auto_test: error: pybuild
--test --test-pytest -i python{version} -p "3.9 3.10" returned exit code 13
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)
--
1013564: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1013564
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: python-django-health-check
Version: 3.12.1-3
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20220624 ftbfs-bookworm
Hi,
During a rebuild of all packages in sid, your package failed to build
on amd64.
Relevant part (hopefully):
> debian/rules binary
> dh binary --with python3 --buildsystem=pybuild
>dh_update_autotools_config -O--buildsystem=pybuild
>dh_autoreconf -O--buildsystem=pybuild
>dh_auto_configure -O--buildsystem=pybuild
> I: pybuild base:239: python3.9 setup.py config
> running config
> I: pybuild base:239: python3.10 setup.py config
> running config
>dh_auto_build -O--buildsystem=pybuild
> I: pybuild base:239: /usr/bin/python3.9 setup.py build
> running build
> running build_py
> creating
> /<>/.pybuild/cpython3_3.9_django-health-check/build/health_check
> copying health_check/__init__.py ->
> /<>/.pybuild/cpython3_3.9_django-health-check/build/health_check
> copying health_check/plugins.py ->
> /<>/.pybuild/cpython3_3.9_django-health-check/build/health_check
> copying health_check/exceptions.py ->
> /<>/.pybuild/cpython3_3.9_django-health-check/build/health_check
> copying health_check/urls.py ->
> /<>/.pybuild/cpython3_3.9_django-health-check/build/health_check
> copying health_check/mixins.py ->
> /<>/.pybuild/cpython3_3.9_django-health-check/build/health_check
> copying health_check/views.py ->
> /<>/.pybuild/cpython3_3.9_django-health-check/build/health_check
> copying health_check/backends.py ->
> /<>/.pybuild/cpython3_3.9_django-health-check/build/health_check
> copying health_check/conf.py ->
> /<>/.pybuild/cpython3_3.9_django-health-check/build/health_check
> running egg_info
> writing django_health_check.egg-info/PKG-INFO
> writing dependency_links to django_health_check.egg-info/dependency_links.txt
> writing requirements to django_health_check.egg-info/requires.txt
> writing top-level names to django_health_check.egg-info/top_level.txt
> reading manifest file 'django_health_check.egg-info/SOURCES.txt'
> reading manifest template 'MANIFEST.in'
> warning: manifest_maker: MANIFEST.in, line 2: 'recursive-include' expects
>...
>
> warning: manifest_maker: MANIFEST.in, line 3: 'prune' expects a single
>
>
> adding license file 'LICENSE'
> writing manifest file 'django_health_check.egg-info/SOURCES.txt'
> creating
> /<>/.pybuild/cpython3_3.9_django-health-check/build/health_check/cache
> copying health_check/cache/__init__.py ->
> /<>/.pybuild/cpython3_3.9_django-health-check/build/health_check/cache
> copying health_check/cache/apps.py ->
> /<>/.pybuild/cpython3_3.9_django-health-check/build/health_check/cache
> copying health_check/cache/backends.py ->
> /<>/.pybuild/cpython3_3.9_django-health-check/build/health_check/cache
> creating
> /<>/.pybuild/cpython3_3.9_django-health-check/build/health_check/contrib
> copying health_check/contrib/__init__.py ->
> /<>/.pybuild/cpython3_3.9_django-health-check/build/health_check/contrib
> creating
> /<>/.pybuild/cpython3_3.9_django-health-check/build/health_check/contrib/celery
> copying health_check/contrib/celery/__init__.py ->
> /<>/.pybuild/cpython3_3.9_django-health-check/build/health_check/contrib/celery
> copying health_check/contrib/celery/apps.py ->
> /<>/.pybuild/cpython3_3.9_django-health-check/build/health_check/contrib/celery
> copying health_check/contrib/celery/backends.py ->
> /<>/.pybuild/cpython3_3.9_django-health-check/build/health_check/contrib/celery
> copying health_check/contrib/celery/tasks.py ->
> /<>/.pybuild/cpython3_3.9_django-health-check/build/health_check/contrib/celery
> creating
> /<>/.pybuild/cpython3_3.9_django-health-check/build/health_check/contrib/psutil
> copying health_check/contrib/psutil/__init__.py ->
> /<>/.pybuild/cpython3_3.9_django-health-check/build/health_check/contrib/psutil
> copying health_check/contrib/psutil/apps.py ->
> /<>/.pybuild/cpython3_3.9_django-health-check/build/health_check/contrib/psutil
> copying health_check/contrib/psutil/backends.py ->
>
Bug#1021325: irrlicht: non-free files included
Source: irrlicht Version: 1.8.5+ds-2 Severity: serious The irrlicht source includes the media/dwarf* files which have a non-free license. Please repack getting rid of it. The package will still build without them.
Bug#1021032: VLC Black screen
> By the way, once updated to the new VLC version (3.0.17.4-5) in a fully > updated Sid I noticed after seeing a few videos the player goes black again > and nothing until a reboot is issued. > > Anyone else noticed this? Yes (also on current sid with VLC 3.0.17.4-5) i can confirm: after switching to another videos in my playlist it turns to black again. Disabling "Integrate video in interface" is a workaround (reported in #1021140).
Processed: Re: Bug#1019353: transition: perl 5.36
Processing control commands: > tag -1 - moreinfo Bug #1019353 [release.debian.org] transition: perl 5.36 Removed tag(s) moreinfo. > block -1 with 1021324 Bug #1019353 [release.debian.org] transition: perl 5.36 1019353 was blocked by: 1016761 1019353 was not blocking any bugs. Added blocking bug(s) of 1019353: 1021324 -- 1019353: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1019353 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1021324: redland-bindings: FTBFS: missing build dependency on pkg-config
Source: redland-bindings Version: 1.0.17.1+dfsg-2 Severity: serious Tags: ftbfs This package fails to build from source on current sid. Log excerpt: checking for swig... swig checking for pkg-config... no checking SWIG support... 4.0.2 - OK [...] checking Enable PHP API... no checking Enable Ruby API... no checking for redland... ./configure: line 13855: --exists: command not found not found configure: error: Redland is not installed - see http://librdf.org/ to get a version 1.0.17 or newer The (regenerated) configure script has this around line 13855: printf %s "checking for redland... " >&6; } if $PKG_CONFIG --exists redland; then REDLAND_CONFIG="$PKG_CONFIG redland" Clearly the problem is that pkg-config no longer gets pulled in. It looks like this regressed with libraptor2-dev 2.0.15-3, which dropped its dependency on pkg-config, triggering a latent bug in redland-bindings of a missing a build dependency. A full build log is available at http://perl.debian.net/rebuild-logs/sid/redland-bindings_1.0.17.1+dfsg-2/redland-bindings_1.0.17.1+dfsg-2.buildlog -- Niko Tyni nt...@debian.org
Bug#1021322: librust-pyo3-dev: impossible to install
Package: librust-pyo3-dev Version: 0.16.5-1 Severity: grave Justification: renders package unusable -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Package is impossible to install: Depends on missing librust-inventory-0.2+default-dev -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEEn+Ppw2aRpp/1PMaELHwxRsGgASEFAmM90pIACgkQLHwxRsGg ASHNsRAAgohwRXMv6v9rUb3Qgji0shgFe5Bg73+Oy4CR1cMPlsVCYQLe5dd6z3aH jJXtx73ImezOjamLamXzPH09jEtPCT8yFczfmFtqC5IrRgVXcRupJXEzZ/56pYML gnrKVIUPDkzX1KHkEUyyY9JJ3xsGw7lEKUOwN/kqGXx2xQIibECRDEPT0djdcu9O OjraEgonD7aYz8h/eratqVyO9OdxvToO1u4FNxxcck/7eLmKOfZJspm2Rbp7eltW Fk8DoVucqTmKc0ZcTv7mr1cUfeoxEd4Vwnvo331fzzdKQsEbjB63uxdCQ8zARaWj Smcb/pYQXnO5eS3mGDwX0NqZMQC/oFGA1reyfZ5FwvMF3wGKFLk8xgu6l0uT699T b0NNU1sAR97j7uL28ftIPadT4m+183uwEQOOytIcMYf+5i4b+Q+8FuFu9i5+lKT0 nM5y2gPCvKILDfWPKnPRh8JSgYFhVcr73CiU76RWxjguYs0gwpTq8XoeLxwyTVQ3 KEKC1idgqbNCTSm8KV7WaXzRcDGzJyhrxLGLOo+OQ93kXJtrcDNpNDs4O15vMjZQ 6D03aUE+Pzqr3god8J5abQ0bi6mmo5ANJ7f5Y/kD9OzRw0FBY9+pPPH0Ka6p1Rc4 OkNkrreiPXFTFQJbgOLl18BTTCkPBeSofcx1i4l2xofN9FglocI= =7z4k -END PGP SIGNATURE-
Bug#1021277: marked as done (strongswan: CVE-2022-40617)
Your message dated Wed, 05 Oct 2022 18:50:56 +
with message-id
and subject line Bug#1021271: fixed in strongswan 5.9.8-1
has caused the Debian Bug report #1021271,
regarding strongswan: CVE-2022-40617
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.)
--
1021271: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1021271
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: strongswan
X-Debbugs-CC: t...@security.debian.org
Severity: grave
Tags: security
Hi,
The following vulnerability was published for strongswan.
CVE-2022-40617[0]:
https://www.strongswan.org/blog/2022/10/03/strongswan-vulnerability-(cve-2022-40617).html
Patch: https://download.strongswan.org/security/CVE-2022-40617/
If you fix the vulnerability please also make sure to include the
CVE (Common Vulnerabilities & Exposures) id in your changelog entry.
For further information see:
[0] https://security-tracker.debian.org/tracker/CVE-2022-40617
https://www.cve.org/CVERecord?id=CVE-2022-40617
Please adjust the affected versions in the BTS as needed.
--- End Message ---
--- Begin Message ---
Source: strongswan
Source-Version: 5.9.8-1
Done: Yves-Alexis Perez
We believe that the bug you reported is fixed in the latest version of
strongswan, 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.
Yves-Alexis Perez (supplier of updated strongswan 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: Wed, 05 Oct 2022 15:25:18 +0200
Source: strongswan
Architecture: source
Version: 5.9.8-1
Distribution: unstable
Urgency: medium
Maintainer: strongSwan Maintainers
Changed-By: Yves-Alexis Perez
Closes: 1021271
Changes:
strongswan (5.9.8-1) unstable; urgency=medium
.
* New upstream version 5.9.8
- Includes fix for CVE-2022-40617, denial of service due to the
revocation plugin potentially using untrusted OCSP URIs and CRL
distribution points in CRLs. (closes: #1021271)
* Remove strongswan-scepclient package, replaced by a pki(1) command
* d/p/0006-fix-format-string-issue-in-enum_flags_to_string dropped, included
upstream
* remove dropped _copyright utility
* d/strongswan-pki.install: install est/estca manpages (RFC 7070)
* d/s-{started,swanctl}.lintian-overrides updated for new lintian
* d/copyright updated for new upstream release
Checksums-Sha1:
8399db837f4e3862be685b0676d3b8c985f0407a 3220 strongswan_5.9.8-1.dsc
897843f9cd4ccefe4317218ecccb4cba32d2dc41 4747096 strongswan_5.9.8.orig.tar.bz2
c67ef343ed5b12aecddf2b872462fba38050b5d3 659 strongswan_5.9.8.orig.tar.bz2.asc
1f8babd9d91935efa761749bb070fc85e0aa96b2 117068
strongswan_5.9.8-1.debian.tar.xz
63fb4a22e356af2ce095ef0b4fccfa8e57c3a014 17180
strongswan_5.9.8-1_amd64.buildinfo
Checksums-Sha256:
23aaa161ff07a47e6a2b9c4e9d5c8dfe8c870e9a720311b291e01a56cddfe4db 3220
strongswan_5.9.8-1.dsc
d3303a43c0bd7b75a12b64855e8edcb53696f06190364f26d1533bde1f2e453c 4747096
strongswan_5.9.8.orig.tar.bz2
0338545be1d68675e874fd3792a336e2a27ac3dae65c4e96c13592f710a0dbc9 659
strongswan_5.9.8.orig.tar.bz2.asc
2a35d4fa4e06cd274ee5ff87e08712ed92c4d6390db03bd6fce5fa3c9c6235bc 117068
strongswan_5.9.8-1.debian.tar.xz
120eaf2c99c900efb51a6fb62d16db0c3d317a5ec127c3f8d48300b08bcb9464 17180
strongswan_5.9.8-1_amd64.buildinfo
Files:
5817700843b50ac7f2195bbb9b7502ed 3220 net optional strongswan_5.9.8-1.dsc
f46b0d3e7aed88824650d0721c887443 4747096 net optional
strongswan_5.9.8.orig.tar.bz2
49e612097053bb8b6cc4eb8bd6f8455f 659 net optional
strongswan_5.9.8.orig.tar.bz2.asc
63fb2457393dd882ec8b4a7aa727e32b 117068 net optional
strongswan_5.9.8-1.debian.tar.xz
21fc321c1c60e5cb6492bf578d0d220f 17180 net optional
strongswan_5.9.8-1_amd64.buildinfo
-BEGIN PGP SIGNATURE-
iQEzBAEBCgAdFiEE8vi34Qgfo83x35gF3rYcyPpXRFsFAmM9ztMACgkQ3rYcyPpX
RFs7Lgf8DVkjFNfxtzvbm0t+uVwc0Q4JdLYCaaWl2NN5PnImDtgb01PuJqvZkc/n
Adkq4mBUTc+nyRoIPKdeGTRH2SJHSaO/ArOuYh5+PhNvBVZm2iWrjqsawUr1sr/g
pUe1Ey7gWK4phrdWknmE0NGKnfO11Ikp/OTPkzgDdrR8Vm+np4opD3Qs0GuNQ+fH
nb3zV19z8NbxpO41jjIBHEf5UKrRHd89aC9o245J/yL3AeJg1fDlsHsUFzNEdcuo
Bug#1021271: marked as done (strongswan: CVE-2022-40617)
Your message dated Wed, 05 Oct 2022 18:50:56 +
with message-id
and subject line Bug#1021271: fixed in strongswan 5.9.8-1
has caused the Debian Bug report #1021271,
regarding strongswan: CVE-2022-40617
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.)
--
1021271: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1021271
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: strongswan
Version: 5.9.6-1
Severity: important
Tags: security upstream
X-Debbugs-Cc: car...@debian.org, Debian Security Team
Control: found -1 5.9.1-1+deb11u2
Control: found -1 5.9.1-1
Control: found -1 5.5.1-4
Hi,
The following vulnerability was published for strongswan.
CVE-2022-40617[0]:
| Using Untrusted URIs for Revocation Checking
If you fix the vulnerability please also make sure to include the
CVE (Common Vulnerabilities & Exposures) id in your changelog entry.
For further information see:
[0] https://security-tracker.debian.org/tracker/CVE-2022-40617
https://www.cve.org/CVERecord?id=CVE-2022-40617
[1]
https://www.strongswan.org/blog/2022/10/03/strongswan-vulnerability-(cve-2022-40617).html
[2] https://download.strongswan.org/security/CVE-2022-40617
Regards,
Salvatore
--- End Message ---
--- Begin Message ---
Source: strongswan
Source-Version: 5.9.8-1
Done: Yves-Alexis Perez
We believe that the bug you reported is fixed in the latest version of
strongswan, 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.
Yves-Alexis Perez (supplier of updated strongswan 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: Wed, 05 Oct 2022 15:25:18 +0200
Source: strongswan
Architecture: source
Version: 5.9.8-1
Distribution: unstable
Urgency: medium
Maintainer: strongSwan Maintainers
Changed-By: Yves-Alexis Perez
Closes: 1021271
Changes:
strongswan (5.9.8-1) unstable; urgency=medium
.
* New upstream version 5.9.8
- Includes fix for CVE-2022-40617, denial of service due to the
revocation plugin potentially using untrusted OCSP URIs and CRL
distribution points in CRLs. (closes: #1021271)
* Remove strongswan-scepclient package, replaced by a pki(1) command
* d/p/0006-fix-format-string-issue-in-enum_flags_to_string dropped, included
upstream
* remove dropped _copyright utility
* d/strongswan-pki.install: install est/estca manpages (RFC 7070)
* d/s-{started,swanctl}.lintian-overrides updated for new lintian
* d/copyright updated for new upstream release
Checksums-Sha1:
8399db837f4e3862be685b0676d3b8c985f0407a 3220 strongswan_5.9.8-1.dsc
897843f9cd4ccefe4317218ecccb4cba32d2dc41 4747096 strongswan_5.9.8.orig.tar.bz2
c67ef343ed5b12aecddf2b872462fba38050b5d3 659 strongswan_5.9.8.orig.tar.bz2.asc
1f8babd9d91935efa761749bb070fc85e0aa96b2 117068
strongswan_5.9.8-1.debian.tar.xz
63fb4a22e356af2ce095ef0b4fccfa8e57c3a014 17180
strongswan_5.9.8-1_amd64.buildinfo
Checksums-Sha256:
23aaa161ff07a47e6a2b9c4e9d5c8dfe8c870e9a720311b291e01a56cddfe4db 3220
strongswan_5.9.8-1.dsc
d3303a43c0bd7b75a12b64855e8edcb53696f06190364f26d1533bde1f2e453c 4747096
strongswan_5.9.8.orig.tar.bz2
0338545be1d68675e874fd3792a336e2a27ac3dae65c4e96c13592f710a0dbc9 659
strongswan_5.9.8.orig.tar.bz2.asc
2a35d4fa4e06cd274ee5ff87e08712ed92c4d6390db03bd6fce5fa3c9c6235bc 117068
strongswan_5.9.8-1.debian.tar.xz
120eaf2c99c900efb51a6fb62d16db0c3d317a5ec127c3f8d48300b08bcb9464 17180
strongswan_5.9.8-1_amd64.buildinfo
Files:
5817700843b50ac7f2195bbb9b7502ed 3220 net optional strongswan_5.9.8-1.dsc
f46b0d3e7aed88824650d0721c887443 4747096 net optional
strongswan_5.9.8.orig.tar.bz2
49e612097053bb8b6cc4eb8bd6f8455f 659 net optional
strongswan_5.9.8.orig.tar.bz2.asc
63fb2457393dd882ec8b4a7aa727e32b 117068 net optional
strongswan_5.9.8-1.debian.tar.xz
21fc321c1c60e5cb6492bf578d0d220f 17180 net optional
strongswan_5.9.8-1_amd64.buildinfo
-BEGIN PGP SIGNATURE-
iQEzBAEBCgAdFiEE8vi34Qgfo83x35gF3rYcyPpXRFsFAmM9ztMACgkQ3rYcyPpX
RFs7Lgf8DVkjFNfxtzvbm0t+uVwc0Q4JdLYCaaWl2NN5PnImDtgb01PuJqvZkc/n
Processed: src:openrazer: fails to migrate to testing for too long: unresolved RC bugs
Processing control commands:
> close -1 3.4.0+dfsg-1
Bug #1021321 [src:openrazer] src:openrazer: fails to migrate to testing for too
long: unresolved RC bugs
Marked as fixed in versions openrazer/3.4.0+dfsg-1.
Bug #1021321 [src:openrazer] src:openrazer: fails to migrate to testing for too
long: unresolved RC bugs
Marked Bug as done
> block -1 by 1018789 1020039
Bug #1021321 {Done: Paul Gevers } [src:openrazer]
src:openrazer: fails to migrate to testing for too long: unresolved RC bugs
1021321 was not blocked by any bugs.
1021321 was not blocking any bugs.
Added blocking bug(s) of 1021321: 1020039 and 1018789
--
1021321: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1021321
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Bug#1021321: src:openrazer: fails to migrate to testing for too long: unresolved RC bugs
Source: openrazer Version: 3.3.0+dfsg-2 Severity: serious Control: close -1 3.4.0+dfsg-1 Tags: sid bookworm User: release.debian@packages.debian.org Usertags: out-of-sync Control: block -1 by 1018789 1020039 Dear maintainer(s), The Release Team considers packages that are out-of-sync between testing and unstable for more than 60 days as having a Release Critical bug in testing [1]. Your package src:openrazer has been trying to migrate for 61 days [2]. Hence, I am filing this bug. Your package has unresolved RC bugs. If a package is out of sync between unstable and testing for a longer period, this usually means that bugs in the package in testing cannot be fixed via unstable. Additionally, blocked packages can have impact on other packages, which makes preparing for the release more difficult. Finally, it often exposes issues with the package and/or its (reverse-)dependencies. We expect maintainers to fix issues that hamper the migration of their package in a timely manner. This bug will trigger auto-removal when appropriate. As with all new bugs, there will be at least 30 days before the package is auto-removed. I have immediately closed this bug with the version in unstable, so if that version or a later version migrates, this bug will no longer affect testing. I have also tagged this bug to only affect sid and bookworm, so it doesn't affect (old-)stable. If you believe your package is unable to migrate to testing due to issues beyond your control, don't hesitate to contact the Release Team. Paul [1] https://lists.debian.org/debian-devel-announce/2020/02/msg5.html [2] https://qa.debian.org/excuses.php?package=openrazer OpenPGP_signature Description: OpenPGP digital signature
Processed: isc-dhcp: CVE-2022-2928 CVE-2022-2929
Processing control commands: > found -1 4.4.1-2.3 Bug #1021320 [src:isc-dhcp] isc-dhcp: CVE-2022-2928 CVE-2022-2929 Marked as found in versions isc-dhcp/4.4.1-2.3. > fixed -1 4.4.1-2.3+deb11u1 Bug #1021320 [src:isc-dhcp] isc-dhcp: CVE-2022-2928 CVE-2022-2929 The source 'isc-dhcp' and version '4.4.1-2.3+deb11u1' do not appear to match any binary packages Marked as fixed in versions isc-dhcp/4.4.1-2.3+deb11u1. -- 1021320: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1021320 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1021320: isc-dhcp: CVE-2022-2928 CVE-2022-2929
Source: isc-dhcp Version: 4.4.3-2 Severity: grave Tags: security upstream Justification: user security hole X-Debbugs-Cc: car...@debian.org, Debian Security Team Control: found -1 4.4.1-2.3 Control: fixed -1 4.4.1-2.3+deb11u1 Hi, The following vulnerabilities were published for isc-dhcp. CVE-2022-2928[0]: | An option refcount overflow exists in dhcpd CVE-2022-2929[1]: | DHCP memory leak 4.4.1-2.3+deb11u1 is uploaded to security-master and pending a DSA release. If needed I can try to contribute a NMU for unstable/bookworm. 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-2928 https://www.cve.org/CVERecord?id=CVE-2022-2928 https://kb.isc.org/docs/cve-2022-2928 [1] https://security-tracker.debian.org/tracker/CVE-2022-2929 https://www.cve.org/CVERecord?id=CVE-2022-2929 https://kb.isc.org/docs/cve-2022-2929 [2] https://lists.isc.org/pipermail/dhcp-announce/2022-October/000437.html Regards, Salvatore
Bug#1020202: marked as done (undercover-el: FTBFS: (file-missing "Opening input file" "No such file or directory" "/tmp/first-example-library-report.json"))
Your message dated Wed, 05 Oct 2022 23:35:47 +0500
with message-id <87wn9euni4.fsf@localhost>
and subject line Re: Bug#1020202: undercover-el: FTBFS: (file-missing
"Opening input file" "No such file or directory"
"/tmp/first-example-library-report.json")
has caused the Debian Bug report #1020202,
regarding undercover-el: FTBFS: (file-missing "Opening input file" "No such
file or directory" "/tmp/first-example-library-report.json")
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.)
--
1020202: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1020202
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: undercover-el
Version: 0.8.1-1
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 binary
> dh binary --with elpa
>dh_update_autotools_config
>dh_autoreconf
>dh_elpa_test
> emacs -batch -Q -l package --eval "(add-to-list 'package-directory-list
> \"/usr/share/emacs/site-lisp/elpa\")" --eval "(add-to-list
> 'package-directory-list \"/usr/share/emacs/site-lisp/elpa-src\")" -f
> package-initialize -L . -L test --eval "(load \"undercover.el\")" -l
> test/first-example-library-test.el --eval \(ert-run-tests-batch-and-exit\)
> Loading /<>/undercover.el (source)...
> UNDERCOVER: Preparing to instrument 1 file.
> UNDERCOVER: Instrumenting
> /<>/test/first-example-library/first-example-library.el for
> collecting coverage information.
> UNDERCOVER: Error while loading
> /<>/test/first-example-library/first-example-library.el for
> coverage:
> UNDERCOVER: Cannot find suitable directory for output in
> ‘native-comp-eln-load-path’
> UNDERCOVER: The problem may be due to edebug failing to parse the file.
> UNDERCOVER: You can try to narrow down the problem using the following steps:
> UNDERCOVER: 1. Open
> "/<>/test/first-example-library/first-example-library.el" in an
> Emacs buffer;
> UNDERCOVER: 2. Run M-: ‘(require 'edebug)’;
> UNDERCOVER: 3. Run M-x ‘edebug-all-defs’;
> UNDERCOVER: 4. Run M-x ‘toggle-debug-on-error’.
> UNDERCOVER: 5. Run M-x ‘eval-buffer’;
> UNDERCOVER: 6. In the *Backtrace* buffer, find a numeric position,
> UNDERCOVER:then M-x ‘goto-char’ to it.
> Running 11 tests (2022-09-17 20:06:21+, selector ‘t’)
>passed 1/11 test/1-setup/edebug-handlers-are-setted (0.97 sec)
>passed 2/11 test/2-run/result-is-correct (0.97 sec)
> Test test/3-verify/check-coverage-statistics backtrace:
> signal(wrong-type-argument (hash-table-p nil))
> apply(signal (wrong-type-argument (hash-table-p nil)))
> (setq value-67 (apply fn-65 args-66))
> (unwind-protect (setq value-67 (apply fn-65 args-66)) (setq form-des
> (if (unwind-protect (setq value-67 (apply fn-65 args-66)) (setq form
> (let (form-description-69) (if (unwind-protect (setq value-67 (apply
> (let ((value-67 'ert-form-evaluation-aborted-68)) (let (form-descrip
> (let* ((fn-65 #'=) (args-66 (condition-case err (let ((signal-hook-f
> (let ((line (car --dolist-tail--))) (let* ((fn-65 #'=) (args-66 (con
> (while --dolist-tail-- (let ((line (car --dolist-tail--))) (let* ((f
> (let ((--dolist-tail-- '(15 16 17 18 19 20))) (while --dolist-tail--
> (let ((example-library-statistics (gethash (file-truename first-exam
> (let ((lexical-binding t)) (undercover--collect-files-coverage under
> (closure (t) nil (let ((lexical-binding t)) (undercover--collect-fil
> ert--run-test-internal(#s(ert--test-execution-info :test #s(ert-test
> ert-run-test(#s(ert-test :name test/3-verify/check-coverage-statisti
> ert-run-or-rerun-test(#s(ert--stats :selector t :tests [... ... ...
> ert-run-tests(t #f(compiled-function (event-type event-args) #
> ert-run-tests-batch(nil)
> ert-run-tests-batch-and-exit()
> command-line-1(("-l" "package" "--eval" "(add-to-list 'package-direc
> command-line()
> normal-top-level()
> Test test/3-verify/check-coverage-statistics condition:
> (wrong-type-argument hash-table-p nil)
>FAILED 3/11 test/3-verify/check-coverage-statistics (0.000339 sec)
>passed 4/11 test/3-verify/check-distance-stop-points-number-of-covers
> (0.57 sec)
> UNDERCOVER: Detected CI: Travis CI
>passed 5/11 test/3-verify/check-environment-variables (0.000168 sec)
> UNDERCOVER: Generating report.
> Test test/3-verify/check-lcov-report-file backtrace:
> signal(ert-test-failed (((should (string-equal report (format "SF:%s
>
Bug#1021317: salt-master: Fails to start with "zmq.error.ZMQError: Invalid argument"
Package: salt-master
Version: 3004.1+dfsg-2
Severity: grave
Justification: renders package unusable
Dear Maintainer,
salt-master fails to start.
journalctl shows:
```
spal. 05 20:47:04 salt-master[11925]: Traceback (most recent call last):
spal. 05 20:47:04 salt-master[11925]: File
"/usr/lib/python3.10/multiprocessing/process.py", line 314, in _bootstrap
spal. 05 20:47:04 salt-master[11925]: self.run()
spal. 05 20:47:04 salt-master[11925]: File
"/usr/lib/python3.10/multiprocessing/process.py", line 108, in run
spal. 05 20:47:04 salt-master[11925]: self._target(*self._args,
**self._kwargs)
spal. 05 20:47:04 salt-master[11925]: File
"/usr/lib/python3/dist-packages/salt/transport/zeromq.py", line 899, in
_publish_daemon
spal. 05 20:47:04 salt-master[11925]: pub_sock.setsockopt(zmq.HWM,
self.opts.get("pub_hwm", 1000))
spal. 05 20:47:04 salt-master[11925]: File "zmq/backend/cython/socket.pyx",
line 453, in zmq.backend.cython.socket.Socket.set
spal. 05 20:47:04 salt-master[11925]: File "zmq/backend/cython/socket.pyx",
line 285, in zmq.backend.cython.socket._setsockopt
spal. 05 20:47:04 salt-master[11925]: File "zmq/backend/cython/checkrc.pxd",
line 28, in zmq.backend.cython.checkrc._check_rc
spal. 05 20:47:04 salt-master[11925]: zmq.error.ZMQError: Invalid argument
```
-- System Information:
Debian Release: bookworm/sid
APT prefers unstable-debug
APT policy: (500, 'unstable-debug'), (500, 'unstable'), (1,
'experimental-debug'), (1, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386
Kernel: Linux 5.19.0-2-amd64 (SMP w/8 CPU threads; PREEMPT)
Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE,
TAINT_UNSIGNED_MODULE
Locale: LANG=lt_LT.UTF-8, LC_CTYPE=lt_LT.UTF-8 (charmap=UTF-8), LANGUAGE=lt
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
Versions of packages salt-master depends on:
ii adduser3.129
ii init-system-helpers1.65.2
ii python33.10.6-1
ii python3-pycryptodome 3.11.0+dfsg1-3+b1
ii python3-systemd235-1
ii python3-zmq24.0.1-1
ii salt-common3004.1+dfsg-2
ii sysvinit-utils [lsb-base] 3.05-6
Versions of packages salt-master recommends:
ii python3-pygit2 1.10.1-2
salt-master suggests no packages.
-- no debconf information
Bug#1021316: rust-kvm-bindings: FTBFS on i386
Source: rust-kvm-bindings
Version: 0.5.0-1
Severity: serious
Tags: ftbfs
Justification: fails to build from source (but built successfully in the past)
X-Debbugs-Cc: sramac...@debian.org
https://buildd.debian.org/status/fetch.php?pkg=rust-kvm-bindings=i386=0.5.0-1=1664239343=0
x86::bindings::bindgen_test_layout_kvm_xen_vcpu_attr__bindgen_ty_1__bindgen_ty_1
stdout
thread
'x86::bindings::bindgen_test_layout_kvm_xen_vcpu_attr__bindgen_ty_1__bindgen_ty_1'
panicked at 'assertion failed: `(left == right)`
left: `4`,
right: `8`: Alignment of kvm_xen_vcpu_attr__bindgen_ty_1__bindgen_ty_1',
src/x86/bindings.rs:11503:5
stack backtrace:
0: rust_begin_unwind
at /usr/src/rustc-1.61.0/library/std/src/panicking.rs:584:5
1: core::panicking::panic_fmt
at /usr/src/rustc-1.61.0/library/core/src/panicking.rs:143:14
2: core::panicking::assert_failed_inner
3: core::panicking::assert_failed
at /usr/src/rustc-1.61.0/library/core/src/panicking.rs:182:5
4:
kvm_bindings::x86::bindings::bindgen_test_layout_kvm_xen_vcpu_attr__bindgen_ty_1__bindgen_ty_1
at
/usr/share/cargo/registry/kvm-bindings-0.5.0/src/x86/bindings.rs:11503:5
5:
kvm_bindings::x86::bindings::bindgen_test_layout_kvm_xen_vcpu_attr__bindgen_ty_1__bindgen_ty_1::{{closure}}
at
/usr/share/cargo/registry/kvm-bindings-0.5.0/src/x86/bindings.rs:11494:1
6: core::ops::function::FnOnce::call_once
at /usr/src/rustc-1.61.0/library/core/src/ops/function.rs:227:5
7: core::ops::function::FnOnce::call_once
at /usr/src/rustc-1.61.0/library/core/src/ops/function.rs:227:5
note: Some details are omitted, run with `RUST_BACKTRACE=full` for a verbose
backtrace.
failures:
x86::bindings::bindgen_test_layout___kernel_fd_set
x86::bindings::bindgen_test_layout_kvm_arm_device_addr
x86::bindings::bindgen_test_layout_kvm_breakpoint
x86::bindings::bindgen_test_layout_kvm_clear_dirty_log
x86::bindings::bindgen_test_layout_kvm_clear_dirty_log__bindgen_ty_1
x86::bindings::bindgen_test_layout_kvm_clock_data
x86::bindings::bindgen_test_layout_kvm_coalesced_mmio
x86::bindings::bindgen_test_layout_kvm_coalesced_mmio_ring
x86::bindings::bindgen_test_layout_kvm_coalesced_mmio_zone
x86::bindings::bindgen_test_layout_kvm_config_tlb
x86::bindings::bindgen_test_layout_kvm_debug_exit_arch
x86::bindings::bindgen_test_layout_kvm_debug_guest
x86::bindings::bindgen_test_layout_kvm_debugregs
x86::bindings::bindgen_test_layout_kvm_device_attr
x86::bindings::bindgen_test_layout_kvm_dirty_gfn
x86::bindings::bindgen_test_layout_kvm_dirty_log
x86::bindings::bindgen_test_layout_kvm_dirty_log__bindgen_ty_1
x86::bindings::bindgen_test_layout_kvm_dirty_tlb
x86::bindings::bindgen_test_layout_kvm_dtable
x86::bindings::bindgen_test_layout_kvm_enable_cap
x86::bindings::bindgen_test_layout_kvm_enc_region
x86::bindings::bindgen_test_layout_kvm_fpu
x86::bindings::bindgen_test_layout_kvm_guest_debug
x86::bindings::bindgen_test_layout_kvm_guest_debug_arch
x86::bindings::bindgen_test_layout_kvm_hyperv_exit
x86::bindings::bindgen_test_layout_kvm_hyperv_exit__bindgen_ty_1
x86::bindings::bindgen_test_layout_kvm_hyperv_exit__bindgen_ty_1__bindgen_ty_1
x86::bindings::bindgen_test_layout_kvm_hyperv_exit__bindgen_ty_1__bindgen_ty_2
x86::bindings::bindgen_test_layout_kvm_hyperv_exit__bindgen_ty_1__bindgen_ty_3
x86::bindings::bindgen_test_layout_kvm_ioapic_state
x86::bindings::bindgen_test_layout_kvm_ioapic_state__bindgen_ty_1
x86::bindings::bindgen_test_layout_kvm_ioeventfd
x86::bindings::bindgen_test_layout_kvm_irq_routing
x86::bindings::bindgen_test_layout_kvm_irq_routing_entry
x86::bindings::bindgen_test_layout_kvm_irq_routing_entry__bindgen_ty_1
x86::bindings::bindgen_test_layout_kvm_irq_routing_s390_adapter
x86::bindings::bindgen_test_layout_kvm_irqchip
x86::bindings::bindgen_test_layout_kvm_irqchip__bindgen_ty_1
x86::bindings::bindgen_test_layout_kvm_memory_alias
x86::bindings::bindgen_test_layout_kvm_memory_region
x86::bindings::bindgen_test_layout_kvm_msr_entry
x86::bindings::bindgen_test_layout_kvm_msr_filter
x86::bindings::bindgen_test_layout_kvm_msr_filter_range
x86::bindings::bindgen_test_layout_kvm_msrs
x86::bindings::bindgen_test_layout_kvm_nested_state
x86::bindings::bindgen_test_layout_kvm_nested_state__bindgen_ty_1
x86::bindings::bindgen_test_layout_kvm_one_reg
x86::bindings::bindgen_test_layout_kvm_pit_channel_state
x86::bindings::bindgen_test_layout_kvm_pit_state
x86::bindings::bindgen_test_layout_kvm_pit_state2
x86::bindings::bindgen_test_layout_kvm_pmu_event_filter
x86::bindings::bindgen_test_layout_kvm_ppc_resize_hpt
x86::bindings::bindgen_test_layout_kvm_ppc_smmu_info
x86::bindings::bindgen_test_layout_kvm_pv_cmd
x86::bindings::bindgen_test_layout_kvm_reg_list
Processed: severity of 1021312 is important
Processing commands for cont...@bugs.debian.org: > severity 1021312 important Bug #1021312 [src:qtquickcontrols-opensource-src] qtquickcontrols-opensource-src: FTBFS on hppa - Tests_TreeView::test_pressAndHold Severity set to 'important' from 'serious' > thanks Stopping processing here. Please contact me if you need assistance. -- 1021312: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1021312 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1020819: subtitlecomposer: Cannot load any video: "Option refcounted_frames not found" error (removed from FFmpeg)
On Mon, 26 Sep 2022 21:40:03 -0700 Cy Kyanos wrote: > Package: subtitlecomposer > Version: 0.7.1-3 > Severity: grave > Tags: fixed-upstream patch > Justification: renders package unusable > Forwarded: https://invent.kde.org/multimedia/subtitlecomposer/-/issues/68 I can confirm this issue exists, although I don't think it's 'grave' as I haven't used this functionality before, but do use subtitlecomposer on a regular basis. I've created a MR to add the patch to the Debian package here: https://salsa.debian.org/qt-kde-team/extras/subtitlecomposer/-/merge_requests/1/diffs signature.asc Description: This is a digitally signed message part.
Bug#1021314: hol88: license issues
Source: hol88
Severity: serious
Version: 2.02.19940316-35.1
hol88 has one certain license issue: It bundles an old copy of NOWEB, which has
a non-free license.
Please repack so that NOWEB is not included.
Furthermore, the license of hol88 might be non-free as well. debian/copyright claims it is public domain, which might
not necessarily be true. There is a license included in License/{READ-ME,License.tex}. Please check carefully if this
can stay in main at all.
Bug#1013612: marked as done (guile-gnome-platform: FTBFS: FAIL: wrapset.scm)
Your message dated Wed, 05 Oct 2022 17:01:19 + with message-id and subject line Bug#1021047: Removed package(s) from unstable has caused the Debian Bug report #1013612, regarding guile-gnome-platform: FTBFS: FAIL: wrapset.scm 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.) -- 1013612: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1013612 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: guile-gnome-platform Version: 2.16.5-4 Severity: serious Justification: FTBFS Tags: bookworm sid ftbfs User: lu...@debian.org Usertags: ftbfs-20220624 ftbfs-bookworm Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > make[5]: Entering directory '/<>/gtk/tests/gtk' > ;;; note: auto-compilation is enabled, set GUILE_AUTO_COMPILE=0 > ;;; or pass the --no-auto-compile argument to disable. > ;;; compiling /<>/gtk/tests/gtk/./wrapset.scm > ;;; WARNING: compilation of /<>/gtk/tests/gtk/./wrapset.scm > failed: > ;;; failed to create path for auto-compiled file > "/<>/gtk/tests/gtk/./wrapset.scm" > ;;; compiling /usr/share/guile/site/unit-test.scm > ;;; WARNING: compilation of /usr/share/guile/site/unit-test.scm failed: > ;;; failed to create path for auto-compiled file > "/usr/share/guile/site/unit-test.scm" > ;;; compiling /usr/share/guile/site/apicheck.scm > ;;; WARNING: compilation of /usr/share/guile/site/apicheck.scm failed: > ;;; failed to create path for auto-compiled file > "/usr/share/guile/site/apicheck.scm" > > Running test suite: main-suite > > Running test suite: -suite -- > Running test case: test-wrapset-api > ;;; compiling /<>/gtk/gnome/gtk.scm > ;;; WARNING: compilation of /<>/gtk/gnome/gtk.scm failed: > ;;; failed to create path for auto-compiled file > "/<>/gtk/gnome/gtk.scm" > ;;; compiling /<>/glib/gnome/gobject.scm > ;;; WARNING: compilation of /<>/glib/gnome/gobject.scm failed: > ;;; failed to create path for auto-compiled file > "/<>/glib/gnome/gobject.scm" > ;;; compiling /<>/glib/gnome/gobject/gtype.scm > ;;; WARNING: compilation of /<>/glib/gnome/gobject/gtype.scm > failed: > ;;; failed to create path for auto-compiled file > "/<>/glib/gnome/gobject/gtype.scm" > ;;; compiling /<>/glib/gnome/gobject/utils.scm > ;;; WARNING: compilation of /<>/glib/gnome/gobject/utils.scm > failed: > ;;; failed to create path for auto-compiled file > "/<>/glib/gnome/gobject/utils.scm" > ;;; compiling /<>/glib/gnome/gobject/config.scm > ;;; WARNING: compilation of /<>/glib/gnome/gobject/config.scm > failed: > ;;; failed to create path for auto-compiled file > "/<>/glib/gnome/gobject/config.scm" > ;;; compiling /<>/glib/gnome/gobject/gvalue.scm > ;;; WARNING: compilation of /<>/glib/gnome/gobject/gvalue.scm > failed: > ;;; failed to create path for auto-compiled file > "/<>/glib/gnome/gobject/gvalue.scm" > ;;; compiling /<>/glib/gnome/gobject/gclosure.scm > ;;; WARNING: compilation of /<>/glib/gnome/gobject/gclosure.scm > failed: > ;;; failed to create path for auto-compiled file > "/<>/glib/gnome/gobject/gclosure.scm" > ;;; compiling /<>/glib/gnome/gobject/gsignal.scm > ;;; WARNING: compilation of /<>/glib/gnome/gobject/gsignal.scm > failed: > ;;; failed to create path for auto-compiled file > "/<>/glib/gnome/gobject/gsignal.scm" > ;;; compiling /<>/glib/gnome/gobject/gparameter.scm > ;;; WARNING: compilation of > /<>/glib/gnome/gobject/gparameter.scm failed: > ;;; failed to create path for auto-compiled file > "/<>/glib/gnome/gobject/gparameter.scm" > ;;; compiling /<>/glib/gnome/gobject/gobject.scm > ;;; WARNING: compilation of /<>/glib/gnome/gobject/gobject.scm > failed: > ;;; failed to create path for auto-compiled file > "/<>/glib/gnome/gobject/gobject.scm" > ;;; compiling /<>/glib/gnome/gw/support/modules.scm > ;;; WARNING: compilation of > /<>/glib/gnome/gw/support/modules.scm failed: > ;;; failed to create path for auto-compiled file > "/<>/glib/gnome/gw/support/modules.scm" > ;;; compiling /<>/glib/gnome/gobject/generics.scm > ;;; WARNING: compilation of /<>/glib/gnome/gobject/generics.scm > failed: > ;;; failed to create path for auto-compiled file > "/<>/glib/gnome/gobject/generics.scm" > ;;; compiling /<>/gtk/gnome/gw/gdk.scm > ;;; WARNING: compilation of /<>/gtk/gnome/gw/gdk.scm failed: > ;;; failed to create path for auto-compiled file > "/<>/gtk/gnome/gw/gdk.scm" > ;;; compiling /usr/share/guile/site/g-wrap/gw/standard.scm > ;;; WARNING: compilation of /usr/share/guile/site/g-wrap/gw/standard.scm > failed: > ;;;
Bug#1012193: marked as done (llvm-toolchain-12: do not include in bookworm)
Your message dated Wed, 05 Oct 2022 16:58:39 + with message-id and subject line Bug#1012404: Removed package(s) from unstable has caused the Debian Bug report #1012193, regarding llvm-toolchain-12: do not include in bookworm 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.) -- 1012193: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1012193 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: llvm-toolchain-12 Version: 1:12.0.1-20 Severity: serious X-Debbugs-Cc: sramac...@debian.org With llvm-toolchain-14 almost ready to migrate, let's reduce the number of llvm-toolchain versions in testing. Cheers -- Sebastian Ramacher --- End Message --- --- Begin Message --- Version: 1:12.0.1-21+rm Dear submitter, as the package llvm-toolchain-12 has just been removed from the Debian archive unstable we hereby close the associated bug reports. We are sorry that we couldn't deal with your issue properly. For details on the removal, please see https://bugs.debian.org/1012404 The version of this package that was in Debian prior to this removal can still be found using http://snapshot.debian.org/. Please note that the changes have been done on the master archive and will not propagate to any mirrors until the next dinstall run at the earliest. This message was generated automatically; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org. Debian distribution maintenance software pp. Thorsten Alteholz (the ftpmaster behind the curtain)--- End Message ---
Bug#1014906: marked as done (opencl-clang-11: do not release with bookworm)
Your message dated Wed, 05 Oct 2022 16:52:38 + with message-id and subject line Bug#1021254: Removed package(s) from unstable has caused the Debian Bug report #1014906, regarding opencl-clang-11: do not release with bookworm 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.) -- 1014906: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1014906 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: opencl-clang-11 Version: 11.0.0-2 Severity: serious X-Debbugs-Cc: sramac...@debian.org Bookworm will be released with llvm-toolchains 13, 14 and 15. llvm-toolchain-11 won't be part of bookworm. So opencl-clang-11 will also not be part of bookworm. Cheers -- Sebastian Ramacher --- End Message --- --- Begin Message --- Version: 11.0.0-3+rm Dear submitter, as the package opencl-clang-11 has just been removed from the Debian archive unstable we hereby close the associated bug reports. We are sorry that we couldn't deal with your issue properly. For details on the removal, please see https://bugs.debian.org/1021254 The version of this package that was in Debian prior to this removal can still be found using http://snapshot.debian.org/. Please note that the changes have been done on the master archive and will not propagate to any mirrors until the next dinstall run at the earliest. This message was generated automatically; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org. Debian distribution maintenance software pp. Thorsten Alteholz (the ftpmaster behind the curtain)--- End Message ---
Bug#1014905: marked as done (spirv-llvm-translator-11: do not release with bookworm)
Your message dated Wed, 05 Oct 2022 16:53:41 + with message-id and subject line Bug#1021252: Removed package(s) from unstable has caused the Debian Bug report #1014905, regarding spirv-llvm-translator-11: do not release with bookworm 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.) -- 1014905: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1014905 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: spirv-llvm-translator-11 Version: 11.0.0-2 Severity: serious X-Debbugs-Cc: sramac...@debian.org Bookworm will be released with llvm-toolchains 13, 14 and 15. llvm-toolchain-11 won't be part of bookworm. So spirv-llvm-translator-11 will also not be part of bookworm. Cheers -- Sebastian Ramacher --- End Message --- --- Begin Message --- Version: 11.0.0-4+rm Dear submitter, as the package spirv-llvm-translator-11 has just been removed from the Debian archive unstable we hereby close the associated bug reports. We are sorry that we couldn't deal with your issue properly. For details on the removal, please see https://bugs.debian.org/1021252 The version of this package that was in Debian prior to this removal can still be found using http://snapshot.debian.org/. Please note that the changes have been done on the master archive and will not propagate to any mirrors until the next dinstall run at the earliest. This message was generated automatically; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org. Debian distribution maintenance software pp. Thorsten Alteholz (the ftpmaster behind the curtain)--- End Message ---
Bug#1020313: marked as done (Should openbsc be shipped in bookworm?)
Your message dated Wed, 05 Oct 2022 16:51:32 + with message-id and subject line Bug#1021267: Removed package(s) from unstable has caused the Debian Bug report #1020313, regarding Should openbsc be shipped in bookworm? 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.) -- 1020313: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1020313 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: openbsc Severity: serious Tags: bookworm sid https://osmocom.org/projects/openbsc This is a legacy all-in-one implementation of the Osmocom BSC + MSC + HLR, instead refer to OsmoBSC, OsmoMSC, OsmoHLR. The new implementation seems to already be packaged. --- End Message --- --- Begin Message --- Version: 1.4.1+dfsg1-2+rm Dear submitter, as the package openbsc has just been removed from the Debian archive unstable we hereby close the associated bug reports. We are sorry that we couldn't deal with your issue properly. For details on the removal, please see https://bugs.debian.org/1021267 The version of this package that was in Debian prior to this removal can still be found using http://snapshot.debian.org/. Please note that the changes have been done on the master archive and will not propagate to any mirrors until the next dinstall run at the earliest. This message was generated automatically; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org. Debian distribution maintenance software pp. Thorsten Alteholz (the ftpmaster behind the curtain)--- End Message ---
Bug#1013006: marked as done (openbsc: ftbfs with GCC-12)
Your message dated Wed, 05 Oct 2022 16:51:32 +
with message-id
and subject line Bug#1021267: Removed package(s) from unstable
has caused the Debian Bug report #1013006,
regarding openbsc: ftbfs with GCC-12
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)
--
1013006: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1013006
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:openbsc
Version: 1.4.1+dfsg1-2
Severity: normal
Tags: sid bookworm
User: debian-...@lists.debian.org
Usertags: ftbfs-gcc-12
[This bug is targeted to the upcoming bookworm release]
Please keep this issue open in the bug tracker for the package it
was filed for. If a fix in another package is required, please
file a bug for the other package (or clone), and add a block in this
package. Please keep the issue open until the package can be built in
a follow-up test rebuild.
The package fails to build in a test rebuild on at least amd64 with
gcc-12/g++-12, but succeeds to build with gcc-11/g++-11. The
severity of this report will be raised before the bookworm release.
The full build log can be found at:
http://qa-logs.debian.net/2022/06/09/gcc12/openbsc_1.4.1+dfsg1-2_unstable_gcc12.log
The last lines of the build log are at the end of this report.
To build with GCC 11, either set CC=gcc-11 CXX=g++-11 explicitly,
or install the gcc, g++, gfortran, ... packages from experimental.
apt-get -t=experimental install g++
Common build failures are new warnings resulting in build failures with
-Werror turned on, or new/dropped symbols in Debian symbols files.
For other C/C++ related build failures see the porting guide at
http://gcc.gnu.org/gcc-11/porting_to.html
GCC 11 defaults to the GNU++17 standard. If your package installs
header files in /usr/include, please don't work around C++17 issues
by choosing a lower C++ standard for the package build, but fix these
issues to build with the C++17 standard.
[...]
from e1_config.c:26:
/usr/include/osmocom/abis/e1_input.h:291:32: note: expected ‘int (*)(struct
subch_demux *, int, const ubit_t *, int, void *)’ {aka ‘int (*)(struct
subch_demux *, int, const unsigned char *, int, void *)’} but argument is of
type ‘int (*)(struct subch_demux *, int, uint8_t *, int, void *)’ {aka ‘int
(*)(struct subch_demux *, int, unsigned char *, int, void *)’}
291 | int (*trau_rcv_cb)(struct subch_demux *dmx,
int ch,
|
~~^
292 | const ubit_t *data, int
len, void *_priv));
|
~
bsc_api.c: In function ‘lchan_to_chosen_channel’:
bsc_api.c:55:9: warning: enumeration value ‘GSM48_CMODE_SPEECH_V1_VAMOS’ not
handled in switch [-Wswitch]
55 | switch (lchan->tch_mode) {
| ^~
bsc_api.c:55:9: warning: enumeration value ‘GSM48_CMODE_SPEECH_V2_VAMOS’ not
handled in switch [-Wswitch]
bsc_api.c:55:9: warning: enumeration value ‘GSM48_CMODE_SPEECH_V3_VAMOS’ not
handled in switch [-Wswitch]
bsc_api.c:55:9: warning: enumeration value ‘GSM48_CMODE_SPEECH_V5_VAMOS’ not
handled in switch [-Wswitch]
gcc -DHAVE_CONFIG_H -I. -I../.. -I../../include -I../.. -Wdate-time
-D_FORTIFY_SOURCE=2 -Wall -pthread -I/usr/include/ -I/usr/include/
-I/usr/include/ -I/usr/include/ -g -O2 -ffile-prefix-map=/<>=.
-fstack-protector-strong -Wformat -Werror=format-security -Werror=implicit
-Werror=maybe-uninitialized -Werror=memset-transposed-args
-Werror=null-dereference -Werror=sizeof-array-argument
-Werror=sizeof-pointer-memaccess -c -o bsc_msc.o bsc_msc.c
gcc -DHAVE_CONFIG_H -I. -I../.. -I../../include -I../.. -Wdate-time
-D_FORTIFY_SOURCE=2 -Wall -pthread -I/usr/include/ -I/usr/include/
-I/usr/include/ -I/usr/include/ -g -O2 -ffile-prefix-map=/<>=.
-fstack-protector-strong -Wformat -Werror=format-security -Werror=implicit
-Werror=maybe-uninitialized -Werror=memset-transposed-args
-Werror=null-dereference -Werror=sizeof-array-argument
-Werror=sizeof-pointer-memaccess -c -o bsc_vty.o bsc_vty.c
gcc -DHAVE_CONFIG_H -I. -I../.. -I../../include -I../.. -Wdate-time
-D_FORTIFY_SOURCE=2 -Wall -pthread -I/usr/include/ -I/usr/include/
-I/usr/include/ -I/usr/include/ -g -O2 -ffile-prefix-map=/<>=.
-fstack-protector-strong -Wformat -Werror=format-security -Werror=implicit
-Werror=maybe-uninitialized -Werror=memset-transposed-args
-Werror=null-dereference -Werror=sizeof-array-argument
Bug#1020314: marked as done (osmo-bts: Stale build dependency on openbsc-dev)
Your message dated Wed, 05 Oct 2022 15:10:14 + with message-id and subject line Bug#1020314: fixed in osmo-bts 1.5.0+dfsg1-1 has caused the Debian Bug report #1020314, regarding osmo-bts: Stale build dependency on openbsc-dev to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 1020314: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1020314 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: osmo-bts Version: 1.4.1+dfsg1-1 Severity: serious Control: block 1020313 by -1 osmo-bts has a build dependency on openbsc-dev that seems to be unused. --- End Message --- --- Begin Message --- Source: osmo-bts Source-Version: 1.5.0+dfsg1-1 Done: Thorsten Alteholz We believe that the bug you reported is fixed in the latest version of osmo-bts, 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 1020...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Thorsten Alteholz (supplier of updated osmo-bts 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: Tue, 04 Oct 2022 22:22:51 +0200 Source: osmo-bts Architecture: source Version: 1.5.0+dfsg1-1 Distribution: experimental Urgency: medium Maintainer: Debian Mobcom Maintainers Changed-By: Thorsten Alteholz Closes: 1020314 Changes: osmo-bts (1.5.0+dfsg1-1) experimental; urgency=medium . * New upstream release. * debian/control: use at least libosmocore 1.7.0 * debian/control: use at least libosmo-abis-dev 1.3.0 + debian/control: remove dependency to openbsc-dev (Closes: #1020314) Checksums-Sha1: 652fb9161869ca477e5f3545c5cb6d9ae59b47d2 2332 osmo-bts_1.5.0+dfsg1-1.dsc 49e76bfecec6917e1ceaaa4982da95052f8bd735 386932 osmo-bts_1.5.0+dfsg1.orig.tar.xz 2c8d7aec766c3b922294d16b7a8068418d583108 5424 osmo-bts_1.5.0+dfsg1-1.debian.tar.xz e3a51ea30d0c23898469ed1830a0fb99e5c20abd 7493 osmo-bts_1.5.0+dfsg1-1_amd64.buildinfo Checksums-Sha256: 6edfb9b14390698c54c59512c8c294cd859f93d77419097b8ef9c6defe5be560 2332 osmo-bts_1.5.0+dfsg1-1.dsc cd2094438206ab2d12e2a2afe195806c747435545bdded587a0caa29102c003b 386932 osmo-bts_1.5.0+dfsg1.orig.tar.xz 858657cd6a455b7f300ac1d8091f6ce8210a7e77a3d56094edbc9b0bff05cb1c 5424 osmo-bts_1.5.0+dfsg1-1.debian.tar.xz 5e02b71f9db45f94b660163be920553c29fd7c1b450b0ae6e2f074df85257cc3 7493 osmo-bts_1.5.0+dfsg1-1_amd64.buildinfo Files: e6b51ab1f043d253b06e367d265b2255 2332 net optional osmo-bts_1.5.0+dfsg1-1.dsc 8d48d2ead6a3536b35ff3853d272d68d 386932 net optional osmo-bts_1.5.0+dfsg1.orig.tar.xz 63f4b875d1c2de69f0a10b8930391c07 5424 net optional osmo-bts_1.5.0+dfsg1-1.debian.tar.xz 4a3ce48824d0e838f137cd83b2dfb9f7 7493 net optional osmo-bts_1.5.0+dfsg1-1_amd64.buildinfo -BEGIN PGP SIGNATURE- iQKnBAEBCgCRFiEEYgH7/9u94Hgi6ruWlvysDTh7WEcFAmM9lJ5fFIAALgAo aXNzdWVyLWZwckBub3RhdGlvbnMub3BlbnBncC5maWZ0aGhvcnNlbWFuLm5ldDYy MDFGQkZGREJCREUwNzgyMkVBQkI5Njk2RkNBQzBEMzg3QjU4NDcTHGRlYmlhbkBh bHRlaG9sei5kZQAKCRCW/KwNOHtYR4LxEACLk1zHHANkUh1gS4tkWpqN9ADWZlG0 HQj7TEbNujS+Us2X0IO1Po6VbTQ2hBgXZ7YUVBmLtbxR9Ykg6XmUzeG16FXkTg+s 8Q/sqkv0wKqtKpyRRJ78J2pMLRU7l++0IxAYEz+6nvnQzAr+uetCqY5v5lxNfkqJ mApfaizYDOJtaaClRtRqGXkPdUPTg4Vaj7ZMo1Qvwv6VOhY7uo6xNfRNvsrn7mVo v1Cgnc5l8FgRcmKYo29HiMhvzhLnMAG4/PpTFZCNOHAcyvTX66sJUSUD8WmJxgve ebNW/N0MMYf4w2CpAn/FGlenzq74yrgkuDlXQo4wTNmy0XPqA6l9tkSgs/xOb5yh FKcRsRndMK+XS8uU4MMqds0piyT4Vu2URV5OLY5H3HxJZIVVzRnzL6ZPVI9sOvO7 Ot9UIkTPuRDZwK3Z9BjFNOwh8q0t53026ZEYT9oIxp01F8XagRqUpJGqrxxCjfzv z4GkrrdiFEQy2adu9cZ9jnsBuNqs7j8pUvsuz6vWpbF7LuEqJtmqgg88A3iW+gaz JciE8cJj4SDT0nLIPNOm3TSj4i9+dZdDZ3eazNt5x18de+nNCdGLN0/a2tDWiNq+ nhaIDYbG/4F5NoGamenbS9Y54w6EGtvitelzJG5PKYMtVHbXv/Vx05APn77gAMTs Thdk7Y5z4h0RGg== =CC1Q -END PGP SIGNATURE End Message ---
Processed: Re: Bug#1021310: libsdl2: FTBFS on hppa - testevdev: FAILED: 1
Processing control commands: > severity -1 normal Bug #1021310 [src:libsdl2] libsdl2: FTBFS on hppa - testevdev: FAILED: 1 Severity set to 'normal' from 'serious' > tags -1 + help Bug #1021310 [src:libsdl2] libsdl2: FTBFS on hppa - testevdev: FAILED: 1 Added tag(s) help. -- 1021310: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1021310 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1021310: libsdl2: FTBFS on hppa - testevdev: FAILED: 1
Control: severity -1 normal Control: tags -1 + help On Wed, 05 Oct 2022 at 14:43:00 +, John David Anglin wrote: > Justification: fails to build from source (but built successfully in the past) hppa is not a release architecture, so FTBFS on hppa is not RC. This test-case seems to have been failing on hppa around 75% of the time since it was added. I don't know why it would do that, because this test-case should be deterministic: it's inspecting a simulation of the capabilitities info that we would have received from the kernel for a particular input device, and running SDL's algorithm to guess what type of input device it represents (keyboard, mouse, gamepad, etc.). When it fails on hppa, the failure mode is that none of the bits representing a device type get set. It seems to be reliable on release architectures, including i386 which is 32-bit and s390x which is big-endian. Non-release architecture porters are welcome to investigate why this is going wrong on their favourite architecture, and if the root cause turns out to be a bug in SDL, I'm sure upstream would appreciate a patch. smcv
Bug#1021312: qtquickcontrols-opensource-src: FTBFS on hppa - Tests_TreeView::test_pressAndHold
Source: qtquickcontrols-opensource-src Version: 5.15.6-2 Severity: serious Tags: ftbfs Justification: fails to build from source (but built successfully in the past) Dear Maintainer, Testsuite fails with following error: PASS : qtquickcontrols::Tests_TreeView::test_keys_navigation() FAIL! : qtquickcontrols::Tests_TreeView::test_pressAndHold() Compared values are not the same Actual (): 0 Expected (): 1 Loc: [/<>/tests/auto/controls/data/tst_treeview.qml(274)] PASS : qtquickcontrols::Tests_TreeView::test_selection_contiguousSelection() PASS : qtquickcontrols::Tests_TreeView::test_selection_extendedSelection() PASS : qtquickcontrols::Tests_TreeView::test_selection_multiSelection() PASS : qtquickcontrols::Tests_TreeView::test_selection_noSelection() XFAIL : qtquickcontrols::Tests_TreeView::test_selection_singleSelection() BUG selected state not updated with Command/Control when SingleSelection Loc: [/<>/tests/auto/controls/data/tst_treeview.qml(402)] XFAIL : qtquickcontrols::Tests_TreeView::test_selection_singleSelection() BUG selected state not updated with Command/Control when SingleSelection Loc: [/<>/tests/auto/controls/data/tst_treeview.qml(404)] PASS : qtquickcontrols::Tests_TreeView::test_selection_singleSelection() PASS : qtquickcontrols::Tests_TreeView::cleanupTestCase() Totals: 498 passed, 1 failed, 6 skipped, 0 blacklisted, 410752ms * Finished testing of qtquickcontrols * make[5]: *** [Makefile:318: check] Error 1 Full log is here: https://buildd.debian.org/status/fetch.php?pkg=qtquickcontrols-opensource-src=hppa=5.15.6-2=1664978713=0 Regards, Dave Anglin -- System Information: Debian Release: bookworm/sid APT prefers buildd-unstable APT policy: (500, 'buildd-unstable'), (500, 'unstable') Architecture: hppa (parisc64) Kernel: Linux 5.19.13+ (SMP w/4 CPU threads) Kernel taint flags: TAINT_WARN Locale: LANG=C, 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)
Bug#1021310: libsdl2: FTBFS on hppa - testevdev: FAILED: 1
Source: libsdl2 Version: 2.24.0+dfsg-2 Severity: serious Tags: ftbfs Justification: fails to build from source (but built successfully in the past) Dear Maintainer, Build fails in testsuite: Thinkpad USB keyboard with Trackpoint - Trackpoint... Expected 0x0003 MOUSE KEYBOARD Got 0x No information... OK testevdev: FAILED: 1 testfilesystem... INFO: base path: '/<>/debian/build-tests/' INFO: pref path: '/<>/debian/.debhelper/generated/_source/home/.local/share/libsdl/test_filesystem/' INFO: pref path: '/<>/debian/.debhelper/generated/_source/home/.local/share/test_filesystem/' testfilesystem: OK ... testdisplayinfo: OK make[2]: *** [Makefile:416: check] Error 1 make[2]: Leaving directory '/<>/debian/build-tests' dh_auto_test: error: cd debian/build-tests && make -j4 check "TESTSUITEFLAGS=-j4 --verbose" VERBOSE=1 V=1 returned exit code 2 make[1]: *** [debian/rules:142: override_dh_auto_test-arch] Error 25 make[1]: Leaving directory '/<>' make: *** [debian/rules:81: binary-arch] Error 2 dpkg-buildpackage: error: debian/rules binary-arch subprocess returned exit status 2 Full log is here: https://buildd.debian.org/status/fetch.php?pkg=libsdl2=hppa=2.24.1%2Bdfsg-1=1664977752=0 Similar fail occurs on powerpc. Regards, Dave Anglin -- System Information: Debian Release: bookworm/sid APT prefers buildd-unstable APT policy: (500, 'buildd-unstable'), (500, 'unstable') Architecture: hppa (parisc64) Kernel: Linux 5.19.13+ (SMP w/4 CPU threads) Kernel taint flags: TAINT_WARN Locale: LANG=C, 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)
Processed: severity of 1006757 is grave
Processing commands for cont...@bugs.debian.org: > severity 1006757 grave Bug #1006757 [src:ghostwriter] ghostwriter: CVE-2022-24724 - integer overflow prior to 0.29.0.gfm.3 and 0.28.3.gfm.21 Severity set to 'grave' from 'important' > thanks Stopping processing here. Please contact me if you need assistance. -- 1006757: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1006757 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1020765: Does Debian 11.x 32 bit support NVDIMM?
Control: severity -1 normal Control: tags -1 +moreinfo On Tue, Oct 04, 2022 at 05:57:12PM +, Williams, Dan J wrote: > On Mon, 26 Sep 2022 08:26:56 + Winnie Yue wrote: > > Package: ndctl > > Version: 71.1-1 > > Severity: serious > > For Debian 11.5 32 bit, I got below info: > > But I found that Debian 11.5 32 bit vm couldn’t recognize the NVDIMM device: > > # dmesg | grep -i bios-e820 | grep persistent > > [ 0.00] BIOS-e820: [mem 0x00024000-0x00043fff] > > persistent (type 7) > > Note that this is not sufficient for advertising NVDIMM resources. A > Type-7 memory range still requires an ACPI NFIT to advertise the memory > range. Thanks Dan for this bit, I've missed it. Winnie: please try passing the proper ACPI data; your email address suggests that your VM is one I don't know how to operate. > That said, why are you trying to run a 32-bit environment. If you need a > 32-bit userspace you can still use a 64-bit kernel. 32-bit x86 is not > well looked after by the kernel community in general these days. That's another point; time spent validating a 32-bit kernel isn't that useful. I was really shocked it can use NVDIMM at all. In the userland, you can't count on the stack other than the very lowest level (ie, ndctl). Meow! -- ⢀⣴⠾⠻⢶⣦⠀ ⣾⠁⢠⠒⠀⣿⡁ It's time to migrate your Imaginary Protocol from version 4i to 6i. ⢿⡄⠘⠷⠚⠋⠀ ⠈⠳⣄
Processed: Re: Bug#1020765: Does Debian 11.x 32 bit support NVDIMM?
Processing control commands: > severity -1 normal Bug #1020765 [ndctl] Does Debian 11.x 32 bit support NVDIMM? Severity set to 'normal' from 'serious' > tags -1 +moreinfo Bug #1020765 [ndctl] Does Debian 11.x 32 bit support NVDIMM? Added tag(s) moreinfo. -- 1020765: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1020765 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1015032: marked as done (uftrace: FTBFS: /usr/bin/env: ‘python’: No such file or directory)
Your message dated Wed, 05 Oct 2022 13:22:36 + with message-id and subject line Bug#1015032: fixed in uftrace 0.12-3 has caused the Debian Bug report #1015032, regarding uftrace: FTBFS: /usr/bin/env: ‘python’: 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.) -- 1015032: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1015032 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: uftrace Version: 0.12-1 Severity: serious Justification: FTBFS Tags: bookworm sid ftbfs User: lu...@debian.org Usertags: ftbfs-20220716 ftbfs-bookworm Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > make[2]: Entering directory '/<>' > gcc -o /<>/uftrace.ot -c -D_GNU_SOURCE > -ffile-prefix-map=/<>=. -Wdate-time -D_FORTIFY_SOURCE=2 -iquote > /<> -iquote /<> -iquote > /<>/arch/x86_64 -Wdeclaration-after-statement -W -Wall > -Wno-unused-parameter -Wno-missing-field-initializers -O2 -g -DDEBUG_MODE=0 > -DHAVE_CXA_DEMANGLE -DHAVE_LIBPYTHON3 -I/usr/include/python3.10 > -DLIBPYTHON_VERSION=3.10 -DHAVE_LIBLUAJIT -I/usr/include/luajit-2.1 > -DHAVE_PERF_CLOCKID -DHAVE_PERF_CTXSW -DHAVE_LIBNCURSES -D_DEFAULT_SOURCE > -D_XOPEN_SOURCE=600 -DHAVE_LIBELF -DHAVE_LIBDW -DHAVE_LIBCAPSTONE > -I/usr/include/capstone -DUNIT_TEST -g -include > /<>/tests/unittest.h -Wno-sign-compare /<>/uftrace.c > gcc -o /<>/cmds/dump.ot -c -D_GNU_SOURCE > -ffile-prefix-map=/<>=. -Wdate-time -D_FORTIFY_SOURCE=2 -iquote > /<> -iquote /<> -iquote > /<>/arch/x86_64 -Wdeclaration-after-statement -W -Wall > -Wno-unused-parameter -Wno-missing-field-initializers -O2 -g -DDEBUG_MODE=0 > -DHAVE_CXA_DEMANGLE -DHAVE_LIBPYTHON3 -I/usr/include/python3.10 > -DLIBPYTHON_VERSION=3.10 -DHAVE_LIBLUAJIT -I/usr/include/luajit-2.1 > -DHAVE_PERF_CLOCKID -DHAVE_PERF_CTXSW -DHAVE_LIBNCURSES -D_DEFAULT_SOURCE > -D_XOPEN_SOURCE=600 -DHAVE_LIBELF -DHAVE_LIBDW -DHAVE_LIBCAPSTONE > -I/usr/include/capstone -DUNIT_TEST -g -include > /<>/tests/unittest.h -Wno-sign-compare > /<>/cmds/dump.c > gcc -o /<>/cmds/graph.ot -c -D_GNU_SOURCE > -ffile-prefix-map=/<>=. -Wdate-time -D_FORTIFY_SOURCE=2 -iquote > /<> -iquote /<> -iquote > /<>/arch/x86_64 -Wdeclaration-after-statement -W -Wall > -Wno-unused-parameter -Wno-missing-field-initializers -O2 -g -DDEBUG_MODE=0 > -DHAVE_CXA_DEMANGLE -DHAVE_LIBPYTHON3 -I/usr/include/python3.10 > -DLIBPYTHON_VERSION=3.10 -DHAVE_LIBLUAJIT -I/usr/include/luajit-2.1 > -DHAVE_PERF_CLOCKID -DHAVE_PERF_CTXSW -DHAVE_LIBNCURSES -D_DEFAULT_SOURCE > -D_XOPEN_SOURCE=600 -DHAVE_LIBELF -DHAVE_LIBDW -DHAVE_LIBCAPSTONE > -I/usr/include/capstone -DUNIT_TEST -g -include > /<>/tests/unittest.h -Wno-sign-compare > /<>/cmds/graph.c > gcc -o /<>/cmds/info.ot -c -D_GNU_SOURCE > -ffile-prefix-map=/<>=. -Wdate-time -D_FORTIFY_SOURCE=2 -iquote > /<> -iquote /<> -iquote > /<>/arch/x86_64 -Wdeclaration-after-statement -W -Wall > -Wno-unused-parameter -Wno-missing-field-initializers -O2 -g -DDEBUG_MODE=0 > -DHAVE_CXA_DEMANGLE -DHAVE_LIBPYTHON3 -I/usr/include/python3.10 > -DLIBPYTHON_VERSION=3.10 -DHAVE_LIBLUAJIT -I/usr/include/luajit-2.1 > -DHAVE_PERF_CLOCKID -DHAVE_PERF_CTXSW -DHAVE_LIBNCURSES -D_DEFAULT_SOURCE > -D_XOPEN_SOURCE=600 -DHAVE_LIBELF -DHAVE_LIBDW -DHAVE_LIBCAPSTONE > -I/usr/include/capstone -DUNIT_TEST -g -include > /<>/tests/unittest.h -Wno-sign-compare > /<>/cmds/info.c > gcc -o /<>/cmds/live.ot -c -D_GNU_SOURCE > -ffile-prefix-map=/<>=. -Wdate-time -D_FORTIFY_SOURCE=2 -iquote > /<> -iquote /<> -iquote > /<>/arch/x86_64 -Wdeclaration-after-statement -W -Wall > -Wno-unused-parameter -Wno-missing-field-initializers -O2 -g -DDEBUG_MODE=0 > -DHAVE_CXA_DEMANGLE -DHAVE_LIBPYTHON3 -I/usr/include/python3.10 > -DLIBPYTHON_VERSION=3.10 -DHAVE_LIBLUAJIT -I/usr/include/luajit-2.1 > -DHAVE_PERF_CLOCKID -DHAVE_PERF_CTXSW -DHAVE_LIBNCURSES -D_DEFAULT_SOURCE > -D_XOPEN_SOURCE=600 -DHAVE_LIBELF -DHAVE_LIBDW -DHAVE_LIBCAPSTONE > -I/usr/include/capstone -DUNIT_TEST -g -include > /<>/tests/unittest.h -Wno-sign-compare > /<>/cmds/live.c > gcc -o /<>/cmds/record.ot -c -D_GNU_SOURCE > -ffile-prefix-map=/<>=. -Wdate-time -D_FORTIFY_SOURCE=2 -iquote > /<> -iquote /<> -iquote > /<>/arch/x86_64 -Wdeclaration-after-statement -W -Wall > -Wno-unused-parameter -Wno-missing-field-initializers -O2 -g -DDEBUG_MODE=0 > -DHAVE_CXA_DEMANGLE -DHAVE_LIBPYTHON3 -I/usr/include/python3.10 > -DLIBPYTHON_VERSION=3.10 -DHAVE_LIBLUAJIT -I/usr/include/luajit-2.1 > -DHAVE_PERF_CLOCKID -DHAVE_PERF_CTXSW -DHAVE_LIBNCURSES -D_DEFAULT_SOURCE >
Bug#1020632: marked as done (ruby-rugged: please update to version 1.5.0.1)
Your message dated Wed, 05 Oct 2022 13:21:43 + with message-id and subject line Bug#1020632: fixed in ruby-rugged 1.5.0.1+ds-1~exp1 has caused the Debian Bug report #1020632, regarding ruby-rugged: please update to version 1.5.0.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.) -- 1020632: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1020632 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: ruby-rugged Version: 1.2.0+ds-1 Severity: important -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Dear maintainers, I have packaged libgit2 1.5 and uploaded it to experimental. Please package the compatible Ruby libgit2 bindings for the transition that is about to happen. Thank you! Cheers Timo -BEGIN PGP SIGNATURE- iQGzBAEBCgAdFiEEJvtDgpxjkjCIVtam+C8H+466LVkFAmMu+kgACgkQ+C8H+466 LVkXHQwAoYFyBSPF/Wog9Zo/kXTOnQD+I/kg1A4Z8WIx1M0ywP/fw1Ir5oZDyTFL AiW4fPF199+t7lmoYmPfzE3RwYTbLBPsLH0sSieXX2CxSxnWD2SoaMeo/EmjZp67 YQrVMLggXtVFAkjwXSttXhAR7rALWmxCIO6pri6FfgFmuCNNxe1N8BK/qbNmx85r ETfTEBXuqOJxL/miymDq0YDaQb6idHy7VVAkqt/7tabLhlfmTC3WW721nOGo8CcA 3oRD+KwtY69OT5r3ZKOwajFuCfMr3RBSpsKqSOIwt/rWTeZbgX7+1tOJ7nEVPwK2 A769brLm4Adfnn4q6KBeJnQ0d5Mtge9aNh5kxv9xllYnfU51oy0A5slNVKaRY7FK RN0jcliZ3fln6AhUsoYaoIzv04Q9On4B+3CLfCaeKbcsP4PiTz3em+cCPENIVNjY Dt0fsJaLKpW/lfsJmiBVn86KAxQ/7VBUH2C8b6HUatDRWn/sWIqC3mNCjKTptGKI ajHwwPEz =idgq -END PGP SIGNATURE- --- End Message --- --- Begin Message --- Source: ruby-rugged Source-Version: 1.5.0.1+ds-1~exp1 Done: Cédric Boutillier We believe that the bug you reported is fixed in the latest version of ruby-rugged, 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 1020...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Cédric Boutillier (supplier of updated ruby-rugged 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: Wed, 05 Oct 2022 14:22:24 +0200 Source: ruby-rugged Architecture: source Version: 1.5.0.1+ds-1~exp1 Distribution: experimental Urgency: medium Maintainer: Debian Ruby Team Changed-By: Cédric Boutillier Closes: 1020632 Changes: ruby-rugged (1.5.0.1+ds-1~exp1) experimental; urgency=medium . [ Mohammed Bilal ] * d/control : Update min version of libgit2-dev . [ Cédric Boutillier ] * New upstream version 1.5.0.1+ds - for libgit2 1.5 (Closes: #1020632) * Bump minimal value of libgit2 to 1.5 in build-deps * Bump Standards-Version to 4.6.1 (no changes needed) Checksums-Sha1: 88a114b4f2e4aeb131f9e64e18462d7ba4fba159 1601 ruby-rugged_1.5.0.1+ds-1~exp1.dsc 4c55dd218e4511f8aca4786bdd0fe7d455a559ac 590492 ruby-rugged_1.5.0.1+ds.orig.tar.xz 07dfd705b1b34c630970185d1ad1fd79f7681e88 6336 ruby-rugged_1.5.0.1+ds-1~exp1.debian.tar.xz 10945229857cd9023e1e2fedafefe54a86df1ceb 10380 ruby-rugged_1.5.0.1+ds-1~exp1_amd64.buildinfo Checksums-Sha256: 01ffeb9be46dda52ea81ba91231513ace1dc9d6ffac3577aed429e9703753d3c 1601 ruby-rugged_1.5.0.1+ds-1~exp1.dsc e5a8b9a33e63459f0a350a092c24eae1b265d6434772db457319079299155a8d 590492 ruby-rugged_1.5.0.1+ds.orig.tar.xz 2ba86d8168b544e8ad7a2ab30cd99967af51570e9ef07c6f6a8a6f425efdcec2 6336 ruby-rugged_1.5.0.1+ds-1~exp1.debian.tar.xz 2bfecf5d984787123600dca217b20646685ad0181845da2699f22b05f512b2f8 10380 ruby-rugged_1.5.0.1+ds-1~exp1_amd64.buildinfo Files: b6a1ba12b1f335e9cb09c7b138662602 1601 ruby optional ruby-rugged_1.5.0.1+ds-1~exp1.dsc ac21749098279583f07564af4931352e 590492 ruby optional ruby-rugged_1.5.0.1+ds.orig.tar.xz 993757848c1ec680d0646ce1b540f26c 6336 ruby optional ruby-rugged_1.5.0.1+ds-1~exp1.debian.tar.xz c6655f58d60c60ca128a7d0e148ac53f 10380 ruby optional ruby-rugged_1.5.0.1+ds-1~exp1_amd64.buildinfo -BEGIN PGP SIGNATURE- iHUEARYKAB0WIQSEz/3CFSD4gwbsKdFSaZq2P58rwwUCYz2BZgAKCRBSaZq2P58r w8EAAP9f+3N0CCZyvq8crypPH/QkvP6mZNgACB0kKHCohovz7QD+MgDEJxp65Vbr niEBwGPhS8yyOacNMqVlJ7YyzNkDVQY= =+CBT -END PGP SIGNATURE End Message ---
Bug#1021032: VLC Black screen
Thank you. I'll open a new bug. By the way, once updated to the new VLC version (3.0.17.4-5) in a fully updated Sid I noticed after seeing a few videos the player goes black again and nothing until a reboot is issued. Anyone else noticed this?
Bug#1021139: marked as pending in barbican
Control: tag -1 pending Hello, Bug #1021139 in barbican reported by you has been fixed in the Git repository and is awaiting an upload. You can see the commit message below and you can check the diff of the fix at: https://salsa.debian.org/openstack-team/services/barbican/-/commit/371703e435c9ae1c26f942f10b569eb8d9a03ba3 * New upstream release: - fix CVE-2022-3100: incorrectly parsed requests which could allow an authenticated user to bypass Barbican access policy (Closes: #1021139). (this message was generated automatically) -- Greetings https://bugs.debian.org/1021139
Processed: Bug#1021139 marked as pending in barbican
Processing control commands:
> tag -1 pending
Bug #1021139 {Done: Thomas Goirand } [src:barbican] barbican:
CVE-2022-3100
Added tag(s) pending.
--
1021139: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1021139
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Bug#1021139: marked as done (barbican: CVE-2022-3100)
Your message dated Wed, 05 Oct 2022 10:04:01 + with message-id and subject line Bug#1021139: fixed in barbican 1:15.0.0~rc3-1 has caused the Debian Bug report #1021139, regarding barbican: CVE-2022-3100 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.) -- 1021139: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1021139 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: barbican X-Debbugs-CC: t...@security.debian.org Severity: grave Tags: security Hi, The following vulnerability was published for barbican. CVE-2022-3100[0]: access policy bypass via query string injection Only reference so far is Red Hat Bugzilla: https://bugzilla.redhat.com/show_bug.cgi?id=2125404 If you fix the vulnerability please also make sure to include the CVE (Common Vulnerabilities & Exposures) id in your changelog entry. For further information see: [0] https://security-tracker.debian.org/tracker/CVE-2022-3100 https://www.cve.org/CVERecord?id=CVE-2022-3100 Please adjust the affected versions in the BTS as needed. --- End Message --- --- Begin Message --- Source: barbican Source-Version: 1:15.0.0~rc3-1 Done: Thomas Goirand We believe that the bug you reported is fixed in the latest version of barbican, 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. Thomas Goirand (supplier of updated barbican package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Wed, 05 Oct 2022 11:34:10 +0200 Source: barbican Architecture: source Version: 1:15.0.0~rc3-1 Distribution: unstable Urgency: high Maintainer: Debian OpenStack Changed-By: Thomas Goirand Closes: 1021139 Changes: barbican (1:15.0.0~rc3-1) unstable; urgency=high . * New upstream release: - fix CVE-2022-3100: incorrectly parsed requests which could allow an authenticated user to bypass Barbican access policy (Closes: #1021139). Checksums-Sha1: 305fbd01040f41ea3dae0db10bc0a213777a7b94 3716 barbican_15.0.0~rc3-1.dsc ead0807662c8127c3a485bc4462d722da8f1c9a1 490716 barbican_15.0.0~rc3.orig.tar.xz c309ca01da139f718dfde00c96e843d647ba7c3f 10200 barbican_15.0.0~rc3-1.debian.tar.xz fdbecc0c78ab242369211dc1ad2fc38bf4ab90a9 21969 barbican_15.0.0~rc3-1_amd64.buildinfo Checksums-Sha256: 543a11b4dcd643e0437970d01b3cb5b1332c8b1899b8ae109f2dfab029e8fa78 3716 barbican_15.0.0~rc3-1.dsc 9dd0c235aa0eb4dd5152ad961aa82e401566ee32aa0e6c59888648787e13838f 490716 barbican_15.0.0~rc3.orig.tar.xz d585f154b7718434539b40f50ea025ccdb9d62dd2501c4e1999f1aa35b15c7d3 10200 barbican_15.0.0~rc3-1.debian.tar.xz 335b1f0f52ed63df06a53bf403f32a77d17aae3c78286871bec5b8bfd60f1aa8 21969 barbican_15.0.0~rc3-1_amd64.buildinfo Files: 8f7b5ba1c9343ceec7dd1dc8bca381e4 3716 net optional barbican_15.0.0~rc3-1.dsc 8e4e03332a4e50edde2a4e480eeef489 490716 net optional barbican_15.0.0~rc3.orig.tar.xz 906a4befcbc52690f6e542f8f46b9f23 10200 net optional barbican_15.0.0~rc3-1.debian.tar.xz d8dcba4f8f1557002fcea98a07c776a7 21969 net optional barbican_15.0.0~rc3-1_amd64.buildinfo -BEGIN PGP SIGNATURE- iQIzBAEBCAAdFiEEoLGp81CJVhMOekJc1BatFaxrQ/4FAmM9UW0ACgkQ1BatFaxr Q/6xnw//aX8j2upyUsy/210s7SydSZwcezuYFO4Kpz/oSD0CXUc/erfusH6XG0fT LshDSkfy3MEkaOkpVXoKUKJGdEhX0fIghu7LJPrrAKwXa6MMREmvhcx7tQdglUk9 k7W+LVN3DJrKSKg4AgJHhU/N4FpFy+mXQgPPzV0l4abWT3T69tYK6RRiGxD+zcIG gBukGctVU7PVu/Jx8jfeG7cZoxmFTngCGZFgxATYURbd7cADdVCILy1EA3C0YK+m 8ffOHYD0gs3urJbteLBqb9B6F09RTFKWI49aTLcqcuBrIiHzdKgjEh3N42N7XmVj XhdUaEiHVoUXiSGElNbPRo+6JqrNmY9aa/6I9k80yoUAEXIMzjUQackmfBGYGpWc ZKH7D1bfZe7Dq2U4mGDuND0+Au7AElR93XkgjTPlf7cszOnpEps9KP850T0FGHD1 0RiuWrB4Y6ReGdYExGpys3Pp8OrW8sE3bNOMWGtjdKUUFJEvO/JwkyOYsebi6+WR K3CLVxp8DCAnfbGrK9o7IcPMh/a3EtE22rZkcXlKTLID7BA1PCFNgEndpQdcK4wk tTFUfJFTqpn+ZjYMExSwIUcfh9itFcfeLo6Rvh80oeN0xQ82rNmA++xhfaWjuHPs xv9TUNeGU/5tNuHLsTerqUeeaoZXVMfKz4zGF1LWJEnUgVk86qY= =pJrY -END PGP SIGNATURE End Message ---
Processed: tagging 1005447
Processing commands for cont...@bugs.debian.org: > tags 1005447 + upstream fixed-upstream Bug #1005447 [src:ola] ola: FTBFS: dh_auto_test: error: make -j4 check VERBOSE=1 returned exit code 2 Added tag(s) fixed-upstream and upstream. > thanks Stopping processing here. Please contact me if you need assistance. -- 1005447: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1005447 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1021283: marked as done (simgrid FTBFS on mipsel)
Your message dated Wed, 05 Oct 2022 08:49:38 + with message-id and subject line Bug#1021283: fixed in simgrid 3.32-2 has caused the Debian Bug report #1021283, regarding simgrid FTBFS on mipsel 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.) -- 1021283: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1021283 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: simgrid Version: 3.32-1 Severity: serious Tags: ftbfs https://buildd.debian.org/status/fetch.php?pkg=simgrid=mipsel=3.32-1=1664920617=0 ... -- Checking for modules 'ns3-core>=3.28;ns3-csma;ns3-point-to-point;ns3-internet;ns3-network;ns3-applications;ns3-wifi' -- No package 'ns3-core' found -- No package 'ns3-csma' found -- No package 'ns3-point-to-point' found -- No package 'ns3-internet' found -- No package 'ns3-network' found -- No package 'ns3-applications' found -- No package 'ns3-wifi' found -- Looking for ns3/core-module.h - not found -- Looking for lib ns3-core -- Looking for lib ns3-core - not found -- Warning: Please install ns-3 (version 3.22 or higher -- http://www.nsnam.org/releases/) or disable this feature. CMake Error at CMakeLists.txt:237 (message): Cannot find ns-3. Please install it (apt-get install ns3 libns3-dev) or disable that cmake option -- Configuring incomplete, errors occurred! ... ns3 is already building on mipsel again, please don't exclude mipsel in the build dependencies. --- End Message --- --- Begin Message --- Source: simgrid Source-Version: 3.32-2 Done: Martin Quinson We believe that the bug you reported is fixed in the latest version of simgrid, 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. Martin Quinson (supplier of updated simgrid 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: Wed, 05 Oct 2022 09:00:11 +0200 Source: simgrid Architecture: source Version: 3.32-2 Distribution: unstable Urgency: medium Maintainer: Martin Quinson Changed-By: Martin Quinson Closes: 1021283 Changes: simgrid (3.32-2) unstable; urgency=medium . * Build-deps: drop lua; reactivate libboost-context-dev; Activate ns3 on all arch since we use it everywhere (Closes: #1021283) Checksums-Sha1: 51497ef2839701684c263d13acc48a6d5da925d7 2298 simgrid_3.32-2.dsc e563275d151aa27f90b8bc80398b240661dcabd2 15532 simgrid_3.32-2.debian.tar.xz 949b8d5f21a1dbe6dcdb1c13227a72363094573f 12942 simgrid_3.32-2_amd64.buildinfo Checksums-Sha256: e00c41baa02a8cc4be98a1e3ec7b6080cde35c7bb555bd745c94593dee028d52 2298 simgrid_3.32-2.dsc 51d3e8ee1b5b1e216217ee2069fb628df884f2b87fb1c3a5ca6634ec4dea1256 15532 simgrid_3.32-2.debian.tar.xz a0dcfe12269ab39f6b082beb97d175490e74c6d038a553d840f5d1a27c7cda9e 12942 simgrid_3.32-2_amd64.buildinfo Files: 4b52e3b89f9129558540b63f07f5f061 2298 science optional simgrid_3.32-2.dsc 9ee13eaa927941bf3963bafc7677718a 15532 science optional simgrid_3.32-2.debian.tar.xz db96cff82dacfd7dea66ef643a4c9a80 12942 science optional simgrid_3.32-2_amd64.buildinfo -BEGIN PGP SIGNATURE- iQJIBAEBCgAyFiEET76cTupS7xPVQWYSmL2XJE9zvqcFAmM9Lg8UHG1xdWluc29u QGRlYmlhbi5vcmcACgkQmL2XJE9zvqcO/g/+KGx0+oA8LLMK7fzz8AOdJQD2P/cI zgxyiwm5flrs2e/CSVIY11E4kuazzcaC9dKeVkjUKrUXjB6xlVWaTwxrNIGU2szg layqFlT8+BEslgK7r5yMU976OFeV7f47nxLJdzUT+sjYP11w6naAKtDLVC0zJjjU /9brKFjoA42tM5Q7dB1mw6iNcmkK8VxqT75NX0Jt0wNhMikSgd/oyyqPFUo7l9rz IsZ0WDlMGeIReCp1Fh/Ah8i6A/O89fuJUqYhEMu0jax2Dw071E2YM9JCAZ4hSttT Yb/sLP3MUewrxADTLOV2zR3pDGqVCNG1p5cP32CCagqWowbb3YuGph3ufR+m+nmc VZiCVDs4iSICY8iGgTjDYGbiaANN93+Bqt80jk+qtHKLeEgXQJ4nlc5uxYVc8MEq u5qGMESSdu+ZMvI9r35345Bc3m2H6ZqZCfX0scC5xldb9kZvGGGdckpfFfxteeGl k68RkNWSc3O/rzAG6mswcVOdl8N4Xm+vA+piQdRQbdRXg6Etxct/NEJgmm1dP68K O5fS3JuZoubIliUAvNyHdw+owE4zCS9hyXmZll5k2M556zsWm5wgKsbOM23C1DHD p4zZJ3DxoI+K05j9jYbtPnbZ79LyKux5q+FwyEJUugRz1YEiGFryVLCI9jI9vWEL 9tRtFzpMHbXrW2A= =8caN -END PGP SIGNATURE End Message ---
Bug#1020994: marked as done (shotcut: binary-all FTBFS)
Your message dated Wed, 05 Oct 2022 08:49:13 + with message-id and subject line Bug#1020994: fixed in shotcut 22.09.23+ds-4 has caused the Debian Bug report #1020994, regarding shotcut: binary-all FTBFS 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.) -- 1020994: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1020994 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: shotcut Version: 22.09.23+ds-3 Severity: serious Tags: ftbfs https://buildd.debian.org/status/fetch.php?pkg=shotcut=all=22.09.23%2Bds-3=1664207628=0 ... debian/rules override_dh_install make[1]: Entering directory '/<>' dh_install patchelf --set-rpath /usr/lib/shotcut debian/shotcut/usr/bin/shotcut patchelf: getting info about 'debian/shotcut/usr/bin/shotcut': No such file or directory make[1]: *** [debian/rules:26: override_dh_install] Error 1 --- End Message --- --- Begin Message --- Source: shotcut Source-Version: 22.09.23+ds-4 Done: Gürkan Myczko We believe that the bug you reported is fixed in the latest version of shotcut, 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 1020...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Gürkan Myczko (supplier of updated shotcut package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Wed, 05 Oct 2022 10:25:15 +0200 Source: shotcut Architecture: source Version: 22.09.23+ds-4 Distribution: unstable Urgency: medium Maintainer: Debian Multimedia Maintainers Changed-By: Gürkan Myczko Closes: 1020994 Changes: shotcut (22.09.23+ds-4) unstable; urgency=medium . * d/rules: fix for binary-all FTBFS. (Closes: #1020994) Checksums-Sha1: 95c143b80395a53bfd4287b63218aef9ea677bba 2429 shotcut_22.09.23+ds-4.dsc 861cc4282e37e1049c0516eb337b390c8df325f0 4176 shotcut_22.09.23+ds-4.debian.tar.xz 2706ac4fbac701bb32708329ca073b80a55ed11f 21294 shotcut_22.09.23+ds-4_source.buildinfo Checksums-Sha256: 5fe8696ea0ce29ad628b38cca3e58415b99c1037d39377433177ff21876958ff 2429 shotcut_22.09.23+ds-4.dsc edc2fa55eb590de5a4f5ae6809f0105b43c7cebe40234b949ede6c6f6603c5c1 4176 shotcut_22.09.23+ds-4.debian.tar.xz 01e45c32ff3bc9677c2a55dd286340db4345b9d58bfa2c4cbfcce9c8923358b6 21294 shotcut_22.09.23+ds-4_source.buildinfo Files: aa3c68c80d6e650338a0a35b5fce5505 2429 video optional shotcut_22.09.23+ds-4.dsc 2db4604d07c154c3b9281c85ed4a8ea4 4176 video optional shotcut_22.09.23+ds-4.debian.tar.xz 99e903d9824873011b663e71f5b3891d 21294 video optional shotcut_22.09.23+ds-4_source.buildinfo -BEGIN PGP SIGNATURE- iQIzBAEBCAAdFiEEtgob82PcExn/Co6JEWhSvN91FcAFAmM9QAoACgkQEWhSvN91 FcAFrw//d+CgXRJZ/Z1yFUDJLzfZy+45sp0YR4/pDN1PVh6e5IBen9riKdqOt/ZN V6f/iBK5lZItlBIPbrrlj5zoevEAq7dbh8wPBwAr9ya0D4hNbIgRwDBp1M0pkJc6 +ZIHZqBNaJ+0G0zx7cjS2bx2xKqMUwYNEWvaRQf6PqTgQlAzF9rKRlqYZwU4fVVc ssg9HQNFo8mPOXFJRo0h1mj7DBBBb28XipgXItvCh/6VceDwj6VceaXw626a/wls l0OhGqCpQKRl7dMdHp5mGA09kHPnHLEqx8ZMma7FDdayacl4+zHgaY0sz0prfrLa MyzAUs+BHbFV67Au35EGAO2MxL4F1aSCpE1aBiusu/VZiJC+UTnm6C8VoFT8eXlO y2gdyNEMI9ojwmxtqUUeHgAXH1kXGqXvYqRGWGzL0WUgNH+4NrPUlSphqfm4MpqK ERiEYQNgkFiENig9ATwmdG8gem+gYSLBZjTno1tYP638YAdOW9aGmS5GzOMcX4X0 CxHJITUYNHeFdUCx/tnVCiZEPRwLrgGWIbR4NndvovVxLtlzo1hVUhrP2UBCeNs9 +c8AuSAXQd8EmBt6eRTpAaSKsyCct/8RZEAbD/MHQpJeamuqM6sElqdWA7tAI/r/ 73OBUBtltIPxZyCIAD4bxM8IKscOIyHJ/O3r1jAuA1KrFeMlSsY= =cC2h -END PGP SIGNATURE End Message ---
Bug#1021284: unifrac-tools seems to be an unintentional hijack of src:unifrac
Hi Adrian, Am Wed, Oct 05, 2022 at 01:16:08AM +0300 schrieb Adrian Bunk: > Source: unifrac-tools > Version: 1.1.1-1 > Severity: serious > > unifrac-tools seems to be an unintentional hijack of src:unifrac, > which is also maintained by Debian Med and RFA (#996921). > > Package name differences: > - libssu-tools -> unifrac-tools > - python3-unifrac -> none Thanks a lot for your bug report. Upstream had restructured the source layout a lot and has moved libssu* to unifrac-tools in version 1.1.1. Thus we had to pass unifrac-tools to new first and will sort out the issue with unifrac (which will only build python3-unifrac in the new version.) I've just added the needed Conflicts/Provides/Replaces in unifrac-tools in Git and will upload soon. There are some remaining issues for unifrac before I can upload, thought. Kind regards Andreas. -- http://fam-tille.de
Bug#1020132: marked as done (node-postgres: FTBFS: dh_auto_test: error: cd ./postgres-bytea && sh -ex ../debian/nodejs/postgres-bytea/test returned exit code 1)
Your message dated Wed, 05 Oct 2022 07:05:49 + with message-id and subject line Bug#1020132: fixed in node-postgres 8.8.0+~cs35.9.20-1 has caused the Debian Bug report #1020132, regarding node-postgres: FTBFS: dh_auto_test: error: cd ./postgres-bytea && sh -ex ../debian/nodejs/postgres-bytea/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.) -- 1020132: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1020132 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: node-postgres Version: 7.14.0-3 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 binary > dh binary >dh_update_autotools_config >dh_autoreconf >dh_auto_configure --buildsystem=nodejs > Link node_modules/buffer-writer -> ../buffer-writer > Link node_modules/packet-reader -> ../packet-reader > Link node_modules/pg-connection-string -> ../pg-connection-string > Link node_modules/pg-cursor -> ../pg-cursor > Link node_modules/pg-int8 -> ../pg-int8 > Link node_modules/pg-numeric -> ../pg-numeric > Link node_modules/pg-pool -> ../pg-pool > Link node_modules/pg-types -> ../pg-types > Link node_modules/pgpass -> ../pgpass > Link node_modules/postgres-array -> ../postgres-array > Link node_modules/postgres-bytea -> ../postgres-bytea > Link node_modules/postgres-date -> ../postgres-date > Link node_modules/postgres-interval -> ../postgres-interval > Link pg-pool/node_modules/pg-cursor -> ../../pg-cursor > Link pg-types/node_modules/pg-int8 -> ../../pg-int8 >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 > 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 > 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/pff node_modules/pff > ln -s ../. node_modules/pg > cd ./buffer-writer && sh -ex ../debian/nodejs/buffer-writer/test > + mocha > > > undefined writes char > undefined gets correct byte length > undefined can add arbitrary buffer to the end > undefined resizing to much larger > adding int32 > undefined writes 0 > undefined writes 1 > undefined writes 256 > undefined writes largest int32 > undefined writing multiple int32s > having to resize the buffer > undefined after resize correct result returned > > int16 > undefined writes 0 > undefined writes 400 > undefined writes many > undefined resizes if internal buffer fills up > > cString > undefined writes empty cstring > undefined writes two empty cstrings > undefined writes non-empty cstring > undefined resizes if reached end > undefined writes multiple cstrings > > can write normal string > undefined can write cString too > undefined can resize > > clearing > undefined clears > undefined writing more > undefined returns result > undefined clears the writer > > flush > undefined added as a hex code to a full writer > undefined added as a hex code to a non-full writer > undefined added as a hex code to a buffer which requires resizing > > header > undefined adding two packets with headers > > > 29 passing (44ms) > > cd ./packet-reader && sh -ex ../debian/nodejs/packet-reader/test > + mocha > > > packet-reader > undefined reads perfect 1 length buffer > undefined reads perfect longer buffer > undefined reads two parts > undefined reads multi-part > undefined resets internal buffer at end of packet > undefined reads multiple messages from single chunk > undefined reads 1 and a split > > variable length header > undefined reads double message buffers > > 1 length code > undefined reads code > undefined is set on uncompleted read > > postgres style packet > undefined reads with padded length > > > 11
Bug#1021286: marked as done (prody downloads from the internet during the build)
Your message dated Wed, 05 Oct 2022 07:06:24 +
with message-id
and subject line Bug#1021286: fixed in prody 2.2.0+dfsg-2
has caused the Debian Bug report #1021286,
regarding prody downloads from the internet during the build
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.)
--
1021286: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1021286
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: prody
Version: 2.2.0+dfsg-1
Severity: serious
Tags: ftbfs
https://buildd.debian.org/status/fetch.php?pkg=prody=i386=2.2.0%2Bdfsg-1=1664908079=0
...
==
ERROR: testCompressed (prody.tests.proteins.test_wwpdb.TestFTP)
--
Traceback (most recent call last):
File
"/<>/.pybuild/cpython3_3.10_prody/build/prody/proteins/wwpdb.py",
line 178, in fetchPDBviaFTP
ftp = FTP(ftp_host)
File "/usr/lib/python3.10/ftplib.py", line 121, in __init__
self.connect(host)
File "/usr/lib/python3.10/ftplib.py", line 158, in connect
self.sock = socket.create_connection((self.host, self.port), self.timeout,
File "/usr/lib/python3.10/socket.py", line 845, in create_connection
raise err
File "/usr/lib/python3.10/socket.py", line 833, in create_connection
sock.connect(sa)
OSError: [Errno 101] Network is unreachable
During handling of the above exception, another exception occurred:
Traceback (most recent call last):
File
"/<>/.pybuild/cpython3_3.10_prody/build/prody/tests/proteins/test_wwpdb.py",
line 33, in testCompressed
self.fns = self.fetch(*self.pdb, folder=TEMPDIR)
File
"/<>/.pybuild/cpython3_3.10_prody/build/prody/proteins/wwpdb.py",
line 180, in fetchPDBviaFTP
raise type(error)('FTP connection problem, potential reason: '
OSError: FTP connection problem, potential reason: no internet connectivity
==
ERROR: testDecompressed (prody.tests.proteins.test_wwpdb.TestFTP)
--
Traceback (most recent call last):
File
"/<>/.pybuild/cpython3_3.10_prody/build/prody/proteins/wwpdb.py",
line 178, in fetchPDBviaFTP
ftp = FTP(ftp_host)
File "/usr/lib/python3.10/ftplib.py", line 121, in __init__
self.connect(host)
File "/usr/lib/python3.10/ftplib.py", line 158, in connect
self.sock = socket.create_connection((self.host, self.port), self.timeout,
File "/usr/lib/python3.10/socket.py", line 845, in create_connection
raise err
File "/usr/lib/python3.10/socket.py", line 833, in create_connection
sock.connect(sa)
OSError: [Errno 101] Network is unreachable
During handling of the above exception, another exception occurred:
Traceback (most recent call last):
File
"/<>/.pybuild/cpython3_3.10_prody/build/prody/tests/proteins/test_wwpdb.py",
line 49, in testDecompressed
self.fns = self.fetch(*self.pdb, folder=TEMPDIR, compressed=False)
File
"/<>/.pybuild/cpython3_3.10_prody/build/prody/proteins/wwpdb.py",
line 180, in fetchPDBviaFTP
raise type(error)('FTP connection problem, potential reason: '
OSError: FTP connection problem, potential reason: no internet connectivity
--
Ran 937 tests in 36.733s
FAILED (errors=2, skipped=32)
E: pybuild pybuild:379: test: plugin distutils failed with: exit code=1: cd
/<>/.pybuild/cpython3_3.10_prody/build; python3.10 -m unittest
discover -v
dh_auto_test: error: pybuild --test -i python{version} -p 3.10 returned exit
code 13
make: *** [debian/rules:6: binary-arch] Error 25
--- End Message ---
--- Begin Message ---
Source: prody
Source-Version: 2.2.0+dfsg-2
Done: Andrius Merkys
We believe that the bug you reported is fixed in the latest version of
prody, 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.
Andrius Merkys (supplier of updated prody 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: Wed, 05 Oct 2022 02:44:14 -0400
Bug#1021032: VLC sound
On 2022-10-03 22:30:19 +0200, Miguel A. Vallejo wrote: > Hi! > > Has anyone noticed the actual version on Sid and the previous one do not > reproduce sound from videos with AAC audio? > > I have some MKV videos with AAC ( aac (LC), 48000 Hz, 5.1, fltp) and they > sound nicely in any other player but complete silence with VLC. > > I don't know if it could be related to this bug. Should I create a new bug? That's a different bug. Please file a new issue with a log. Cheers > > Thank you -- Sebastian Ramacher
