On Sun Oct 11, 2026 at 12:19 PM CEST, Peter Marko wrote: > Please drop my libpcre2 series for now.
Ok, I dropped it from stable/wrynose-next. > When trying to create this series for scarthgap and trying to resolve > conflicts I found that pcre2 now committed to do "at least five years" > of maintenance for each release. > https://github.com/PCRE2Project/pcre2/commit/0f85a365a7ab586a39089f4ecdc4f9f6857c043e#diff-599c7525a19150cfd62bfa7bafbf578487389804a4ec3964ffa60d322db9bbfdR22-R44 > > Release branches are available that we could use. > Checking contents of release/10.47 branch, it contains commits which I > picked, however some are squashed with other ones indicating that my > backport was not complete. > For example fix for CVE-2026-89156 now consists of two squashed > commits where I picked only one. > https://github.com/PCRE2Project/pcre2/commit/5528f329f597eabbf1cfd5a1f3b4fa51a8c02d60 > This requires further study before merging. Agreed but this upstream maintenance branch looks - on paper - compatible with our policy. So, this is encouraging. > This also opens second question, similar to one recently asked for > rsync very recently. > May I switch libpcre2 to gif fetcher and update to latest release > branch hash instead of backporting commits? > Or should I rather pick (potentially all) commits from there? > I'd prefer to switch to the git fetcher. I also like the idea of switching to git fetcher. So, I'll happily review a series doing the switch then upgrade along the branch. Thanks! -- Yoann Congal Smile ECS
-=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#247593): https://lists.openembedded.org/g/openembedded-core/message/247593 Mute This Topic: https://lists.openembedded.org/mt/121697589/21656 Group Owner: [email protected] Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub [[email protected]] -=-=-=-=-=-=-=-=-=-=-=-
