This one took me at least a year to find. I always had problems with eix-sync and could not find out why. Now I finally read the source code of eix-sync, and found, that the documentation states, that @@ hooks come before @ hooks, while eix-sync itself has the oder flipped. (It runs @@ hooks at the very end in UpdateDiff.) This causes eix-update not to be executed, when eix-remote is ran in a @ hook. Because it thinks that eix-remote already ran eix-update. Instead eix-remote should be ran in a @@ hook. Reproducible: Always Steps to Reproduce: 1. Copy the attached “eix-sync.conf” no “/etc/”. 2. Run “eix-sync”. Actual Results: When eix-sync wants to run eix-update, it shows an error, stating that apparently it already wan ran in a hook. Expected Results: With proper documentation, eix-remote would have been run in a @@ hook, and eix-update before it. So the problem would not have occured.
Created attachment 212874 [details] Proper eix-sync configuration file to do everything in one go.
Created attachment 212875 [details] Buggy eix-sync config file. Order according to man page. This is the one to use, when trying to reproduce the problem. (But a quick look at the man page, and at the source of eix-sync, will make it perfectly clear too. :)
Beware, that I haven’t checked, if similar problems exist for the !!, ! and ~ hooks. When we’re at it, this should be checked too.
Thanks for the report. Indeed, the order in the documentation is wrong; also the eix-remote examples were probably meant the opposite way (IIRC, I had written them after refreshing my memory by the documentation above; the other examples were written earlier and appear to be correct). I will fix the documentation, not modify the behavior, i.e. the order will remain in normal situations: !!/! ~ emerge --sync @ eix-update @@ eix-diff
The documentation is fixed in current eix svn trunk (>=eix-0.19.2). However, it may take quite a while for the next releaese.
(In reply to comment #5) > The documentation is fixed in current eix svn trunk (>=eix-0.19.2). > However, it may take quite a while for the next releaese. > in cvs tree. thx
