Closed GoogleCodeExporter closed 9 years ago
As I said in email, it looks like, during an upgrade, opkg is
checking for orphan packages before the old package is marked as uninstalled.
I was wrong thinking that was the problem though, pkg_remove_orphan_dependent
gets the number of installed dependents of each autoinstalled package and then
subtracts one to account for the old package which is about to be removed. It
may be double counting dependencies though.
Original comment by paul.betafive
on 25 Aug 2014 at 12:44
I'm pretty sure this is now fixed in both the opkg-0.2.x and master branches. I
managed to locally reproduce your issue and made some changes to
pkg_remove_orphan_dependent until the autoremove went ahead as expected.
I'm going to assume this is now fixed. If it isn't just add a comment and we
can re-open this.
Original comment by paul.betafive
on 28 Oct 2014 at 11:38
Original issue reported on code.google.com by
seo...@gmail.com
on 7 Aug 2014 at 12:52