Summary: | app-portage/eix-0.29.3 SIGSEGV when using wrong format specifier | ||
---|---|---|---|
Product: | Portage Development | Reporter: | Seraphim Mellos <mellos> |
Component: | Tools | Assignee: | Martin Väth <martin> |
Status: | RESOLVED FIXED | ||
Severity: | minor | CC: | aayla.secura.1138, axs, erikdenstore+gbugs, gem, mmk, prometheanfire, proxy-maint, xmw |
Priority: | Normal | ||
Version: | unspecified | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- |
Description
Seraphim Mellos
2013-09-02 13:45:50 UTC
Forgot to mention that both machines are using =sys-apps/portage-2.1.12.2 although I don't think that has anything to do with the error. This issue is also affecting puppet (all tested versions up to 2.7.23) which is using the following eix call: eix --format "<installedversions:VERSION>" dev-lang/python This is causing a SIGSEGV as well which I assume means that VERSION was deprecated going from 0.25.5 to 0.29.3? If VERSION has been deprecated, a bug should be opened with puppet to fix the eix call as well. The segfault is fixed in eix git master on BerliOS (>=eix-0.29.4). The variable VERSION has never been documented; it is one of many variables which were used in delayed substitution and which are likely to be modified if a new concept for the output is introduced. Puppet should not rely on such variables but instead e.g. export VERSION as desired. I opened bug 483522 for the puppet issue. +*eix-0.29.4 (10 Sep 2013) + + 10 Sep 2013; Ian Stakenvicius <axs@gentoo.org> +eix-0.29.4.ebuild: + version bump, fixes bugs 480604, 483392 + *** Bug 488328 has been marked as a duplicate of this bug. *** *** Bug 521216 has been marked as a duplicate of this bug. *** *** Bug 528478 has been marked as a duplicate of this bug. *** *** Bug 528478 has been marked as a duplicate of this bug. *** |