Bug 12474 - If `opkg install file` collides with repo pkg with same name/version, the repo metadata is used
Summary: If `opkg install file` collides with repo pkg with same name/version, the rep...
Status: ACCEPTED
Alias: None
Product: opkg
Classification: Yocto Project Subprojects
Component: opkg (show other bugs)
Version: 0.4.1
Hardware: All Multiple
: Undecided normal
Target Milestone: next-patch
Assignee: Alex Stewart
QA Contact:
URL:
Whiteboard:
Depends on:
Blocks:
 
Reported: 2018-01-11 17:22 UTC by Richard Tollerton
Modified: 2021-07-08 17:00 UTC (History)
2 users (show)

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


Attachments
opkg test: when ipk to install collides with ipk in repo, use metadata from file (593 bytes, text/x-python)
2018-01-11 17:22 UTC, Richard Tollerton
no flags Details

Note You need to log in before you can comment on or make changes to this bug.
Description Richard Tollerton 2018-01-11 17:22:12 UTC
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.
Comment 1 Alejandro del Castillo 2018-12-21 00:00:19 UTC
Re-targeting before release