It's in 15.0 with all the current patches.

On Sat, May 9, 2026 at 10:46 AM Greg Tourte <[email protected]> wrote:

> I cannot reproduce this either, neither on -stable nor on -current.
>
> On Sat, 9 May 2026 at 17:25, Willy Sudiarto Raharjo <
> [email protected]> wrote:
>
>> >Botan is not building for me:
>> >
>> >cd . && ln -fs libbotan-3.so.12 libbotan-3.so.12.12.0
>> >"/usr/bin/python3" "src/scripts/build_docs.py" --build-dir="build"
>> >   INFO: Starting sphinx-build -q -c src/configs/sphinx -j auto -W
>> >--keep-going -b html doc build/docs/handbook
>> >Could not import furo theme; falling back to agago
>> >/tmp/SBo/Botan-3.12.0/doc/api_ref/pbkdf.rst:173: WARNING: Could not lex
>> >literal_block as "cpp". Highlighting skipped.
>> >  ERROR: Error running sphinx-build -q -c src/configs/sphinx -j auto -W
>> >--keep-going -b html doc build/docs/handbook
>> >make: *** [Makefile:53: build/doc.stamp] Error 1
>> >A failure occurred while building Botan:
>> >  Botan.SlackBuild returned non-zero.
>>
>>
>> It built fine on our CI test
>> https://github.com/SlackBuildsOrg/slackbuilds/pull/15546
>>
>> did you test this on -current or -stable, just to make sure
>>
>>
>> --
>> Willy Sudiarto Raharjo
>> _______________________________________________
>> SlackBuilds-users mailing list
>> [email protected]
>> https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
>> Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
>> FAQ - https://slackbuilds.org/faq/
>>
>> _______________________________________________
> SlackBuilds-users mailing list
> [email protected]
> https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
> Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
> FAQ - https://slackbuilds.org/faq/
>
>
_______________________________________________
SlackBuilds-users mailing list
[email protected]
https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
FAQ - https://slackbuilds.org/faq/

Reply via email to