Source: lime
Version: 5.1.64+dfsg-2
Severity: serious
Justification: FTBFS
Tags: trixie sid ftbfs
Hi,
During a rebuild of all packages in sid, your package failed to build
on amd64.
Relevant part (hopefully):
> cd /<<PKGBUILDDIR>>/obj-x86_64-linux-gnu/src && /usr/bin/c++ -DBCTBX_STATIC
> -DEC25519_ENABLED -DEC448_ENABLED -DFFI_ENABLED -DLIME_EXPORTS -Dlime_EXPORTS
> -I/<<PKGBUILDDIR>>/include -I/<<PKGBUILDDIR>>/src
> -I/<<PKGBUILDDIR>>/obj-x86_64-linux-gnu -I/usr/include/soci
> -I/usr/lib/jvm/default-java/include -I/usr/lib/jvm/default-java/include/linux
> -g -O2 -ffile-prefix-map=/<<PKGBUILDDIR>>=. -fstack-protector-strong -Wformat
> -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -std=gnu++14 -fPIC
> -Wall -Wuninitialized -Wno-deprecated-declarations
> -Wno-missing-field-initializers -Werror -Wextra -Wno-unused-parameter
> -fno-strict-aliasing -MD -MT src/CMakeFiles/lime.dir/lime_manager.cpp.o -MF
> CMakeFiles/lime.dir/lime_manager.cpp.o.d -o
> CMakeFiles/lime.dir/lime_manager.cpp.o -c
> /<<PKGBUILDDIR>>/src/lime_manager.cpp
> In file included from /<<PKGBUILDDIR>>/src/lime_double_ratchet.hpp:28,
> from /<<PKGBUILDDIR>>/src/lime_double_ratchet.cpp:21:
> /<<PKGBUILDDIR>>/src/lime_settings.hpp:49:24: error: ‘uint16_t’ in namespace
> ‘std’ does not name a type; did you mean ‘wint_t’?
> 49 | constexpr std::uint16_t maxMessageSkip=1024;
> | ^~~~~~~~
> | wint_t
> /<<PKGBUILDDIR>>/src/lime_settings.hpp:54:24: error: ‘uint16_t’ in namespace
> ‘std’ does not name a type; did you mean ‘wint_t’?
> 54 | constexpr std::uint16_t maxMessagesReceivedAfterSkip = 128;
> | ^~~~~~~~
> | wint_t
> /<<PKGBUILDDIR>>/src/lime_settings.hpp:62:24: error: ‘uint16_t’ in namespace
> ‘std’ does not name a type; did you mean ‘wint_t’?
> 62 | constexpr std::uint16_t maxSendingChain=1000;
> | ^~~~~~~~
> | wint_t
> /<<PKGBUILDDIR>>/src/lime_double_ratchet.cpp: In member function ‘void
> lime::DR<Curve>::ratchetEncrypt(const inputContainer&, std::vector<unsigned
> char>&&, std::vector<unsigned char>&, bool)’:
> /<<PKGBUILDDIR>>/src/lime_double_ratchet.cpp:345:45: error: ‘maxSendingChain’
> is not a member of ‘lime::settings’
> 345 | if (m_Ns >= lime::settings::maxSendingChain) { // if
> we reached maximum encryption wuthout DH ratchet step, session becomes
> inactive
> | ^~~~~~~~~~~~~~~
> /<<PKGBUILDDIR>>/src/lime_double_ratchet.cpp: In member function ‘bool
> lime::DR<Curve>::ratchetDecrypt(const std::vector<unsigned char>&, const
> std::vector<unsigned char>&, outputContainer&, bool)’:
> /<<PKGBUILDDIR>>/src/lime_double_ratchet.cpp:389:60: error: ‘maxMessageSkip’
> is not a member of ‘lime::settings’
> 389 | int maxAllowedDerivation =
> lime::settings::maxMessageSkip;
> |
> ^~~~~~~~~~~~~~
> /<<PKGBUILDDIR>>/src/lime_double_ratchet.cpp:413:78: error: ‘maxMessageSkip’
> is not a member of ‘lime::settings’
> 413 | skipMessageKeys(header.PN(),
> lime::settings::maxMessageSkip-header.Ns()); // we must keep header.Ns
> derivations available for the next chain
> |
> ^~~~~~~~~~~~~~
> [ 81%] Building CXX object src/CMakeFiles/lime.dir/lime_ffi.cpp.o
> cd /<<PKGBUILDDIR>>/obj-x86_64-linux-gnu/src && /usr/bin/c++ -DBCTBX_STATIC
> -DEC25519_ENABLED -DEC448_ENABLED -DFFI_ENABLED -DLIME_EXPORTS -Dlime_EXPORTS
> -I/<<PKGBUILDDIR>>/include -I/<<PKGBUILDDIR>>/src
> -I/<<PKGBUILDDIR>>/obj-x86_64-linux-gnu -I/usr/include/soci
> -I/usr/lib/jvm/default-java/include -I/usr/lib/jvm/default-java/include/linux
> -g -O2 -ffile-prefix-map=/<<PKGBUILDDIR>>=. -fstack-protector-strong -Wformat
> -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -std=gnu++14 -fPIC
> -Wall -Wuninitialized -Wno-deprecated-declarations
> -Wno-missing-field-initializers -Werror -Wextra -Wno-unused-parameter
> -fno-strict-aliasing -MD -MT src/CMakeFiles/lime.dir/lime_ffi.cpp.o -MF
> CMakeFiles/lime.dir/lime_ffi.cpp.o.d -o CMakeFiles/lime.dir/lime_ffi.cpp.o -c
> /<<PKGBUILDDIR>>/src/lime_ffi.cpp
> make[5]: *** [src/CMakeFiles/lime.dir/build.make:149:
> src/CMakeFiles/lime.dir/lime_double_ratchet.cpp.o] Error 1
The full build log is available from:
http://qa-logs.debian.net/2023/07/24/lime_5.1.64+dfsg-2_unstable.log
A list of current common problems and possible solutions is available at
http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute!
If you reassign this bug to another package, please mark it as 'affects'-ing
this package. See https://www.debian.org/Bugs/server-control#affects
If you fail to reproduce this, please provide a build log and diff it with mine
so that we can identify if something relevant changed in the meantime.
