Bug 9081 - RRS should respect DEFAULT_PREFERENCE when multiple versions of the same recipe are available
Summary: RRS should respect DEFAULT_PREFERENCE when multiple versions of the same reci...
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: x86 Multiple
: Medium normal
Target Milestone: 2.4
Assignee: Jose Lamego
QA Contact: oscar lopez arandas
URL:
Whiteboard:
Depends on: 9746
Blocks:
  Show dependency tree
 
Reported: 2016-02-09 10:30 UTC by Alexander Kanavin
Modified: 2017-09-11 12:22 UTC (History)
4 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 Alexander Kanavin 2016-02-09 10:30:24 UTC 
For example there are two versions of gstreamer recipes (stable and development), the development version has a DEFAULT_PREFERENCE of -1 (which means it is not the preferred version), yet RRS reports against that version. It should pick the stable version instead. 'bitbake -c checkpkg' on the other hand works as expected.

An alternative is to include all versions of the recipes into the report.
Comment 1 Jose Lamego 2017-09-07 21:05:30 UTC 
Alexander, I was not able to reproduce this issue:

Seems that RRS is appropriately tracking gstreamer1.0 + others recipes, but not development versions. The recipes that I found that are using DEFAULT_PREFERENCE variable seem to be appropriately reported too.

Please provide a recent example of the detected behavior and the expected outcome.
Comment 2 Alexander Kanavin 2017-09-11 12:22:32 UTC 
That's right. I couldn't find another example in oe-core; we've removed all or almost all alternative versions of recipes lately.