[Pkg-puppet-devel] Bug#962320: facter crashes with "free(): invalid pointer"

[Adrian Bunk]

Control: reassign -1 src:boost1.71
Control: reassign 962527 src:boost1.71
Control: reassign 962523 src:boost1.71
Control: forcemerge -1 962527 962523
Control: affects -1 libfacter3.11.0 puppet facter
Control: retitle -1 libboost-*1.71.0 packages need Breaks: libboost-*1.67.0

On Sat, Jun 06, 2020 at 09:31:47AM +0200, Vincent Bernat wrote:
> Package: libfacter3.11.0
> Version: 3.11.0-4.1
> Severity: grave
>...
> Versions of packages libfacter3.11.0 depends on:
>...
> ii  libboost-filesystem1.67.0                          1.67.0-18
> ii  libboost-locale1.67.0                              1.67.0-18
> ii  libboost-program-options1.67.0                     1.67.0-18
> ii  libboost-regex1.67.0 [libboost-regex1.67.0-icu63]  1.67.0-18
> ii  libboost-system1.67.0                              1.67.0-18
>...
> ii  libcpp-hocon0.1.7                                  0.1.7-1+b2
>...
> ii  libleatherman1.4.2                                 1.4.2+dfsg-2+b1
>...

This ends up one binary using both Boost 1.67 and Boost 1.71 at the
same time, which is not working:
$ ldd /usr/bin/facter | grep boost
        libboost_program_options.so.1.67.0 => /lib/x86_64-linux-gnu/libboost_program_options.so.1.67.0 (0x00007f8294a63000)
        libboost_locale.so.1.67.0 => /lib/x86_64-linux-gnu/libboost_locale.so.1.67.0 (0x00007f8294463000)
        libboost_system.so.1.67.0 => /lib/x86_64-linux-gnu/libboost_system.so.1.67.0 (0x00007f829445c000)
        libboost_filesystem.so.1.67.0 => /lib/x86_64-linux-gnu/libboost_filesystem.so.1.67.0 (0x00007f829443e000)
        libboost_regex.so.1.67.0 => /lib/x86_64-linux-gnu/libboost_regex.so.1.67.0 (0x00007f8294308000)
        libboost_date_time.so.1.67.0 => /lib/x86_64-linux-gnu/libboost_date_time.so.1.67.0 (0x00007f8293c80000)
        libboost_chrono.so.1.67.0 => /lib/x86_64-linux-gnu/libboost_chrono.so.1.67.0 (0x00007f8293c75000)
        libboost_locale.so.1.71.0 => /lib/x86_64-linux-gnu/libboost_locale.so.1.71.0 (0x00007f8293b98000)
        libboost_thread.so.1.71.0 => /lib/x86_64-linux-gnu/libboost_thread.so.1.71.0 (0x00007f8293b6c000)
        libboost_thread.so.1.67.0 => /lib/x86_64-linux-gnu/libboost_thread.so.1.67.0 (0x00007f8293b3d000)
        libboost_log.so.1.67.0 => /lib/x86_64-linux-gnu/libboost_log.so.1.67.0 (0x00007f82934e0000)
        libboost_log_setup.so.1.67.0 => /lib/x86_64-linux-gnu/libboost_log_setup.so.1.67.0 (0x00007f8293431000)
        libboost_atomic.so.1.67.0 => /lib/x86_64-linux-gnu/libboost_atomic.so.1.67.0 (0x00007f829342c000)
$

Short-term this should be fixed when the following bugs are fixed
resulting in recompilation with Boost 1.71:
#960416 leatherman: FTBFS with boost 1.71
#959573 facter FTBFS with yaml-cpp 0.6.3

For avoiding similar problems for people upgrading from buster,
it would be good if for both 1.71 and whatever version of Boost
will be released in Buster the library packages will add a Breaks:
on the corresponding libboost-*1.67.0 package.

cu
Adrian