This update has been unpushed.

Going to unpush the update, because the newer build includes high CVE fix.

Works fine in all *pkg tools

Regression in bannertopdf function.

Regression in bannertopdf function.

This update has been unpushed.

This update has been unpushed.

LGTM

LGTM!

Unfortunately it looks it was glitch at first - now pidgin asks again for accepting cert with every startup and every network change. It might be crypto-policy issue, but rather be safe than sorry.

The update works in general, certificate dialog did not show up during startup.

The latest rawhide and F41 do not show the issue - I'm unpushing the update, since I will create a new one today with CVE fix.

This update has been unpushed.

Unfortunately there is a regression caught by the testsuite regarding python3 Vim plugin - I looked into it for time and it looks like it was not triggered by the latest Vim changes (I've cloned the upstream project and built the project in VM, and the error has shown up even for patchlevel which previously passed in Fedora - 660) nor Python ones.

There hasn't been Python update in the meantime which could cause this, so I will check buildroots of successful and failing build to see which packages got changed and which can cause it...

This update has been unpushed.

This update has been unpushed.

This update has been unpushed.

This update has been unpushed.

@kparal thanks for letting me know! I'll restart the tests either way, because upstream test suite reports less warn messages than expected, causing the test to fail - this happened several times in the past as well, I'm not able to reproduce it locally and restarting test helps most times...