Paul Eggleton 4ea3834033 rrs_upstream_history: properly handle missing Recipe ... If the Recipe object doesn't exist here then an exception will be raised rather than None being returned, and this will also trigger if multiple recipes match. This may have never triggered in the past because this would have been run right after updating all the recipes in the layer and clearing out duplicates (which we were doing earlier), and thus what is in the database would match the recipe files in the repository, assuming no errors occurred during parsing). We can't remove duplicates though so we need to switch over to using filter() and taking the first recipe. Signed-off-by: Paul Eggleton <paul.eggleton@linux.intel.com>		2018-05-04 23:57:53 +12:00
..
common.py	rrs/tools/common.py: import sys/os at top	2018-05-04 23:57:52 +12:00
daily_run.sh	rrs/tools/rrs_unique_recipes: drop	2018-05-04 23:57:52 +12:00
rrs_distros.py	rrs/tools: add dry-run option to each script	2018-05-04 23:57:52 +12:00
rrs_maintainer_history.py	rrs_maintainer_history.py: support maintenance plans and remove poky hardcoding	2018-05-04 23:57:52 +12:00
rrs_upgrade_history.py	rrs_upgrade_history: drop unused import	2018-05-04 23:57:53 +12:00
rrs_upstream_email.py	rrs/tools/rrs_upstream_email.py: Update message to point recipe file	2018-05-04 23:57:52 +12:00
rrs_upstream_history.py	rrs_upstream_history: properly handle missing Recipe	2018-05-04 23:57:53 +12:00