As was reported in bug 483392, puppet-2.7.23 uses the call eix --format "<installedversions:VERSION>" dev-lang/python The variable VERSION, however, was never documented by eix and should be exported by puppet; it breaks with current eix version (The call will also break with older eix versions if the user modified DEFAULT_FORMAT.) A correct and rather future-save call would be e.g. DEFAULT_FORMAT=normal VERSION='<version>{!last} {}' eix --format ... I did not check whether the issue has been fixed in newer puppet versions. If yes, they should be stabilized soon, because puppet-2.7.23 breaks with currently stabilized eix.
I've seen some work with eix recently. has =app-portage/eix-0.29.4 fixed this for you?
(In reply to Matthew Thode ( prometheanfire ) from comment #1) > has =app-portage/eix-0.29.4 fixed this for you? I am the maintainer of eix and never used puppet. On some systems eix even raised a segfault when using an undefined variable like VERSION; although this segfault has been fixed in eix-0.29.4, puppet will just get an empty output from eix, because VERSION is not defined. This is why I reported this bug - without the segfault it might be hard to find that something is wrong with the call of eix.
I had a look into the puppet source code and they are using LASTVERSION which they export into the env with every eix call. I've traced the faulty eix call and it seems like it's not strictly puppet but a facter fact from a 3rd party puppet module. I think this can be closed as invalid.
Ok, that sounds good to me, I've not seen the issue in my puppet runs (3.2.4 or 3.3.0), also, no other bugs related to this...
