Your message dated Wed, 16 Dec 2020 23:00:26 +0100
with message-id
<CALF6qJ=v-owqhn1srwkyzjp_6kejkrzrf31leknck7deoeo...@mail.gmail.com>
and subject line Close
has caused the Debian Bug report #975660,
regarding scram: FTBFS against boost_1.74
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.)
--
975660: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=975660
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: scram
Version: 0.16.2-1
Severity: important
Tags: ftbfs
User: team+bo...@tracker.debian.org
Usertags: boost174
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512
Dear maintainer,
it was discovered that your package failed to build
against boost_1.74. Logs can be found here [1]. Most relevant
part is probably this:
[ 19%] Building CXX object src/CMakeFiles/scram.dir/config.cc.o
cd /<<PKGBUILDDIR>>/obj-x86_64-linux-gnu/src && /usr/bin/c++ -DBOOST_ALL_NO_LIB
-DBOOST_FILESYSTEM_DYN_LINK -DBOOST_PROGRAM_OPTIONS_DYN_LINK
-DBOOST_RANDOM_DYN_LINK -DBOOST_SYSTEM_DYN_LINK
-DPROJECT_SOURCE_DIR=\"/<<PKGBUILDDIR>>\" -Dscram_EXPORTS
-I/<<PKGBUILDDIR>>/obj-x86_64-linux-gnu/src -I/<<PKGBUILDDIR>>/src
-I/<<PKGBUILDDIR>> -isystem /usr/include/libxml2 -g -O2
-fdebug-prefix-map=/<<PKGBUILDDIR>>=. -fstack-protector-strong -Wformat
-Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -fno-new-ttp-matching
-O3 -DNDEBUG -fPIC -std=c++17 -o CMakeFiles/scram.dir/config.cc.o -c
/<<PKGBUILDDIR>>/src/config.cc
In file included from /<<PKGBUILDDIR>>/src/settings.cc:27:
/<<PKGBUILDDIR>>/src/settings.cc: In member function ‘scram::core::Settings&
scram::core::Settings::algorithm(std::string_view)’:
/<<PKGBUILDDIR>>/src/error.h:39:40: error:
‘BOOST_THROW_EXCEPTION_CURRENT_FUNCTION’ was not declared in this scope
39 | throw err <<
::boost::throw_function(BOOST_THROW_EXCEPTION_CURRENT_FUNCTION) \
It is planned to push boost_1.74 as the default version in Debian/Bullseye.
[1]
http://qa-logs.debian.net/2020/10/27-boost/boost/scram_0.16.2-1_unstable_boost.log
Best regards
Anton
- -- System Information:
Debian Release: bullseye/sid
APT prefers testing
APT policy: (500, 'testing')
Architecture: amd64 (x86_64)
Foreign Architectures: i386
Kernel: Linux 5.9.0-1-amd64 (SMP w/8 CPU threads)
Kernel taint flags: TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
-----BEGIN PGP SIGNATURE-----
iQJFBAEBCgAvFiEEu71F6oGKuG/2fnKF0+Fzg8+n/wYFAl+9Y0wRHGdsYWRrQGRl
Ymlhbi5vcmcACgkQ0+Fzg8+n/wZ/vQ/+I16O0GIcjOiVDon3vjDctFUItgC3ynuq
ceER0Hu6uHZxn3SWUzhQqCc4cVVp3wTXIELn6iYc3Ekv2H2ZgZYKP9sF6F5u6Ue3
7PxElbjUBZz/SQjMNyRALWZY/ZSFqlLr6iCZ9YIYA9Di/bE8y6gBNMdmczWG32yy
umvpDH3sVd1S0ORLzvuCANfrQb6YZO5SFZYlE6zvqaIdXqbTICGLyx4QLMYIDE8e
07TcTPz61htFCfz55M6KUAtgO0ihPS0dCu19rp+8Gpf2n2PIZbytvtFWGZZPlAxy
Bz9aY4PFqJKFs454hLb6SXNuF59QhNOCCg97+jxmqIy3OqyrEnQqv5RvwkgDoxsq
2rjbUGZMnWaUyb5tJuc3WKBUBvmIYcg0ciZYKDNwAhy2ECBRZvRRKXWT29tHS8Z3
3A37OcIbwx/Nre1x6ayyS8T5j3iHnTq5s4t7CwqOJWRHovyFWRTU7vCf51dDBTe6
8vxhrRzCv2UFfeDIOFnN6zNFGm+n+q5wWj/YVUHGGzUSbGa82+v7iQL3/+iI9pdP
1CYmueriQAuyiqsktxCASiYCuj+vbHgmTklWfnzeRdpEg3lE14A2sC7sHH8/KAYt
kuGW2JO+lZAuZKUB5ZLVEc4uumdL+XzpqcprrpJZNDgeS6nrdKWJE7IMNFddReAK
JrxPYAPm+fo=
=H+2c
-----END PGP SIGNATURE-----
--- End Message ---
--- Begin Message ---
fixed 975660 0.16.2-2
thanks
--- End Message ---
--
debian-science-maintainers mailing list
debian-science-maintainers@alioth-lists.debian.net
https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/debian-science-maintainers
