12474 2018-01-11 17:22:12 +0000 If `opkg install file` collides with repo pkg with same name/version, the repo metadata is used 2021-07-08 17:00:52 +0000 1 1 6 Yocto Project Subprojects opkg opkg 0.4.1 All Multiple ACCEPTED Undecided normal next-patch 1 rich.tollerton alex.stewart alex.stewart rich.tollerton --- --- No (bug/feature does not impact docs) oldest_to_newest 79046 0 4171 rich.tollerton 2018-01-11 17:22:12 +0000 Created attachment 4171 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. 82573 1 alejandro.delcastillo 2018-12-21 00:00:19 +0000 Re-targeting before release 4171 2018-01-11 17:22:12 +0000 2018-01-11 17:22:12 +0000 opkg test: when ipk to install collides with ipk in repo, use metadata from file 40_upgrade_deps_override.py text/x-python 593 rich.tollerton IyEgL3Vzci9iaW4vZW52IHB5dGhvbjMKIwojIENyZWF0ZSBhIHBhY2thZ2UgaW4gYSByZXBvIHdp dGggYSBzcHVyaW91cyBkZXBlbmRlbmN5LiBEb3dubG9hZCB0aGUgaW5kZXggZm9yCiMgdGhlIHJl cG8uIFRoZW4gY3JlYXRlIGEgZGlmZmVyZW50IGJ1aWxkIG9mIHRoYXQgcGFja2FnZSwgd2l0aCB0 aGUgc2FtZSBuYW1lCiMgYW5kIHZlcnNpb24sIHdpdGggdGhlIHNwdXJpb3VzIGRlcGVuZGVuY3kg cmVtb3ZlZC4KCmltcG9ydCBvcwppbXBvcnQgb3BrLCBjZmcsIG9wa2djbApvcGsucmVncmVzc19p bml0KCkKCm8gPSBvcGsuT3BrR3JvdXAoKQpvLmFkZChQYWNrYWdlPSI0MGEiLCBWZXJzaW9uPSIx LjAiLCBEZXBlbmRzPSI0MGIiKSAjIGRvZXNuJ3QgZXhpc3QhCm8ud3JpdGVfb3BrKCkKby53cml0 ZV9saXN0KCkKCm9wa2djbC51cGRhdGUoKQoKcGtnID0gb3BrLk9wayhQYWNrYWdlPSI0MGEiLCBW ZXJzaW9uPSIxLjAiKQpwa2cud3JpdGUoKQpvcGtnY2wuaW5zdGFsbCgiNDBhXzEuMF9hbGwub3Br IikKCmlmIG5vdCBvcGtnY2wuaXNfaW5zdGFsbGVkKCI0MGEiLCAiMS4wIik6CglvcGsuZmFpbCgi NDBhIHdhc24ndCBpbnN0YWxsZWQiKQo=