Bug#960421: libpwiz: FTBFS with boost 1.71
Some googling lead me to
https://svnweb.freebsd.org/ports/head/multimedia/mkvtoolnix/files/patch-boost-1.69?view=markup&pathrev=482787
which suggests it is now necessary to manually convert from tribool to bool by
writing bool{value}
Unfortunately after doing that I get
In file included from /usr/include/boost/type_traits/is_convertible.hpp:20,
from /usr/include/boost/iterator/interoperable.hpp:13,
from /usr/include/boost/iterator/iterator_facade.hpp:11,
from /usr/include/boost/range/iterator_range_core.hpp:27,
from /usr/include/boost/lexical_cast.hpp:30,
from ./pwiz/utility/misc/optimized_lexical_cast.hpp:29,
from ./pwiz/utility/misc/Environment.hpp:24,
from ./pwiz/utility/misc/Std.hpp:29,
from pwiz/data/identdata/Serializer_Text.cpp:25:
/usr/include/boost/lexical_cast/detail/converter_lexical.hpp: In instantiation of ‘struct
boost::detail::deduce_source_char_impl
>’:
/usr/include/boost/lexical_cast/detail/converter_lexical.hpp:279:89: required from
‘struct boost::detail::deduce_source_char’
/usr/include/boost/lexical_cast/detail/converter_lexical.hpp:406:85: required from ‘struct
boost::detail::lexical_cast_stream_traits >’
/usr/include/boost/lexical_cast/detail/converter_lexical.hpp:468:15: required from ‘struct
boost::detail::lexical_converter_impl,
boost::logic::tribool>’
/usr/include/boost/lexical_cast/try_lexical_convert.hpp:201:44: required from ‘bool
boost::conversion::detail::try_lexical_convert(const Source&, Target&) [with Target =
std::__cxx11::basic_string; Source = boost::logic::tribool]’
/usr/include/boost/lexical_cast.hpp:41:60: required from ‘Target
boost::lexical_cast(const Source&) [with Target =
std::__cxx11::basic_string; Source = boost::logic::tribool]’
pwiz/data/identdata/TextWriter.hpp:136:57: required from ‘pwiz::identdata::TextWriter&
pwiz::identdata::TextWriter::operator()(const string&, const object_type&) [with
object_type = boost::logic::tribool; std::string = std::__cxx11::basic_string]’
pwiz/data/identdata/TextWriter.hpp:509:53: required from here
/usr/include/boost/lexical_cast/detail/converter_lexical.hpp:210:13: error:
static assertion failed: Source type is neither std::ostream`able nor
std::wostream`able
210 | BOOST_STATIC_ASSERT_MSG((result_t::value || boost::has_left_shift<
std::basic_ostream< type >, T >::value),
| ^~~
make[1]: *** [Makefile:5478: pwiz/data/identdata/Serializer_Text.lo] Error 1
Which I have no clue about.
Debdiff of what I have done so far is attatched.
diff -Nru libpwiz-3.0.18342/debian/changelog libpwiz-3.0.18342/debian/changelog
--- libpwiz-3.0.18342/debian/changelog 2019-02-01 22:38:03.0 +
+++ libpwiz-3.0.18342/debian/changelog 2020-06-08 01:56:54.0 +
@@ -1,3 +1,10 @@
+libpwiz (3.0.18342-2+rpi1) bullseye-staging; urgency=medium
+
+ * Explicitly convert tribool to bool, this seems to be needed with the
+new boost.
+
+ -- Peter Michael Green Mon, 08 Jun 2020 01:56:54
+
+
libpwiz (3.0.18342-2) unstable; urgency=low
* Improve header path (move pwiz to proteowizard) to ease with nested
diff -Nru libpwiz-3.0.18342/debian/patches/boost.patch
libpwiz-3.0.18342/debian/patches/boost.patch
--- libpwiz-3.0.18342/debian/patches/boost.patch1970-01-01
00:00:00.0 +
+++ libpwiz-3.0.18342/debian/patches/boost.patch2020-06-08
01:56:54.0 +
@@ -0,0 +1,42 @@
+Description: Explicitly convert tribool to bool
+ this seems to be needed with the new boost.
+Author: Peter Michael Green
+
+--- libpwiz-3.0.18342.orig/pwiz/data/identdata/IdentData.cpp
libpwiz-3.0.18342/pwiz/data/identdata/IdentData.cpp
+@@ -1047,7 +1047,7 @@ PWIZ_API_DECL proteome::DigestedPeptide
+ BOOST_FOREACH(CVID cleavageAgent, cleavageAgents)
+ {
+ if (!findPeptideEvidenceWithRegex(pe, peptide,
peptideSequenceInContext, cleavageAgent, "",
+- sip.enzymes.independent,
nTerminusIsSpecific, cTerminusIsSpecific,
++ bool{sip.enzymes.independent},
nTerminusIsSpecific, cTerminusIsSpecific,
+ bestSpecificity, bestResult))
+ break;
+ }
+@@ -1055,7 +1055,7 @@ PWIZ_API_DECL proteome::DigestedPeptide
+ BOOST_FOREACH(const string& regex, cleavageAgentRegexes)
+ {
+ if (!findPeptideEvidenceWithRegex(pe, peptide,
peptideSequenceInContext, CVID_Unknown, regex,
+- sip.enzymes.independent,
nTerminusIsSpecific, cTerminusIsSpecific,
++ bool{sip.enzymes.independent},
nTerminusIsSpecific, cTerminusIsSpecific,
+ bestSpecificity, bestResult))
+ break;
+ }
+@@ -1109,7 +1109,7 @@ PWIZ_API_DECL vector
Bug#962176: numba: fails autopktest with numpy 1.18
Source: numba Followup-For: Bug #962176 The upstream patch does not apply cleaning (on its own), doesn't give a clean build that passes all tests. Probably we need to wait for their next release, else pull an entire git snapshot or rc release. But 0.50.0 is already rc, shouldn't be too long before final release.
Bug#962434: ros-resource-retriever: calls home during build.
Source: ros-resource-retriever
Version: 1.12.6-1
Severity: serious
Hello, using internet during build is forbidden by policy, but still allowed in
Debian builders.
In Ubuntu, where this is more strictly forbidden, the failure seems to indicate
that the package
is trying to connect to internet during tests:
see e.g.
https://launchpad.net/ubuntu/+source/ros-resource-retriever/1.12.6-1/+build/19419607
[ FAILED ] 1 test, listed below:
[ FAILED ] Retriever.http
def test_http():
res = r.get("http://packages.ros.org/ros.key";)
assert len(res) > 0
thanks
Gianfranco
Bug#962381: marked as done (gqrx-sdr: gqrx segmentation fault at start time in testing)
Your message dated Sun, 7 Jun 2020 23:26:48 +0200 with message-id <20200607212648.GC17366@sarastro> and subject line has caused the Debian Bug report #962381, regarding gqrx-sdr: gqrx segmentation fault at start time in testing 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.) -- 962381: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=962381 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: gqrx-sdr Version: 2.12.1-1+b3 Severity: grave Justification: renders package unusable gqrx does not start in testing, this renders the package unusable. The problem is reproducible by spinning up a testing chroot (as of today) and trying to start gqrx This is the stacktrace: *** Thread 1 "gqrx" received signal SIGSEGV, Segmentation fault. 0x555f5a52 in boost::system::error_category::equivalent(boost::system::error_code const&, int) const () (gdb) thread apply all bt Thread 3 (Thread 0x7fffecc54700 (LWP 1745241)): #0 0x7599cb7f in __GI___poll (fds=0x7fffe00029e0, nfds=3, timeout=-1) at ../sysdeps/unix/sysv/linux/poll.c:29 #1 0x736847fe in ?? () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7368491f in g_main_context_iteration () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x768637c1 in QEventDispatcherGlib::processEvents(QFlags) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #4 0x7680c6db in QEventLoop::exec(QFlags) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #5 0x7664d6f1 in QThread::exec() () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #6 0x7fffefe724e6 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5DBus.so.5 #7 0x7664e872 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #8 0x77cd4f27 in start_thread (arg=) at pthread_create.c:479 #9 0x759a731f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 2 (Thread 0x7fffef132700 (LWP 1745240)): #0 0x7599cb7f in __GI___poll (fds=0x7fffef131828, nfds=1, timeout=-1) at ../sysdeps/unix/sysv/linux/poll.c:29 #1 0x730cfd02 in ?? () from /usr/lib/x86_64-linux-gnu/libxcb.so.1 #2 0x730d198a in xcb_wait_for_event () from /usr/lib/x86_64-linux-gnu/libxcb.so.1 #3 0x7fffeffabca0 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5XcbQpa.so.5 #4 0x7664e872 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #5 0x77cd4f27 in start_thread (arg=) at pthread_create.c:479 #6 0x759a731f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 1 (Thread 0x703e8c80 (LWP 1745239)): #0 0x555f5a52 in boost::system::error_category::equivalent(boost::system::error_code const&, int) const () #1 0x76331e8f in boost::asio::detail::posix_mutex::posix_mutex() () from /usr/lib/x86_64-linux-gnu/libgnuradio-blocks.so.3.8.1 #2 0x763329c7 in boost::asio::io_context::io_context() () from /usr/lib/x86_64-linux-gnu/libgnuradio-blocks.so.3.8.1 #3 0x7635ac5c in ?? () from /usr/lib/x86_64-linux-gnu/libgnuradio-blocks.so.3.8.1 #4 0x7635ad39 in gr::blocks::udp_sink::make(unsigned long, std::__cxx11::basic_string, std::allocator > const&, int, int, bool) () from /usr/lib/x86_64-linux-gnu/libgnuradio-blocks.so.3.8.1 #5 0x55641ecc in udp_sink_f::udp_sink_f() () #6 0x556425ef in make_udp_sink_f() () #7 0x556122aa in receiver::receiver(std::__cxx11::basic_string, std::allocator >, std::__cxx11::basic_string, std::allocator >, unsigned int) () #8 0x55605cd0 in MainWindow::MainWindow(QString, bool, QWidget*) () #9 0x555e9f57 in main () *** -- System Information: Debian Release: bullseye/sid APT prefers testing APT policy: (500, 'testing') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 5.6.0-2-amd64 (SMP w/4 CPU cores) Kernel taint flags: TAINT_FIRMWARE_WORKAROUND Locale: LANG=en_IE.utf8, LC_CTYPE=en_IE.utf8 (charmap=UTF-8), LANGUAGE=en_IE.utf8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages gqrx-sdr depends on: ii libboost-program-options1.71.0 1.71.0-6+b2 ii libc6 2.30-8 ii libgcc-s1 10.1.0-3 ii libgnuradio-analog3.8.1 3.8.1.0-1+b3 ii libgnuradio-blocks3.8.1 3.8.1.0-1+b3 ii libgnuradio-digital3.8.13.8.1.0-1+b3 ii libgnuradio-fft3.8.13.8.1.0-1+b3 ii libgnuradio-filter3.8.1 3.8.1.0-1+b3 ii libgnuradio-osmosdr0.2.00.2.0-2+b3 ii libgnuradio-pmt3.8.1
Processed: your mail
Processing commands for cont...@bugs.debian.org:
> found 962381 2.12.1-1+b2
Bug #962381 {Done: Antonio Radici } [gqrx-sdr] gqrx-sdr:
gqrx segmentation fault at start time in testing
Did not alter found versions and reopened.
> fixed 962381 2.12.1-1+b3
Bug #962381 [gqrx-sdr] gqrx-sdr: gqrx segmentation fault at start time in
testing
Marked as fixed in versions gqrx-sdr/2.12.1-1.
>
End of message, stopping processing here.
Please contact me if you need assistance.
--
962381: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=962381
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Processed: cupt: diff for NMU version 2.10.4+nmu1
Processing control commands: > tags 960381 + pending Bug #960381 [src:cupt] cupt: FTBFS with boost 1.71 Added tag(s) pending. -- 960381: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=960381 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#960381: cupt: diff for NMU version 2.10.4+nmu1
Control: tags 960381 + pending Dear maintainer, I've prepared an NMU for cupt (versioned as 2.10.4+nmu1) and uploaded it to DELAYED/2. Please feel free to tell me if I should delay it longer. Cheers -- Sebastian Ramacher diff -Nru cupt-2.10.4/cpp/CMakeLists.txt cupt-2.10.4+nmu1/cpp/CMakeLists.txt --- cupt-2.10.4/cpp/CMakeLists.txt 2019-11-10 10:53:34.0 +0100 +++ cupt-2.10.4+nmu1/cpp/CMakeLists.txt 2020-06-07 22:52:03.0 +0200 @@ -8,9 +8,9 @@ find_package(Boost 1.42.0) IF(Boost_FOUND) - IF(Boost_VERSION LESS 104200) + IF(Boost_VERSION LESS 1.42) message(FATAL_ERROR "need Boost of version 1.42.0") - ENDIF(Boost_VERSION LESS 104200) + ENDIF(Boost_VERSION LESS 1.42) ELSE() message(FATAL_ERROR "missing Boost") ENDIF() diff -Nru cupt-2.10.4/debian/changelog cupt-2.10.4+nmu1/debian/changelog --- cupt-2.10.4/debian/changelog 2019-11-10 10:53:34.0 +0100 +++ cupt-2.10.4+nmu1/debian/changelog 2020-06-07 22:56:21.0 +0200 @@ -1,3 +1,11 @@ +cupt (2.10.4+nmu1) unstable; urgency=medium + + * Non-maintainer upload. + * cmakelists: Fix boost version check (Closes: #960381) +Based on the patch from Ubuntu + + -- Sebastian Ramacher Sun, 07 Jun 2020 22:56:21 +0200 + cupt (2.10.4) unstable; urgency=low * console: signature.asc Description: PGP signature
Bug#962381: marked as done (gqrx-sdr: gqrx segmentation fault at start time in testing)
Your message dated Sun, 7 Jun 2020 22:35:48 +0200 with message-id <20200607203548.GA17366@sarastro> and subject line Re: Bug#962381: gqrx-sdr: gqrx segmentation fault at start time in testing has caused the Debian Bug report #962381, regarding gqrx-sdr: gqrx segmentation fault at start time in testing 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.) -- 962381: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=962381 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: gqrx-sdr Version: 2.12.1-1+b3 Severity: grave Justification: renders package unusable gqrx does not start in testing, this renders the package unusable. The problem is reproducible by spinning up a testing chroot (as of today) and trying to start gqrx This is the stacktrace: *** Thread 1 "gqrx" received signal SIGSEGV, Segmentation fault. 0x555f5a52 in boost::system::error_category::equivalent(boost::system::error_code const&, int) const () (gdb) thread apply all bt Thread 3 (Thread 0x7fffecc54700 (LWP 1745241)): #0 0x7599cb7f in __GI___poll (fds=0x7fffe00029e0, nfds=3, timeout=-1) at ../sysdeps/unix/sysv/linux/poll.c:29 #1 0x736847fe in ?? () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7368491f in g_main_context_iteration () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x768637c1 in QEventDispatcherGlib::processEvents(QFlags) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #4 0x7680c6db in QEventLoop::exec(QFlags) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #5 0x7664d6f1 in QThread::exec() () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #6 0x7fffefe724e6 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5DBus.so.5 #7 0x7664e872 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #8 0x77cd4f27 in start_thread (arg=) at pthread_create.c:479 #9 0x759a731f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 2 (Thread 0x7fffef132700 (LWP 1745240)): #0 0x7599cb7f in __GI___poll (fds=0x7fffef131828, nfds=1, timeout=-1) at ../sysdeps/unix/sysv/linux/poll.c:29 #1 0x730cfd02 in ?? () from /usr/lib/x86_64-linux-gnu/libxcb.so.1 #2 0x730d198a in xcb_wait_for_event () from /usr/lib/x86_64-linux-gnu/libxcb.so.1 #3 0x7fffeffabca0 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5XcbQpa.so.5 #4 0x7664e872 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #5 0x77cd4f27 in start_thread (arg=) at pthread_create.c:479 #6 0x759a731f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 1 (Thread 0x703e8c80 (LWP 1745239)): #0 0x555f5a52 in boost::system::error_category::equivalent(boost::system::error_code const&, int) const () #1 0x76331e8f in boost::asio::detail::posix_mutex::posix_mutex() () from /usr/lib/x86_64-linux-gnu/libgnuradio-blocks.so.3.8.1 #2 0x763329c7 in boost::asio::io_context::io_context() () from /usr/lib/x86_64-linux-gnu/libgnuradio-blocks.so.3.8.1 #3 0x7635ac5c in ?? () from /usr/lib/x86_64-linux-gnu/libgnuradio-blocks.so.3.8.1 #4 0x7635ad39 in gr::blocks::udp_sink::make(unsigned long, std::__cxx11::basic_string, std::allocator > const&, int, int, bool) () from /usr/lib/x86_64-linux-gnu/libgnuradio-blocks.so.3.8.1 #5 0x55641ecc in udp_sink_f::udp_sink_f() () #6 0x556425ef in make_udp_sink_f() () #7 0x556122aa in receiver::receiver(std::__cxx11::basic_string, std::allocator >, std::__cxx11::basic_string, std::allocator >, unsigned int) () #8 0x55605cd0 in MainWindow::MainWindow(QString, bool, QWidget*) () #9 0x555e9f57 in main () *** -- System Information: Debian Release: bullseye/sid APT prefers testing APT policy: (500, 'testing') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 5.6.0-2-amd64 (SMP w/4 CPU cores) Kernel taint flags: TAINT_FIRMWARE_WORKAROUND Locale: LANG=en_IE.utf8, LC_CTYPE=en_IE.utf8 (charmap=UTF-8), LANGUAGE=en_IE.utf8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages gqrx-sdr depends on: ii libboost-program-options1.71.0 1.71.0-6+b2 ii libc6 2.30-8 ii libgcc-s1 10.1.0-3 ii libgnuradio-analog3.8.1 3.8.1.0-1+b3 ii libgnuradio-blocks3.8.1 3.8.1.0-1+b3 ii libgnuradio-digital3.8.13.8.1.0-1+b3 ii libgnuradio-fft3.8.13.8.1.0-1+b3 ii libgnuradio-filter3.8.1 3.8.1.0-1+b3 i
Bug#962424: zfsutils-linux: systemd zfs-mount-generator breaks boot if multiple datasets have the same mountpoint
Btw the workaround seems to be to mask zfs-mount-generator (`mkdir /etc/systemd/system-generators/; ln -s /dev/null /etc/systemd/system-generators/zfs-mount-generator`) Cheers -- Clément 'wxcafé' Hertling
Processed: fixed 960321 in 2.2.18-8
Processing commands for cont...@bugs.debian.org:
> fixed 960321 2.2.18-8
Bug #960321 {Done: Calogero Lo Leggio } [src:burp] burp:
flaky arm64 autopkgtest: .../src/test/clientscript failed
The source 'burp' and version '2.2.18-8' do not appear to match any binary
packages
Marked as fixed in versions burp/2.2.18-8.
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
960321: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=960321
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Processed: Fixed in 2.3.2
Processing commands for cont...@bugs.debian.org: > tags 962423 fixed-upstream patch Bug #962423 [pglogical] pglogical FTBFS error: static declaration of 'AcquireDeletionLock' follows non-static declaration Added tag(s) fixed-upstream and patch. > forwarded 962423 > https://github.com/2ndQuadrant/pglogical/commit/71c96f629a202ea233e459e8b48d016257feae15 Bug #962423 [pglogical] pglogical FTBFS error: static declaration of 'AcquireDeletionLock' follows non-static declaration Set Bug forwarded-to-address to 'https://github.com/2ndQuadrant/pglogical/commit/71c96f629a202ea233e459e8b48d016257feae15'. > thanks Stopping processing here. Please contact me if you need assistance. -- 962423: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=962423 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: zimlib: diff for NMU version 4.0.4-5.1
Processing control commands: > tags 960243 + patch Bug #960243 [src:zimlib] zimlib FTBFS with ICU 67.1 Added tag(s) patch. > tags 960243 + pending Bug #960243 [src:zimlib] zimlib FTBFS with ICU 67.1 Added tag(s) pending. -- 960243: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=960243 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#960243: zimlib: diff for NMU version 4.0.4-5.1
Control: tags 960243 + patch Control: tags 960243 + pending Dear maintainer, I've prepared an NMU for zimlib (versioned as 4.0.4-5.1) and uploaded it to DELAYED/2. Please feel free to tell me if I should delay it longer. Cheers -- Sebastian Ramacher diff -Nru zimlib-4.0.4/debian/changelog zimlib-4.0.4/debian/changelog --- zimlib-4.0.4/debian/changelog 2018-12-19 09:53:38.0 +0100 +++ zimlib-4.0.4/debian/changelog 2020-06-07 22:26:22.0 +0200 @@ -1,3 +1,11 @@ +zimlib (4.0.4-5.1) unstable; urgency=medium + + * Non-maintainer upload. + * debian/libzim4.symbols: Mark more template instantiations as optional and +update for changes due to icu 67. (Closes: #960243) + + -- Sebastian Ramacher Sun, 07 Jun 2020 22:26:22 +0200 + zimlib (4.0.4-5) unstable; urgency=medium * Have libzim-dev depend upon libraries it Requires in libzim.pc diff -Nru zimlib-4.0.4/debian/libzim4.symbols zimlib-4.0.4/debian/libzim4.symbols --- zimlib-4.0.4/debian/libzim4.symbols 2018-12-11 08:33:26.0 +0100 +++ zimlib-4.0.4/debian/libzim4.symbols 2020-06-07 22:25:05.0 +0200 @@ -165,6 +165,8 @@ _ZN3zim4unix2FS6renameERKNSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEES9_@Base 4.0.4 _ZN3zim4unix2FS8openFileERKNSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEE@Base 4.0.4 _ZN3zim4unix2FS9removeDirERKNSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEE@Base 4.0.4 + (optional=templinst)_ZN3zim5CacheINS_15article_index_tESt10shared_ptrIKNS_6DirentEEE3putERKS1_RKS5_@Base 4.0.4 + (optional=templinst)_ZN3zim5CacheINS_15cluster_index_tESt10shared_ptrINS_7ClusterEEE3putERKS1_RKS4_@Base 4.0.4 _ZN3zim6Dirent15deletedMimeTypeE@Base 4.0.4 _ZN3zim6Dirent16redirectMimeTypeE@Base 4.0.4 _ZN3zim6Dirent18linktargetMimeTypeE@Base 4.0.4 @@ -310,10 +312,10 @@ (optional=templinst)_ZN5QueueIPN3zim6writer7ClusterEED0Ev@Base 4.0.4 (optional=templinst)_ZN5QueueIPN3zim6writer7ClusterEED1Ev@Base 4.0.4 (optional=templinst)_ZN5QueueIPN3zim6writer7ClusterEED2Ev@Base 4.0.4 - (optional=templinst)_ZN6icu_6314StringByteSinkINSt7__cxx1112basic_stringIcSt11char_traitsIcESaIc6AppendEPKci@Base 4.0.4 - (optional=templinst)_ZN6icu_6314StringByteSinkINSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcD0Ev@Base 4.0.4 - (optional=templinst)_ZN6icu_6314StringByteSinkINSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcD1Ev@Base 4.0.4 - (optional=templinst)_ZN6icu_6314StringByteSinkINSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcD2Ev@Base 4.0.4 + (optional=templinst)_ZN6icu_6714StringByteSinkINSt7__cxx1112basic_stringIcSt11char_traitsIcESaIc6AppendEPKci@Base 4.0.4 + (optional=templinst)_ZN6icu_6714StringByteSinkINSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcD0Ev@Base 4.0.4 + (optional=templinst)_ZN6icu_6714StringByteSinkINSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcD1Ev@Base 4.0.4 + (optional=templinst)_ZN6icu_6714StringByteSinkINSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcD2Ev@Base 4.0.4 _ZN8RESOURCE9stopwords2enB5cxx11E@Base 4.0.4 _ZN8RESOURCE9stopwords2heB5cxx11E@Base 4.0.4 _ZN8RESOURCE9stopwords3fraB5cxx11E@Base 4.0.4 @@ -454,8 +456,8 @@ (optional=templinst|arch=ia64)_ZNSt10unique_ptrIN3zim15search_iterator12InternalDataESt14default_deleteIS2_EED2Ev@Base 4.0.4 (optional=templinst|arch=ia64)_ZNSt10unique_ptrIN3zim6Search12InternalDataESt14default_deleteIS2_EED1Ev@Base 4.0.4 (optional=templinst|arch=ia64)_ZNSt10unique_ptrIN3zim6Search12InternalDataESt14default_deleteIS2_EED2Ev@Base 4.0.4 - (optional=templinst)_ZNSt10unique_ptrIN6icu_6314TransliteratorESt14default_deleteIS1_EED1Ev@Base 4.0.4 - (optional=templinst)_ZNSt10unique_ptrIN6icu_6314TransliteratorESt14default_deleteIS1_EED2Ev@Base 4.0.4 + (optional=templinst)_ZNSt10unique_ptrIN6icu_6714TransliteratorESt14default_deleteIS1_EED1Ev@Base 4.0.4 + (optional=templinst)_ZNSt10unique_ptrIN6icu_6714TransliteratorESt14default_deleteIS1_EED2Ev@Base 4.0.4 (optional=templinst)_ZNSt11_Deque_baseIPN3zim6writer7ClusterESaIS3_EED1Ev@Base 4.0.4 (optional=templinst)_ZNSt11_Deque_baseIPN3zim6writer7ClusterESaIS3_EED2Ev@Base 4.0.4 (optional=templinst|arch=armel)_ZNSt12__shared_ptrIKN3zim6BufferELN9__gnu_cxx12_Lock_policyE1EEC1INS0_12MemoryBufferILb1EEEvEEPT_@Base 4.0.4 @@ -664,6 +666,7 @@ (optional=templinst|arch=!ia64)_ZSt4swapIN3zim6writer6DirentEENSt9enable_ifIXsrSt6__and_IJSt6__not_ISt15__is_tuple_likeIT_EESt21is_move_constructibleIS7_ESt18is_move_assignableIS7_EEE5valueEvE4typeERS7_SH_@Base 4.0.4 (optional=templinst)_ZSt9__find_ifIN9__gnu_cxx17__normal_iteratorIPKcNSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcENS0_5__ops10_Iter_predIPFbcT_SG_SG_T0_St26random_access_iterator_tag@Base 4.0.4 (optional=templinst)_ZSt9__find_ifIN9__gnu_cxx17__normal_iteratorIPKcNSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcENS0_5__ops16_Iter_equals_valIS2_EEET_SE_SE_T0_St26random_access_iterator_tag@Base 4.0.4 + (optional=templinst)_ZStplIcSt11char_traitsIcESaIcEENSt7__cxx1112basic_stringIT_T0_T1_EEOS8_RKS8_@Base 4.0.4
Processed: frama-c: FTBFS fixed upstream
Processing control commands: > forwarded -1 > https://lists.gforge.inria.fr/pipermail/frama-c-discuss/2020-June/005823.html Bug #959599 [src:frama-c] frama-c: FTBFS: Error: Unbound value const_of_big_int Set Bug forwarded-to-address to 'https://lists.gforge.inria.fr/pipermail/frama-c-discuss/2020-June/005823.html'. > tags -1 fixed-upstream Bug #959599 [src:frama-c] frama-c: FTBFS: Error: Unbound value const_of_big_int Added tag(s) fixed-upstream. -- 959599: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=959599 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#960321: marked as done (burp: flaky arm64 autopkgtest: .../src/test/clientscript failed)
Your message dated Sun, 7 Jun 2020 22:17:17 +0200 with message-id <2cbd0459-3373-4c98-b7aa-b4fd4b603...@nerdrug.org> and subject line has caused the Debian Bug report #960321, regarding burp: flaky arm64 autopkgtest: .../src/test/clientscript failed 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.) -- 960321: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=960321 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: burp Version: 2.2.18-2 Severity: serious Tags: sid bullseye X-Debbugs-CC: debian...@lists.debian.org User: debian...@lists.debian.org Usertags: flaky Dear maintainer(s), With a recent upload of glibc to unstable, the autopkgtest of burp failed on arm64 in testing when that autopkgtest was run with the binary packages of glibc from unstable. I looked into the history of your autopkgtest and it fails often on arm64. Because the unstable-to-testing migration software now blocks on regressions in testing, flaky tests, i.e. tests that flip between passing and failing without changes to the list of installed packages, are causing people unrelated to your package to spend time on these tests. Please either fix the test to be more robust, or use the "flaky" restriction for the offending test until a solution has been found. I copied the output at the bottom of this report. Not all the failing tests [1] that I inspected look the same. I'll have the migration software ignore the results of your autopkgtest on arm64 until this bug is fixed. Paul [1] https://ci.debian.net/packages/b/burp/testing/arm64/ https://ci.debian.net/data/autopkgtest/testing/arm64/b/burp/4545083/log.gz Starting tests Server log: /tmp/autopkgtest-lxc.nu3r440c/downtmp/build.2w2/src/test/logs/server.log Client log: /tmp/autopkgtest-lxc.nu3r440c/downtmp/build.2w2/src/test/logs/client.log Diff log: /tmp/autopkgtest-lxc.nu3r440c/downtmp/build.2w2/src/test/logs/diff.log More logs can be found in: /tmp/autopkgtest-lxc.nu3r440c/downtmp/build.2w2/src/test/target/var/spool/burp/testclient/ Initialising server certificate authority Starting test server Running protocol 1 tests Test 1 Interrupt server phase1 Test 1 OK Test 2 Interrupt client phase1 Test 2 OK Test 3 Compression on, encryption off, change files off Test 3 failed: /tmp/autopkgtest-lxc.nu3r440c/downtmp/build.2w2/src/test/clientscript failed (backup 1) Killing test server make: *** [Makefile:16: test] Error 1 autopkgtest [08:45:13]: test burp-builtin-test: ---] signature.asc Description: OpenPGP digital signature --- End Message --- --- Begin Message --- signature.asc Description: OpenPGP digital signature --- End Message ---
Bug#959599: frama-c: FTBFS fixed upstream
Control: forwarded -1 https://lists.gforge.inria.fr/pipermail/frama-c-discuss/2020-June/005823.html Control: tags -1 fixed-upstream > Hello, > > Le jeu. 4 juin 2020 à 18:43, John Scott a écrit : > > I'm not the maintainer, just a prospective user taking a look, but Frama-C > > hasn't been building from source in a while [1] and I couldn't find a bug > > for > > it. It fails with > > File "src/plugins/wp/ProverWhy3.ml", line 131, characters 29-45: > > 131 | Why3.(Term.t_const Number.(const_of_big_int (BigInt.of_string > > (Z.to_string z Why3.Ty.ty_int > > Error: Unbound value const_of_big_int > > Thanks for the report. There is indeed a compatibility issue between > Frama-C 20.0 and Why3 1.3, which is fixed in the upcoming Frama-C 21.0 > (currently available in beta) On the other hand, Frama-C 21.0 won't be > compatible with Why3 < 1.3 I'm having trouble finding their VCS and what commit fixed this, but updating Frama-C to the beta should be sufficient. Unstable and testing already have Why3 >= 1.3. signature.asc Description: This is a digitally signed message part.
Bug#960321: burp: flaky arm64 autopkgtest: .../src/test/clientscript failed
As suggested by upstream developer, I removed superfluous 'slow and intensive' test. The definitive fix is introduced in version 2.2.18-8 References: github issue to upstream dev: https://github.com/grke/burp/issues/866 salsa commit: https://salsa.debian.org/debian/burp/-/commit/f9363a7af36ac729c319f0545c8b1e070df4090d Thanks! > References: > > [1]: https://github.com/grke/burp/issues/866 > > [2]: > https://salsa.debian.org/debian/burp/-/commit/513e4c37a59f5cea98bc7723188c2ed0cb70f776 > signature.asc Description: OpenPGP digital signature
Bug#962424: zfsutils-linux: systemd zfs-mount-generator breaks boot if multiple datasets have the same mountpoint
Package: zfsutils-linux Version: 0.8.4-1~bpo10+1 Severity: grave Tags: upstream Justification: renders package unusable Hey The systemd zfs-mount-generator script (/lib/systemd/system-generators/zfs-mount-generator) can break system boot if there are multiple datasets with the same mountpoint, because it ignores the zfs property canmount=noauto. I store backups on my system and after upgrading the system wouldn't boot anymore because while my backups are canmount=noauto, the generator was trying to mount multiple datasets to the same mountpoints (/, /usr/, ...) which obviously breaks... everything. I'd say that's less than ideal. ZoL's integration with systemd has always been subpar (until 0.8.4 zfs-import-cache was broken because it looked at /usr/local/etc/zfs/zpool.cache instead of /etc/zfs/zpool.cache, for example), but breaking boot in a patch release is really not good -- System Information: Debian Release: 10.4 APT prefers stable APT policy: (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 5.5.0-0.bpo.2-amd64 (SMP w/8 CPU cores) Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) (ignored: LC_ALL set to en_US.UTF-8), LANGUAGE=en_US.UTF-8 (charmap=UTF-8) (ignored: LC_ALL set to en_US.UTF-8) Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages zfsutils-linux depends on: ii libblkid12.33.1-0.1 ii libc62.28-10 ii libnvpair1linux 0.8.4-1~bpo10+1 ii libudev1 241-7~deb10u4 ii libuuid1 2.33.1-0.1 ii libuutil1linux 0.8.4-1~bpo10+1 ii libzfs2linux 0.8.4-1~bpo10+1 ii libzpool2linux 0.8.4-1~bpo10+1 ii python3 3.7.3-1 ii zlib1g 1:1.2.11.dfsg-1 Versions of packages zfsutils-linux recommends: ii lsb-base10.2019051400 ii zfs-dkms [zfs-modules] 0.8.4-1~bpo10+1 ii zfs-zed 0.8.4-1~bpo10+1 Versions of packages zfsutils-linux suggests: pn nfs-kernel-server pn samba-common-bin ii zfs-initramfs 0.8.4-1~bpo10+1 -- Configuration Files: /etc/cron.d/zfsutils-linux [Errno 2] No such file or directory: '/etc/cron.d/zfsutils-linux' /etc/sudoers.d/zfs [Errno 13] Permission denied: '/etc/sudoers.d/zfs' -- no debconf information
Bug#949837: innoextract: diff for NMU version 1.8-1.2
Control: tags 949837 + pending
Dear maintainer,
I've prepared an NMU for innoextract (versioned as 1.8-1.2) and
uploaded it to DELAYED/2. Please feel free to tell me if I
should delay it longer.
Cheers
--
Sebastian Ramacher
diff -Nru innoextract-1.8/debian/changelog innoextract-1.8/debian/changelog
--- innoextract-1.8/debian/changelog 2020-05-02 20:00:51.0 +0200
+++ innoextract-1.8/debian/changelog 2020-06-07 22:00:19.0 +0200
@@ -1,3 +1,11 @@
+innoextract (1.8-1.2) unstable; urgency=medium
+
+ * Non-maintainer upload.
+ * debian/patches: Apply upstream patch to fix build with boost 1.71.
+(Closes: #949837)
+
+ -- Sebastian Ramacher Sun, 07 Jun 2020 22:00:19 +0200
+
innoextract (1.8-1.1) unstable; urgency=low
* Non-maintainer upload.
diff -Nru innoextract-1.8/debian/patches/b47f46102bccf1d813ca159230029b0cd820ceff.patch innoextract-1.8/debian/patches/b47f46102bccf1d813ca159230029b0cd820ceff.patch
--- innoextract-1.8/debian/patches/b47f46102bccf1d813ca159230029b0cd820ceff.patch 1970-01-01 01:00:00.0 +0100
+++ innoextract-1.8/debian/patches/b47f46102bccf1d813ca159230029b0cd820ceff.patch 2020-06-07 21:59:01.0 +0200
@@ -0,0 +1,158 @@
+From b47f46102bccf1d813ca159230029b0cd820ceff Mon Sep 17 00:00:00 2001
+From: Daniel Scharrer
+Date: Mon, 23 Sep 2019 00:00:52 +0200
+Subject: [PATCH] CMake: Remove library link checks
+
+This was needed with older CMake versions to work around CMake searching
+under lib with -m32 instead of under lib32 for platforms where lib
+contains 64-bit binaries. This has since been fixed in CMake and users
+of older CMake versions can add the lib32 directories to
+CMAKE_LIBRARY_PATH to work around the issue on their end.
+
+With newer CMake and Boost versions these checks fail because the
+boost-config.cmake files shipped with Boost use imported targets instead
+of library paths and try_compile does not add these imported targets to
+the generated project.
+
+See: https://gitlab.kitware.com/cmake/cmake/issues/11260
+---
+ CMakeLists.txt | 4 --
+ cmake/CompileCheck.cmake | 88
+ 2 files changed, 92 deletions(-)
+
+diff --git a/CMakeLists.txt b/CMakeLists.txt
+index b98e59d..8aba97c 100644
+--- a/CMakeLists.txt
b/CMakeLists.txt
+@@ -158,7 +158,6 @@ endif()
+
+ if(USE_LZMA)
+ find_package(LZMA REQUIRED)
+- check_link_library(LZMA LZMA_LIBRARIES)
+ list(APPEND LIBRARIES ${LZMA_LIBRARIES})
+ include_directories(SYSTEM ${LZMA_INCLUDE_DIR})
+ add_definitions(${LZMA_DEFINITIONS})
+@@ -176,7 +175,6 @@ find_package(Boost REQUIRED COMPONENTS
+ system
+ program_options
+ )
+-check_link_library(Boost Boost_LIBRARIES)
+ list(APPEND LIBRARIES ${Boost_LIBRARIES})
+ link_directories(${Boost_LIBRARY_DIRS})
+ include_directories(SYSTEM ${Boost_INCLUDE_DIR})
+@@ -210,7 +208,6 @@ if(Boost_HAS_STATIC_LIBS)
+ break()
+ endif()
+ endforeach()
+- check_link_library(${Lib} ${LIB}_LIBRARIES)
+ list(APPEND LIBRARIES ${${LIB}_LIBRARIES})
+ endforeach()
+ endif()
+@@ -227,7 +224,6 @@ elseif(NOT WITH_CONV OR WITH_CONV STREQUAL "iconv")
+ endif()
+ find_package(iconv ${ICONV_REQUIRED})
+ if(ICONV_FOUND)
+- check_link_library(iconv iconv_LIBRARIES)
+ list(APPEND LIBRARIES ${iconv_LIBRARIES})
+ include_directories(SYSTEM ${iconv_INCLUDE_DIR})
+ add_definitions(${iconv_DEFINITIONS})
+diff --git a/cmake/CompileCheck.cmake b/cmake/CompileCheck.cmake
+index 1e88599..4a72d38 100644
+--- a/cmake/CompileCheck.cmake
b/cmake/CompileCheck.cmake
+@@ -192,95 +192,7 @@ function(add_ldflag FLAG)
+
+ endfunction(add_ldflag)
+
+-function(try_link_library LIBRARY_NAME LIBRARY_FILE ERROR_VAR)
+- # See if we can link a simple program with the library using the configured c++ compiler
+- set(link_test_file "${CMAKE_CURRENT_BINARY_DIR}/link_test.cpp")
+- file(WRITE ${link_test_file} "int main(){}\n")
+- if(CMAKE_THREAD_LIBS_INIT)
+- list(APPEND LIBRARY_FILE "${CMAKE_THREAD_LIBS_INIT}")
+- endif()
+- try_compile(
+- CHECK_${LIBRARY_NAME}_LINK "${PROJECT_BINARY_DIR}" "${link_test_file}"
+- CMAKE_FLAGS "-DLINK_LIBRARIES=${LIBRARY_FILE}"
+- "-DCMAKE_CXX_FLAGS=${CMAKE_CXX_FLAGS}"
+- "-DCMAKE_EXE_LINKER_FLAGS=${CMAKE_EXE_LINKER_FLAGS}"
+- "-DCMAKE_SHARED_LINKER_FLAGS=${CMAKE_SHARED_LINKER_FLAGS}"
+- "-DCMAKE_MODULE_LINKER_FLAGS=${CMAKE_MODULE_LINKER_FLAGS}"
+- OUTPUT_VARIABLE ERRORLOG
+- )
+- set(${ERROR_VAR} "${ERRORLOG}" PARENT_SCOPE)
+-endfunction(try_link_library)
+-
+-##
+-# Check that a a library actually works for the current configuration
+-# This is neede because CMake prefers /usr/lib over /usr/lib32 for -m32 builds
+-# See https://public.kitware.com/Bug/view.php?id=11260
+-function(check_link_library LIBRARY_NAME LIBRARY_VARIABLE)
+-
+- if(MSVC)
+- # The main point of this is to work around CMakes ignorance of lib32.
+- # This doesn't really apply for systems that
Processed: innoextract: diff for NMU version 1.8-1.2
Processing control commands: > tags 949837 + pending Bug #949837 [innoextract] FTBFS with Boost 1.71 Added tag(s) pending. -- 949837: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=949837 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#962423: pglogical FTBFS error: static declaration of 'AcquireDeletionLock' follows non-static declaration
Package: pglogical Version: 2.3.1-1 Severity: serious Tags: ftbfs It seems pglogical recently started failing to build. http://buildd.raspbian.org/status/fetch.php?pkg=pglogical&arch=armhf&ver=2.3.1-1%2Bb1&stamp=1591473342 https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/pglogical.html /build/1st/pglogical-2.3.1/pglogical_dependency.c:235:13: error: static declaration of 'AcquireDeletionLock' follows non-static declaration 235 | static void AcquireDeletionLock(const ObjectAddress *object, int flags); | ^~~ In file included from /build/1st/pglogical-2.3.1/pglogical_dependency.c:29: /usr/include/postgresql/12/server/catalog/dependency.h:145:13: note: previous declaration of 'AcquireDeletionLock' was here 145 | extern void AcquireDeletionLock(const ObjectAddress *object, int flags); | ^~~ /build/1st/pglogical-2.3.1/pglogical_dependency.c:236:13: error: static declaration of 'ReleaseDeletionLock' follows non-static declaration 236 | static void ReleaseDeletionLock(const ObjectAddress *object); | ^~~ In file included from /build/1st/pglogical-2.3.1/pglogical_dependency.c:29: /usr/include/postgresql/12/server/catalog/dependency.h:147:13: note: previous declaration of 'ReleaseDeletionLock' was here 147 | extern void ReleaseDeletionLock(const ObjectAddress *object); | ^~~ make[2]: *** [: pglogical_dependency.o] Error 1
Processed: Dupe
Processing commands for cont...@bugs.debian.org: > forcemerge 960877 962092 Bug #960877 [meson] meson 0.54.2-1 breaks bali-phy build Bug #962092 [meson] meson: Link with static lib instead of shared one with boost 1.71 Set Bug forwarded-to-address to 'https://github.com/mesonbuild/meson/issues/7221'. Severity set to 'serious' from 'normal' Added indication that 962092 affects src:bali-phy Added tag(s) ftbfs. Merged 960877 962092 > End of message, stopping processing here. Please contact me if you need assistance. -- 960877: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=960877 962092: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=962092 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#962232: vanguards indirectly build-depends on cruft package.
On Thu, 4 Jun 2020 21:21:53 +0100 peter green wrote: > Package: vanguards > Version: 0.3.1-2 > Severity: serious > > vanguards build-depends on pypy-pytest which depends on pypy-funcsigs which is no longer built by the python-funcsigs source package. The pytest maintainer has also said they would like to get rid of pypy support from pytest. Afaict vanguards is the only application that build-depends on pypy- pytest (there are also some module packages but they all look like they could drop pypy support at the same time pytest does). > > The ideal fix would be to move to pypy3, but I understand that is currently blocked on tooling (see https://bugs.debian.org/cgi-bin/bugreport.cgi? bug=932820 ). Over in bug 937769 Chris Lamb proposed a patch to run the testsuite with python 3. Obviously running the testsuite with a different python version from that used to actually run the program is suboptimal but I think it's the lesser evil here. > > I manually applied the patch, cleaning up some formatting and making the dependency versioning for the python3-stem build-dependency match that for the pypy-stem build-dependency. While testing I also noticed some clean target issues so I fixed them. > > A debdiff is attatched, if I get no objections (and the maintainer doesn't upload this first) I will likely NMU this in a week or so. > pypy-pytest is a cruft package now, so it's no longer indirect. Scott K signature.asc Description: This is a digitally signed message part.
Bug#938099: marked as done (python-pysqlite2: Python2 removal in sid/bullseye)
Your message dated Sun, 07 Jun 2020 19:36:37 + with message-id and subject line Bug#962370: Removed package(s) from unstable has caused the Debian Bug report #938099, regarding python-pysqlite2: Python2 removal in sid/bullseye 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.) -- 938099: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=938099 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: src:python-pysqlite2 Version: 2.7.0-1 Severity: normal Tags: sid bullseye User: debian-pyt...@lists.debian.org Usertags: py2removal Python2 becomes end-of-live upstream, and Debian aims to remove Python2 from the distribution, as discussed in https://lists.debian.org/debian-python/2019/07/msg00080.html Your package either build-depends, depends on Python2, or uses Python2 in the autopkg tests. Please stop using Python2, and fix this issue by one of the following actions. - Convert your Package to Python3. This is the preferred option. In case you are providing a Python module foo, please consider dropping the python-foo package, and only build a python3-foo package. Please don't drop Python2 modules, which still have reverse dependencies, just document them. This is the preferred option. - If the package is dead upstream, cannot be converted or maintained in Debian, it should be removed from the distribution. If the package still has reverse dependencies, raise the severity to "serious" and document the reverse dependencies with the BTS affects command. If the package has no reverse dependencies, confirm that the package can be removed, reassign this issue to ftp.debian.org, make sure that the bug priority is set to normal and retitle the issue to "RM: PKG -- removal triggered by the Python2 removal". - If the package has still many users (popcon >= 300), or is needed to build another package which cannot be removed, document that by adding the "py2keep" user tag (not replacing the py2remove tag), using the debian-pyt...@lists.debian.org user. Also any dependencies on an unversioned python package (python, python-dev) must not be used, same with the python shebang. These have to be replaced by python2/python2.7 dependencies and shebang. This is the least preferred option. If the conversion or removal needs action on another package first, please document the blocking by using the BTS affects command, like affects + src:python-pysqlite2 If there is no py2removal bug for that reverse-dependency, please file a bug on this package (similar to this bug report). If there are questions, please refer to the wiki page for the removal: https://wiki.debian.org/Python/2Removal, or ask for help on IRC #debian-python, or the debian-pyt...@lists.debian.org mailing list. --- End Message --- --- Begin Message --- Version: 2.7.0-1+rm Dear submitter, as the package python-pysqlite2 has just been removed from the Debian archive unstable we hereby close the associated bug reports. We are sorry that we couldn't deal with your issue properly. For details on the removal, please see https://bugs.debian.org/962370 The version of this package that was in Debian prior to this removal can still be found using http://snapshot.debian.org/. Please note that the changes have been done on the master archive and will not propagate to any mirrors until the next dinstall run at the earliest. This message was generated automatically; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org. Debian distribution maintenance software pp. Scott Kitterman (the ftpmaster behind the curtain)--- End Message ---
Bug#937749: marked as done (python-fcgi: Python2 removal in sid/bullseye)
Your message dated Sun, 07 Jun 2020 19:37:01 + with message-id and subject line Bug#962371: Removed package(s) from unstable has caused the Debian Bug report #937749, regarding python-fcgi: Python2 removal in sid/bullseye 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.) -- 937749: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=937749 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: src:python-fcgi Version: 19980130-1 Severity: normal Tags: sid bullseye User: debian-pyt...@lists.debian.org Usertags: py2removal Python2 becomes end-of-live upstream, and Debian aims to remove Python2 from the distribution, as discussed in https://lists.debian.org/debian-python/2019/07/msg00080.html Your package either build-depends, depends on Python2, or uses Python2 in the autopkg tests. Please stop using Python2, and fix this issue by one of the following actions. - Convert your Package to Python3. This is the preferred option. In case you are providing a Python module foo, please consider dropping the python-foo package, and only build a python3-foo package. Please don't drop Python2 modules, which still have reverse dependencies, just document them. This is the preferred option. - If the package is dead upstream, cannot be converted or maintained in Debian, it should be removed from the distribution. If the package still has reverse dependencies, raise the severity to "serious" and document the reverse dependencies with the BTS affects command. If the package has no reverse dependencies, confirm that the package can be removed, reassign this issue to ftp.debian.org, make sure that the bug priority is set to normal and retitle the issue to "RM: PKG -- removal triggered by the Python2 removal". - If the package has still many users (popcon >= 300), or is needed to build another package which cannot be removed, document that by adding the "py2keep" user tag (not replacing the py2remove tag), using the debian-pyt...@lists.debian.org user. Also any dependencies on an unversioned python package (python, python-dev) must not be used, same with the python shebang. These have to be replaced by python2/python2.7 dependencies and shebang. This is the least preferred option. If the conversion or removal needs action on another package first, please document the blocking by using the BTS affects command, like affects + src:python-fcgi If there is no py2removal bug for that reverse-dependency, please file a bug on this package (similar to this bug report). If there are questions, please refer to the wiki page for the removal: https://wiki.debian.org/Python/2Removal, or ask for help on IRC #debian-python, or the debian-pyt...@lists.debian.org mailing list. --- End Message --- --- Begin Message --- Version: 19980130-1+rm Dear submitter, as the package python-fcgi has just been removed from the Debian archive unstable we hereby close the associated bug reports. We are sorry that we couldn't deal with your issue properly. For details on the removal, please see https://bugs.debian.org/962371 The version of this package that was in Debian prior to this removal can still be found using http://snapshot.debian.org/. Please note that the changes have been done on the master archive and will not propagate to any mirrors until the next dinstall run at the earliest. This message was generated automatically; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org. Debian distribution maintenance software pp. Scott Kitterman (the ftpmaster behind the curtain)--- End Message ---
Bug#960243: zimlib FTBFS with ICU 67.1
I downloaded the build logs and filtered them to show the missing symbols that were not already marked as optional. plugwash@thinkpad:~$ wget -O zimlib.log 'https://buildd.debian.org/status/fetch.php?pkg=zimlib&arch=amd64&ver=4.0.4-5%2Bb1&stamp=1591384179&raw=0' plugwash@thinkpad:~$ html2text -width 10 zimlib.log | grep MISSING | grep -v optional +#MISSING: 4.0.4-5+b1# _ZTIN6icu_6314StringByteSinkINSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcE@Base 4.0.4 +#MISSING: 4.0.4-5+b1# _ZTSN6icu_6314StringByteSinkINSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcE@Base 4.0.4 +#MISSING: 4.0.4-5+b1# _ZTVN6icu_6314StringByteSinkINSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcE@Base 4.0.4 plugwash@thinkpad:~$ Decoding these with c++filt -n goves typeinfo for icu_63::StringByteSink, std::allocator > > typeinfo name for icu_63::StringByteSink, std::allocator > > vtable for icu_63::StringByteSink, std::allocator > > These look like ICU template instantiations to me and seem unlikely to be part of the public interface of zimlib. If I was the maintainer I would probablly just mark them as optional.
Bug#962381: gqrx-sdr: gqrx segmentation fault at start time in testing
On Sun, 07 Jun 2020 10:36:54 +0200 Antonio Radici wrote: > gqrx does not start in testing, this renders the package unusable. I'm sorry to hear this. I noticed the -b3 version get upgraded today too, but it works for me when I start it (I have a box tracking testing, so no chroot here.) > > The problem is reproducible by spinning up a testing chroot (as of > today) and trying to start gqrx gqrx without hardware can be fragile. For that there are run time arguments. `gqrx --reset` and `gqrx --edit` handle initial configuration problems. Does it then work for you selecting the input device doing `gqrx --edit` ? What device are you trying to use? Does your chroot expose it correctly and with the right permissions? -Maitland
Bug#962402: haskell-text-icu: FTBFS on ppc64el and s390x: toEnum{BlockCode}: tag (302) is outside of enumeration's range (0,280)
Source: haskell-text-icu
Version: 0.7.0.1-13
Severity: serious
Tags: ftbfs sid bullseye
Justification: fails to build from source (but built successfully in the past)
haskell-text-icu failed to build on ppc64el and s390x:
| t_blockCode: [Failed]
| *** Failed! (after 25 tests):
| Exception:
| toEnum{BlockCode}: tag (302) is outside of enumeration's range (0,280)
| CallStack (from HasCallStack):
| error, called at Data/Text/ICU/Char.hsc:420:17 in
text-icu-0.7.0.1-HrPKp64TYdw7vXJENJMEzR:Data.Text.ICU.Char
| '\200806'
| (used seed -154261753971613436)
See
https://buildd.debian.org/status/fetch.php?pkg=haskell-text-icu&arch=ppc64el&ver=0.7.0.1-13&stamp=1591383958&raw=0
Cheers
--
Sebastian Ramacher
signature.asc
Description: PGP signature
Bug#962190: primer3: please disable Big Endian tests on autopkgtests too
On Thu, Jun 04, 2020 at 12:47:24PM +0200, Gianfranco Costamagna wrote: > Source: primer3 > Version: 2.4.0-2 > Severity: serious > > Hello, can you please apply the same on autopkgtests? now autopkgtests > failures are considered RC buggy > > something like this might work: >... Running tests is pointless when the only "fix" for failing tests is to disable tests until the build/autopkgtest succeeds. Either the package or the test is broken on big endian. Could an s390x porter (Cc added) please take a look? Thanks Adrian
Processed: found 962205 in 1.2.4-1
Processing commands for cont...@bugs.debian.org: > found 962205 1.2.4-1 Bug #962205 [buildstream] buildstream: Missing dependency on bubblewrap Marked as found in versions buildstream/1.2.4-1. > thanks Stopping processing here. Please contact me if you need assistance. -- 962205: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=962205 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#962399: vmdb2 FTBFS: help2man: can't get `--help' info from vmdb2
Source: vmdb2 Version: 0.16-1 Severity: serious Tags: ftbfs https://buildd.debian.org/status/fetch.php?pkg=vmdb2&arch=all&ver=0.16-1&stamp=1591514624&raw=0 ... debian/rules override_dh_installman make[1]: Entering directory '/<>' [ ! -e vmdb2.1 ] help2man -N vmdb2 -i debian/vmdb2.1.in > debian/vmdb2.1 help2man: can't get `--help' info from vmdb2 Try `--no-discard-stderr' if option outputs to stderr make[1]: *** [debian/rules:18: override_dh_installman] Error 127
Bug#933128: libparse-debianchangelog-perl: Unsuitable for Bullseye unless someone becomes upstream
Hi, intrigeri wrote: > I did not dare proposing this course of action so far because the > notes from our BoF at DebConf19 are a bit ambiguous about whether we > decided to remove the package from sid, in addition to removing it > from testing. I wasn't at the BoF, but was opposing rather strongly afterwards since I was not aware that libdpkg-dev is partially a fork and provides the same functionality. (And I didn't want to loose the changelog parsing functionality in aptitude.) Since Guillem cleared up this and even provided a patch for aptitude (which is applied and in testing for a week or two), I changed my opinion on this topic completely. > If another team member +1's the package removal, I'll happily proceed. Seconded. :-) Regards, Axel -- ,''`. | Axel Beckert , https://people.debian.org/~abe/ : :' : | Debian Developer, ftp.ch.debian.org Admin `. `' | 4096R: 2517 B724 C5F6 CA99 5329 6E61 2FF9 CD59 6126 16B5 `-| 1024D: F067 EA27 26B9 C3FC 1486 202E C09E 1D89 9593 0EDE signature.asc Description: PGP signature
Processed: found 956285 in 1.1.1-1
Processing commands for cont...@bugs.debian.org: > found 956285 1.1.1-1 Bug #956285 [libtorrent-rasterbar] Problems identified in debian/copyright There is no source info for the package 'libtorrent-rasterbar' at version '1.1.1-1' with architecture '' Unable to make a source version for version '1.1.1-1' Marked as found in versions 1.1.1-1. > thanks Stopping processing here. Please contact me if you need assistance. -- 956285: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=956285 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: Fixed in 3.10.4
Processing commands for cont...@bugs.debian.org: > forwarded 959439 https://github.com/supercollider/supercollider/pull/4612 Bug #959439 [supercollider] FTBFS with Boost 1.71 Set Bug forwarded-to-address to 'https://github.com/supercollider/supercollider/pull/4612'. > tags 959439 fixed-upstream Bug #959439 [supercollider] FTBFS with Boost 1.71 Added tag(s) fixed-upstream. > thanks Stopping processing here. Please contact me if you need assistance. -- 959439: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=959439 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: Fixed upstream
Processing commands for cont...@bugs.debian.org: > forwarded 962069 > https://github.com/synfig/synfig/commit/dedb2f7f82a04c0cb3aad462bbe055412f3f5e18 Bug #962069 [src:synfig] synfig: FTBFS with icu 67 Set Bug forwarded-to-address to 'https://github.com/synfig/synfig/commit/dedb2f7f82a04c0cb3aad462bbe055412f3f5e18'. > tags 962069 fixed-upstream patch Bug #962069 [src:synfig] synfig: FTBFS with icu 67 Added tag(s) fixed-upstream and patch. > thanks Stopping processing here. Please contact me if you need assistance. -- 962069: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=962069 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: bug 954711 is forwarded to https://git.ircad.fr/sight/sight/-/issues/462
Processing commands for cont...@bugs.debian.org: > forwarded 954711 https://git.ircad.fr/sight/sight/-/issues/462 Bug #954711 [sight] FTBFS with Boost 1.71 Changed Bug forwarded-to-address to 'https://git.ircad.fr/sight/sight/-/issues/462' from 'Flavien Bridault '. > thanks Stopping processing here. Please contact me if you need assistance. -- 954711: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=954711 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#962390: aoflagger FTBFS with boost 1.71
Source: aoflagger Version: 2.15.0-1 Severity: serious Tags: ftbfs patch fixed-upstream Forwarded: https://sourceforge.net/p/aoflagger/code/ci/1b8a46d70650bf59320f8a0c9371e619ac40/ Control: block 961995 by -1 After the #960331 fix it failed with: ... -- Found PythonLibs: /usr/lib/x86_64-linux-gnu/libpython3.8.so (found suitable version "3.8.3", minimum required is "3") -- Found PythonInterp: /usr/bin/python3.8 (found version "3.8.3") -- Using python version 3.8.3 CMake Error at /usr/share/cmake-3.16/Modules/FindPackageHandleStandardArgs.cmake:146 (message): Could NOT find Boost (missing: python3 numpy3) (found suitable version "1.71.0", minimum required is "1.55.0") Call Stack (most recent call first): /usr/share/cmake-3.16/Modules/FindPackageHandleStandardArgs.cmake:393 (_FPHSA_FAILURE_MESSAGE) /usr/share/cmake-3.16/Modules/FindBoost.cmake:2179 (find_package_handle_standard_args) CMakeLists.txt:34 (find_package) -- Configuring incomplete, errors occurred!
Processed: aoflagger FTBFS with boost 1.71
Processing control commands: > block 961995 by -1 Bug #961995 [release.debian.org] transition: boost-defaults 961995 was blocked by: 953873 962070 962173 955581 959480 960416 960414 960422 962251 960385 960500 960427 962253 962286 962252 953871 960421 962288 959479 960331 962086 960381 959573 960418 960383 962287 954711 960426 960413 958156 962229 960424 948281 960412 948127 948407 960378 954649 949837 959439 954351 955579 948122 959463 959417 959437 954648 961995 was not blocking any bugs. Added blocking bug(s) of 961995: 962390 -- 961995: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=961995 962390: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=962390 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#962368: frogatto-data: Source-only upload not automatically built for non-free packages
On Sat, 06 Jun 2020 at 20:22:28 -0400, Boyuan Yang wrote: > Martin Quinson 于2020年6月6日周六 下午7:11写道： > > In the meanwhile, I'll do a source+binary upload of the package. > > This should fall back to the old behavior and not introduce new > problems. I have no idea if britney would influence testing migration > though (probably not since this is of non-free). The restriction that prevents testing migration for binaries built by the uploader does not apply to non-free, precisely because not every non-free package is autobuildable. I'm not sure whether contrib behaves like main, or like non-free (but everything directly shipped in a contrib source/binary package is Free Software, so their autobuilding is unrestricted, making source-only uploads a safe default). smcv
Processed: Forwarded
Processing commands for cont...@bugs.debian.org: > forwarded 960426 https://github.com/svgpp/svgpp/issues/79 Bug #960426 [src:svgpp] svgpp: FTBFS with boost 1.71 Set Bug forwarded-to-address to 'https://github.com/svgpp/svgpp/issues/79'. > thanks Stopping processing here. Please contact me if you need assistance. -- 960426: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=960426 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#960426: Forwarded
forwarded 960426 https://github.com/svgpp/svgpp/issues/79 thanks
Bug#934458: linkchecker-gui: Fails to start at all
Hello Paolo, I just saw your message. Please, next time send your reply also to 934458-submit...@bugs.debian.org, because the answer to the bugs are not forwarded to the submitter, unfortunately. I have python-xdg installed, but this does not change anything: ii python-xdg 0.25-5 all Python 2 library to access freedesktop.org standards Anything else I can try? (Unfortunately I don't speak python). I see that in the PTS linkchecker(-gui) does not look very well. I put the current Maintainer, Antoine, in CC, maybe he (she?) can shed some light on the current support status of linkchecker? (Or should I look for another tool?) Greetings Helge -- Dr. Helge Kreutzmann deb...@helgefjell.de Dipl.-Phys. http://www.helgefjell.de/debian.php 64bit GNU powered gpg signed mail preferred Help keep free software "libre": http://www.ffii.de/ signature.asc Description: PGP signature
Bug#962381: gqrx-sdr: gqrx segmentation fault at start time in testing
Package: gqrx-sdr Version: 2.12.1-1+b3 Severity: grave Justification: renders package unusable gqrx does not start in testing, this renders the package unusable. The problem is reproducible by spinning up a testing chroot (as of today) and trying to start gqrx This is the stacktrace: *** Thread 1 "gqrx" received signal SIGSEGV, Segmentation fault. 0x555f5a52 in boost::system::error_category::equivalent(boost::system::error_code const&, int) const () (gdb) thread apply all bt Thread 3 (Thread 0x7fffecc54700 (LWP 1745241)): #0 0x7599cb7f in __GI___poll (fds=0x7fffe00029e0, nfds=3, timeout=-1) at ../sysdeps/unix/sysv/linux/poll.c:29 #1 0x736847fe in ?? () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7368491f in g_main_context_iteration () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x768637c1 in QEventDispatcherGlib::processEvents(QFlags) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #4 0x7680c6db in QEventLoop::exec(QFlags) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #5 0x7664d6f1 in QThread::exec() () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #6 0x7fffefe724e6 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5DBus.so.5 #7 0x7664e872 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #8 0x77cd4f27 in start_thread (arg=) at pthread_create.c:479 #9 0x759a731f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 2 (Thread 0x7fffef132700 (LWP 1745240)): #0 0x7599cb7f in __GI___poll (fds=0x7fffef131828, nfds=1, timeout=-1) at ../sysdeps/unix/sysv/linux/poll.c:29 #1 0x730cfd02 in ?? () from /usr/lib/x86_64-linux-gnu/libxcb.so.1 #2 0x730d198a in xcb_wait_for_event () from /usr/lib/x86_64-linux-gnu/libxcb.so.1 #3 0x7fffeffabca0 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5XcbQpa.so.5 #4 0x7664e872 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #5 0x77cd4f27 in start_thread (arg=) at pthread_create.c:479 #6 0x759a731f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 1 (Thread 0x703e8c80 (LWP 1745239)): #0 0x555f5a52 in boost::system::error_category::equivalent(boost::system::error_code const&, int) const () #1 0x76331e8f in boost::asio::detail::posix_mutex::posix_mutex() () from /usr/lib/x86_64-linux-gnu/libgnuradio-blocks.so.3.8.1 #2 0x763329c7 in boost::asio::io_context::io_context() () from /usr/lib/x86_64-linux-gnu/libgnuradio-blocks.so.3.8.1 #3 0x7635ac5c in ?? () from /usr/lib/x86_64-linux-gnu/libgnuradio-blocks.so.3.8.1 #4 0x7635ad39 in gr::blocks::udp_sink::make(unsigned long, std::__cxx11::basic_string, std::allocator > const&, int, int, bool) () from /usr/lib/x86_64-linux-gnu/libgnuradio-blocks.so.3.8.1 #5 0x55641ecc in udp_sink_f::udp_sink_f() () #6 0x556425ef in make_udp_sink_f() () #7 0x556122aa in receiver::receiver(std::__cxx11::basic_string, std::allocator >, std::__cxx11::basic_string, std::allocator >, unsigned int) () #8 0x55605cd0 in MainWindow::MainWindow(QString, bool, QWidget*) () #9 0x555e9f57 in main () *** -- System Information: Debian Release: bullseye/sid APT prefers testing APT policy: (500, 'testing') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 5.6.0-2-amd64 (SMP w/4 CPU cores) Kernel taint flags: TAINT_FIRMWARE_WORKAROUND Locale: LANG=en_IE.utf8, LC_CTYPE=en_IE.utf8 (charmap=UTF-8), LANGUAGE=en_IE.utf8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages gqrx-sdr depends on: ii libboost-program-options1.71.0 1.71.0-6+b2 ii libc6 2.30-8 ii libgcc-s1 10.1.0-3 ii libgnuradio-analog3.8.1 3.8.1.0-1+b3 ii libgnuradio-blocks3.8.1 3.8.1.0-1+b3 ii libgnuradio-digital3.8.13.8.1.0-1+b3 ii libgnuradio-fft3.8.13.8.1.0-1+b3 ii libgnuradio-filter3.8.1 3.8.1.0-1+b3 ii libgnuradio-osmosdr0.2.00.2.0-2+b3 ii libgnuradio-pmt3.8.13.8.1.0-1+b3 ii libgnuradio-runtime3.8.13.8.1.0-1+b3 ii liblog4cpp5v5 1.1.3-1 ii libpulse0 13.0-5 ii libqt5core5a5.12.5+dfsg-10+b1 ii libqt5gui5 5.12.5+dfsg-10+b1 ii libqt5network5 5.12.5+dfsg-10+b1 ii libqt5svg5 5.12.5-2 ii libqt5widgets5 5.12.5+dfsg-10+b1 ii libstdc++6 10.1.0-3 ii pulseaudio 13.0-5 gqrx-sdr recommends no packages. gqrx-sdr suggests no packages. -- no debconf information
Bug#962319: libextutils-hascompiler-perl: test failures perl 5.30.3-2
On Sat, Jun 06, 2020 at 10:28:49AM +0300, Niko Tyni wrote:
> Package: libextutils-hascompiler-perl
> Version: 0.021-2
> Severity: serious
>
> This package fails its test suite with perl 5.30.3-2 from unstable.
> With perl 5.30.3-2, #798626 is fixed and $Config{useshrplib} now
> correctly indicates that static linking is supported. However, the
> ExtUtils::HasCompiler check does not actually link, so it fails to detect
> that libperl.a is missing. ExtUtils::MakeMaker still fails in the same
> way, so the results now disagree.
I reinstated $Config{useshrplib}='true' for perl 5.30.3-4 because other
projects were checking that to find out whether a shared libperl is
available.
So the fix I made in libextutils-hascompiler-perl to close this bug is
no longer necessary. However, I still think it's the right thing to do
- given we support static builds, it's good for ExtUtils::HasCompiler
to signal that. So I'm not reverting it unless we find out it causes
problems.
--
Niko Tyni nt...@debian.org
Bug#933128: libparse-debianchangelog-perl: Unsuitable for Bullseye unless someone becomes upstream
Hi, gregor herrmann (2020-05-22): > On Fri, 22 May 2020 09:58:12 +0200, intrigeri wrote: > >> So, once aptitude >= 0.8.13-1 has migrated to testing, we'll need to >> ask (presumably the release team) for libparse-debianchangelog-perl to >> lose its "key package" status, so the autoremoval machinery can remove >> it from testing due to this very RC bug. > > Unless we go directly for an RM;RoM bug, then it will be removed from > testing when it's gone from unstable. Indeed. This would be my preferred option: it's simpler for everyone involved, it communicates the maintenance status more clearly, and it avoids confusion that could lead to new reverse-dependencies to be uploaded. I did not dare proposing this course of action so far because the notes from our BoF at DebConf19 are a bit ambiguous about whether we decided to remove the package from sid, in addition to removing it from testing. If another team member +1's the package removal, I'll happily proceed. Cheers!
