Bug#1039566: "Uncaught exception" on crypto.getRandomValues(new Uint32Array(32))
With the update to 115.0.2 it works again - even in the profile that was broken before. Thanks!
Bug#1037798: marked as done (onetbb: ftbfs with GCC-13)
Your message dated Fri, 14 Jul 2023 05:21:33 + with message-id and subject line Bug#1037798: fixed in onetbb 2021.9.0-1 has caused the Debian Bug report #1037798, regarding onetbb: ftbfs with GCC-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.) -- 1037798: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1037798 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: src:onetbb Version: 2021.8.0-2 Severity: normal Tags: sid trixie User: debian-...@lists.debian.org Usertags: ftbfs-gcc-13 [This bug is targeted to the upcoming trixie 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-13/g++-13, but succeeds to build with gcc-12/g++-12. The severity of this report will be raised before the trixie release. The full build log can be found at: http://qa-logs.debian.net/2023/05/22/logs/onetbb_2021.8.0-2_unstable_gccexp.log The last lines of the build log are at the end of this report. To build with GCC 13, either set CC=gcc-13 CXX=g++-13 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-13/porting_to.html [...] /<>/src/tbb/../../include/oneapi/tbb/concurrent_vector.h:284:26: required from ‘tbb::detail::d1::concurrent_vector::concurrent_vector(const allocator_type&) [with T = tbb::detail::d0::padded >, 128>; Allocator = tbb::detail::d1::tbb_allocator >, 128> >; allocator_type = tbb::detail::d1::tbb_allocator >, 128> >]’ /<>/src/tbb/../../include/oneapi/tbb/concurrent_vector.h:281:61: required from ‘tbb::detail::d1::concurrent_vector::concurrent_vector() [with T = tbb::detail::d0::padded >, 128>; Allocator = tbb::detail::d1::tbb_allocator >, 128> >]’ /<>/src/tbb/../../include/oneapi/tbb/enumerable_thread_specific.h:953:30: required from ‘tbb::detail::d1::enumerable_thread_specific::enumerable_thread_specific(const tbb::detail::d1::enumerable_thread_specific&) [with T = minimalNComparable<129>; Allocator = tbb::detail::d1::tbb_allocator >; tbb::detail::d1::ets_key_usage_type ETS_key_type = tbb::detail::d1::ets_no_key]’ /<>/test/conformance/conformance_enumerable_thread_specific.cpp:870:14: required from ‘void ets_copy_assign_test(InitSrc, InitDst, Validator, const char*) [with T = minimalNComparable<129>; Allocator = tbb::detail::d1::tbb_allocator; InitSrc = minimalNComparable<129>; InitDst = minimalNComparable<129>; Validator = Validator, 3142>]’ /<>/test/conformance/conformance_enumerable_thread_specific.cpp:927:39: required from ‘void run_assign_and_copy_constructor_test(const char*, const char*) [with T = minimalNComparable<129>; Allocator = tbb::detail::d1::tbb_allocator]’ /<>/test/conformance/conformance_enumerable_thread_specific.cpp:948:86: required from ‘void run_assignment_and_copy_constructor_tests(const char*) [with Allocator = tbb::detail::d1::tbb_allocator]’ /<>/test/conformance/conformance_enumerable_thread_specific.cpp:1207:74: required from here /<>/src/tbb/../../include/oneapi/tbb/detail/_segment_table.h:63:63: warning: member ‘tbb::detail::d1::segment_table >, 128>, tbb::detail::d1::tbb_allocator >, 128> >, tbb::detail::d1::concurrent_vector >, 128>, tbb::detail::d1::tbb_allocator >, 128> > >, 3>::my_embedded_table’ is used uninitialized [-Wuninitialized] /<>/src/tbb/../../include/oneapi/tbb/detail/_segment_table.h: In instantiation of ‘tbb::detail::d1::segment_table::segment_table(const allocator_type&) [with T = tbb::detail::d0::padded > >, 128>; Allocator = tbb::detail::d1::tbb_allocator > >, 128> >; DerivedType = tbb::detail::d1::concurrent_vector > >, 128>, tbb::detail::d1::tbb_allocator > >, 128> > >; long unsigned int PointersPerEmbeddedTable = 3; allocator_type = tbb::detail::d1::tbb_allocator > >, 128> >]’: /<>/src/tbb/../../include/oneapi/tbb/concurrent_vector.h:284:26: required from ‘tbb::detail::d1::concurrent_vector::concurrent_vector(const allocator_type&) [with T = tbb::detail::d0::padded > >, 128>; Allocator = tbb::detail::d1::tbb_allocator > >, 128> >; allocator_type =
Bug#1037838: marked as done (readstat: ftbfs with GCC-13)
Your message dated Fri, 14 Jul 2023 05:21:41 + with message-id and subject line Bug#1037838: fixed in readstat 1.1.9-2 has caused the Debian Bug report #1037838, regarding readstat: ftbfs with GCC-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.) -- 1037838: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1037838 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: src:readstat Version: 1.1.8-1 Severity: normal Tags: sid trixie User: debian-...@lists.debian.org Usertags: ftbfs-gcc-13 [This bug is targeted to the upcoming trixie 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-13/g++-13, but succeeds to build with gcc-12/g++-12. The severity of this report will be raised before the trixie release. The full build log can be found at: http://qa-logs.debian.net/2023/05/22/logs/readstat_1.1.8-1_unstable_gccexp.log The last lines of the build log are at the end of this report. To build with GCC 13, either set CC=gcc-13 CXX=g++-13 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-13/porting_to.html [...] checking for deflate in -lz... yes checking that generated files are newer than configure... done configure: creating ./config.status config.status: creating Makefile config.status: executing depfiles commands config.status: executing libtool commands Configuration: C compiler: gcc CFLAGS: -g -O2 -ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat -Werror=format-security LD: /usr/bin/ld -m elf_x86_64 C++ compiler: g++ CXXFLAGS: -g -O2 -ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat -Werror=format-security CXXLD: Host: x86_64-pc-linux-gnu Extra warnings: Extra libs: -lm Extra ld flags: Fuzzing engine: Ragel: true Ragel flags: dh_auto_build make -j8 make[1]: Entering directory '/<>' gcc -DPACKAGE_NAME=\"ReadStat\" -DPACKAGE_TARNAME=\"readstat\" -DPACKAGE_VERSION=\"1.1.8\" -DPACKAGE_STRING=\"ReadStat\ 1.1.8\" -DPACKAGE_BUGREPORT=\"https://github.com/WizardMac/ReadStat/issues\; -DPACKAGE_URL=\"https://github.com/WizardMac/ReadStat\; -DPACKAGE=\"readstat\" -DVERSION=\"1.1.8\" -DHAVE_STDIO_H=1 -DHAVE_STDLIB_H=1 -DHAVE_STRING_H=1 -DHAVE_INTTYPES_H=1 -DHAVE_STDINT_H=1 -DHAVE_STRINGS_H=1 -DHAVE_SYS_STAT_H=1 -DHAVE_SYS_TYPES_H=1 -DHAVE_UNISTD_H=1 -DSTDC_HEADERS=1 -DHAVE_DLFCN_H=1 -DLT_OBJDIR=\".libs/\" -DHAVE_ICONV=1 -DICONV_CONST= -I. -Wdate-time -D_FORTIFY_SOURCE=2 -DREADSTAT_VERSION=\"1.1.8\" -Wall -Werror -pedantic-errors -std=c99 -DHAVE_ZLIB=1 -DHAVE_XLSXWRITER=1 -DHAVE_CSVREADER=1 -g -O2 -ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat -Werror=format-security -c -o src/bin/readstat-readstat.o `test -f 'src/bin/readstat.c' || echo './'`src/bin/readstat.c gcc -DPACKAGE_NAME=\"ReadStat\" -DPACKAGE_TARNAME=\"readstat\" -DPACKAGE_VERSION=\"1.1.8\" -DPACKAGE_STRING=\"ReadStat\ 1.1.8\" -DPACKAGE_BUGREPORT=\"https://github.com/WizardMac/ReadStat/issues\; -DPACKAGE_URL=\"https://github.com/WizardMac/ReadStat\; -DPACKAGE=\"readstat\" -DVERSION=\"1.1.8\" -DHAVE_STDIO_H=1 -DHAVE_STDLIB_H=1 -DHAVE_STRING_H=1 -DHAVE_INTTYPES_H=1 -DHAVE_STDINT_H=1 -DHAVE_STRINGS_H=1 -DHAVE_SYS_STAT_H=1 -DHAVE_SYS_TYPES_H=1 -DHAVE_UNISTD_H=1 -DSTDC_HEADERS=1 -DHAVE_DLFCN_H=1 -DLT_OBJDIR=\".libs/\" -DHAVE_ICONV=1 -DICONV_CONST= -I. -Wdate-time -D_FORTIFY_SOURCE=2 -DREADSTAT_VERSION=\"1.1.8\" -Wall -Werror -pedantic-errors -std=c99 -DHAVE_ZLIB=1 -DHAVE_XLSXWRITER=1 -DHAVE_CSVREADER=1 -g -O2 -ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat -Werror=format-security -c -o src/bin/util/readstat-file_format.o `test -f 'src/bin/util/file_format.c' || echo './'`src/bin/util/file_format.c gcc -DPACKAGE_NAME=\"ReadStat\" -DPACKAGE_TARNAME=\"readstat\" -DPACKAGE_VERSION=\"1.1.8\" -DPACKAGE_STRING=\"ReadStat\ 1.1.8\" -DPACKAGE_BUGREPORT=\"https://github.com/WizardMac/ReadStat/issues\; -DPACKAGE_URL=\"https://github.com/WizardMac/ReadStat\; -DPACKAGE=\"readstat\" -DVERSION=\"1.1.8\" -DHAVE_STDIO_H=1 -DHAVE_STDLIB_H=1
Bug#1037658: marked as done (flatbuffers: ftbfs with GCC-13)
Your message dated Fri, 14 Jul 2023 05:20:19 + with message-id and subject line Bug#1037658: fixed in flatbuffers 2.0.8+dfsg1-3 has caused the Debian Bug report #1037658, regarding flatbuffers: ftbfs with GCC-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.) -- 1037658: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1037658 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: src:flatbuffers Version: 2.0.8+dfsg1-2 Severity: normal Tags: sid trixie User: debian-...@lists.debian.org Usertags: ftbfs-gcc-13 [This bug is targeted to the upcoming trixie 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-13/g++-13, but succeeds to build with gcc-12/g++-12. The severity of this report will be raised before the trixie release. The full build log can be found at: http://qa-logs.debian.net/2023/05/22/logs/flatbuffers_2.0.8+dfsg1-2_unstable_gccexp.log The last lines of the build log are at the end of this report. To build with GCC 13, either set CC=gcc-13 CXX=g++-13 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-13/porting_to.html [...] inlined from ‘static _Tp* std::allocator_traits >::allocate(allocator_type&, size_type) [with _Tp = unsigned char]’ at /usr/include/c++/13/bits/alloc_traits.h:482:28, inlined from ‘std::_Vector_base<_Tp, _Alloc>::pointer std::_Vector_base<_Tp, _Alloc>::_M_allocate(std::size_t) [with _Tp = unsigned char; _Alloc = std::allocator]’ at /usr/include/c++/13/bits/stl_vector.h:378:33, inlined from ‘std::_Vector_base<_Tp, _Alloc>::pointer std::_Vector_base<_Tp, _Alloc>::_M_allocate(std::size_t) [with _Tp = unsigned char; _Alloc = std::allocator]’ at /usr/include/c++/13/bits/stl_vector.h:375:7, inlined from ‘void std::vector<_Tp, _Alloc>::_M_range_insert(iterator, _ForwardIterator, _ForwardIterator, std::forward_iterator_tag) [with _ForwardIterator = const unsigned char*; _Tp = unsigned char; _Alloc = std::allocator]’ at /usr/include/c++/13/bits/vector.tcc:805:40, inlined from ‘std::vector<_Tp, _Alloc>::iterator std::vector<_Tp, _Alloc>::insert(const_iterator, _InputIterator, _InputIterator) [with _InputIterator = const unsigned char*; = void; _Tp = unsigned char; _Alloc = std::allocator]’ at /usr/include/c++/13/bits/stl_vector.h:1483:19, inlined from ‘const uint8_t* flatbuffers::AddFlatBuffer(std::vector&, const uint8_t*, size_t)’ at /<>/src/reflection.cpp:614:17: /usr/include/c++/13/bits/new_allocator.h:147:55: note: at offset [-9223372036854775808, -4] into destination object of size [4, 9223372036854775807] allocated by ‘operator new’ 147 | return static_cast<_Tp*>(_GLIBCXX_OPERATOR_NEW(__n * sizeof(_Tp))); | ^ [ 83%] Building CXX object CMakeFiles/flattests.dir/tests/flexbuffers_test.cpp.o /usr/bin/c++ -DFLATBUFFERS_LOCALE_INDEPENDENT=1 -I/<>/include -I/<>/grpc -I/<>/tests -I/<>/samples -g -O2 -ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -Wno-error=date-time -Wno-error=maybe-uninitialized -Wno-error=stringop-overflow -Wall -pedantic -Wextra -Wno-unused-parameter -Wold-style-cast -fsigned-char -Wnon-virtual-dtor -Wunused-result -Wunused-parameter -Werror=unused-parameter -Wmissing-declarations -Wzero-as-null-pointer-constant -faligned-new -Wextra-semi -std=c++17 -MD -MT CMakeFiles/flattests.dir/tests/flexbuffers_test.cpp.o -MF CMakeFiles/flattests.dir/tests/flexbuffers_test.cpp.o.d -o CMakeFiles/flattests.dir/tests/flexbuffers_test.cpp.o -c /<>/tests/flexbuffers_test.cpp [ 84%] Building CXX object CMakeFiles/flattests.dir/tests/fuzz_test.cpp.o /usr/bin/c++ -DFLATBUFFERS_LOCALE_INDEPENDENT=1 -I/<>/include -I/<>/grpc -I/<>/tests -I/<>/samples -g -O2 -ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -Wno-error=date-time -Wno-error=maybe-uninitialized -Wno-error=stringop-overflow -Wall
Bug#1037587: marked as done (barrier: ftbfs with GCC-13)
Your message dated Fri, 14 Jul 2023 05:19:37 + with message-id and subject line Bug#1037587: fixed in barrier 2.4.0+dfsg-4 has caused the Debian Bug report #1037587, regarding barrier: ftbfs with GCC-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.) -- 1037587: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1037587 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: src:barrier Version: 2.4.0+dfsg-3 Severity: normal Tags: sid trixie User: debian-...@lists.debian.org Usertags: ftbfs-gcc-13 [This bug is targeted to the upcoming trixie 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-13/g++-13, but succeeds to build with gcc-12/g++-12. The severity of this report will be raised before the trixie release. The full build log can be found at: http://qa-logs.debian.net/2023/05/22/logs/barrier_2.4.0+dfsg-3_unstable_gccexp.log The last lines of the build log are at the end of this report. To build with GCC 13, either set CC=gcc-13 CXX=g++-13 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-13/porting_to.html [...] cd /<>/builddir/src/lib/base && /usr/bin/c++ -DBARRIER_BUILD_DATE=\"20221014\" -DBARRIER_BUILD_NUMBER=1 -DBARRIER_REVISION=\"\" -DBARRIER_VERSION=\"2.4.0-release\" -DBARRIER_VERSION_MAJOR=2 -DBARRIER_VERSION_MINOR=4 -DBARRIER_VERSION_PATCH=0 -DBARRIER_VERSION_STRING=\"2.4.0-release-release\" -DHAVE_CONFIG_H -DNDEBUG -DSYSAPI_UNIX=1 -DWINAPI_XWINDOWS=1 -I/<>/gulrak-filesystem/include -I/<>/src/./lib -I/<>/builddir/src/lib -isystem /usr/include/avahi-compat-libdns_sd -g -O2 -ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -fPIC -std=c++14 -MD -MT src/lib/base/CMakeFiles/base.dir/String.cpp.o -MF CMakeFiles/base.dir/String.cpp.o.d -o CMakeFiles/base.dir/String.cpp.o -c /<>/src/lib/base/String.cpp [ 19%] Linking CXX static library libarch.a cd /<>/builddir/src/lib/arch && /usr/bin/cmake -P CMakeFiles/arch.dir/cmake_clean_target.cmake cd /<>/builddir/src/lib/arch && /usr/bin/cmake -E cmake_link_script CMakeFiles/arch.dir/link.txt --verbose=1 /usr/bin/ar qc libarch.a CMakeFiles/arch.dir/Arch.cpp.o CMakeFiles/arch.dir/ArchConsoleStd.cpp.o CMakeFiles/arch.dir/ArchDaemonNone.cpp.o CMakeFiles/arch.dir/IArchString.cpp.o CMakeFiles/arch.dir/unix/ArchConsoleUnix.cpp.o CMakeFiles/arch.dir/unix/ArchDaemonUnix.cpp.o CMakeFiles/arch.dir/unix/ArchInternetUnix.cpp.o CMakeFiles/arch.dir/unix/ArchLogUnix.cpp.o CMakeFiles/arch.dir/unix/ArchMultithreadPosix.cpp.o CMakeFiles/arch.dir/unix/ArchNetworkBSD.cpp.o CMakeFiles/arch.dir/unix/ArchSleepUnix.cpp.o CMakeFiles/arch.dir/unix/ArchStringUnix.cpp.o CMakeFiles/arch.dir/unix/ArchSystemUnix.cpp.o CMakeFiles/arch.dir/unix/ArchTaskBarXWindows.cpp.o CMakeFiles/arch.dir/unix/ArchTimeUnix.cpp.o CMakeFiles/arch.dir/unix/XArchUnix.cpp.o /usr/bin/ranlib libarch.a make[3]: Leaving directory '/<>/builddir' [ 19%] Built target arch [ 20%] Building CXX object src/lib/base/CMakeFiles/base.dir/Unicode.cpp.o cd /<>/builddir/src/lib/base && /usr/bin/c++ -DBARRIER_BUILD_DATE=\"20221014\" -DBARRIER_BUILD_NUMBER=1 -DBARRIER_REVISION=\"\" -DBARRIER_VERSION=\"2.4.0-release\" -DBARRIER_VERSION_MAJOR=2 -DBARRIER_VERSION_MINOR=4 -DBARRIER_VERSION_PATCH=0 -DBARRIER_VERSION_STRING=\"2.4.0-release-release\" -DHAVE_CONFIG_H -DNDEBUG -DSYSAPI_UNIX=1 -DWINAPI_XWINDOWS=1 -I/<>/gulrak-filesystem/include -I/<>/src/./lib -I/<>/builddir/src/lib -isystem /usr/include/avahi-compat-libdns_sd -g -O2 -ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -fPIC -std=c++14 -MD -MT src/lib/base/CMakeFiles/base.dir/Unicode.cpp.o -MF CMakeFiles/base.dir/Unicode.cpp.o.d -o CMakeFiles/base.dir/Unicode.cpp.o -c /<>/src/lib/base/Unicode.cpp [ 20%] Building CXX object src/lib/base/CMakeFiles/base.dir/XBase.cpp.o cd /<>/builddir/src/lib/base && /usr/bin/c++ -DBARRIER_BUILD_DATE=\"20221014\"
Bug#1037877: marked as done (uhd: ftbfs with GCC-13)
Your message dated Fri, 14 Jul 2023 04:11:10 +
with message-id
and subject line Bug#1037877: fixed in uhd 4.4.0.0+ds1-2
has caused the Debian Bug report #1037877,
regarding uhd: ftbfs with GCC-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.)
--
1037877: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1037877
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:uhd
Version: 4.3.0.0+ds1-5
Severity: normal
Tags: sid trixie
User: debian-...@lists.debian.org
Usertags: ftbfs-gcc-13
[This bug is targeted to the upcoming trixie 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-13/g++-13, but succeeds to build with gcc-12/g++-12. The
severity of this report will be raised before the trixie release.
The full build log can be found at:
http://qa-logs.debian.net/2023/05/22/logs/uhd_4.3.0.0+ds1-5_unstable_gccexp.log
The last lines of the build log are at the end of this report.
To build with GCC 13, either set CC=gcc-13 CXX=g++-13 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-13/porting_to.html
[...]
Underfull \hbox (badness 1) in paragraph at lines 6594--6595
[]| \T1/phv/m/n/10 STREAM_MODE_NUM_SAMPS_AND_DONE,
Underfull \hbox (badness 1) in paragraph at lines 6595--6596
[]| \T1/phv/m/n/10 STREAM_MODE_NUM_SAMPS_AND_MORE,
[1339]
Underfull \hbox (badness 2012) in paragraph at lines 6647--6649
[]\T1/phv/m/n/10 uhd::transport::bounded_buffer_detail$\OML/cmm/m/it/10 <$ \T1/
phv/m/n/10 elem_type $\OML/cmm/m/it/10 >$\T1/phv/m/n/10 ,
[1340] [1341] [1342] [1343] [1344]
Overfull \hbox (58.90596pt too wide) in paragraph at lines 7222--7224
[]| \T1/phv/m/n/10 chdr_packet::to_string_with_payload$\OML/cmm/m/it/10 <$ \T1/
phv/m/n/10 chdr_rfnoc::mgmt_payload
Overfull \hbox (60.05463pt too wide) in paragraph at lines 7281--7282
[]\T1/phv/m/n/10 UHD_ASYNC_METADATA_EVENT_CODE_SEQ_ERROR_IN_BURST
Overfull \hbox (65.69771pt too wide) in paragraph at lines 7289--7290
[]\T1/phv/m/n/10 UHD_ASYNC_METADATA_EVENT_CODE_UNDERFLOW_IN_PACKET
Overfull \hbox (24.66716pt too wide) in paragraph at lines 7291--7292
[]\T1/phv/m/n/10 UHD_ASYNC_METADATA_EVENT_CODE_USER_PAYLOAD
[1345] [1346]
Overfull \hbox (19.14113pt too wide) in paragraph at lines 7503--7504
[]\T1/phv/m/n/10 UHD_RFNOC_BLOCK_REGISTER_DIRECT_MB_ACCESS
Overfull \hbox (21.40903pt too wide) in paragraph at lines 7505--7506
[]\T1/phv/m/n/10 UHD_RFNOC_BLOCK_REGISTER_FOR_DEVICE_DIRECT
[1347] [1348] [1349] [1350] [1351]
Underfull \hbox (badness 1) in paragraph at lines 8091--8092
[]| \T1/phv/m/n/10 UHD_STREAM_MODE_START_CONTINUOUS,
Underfull \hbox (badness 1) in paragraph at lines 8092--8093
[]| \T1/phv/m/n/10 UHD_STREAM_MODE_STOP_CONTINUOUS,
[1352] [1353]
Underfull \hbox (badness 1) in paragraph at lines 8294--8296
[]| \T1/phv/m/n/10 uhd::soft_register_t$\OML/cmm/m/it/10 <$ \T1/phv/m/n/10 reg_
data_t, read-able,
[1354]) (./refman.aux)
LaTeX Warning: There were multiply-defined labels.
)
(see the transcript file for additional information){/usr/share/texlive/texmf-d
ist/fonts/enc/dvips/base/8r.enc}<
/usr/share/texlive/texmf-dist/fonts/type1/public/amsfonts/cm/cmr10.pfb>
Output written on refman.pdf (1474 pages, 4982545 bytes).
Transcript written on refman.log.
make[2]: Leaving directory
'/<>/obj-x86_64-linux-gnu/docs/doxygen/latex'
ninja: build stopped: subcommand failed.
dh_auto_build: error: cd obj-x86_64-linux-gnu && LC_ALL=C.UTF-8 ninja -j8 -v
returned exit code 1
make[1]: *** [debian/rules:29: override_dh_auto_build] Error 25
make[1]: Leaving directory '/<>'
make: *** [debian/rules:21: build] Error 2
dpkg-buildpackage: error: debian/rules build subprocess returned exit status 2
--- End Message ---
--- Begin Message ---
Source: uhd
Source-Version: 4.4.0.0+ds1-2
Done: A. Maitland Bottoms
We believe that the bug you reported is fixed in the latest version of
uhd, 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
Bug#1030932: marked as done (golang-github-go-enry-go-license-detector: FTBFS on mipsel: test failures)
Your message dated Fri, 14 Jul 2023 09:30:47 +0530 with message-id and subject line Re: Bug#1030932: golang-github-go-enry-go-license-detector: FTBFS on mipsel: test failures has caused the Debian Bug report #1030932, regarding golang-github-go-enry-go-license-detector: FTBFS on mipsel: test failures 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.) -- 1030932: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1030932 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: golang-github-go-enry-go-license-detector Version: 4.3.0+git20221007.a3a1cc6-1 Severity: serious Tags: ftbfs Justification: fails to build from source (but built successfully in the past) https://buildd.debian.org/status/fetch.php?pkg=golang-github-go-enry-go-license-detector=mipsel=4.3.0%2Bgit20221007.a3a1cc6-1%2Bb2=1675941345=0 /<>/_build/src/github.com/go-enry/go-license-detector/licensedb/dataset_test.go:26 +0x618 FAILgithub.com/go-enry/go-license-detector/licensedb602.300s ? github.com/go-enry/go-license-detector/licensedb/api[no test files] === RUN TestLocalFiler --- PASS: TestLocalFiler (0.00s) === RUN TestGitFiler --- PASS: TestGitFiler (0.13s) === RUN TestZipFiler --- PASS: TestZipFiler (0.00s) === RUN TestNestedFiler --- PASS: TestNestedFiler (0.00s) PASS ok github.com/go-enry/go-license-detector/licensedb/filer 0.203s === RUN TestSplitLicenseName --- PASS: TestSplitLicenseName (0.00s) PASS ok github.com/go-enry/go-license-detector/licensedb/internal 2.839s ? github.com/go-enry/go-license-detector/licensedb/internal/assets [no test files] === RUN TestFastlog --- PASS: TestFastlog (0.00s) PASS ok github.com/go-enry/go-license-detector/licensedb/internal/fastlog 0.068s === RUN TestNormalizeLines --- PASS: TestNormalizeLines (0.00s) PASS ok github.com/go-enry/go-license-detector/licensedb/internal/normalize 0.028s === RUN TestHTML --- PASS: TestHTML (0.00s) PASS ok github.com/go-enry/go-license-detector/licensedb/internal/processors 0.064s ? github.com/go-enry/go-license-detector/licensedb/internal/wmh [no test files] FAIL dh_auto_test: error: cd _build && go test -vet=off -v -p 4 github.com/go-enry/go-license-detector/cmd/license-detector github.com/go-enry/go-license-detector/licensedb github.com/go-enry/go-license-detector/licensedb/api github.com/go-enry/go-license-detector/licensedb/filer github.com/go-enry/go-license-detector/licensedb/internal github.com/go-enry/go-license-detector/licensedb/internal/assets github.com/go-enry/go-license-detector/licensedb/internal/fastlog github.com/go-enry/go-license-detector/licensedb/internal/normalize github.com/go-enry/go-license-detector/licensedb/internal/processors github.com/go-enry/go-license-detector/licensedb/internal/wmh returned exit code 1 make: *** [debian/rules:6: binary-arch] Error 25 Cheers -- Sebastian Ramacher --- End Message --- --- Begin Message --- Control: fixed -1 4.3.0+git20221007.a3a1cc6-3 On Thu, 13 Jul 2023 23:49:56 +0800 Shengjing Zhu wrote: > You look at the wrong log, it's golang-github-hhatto-gorst, not > golang-github-go-enry-go-license-detector. > It FTBFS on buildd currently. After increasing the timeout to 150m, the build is now succeeding on armel and mipsel. https://buildd.debian.org/status/fetch.php?pkg=golang-github-go-enry-go-license-detector=armel=4.3.0%2Bgit20221007.a3a1cc6-3=1689278197=0 https://buildd.debian.org/status/fetch.php?pkg=golang-github-go-enry-go-license-detector=mipsel=4.3.0%2Bgit20221007.a3a1cc6-3=1689281650=0--- End Message ---
Processed: Re: Bug#1030932: golang-github-go-enry-go-license-detector: FTBFS on mipsel: test failures
Processing control commands: > fixed -1 4.3.0+git20221007.a3a1cc6-3 Bug #1030932 [src:golang-github-go-enry-go-license-detector] golang-github-go-enry-go-license-detector: FTBFS on mipsel: test failures Marked as fixed in versions golang-github-go-enry-go-license-detector/4.3.0+git20221007.a3a1cc6-3. -- 1030932: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1030932 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1030932: golang-github-go-enry-go-license-detector: FTBFS on mipsel: test failures
Control: fixed -1 4.3.0+git20221007.a3a1cc6-3 On Thu, 13 Jul 2023 23:49:56 +0800 Shengjing Zhu wrote: > You look at the wrong log, it's golang-github-hhatto-gorst, not > golang-github-go-enry-go-license-detector. > It FTBFS on buildd currently. After increasing the timeout to 150m, the build is now succeeding on armel and mipsel. https://buildd.debian.org/status/fetch.php?pkg=golang-github-go-enry-go-license-detector=armel=4.3.0%2Bgit20221007.a3a1cc6-3=1689278197=0 https://buildd.debian.org/status/fetch.php?pkg=golang-github-go-enry-go-license-detector=mipsel=4.3.0%2Bgit20221007.a3a1cc6-3=1689281650=0
Bug#1012859: Info received (Syslog)
Dear Leslie, I'm sorry no one noticed your bug. Reply follows inline: Jeremy, thank you for following up on this bug! This brought the bug to my attention :) Leslie Rhorer writes: > On 7/13/2023 5:18 PM, Jeremy Davis wrote: >> [Just a random passer-by that might have an idea?] >> >> It looks to me like you are missing the firmware-realtek[1][2] >> (non-free) package?! > > No, I am not missing it. The package is broken in Bullseye. The > firmware is there, but does not work. It worked just fine in Buster, > but when I upgraded to Bullseye, the 10G NIC completely quit working. > It's been over a year, so I don't recall everything I did, but I spent > many, many hours trying to get the new firmware working, and many more > hours trying to extract the firmware from the oldstable package, and > then quite a few more hours trying to compile from source, but nothing > worked. I could not even get the source code to compile. Given your intention to upgrade from buster to bullseye, here is what you can try (please read to the end of this email first, because an alternative method is a better use of your time): 1a. Enable bullseye-backports (non-free), and 'apt install -t bullseye-backports firmware-linux firmware-misc-nonfree' which is currently 20230210-4~bpo11+1 2a. Reboot 3a. If both your NICs work, then it's a firmware bug. If this is the case, please report a bug against firmware-linux-nonfree 20210315-3. -- 1b. If the steps above are insufficient, 'apt install -t bullseye-backports linux-image-amd64' which is currently 6.1.20-2~bpo11+1 2b. Reboot. GRUB should automatically choose the backports kernel. 3b. Your NICs should work at this point. If they do, and you'd like to report a bug against the linux-image-amd64 version in bullseye, then please go ahead and do so, but please make sure that you've tested 5.10.178-3 before doing so:) > The bottom line is the firmware from the Buster non-free distro > works perfectly well, but noone has come forth with a fix for Bullseye, > and I have no reason to believe the firmware from Bookworm will work. > The NIC is an Asus PEB-10G/57811-1S 10GbE SFP+ Network Adapter which > employs a BCM 57811S controller. Maybe nobody knows that this specific hardware is broken? It may be that the Asus PEB-10G/57811-1S has some hardware quirks that Broadcom doesn't know about. In your original bug log you'll notice this snippet RTL8211E Gigabit Ethernet which is the Realtek one, Gibabit, RJ45 copper. I wonder if this one is a completely different NIC built into your motherboard. ie: the historically very buggy Realtek 8111E? Alternatively, if the 10GbE SFP+ PCIe adapter NIC uses a Realtek for gigabit PHY, then the nature of the bug could be that both both Realtek and Broadcom broke your NIC (either in the firmware on in the driver, or both). >> If you haven't already tried, I'd suggest that you try a clean >> bookworm install from ISO. FWIW bookworm now includes a separate >> "non-free-firmware" repo that is enabled by default. So the official >> installer should "just work". > I can try, but I really would not be well advised to do so until I > can get the dead system working again. Jeremy is right about how bookworm includes non-free-firmware by default, and also that the state of your hardware with bookworm should be tested first. The best use of your time will be to test with live media (USB or DVD). If you'd like to have a GUI for your test, please choose a variant you recognise and are comfortable with. The "standard" flavour is CLI only, which--alternatively--might be what you want (it's a smaller download ). https://cdimage.debian.org/debian-cd/current-live/amd64/iso-hybrid/ If the problem still exists in bookworm, then it needs to be fixed in bookworm before the fix can be backported to buster, and the live media is the fastest way to test this. Regards, Nicholas signature.asc Description: PGP signature
Bug#993849: authenticator
> If someone wants to help, feel contribute in the debian-rust team. I meant feel free :) --- Matthias Geiger OpenPGP_0x18BD106B3B6C5475.asc Description: OpenPGP public key OpenPGP_signature Description: OpenPGP digital signature
Bug#1012859: Info received (Syslog)
On 7/13/2023 5:18 PM, Jeremy Davis wrote: [Just a random passer-by that might have an idea?] On 14/7/23 07:14, Leslie Rhorer wrote: I filed report 1012859 to the Debian BTS over a year ago. Nothing has been done so far, and I have one cripped system and one dead system that needs to be upgraded to the most recent version, but I can't really proceed until the proper files get included into the Debian distro. Can someone please help? It looks to me like you are missing the firmware-realtek[1][2] (non-free) package?! No, I am not missing it. The package is broken in Bullseye. The firmware is there, but does not work. It worked just fine in Buster, but when I upgraded to Bullseye, the 10G NIC completely quit working. It's been over a year, so I don't recall everything I did, but I spent many, many hours trying to get the new firmware working, and many more hours trying to extract the firmware from the oldstable package, and then quite a few more hours trying to compile from source, but nothing worked. I could not even get the source code to compile. The bottom line is the firmware from the Buster non-free distro works perfectly well, but noone has come forth with a fix for Bullseye, and I have no reason to believe the firmware from Bookworm will work. The NIC is an Asus PEB-10G/57811-1S 10GbE SFP+ Network Adapter which employs a BCM 57811S controller. [1] https://packages.debian.org/bullseye/firmware-realtek [2] https://packages.debian.org/bookworm/firmware-realtek If you haven't already tried, I'd suggest that you try a clean bookworm install from ISO. FWIW bookworm now includes a separate "non-free-firmware" repo that is enabled by default. So the official installer should "just work". I can try, but I really would not be well advised to do so until I can get the dead system working again. If not, then I would suggest opening a new bug against the current installer. In the meantime, try manually installing the package (e.g. copy the deb via a USB stick). Hope that helps. Regards, Jeremy
Bug#993849: RE. authenticator
I uploaded the rust-gtk stack into debian which was the major missing chunk. If my tracking spreadsheet is correct (rust) authenticator is still missing five crates: scrypt, search-provider, libadwaita, gst-plugin-gtk4 and aes-gcm. Some of them have more reverse dependencies. I haven't looked into it further and I'm a bit busy atm. If bug #1017905 gets resolved libadwaita can enter debian; this is being worked on by myself and jbicha. The rest of the dependencies look straightforward to tackle. If someone wants to help, feel contribute in the debian-rust team. The "new" application should go under the gnome teams' umbrella imho. regards, Matthias Geiger OpenPGP_0x18BD106B3B6C5475.asc Description: OpenPGP public key OpenPGP_signature Description: OpenPGP digital signature
Bug#1040398: marked as done (python-pytest-benchmark: undeclared dependency on python3-py)
Your message dated Thu, 13 Jul 2023 22:32:16 + with message-id and subject line Bug#1040398: fixed in python-pytest-benchmark 3.2.2-4 has caused the Debian Bug report #1040398, regarding python-pytest-benchmark: undeclared dependency on python3-py 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.) -- 1040398: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1040398 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: python-pytest-benchmark Version: 3.2.2-3 Severity: grave Tags: fixed-upstream -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Dear maintainer, your package uses python3-py but does not declare a dependency on it, which makes the package unusable and breaks various autopkgtests, now that python3-pytest no longer depends on python3-py. The latest upstream release 4.0.0 has fixed the bug. Alternatively, you could add python3-py to your Depends. Cheers Timo -BEGIN PGP SIGNATURE- iQGzBAEBCgAdFiEEJvtDgpxjkjCIVtam+C8H+466LVkFAmSla4MACgkQ+C8H+466 LVkCMwwAtJmiWlni4r08kT/9NFEYOWKi5p4RoxEhXKGpMiThR5TlM6XvGWWTs+WU 8+JtjHZXq6XTsP7w1Ra/z27GsFeYbfjiI94YK52o7KqdsCokLDL1ur1oJ3uwHD6r JesIytQA7Q0Wrr/I+kgeK6mb0GXVgyCBycmDYLykTx0pF7f1CKF0wV4wVoBcLdA1 2MNVno9saSukfTgsTyjoe+MkZGyZOobEV51IV3bsdsPEb2+z6rO/TN3PpTtf1p+h jNUsNL1BGi0uwblk8coJGac43dX8tHUonfZlaePkPzOlt+Qm/HcIDBEYvQtCrrQJ yhbKIGeGIN7Rq9O6sAdnhzKKi34OkDXKW8ysNIvz4wCXmLPrgGJDYxMeIOn8KqmS sD6f9JB82WY5yHEhwvAmhRnhF3rTIDeuhllhQHZA0Dvnr+gCnyoBW7KQf8XqRyF7 x/MJffEM+NZOPYvejOfGKxwZPUQGrZMjMXEQDDN5XCvSLpRMsdHuWA0TidYqaJPF K2vXz3EE =zoLV -END PGP SIGNATURE- --- End Message --- --- Begin Message --- Source: python-pytest-benchmark Source-Version: 3.2.2-4 Done: Timo Röhling We believe that the bug you reported is fixed in the latest version of python-pytest-benchmark, 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 1040...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Timo Röhling (supplier of updated python-pytest-benchmark 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, 11 Jul 2023 23:49:23 +0200 Source: python-pytest-benchmark Architecture: source Version: 3.2.2-4 Distribution: unstable Urgency: medium Maintainer: Hugo Lefeuvre Changed-By: Timo Röhling Closes: 1040398 Changes: python-pytest-benchmark (3.2.2-4) unstable; urgency=medium . * Team upload. * Add missing depend on python3-py (Closes: #1040398) Checksums-Sha1: a13ec9b1301db8fce0a96103e71ece9fec1d5be6 2095 python-pytest-benchmark_3.2.2-4.dsc 48b800a2a9ccd1ff406667039469dad8646e59f6 3636 python-pytest-benchmark_3.2.2-4.debian.tar.xz ff11aa774fb8f75727f70fdc264d00e56a666bb2 6895 python-pytest-benchmark_3.2.2-4_amd64.buildinfo Checksums-Sha256: 19179b492d3b45dcd9b43986031502211bbf7073b834b506028a474577b478fc 2095 python-pytest-benchmark_3.2.2-4.dsc 6234b7d00d1f496ddd618af00f893107073f132cedb89e1b3eabae8685d241e5 3636 python-pytest-benchmark_3.2.2-4.debian.tar.xz 0ffe96b79091e1cf0bcabc0bc6d8a378bae63a1cfb9efb36215d7a6f8c20c804 6895 python-pytest-benchmark_3.2.2-4_amd64.buildinfo Files: b8788f02a94fb22b78ed02cf6e2c443a 2095 python optional python-pytest-benchmark_3.2.2-4.dsc ba6c7aa353796c7fa7d4f84b8b18bb3c 3636 python optional python-pytest-benchmark_3.2.2-4.debian.tar.xz b5b8e7a98116aa5b6fdd8500ae1e3fec 6895 python optional python-pytest-benchmark_3.2.2-4_amd64.buildinfo -BEGIN PGP SIGNATURE- iQHIBAEBCgAyFiEEJvtDgpxjkjCIVtam+C8H+466LVkFAmSt0LQUHHJvZWhsaW5n QGRlYmlhbi5vcmcACgkQ+C8H+466LVljNAwAgiyZj52J1T0M5C9MoLgQlZ8ejXa1 wwSeCQHM3bM72BI8YIFrxEZVWUNxFHWHC9LzbIJeTzrHBNKr6VnpT6jQzwsM65mn wIsOD0REuP6APA1LF+GvIphyLd5gem8/1xj+RLMQvmQMJF6ODjBeQnVtd/3foXf7 XzFtC2AJnDyTSeXbqzWgHoeB/oSHSG/Z6a+dMzelFw/saNL25Nbqg4b20AyNZNX8 n0t+ItmhUzJslFDPJiC2T/2R3Len/KwZ/mgYhZ1Hs0hid3KgPMMwLxZL2NkiF1wP HFv5MPItSs2OAO0Y2N8aHi8CIdKXsPDMPoyR+whmBMIK3vcJxpAOBdfGe87eM3vO jrEAWTTscALX1/XnI+sW0DmZl0DgXGXfx1jpGNcan+XvFW2PWyXrVe44JaT9xk3e LdQi6Bf9c5QC3Uo4EFPIT4gxDApXYXjJBmMMMjM9cBylYc4kVsjMo7s5r/p7nM40 tB2aURo6WD9Ya46TNnZINPxgoN1vAM6gAg4d =Irix -END PGP SIGNATURE End Message ---
Bug#1012859: Info received (Syslog)
[Just a random passer-by that might have an idea?] On 14/7/23 07:14, Leslie Rhorer wrote: I filed report 1012859 to the Debian BTS over a year ago. Nothing has been done so far, and I have one cripped system and one dead system that needs to be upgraded to the most recent version, but I can't really proceed until the proper files get included into the Debian distro. Can someone please help? It looks to me like you are missing the firmware-realtek[1][2] (non-free) package?! [1] https://packages.debian.org/bullseye/firmware-realtek [2] https://packages.debian.org/bookworm/firmware-realtek If you haven't already tried, I'd suggest that you try a clean bookworm install from ISO. FWIW bookworm now includes a separate "non-free-firmware" repo that is enabled by default. So the official installer should "just work". If not, then I would suggest opening a new bug against the current installer. In the meantime, try manually installing the package (e.g. copy the deb via a USB stick). Hope that helps. Regards, Jeremy OpenPGP_signature Description: OpenPGP digital signature
Processed: GCC 13 is the default now, raising severity to RC
Processing commands for cont...@bugs.debian.org: > severity 1037641 serious Bug #1037641 [src:edb-debugger] edb-debugger: ftbfs with GCC-13 Severity set to 'serious' from 'important' > severity 1037564 serious Bug #1037564 [src:0ad] 0ad: ftbfs with GCC-13 Severity set to 'serious' from 'important' > severity 1037565 serious Bug #1037565 [src:4ti2] 4ti2: ftbfs with GCC-13 Severity set to 'serious' from 'important' > severity 1037566 serious Bug #1037566 [src:abinit] abinit: ftbfs with GCC-13 Severity set to 'serious' from 'important' > severity 1037568 serious Bug #1037568 [src:actor-framework] actor-framework: ftbfs with GCC-13 Severity set to 'serious' from 'important' > severity 1037569 serious Bug #1037569 [src:aflplusplus] aflplusplus: ftbfs with GCC-13 Severity set to 'serious' from 'important' > severity 1037570 serious Bug #1037570 [src:afnix] afnix: ftbfs with GCC-13 Severity set to 'serious' from 'important' > severity 1037571 serious Bug #1037571 [src:aghermann] aghermann: ftbfs with GCC-13 Severity set to 'serious' from 'important' > severity 1037572 serious Bug #1037572 [src:android-file-transfer] android-file-transfer: ftbfs with GCC-13 Severity set to 'serious' from 'important' > severity 1037573 serious Bug #1037573 [src:android-platform-art] android-platform-art: ftbfs with GCC-13 Severity set to 'serious' from 'important' > severity 1037574 serious Bug #1037574 [src:android-platform-system-tools-hidl] android-platform-system-tools-hidl: ftbfs with GCC-13 Severity set to 'serious' from 'important' > severity 1037575 serious Bug #1037575 [src:android-platform-external-boringssl] android-platform-external-boringssl: ftbfs with GCC-13 Severity set to 'serious' from 'important' > severity 1037576 serious Bug #1037576 [src:android-platform-tools] android-platform-tools: ftbfs with GCC-13 Severity set to 'serious' from 'important' > severity 1037577 serious Bug #1037577 [src:antpm] antpm: ftbfs with GCC-13 Severity set to 'serious' from 'important' > severity 1037578 serious Bug #1037578 [src:apparmor] apparmor: ftbfs with GCC-13 Severity set to 'serious' from 'important' > severity 1037579 serious Bug #1037579 [src:armnn] armnn: ftbfs with GCC-13 Severity set to 'serious' from 'important' > severity 1037583 serious Bug #1037583 [src:audmes] audmes: ftbfs with GCC-13 Severity set to 'serious' from 'important' > severity 1037584 serious Bug #1037584 [src:audacity] audacity: ftbfs with GCC-13 Severity set to 'serious' from 'important' > severity 1037586 serious Bug #1037586 [src:ayatana-indicator-session] ayatana-indicator-session: ftbfs with GCC-13 Severity set to 'serious' from 'important' > severity 1037587 serious Bug #1037587 [src:barrier] barrier: ftbfs with GCC-13 Severity set to 'serious' from 'important' > severity 1037592 serious Bug #1037592 [src:biometryd] biometryd: ftbfs with GCC-13 Severity set to 'serious' from 'important' > severity 1037593 serious Bug #1037593 [src:binutils-avr] binutils-avr: ftbfs with GCC-13 Severity set to 'serious' from 'important' > severity 1037594 serious Bug #1037594 [src:blender] blender: ftbfs with GCC-13 Severity set to 'serious' from 'important' > severity 1037597 serious Bug #1037597 [src:broker] broker: ftbfs with GCC-13 Severity set to 'serious' from 'important' > severity 1037598 serious Bug #1037598 [src:capnproto] capnproto: ftbfs with GCC-13 Severity set to 'serious' from 'important' > severity 1037599 serious Bug #1037599 [src:bustools] bustools: ftbfs with GCC-13 Severity set to 'serious' from 'important' > severity 1037600 serious Bug #1037600 [src:casacore] casacore: ftbfs with GCC-13 Severity set to 'serious' from 'important' > severity 1037602 serious Bug #1037602 [src:ceph] ceph: ftbfs with GCC-13 Severity set to 'serious' from 'important' > severity 1037603 serious Bug #1037603 [src:civetweb] civetweb: ftbfs with GCC-13 Severity set to 'serious' from 'important' > severity 1037604 serious Bug #1037604 [src:chromium] chromium: ftbfs with GCC-13 Severity set to 'serious' from 'important' > severity 1037606 serious Bug #1037606 [src:clog] clog: ftbfs with GCC-13 Severity set to 'serious' from 'important' > severity 1037607 serious Bug #1037607 [src:colobot] colobot: ftbfs with GCC-13 Severity set to 'serious' from 'important' > severity 1037609 serious Bug #1037609 [src:content-hub] content-hub: ftbfs with GCC-13 Severity set to 'serious' from 'important' > severity 1037610 serious Bug #1037610 [src:criu] criu: ftbfs with GCC-13 Severity set to 'serious' from 'important' > severity 1037611 serious Bug #1037611 [src:cryptominisat] cryptominisat: ftbfs with GCC-13 Severity set to 'serious' from 'important' > severity 1037613 serious Bug #1037613 [src:cups-bjnp] cups-bjnp: ftbfs with GCC-13 Severity set to 'serious' from 'important' > severity 1037614 serious Bug #1037614 [src:cura-engine] cura-engine: ftbfs with GCC-13 Severity set to 'serious' from 'important' > severity 1037615 serious Bug #1037615 [src:cvise] cvise: ftbfs with
Bug#1040994: marked as done (python3-skimage must build depend on python3-imageio (>= 2.31.1-1~))
Your message dated Thu, 13 Jul 2023 21:55:33 +
with message-id
and subject line Bug#1040994: fixed in skimage 0.21.0-5
has caused the Debian Bug report #1040994,
regarding python3-skimage must build depend on python3-imageio (>= 2.31.1-1~)
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)
--
1040994: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1040994
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: python3-skimage
Version: 0.21.0-2
Severity: serious
https://ci.debian.net/data/autopkgtest/testing/amd64/s/skimage/35740206/log.gz
...
66s _ ERROR collecting io/tests/test_collection.py
_
66s ImportError while importing test module
'/usr/lib/python3/dist-packages/skimage/io/tests/test_collection.py'.
66s Hint: make sure your test modules/packages have valid Python names.
66s Traceback:
66s /usr/lib/python3.11/importlib/__init__.py:126: in import_module
66s return _bootstrap._gcd_import(name[level:], package, level)
66s /usr/lib/python3/dist-packages/skimage/io/tests/test_collection.py:5: in
66s import imageio.v3 as iio3
66s E ModuleNotFoundError: No module named 'imageio.v3'
66s === warnings summary
===
66s ../../../../usr/lib/python3/dist-packages/pkg_resources/__init__.py:121
66s /usr/lib/python3/dist-packages/pkg_resources/__init__.py:121:
DeprecationWarning: pkg_resources is deprecated as an API
66s warnings.warn("pkg_resources is deprecated as an API",
DeprecationWarning)
66s
66s ../../../../usr/lib/python3/dist-packages/pkg_resources/__init__.py:2870
66s /usr/lib/python3/dist-packages/pkg_resources/__init__.py:2870:
DeprecationWarning: Deprecated call to
`pkg_resources.declare_namespace('mpl_toolkits')`.
66s Implementing implicit namespace packages (as specified in PEP 420) is
preferred to `pkg_resources.declare_namespace`. See
https://setuptools.pypa.io/en/latest/references/keywords.html#keyword-namespace-packages
66s declare_namespace(pkg)
66s
66s ../../../../usr/lib/python3/dist-packages/pywt/__init__.py:14
66s /usr/lib/python3/dist-packages/pywt/__init__.py:14: DeprecationWarning:
The distutils package is deprecated and slated for removal in Python 3.12. Use
setuptools or check PEP 632 for potential alternatives
66s from distutils.version import LooseVersion
66s
66s ../../../../usr/lib/python3/dist-packages/_pytest/cacheprovider.py:433
66s /usr/lib/python3/dist-packages/_pytest/cacheprovider.py:433:
PytestCacheWarning: could not create cache path
/usr/lib/python3/dist-packages/skimage/.pytest_cache/v/cache/nodeids
66s config.cache.set("cache/nodeids", sorted(self.cached_nodeids))
66s
66s ../../../../usr/lib/python3/dist-packages/_pytest/cacheprovider.py:387
66s /usr/lib/python3/dist-packages/_pytest/cacheprovider.py:387:
PytestCacheWarning: could not create cache path
/usr/lib/python3/dist-packages/skimage/.pytest_cache/v/cache/lastfailed
66s config.cache.set("cache/lastfailed", self.lastfailed)
66s
66s ../../../../usr/lib/python3/dist-packages/_pytest/stepwise.py:56
66s /usr/lib/python3/dist-packages/_pytest/stepwise.py:56:
PytestCacheWarning: could not create cache path
/usr/lib/python3/dist-packages/skimage/.pytest_cache/v/cache/stepwise
66s session.config.cache.set(STEPWISE_CACHE_DIR, [])
66s
66s -- Docs: https://docs.pytest.org/en/stable/how-to/capture-warnings.html
66s === short test summary info
66s ERROR
../../../../usr/lib/python3/dist-packages/skimage/io/tests/test_collection.py
66s Interrupted: 1 error during collection
66s === 5 skipped, 6 warnings, 1 error in 3.69s
67s autopkgtest [00:30:25]: test python3: ---]
67s autopkgtest [00:30:25]: test python3: - - - - - - - - - - results - - - -
- - - - - -
67s python3 FAIL non-zero exit status 2
This is due to
skimage (0.21.0-2) unstable; urgency=medium
* Drop Don-t-import-unavailable-imageio.v3.patch: package is available now
...
-- Ole Streicher Mon, 10 Jul 2023 15:39:10 +0200
Updating the build dependency to python3-imageio (>= 2.31.1-1)
(which will also version the runtime dependency) will ensure
that a recent enough version of python3-imageio is installed
when building or running skimage.
--- End Message ---
--- Begin Message ---
Source: skimage
Source-Version: 0.21.0-5
Done: Ole Streicher
We believe that the bug you
Bug#1012859: Info received (Syslog)
I filed report 1012859 to the Debian BTS over a year ago. Nothing has been done so far, and I have one cripped system and one dead system that needs to be upgraded to the most recent version, but I can't really proceed until the proper files get included into the Debian distro. Can someone please help? On 6/15/2022 3:12 PM, Debian Bug Tracking System wrote: Thank you for the additional information you have supplied regarding this Bug report. This is an automatically generated reply to let you know your message has been received. Your message is being forwarded to the package maintainers and other interested parties for their attention; they will reply in due course. Your message has been sent to the package maintainer(s): Debian Install Team If you wish to submit further information on this problem, please send it to1012...@bugs.debian.org. Please do not send mail toow...@bugs.debian.org unless you wish to report a problem with the Bug-tracking system.
Bug#1040901: linux modules must not be signed with CA key, bump ABI every upload
On Wed, 12 Jul 2023 10:05:03 +0200 Julian Andres Klode wrote: [...] > A reasonable compromise at a first step for a limited time is to > ensure that > > 1) the kernel refuses to load modules for a different ABI in lockdown, > for example, the modprobe --force-vermagic does not work anymore. [...] I already implemented that in 2016. Did it break? Ben. -- Ben Hutchings Every program is either trivial or else contains at least one bug signature.asc Description: This is a digitally signed message part
Bug#1041002: easy-format FTBFS with ocaml-dune 3.9.0
Source: easy-format Version: 1.3.4-1 Severity: serious Tags: ftbfs trixie sid https://tests.reproducible-builds.org/debian/rb-pkg/trixie/arm64/easy-format.html ... debian/rules override_dh_auto_install make[1]: Entering directory '/build/easy-format-1.3.4' dune install --destdir=/build/easy-format-1.3.4/debian/tmp --prefix=/usr --libdir=../usr/lib/ocaml dune: option '--libdir': the path must be absolute to avoid ambiguity Usage: dune install [OPTION]… [PACKAGE]… Try 'dune install --help' or 'dune --help' for more information. make[1]: *** [debian/rules:22: override_dh_auto_install] Error 1
Processed: severity of 1040966 is important
Processing commands for cont...@bugs.debian.org: > severity 1040966 important Bug #1040966 [src:linux] linux-image-6.1.0-9-amd64: Thinkpad T470 fails to wake from suspend after bookworm upgrade Severity set to 'important' from 'serious' > thanks Stopping processing here. Please contact me if you need assistance. -- 1040966: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1040966 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1041001: cryptokit FTBFS with ocaml-dune 3.9.0
Source: cryptokit Version: 1.18-1 Severity: serious Tags: ftbfs trixie sid https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/cryptokit.html ... debian/rules override_dh_auto_install make[1]: Entering directory '/build/1st/cryptokit-1.18' dune install --destdir=/build/1st/cryptokit-1.18/debian/tmp --prefix=/usr --libdir=../usr/lib/ocaml dune: option '--libdir': the path must be absolute to avoid ambiguity Usage: dune install [OPTION]… [PACKAGE]… Try 'dune install --help' or 'dune --help' for more information. make[1]: *** [debian/rules:20: override_dh_auto_install] Error 1
Bug#1041000: cppo FTBFS with ocaml-dune 3.9.0
Source: cppo Version: 1.6.9-1 Severity: serious Tags: ftbfs trixie sid https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/cppo.html ... debian/rules override_dh_auto_install make[1]: Entering directory '/build/1st/cppo-1.6.9' dune install --destdir=/build/1st/cppo-1.6.9/debian/tmp --prefix=/usr --libdir=../usr/lib/ocaml dune: option '--libdir': the path must be absolute to avoid ambiguity Usage: dune install [OPTION]… [PACKAGE]… Try 'dune install --help' or 'dune --help' for more information. make[1]: *** [debian/rules:19: override_dh_auto_install] Error 1
Bug#1040999: camlimages FTBFS with ocaml-dune 3.9.0
Source: camlimages Version: 1:5.0.4-2 Severity: serious Tags: ftbfs trixie sid https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/camlimages.html ... debian/rules override_dh_auto_install make[1]: Entering directory '/build/1st/camlimages-5.0.4' dune install --destdir=/build/1st/camlimages-5.0.4/debian/tmp --prefix=/usr --libdir=../usr/lib/ocaml dune: option '--libdir': the path must be absolute to avoid ambiguity Usage: dune install [OPTION]… [PACKAGE]… Try 'dune install --help' or 'dune --help' for more information. make[1]: *** [debian/rules:15: override_dh_auto_install] Error 1
Bug#1040998: chromaprint FTBFS with googletest 1.13.0
Source: chromaprint Version: 1.5.1-2 Severity: serious Tags: ftbfs trixie sid https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/chromaprint.html ... In file included from /usr/src/googletest/googletest/include/gtest/gtest-message.h:57, from /usr/src/googletest/googletest/include/gtest/gtest-assertion-result.h:46, from /usr/src/googletest/googletest/include/gtest/gtest.h:64, from /usr/src/googletest/googletest/src/gtest-all.cc:38: /usr/src/googletest/googletest/include/gtest/internal/gtest-port.h:270:2: error: #error C++ versions less than C++14 are not supported. 270 | #error C++ versions less than C++14 are not supported. | ^ ... This can be fixed by setting CMAKE_CXX_STANDARD to 14 in CMakeLists.txt
Processed: retitle 1040994 to python3-skimage must build depend on python3-imageio (>= 2.31.1-1~)
Processing commands for cont...@bugs.debian.org: > retitle 1040994 python3-skimage must build depend on python3-imageio (>= > 2.31.1-1~) Bug #1040994 [python3-skimage] python3-skimage must build depend on python3-imageio (>= 2.31.1-1) Changed Bug title to 'python3-skimage must build depend on python3-imageio (>= 2.31.1-1~)' from 'python3-skimage must build depend on python3-imageio (>= 2.31.1-1)'. > thanks Stopping processing here. Please contact me if you need assistance. -- 1040994: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1040994 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1040995: librust-kv-log-macro-dev is no longer installable
Package: librust-kv-log-macro-dev Version: 1.0.8-2 Severity: serious Tags: trixie sid The following packages have unmet dependencies: librust-kv-log-macro-dev : Depends: librust-log-0.4+kv-unstable-dev (>= 0.4.8)
Bug#1040994: python3-skimage must build depend on python3-imageio (>= 2.31.1-1)
Package: python3-skimage
Version: 0.21.0-2
Severity: serious
https://ci.debian.net/data/autopkgtest/testing/amd64/s/skimage/35740206/log.gz
...
66s _ ERROR collecting io/tests/test_collection.py
_
66s ImportError while importing test module
'/usr/lib/python3/dist-packages/skimage/io/tests/test_collection.py'.
66s Hint: make sure your test modules/packages have valid Python names.
66s Traceback:
66s /usr/lib/python3.11/importlib/__init__.py:126: in import_module
66s return _bootstrap._gcd_import(name[level:], package, level)
66s /usr/lib/python3/dist-packages/skimage/io/tests/test_collection.py:5: in
66s import imageio.v3 as iio3
66s E ModuleNotFoundError: No module named 'imageio.v3'
66s === warnings summary
===
66s ../../../../usr/lib/python3/dist-packages/pkg_resources/__init__.py:121
66s /usr/lib/python3/dist-packages/pkg_resources/__init__.py:121:
DeprecationWarning: pkg_resources is deprecated as an API
66s warnings.warn("pkg_resources is deprecated as an API",
DeprecationWarning)
66s
66s ../../../../usr/lib/python3/dist-packages/pkg_resources/__init__.py:2870
66s /usr/lib/python3/dist-packages/pkg_resources/__init__.py:2870:
DeprecationWarning: Deprecated call to
`pkg_resources.declare_namespace('mpl_toolkits')`.
66s Implementing implicit namespace packages (as specified in PEP 420) is
preferred to `pkg_resources.declare_namespace`. See
https://setuptools.pypa.io/en/latest/references/keywords.html#keyword-namespace-packages
66s declare_namespace(pkg)
66s
66s ../../../../usr/lib/python3/dist-packages/pywt/__init__.py:14
66s /usr/lib/python3/dist-packages/pywt/__init__.py:14: DeprecationWarning:
The distutils package is deprecated and slated for removal in Python 3.12. Use
setuptools or check PEP 632 for potential alternatives
66s from distutils.version import LooseVersion
66s
66s ../../../../usr/lib/python3/dist-packages/_pytest/cacheprovider.py:433
66s /usr/lib/python3/dist-packages/_pytest/cacheprovider.py:433:
PytestCacheWarning: could not create cache path
/usr/lib/python3/dist-packages/skimage/.pytest_cache/v/cache/nodeids
66s config.cache.set("cache/nodeids", sorted(self.cached_nodeids))
66s
66s ../../../../usr/lib/python3/dist-packages/_pytest/cacheprovider.py:387
66s /usr/lib/python3/dist-packages/_pytest/cacheprovider.py:387:
PytestCacheWarning: could not create cache path
/usr/lib/python3/dist-packages/skimage/.pytest_cache/v/cache/lastfailed
66s config.cache.set("cache/lastfailed", self.lastfailed)
66s
66s ../../../../usr/lib/python3/dist-packages/_pytest/stepwise.py:56
66s /usr/lib/python3/dist-packages/_pytest/stepwise.py:56:
PytestCacheWarning: could not create cache path
/usr/lib/python3/dist-packages/skimage/.pytest_cache/v/cache/stepwise
66s session.config.cache.set(STEPWISE_CACHE_DIR, [])
66s
66s -- Docs: https://docs.pytest.org/en/stable/how-to/capture-warnings.html
66s === short test summary info
66s ERROR
../../../../usr/lib/python3/dist-packages/skimage/io/tests/test_collection.py
66s Interrupted: 1 error during collection
66s === 5 skipped, 6 warnings, 1 error in 3.69s
67s autopkgtest [00:30:25]: test python3: ---]
67s autopkgtest [00:30:25]: test python3: - - - - - - - - - - results - - - -
- - - - - -
67s python3 FAIL non-zero exit status 2
This is due to
skimage (0.21.0-2) unstable; urgency=medium
* Drop Don-t-import-unavailable-imageio.v3.patch: package is available now
...
-- Ole Streicher Mon, 10 Jul 2023 15:39:10 +0200
Updating the build dependency to python3-imageio (>= 2.31.1-1)
(which will also version the runtime dependency) will ensure
that a recent enough version of python3-imageio is installed
when building or running skimage.
Bug#1040790: marked as done (installation-reports: ID in /etc/machine-id and /var/lib/dbus/machine-id mismatch on fresh debian 12 installation)
Your message dated Thu, 13 Jul 2023 18:36:20 + with message-id and subject line Bug#1040790: fixed in dbus 1.15.6-2 has caused the Debian Bug report #1040790, regarding installation-reports: ID in /etc/machine-id and /var/lib/dbus/machine-id mismatch on fresh debian 12 installation 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.) -- 1040790: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1040790 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: installation-reports Severity: serious Tags: d-i Justification: https://wiki.debian.org/MachineId (Please provide enough information to help the Debian maintainers evaluate the report efficiently - e.g., by filling in the sections below.) Boot method: CD/network Image version: http://ftp.debian.org/debian/dists/bookworm/main/installer-amd64/ Date: 2023-07-10 Machine: Virtual-Maschine Partitions: Disk /dev/vda: 10 GiB, 10737418240 bytes, 20971520 sectors Units: sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 512 bytes / 512 bytes Disklabel type: dos Disk identifier: 0xcf0c07c3 Device Boot Start End Sectors Size Id Type /dev/vda1 2048 2000895 1998848 976M 82 Linux swap / Solaris /dev/vda2 *2000896 20969471 189685769G 83 Linux Base System Installation Checklist: [O] = OK, [E] = Error (please elaborate below), [ ] = didn't try it Initial boot: [O] Detect network card:[O] Configure network: [O] Detect media: [O] Load installer modules: [O] Clock/timezone setup: [O] User/password setup:[O] Detect hard drives: [O] Partition hard drives: [O] Install base system:[O] Install tasks: [O] Install boot loader:[O] Overall install:[O]? Comments/Problems: After installation was finished and the system has been restarted the files "/etc/machine-id" and "/var/lib/dbus/machine-id" are not linked in any way (no soft or hardlink) and the ID inside the files differ from each other. Expected: "cat /etc/machine-id /var/lib/dbus/machine-id" should return the same ID two times Workaround: rm /etc/machine-id /var/lib/dbus/machine-id && dbus-uuidgen --ensure=/etc/machine-id && dbus-uuidgen --ensure -- Package-specific info: == Installer lsb-release: == DISTRIB_ID=Debian DISTRIB_DESCRIPTION="Debian GNU/Linux installer" DISTRIB_RELEASE="12 (bookworm) - installer build 20230607" X_INSTALLATION_MEDIUM=netboot == Installer hardware-summary: == uname -a: Linux debian-test 6.1.0-9-amd64 #1 SMP PREEMPT_DYNAMIC Debian 6.1.27-1 (2023-05-08) x86_64 GNU/Linux lspci -knn: 00:00.0 Host bridge [0600]: Intel Corporation 440FX - 82441FX PMC [Natoma] [8086:1237] (rev 02) lspci -knn: Subsystem: Red Hat, Inc. Qemu virtual machine [1af4:1100] lspci -knn: 00:01.0 ISA bridge [0601]: Intel Corporation 82371SB PIIX3 ISA [Natoma/Triton II] [8086:7000] lspci -knn: Subsystem: Red Hat, Inc. Qemu virtual machine [1af4:1100] lspci -knn: 00:01.1 IDE interface [0101]: Intel Corporation 82371SB PIIX3 IDE [Natoma/Triton II] [8086:7010] lspci -knn: Subsystem: Red Hat, Inc. Qemu virtual machine [1af4:1100] lspci -knn: Kernel driver in use: ata_piix lspci -knn: Kernel modules: ata_piix, ata_generic lspci -knn: 00:01.3 Bridge [0680]: Intel Corporation 82371AB/EB/MB PIIX4 ACPI [8086:7113] (rev 03) lspci -knn: Subsystem: Red Hat, Inc. Qemu virtual machine [1af4:1100] lspci -knn: 00:02.0 VGA compatible controller [0300]: Cirrus Logic GD 5446 [1013:00b8] lspci -knn: Subsystem: Red Hat, Inc. QEMU Virtual Machine [1af4:1100] lspci -knn: Kernel driver in use: cirrus lspci -knn: Kernel modules: cirrus lspci -knn: 00:03.0 Ethernet controller [0200]: Red Hat, Inc. Virtio network device [1af4:1000] lspci -knn: Subsystem: Red Hat, Inc. Device [1af4:0001] lspci -knn: Kernel driver in use: virtio-pci lspci -knn: Kernel modules: virtio_pci lspci -knn: 00:04.0 Communication controller [0780]: Red Hat, Inc. Virtio console [1af4:1003] lspci -knn: Subsystem: Red Hat, Inc. Device [1af4:0003] lspci -knn: Kernel driver in use: virtio-pci lspci -knn: Kernel modules: virtio_pci lspci -knn: 00:05.0 SCSI storage controller [0100]: Red Hat, Inc. Virtio block device [1af4:1001] lspci -knn: Subsystem: Red Hat, Inc. Device [1af4:0002] lspci -knn: Kernel driver in use: virtio-pci lspci -knn:
Bug#1040790: installation-reports: ID in /etc/machine-id and /var/lib/dbus/machine-id mismatch on fresh debian 12 installation
On Mon, 10 Jul 2023 at 17:27:50 +0200, yogg wrote: > After installation was finished and the system has been restarted the > files "/etc/machine-id" and "/var/lib/dbus/machine-id" are not linked > in any way (no soft or hardlink) and the ID inside the files differ from > each other. This was a regression in bookworm, thank you for reporting it. A fix is in unstable, and on its way into testing and a future bookworm stable update (hopefully as soon as 12.1, which is due in just over a week). What user-visible symptoms, if any, did this cause for you? The machine ID can be used by almost anything (in the same way that almost anything can use the hostname), so it's difficult to get a clear picture of how bad this is, or how much risk it would be acceptable to take when fixing this up on existing systems. > Workaround: > rm /etc/machine-id /var/lib/dbus/machine-id && dbus-uuidgen > --ensure=/etc/machine-id && dbus-uuidgen --ensure "rm /var/lib/dbus/machine-id && dbus-uuidgen --ensure" would be enough, in fact. smcv
Bug#1030955: marked as done (golang-github-hhatto-gorst: autopkgtest failure)
Your message dated Thu, 13 Jul 2023 17:26:57 + with message-id and subject line Bug#1030955: fixed in golang-github-hhatto-gorst 0.0~git20181029.ca9f730-3 has caused the Debian Bug report #1030955, regarding golang-github-hhatto-gorst: autopkgtest failure 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.) -- 1030955: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1030955 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: golang-github-hhatto-gorst Version: 0.0~git20181029.ca9f730-2 Severity: serious https://ci.debian.net/data/autopkgtest/testing/amd64/g/golang-github-hhatto-gorst/31199561/log.gz ... dh_auto_test -O--builddirectory=_build -O--buildsystem=golang cd _build && go test -vet=off -v -p 64 github.com/hhatto/gorst github.com/hhatto/gorst/cmd/gorst === RUN TestExampleOfSimpleText 2023/02/09 22:05:24 open data/simple.rst: no such file or directory --- PASS: TestExampleOfSimpleText (0.00s) === RUN TestExampleOfPydebsignReadme 2023/02/09 22:05:24 open data/pydebsign.readme.rst: no such file or directory rst_test.go:46: invalid convert --- FAIL: TestExampleOfPydebsignReadme (0.00s) === RUN TestExampleOfMeowReadme 2023/02/09 22:05:24 open data/meow.readme.rst: no such file or directory --- PASS: TestExampleOfMeowReadme (0.00s) === RUN TestExampleOfAutopep8Readme 2023/02/09 22:05:24 open data/autopep8.readme.rst: no such file or directory rst_test.go:61: contain heading in autopep8 rst_test.go:64: para in autopep8 --- FAIL: TestExampleOfAutopep8Readme (0.00s) === RUN TestExampleOfHeadingTitle --- PASS: TestExampleOfHeadingTitle (0.00s) === RUN TestExampleOfHeading --- PASS: TestExampleOfHeading (0.00s) === RUN TestAutoLink --- PASS: TestAutoLink (0.00s) === RUN TestLinkContainsUnderbar --- PASS: TestLinkContainsUnderbar (0.00s) === RUN TestLinkComplexCases --- PASS: TestLinkComplexCases (0.00s) === RUN TestUnquotedRefLinkUnderbarWithDot --- PASS: TestUnquotedRefLinkUnderbarWithDot (0.00s) === RUN TestUnquotedRefLinkUnderbarWithDotAndList --- PASS: TestUnquotedRefLinkUnderbarWithDotAndList (0.00s) === RUN TestSimpleLinkRef --- PASS: TestSimpleLinkRef (0.00s) === RUN TestNotLinkRef --- PASS: TestNotLinkRef (0.00s) === RUN TestEmbeddedURI --- PASS: TestEmbeddedURI (0.00s) === RUN TestEmbeddedURIwithNewline --- PASS: TestEmbeddedURIwithNewline (0.00s) === RUN TestEmbeddedAnonymouseURI --- PASS: TestEmbeddedAnonymouseURI (0.00s) === RUN TestImage --- PASS: TestImage (0.00s) === RUN TestImageWithAlt --- PASS: TestImageWithAlt (0.00s) === RUN TestImageWithTarget --- PASS: TestImageWithTarget (0.00s) === RUN TestImageWithAltAndTarget --- PASS: TestImageWithAltAndTarget (0.00s) === RUN TestGridTable --- PASS: TestGridTable (0.00s) === RUN TestHeaderLessGridTable --- PASS: TestHeaderLessGridTable (0.00s) === RUN TestApplicationDepent --- PASS: TestApplicationDepent (0.00s) FAIL FAILgithub.com/hhatto/gorst 0.006s ? github.com/hhatto/gorst/cmd/gorst [no test files] FAIL dh_auto_test: error: cd _build && go test -vet=off -v -p 64 github.com/hhatto/gorst github.com/hhatto/gorst/cmd/gorst returned exit code 1 make: *** [debian/rules:6: build] Error 25 The Ubuntu diff contains a patch that looks like a workaround (untested). --- End Message --- --- Begin Message --- Source: golang-github-hhatto-gorst Source-Version: 0.0~git20181029.ca9f730-3 Done: Pirate Praveen We believe that the bug you reported is fixed in the latest version of golang-github-hhatto-gorst, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 1030...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Pirate Praveen (supplier of updated golang-github-hhatto-gorst 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: Thu, 13 Jul 2023 22:26:02 +0530 Source: golang-github-hhatto-gorst Architecture: source Version: 0.0~git20181029.ca9f730-3 Distribution: unstable Urgency: medium Maintainer: Debian Go Packaging Team Changed-By: Pirate Praveen Closes: 1030955 Changes: golang-github-hhatto-gorst (0.0~git20181029.ca9f730-3) unstable; urgency=medium .
Bug#1040988: Clashes with existing composite manager
Package: picom Version: 10.2-1 Severity: serious picom adds an autostart file which makes it automatically start on session login. Today I noticed that journald/rsyslog ran while and my logs were flodded with the following messages (I was logged into a GNOME session at that time): Jul 13 19:18:11 pluto picom.desktop[2236]: [ 13.07.2023 19:18:11.510 redirect_start FATAL ERROR ] Another composite manager is already running (and does not handle _NET_WM_CM_Sn correctly) Jul 13 19:18:11 pluto picom.desktop[2236]: [ 13.07.2023 19:18:11.510 redirect_start FATAL ERROR ] Another composite manager is already running (and does not handle _NET_WM_CM_Sn correctly) Jul 13 19:18:11 pluto picom.desktop[2236]: [ 13.07.2023 19:18:11.510 redirect_start FATAL ERROR ] Another composite manager is already running (and does not handle _NET_WM_CM_Sn correctly) Within minutes, my disk was filled with hundreds of megabytes of log data (/var/log/syslog was over 1GB), before I killed the rogue picom process. -- System Information: Debian Release: trixie/sid APT prefers unstable APT policy: (500, 'unstable'), (200, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 6.3.0-2-amd64 (SMP w/4 CPU threads; PREEMPT) Kernel taint flags: TAINT_FIRMWARE_WORKAROUND Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8), LANGUAGE not set Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages picom depends on: ii libc62.37-5 ii libconfig9 1.5-0.4 ii libdbus-1-3 1.14.8-2 ii libegl1 1.6.0-1 pn libev4 ii libgl1 1.6.0-1 ii libpcre3 2:8.39-15 ii libpixman-1-00.42.2-1 ii libx11-6 2:1.8.6-1 ii libx11-xcb1 2:1.8.6-1 ii libxcb-composite01.15-1 ii libxcb-damage0 1.15-1 ii libxcb-glx0 1.15-1 ii libxcb-image00.4.0-2 ii libxcb-present0 1.15-1 ii libxcb-randr01.15-1 ii libxcb-render-util0 0.3.9-1+b1 ii libxcb-render0 1.15-1 ii libxcb-shape01.15-1 ii libxcb-sync1 1.15-1 ii libxcb-xfixes0 1.15-1 ii libxcb-xinerama0 1.15-1 ii libxcb1 1.15-1 ii python3 3.11.4-5 picom recommends no packages. picom suggests no packages.
Bug#1030932: golang-github-go-enry-go-license-detector: FTBFS on mipsel: test failures
On Thu, Jul 13 2023 at 11:49:56 PM +08:00:00 +08:00:00, Shengjing Zhu wrote: Control: reopen -1 Thanks, I noticed the failure on buildd and was going to reopen it and found you did it aready. Hi, On Thu, Jul 13, 2023 at 6:09 PM Pirate Praveen wrote: On Thu, 9 Feb 2023 14:40:48 +0100 Sebastian Ramacher wrote: > Source: golang-github-go-enry-go-license-detector > Version: 4.3.0+git20221007.a3a1cc6-1 > Severity: serious > Tags: ftbfs > Justification: fails to build from source (but built successfully in the past) > > https://buildd.debian.org/status/fetch.php?pkg=golang-github-go-enry-go-license-detector=mipsel=4.3.0%2Bgit20221007.a3a1cc6-1%2Bb2=1675941345=0 > This looks like a temporary error, last build was passing https://buildd.debian.org/status/fetch.php?pkg=golang-github-hhatto-gorst=mipsel=0.0%7Egit20181029.ca9f730-2%2Bb6=1681037294=0 You look at the wrong log, it's golang-github-hhatto-gorst, not golang-github-go-enry-go-license-detector. It FTBFS on buildd currently. Thanks for pointing out the mistake. I was looking at both failures and got confused. -- Shengjing Zhu
Bug#1030955: golang-github-hhatto-gorst: autopkgtest failure
On Thu, 13 Jul 2023 21:24:53 +0530 Nilesh Patra wrote: > Control: tags -1 patch > > On Thu, Jul 13, 2023 at 03:10:40PM +0530, Pirate Praveen wrote: > > On Fri, 10 Feb 2023 00:07:51 +0200 Adrian Bunk wrote: > > > The Ubuntu diff contains a patch that looks like a workaround (untested). > > > > This patch says data directory is reserved for golang autopkgtest in Ubuntu. > > Is this the same on debian too? If yes, that looks like a bad idea to me. > > AFAIK, it uses the standard AUTOPKGTEST_TMP directory which is the > standard across debian. I got the same impression on skimming through > dh-golang code. > > As far as fix for your package is concerned, it is as simple as avoiding > to remove entire data directory (which is just 28K in size). I'm able to get > autopkgtests passing locally. Patch pasted > inline. Thanks. I guess I was over enthusiastic to suppress I: golang-github-hhatto-gorst-dev: package-contains-documentation-outside-usr-share-doc [usr/share/gocode/src/github.com/hhatto/gorst/data/autopep8.readme.rst] and did not notice the autopkgtest failure then. I'm uploading the fix you suggested.
Bug#1040774: msolve FTBFS on 32bit: test failure and hang
Control: severity -1 important On Thu 13 Jul 2023 12:21:48 PM -04, Doug Torrance wrote: [[PGP Signed Part:Undecided]] Control: forwarded -1 https://github.com/algebraic-solving/msolve/issues/66 On Mon 10 Jul 2023 03:33:43 PM +03, Adrian Bunk wrote: Source: msolve Version: 0.5.0-1 Severity: serious Tags: ftbfs https://buildd.debian.org/status/logs.php?pkg=msolve=0.5.0-1 ... make check-TESTS make[3]: Entering directory '/<>' make[4]: Entering directory '/<>' PASS: fglm_build_matrixn_radical_shape-31 PASS: neogb_io PASS: fglm_build_matrixn_nonradical_shape-31 PASS: fglm_build_matrixn_nonradical_radicalshape-31 FAIL: test/diff/diff_elim-qq.sh PASS: test/diff/diff_elim-31.sh PASS: test/diff/diff_F4SAT-31.sh FAIL: test/diff/diff_kat6-31.sh FAIL: test/diff/diff_eco11-31.sh E: Build killed with signal TERM after 150 minutes of inactivity [[End of PGP Signed Part]] The latest upload (0.5.0-2) of msolve skips the tests on 32-bit architectures so that it will still build. The issue has been reported upstream and hopefully will be fixed in a future release. Since the program still works for some inputs on these architectures, I'm dropping the severity of the bug to "important". signature.asc Description: PGP signature
Processed: Re: Bug#1040774: msolve FTBFS on 32bit: test failure and hang
Processing control commands: > severity -1 important Bug #1040774 [src:msolve] msolve FTBFS on 32bit: test failure and hang Severity set to 'important' from 'serious' -- 1040774: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1040774 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: Re: Bug#1040774: msolve FTBFS on 32bit: test failure and hang
Processing control commands: > forwarded -1 https://github.com/algebraic-solving/msolve/issues/66 Bug #1040774 [src:msolve] msolve FTBFS on 32bit: test failure and hang Set Bug forwarded-to-address to 'https://github.com/algebraic-solving/msolve/issues/66'. -- 1040774: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1040774 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1040774: msolve FTBFS on 32bit: test failure and hang
Control: forwarded -1 https://github.com/algebraic-solving/msolve/issues/66 On Mon 10 Jul 2023 03:33:43 PM +03, Adrian Bunk wrote: Source: msolve Version: 0.5.0-1 Severity: serious Tags: ftbfs https://buildd.debian.org/status/logs.php?pkg=msolve=0.5.0-1 ... make check-TESTS make[3]: Entering directory '/<>' make[4]: Entering directory '/<>' PASS: fglm_build_matrixn_radical_shape-31 PASS: neogb_io PASS: fglm_build_matrixn_nonradical_shape-31 PASS: fglm_build_matrixn_nonradical_radicalshape-31 FAIL: test/diff/diff_elim-qq.sh PASS: test/diff/diff_elim-31.sh PASS: test/diff/diff_F4SAT-31.sh FAIL: test/diff/diff_kat6-31.sh FAIL: test/diff/diff_eco11-31.sh E: Build killed with signal TERM after 150 minutes of inactivity signature.asc Description: PGP signature
Bug#1030955: golang-github-hhatto-gorst: autopkgtest failure
Control: tags -1 patch On Thu, Jul 13, 2023 at 03:10:40PM +0530, Pirate Praveen wrote: > On Fri, 10 Feb 2023 00:07:51 +0200 Adrian Bunk wrote: > > The Ubuntu diff contains a patch that looks like a workaround (untested). > > This patch says data directory is reserved for golang autopkgtest in Ubuntu. > Is this the same on debian too? If yes, that looks like a bad idea to me. AFAIK, it uses the standard AUTOPKGTEST_TMP directory which is the standard across debian. I got the same impression on skimming through dh-golang code. As far as fix for your package is concerned, it is as simple as avoiding to remove entire data directory (which is just 28K in size). I'm able to get autopkgtests passing locally. Patch pasted inline. From 7aa6fc7ccf9bb7b938d290bc1e2eab2b324fb7ff Mon Sep 17 00:00:00 2001 From: Nilesh Patra Date: Thu, 13 Jul 2023 21:22:59 +0530 Subject: [PATCH] Avoid removing entire data dir during dh_install step --- debian/rules | 1 - 1 file changed, 1 deletion(-) diff --git a/debian/rules b/debian/rules index c858f56..28c01cd 100755 --- a/debian/rules +++ b/debian/rules @@ -7,5 +7,4 @@ export DH_GOLANG_INSTALL_EXTRA := data override_dh_install: dh_install -O--builddirectory=_build -O--buildsystem=golang -O--with=golang - rm -rf debian/golang-github-hhatto-gorst-dev/usr/share/gocode/src/github.com/hhatto/gorst/data rm -rf debian/golang-github-hhatto-gorst-dev/usr/share/gocode/src/github.com/hhatto/gorst/*.html -- 2.39.2 signature.asc Description: PGP signature
Processed: Re: golang-github-hhatto-gorst: autopkgtest failure
Processing control commands: > tags -1 patch Bug #1030955 [src:golang-github-hhatto-gorst] golang-github-hhatto-gorst: autopkgtest failure Added tag(s) patch. -- 1030955: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1030955 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1040976: marked as done (crowdsec: only looks at traditional log files)
Your message dated Thu, 13 Jul 2023 15:49:07 + with message-id and subject line Bug#1040976: fixed in crowdsec 1.4.6-5 has caused the Debian Bug report #1040976, regarding crowdsec: only looks at traditional log files to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 1040976: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1040976 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: crowdsec Version: 1.4.6-4 Severity: serious Justification: maintainer/upstream's judgement Hi, One critical thing that was missed during the bookworm release cycle is that crowdsec's default configuration only checks traditional log files. In particular: /var/log/auth.log to detect failed SSH logins. That was fine in Debian 11, but with rsyslog's Priority being lowered from important to optional in Debian 12, the traditional log files are no longer produced and we're lacking detection. :/ There are two things to consider here to provide a fix: - We could try and enable the journalctl datasource selectively, but since we're shipping the default config file marked conffiles, that is likely to trigger prompting users during upgrades, so that doesn't look too appealing. If we *don't* do that though, crowdsec's current version would fail to initialize the journalctl datasource if journald isn't available, and would error out. - So the current plan is to apply two changes: one updating the default config file, and one adjusting crowdsec's behaviour when it comes to unavailable datasources: logging and continuing instead of failing. Upstream has: - https://github.com/crowdsecurity/crowdsec/pull/2316 to update the config file. - https://github.com/crowdsecurity/crowdsec/commit/a910b7becad1e06cb460949ab448d3172eb5679f to make sure the engine doesn't fail with an unavailable datasource. The second one comes with a slight behavorial change: crowdsec now errors out if there's no valid datasources. That seems way better than running with a broken config though. Cheers, -- Cyril Brulebois -- Debian Consultant @ DEBAMAX -- https://debamax.com/ --- End Message --- --- Begin Message --- Source: crowdsec Source-Version: 1.4.6-5 Done: Cyril Brulebois We believe that the bug you reported is fixed in the latest version of crowdsec, 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 1040...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Cyril Brulebois (supplier of updated crowdsec 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: Thu, 13 Jul 2023 17:23:01 +0200 Source: crowdsec Architecture: source Version: 1.4.6-5 Distribution: unstable Urgency: medium Maintainer: Cyril Brulebois Changed-By: Cyril Brulebois Closes: 1040976 Changes: crowdsec (1.4.6-5) unstable; urgency=medium . * Fix default acquis.yaml to also include the journalctl datasource, limited to the ssh.service unit, making sure acquisition works even without the traditional auth.log file (Closes: #1040976): - 0017-fix-default-acquisition.patch * Make sure an invalid datasource doesn't make the engine error out, making it possible to include the journalctl datasource in the default config file unconditionally, without having to worry whether journalctl is actually deployed and usable: - 0018-non-fatal-errors-for-invalid-datasources.patch Checksums-Sha1: ce015bda4138b517bf215d32673841eb4a93116f 4936 crowdsec_1.4.6-5.dsc b0d03c57e0e9e3bba4d6c9e315a9bbb33b47c712 30716 crowdsec_1.4.6-5.debian.tar.xz 67ef1e29e21f50fcc5bcefb140dc57160250f401 7645 crowdsec_1.4.6-5_source.buildinfo Checksums-Sha256: a98f878a00a902fd652ca936ce9f600fe0abf4198351fd3e106e10854e7c9050 4936 crowdsec_1.4.6-5.dsc c167f5659622628a97a16f7295da7a73e53419cac54762eeda83e147494a91dc 30716 crowdsec_1.4.6-5.debian.tar.xz 0692a3eed9a1088ce3c052151afa134e82dd12b196e4f838fa645de39f5b8a42 7645 crowdsec_1.4.6-5_source.buildinfo Files: 5766856a93abd3617a2c2678ad78b114 4936 golang optional crowdsec_1.4.6-5.dsc e89b185c383a3769ff8044338a76ece6 30716 golang optional crowdsec_1.4.6-5.debian.tar.xz
Processed: Re: Bug#1030932: golang-github-go-enry-go-license-detector: FTBFS on mipsel: test failures
Processing control commands:
> reopen -1
Bug #1030932 {Done: Pirate Praveen }
[src:golang-github-go-enry-go-license-detector]
golang-github-go-enry-go-license-detector: FTBFS on mipsel: test failures
Bug reopened
Ignoring request to alter fixed versions of bug #1030932 to the same values
previously set
--
1030932: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1030932
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Bug#1030932: golang-github-go-enry-go-license-detector: FTBFS on mipsel: test failures
Control: reopen -1 Hi, On Thu, Jul 13, 2023 at 6:09 PM Pirate Praveen wrote: > > On Thu, 9 Feb 2023 14:40:48 +0100 Sebastian Ramacher > wrote: > > Source: golang-github-go-enry-go-license-detector > > Version: 4.3.0+git20221007.a3a1cc6-1 > > Severity: serious > > Tags: ftbfs > > Justification: fails to build from source (but built successfully in > the past) > > > > > https://buildd.debian.org/status/fetch.php?pkg=golang-github-go-enry-go-license-detector=mipsel=4.3.0%2Bgit20221007.a3a1cc6-1%2Bb2=1675941345=0 > > > > This looks like a temporary error, last build was passing > > https://buildd.debian.org/status/fetch.php?pkg=golang-github-hhatto-gorst=mipsel=0.0%7Egit20181029.ca9f730-2%2Bb6=1681037294=0 You look at the wrong log, it's golang-github-hhatto-gorst, not golang-github-go-enry-go-license-detector. It FTBFS on buildd currently. -- Shengjing Zhu
Bug#1040976: crowdsec: only looks at traditional log files
Package: crowdsec Version: 1.4.6-4 Severity: serious Justification: maintainer/upstream's judgement Hi, One critical thing that was missed during the bookworm release cycle is that crowdsec's default configuration only checks traditional log files. In particular: /var/log/auth.log to detect failed SSH logins. That was fine in Debian 11, but with rsyslog's Priority being lowered from important to optional in Debian 12, the traditional log files are no longer produced and we're lacking detection. :/ There are two things to consider here to provide a fix: - We could try and enable the journalctl datasource selectively, but since we're shipping the default config file marked conffiles, that is likely to trigger prompting users during upgrades, so that doesn't look too appealing. If we *don't* do that though, crowdsec's current version would fail to initialize the journalctl datasource if journald isn't available, and would error out. - So the current plan is to apply two changes: one updating the default config file, and one adjusting crowdsec's behaviour when it comes to unavailable datasources: logging and continuing instead of failing. Upstream has: - https://github.com/crowdsecurity/crowdsec/pull/2316 to update the config file. - https://github.com/crowdsecurity/crowdsec/commit/a910b7becad1e06cb460949ab448d3172eb5679f to make sure the engine doesn't fail with an unavailable datasource. The second one comes with a slight behavorial change: crowdsec now errors out if there's no valid datasources. That seems way better than running with a broken config though. Cheers, -- Cyril Brulebois -- Debian Consultant @ DEBAMAX -- https://debamax.com/
Bug#1040199: marked as done (linux-image-6.3.0-1-amd64: kernel panic during boot)
Your message dated Thu, 13 Jul 2023 12:50:50 + with message-id and subject line Bug#1038003: fixed in xtrx-dkms 0.0.1+git20190320.5ae3a3e-3.3 has caused the Debian Bug report #1038003, regarding linux-image-6.3.0-1-amd64: kernel panic during boot 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.) -- 1038003: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1038003 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: src:linux Version: 6.3.7-1 Severity: grave Justification: renders package unusable Dear Maintainer, Tracking sid, after upgrading from 6.1.0-9-amd64 to 6.3.0-1-amd64 (6.3.7-1), I experienced a kernel panic during boot. Here is its trace: ``` [2.961158] Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(0,0) [2.961243] CPU: 14 PID: 1 Comm: swapper/0 Not tainted 6.3.0-1-amd64 #1 Debian 6.3.7-1 [2.961323] Hardware name: Gigabyte Technology Co., Ltd. X570 I AORUS PRO WIFI/X570 I AORUS PRO WIFI, BIOS F37a 02/08/2023 [2.961412] Call Trace: [2.961473] [2.961532] dump_stack_lvl+0x47/0x60 [2.961600] panic+0x358/0x360 [2.961666] mount_block_root+0x23f/0x2d0 [2.961735] prepare_namespace+0xf0/0x170 [2.961800] kernel_init_freeable+0x42e/0x480 [2.961868] ? __pfx_kernel_init+0x10/0x10 [2.961936] kernel_init+0x1a/0x1c0 [2.962000] ret_from_fork+0x2c/0x50 [2.962067] [2.962202] Kernel Offset: 0x22e0 from 0x8100 (relocation range: 0x8000-0xbfff) [2.962294] ---[ end Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(0,0) ]--- ``` AFAIK, there is not other reports of this, and I was wondering if it could be due to the fact that this is an "old" installation. FWIW, since this is something that I saw when people were trying/using UEFI, I thought I should mention that my drives are still using MBR partitions, and so, boot in BIOS is configured as CSM. Hope that helps, JB -- Package-specific info: ** Kernel log: boot messages should be attached ** Model information sys_vendor: Gigabyte Technology Co., Ltd. product_name: X570 I AORUS PRO WIFI product_version: -CF chassis_vendor: Default string chassis_version: Default string bios_vendor: American Megatrends International, LLC. bios_version: F37a board_vendor: Gigabyte Technology Co., Ltd. board_name: X570 I AORUS PRO WIFI board_version: Default string ** PCI devices: 00:00.0 Host bridge [0600]: Advanced Micro Devices, Inc. [AMD] Starship/Matisse Root Complex [1022:1480] Subsystem: Advanced Micro Devices, Inc. [AMD] Starship/Matisse Root Complex [1022:1480] Control: I/O- Mem- BusMaster- SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx- Status: Cap- 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- TAbort- SERR- 00:01.0 Host bridge [0600]: Advanced Micro Devices, Inc. [AMD] Starship/Matisse PCIe Dummy Host Bridge [1022:1482] Control: I/O- Mem- BusMaster- SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx- Status: Cap- 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- TAbort- SERR- TAbort- Reset- FastB2B- PriDiscTmr- SecDiscTmr- DiscTmrStat- DiscTmrSERREn- Capabilities: Kernel driver in use: pcieport 00:02.0 Host bridge [0600]: Advanced Micro Devices, Inc. [AMD] Starship/Matisse PCIe Dummy Host Bridge [1022:1482] Control: I/O- Mem- BusMaster- SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx- Status: Cap- 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- TAbort- SERR- TAbort- SERR- TAbort- Reset- FastB2B- PriDiscTmr- SecDiscTmr- DiscTmrStat- DiscTmrSERREn- Capabilities: Kernel driver in use: pcieport 00:04.0 Host bridge [0600]: Advanced Micro Devices, Inc. [AMD] Starship/Matisse PCIe Dummy Host Bridge [1022:1482] Control: I/O- Mem- BusMaster- SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx- Status: Cap- 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- TAbort- SERR- TAbort- SERR- TAbort- SERR- TAbort- Reset- FastB2B- PriDiscTmr- SecDiscTmr- DiscTmrStat- DiscTmrSERREn- Capabilities: Kernel driver in use: pcieport 00:08.0 Host bridge [0600]: Advanced Micro Devices, Inc. [AMD] Starship/Matisse PCIe Dummy Host Bridge [1022:1482] Control: I/O- Mem- BusMaster- SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx- Status: Cap- 66MHz- UDF- FastB2B- ParErr-
Bug#1038003: marked as done (xtrx-dkms: module fails to build for Linux 6.3: error: assignment of read-only member 'vm_flags')
Your message dated Thu, 13 Jul 2023 12:50:50 +
with message-id
and subject line Bug#1038003: fixed in xtrx-dkms 0.0.1+git20190320.5ae3a3e-3.3
has caused the Debian Bug report #1038003,
regarding xtrx-dkms: module fails to build for Linux 6.3: error: assignment of
read-only member 'vm_flags'
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.)
--
1038003: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1038003
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: xtrx-dkms
Version: 0.0.1+git20190320.5ae3a3e-3.2
Severity: serious
Tags: sid trixie
User: debian...@lists.debian.org
Usertags: piuparts
related to this kernel change: bc292ab00f6c ("mm: introduce vma->vm_flags
wrapper functions")
DKMS make.log for xtrx-0.0.1+git20190320.5ae3a3e-3.2 for kernel 6.3.0-1-amd64
(x86_64)
Thu Jun 15 10:23:22 UTC 2023
make: Entering directory '/usr/src/linux-headers-6.3.0-1-amd64'
CC [M] /var/lib/dkms/xtrx/0.0.1+git20190320.5ae3a3e-3.2/build/xtrx.o
/var/lib/dkms/xtrx/0.0.1+git20190320.5ae3a3e-3.2/build/xtrx.c: In function
'xtrxfd_mmap':
/var/lib/dkms/xtrx/0.0.1+git20190320.5ae3a3e-3.2/build/xtrx.c:1075:31: error:
assignment of read-only member 'vm_flags'
1075 | vma->vm_flags |= VM_LOCKED;
| ^~
/var/lib/dkms/xtrx/0.0.1+git20190320.5ae3a3e-3.2/build/xtrx.c:1090:31: error:
assignment of read-only member 'vm_flags'
1090 | vma->vm_flags |= VM_IO;
| ^~
/var/lib/dkms/xtrx/0.0.1+git20190320.5ae3a3e-3.2/build/xtrx.c:1115:31: error:
assignment of read-only member 'vm_flags'
1115 | vma->vm_flags |= VM_LOCKED;
| ^~
make[1]: *** [/usr/src/linux-headers-6.3.0-1-common/scripts/Makefile.build:257:
/var/lib/dkms/xtrx/0.0.1+git20190320.5ae3a3e-3.2/build/xtrx.o] Error 1
make: *** [/usr/src/linux-headers-6.3.0-1-common/Makefile:2050:
/var/lib/dkms/xtrx/0.0.1+git20190320.5ae3a3e-3.2/build] Error 2
make: Leaving directory '/usr/src/linux-headers-6.3.0-1-amd64'
Andreas
--- End Message ---
--- Begin Message ---
Source: xtrx-dkms
Source-Version: 0.0.1+git20190320.5ae3a3e-3.3
Done: Ying-Chun Liu (PaulLiu)
We believe that the bug you reported is fixed in the latest version of
xtrx-dkms, 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 1038...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Ying-Chun Liu (PaulLiu) (supplier of updated xtrx-dkms
package)
(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Format: 1.8
Date: Sat, 24 Jun 2023 04:22:04 +0800
Source: xtrx-dkms
Architecture: source
Version: 0.0.1+git20190320.5ae3a3e-3.3
Distribution: unstable
Urgency: low
Maintainer: Sepi Gair
Changed-By: Ying-Chun Liu (PaulLiu)
Closes: 1038003
Changes:
xtrx-dkms (0.0.1+git20190320.5ae3a3e-3.3) unstable; urgency=low
.
* Non-maintainer upload.
* Fix dkms build failure with kernel 6.3 (Closes: #1038003)
- add debian/patches/0003-xtrx.c-fix-build-error-with-kernel-6.3.patch
Checksums-Sha1:
a591958ea97783563e111310ad5955f41cb71ba3 2095
xtrx-dkms_0.0.1+git20190320.5ae3a3e-3.3.dsc
a433176062cf335b7b9faf1e5c3eb294354234aa 4476
xtrx-dkms_0.0.1+git20190320.5ae3a3e-3.3.debian.tar.xz
adb52f1cdea04503bf6834464beca258b26d8248 6949
xtrx-dkms_0.0.1+git20190320.5ae3a3e-3.3_source.buildinfo
Checksums-Sha256:
b0b995b5ff1ecab43ba86fe6975f2abd9d3089eb893d69c9986ce83dff5586d8 2095
xtrx-dkms_0.0.1+git20190320.5ae3a3e-3.3.dsc
56da21e2dc22cd689fd8b632867ffc96c82bf432b867f95ad8da35e1322b53bc 4476
xtrx-dkms_0.0.1+git20190320.5ae3a3e-3.3.debian.tar.xz
e496eb9a759c642787260f24851bd603c356031671e8f388d403f9308cdfe292 6949
xtrx-dkms_0.0.1+git20190320.5ae3a3e-3.3_source.buildinfo
Files:
b0fe3e63c68f9358a4bbbe121bcda712 2095 kernel optional
xtrx-dkms_0.0.1+git20190320.5ae3a3e-3.3.dsc
ead2a8a638047345d958c9a7097f70ed 4476 kernel optional
xtrx-dkms_0.0.1+git20190320.5ae3a3e-3.3.debian.tar.xz
b880581163b0bfacb2e01981ca73a561 6949 kernel optional
xtrx-dkms_0.0.1+git20190320.5ae3a3e-3.3_source.buildinfo
-BEGIN PGP SIGNATURE-
iQJHBAEBCgAxFiEEo2h49GQQhoFgDLZIRBc/oT0FiIgFAmSitdgTHHBhdWxsaXVA
Processed: closing 1040967
Processing commands for cont...@bugs.debian.org: > close 1040967 0.11.4+ds-3 Bug #1040967 [src:cpp-httplib] cpp-httplib FTBFS with googletest 1.13.0 The source 'cpp-httplib' and version '0.11.4+ds-3' do not appear to match any binary packages Marked as fixed in versions cpp-httplib/0.11.4+ds-3. Bug #1040967 [src:cpp-httplib] cpp-httplib FTBFS with googletest 1.13.0 Marked Bug as done > thanks Stopping processing here. Please contact me if you need assistance. -- 1040967: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1040967 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1040967: cpp-httplib FTBFS with googletest 1.13.0
Source: cpp-httplib Version: 0.11.4+ds-1 Severity: serious Tags: ftbfs trixie sid https://buildd.debian.org/status/fetch.php?pkg=cpp-httplib=amd64=0.11.4%2Bds-2=1689245748=0 ... In file included from /usr/include/gtest/gtest-message.h:57, from /usr/include/gtest/gtest-assertion-result.h:46, from /usr/include/gtest/gtest.h:64, from ../test/test.cc:4: /usr/include/gtest/internal/gtest-port.h:270:2: error: #error C++ versions less than C++14 are not supported. 270 | #error C++ versions less than C++14 are not supported. | ^ ... Removing the line 'cpp_std=c++11', from meson.build fixes the FTBFS.
Processed: Re: refpolicy: more rigorous validation
Processing control commands: > severity -1 serious Bug #1030804 [refpolicy] refpolicy: more rigorous validation Severity set to 'serious' from 'normal' > affects -1 src:libsepol Bug #1030804 [refpolicy] refpolicy: more rigorous validation Added indication that 1030804 affects src:libsepol -- 1030804: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1030804 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1040966: linux-image-6.1.0-9-amd64: Thinkpad T470 fails to wake from suspend after bookworm upgrade
Package: src:linux
Version: 6.1.27-1
Severity: serious
Justification: 0 (Preface)
X-Debbugs-Cc: senc...@riseup.net
Dear Maintainer,
after a running the bookworm update I have frequent and recurring problems
waking the machine from sleep.
I have seen two possible states after waking up:
1. Completely unresponsive with dark screen: Power LED is lit. FnLock LED
doesn't respond. MagicSysrq doesn't work.
2. Completely unresponsive with lock screen: Screen wakes up and show the gnome
screen. FnLock can be toggled. Otherwise no interaction possible. MagicSysrq
doesn't do anything.
Before the upgrade Suspend to RAM worked completely fine. For some time I
suspected tl-smapi-dkms to be the cause, but this was ruled out now (it just
happened again after removing the package).
The only other kernel module I am aware of is the broadcom-sta-dkms. I tried to
unload it before sleep, but the issue happened again.
journalctl revealed no interesting messages before sleep, and nothing after a
failed wake up.
-- Package-specific info:
** Version:
Linux version 6.1.0-9-amd64 (debian-ker...@lists.debian.org) (gcc-12 (Debian
12.2.0-14) 12.2.0, GNU ld (GNU Binutils for Debian) 2.40) #1 SMP
PREEMPT_DYNAMIC Debian 6.1.27-1 (2023-05-08)
** Command line:
BOOT_IMAGE=/vmlinuz-6.1.0-9-amd64
root=UUID=2258140b-a9a9-46ab-94ae-4c5e09a007d6 ro
** Tainted: POE (12289)
* proprietary module was loaded
* externally-built ("out-of-tree") module was loaded
* unsigned module was loaded
** Kernel log:
[ 19.930813] intel_rapl_common: Found RAPL domain uncore
[ 19.930815] intel_rapl_common: Found RAPL domain dram
[ 19.930817] intel_rapl_common: Found RAPL domain psys
[ 19.943525] audit: type=1400 audit(1689240616.727:5): apparmor="STATUS"
operation="profile_load" profile="unconfined" name="lsb_release" pid=854
comm="apparmor_parser"
[ 19.947026] audit: type=1400 audit(1689240616.731:6): apparmor="STATUS"
operation="profile_load" profile="unconfined" name="firejail-default" pid=853
comm="apparmor_parser"
[ 19.951740] audit: type=1400 audit(1689240616.735:7): apparmor="STATUS"
operation="profile_load" profile="unconfined" name="ping" pid=847
comm="apparmor_parser"
[ 19.957230] audit: type=1400 audit(1689240616.739:8): apparmor="STATUS"
operation="profile_load" profile="unconfined" name="lxc-container-default"
pid=855 comm="apparmor_parser"
[ 19.958443] audit: type=1400 audit(1689240616.739:9): apparmor="STATUS"
operation="profile_load" profile="unconfined" name="lxc-container-default-cgns"
pid=855 comm="apparmor_parser"
[ 19.959416] audit: type=1400 audit(1689240616.739:10): apparmor="STATUS"
operation="profile_load" profile="unconfined"
name="lxc-container-default-with-mounting" pid=855 comm="apparmor_parser"
[ 19.960453] audit: type=1400 audit(1689240616.739:11): apparmor="STATUS"
operation="profile_load" profile="unconfined"
name="lxc-container-default-with-nesting" pid=855 comm="apparmor_parser"
[ 20.358776] Adding 12597056k swap on /dev/mapper/swap. Priority:-2
extents:1 across:12597056k SSFS
[ 20.403115] mc: Linux media interface: v0.10
[ 20.431583] videodev: Linux video capture interface: v2.00
[ 20.551062] input: keyd virtual keyboard as /devices/virtual/input/input23
[ 20.551189] input: keyd virtual pointer as /devices/virtual/input/input24
[ 20.593068] usb 1-8: Found UVC 1.00 device Integrated Camera (5986:111c)
[ 20.622551] input: Integrated Camera: Integrated C as
/devices/pci:00/:00:14.0/usb1/1-8/1-8:1.0/input/input25
[ 20.623878] usbcore: registered new interface driver uvcvideo
[ 20.674648] Process accounting resumed
[ 20.943691] IPv6: ADDRCONF(NETDEV_CHANGE): v-peer1: link becomes ready
[ 20.944744] IPv6: ADDRCONF(NETDEV_CHANGE): v-eth1: link becomes ready
[ 20.968704] usbcore: registered new device driver apple-mfi-fastcharge
[ 21.009079] systemd-journald[469]: File
/var/log/journal/2452626f3a7f4738ab5cba389727f188/user-1000.journal corrupted
or uncleanly shut down, renaming and replacing.
[ 21.304365] alg: No test for fips(ansi_cprng) (fips_ansi_cprng)
[ 21.615076] Bluetooth: Core ver 2.22
[ 21.616164] NET: Registered PF_BLUETOOTH protocol family
[ 21.617211] Bluetooth: HCI device and connection manager initialized
[ 21.619479] Bluetooth: HCI socket layer initialized
[ 21.620499] Bluetooth: L2CAP socket layer initialized
[ 21.621504] Bluetooth: SCO socket layer initialized
[ 21.689563] usbcore: registered new interface driver btusb
[ 21.715416] usb 1-7.1: USB disconnect, device number 4
[ 21.811326] Bluetooth: hci0: BCM: chip id 73 build 1125
[ 21.813302] Bluetooth: hci0: BCM: product 05ac:828d
[ 21.815314] Bluetooth: hci0: BCM: features 0x07
[ 21.832308] Bluetooth: hci0: BCM20702B0 Generic USB Class 1 @ 20 MHz
[ 21.888108] Bluetooth: BNEP (Ethernet Emulation) ver 1.3
[ 21.889080] Bluetooth: BNEP filters: protocol multicast
[ 21.894728] Bluetooth: BNEP socket layer initialized
[ 21.899522] Bluetooth: MGMT
Bug#1030955: golang-github-hhatto-gorst: autopkgtest failure
On Fri, 10 Feb 2023 00:07:51 +0200 Adrian Bunk wrote: > The Ubuntu diff contains a patch that looks like a workaround (untested). This patch says data directory is reserved for golang autopkgtest in Ubuntu. Is this the same on debian too? If yes, that looks like a bad idea to me.
Processed: src:slixmpp: fails to migrate to testing for too long: autopkgtest regression
Processing control commands:
> close -1 1.8.4-2
Bug #1040964 [src:slixmpp] src:slixmpp: fails to migrate to testing for too
long: autopkgtest regression
Marked as fixed in versions slixmpp/1.8.4-2.
Bug #1040964 [src:slixmpp] src:slixmpp: fails to migrate to testing for too
long: autopkgtest regression
Marked Bug as done
> block -1 by 1040057
Bug #1040964 {Done: Paul Gevers } [src:slixmpp] src:slixmpp:
fails to migrate to testing for too long: autopkgtest regression
1040964 was not blocked by any bugs.
1040964 was not blocking any bugs.
Added blocking bug(s) of 1040964: 1040057
--
1040964: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1040964
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Bug#1040964: src:slixmpp: fails to migrate to testing for too long: autopkgtest regression
Source: slixmpp Version: 1.8.3-1 Severity: serious Control: close -1 1.8.4-2 Tags: sid trixie User: release.debian@packages.debian.org Usertags: out-of-sync Control: block -1 by 1040057 Dear maintainer(s), The Release Team considers packages that are out-of-sync between testing and unstable for more than 30 days as having a Release Critical bug in testing [1]. Your package src:slixmpp has been trying to migrate for 32 days [2]. Hence, I am filing this bug. There was bug 1040057 filed about the version in unstable failing it's autopkgtest on arm64. If a package is out of sync between unstable and testing for a longer period, this usually means that bugs in the package in testing cannot be fixed via unstable. Additionally, blocked packages can have impact on other packages, which makes preparing for the release more difficult. Finally, it often exposes issues with the package and/or its (reverse-)dependencies. We expect maintainers to fix issues that hamper the migration of their package in a timely manner. This bug will trigger auto-removal when appropriate. As with all new bugs, there will be at least 30 days before the package is auto-removed. I have immediately closed this bug with the version in unstable, so if that version or a later version migrates, this bug will no longer affect testing. I have also tagged this bug to only affect sid and trixie, so it doesn't affect (old-)stable. If you believe your package is unable to migrate to testing due to issues beyond your control, don't hesitate to contact the Release Team. Paul [1] https://lists.debian.org/debian-devel-announce/2023/06/msg1.html [2] https://qa.debian.org/excuses.php?package=slixmpp OpenPGP_signature Description: OpenPGP digital signature
Processed: src:starpu: fails to migrate to testing for too long: unsatisfiable dependency on armel, mipsel and s390x + segfault
Processing control commands: > close -1 1.4.1+dfsg-2 Bug #1040963 [src:starpu] src:starpu: fails to migrate to testing for too long: unsatisfiable dependency on armel, mipsel and s390x + segfault Marked as fixed in versions starpu/1.4.1+dfsg-2. Bug #1040963 [src:starpu] src:starpu: fails to migrate to testing for too long: unsatisfiable dependency on armel, mipsel and s390x + segfault Marked Bug as done -- 1040963: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1040963 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1040963: src:starpu: fails to migrate to testing for too long: unsatisfiable dependency on armel, mipsel and s390x + segfault
Source: starpu Version: 1.3.10+dfsg-2 Severity: serious Control: close -1 1.4.1+dfsg-2 Tags: sid trixie User: release.debian@packages.debian.org Usertags: out-of-sync Dear maintainer(s), The Release Team considers packages that are out-of-sync between testing and unstable for more than 30 days as having a Release Critical bug in testing [1]. Your package src:starpu has been trying to migrate for 32 days [2]. Hence, I am filing this bug. According to the migration software, the new version of libstarpu-dev can't be installed on armel, mipsel and s390x. Additionally the autopkgtest segfaults on armhf. If a package is out of sync between unstable and testing for a longer period, this usually means that bugs in the package in testing cannot be fixed via unstable. Additionally, blocked packages can have impact on other packages, which makes preparing for the release more difficult. Finally, it often exposes issues with the package and/or its (reverse-)dependencies. We expect maintainers to fix issues that hamper the migration of their package in a timely manner. This bug will trigger auto-removal when appropriate. As with all new bugs, there will be at least 30 days before the package is auto-removed. I have immediately closed this bug with the version in unstable, so if that version or a later version migrates, this bug will no longer affect testing. I have also tagged this bug to only affect sid and trixie, so it doesn't affect (old-)stable. If you believe your package is unable to migrate to testing due to issues beyond your control, don't hesitate to contact the Release Team. Paul [1] https://lists.debian.org/debian-devel-announce/2023/06/msg1.html [2] https://qa.debian.org/excuses.php?package=starpu OpenPGP_signature Description: OpenPGP digital signature
Bug#1040962: src:sympy: fails to migrate to testing for too long: autopkgtest regression
Source: sympy Version: 1.11.1-1 Severity: serious Control: close -1 1.12-2 Tags: sid trixie User: release.debian@packages.debian.org Usertags: out-of-sync Control: block -1 by 1040058 Dear maintainer(s), The Release Team considers packages that are out-of-sync between testing and unstable for more than 30 days as having a Release Critical bug in testing [1]. Your package src:sympy has been trying to migrate for 32 days [2]. Hence, I am filing this bug. The package in unstable causes an autopkgtest regression is sagemath as reported in bug 1040058. If a package is out of sync between unstable and testing for a longer period, this usually means that bugs in the package in testing cannot be fixed via unstable. Additionally, blocked packages can have impact on other packages, which makes preparing for the release more difficult. Finally, it often exposes issues with the package and/or its (reverse-)dependencies. We expect maintainers to fix issues that hamper the migration of their package in a timely manner. This bug will trigger auto-removal when appropriate. As with all new bugs, there will be at least 30 days before the package is auto-removed. I have immediately closed this bug with the version in unstable, so if that version or a later version migrates, this bug will no longer affect testing. I have also tagged this bug to only affect sid and trixie, so it doesn't affect (old-)stable. If you believe your package is unable to migrate to testing due to issues beyond your control, don't hesitate to contact the Release Team. Paul [1] https://lists.debian.org/debian-devel-announce/2023/06/msg1.html [2] https://qa.debian.org/excuses.php?package=sympy OpenPGP_signature Description: OpenPGP digital signature
Processed: src:sympy: fails to migrate to testing for too long: autopkgtest regression
Processing control commands:
> close -1 1.12-2
Bug #1040962 [src:sympy] src:sympy: fails to migrate to testing for too long:
autopkgtest regression
Marked as fixed in versions sympy/1.12-2.
Bug #1040962 [src:sympy] src:sympy: fails to migrate to testing for too long:
autopkgtest regression
Marked Bug as done
> block -1 by 1040058
Bug #1040962 {Done: Paul Gevers } [src:sympy] src:sympy:
fails to migrate to testing for too long: autopkgtest regression
1040962 was not blocked by any bugs.
1040962 was not blocking any bugs.
Added blocking bug(s) of 1040962: 1040058
--
1040962: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1040962
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Bug#1040961: src:wike: fails to migrate to testing for too long: build depends on version in experimental
Source: wike Version: 1.8.2-1 Severity: serious Control: close -1 2.0.1-3 Tags: sid trixie User: release.debian@packages.debian.org Usertags: out-of-sync Dear maintainer(s), The Release Team considers packages that are out-of-sync between testing and unstable for more than 30 days as having a Release Critical bug in testing [1]. Your package src:wike has been trying to migrate for 32 days [2]. Hence, I am filing this bug. It seems you're waiting for a build dependency that is only available in experimental. If a package is out of sync between unstable and testing for a longer period, this usually means that bugs in the package in testing cannot be fixed via unstable. Additionally, blocked packages can have impact on other packages, which makes preparing for the release more difficult. Finally, it often exposes issues with the package and/or its (reverse-)dependencies. We expect maintainers to fix issues that hamper the migration of their package in a timely manner. This bug will trigger auto-removal when appropriate. As with all new bugs, there will be at least 30 days before the package is auto-removed. I have immediately closed this bug with the version in unstable, so if that version or a later version migrates, this bug will no longer affect testing. I have also tagged this bug to only affect sid and trixie, so it doesn't affect (old-)stable. If you believe your package is unable to migrate to testing due to issues beyond your control, don't hesitate to contact the Release Team. Paul [1] https://lists.debian.org/debian-devel-announce/2023/06/msg1.html [2] https://qa.debian.org/excuses.php?package=wike OpenPGP_signature Description: OpenPGP digital signature
Processed: src:wike: fails to migrate to testing for too long: build depends on version in experimental
Processing control commands: > close -1 2.0.1-3 Bug #1040961 [src:wike] src:wike: fails to migrate to testing for too long: build depends on version in experimental The source 'wike' and version '2.0.1-3' do not appear to match any binary packages Marked as fixed in versions wike/2.0.1-3. Bug #1040961 [src:wike] src:wike: fails to migrate to testing for too long: build depends on version in experimental Marked Bug as done -- 1040961: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1040961 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1040960: gcc-sh-elf binary-all build rejected
Source: gcc-sh-elf Version: 7 Severity: serious Tags: ftbfs bunk@coccia:~$ cat /srv/ftp-master.debian.org/queue/reject/gcc-sh-elf_7_all-buildd.changes.reason Version check failed: Your upload included the binary package libnewlib-sh-elf-dev, version 3.3.0-1.3+7, for all, however testing already has version 3.3.0+6. Uploads to unstable must have a higher version than present in testing. bunk@coccia:~$ Fixing #996432 including the upgrade would be one way to fix this problem.
Bug#1040584: marked as done (seek-bzip: broken symlinks: /usr/bin/seek-bunzip, /usr/bin/seek-table)
Your message dated Thu, 13 Jul 2023 07:47:08 + with message-id and subject line Bug#1040584: fixed in node-openpgp-seek-bzip 1.0.5-2+deb12u1 has caused the Debian Bug report #1040584, regarding seek-bzip: broken symlinks: /usr/bin/seek-bunzip, /usr/bin/seek-table 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.) -- 1040584: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1040584 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: seek-bzip Version: 1.0.5-2 Severity: serious User: debian...@lists.debian.org Usertags: piuparts Hi, during a test with piuparts I noticed your package ships (or creates) broken symlinks: 0m22.5s ERROR: FAIL: Broken symlinks: /usr/bin/seek-bunzip -> ../share/nodejs/@openpgp/seek-bzip/bin/seek-bunzip (seek-bzip) /usr/bin/seek-table -> ../share/nodejs/@openpgp/seek-bzip/bin/seek-bzip-table (seek-bzip) cheers, Andreas --- End Message --- --- Begin Message --- Source: node-openpgp-seek-bzip Source-Version: 1.0.5-2+deb12u1 Done: Yadd We believe that the bug you reported is fixed in the latest version of node-openpgp-seek-bzip, 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 1040...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Yadd (supplier of updated node-openpgp-seek-bzip package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Sun, 09 Jul 2023 09:29:47 +0400 Source: node-openpgp-seek-bzip Architecture: source Version: 1.0.5-2+deb12u1 Distribution: bookworm Urgency: medium Maintainer: Debian Javascript Maintainers Changed-By: Yadd Closes: 1040584 Changes: node-openpgp-seek-bzip (1.0.5-2+deb12u1) bookworm; urgency=medium . * Team upload * Fix seek-bzip install (Closes: #1040584) Checksums-Sha1: 412e7abab60a2262c25c235b7c6f8e8c23134fc4 2242 node-openpgp-seek-bzip_1.0.5-2+deb12u1.dsc 09d564c2d9bc9a79a277dcb357b25477c49e5983 3540 node-openpgp-seek-bzip_1.0.5-2+deb12u1.debian.tar.xz Checksums-Sha256: e88ad0e8c44558d03bf1cbb4580528258278564d219f70cc222e8cd133380f76 2242 node-openpgp-seek-bzip_1.0.5-2+deb12u1.dsc deef083883c1c78fc0595f9dd654504980c74f1d90655daa49a9e2fb525d1176 3540 node-openpgp-seek-bzip_1.0.5-2+deb12u1.debian.tar.xz Files: f7695e512fddc7cf3cc49205b5b299e0 2242 javascript optional node-openpgp-seek-bzip_1.0.5-2+deb12u1.dsc ba356ff96bd9149f5aa4bc4c7f81e0a8 3540 javascript optional node-openpgp-seek-bzip_1.0.5-2+deb12u1.debian.tar.xz -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEEAN/li4tVV3nRAF7J9tdMp8mZ7ukFAmSuIeAACgkQ9tdMp8mZ 7um0ShAAg9Wta0jJ4cU5Lei16WDM4Pahs8OKIHJm/WXa+k9LDr/bSbDozVWZcbK2 UxbgxoJ4srL1AU87K2ltrbV+kLn0wgk+wg1GHtiM5nDyoSW/erasungfLPk6ClMD QRZJjIaJTluzXnTscAEnRp9sIlrjrs/0RBjKi45JMonK5/L7AJcSR7xD3giEnV4g GQfUpGzJKClFWMKORYxMjmkchNS5wwIe133mqtk3G9bS48bjDK7NqQCaGzdjpDuX u1bMApnjVae/9BqcD7vKts6cRNpaIKvPLYxZJxSKdYpRMlFYqjbsg2DzjyCCc3GI 525a3zGxWmkHxX8KBabQqac86PKE7yLdIu2OA91DBBorZnjB8bHzE6RjUyKr6DjD Sd1fUDtPgDa5G+yjvzOqi5oPKmXZkBWCVqLzzWRUdtdiQTpRjiNL54gThXZZDlIg mW9OunUf3+B5COC5CVlmzOnXUSadv+6TYr4Ia2p43yATt8Hl5ZkYpr5/ANVhlql8 AImEVDvJFfCxiZiivc8kKEzmqX0TW29Gt0qH2SCxuwZcoF+T/NPick7ozt4kwQBL nm4eD+sr23y/gKmZH8WRzWMV0K2TRX8Opu0L9DT9HSvqhMk3FcqrwQ1otAYLGwC6 kpOdV+cZHo/ZMGIYXufR+4K3Eq2HIp0HHM/FCqh2UIq2pREeqPY= =b6Q9 -END PGP SIGNATURE End Message ---
Bug#1040537: marked as done (frama-c FTBFS: Error: This expression has type ... but an expression was expected of type)
Your message dated Thu, 13 Jul 2023 07:49:32 + with message-id and subject line Bug#1040537: fixed in frama-c 20220511-manganese-4 has caused the Debian Bug report #1040537, regarding frama-c FTBFS: Error: This expression has type ... but an expression was expected of type to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 1040537: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1040537 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: frama-c Version: 20220511-manganese-3 Severity: serious Tags: ftbfs trixie sid https://buildd.debian.org/status/fetch.php?pkg=frama-c=amd64=20220511-manganese-3%2Bb6=1688693485=0 ... ocamlfind ocamlc -c -package findlib -package ocamlgraph -package unix -package str -package dynlink -package bytes -package zarith -package yojson -package bigarray -package ppx_import -package ppx_deriving.eq -w -a -bin-annot -strict-sequence -safe-string -g -I src/plugins/pdg_types -I src/plugins/value_types -I src/libraries/stdlib -I src/libraries/utils -I src/libraries/project -I src/libraries/datatype -I src/kernel_internals/parsing -I src/kernel_internals/typing -I src/kernel_internals/runtime -I src/kernel_services/parsetree -I src/kernel_services/ast_data -I src/kernel_services/ast_queries -I src/kernel_services/ast_printing -I src/kernel_services/ast_building -I src/kernel_services/cmdline_parameters -I src/kernel_services/plugin_entry_points -I src/kernel_services/abstract_interp -I src/kernel_services/visitors -I src/kernel_services/analysis -I src/kernel_services/ast_transformations -I src/plugins/gui -I /<>/lib/plugins src/kernel_services/ast_printing/logic_print.mli File "src/libraries/utils/json.mll", line 374, characters 8-16: Error: This expression has type (string list -> Yojson.Basic.t -> Yojson.Basic.t option, [> `Assoc of (String.t * Yojson.Basic.t) list | `List of Yojson.Basic.t list ] as 'a) Hashtbl.t = (string list -> Yojson.Basic.t -> Yojson.Basic.t option, 'a) Hashtbl.t but an expression was expected of type (Filepath.Normalized.t, Yojson.Basic.t) Hashtbl.t Type string list -> Yojson.Basic.t -> Yojson.Basic.t option is not compatible with type Filepath.Normalized.t make[1]: *** [share/Makefile.generic:88: src/libraries/utils/json.cmx] Error 2 make[1]: *** Waiting for unfinished jobs --- End Message --- --- Begin Message --- Source: frama-c Source-Version: 20220511-manganese-4 Done: Stéphane Glondu We believe that the bug you reported is fixed in the latest version of frama-c, 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 1040...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Stéphane Glondu (supplier of updated frama-c 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: Thu, 13 Jul 2023 09:10:19 +0200 Source: frama-c Architecture: source Version: 20220511-manganese-4 Distribution: unstable Urgency: medium Maintainer: Debian OCaml Maintainers Changed-By: Stéphane Glondu Closes: 1040537 Changes: frama-c (20220511-manganese-4) unstable; urgency=medium . [ Stéphane Glondu ] * Team upload * Fix compilation with recent yojson (Closes: #1040537) . [ Debian Janitor ] * debian/copyright: use spaces rather than tabs to start continuation lines. Checksums-Sha1: 181bab74f9ade5567d05424e9ac2961fe6655cbc 2212 frama-c_20220511-manganese-4.dsc 523803caa46c1e83d5e54ae3dec5d47d61a53140 16828 frama-c_20220511-manganese-4.debian.tar.xz Checksums-Sha256: 066a24e898f3fffc080b80ad39bf7cdc8ad0009abf44012977233f2bf85d8a85 2212 frama-c_20220511-manganese-4.dsc a5a5a982e252bf1d29189c6434be0496610c7c5915d3db4d9f2621a381567131 16828 frama-c_20220511-manganese-4.debian.tar.xz Files: 616104dd24226e60f3a09350860d0c2c 2212 devel optional frama-c_20220511-manganese-4.dsc 053a00a954b2d036930a96e825889f8e 16828 devel optional frama-c_20220511-manganese-4.debian.tar.xz -BEGIN PGP SIGNATURE- iQFGBAEBCgAwFiEEbeJOl+yohsxW5iUOIbju8bGJMIEFAmSvpT8SHGdsb25kdUBk
Bug#1040959: rust-sequoia-sq: build dependency got updated
Source: rust-sequoia-sq Version: 0.27.0-2 Severity: serious Tags: sid trixie User: debian...@lists.debian.org Usertag: edos-uninstallable Dear maintainer(s), Dose [1] is reporting issues with your packages. Normally your build dependencies shouldn't be removed from testing without removal all reverse build dependencies too, nor should a package be allowed to migrate unless all build dependencies are candidate for migration too. However, somehow we ended up in the current state and your source package is missing some Build-Depends for some while now. Not being able to build from source in a suite is an RC bug in that suite. Can you please solve the situation? Paul [1] https://qa.debian.org/dose/debcheck/src_testing_main/index.html OpenPGP_signature Description: OpenPGP digital signature
Bug#1040937: marked as done (libdune-ocaml-dev: Missing libdune-ocaml-dev-* Provides)
Your message dated Thu, 13 Jul 2023 06:49:16 + with message-id and subject line Bug#1040874: fixed in ocaml-dune 3.9.0-3 has caused the Debian Bug report #1040874, regarding libdune-ocaml-dev: Missing libdune-ocaml-dev-* Provides 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.) -- 1040874: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1040874 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: libdune-ocaml-dev Version: 3.9.0-2 Severity: serious Control: affects -1 libutop-ocaml-dev The following packages have unmet dependencies: libutop-ocaml-dev : Depends: libdune-ocaml-dev-v9190 but it is not installable libdune-ocaml-dev does not have any libdune-ocaml-dev-* Provides. Looking at the dependencies of libdune-ocaml-dev, the loss of the libcsexp-ocaml-dev-* dependency (that is present in bookworm) might also be a bug. --- End Message --- --- Begin Message --- Source: ocaml-dune Source-Version: 3.9.0-3 Done: Stéphane Glondu We believe that the bug you reported is fixed in the latest version of ocaml-dune, 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 1040...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Stéphane Glondu (supplier of updated ocaml-dune 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: Thu, 13 Jul 2023 08:14:09 +0200 Source: ocaml-dune Architecture: source Version: 3.9.0-3 Distribution: unstable Urgency: medium Maintainer: Debian OCaml Maintainers Changed-By: Stéphane Glondu Closes: 1040874 Changes: ocaml-dune (3.9.0-3) unstable; urgency=medium . [ Pino Toscano ] * Deal with PIPE_BUF not present (as in GNU/Hurd), applying a patch proposed for the OCaml 'spawn' library; patch vendor-spawn-pipe_buf.diff. . [ Dan Bungert ] * Add dh_ocaml compatible substitution variables per OCaml packaging policy (Closes: #1040874) Checksums-Sha1: a89761f8d73e6cb49d93b4b24cf96c9a76600e47 1887 ocaml-dune_3.9.0-3.dsc 599f6282798ec39fefbf0ae1d24b5e5563de272e 5324 ocaml-dune_3.9.0-3.debian.tar.xz Checksums-Sha256: 8f579eab18fe7e434910de644c21ee0c7c0110b9592f08d6204f910a04340077 1887 ocaml-dune_3.9.0-3.dsc e1956768ea2fc767791d4015e9e279776102cc5c7d0628f223f492894c337ec1 5324 ocaml-dune_3.9.0-3.debian.tar.xz Files: 99a81dc8843a43d8d8333ad453ec4da8 1887 ocaml optional ocaml-dune_3.9.0-3.dsc de291a391e150d1c24d416c94e243337 5324 ocaml optional ocaml-dune_3.9.0-3.debian.tar.xz -BEGIN PGP SIGNATURE- iQFGBAEBCgAwFiEEbeJOl+yohsxW5iUOIbju8bGJMIEFAmSvmpkSHGdsb25kdUBk ZWJpYW4ub3JnAAoJECG47vGxiTCBdJEH/3T5P7r4m873DO/nwc3gLkNTDBQ7nefR N6bMqnYExuv3J93gRAMeIbD5S+a7ORW5nM3NZHe8uAyIkflY3IREQ1FIbXVKIsky /q34SNvjB2kwfRkdtT5MMDCM8rL3D/W8nxCjj/6Yfguj8dzHU0r2dZASVfRebzne WusepIR9yIQg9nxHTddPPPERcwTEEWZkjDr7k6ChZfysB7CL8hOwwfXZx9FcN0Sr uHYD6joch5RhtBeBHuCh8RA3U6Ck1sFEliocZgcNTj+WGEmn+Kh9NrSttDF4Bx6K mksTBociLMiWsRjx1yKnuOSSixDLm5S/dpNqglP0UgV0grNJ2DJ/8wg= =LX2p -END PGP SIGNATURE End Message ---
Bug#1040874: marked as done (ocaml-dune: Please add ocaml:Provides to d/control)
Your message dated Thu, 13 Jul 2023 06:49:16 +
with message-id
and subject line Bug#1040874: fixed in ocaml-dune 3.9.0-3
has caused the Debian Bug report #1040874,
regarding ocaml-dune: Please add ocaml:Provides to d/control
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.)
--
1040874: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1040874
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: ocaml-dune
Version: 3.9.0-2
Severity: normal
X-Debbugs-Cc: daniel.bung...@canonical.com
Dear Maintainer,
utop shows the following in testing migration:
* libutop-ocaml-dev/amd64 has unsatisfiable dependency
Attempting an install of libutop-ocaml-dev reports:
libutop-ocaml-dev : Depends: libdune-ocaml-dev-v9190 but it is not installable
I believe that adding the ocaml:Provides will resolve this. Debdiff attached.
-Dan
diff -Nru ocaml-dune-3.9.0/debian/changelog ocaml-dune-3.9.0/debian/changelog
--- ocaml-dune-3.9.0/debian/changelog 2023-07-05 02:40:57.0 -0600
+++ ocaml-dune-3.9.0/debian/changelog 2023-07-11 13:41:34.0 -0600
@@ -1,3 +1,10 @@
+ocaml-dune (3.9.0-3) unstable; urgency=medium
+
+ * Rebuild against new OCAML ABIs.
+ * Add dh_ocaml compatible substitution variables per OCaml packaging policy
+
+ -- Dan Bungert Tue, 11 Jul 2023 13:41:34 -0600
+
ocaml-dune (3.9.0-2) unstable; urgency=medium
* Team upload.
diff -Nru ocaml-dune-3.9.0/debian/control ocaml-dune-3.9.0/debian/control
--- ocaml-dune-3.9.0/debian/control 2023-07-05 02:40:57.0 -0600
+++ ocaml-dune-3.9.0/debian/control 2023-07-11 13:41:34.0 -0600
@@ -22,7 +22,9 @@
whitedune (<< 0.30.10-2.2),
dune (<< 1.6.2-3)
Replaces: jbuilder (<< 1.0~beta20-1), whitedune (<< 0.30.10-2.2), dune (<<
1.6.2-3)
-Provides: jbuilder
+Provides:
+ jbuilder,
+ ${ocaml:Provides}
Depends:
${ocaml:Depends},
${shlibs:Depends},
@@ -41,6 +43,8 @@
${ocaml:Depends},
${shlibs:Depends},
${misc:Depends}
+Provides:
+ ${ocaml:Provides}
Suggests:
ocaml-findlib
Description: composable build system for OCaml projects (libraries)
--- End Message ---
--- Begin Message ---
Source: ocaml-dune
Source-Version: 3.9.0-3
Done: Stéphane Glondu
We believe that the bug you reported is fixed in the latest version of
ocaml-dune, 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 1040...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Stéphane Glondu (supplier of updated ocaml-dune 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: Thu, 13 Jul 2023 08:14:09 +0200
Source: ocaml-dune
Architecture: source
Version: 3.9.0-3
Distribution: unstable
Urgency: medium
Maintainer: Debian OCaml Maintainers
Changed-By: Stéphane Glondu
Closes: 1040874
Changes:
ocaml-dune (3.9.0-3) unstable; urgency=medium
.
[ Pino Toscano ]
* Deal with PIPE_BUF not present (as in GNU/Hurd), applying a patch
proposed for the OCaml 'spawn' library; patch
vendor-spawn-pipe_buf.diff.
.
[ Dan Bungert ]
* Add dh_ocaml compatible substitution variables per OCaml packaging
policy (Closes: #1040874)
Checksums-Sha1:
a89761f8d73e6cb49d93b4b24cf96c9a76600e47 1887 ocaml-dune_3.9.0-3.dsc
599f6282798ec39fefbf0ae1d24b5e5563de272e 5324 ocaml-dune_3.9.0-3.debian.tar.xz
Checksums-Sha256:
8f579eab18fe7e434910de644c21ee0c7c0110b9592f08d6204f910a04340077 1887
ocaml-dune_3.9.0-3.dsc
e1956768ea2fc767791d4015e9e279776102cc5c7d0628f223f492894c337ec1 5324
ocaml-dune_3.9.0-3.debian.tar.xz
Files:
99a81dc8843a43d8d8333ad453ec4da8 1887 ocaml optional ocaml-dune_3.9.0-3.dsc
de291a391e150d1c24d416c94e243337 5324 ocaml optional
ocaml-dune_3.9.0-3.debian.tar.xz
-BEGIN PGP SIGNATURE-
iQFGBAEBCgAwFiEEbeJOl+yohsxW5iUOIbju8bGJMIEFAmSvmpkSHGdsb25kdUBk
ZWJpYW4ub3JnAAoJECG47vGxiTCBdJEH/3T5P7r4m873DO/nwc3gLkNTDBQ7nefR
N6bMqnYExuv3J93gRAMeIbD5S+a7ORW5nM3NZHe8uAyIkflY3IREQ1FIbXVKIsky
/q34SNvjB2kwfRkdtT5MMDCM8rL3D/W8nxCjj/6Yfguj8dzHU0r2dZASVfRebzne
WusepIR9yIQg9nxHTddPPPERcwTEEWZkjDr7k6ChZfysB7CL8hOwwfXZx9FcN0Sr
uHYD6joch5RhtBeBHuCh8RA3U6Ck1sFEliocZgcNTj+WGEmn+Kh9NrSttDF4Bx6K
mksTBociLMiWsRjx1yKnuOSSixDLm5S/dpNqglP0UgV0grNJ2DJ/8wg=
=LX2p
Bug#1040874: marked as pending in jbuilder
Control: tag -1 pending Hello, Bug #1040874 in jbuilder 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/ocaml-team/ocaml-dune/-/commit/69c63b9b269f1038b9e599e3f18498416b578733 Add ocaml:Provides to d/control (Closes: #1040874) (this message was generated automatically) -- Greetings https://bugs.debian.org/1040874
Processed: Bug#1040874 marked as pending in jbuilder
Processing control commands: > tag -1 pending Bug #1040874 [libdune-ocaml-dev] ocaml-dune: Please add ocaml:Provides to d/control Bug #1040937 [libdune-ocaml-dev] libdune-ocaml-dev: Missing libdune-ocaml-dev-* Provides Added tag(s) pending. Added tag(s) pending. -- 1040874: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1040874 1040937: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1040937 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: forcibly merging 1040874 1040937
Processing commands for cont...@bugs.debian.org: > forcemerge 1040874 1040937 Bug #1040874 [libdune-ocaml-dev] ocaml-dune: Please add ocaml:Provides to d/control Bug #1040874 [libdune-ocaml-dev] ocaml-dune: Please add ocaml:Provides to d/control Marked as found in versions ocaml-dune/3.9.0-2. Bug #1040937 [libdune-ocaml-dev] libdune-ocaml-dev: Missing libdune-ocaml-dev-* Provides Removed indication that 1040937 affects libutop-ocaml-dev Merged 1040874 1040937 > thanks Stopping processing here. Please contact me if you need assistance. -- 1040874: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1040874 1040937: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1040937 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed (with 1 error): reassign 1040874 to libdune-ocaml-dev, severity of 1040874 is serious, merging 1040874 1040937
Processing commands for cont...@bugs.debian.org: > reassign 1040874 libdune-ocaml-dev Bug #1040874 [src:ocaml-dune] ocaml-dune: Please add ocaml:Provides to d/control Bug reassigned from package 'src:ocaml-dune' to 'libdune-ocaml-dev'. No longer marked as found in versions ocaml-dune/3.9.0-2. Ignoring request to alter fixed versions of bug #1040874 to the same values previously set > severity 1040874 serious Bug #1040874 [libdune-ocaml-dev] ocaml-dune: Please add ocaml:Provides to d/control Severity set to 'serious' from 'normal' > merge 1040874 1040937 Bug #1040874 [libdune-ocaml-dev] ocaml-dune: Please add ocaml:Provides to d/control Unable to merge bugs because: affects of #1040937 is 'libutop-ocaml-dev' not '' Failed to merge 1040874: Did not alter merged bugs. > thanks Stopping processing here. Please contact me if you need assistance. -- 1040874: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1040874 1040937: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1040937 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1040406: python3-azure-cli - fails with No module named 'azure.mgmt.compute.v2022_11_01'
Package: azure-cli Version: 2.45.0-1 Followup-For: Bug #1040406 X-Debbugs-Cc: rvandegr...@debian.org Hi Luca, I'm hitting this issue on azure-cli in bookworm. It sounds like this package is difficult - but is there any possibility of a stable update? $ az vm The command failed with an unexpected error. Here is the traceback: No module named 'azure.mgmt.compute.v2022_11_01' ... Thanks, Ross -- System Information: Debian Release: 12.0 APT prefers stable-security APT policy: (500, 'stable-security'), (500, 'stable'), (40, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 6.4.0-rc3 (SMP w/16 CPU threads; PREEMPT) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE not set Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages azure-cli depends on: ii python33.11.2-1+b1 ii python3-azure-cli 2.45.0-1 azure-cli recommends no packages. azure-cli suggests no packages. -- no debconf information
Processed: Re: Bug#1040924: clevis-udisks2: Depends on NBS libblockdev-crypto2
Processing control commands: > Tags 1040924 +pending Bug #1040924 [clevis-udisks2] clevis-udisks2: Depends on NBS libblockdev-crypto2 Added tag(s) pending. -- 1040924: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1040924 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1040924: clevis-udisks2: Depends on NBS libblockdev-crypto2
Control: Tags 1040924 +pending Jeremy Bícha wrote... > Yes, it's a transition. Sorry that it didn't follow the recommended procedure. Thanks for the clarification. New version is underway, I'd like to do some thourough testing, though. Christoph signature.asc Description: PGP signature
