Christian Lohmaier 5acbd4b5f5 create-mar: flush stdout to see the message when using 2>&1 | tee log ...

in case the script is aborted/fails otherwise and doesn't remove the
lockfile, another attempt to obtain the lock ends up in an endless loop

No problem if the user sees the corresponing messages, but when using
shell redirection of stdout and stderr and trying to tee that to a
logfile, the message is never seen/the buffers are not flushed

So force flushing stdout to have the message show up in the terminal

Change-Id: Ib133b9bc523d9ba2210564f75762258f41415f71
Reviewed-on: https://gerrit.libreoffice.org/c/core/+/182595
Tested-by: Jenkins
Reviewed-by: Xisco Fauli <xiscofauli@libreoffice.org>
Reviewed-by: Christian Lohmaier <lohmaier+LibreOffice@googlemail.com>
(cherry picked from commit 55b13db9f18a945bb5e61e14a462f5770ce99d66)
Reviewed-on: https://gerrit.libreoffice.org/c/core/+/182618

2025-03-07 14:23:36 +01:00

..

create_full_mar.py

tdf#158803 remove unused path.convert_to_unix import

2024-03-28 08:51:01 +01:00

create_partial_update.py

create-mar: flush stdout to see the message when using 2>&1 | tee log

2025-03-07 14:23:36 +01:00

path.py

…

signing.py

…

tools.py

tdf#158803 fix fstring

2024-03-28 08:49:23 +01:00

uncompress_mar.py

…