When I was inspecting media-video/libav to see its state, I ran `eix -R media-video/libav` (well, I have it as a default option) and had as a result 0.8.2^t[2] (~)0.8.2-r2[2] 0.8.3[2] 0.8.5(0/0.8) (~)0.8.6(0/0.8) **0.8.9999(0/0.8) **0.8.9999[2] (~)9.5(0/9) **9.9999(0/9) **9999(0/9)^t **9999^t[2] so I assumed that it had a Gentoo portage tree version 9.5 that is unmasked. It appears that that was not the case as I learned when trying to emerge a package I was working on, luckily I didn't commit yet. So, I went to check it again and ran a clean `eix media-video/libav` and as a result I had 0.8.5(0/0.8) (~)0.8.6(0/0.8) (~)0.8.7(0/0.8) **0.8.9999(0/0.8) [M] (~)9.6(0/9) **9.9999(0/9) **9999(0/9)^t which has 1) much newer versions, 2) no unmasked 9.5 and 3) a masked 9.6. It seems I better use eshowkw from now on, where Keywords for media-video/libav: | | u | | a a p s | n | | l m h i m m p s p | u s | r | p d a p a 6 i p c 3 a x | s l | e | h 6 r p 6 8 p p 6 9 s r 8 | e o | p | a 4 m a 4 k s c 4 0 h c 6 | d t | o ----------+---------------------------+---------+------- 0.8.5 | + + + + + o ~ + + o o + + | o 0/0.8 | gentoo 0.8.6 | ~ ~ ~ ~ ~ o ~ ~ ~ o o ~ ~ | # | gentoo 0.8.7 | ~ ~ ~ + ~ o ~ ~ ~ o o ~ ~ | o | gentoo 0.8.9999 | o o o o o o o o o o o o o | o | gentoo ----------+---------------------------+---------+------- [M][I]9.6 | ~ ~ ~ ~ ~ o ~ ~ ~ o o ~ ~ | o 0/9 | gentoo 9.9999 | o o o o o o o o o o o o o | # | gentoo 9999 | o o o o o o o o o o o o o | o | gentoo confirms that eix -R was out of date. You clearly see 9.6 masked here. However, I still like to properly use eix -R for my own benefit; how can I correct this out-of-date situation such that eix -R is as up-to-date as eix? Currently I do: eix-remote update layman -S eix-sync -C --ask=n I've had many more problems in the past with eix; some were just because I used sqlite for some time (eg. no explicit metadata update causing it to be out of sync), then later I tried to fix my remote information (above solution, but I just discovered it to be out of sync). That's how I came up with these commands and the order they are in. Is it because I run the remote update before the sync? Can I combine these eix and layman calls? How do I fix eix -R to not be out of date? Thanks you very much in advance.
what eix version are you using?
`emerge -pvC eix` yields 0.28.4; I'm not entirely sure if this is a bug though, but it has been tedious enough to get eix to work right so please see this as a support bug.
> It seems I better use eshowkw It is better if you use eix (without -R): This reads the eix database (/var/cache/portage.eix) which is by default updated with eix-sync and eix-update. If you use eix -R you access instead the remote database (/var/cache/remote.eix). The latter is by default *not* updated by eix-sync but only by eix-remote. Of course, you can configure eix-sync to call eix-remote at every call. This is documented on the eix manpage: Put e.g. the lines @@StatusInfo 'eix-remote add1' @@eix-remote add1 into /etc/eix-sync.conf: This updates your current gentoo tree in the remote database. It does *not* update the remote data: To get the newest remote data use eix-remote fetch1 before. To do this at every eix-sync (which however is perhaps a bit too often), you can put in addition @eix-remote fetch into /etc/eix-sync.conf. All this is documented in the eix manpage (which admittedly is rather long and full of information). Closing the bug as everything seems to work as documented...
(In reply to comment #3) I mistyped the paths: /var/cache/eix/portage.eix and /var/cache/eix/remote.eix were meant.
It doesn't run the `eix-remote add1` for me. This is what I have put in /etc/eix-sync.conf: * @eix-remote fetch1 @@StatusInfo 'eix-remote add1' @@eix-remote add1 This is what I call now to sync: eix-sync -C --ask=n The output contains: ... * eix-remote add1 * Calling eix-diff ... As you see, the @@eix-remote add1 doesn't run; it goes straight on to eix-diff. Though, running `eix-remote add1` apart after the eix-sync call works; for now, I'll call this separately after the eix-sync as a workaround. Would be nice to see this fixed so I can just call a plain eix-sync again.
I suppose a newline at the end of the last line in /etc/eix-sync.conf is missing.
That was it, thanks. Up to you whether you consider this a bug...
(In reply to comment #7) > That was it, thanks. Up to you whether you consider this a bug... Just changed the topic and fixed it in the git master branch (>=eix-0.25.6).
Closing since eix-0.29.0 is in tree.
