8342 2015-09-20 22:35:36 +0000 [internalsolv] Opkg fails to attempt all satisfying dependencies after installing the first one fails (old issue #85) 2021-07-08 15:28:48 +0000 1 1 6 Yocto Project Subprojects opkg opkg unspecified x86 Multiple ACCEPTED Undecided minor --- 1 alejandro.delcastillo alex.stewart --- --- No (bug/feature does not impact docs) oldest_to_newest 54320 0 alejandro.delcastillo 2015-09-20 22:35:36 +0000 What steps will reproduce the problem? #!/usr/bin/python3 import opk, cfg, opkgcl def cleanup(): opkgcl.remove("a") opkgcl.remove("b") opkgcl.remove('c') opk.regress_init() o = opk.OpkGroup() o.add(Package="a", Provides="v") o.add(Package="b", Provides="v", Depends="b_nonexistant") o.add(Package="c", Depends="v") o.write_opk() o.write_list() opkgcl.update() # install ``c'' from repository opkgcl.install("c") if not opkgcl.is_installed("c"): print(__file__, ": package ``c'' not installed.") cleanup() exit(False) cleanup() What is the expected output? What do you see instead? Opkg should try subsequent satisfying dependencies in the event of failing to install the first one (e.g. due to missing dependency or conflict). Originally reported by graham.gower, Oct 24, 2011 ----------------------------------------------------------------------------- #1 paul.betafive (Sep 18, 2013) I'll add this to my todo list as Graham isn't working on opkg anymore. #2 paul.betafive (Mar 1, 2014) This case should occur relatively rarely in well managed package feeds so I see it as less of a priority to fix than other bugs. Tagged for v0.4 for now. 82561 1 alejandro.delcastillo 2018-12-20 23:34:47 +0000 De-prioritzing internalsolv bugs