On Fri, 2026-10-23 at 22:05 +0200, Jeroen Hofstee wrote: > Hello Paul, > > For what it is worth, [1] should do the same for scarthgap / > python3-certifi, > but without porting all new versions back. I don't really mind which > approach > we take. > > [1] > https://github.com/victronenergy/openembedded-core/commit/4b6650b6cf7d5ebcd60a0bd41c7d9bda3a750a21
Hi Jeroen, We do want to follow ca-certificates updates on our stable branches. This has been discussed with Yoann and the TSC before. Failing to keep CA certificates up-to-date can result in inability to connect to services signed by a new cert. There have also been other certificates removed since Scarthgap was released. And lastly we should keep the different copies of the certificate store aligned where we can. Best regards, -- Paul Barker
-=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#248584): https://lists.openembedded.org/g/openembedded-core/message/248584 Mute This Topic: https://lists.openembedded.org/mt/121898134/21656 Group Owner: [email protected] Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub [[email protected]] -=-=-=-=-=-=-=-=-=-=-=-
