| Summary: |
[internalsolv] Package install upgrades provider of virtual dependency incorrectly |
| Product: |
[Yocto Project Subprojects] opkg
|
Reporter: |
Michael Hansen <michael.j.hansen> |
| Component: |
opkg | Assignee: |
Alex Stewart <alex.stewart> |
| Status: |
ACCEPTED
---
|
QA Contact: |
|
| Severity: |
minor
|
|
|
| Priority: |
Undecided
|
|
|
| Version: |
0.3.3 | |
|
| Target Milestone: |
--- | |
|
| Hardware: |
x86 | |
|
| OS: |
Multiple | |
|
| Whiteboard: |
|
|
OS type for building Yocto:
|
---
|
Type of Regression:
|
---
|
|
Verified:
|
|
Documentation change:
|
No (bug/feature does not impact docs)
|
| Attachments: |
|
Probably related to #9802, packages will be upgraded incorrectly when referenced through a virtual dependency: Given: Package a depends on bapi-1.0 Package b-1.0 provides bapi-1.0 Package b-2.0 provides bapi-2.0 Perform: Install package b-1.0 Install package a Expected: a is installed, b is kept at version 1.0 Actual: b is upgraded to 2.0, and a is successfully installed despite broken dependency