summaryrefslogtreecommitdiff
path: root/meta/recipes-support/libical
diff options
context:
space:
mode:
authorRichard Purdie <richard.purdie@linuxfoundation.org>2013-03-14 00:15:10 +0000
committerRichard Purdie <richard.purdie@linuxfoundation.org>2013-03-14 16:37:03 +0000
commitbd03014c8fd080e04dd0a96a6b4b9211568c1cf1 (patch)
tree9f82cf867e123f7f43453a0eb643f8c7a5dbb53b /meta/recipes-support/libical
parente40c36ff8610ebb9ce16a4d1c14c7cf94f87cd6a (diff)
downloadopenembedded-core-bd03014c8fd080e04dd0a96a6b4b9211568c1cf1.tar.gz
openembedded-core-bd03014c8fd080e04dd0a96a6b4b9211568c1cf1.tar.bz2
openembedded-core-bd03014c8fd080e04dd0a96a6b4b9211568c1cf1.zip
package_rpm: Ensure package dependencies have correct version numbers
If a recipe has versioned dependencies on another package within the same recipe, there are potentially races where the version remapping may not happen correctly. This issue triggered with neard in multilib builds since it uses a "-" character in its PV which is illegal in an rpm version field. The remapping to "+" was not occuring. It only triggers in the multilib case since in this case, expansion of the datastore happens at slightly different points. The correct fix is to search for PV, not PKGV but substitute the PV value. Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Diffstat (limited to 'meta/recipes-support/libical')
0 files changed, 0 insertions, 0 deletions