Problem when upgrading a package which depends on a new package

[GoogleCodeExporter]

What steps will reproduce the problem?
1. Install a package A which depends on B
2. Update the package A which now depends on C, but C conflicts with B
3. Try to upgrade :)

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

What we should expect:
root@terminal:# opkg upgrade -force-defaults -autoremove
Upgrading A on root from 1.0-r0.1 to 2.0-r0.1...
Downloading ...
Installing C (1.0-r0) to root...
The following packages conflict with C: B 
B is now orphaned, uninstalling...

What I see:
root@terminal:# opkg upgrade -force-defaults -autoremove
Upgrading A on root from 1.0-r0.1 to 2.0-r0.1...
Downloading ...
Installing C (1.0-r0) to root...
Collected errors: * ERROR: The following packages conflict with C: * B *

Original issue reported on code.google.com by pixdamix@gmail.com on 9 Dec 2009 at 9:29

[GoogleCodeExporter]

Might be resolved using "Replaces", switch to low priority

Original comment by pixdamix@gmail.com on 10 Feb 2010 at 9:03

• Added labels: Priority-Low
• Removed labels: Priority-Medium

[GoogleCodeExporter]

If C conflicts with B but does not replace B it should still disappear due to 
the 'autoremove' flag. It's probably a rare case so I'll keep the priority as 
low but I agree this is a bug.

Original comment by paul.betafive on 28 Sep 2013 at 1:20

• Added labels: Milestone-1.0