Bug 8400 - rrs: add the cause of an unknown recipe version
Summary: rrs: add the cause of an unknown recipe version
Status: RESOLVED OBSOLETE
Alias: None
Product: Recipe Reporting System (RRS)
Classification: Yocto Project Subprojects
Component: Recipe Reporting System (RRS) (show other bugs)
Version: unspecified
Hardware: All Multiple
: Medium enhancement
Target Milestone: 4.99
Assignee: Paul Eggleton
QA Contact:
URL:
Whiteboard: .
Depends on: 9746
Blocks:
  Show dependency tree
 
Reported: 2015-09-25 17:43 UTC by Mariano Lopez
Modified: 2022-01-21 22:17 UTC (History)
5 users (show)

See Also:
OS type for building Yocto: ---
Type of Regression: ---
Verified:
Documentation change: No (bug/feature does not impact docs)

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Mariano Lopez 2015-09-25 17:43:17 UTC 
There could be several reason why the upstream version of the recipe is unknown (broken link, time out, etc.). The enhancement request here is to include the unknown reason so it will be easier to maintain the broken links or errors that require manual intervention.
Comment 1 Alexander Kanavin 2017-11-07 14:04:31 UTC 
FWIW, I think with 
a) addition of support for repos without version tags in checkpkg
b) addition of RECIPE_VERSION_UNKNOWN acknowledgment in recipes

this issue is obsolete. When a recipe goes from known to unknown, it's usually because upstream went offline or removed the tarball, and this requires manual investigation and fixing anyway.
Comment 2 Alexander Kanavin 2022-01-21 22:17:46 UTC 
See the comment above.