'--autoremove' option removes recommended pacakge

[GoogleCodeExporter]

What steps will reproduce the problem?

1. Create packages A and C which both recommend B.
2. Create package B.
3. Install A and C.
4. Remove A with --autoremove 

What is the expected output? What do you see instead?

Expect B to remain installed as it is still depended on by C. Instead, B is 
removed.

This test case was initially part of tests/regress/issue58.py but the failure 
was not as described in issue 58 in the bug tracker, so this was split out into 
a new issue.

Original issue reported on code.google.com by paul.betafive on 3 Aug 2013 at 3:27

[GoogleCodeExporter]

We have more pressing issues than this one, tagging it for v0.4.

Original comment by paul.betafive on 1 Mar 2014 at 3:21

• Added labels: Milestone-0.4, Priority-Low
• Removed labels: Priority-Medium

[GoogleCodeExporter]

Fixed in opkg-0.2.x and master.

Original comment by paul.betafive on 3 Jul 2014 at 1:55

• Changed state: Fixed