update-eix-remote return: /usr/bin/update-eix-remote: line 11: .//usr/bin/update-eix-functions.sh: No such file or directory after change the script line 11 of "/usr/bin/update-eix-remote" from ". ./'/usr/bin/update-eix-functions.sh'" to ". '/usr/bin/update-eix-functions.sh'" the script runing well download the "http://dev.gentooexperimental.org/eix_cache/eix-caches.tbz2" and unpacking. but the overlays are not added, local (layman's) and remote fetched. Reproducible: Always Steps to Reproduce: 1. change line 11 of "/usr/bin/update-eix-remote" to fixing calling "/usr/bin/update-eix-functions.sh" 2. update-eix-remote update Actual Results: * Unpacking data * Calling update-eix Reading Portage settings .. Adding virtual overlays from /var/cache/eix .. Excluded /usr/portage/local/layman/desktop-effects Excluded ":::ALL MY LAYMAN'S OVERLAYS:::" Excluded /usr/portage/local/layman/.... Excluded Building database (/var/cache/eix) .. [0] "gentoo" /usr/portage/ (cache: metadata) Reading 100% Excluding "" /etc/portage/local (cache: eix [/etc/portage/local]) Applying masks .. Calculating hash tables .. Writing database file /var/cache/eix .. Database contains 12767 packages in 151 categories. Expected Results: adding overlays to the eix db
The typing error in the script was a missing update in Makefile.am - this will be fixed with the next eix release. I cannot currently download eix-caches.tbz2 (the server seems to be unavailable). However, the eix cache format has changed with eix-0.13.0, so until the server generating eix-caches.tbz2 is upgraded to this eix version, you cannot use this file with eix-0.13.0. BTW: It is intentional that your local [layman] overlays are excluded (you will probably not want to risk that eix shows wrong information about your actual local overlays just because you added additional stuff).
(In reply to comment #1) > The typing error in the script was a missing update in Makefile.am - > this will be fixed with the next eix release. > > I cannot currently download eix-caches.tbz2 (the server seems to be > unavailable). However, the eix cache format has changed with eix-0.13.0, > so until the server generating eix-caches.tbz2 is upgraded to this eix > version, you cannot use this file with eix-0.13.0. > > BTW: It is intentional that your local [layman] overlays are excluded > (you will probably not want to risk that eix shows wrong information about > your actual local overlays just because you added additional stuff). > if the problem of eix-caches.tbz2 is the version on the server, sorry my post.
(In reply to comment #2) > if the problem of eix-caches.tbz2 is the version on the server I had thought so, first: It is always difficult to test update-eix-remote after a change in the cachefile format, that's why I don't test it if I think nothing was changed there... However, it seems that there was also a bug in the path resolution which caused the confusing messages (although it is correct that the paths should be excluded, they usually do not match the overlay list passed by update-eix-remote, and thus usually no messages are printed. Unfortunately, the passed overlay list was resolved to only empty names - so things didn't work at all). I will release eix-0.13.1 urgently which hopefully fixes the issue (however, currently the caches on the server are still in the old format).
Closing since the archive on the server seems to be correct now
