[ClusterLabs] ftime-imposed problems and compatibility going forward (Was: Final Pacemaker 2.0.3 release now available)

Jan Pokorný jpokorny at redhat.com
Tue Nov 26 14:38:37 EST 2019

On 26/11/19 20:30 +0100, Jan Pokorný wrote:
> And yet another, this time late, stay-compatible type of problem with
> pacemaker vs. concurrent changes in build dependencies has popped up,
> this time with Inkscape.  Whenever its 1.0 version is released,
> when with my ask https://github.com/ClusterLabs/pacemaker/pull/1953

sorry, https://gitlab.com/inkscape/inbox/issues/1244, apparently

> refused, the just released version (and equally the older ones) will
> choke when documentation gets prepared (corollary of the respective
> packages incl. Inkscape being around, to begin with).
> Workaround is then to either disable that step of the build process:
>   ./configure --with-brand=
>   ("equals nothing")
> or to apply this patch:
>   https://github.com/ClusterLabs/pacemaker/pull/1953

Jan (Poki)
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 819 bytes
Desc: not available
URL: <https://lists.clusterlabs.org/pipermail/users/attachments/20191126/f7561f80/attachment.sig>

More information about the Users mailing list