Control: reassign -1 src:boost1.83
Control: affects -1 swift-im
Control: tags -1 fixed-upstream patch
Control: retitle -1 boost1.83: Boost.Signals2 causes FTBFS


Hi,

This seems to be a boost bug:
https://github.com/boostorg/signals2/issues/70

-- 
tobi


On Thu, 16 Nov 2023 22:08:39 +0100 gl...@debian.org wrote:
> Source: swift-im
> Version: 5.0~alpha2.145.g12d031cf8+dfsg-3
> Severity: normal
> User: gl...@debian.org
> Usertags: boost183 ftbfs-boost183-transition
> 
> Hi,
> 
> we are preparing the transition of all libs on the new boost 1.83.
During the
> rebuild of packages against this library it was identified that
probably your
> package fails to build.
> 
> Relevant part (hopefully):
> 
> -----
> 
> /usr/include/boost/function_equal.hpp:17:14: error: no match for
'operator==' (operand types are 'const
boost::reference_wrapper<boost::signals2::signal<void(std::shared_ptr<S
wift::Message>)> >' and 'const
boost::reference_wrapper<boost::signals2::signal<void(std::shared_ptr<S
wift::Message>)> >')
>    17 |   { return f == g; }
>       |            ~~^~~~
> 
> 
> -----
> 
> To reproduce this behavior, you can install  -dev Boost packages from
the
> experimental repository, as shown in the following command:
> 
>   apt install libboost-dev -t experimental
> 
> 
> The full build log is available from:
> https://people.debian.org/~gladk/boost183/libpappsomspp.log
> 
> All bugs filed during this archive rebuild are listed at:
>
https://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=ftbfs-boost183-transition;users=gl...@debian.org
> or:
>
https://udd.debian.org/bugs/?release=na&merged=ign&fnewerval=7&flastmodval=7&fusertag=only&fusertagtag=ftbfs-boost183-transition&fusertaguser=gl...@debian.org&allbugs=1&cseverity=1&ctags=1&caffected=1#results
> 
> 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 are unable to reproduce this, please provide a build log and
diff it
> so that we can identify any relevant changes that may have occurred
in the meantime.
> 
> 
> 

Reply via email to