Hi Alex, Thanks for your note. I’m working through the remaining downstream recipe changes today which should address the rest of the UNKNOWN_BROKEN recipes.
While looking at it yesterday, the download packages come primarily in two archetypes: 1. Those that replace ‘_’ with ‘-‘ in the source archives 2. Those that leave the ‘_’ ONLY in the archives Given that, I think it’s unlikely there’s a clean fix in the bbclass without a more invasive change to the upstream check logic. I can, however, package all the changes for one-core into a single patchset and submit a v2. That will at least address all the core updates in one fell swoop. Does that sound reasonable? -Derek On Fri, Dec 13, 2024 at 2:28 AM Alexander Kanavin <[email protected]> wrote: > On Thu, 12 Dec 2024 at 19:56, Derek Straka via lists.openembedded.org > <[email protected]> wrote: > > > Update the UPSTREAM_CHECK_URI to leverage the simple repo API. The > > project URLs require javascript which breaks the version checking fetch > > and subsequent logic. The simple repo API provides similar > > functionality with a well defined spec which is used by tools such as > > pip. Also update the UPSTREAM_CHECK_REGEX to be compatible with the > > information retrieved via the API > > Unfortunately even with this patch, there's a large amount of > UNKNOWN_BROKEN in the output of 'devtool check-upgrade-status'. Can > you please check those, hopefully it's a simple tweak? > > Alex >
-=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#208685): https://lists.openembedded.org/g/openembedded-core/message/208685 Mute This Topic: https://lists.openembedded.org/mt/110085421/21656 Group Owner: [email protected] Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub [[email protected]] -=-=-=-=-=-=-=-=-=-=-=-
