Bug 609344

Summary:	app-portage/eix-0.32.4 does not update cleanly from previous versions
Product:	Gentoo Linux	Reporter:	Phil Stracchino (Unix Ronin) <phils>
Component:	Current packages	Assignee:	Gentoo Linux bug wranglers <bug-wranglers>
Status:	RESOLVED DUPLICATE
Severity:	normal	CC:	phils
Priority:	Normal
Version:	unspecified
Hardware:	All
OS:	Linux
Whiteboard:
Package list:		Runtime testing required:	---

Description Phil Stracchino (Unix Ronin) 2017-02-14 13:44:20 UTC

app-portage/eix-0.32.4 fails to update existing files when installed as an update to an existing version.  It will first complain that /var/cache/eix/previous.eix is too old a version (34 instead of 37).  If you remove the file, expecting eix to recreate it, eix will complain that it cannot write to it.  If you remove the entire directory trying to trigger a reset, eix will now complain that it can't write to portage.eix either.

The only workaround I have found is:

rm -rf /var/cache/eix
emerge -1 app-portage/eix

This forces the cache directory and files to be properly recreated.

Comment 1 Phil Stracchino (Unix Ronin) 2017-02-14 13:46:45 UTC

Actually, I spoke somewhat too soon; eix will still complain on the next eix-sync that it cannot open previous.eix for reading.

Comment 2 Phil Stracchino (Unix Ronin) 2017-02-15 14:34:15 UTC

So there's actually a set of problems here:
1.  app-portage/eix-0.32.4 cannot use the previous.eix file from an older version of eix
2.  app-portage/eix-0.32.4 cannot overwrite the previous.eix file if it was created by an older version
3.  app-portage/eix-0.32.4 will not create previous.eix if it is missing, it will just complain that it cannot open it.

Comment 3 Brian Evans (RETIRED) gentoo-dev

2017-02-15 14:49:19 UTC


*** This bug has been marked as a duplicate of bug 609264 ***