Backport v2022 <- v2023dev1: Update from debian/bullseye-security

Backport !84 (merged) to v2022

Fixes: https://phabricator.apertis.org/T8519

marked this merge request as draft

marked this merge request as ready

mentioned in merge request rust-cbindgen!11 (merged)

Hehe, as I said in another place, it's preferable to avoid creating new branches when doing a straight merge.

In this case it would even avoid errors: landing this MR as-is would miss 222f4a45 which is the actual commit that was landed in !84 (merged)and got tagged as the release commit. :)

Hah, it's not even that. It seems that v2022 is two security updates behind, and this lands just one. :)

Is it ok to push 0565e486 here?

I will close this MR and directly create MR to merge apertis/v2023dev1 into apertis/v2022 :)

closed