On a binary only system, gettext got dep-cleaned. When you run eix without it present, the following message is printed /usr/bin/eix-functions.sh: line 434: .: gettext.sh: file not found Reproducible: Always
I have no explanation for this: This line is only executed if the test command -v gettext.sh >/dev/null 2>&1 succeeded. What is the output of the command sequence command -v gettext.sh && echo $? on your system? Which shell is started by the first line of eix-functions.sh on your system?
I forgot the most important question: Does the problem occur with the most recent version of eix (eix-0.30.5)? (There were some fixes concerning gettext.sh in eix-0.30.2 or so)
Ok now my turn to be without explanation. I re-installed gettext so that I could use eix, and then filed this bug. To test your question in Comment 2, I cleaned gettext again, and now it works as expected. All of this is using eix-0.29.3 (armv7a stable). I'll keep an eye on it, and re-open if needed, but for now you might as well close it. Sorry for the confusion, and I wish I knew how this happened.
Closing to not hinder stabilization of eix-0.30.4
Martin, This annoyed me (computers should be deterministic :) I figured out why my problem "disappeared". The issue wasn't with the eix command, it was when I attemted to run the eix-sync wrapper. Perhaps this has a different codepath. The original "/usr/bin/eix-functions.sh: line 434: .: gettext.sh: file not found" came back after I had removed gettext again, and attempted to eix-sync. However, I can confirm that upgrading to eix-0.30.4 corrected the problem. I just thought you might like to know.
Concerning eix, that's what I suspected: That you were using an older version which probably had this bug. This is one of the main reasons I filed the stabilization bug ASAP: I got recently too many reports about bugs which have been fixed already in eix. So, please leave this bug closed to let eix-0.30.4 become stable.
