python-smartpm: fix sometimes reporting no provider instead of conflict
authorPaul Eggleton <paul.eggleton@linux.intel.com>
Wed, 24 Jul 2013 10:15:57 +0000 (11:15 +0100)
committerRichard Purdie <richard.purdie@linuxfoundation.org>
Mon, 29 Jul 2013 12:09:14 +0000 (13:09 +0100)
commit113258f02559c8af3483a99370b9c3d8eada6412
tree3c14aca1336cccc4d141a0e7bad02326ad070a22
parentfa2fa29f8c1fd718b7161162bf0fb14f61bb9ee0
python-smartpm: fix sometimes reporting no provider instead of conflict

If a requirement of a package is conflicted, depending on how the
solution is reached, Smart's transaction code may eliminate all
providers of the requirement and then error out because nothing provides
them without saying why. To work around this, store a reason and report
that back if we need to, so for example instead of:

  error: Can't install packagegroup-core-ssh-dropbear-1.0-r1@all: no package provides dropbear

we will now get:

  error: Can't install packagegroup-core-ssh-dropbear-1.0-r1@all: unable to install provider for dropbear:
  error:     dropbear-2013.58-r1.0@armv5te is conflicted by openssh-sshd-6.2p2-r0@armv5te

Fixes [YOCTO #4305].

(From OE-Core rev: 1ed09b87fc8780d4a99f6516493fae2e0c92862c)

Signed-off-by: Paul Eggleton <paul.eggleton@linux.intel.com>
Signed-off-by: Saul Wold <sgw@linux.intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
meta/recipes-devtools/python/python-smartpm/smart-conflict-provider.patch [new file with mode: 0644]
meta/recipes-devtools/python/python-smartpm_1.4.1.bb