I get error message on eix-diff after upgrading to =app-portage/eix-0.32.4 "cannot open database file /var/cache/eix/previous.eix for reading (mode = 'rb')" I have tried eix-update but it does not solve the problem.
Can you please remove the file (sudo rm -v /var/cache/eix/previous.eix) and re-run eix-update?
(In reply to Michael Weber from comment #1) > Can you please remove the file (sudo rm -v /var/cache/eix/previous.eix) and > re-run eix-update? Here we go https://i.imgur.com/riQuvhr.png
portage.eix needs to be moved/copied to previos.eix, eix-update doesn't do that. Plain eix-sync does this, and if you don't want it to sync your tree, your can run eix-sync -c /bin/true or eix-sync -a -c /bin/true for testing. khonsu ~ # eix-sync -c /bin/true * Running /bin/true * Main gentoo tree does not appear to have changed: exiting * Use -a or set have_changed=: in a ! hook to override this check * Time statistics: 1 seconds total khonsu ~ # eix-sync -a -c /bin/true * Running /bin/true * Copying old database to /var/cache/eix/previous.eix * Running eix-update Reading Portage settings... Building database (/var/cache/eix/portage.eix)... [0] "gentoo" /usr/portage/ (cache: metadata-md5-or-flat) Reading category 163|163 (100) Finished Applying masks... Calculating hash tables... Writing database file /var/cache/eix/portage.eix... Database contains 19432 packages in 163 categories. * Calling eix-diff * Time statistics: 20 seconds for eix-update 7 seconds for eix-diff 28 seconds total
(In reply to Michael Weber from comment #3) > portage.eix needs to be moved/copied to previos.eix, eix-update doesn't do > that. > > Plain > eix-sync > does this, and if you don't want it to sync your tree, your can run > eix-sync -c /bin/true > or > eix-sync -a -c /bin/true > for testing. > > khonsu ~ # eix-sync -c /bin/true > * Running /bin/true > * Main gentoo tree does not appear to have changed: exiting > * Use -a or set have_changed=: in a ! hook to override this check > * Time statistics: > 1 seconds total > khonsu ~ # eix-sync -a -c /bin/true > * Running /bin/true > * Copying old database to /var/cache/eix/previous.eix > * Running eix-update > Reading Portage settings... > Building database (/var/cache/eix/portage.eix)... > [0] "gentoo" /usr/portage/ (cache: metadata-md5-or-flat) > Reading category 163|163 (100) Finished > Applying masks... > Calculating hash tables... > Writing database file /var/cache/eix/portage.eix... > Database contains 19432 packages in 163 categories. > * Calling eix-diff > * Time statistics: > 20 seconds for eix-update > 7 seconds for eix-diff > 28 seconds total I have tried moving portage.eix to previous.eix then eix-update and problem is still there. Then i have removed both files and than eix-update, portage.eix is created again and problem is still there.
(In reply to Branko Djusic from comment #4) > (In reply to Michael Weber from comment #3) > > portage.eix needs to be moved/copied to previos.eix, eix-update doesn't do > > that. > > > > Plain > > eix-sync > > does this, and if you don't want it to sync your tree, your can run > > eix-sync -c /bin/true > > or > > eix-sync -a -c /bin/true > > for testing. > > > > khonsu ~ # eix-sync -c /bin/true > > * Running /bin/true > > * Main gentoo tree does not appear to have changed: exiting > > * Use -a or set have_changed=: in a ! hook to override this check > > * Time statistics: > > 1 seconds total > > khonsu ~ # eix-sync -a -c /bin/true > > * Running /bin/true > > * Copying old database to /var/cache/eix/previous.eix > > * Running eix-update > > Reading Portage settings... > > Building database (/var/cache/eix/portage.eix)... > > [0] "gentoo" /usr/portage/ (cache: metadata-md5-or-flat) > > Reading category 163|163 (100) Finished > > Applying masks... > > Calculating hash tables... > > Writing database file /var/cache/eix/portage.eix... > > Database contains 19432 packages in 163 categories. > > * Calling eix-diff > > * Time statistics: > > 20 seconds for eix-update > > 7 seconds for eix-diff > > 28 seconds total > > I have tried moving portage.eix to previous.eix then eix-update and problem > is still there. Then i have removed both files and than eix-update, > portage.eix is created again and problem is still there. It's fixed after eix-sync.
*** Bug 609344 has been marked as a duplicate of this bug. ***
(In reply to Branko Djusic from comment #5) > It's fixed after eix-sync. Um, no, it isn't. I confirm that eix-sync in eix-0.32.4 does not create the previous.eix file if nissing, nor overwrite it if an older version. This bug is NOT resolved.
(In reply to Phil Stracchino (Unix Ronin) from comment #7) > (In reply to Branko Djusic from comment #5) > > It's fixed after eix-sync. > > Um, no, it isn't. I confirm that eix-sync in eix-0.32.4 does not create the > previous.eix file if nissing, nor overwrite it if an older version. This > bug is NOT resolved. Did you have tried to remove previous.eix and portage.eix and then run eix-sync ?
(In reply to Branko Djusic from comment #8) > (In reply to Phil Stracchino (Unix Ronin) from comment #7) > > (In reply to Branko Djusic from comment #5) > > > It's fixed after eix-sync. > > > > Um, no, it isn't. I confirm that eix-sync in eix-0.32.4 does not create the > > previous.eix file if nissing, nor overwrite it if an older version. This > > bug is NOT resolved. > > Did you have tried to remove previous.eix and portage.eix and then run > eix-sync ? I missed the details of the test request. (Thanks grknight for pointing it out.) If I manually move portage.eix to previous.eix, eix-sync and eix-diff then appear to work as expected. If previous.eix is missing, eix-0.32.4 will not create it.
