You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We hit this often on the Gentoo Infrastructure servers, 0.32.9. I think it's a locking issue that eix-update might be running concurrently to a query. The query should block until eix-update has completed, OR the database updates should be written atomically.
# /usr/bin/eix --nocolor --pure-packages \
--format '<category> <name> [<installedversions:LASTVERSION>] [<bestversion:LASTVERSION>] <homepage> <description>' \
--exact --category-name \
sys-apps/iproute2
/var/cache/eix/portage.eix was created with an incompatible eix-update:
It uses database format 37 (current is 37).
Please run "eix-update" and try again.
The text was updated successfully, but these errors were encountered:
This never happened to me, and it is mysterious to me. According to the code, the output It uses database format 37 (current is 37)
cannot happen: It happens only if a previous test decided that the 2 printed numbers are unequal.
I have only a vague idea that some __attribute__ ((pure)) might lead to a miscompilation of that test.
Are you able to apply the following patch to check whether it fixes the problem for you?
Edit: I change the title, because this error certainly has nothing to do with locking. There is no read operation happening between the check and the output. In fact, the code is almost completely trivial which is why I have no idea what goes wrong here.
vaeth
changed the title
eix database wrongly claims incompatible: eix-update should lock database.
eix claims identical database versions differ
Oct 2, 2017
We hit this often on the Gentoo Infrastructure servers, 0.32.9. I think it's a locking issue that
eix-update
might be running concurrently to a query. The query should block untileix-update
has completed, OR the database updates should be written atomically.The text was updated successfully, but these errors were encountered: