Date: prev next · Thread: first prev next last
January 2026 Archives by date, by thread · List index


Tinderbox on Master for Linux - Build # 67161 - Fixed:


Check console output at https://ci.libreoffice.org/job/lo_tb_master_linux/67161/ to view the 
results.

Changes for Build #67160
No changes

Changes for Build #67161
[Tor Lillqvist] No Noto font in configury here

[Tor Lillqvist] Add some DISABLE_DYNLOADING ifdefs to osl/w32, as for unx

[Tor Lillqvist] Skip private system fonts found by fontcofig on macOS

[Tor Lillqvist] Don't fail assertion in Task::~Task() if LibreOfficeKit is active

[Tor Lillqvist] Make the windowsfonts.patch apply again

[Tor Lillqvist] Package the fonts.conf file and the conf.d folder also for Windows

[Tor Lillqvist] Don't package conflicting and pointless fontconfig configuration files

[Tor Lillqvist] Don't use sub-pixel rendering in WASM and CODA-W

[Tor Lillqvist] Look for fonts also in WINDOWSUSERFONTDIR

[Tor Lillqvist] Make also fonts installed from the Microsoft Store show up in CODA-W

[Tor Lillqvist] Obey --enable-msvc-debug-runtime when building harfbuzz
-- 
To unsubscribe e-mail to: libreoffice-ci+unsubscribe@global.libreoffice.org
Problems? https://www.libreoffice.org/get-help/mailing-lists/how-to-unsubscribe/
Posting guidelines + more: https://wiki.documentfoundation.org/Netiquette
List archive: https://listarchives.libreoffice.org/global/libreoffice-ci/
Privacy Policy: https://www.documentfoundation.org/privacy

Context


Privacy Policy | Impressum (Legal Info) | Copyright information: Unless otherwise specified, all text and images on this website are licensed under the Creative Commons Attribution-Share Alike 3.0 License. This does not include the source code of LibreOffice, which is licensed under the Mozilla Public License (MPLv2). "LibreOffice" and "The Document Foundation" are registered trademarks of their corresponding registered owners or are in actual use as trademarks in one or more countries. Their respective logos and icons are also subject to international copyright laws. Use thereof is explained in our trademark policy.