For example, dev-python/pypy has the following SLOT definition: SLOT=$(get_version_component_range 1-2 ${PV}) Per hasufell, this produces the following output from eix: ((get_version_component_range) ~1.9-r2 This is the expected output: 1.9 ~1.9-r2
You did not write which eix version you use: If you use <eix-0.29.1, you might suffer from the md5 bug. Upgrading should fix the issue. Otherwise, I assume that you are speaking about an ebuild from some overlay without metadata/* being up-to-date: In this case, this is probably a dupe of bug 194314 and related bugs. Cache-method "parse" (in these bugs still called "none") cannot solve this issue. The recommended workaround is to use egencache to update metadata/* in the overlay (if you did not change the defaults, the metadata should be used - if you do not suffer from the md5 bug; you can verify with eix-update -v which method actually is used).
tested on 0.25.5 and 0.29.1 both affected
As I said, then it is probably a dupe of 194314: This is expected behaviour if you use cache method "parse" or "parse*". As a workaround proceed e.g. as described in the section SPEEDUP on the manpage. If updating the metadata with the egencache command mentioned there does not produce the expected results, reopen this bug. *** This bug has been marked as a duplicate of bug 194314 ***
schön
