yes, it's the wrong syntax, but it shouldn't produce an internal error, isn't it ? Here's what I mean: n22 ~ # equery --nocolor --quiet list -i /var/www/localhost/htdocs/apache_pb2.gif !!! Internal portage error, terminating !!! too many values to unpack
Try gentoolkit-0.2.2_pre4. It does not give that error for me.
Happens here with gentoolkit 0.2.2 (final) I think it's about number of slashes in the atom gehinom ~ # equery list a/b [ Searching for package 'b' in 'a' among: ] * installed packages gehinom ~ # equery list a/b/ !!! Internal portage error, terminating !!! too many values to unpack gehinom ~ # equery list a/b/c !!! Internal portage error, terminating !!! too many values to unpack
I've been looking through the equery script and it seems that the error is thrown during package name parsing. The exact location is line 1282: (cat, name, ver, rev) = gentoolkit.split_package_name(query) The problem seems to be that the gentoolkit function split_package_name does not support queries not of the form "(cat(/name(-ver(-rev)?)?)?)?" Any ideas?
app-portage/gentoolkit-0.2.3-r1 seems to have the same behaviour
Same thing with app-portage/gentoolkit-0.2.4_pre6. equery --nocolor --quiet list -i /var/www/localhost/htdocs/apache_pb2.gif !!! Internal portage error, terminating !!! too many values to unpack
This bug is not fixed.
Created attachment 143923 [details, diff] equery_catch_list_filenames.diff This patch puts some error handling around (cat, name, ver, rev) = gentoolkit.split_package_name(query) that specifically checks for str(ValueError) == 'too many values to unpack' because if gentoolkit.split_package_name(query) returns more than four values it's indicative of a pattern with more than one slash in it, which cannot possibly match any package.
$ svn commit -m "Fix equery list to not generate an internal portage error when fed input with too many slashes. (Bug 119806)" Sending equery/equery Transmitting file data . Committed revision 470.
Released in gentoolkit-0.2.4_rc2
*** Bug 212314 has been marked as a duplicate of this bug. ***