| Summary: | Upstream version reported as 'unknown' for recipes where it should be known | ||
|---|---|---|---|
| Product: | [Yocto Project Subprojects] Recipe Reporting System (RRS) | Reporter: | Alexander Kanavin <alex.kanavin> |
| Component: | Recipe Reporting System (RRS) | Assignee: | Mariano Lopez <mariano.lopez> |
| Status: | RESOLVED FIXED | QA Contact: | Alexandru Georgescu <alexandru.c.georgescu> |
| Severity: | normal | ||
| Priority: | Medium | CC: | anibal.limon, sgw |
| Version: | unspecified | ||
| Target Milestone: | 1.9 M4 | ||
| Hardware: | x86 | ||
| OS: | Multiple | ||
| Whiteboard: | |||
| OS type for building Yocto: | --- | Type of Regression: | --- |
| Verified: | Documentation change: | No (bug/feature does not impact docs) | |
|
Description
Alexander Kanavin
2015-06-12 13:05:05 UTC
If I go to recipe details for alsa-plugins the current status is "Up-to-date" and if I check the recipe history the upstream version was known since 2015-05-24 (RRS displays "Unknown" when it can't get the upstream version). The bug was reported on 2015-06-12 so it doesn't make sense. Are you still seeing the status as unknown? If not, Can you please provide another example? Looks like the problem with alsa-plugins has fixed itself. I can't at the moment provide another example, so I'll reopen this bug if I find one. The problem exists yet. May be an sporadic issue in upstream server (404), debug is needed. Just in case - please note that there are also recipes where the upstream status is unknown because the RRS genuinely can't figure it out. I'm taking care of those right now, and that's not the issue here. This has been solved by commit: http://git.yoctoproject.org/cgit/cgit.cgi/layerindex-web/commit/?h=rrs&id=e8a13de121c800fb6f3b4a2ab0ab95043d64d1c2 Seems ok now. Have to reopen this. Just now alsa-plugins is 'unknown' but alsa-lib is 'up-to-date'. Locally on my machine both resolve upstream version correctly. Sometimes the script getting the version for upstream sites can't get the version for different reasons: including time outs, server downs, network issues. When this happens it will put the recipe as unknown and this is what happened on September 25th. A manual run of the script fetched the correct version and now appears as up to date. I have opened bug 8400 to request an enhancement to get why the recipe is in unknown status. |