| Summary: |
If `opkg install file` collides with repo pkg with same name/version, the repo metadata is used |
| Product: |
[Yocto Project Subprojects] opkg
|
Reporter: |
Richard Tollerton <rich.tollerton> |
| Component: |
opkg | Assignee: |
Alex Stewart <alex.stewart> |
| Status: |
ACCEPTED
---
|
QA Contact: |
|
| Severity: |
normal
|
|
|
| Priority: |
Undecided
|
CC: |
alex.stewart, rich.tollerton
|
| Version: |
0.4.1 | |
|
| Target Milestone: |
next-patch | |
|
| Hardware: |
All | |
|
| OS: |
Multiple | |
|
| Whiteboard: |
|
|
OS type for building Yocto:
|
---
|
Type of Regression:
|
---
|
|---|
|
Verified:
|
|
Documentation change:
|
No (bug/feature does not impact docs)
|
|---|
| Attachments: |
|
Created attachment 4171 [details] opkg test: when ipk to install collides with ipk in repo, use metadata from file Suppose you are fixing a bug in a package, have rebuilt the package, and are in the process of manually testing the fix with `opkg install file`. And you have _not_ bumped the package version. However, the broken package is in a repo indexed by opkg. What I expect to see happen is that the metadata loaded for the ipk is, you know, loaded from the ipk. At a minimum, I know for a fact that pacman does this. However, the observed behavior is that the metadata from the index is loaded instead. See attached for proposed test.