Il 13/06/20 11:05, Giovanni Mascellani ha scritto:
> No problems in line of principle, but I am not sure I understand what
> would this solve: the conflict between two different versions of Boost
> arises when the same executable links against both (through different
> dependencies). There is no
Hi,
Il 09/06/20 17:06, Adrian Bunk ha scritto:
> 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.
Processing control commands:
> reassign -1 src:boost1.71
Bug #962320 [libfacter3.11.0] facter crashes with "free(): invalid pointer"
Bug reassigned from package 'libfacter3.11.0' to 'src:boost1.71'.
No longer marked as found in versions facter/3.11.0-4.1.
Ignoring request to alter f
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
Package: libfacter3.11.0
Version: 3.11.0-4.1
Severity: grave
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Hey!
#0 __GI_raise (sig=sig@entry=6) at ../sysdeps/unix/sysv/linux/raise.c:50
set = {__val = {0, 1431634051, 94476679444720, 139623352393688, 0,
94476679915560, 94476680133744,
5 matches
Mail list logo