'Conflicts' depends on installation order

[GoogleCodeExporter]

What steps will reproduce the problem?
1. Create package a.ipk with "Conflicts: b"
2. Create package b.ipk with no "Conflicts"
3. Using opkg 0.2.2 (Yocto/dizzy), install both:

   # opkg-cl install a.ipk
   # opkg-cl install b.ipk

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

EXPECTED RESULTS:

   # opkg-cl install a.ipk
   Installing a (1.0-r0) on root.
   # opkg-cl install b.ipk
   Installing b (1.0-r0) on root.
   Collected errors:
    * check_conflicts_for: The following packages conflict with b:
    * check_conflicts_for:  a * 
    * opkg_install_cmd: Cannot install package b.

ACTUAL RESULTS:

   # opkg-cl install a.ipk
   Installing a (1.0-r0) on root.
   # opkg-cl install b.ipk
   Installing b (1.0-r0) on root.

What version of the product are you using? On what operating system?

opkg 0.2.2
Yocto 1.7 (dizzy), opkg 1:0.2.2-r0

Please provide any additional information below.

If you reverse the package install order, it works as expected.

Original issue reported on code.google.com by gabrb...@gmail.com on 14 Dec 2014 at 9:44

[GoogleCodeExporter]

This is solved on the master branch. I haven't backported the fix to the 
opkg-0.2.x series but it should be fairly easy to do so. You'd need to backport 
commits 4e4797b, 2e2329b and 88f1fc54, and there may be a merge conflict to fix 
with the first of those but it should be fairly straightforward. If you have 
any trouble backporting those or if doing so doesn't fix the issue for you, 
please let me know.

Original comment by paul.betafive on 14 Dec 2014 at 11:42

• Changed state: Fixed

[GoogleCodeExporter]

Thank you! I'll check it out!

Original comment by gabrb...@gmail.com on 15 Dec 2014 at 3:58