*Reproduction steps*
1. Have package A depending on package B.
2. Do 'opkg-cl upgrade'
*Behavior*
Package A is upgraded first (version 1->2) and it also makes package B upgraded
to version 2 (becasue of dependency). Then, the upgrade procedure gets to
package B which is already upgraded but opkg still sees it in version 1 as it
was when upgrade started. Obviously second attempt to install package B fails
and makes opkg return code to be -1, even if all expected packages have
actually been upgraded to expected versions.
*Expectations*
For successful upgrades I expect opkg exit code to be 0.
*Versions seen*
0.1.8 and 0.2.4, medial versions possibly impacted.
*Remarks*
Not tested what would happen if package B was upgraded before A because of
different upgrade order.
*Workaround*
I'm calling opkg twice - if the first run upgraded what it was supposed to
upgrade, then the second run has no work to do and just exits with '0'.
Original issue reported on code.google.com by michal.p...@gmail.com on 28 Nov 2014 at 12:03
Original issue reported on code.google.com by
michal.p...@gmail.com
on 28 Nov 2014 at 12:03