Your message dated Fri, 23 Nov 2018 09:01:27 +0200
with message-id <8c28f96e-1775-1154-3136-6937298d5...@debian.org>
and subject line Fixed
has caused the Debian Bug report #914054,
regarding calamares FTBFS with boost 1.67
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.)
--
914054: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=914054
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: calamares
Version: 3.2.2-1
Severity: serious
Tags: ftbfs
https://buildd.debian.org/status/package.php?p=calamares&suite=sid
...
cd /<<PKGBUILDDIR>>/obj-x86_64-linux-gnu/src/libcalamares && /usr/bin/c++
-DDLLEXPORT_PRO -DPYTHONQT_USE_RELEASE_PYTHON_FALLBACK -DQT_CORE_LIB
-DQT_NO_DEBUG -DQT_SHARED -DQT_SHAREDPOINTER_TRACK_POINTERS
-DQT_STRICT_ITERATORS -Dcalamares_EXPORTS
-I/<<PKGBUILDDIR>>/obj-x86_64-linux-gnu/src/libcalamares/calamares_autogen/include
-I/<<PKGBUILDDIR>>/src -I/<<PKGBUILDDIR>>/src/libcalamares
-I/<<PKGBUILDDIR>>/src/libcalamaresui
-I/<<PKGBUILDDIR>>/obj-x86_64-linux-gnu/src
-I/<<PKGBUILDDIR>>/obj-x86_64-linux-gnu/src/libcalamares
-I/<<PKGBUILDDIR>>/obj-x86_64-linux-gnu/src/libcalamaresui
-I/usr/include/python3.6m -I/usr/include/PythonQt5 -isystem
/usr/include/x86_64-linux-gnu/qt5 -isystem
/usr/include/x86_64-linux-gnu/qt5/QtCore -isystem
/usr/lib/x86_64-linux-gnu/qt5/mkspecs/linux-g++ -g -O2
-fdebug-prefix-map=/<<PKGBUILDDIR>>=. -fstack-protector-strong -Wformat
-Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -Wl,--no-undefined
-Wl,--fatal-warnings -Wnon-virtual-dtor -Woverloaded-virtual
-Werror=return-type -fdiagnostics-color=auto -fPIC -fPIC -std=gnu++14 -o
CMakeFiles/calamares.dir/GlobalStorage.cpp.o -c
/<<PKGBUILDDIR>>/src/libcalamares/GlobalStorage.cpp
In file included from /usr/include/yaml-cpp/node/iterator.h:13,
from /usr/include/yaml-cpp/node/impl.h:11,
from /usr/include/yaml-cpp/yaml.h:17,
from /<<PKGBUILDDIR>>/src/modules/test_conf.cpp:29:
/usr/include/yaml-cpp/node/detail/iterator.h: In member function 'void
YAML::detail::iterator_base<V>::increment()':
/usr/include/yaml-cpp/node/detail/iterator.h:48:54: error: 'next' is not a
member of 'boost'
void increment() { this->base_reference() = boost::next(this->base()); }
^~~~
/usr/include/yaml-cpp/node/detail/iterator.h:48:54: note: suggested
alternatives:
In file included from /usr/include/c++/8/bits/stl_algobase.h:66,
from /usr/include/c++/8/bits/char_traits.h:39,
from /usr/include/c++/8/ios:40,
from /usr/include/c++/8/ostream:38,
from /usr/include/c++/8/iostream:39,
from /<<PKGBUILDDIR>>/src/modules/test_conf.cpp:27:
/usr/include/c++/8/bits/stl_iterator_base_funcs.h:213:5: note: 'std::next'
next(_InputIterator __x, typename
^~~~
In file included from /usr/include/boost/mpl/next.hpp:17,
from /usr/include/boost/mpl/bind.hpp:25,
from /usr/include/boost/mpl/lambda.hpp:18,
from /usr/include/boost/mpl/apply.hpp:25,
from /usr/include/boost/iterator/iterator_facade.hpp:36,
from /usr/include/yaml-cpp/node/detail/node_iterator.h:12,
from /usr/include/yaml-cpp/node/detail/iterator.h:12,
from /usr/include/yaml-cpp/node/iterator.h:13,
from /usr/include/yaml-cpp/node/impl.h:11,
from /usr/include/yaml-cpp/yaml.h:17,
from /<<PKGBUILDDIR>>/src/modules/test_conf.cpp:29:
/usr/include/boost/mpl/next_prior.hpp:29:8: note: 'boost::mpl::next'
struct next
^~~~
make[3]: *** [src/modules/CMakeFiles/test_conf.dir/build.make:66:
src/modules/CMakeFiles/test_conf.dir/test_conf.cpp.o] Error 1
--- End Message ---
--- Begin Message ---
Fixed by rebuilding against newer version of yamlk-cpp that was recently
uploaded in unstable.
--- End Message ---
