[OE-core] [PATCH 2/2] oe-core: take UPSTREAM_CHECK_COMMITS into use where possible

Alexander Kanavin alexander.kanavin at linux.intel.com
Wed Nov 1 08:38:48 UTC 2017


On 10/31/2017 11:03 PM, Randy MacLeod wrote:
> On 2017-10-31 01:43 PM, Alexander Kanavin wrote:
>> This greatly reduces the amount of recipes for which upstream
>> version check fails: from about 30 to about 8.
> 
> Has anyone looked into piggy-backing off:
>     https://release-monitoring.org/
> Currently 15791 projects are being monitored by Anitya.
>     https://github.com/release-monitoring/anitya
> I *suspect* this is a Redhat backed project so it's likely
> to remain active and up to date.
> 
> Hmmm, I just tried a few of the packages listed below and only
> 2 of 8 were tracked packages but this is an outliers list so
> maybe that's a sign that the r-m.org site is doing better than
> our tracker.

Their data is not of sufficient quality unfortunately. For Python they 
report 3.7.0 as the latest version even though it won't be released 
until june 2018. Python 2.x is neglected altogether. Latest 3.6 version 
is 3.6.3 released a month ago, but they report only 3.6.2.

Similar issues with webkitgtk: they report 2.19.1 (a pre-release), but 
not 2.18.2 (actual latest release).

Then there's the question of who maintains the mapping of their database 
to our package names.

Our tracker has over 98% accuracy, while this one failed both of the 
randomly chosen samples ;)

Alex



More information about the Openembedded-core mailing list