Created attachment 305405 [details] build.log [ebuild U ] app-portage/eix-0.25.3 [0.25.0] USE="dep nls -debug -doc -optimization -security -sqlite -strong-optimization -tools -zsh-completion" 0 kB >>> Installing (1 of 1) app-portage/eix-0.25.3 * checking 19 files for package collisions * This package will overwrite one or more files that may belong to other * packages (see list below). You can use a command such as `portageq * owners / <filename>` to identify the installed package that owns a * file. If portageq reports that only one package owns a file then do * NOT file a bug report. A bug report is only useful if it identifies at * least two or more packages that are known to install the same file(s). * If a collision occurs and you can not explain where the file came from * then you should simply ignore the collision since there is not enough * information to determine if a real problem exists. Please do NOT file * a bug report at http://bugs.gentoo.org unless you report exactly which * two packages install the same file(s). Once again, please do NOT file * a bug report unless you have completely understood the above message. * * package app-portage/eix-0.25.3 NOT merged * * Detected file collision(s): * * /var/cache/eix * * Searching all installed packages for file collisions... * * Press Ctrl-C to Stop * * None of the installed packages claim the file(s). * * Package 'app-portage/eix-0.25.3' NOT merged due to file collisions. If * necessary, refer to your elog messages for the whole content of the * above message.
-rw-rw-r-- 1 portage portage 5332298 Mar 15 02:01 /var/cache/eix rm -f it -> update -> now it's a directory in 0.25.3. but eix's ebuild should take care of the old cache file, propably punt it from pkg_preinst() to allow succesful emerge.
(In reply to comment #1) > -rw-rw-r-- 1 portage portage 5332298 Mar 15 02:01 /var/cache/eix > > rm -f it -> update -> now it's a directory in 0.25.3. but eix's ebuild > should take care of the old cache file, propably punt it from pkg_preinst() > to allow succesful emerge. 1) known. 2) Questionable on the proper way to do it. Suggestions? Patch? *eix-0.25.3 (14 Mar 2012) 14 Mar 2012; Jeremy Olexa <darkside@gentoo.org> +eix-0.25.3.ebuild: Version bump from upstream. Due to filesystem layout changes, there WILL be a file collision for /var/cache/eix. It is safe to remove this file and then regenerate it with 'eix-update'
Created attachment 305417 [details, diff] Provide migration path
(In reply to comment #3) > Created attachment 305417 [details, diff] [details, diff] > Provide migration path bah, just drop the ebegin/eend crap from this one and it's good enough imho
Ok, thanks. + 15 Mar 2012; Jeremy Olexa <darkside@gentoo.org> eix-0.25.3.ebuild: + Add file collision avoidance logic by Samuli Suominen in bug 408249
Would it make sense to delete /var/cache/eix.previous, too? It's handled in /var/cache/eix/ Otherwise this would create another orphaned file in filesystem.
(In reply to comment #6) > Would it make sense to delete /var/cache/eix.previous, too? It's handled in > /var/cache/eix/ > > Otherwise this would create another orphaned file in filesystem. Not critical & already handled. pkg_postinst() { # fowners in src_install doesn't work for owner/group portage: # merging changes this owner/group back to root. use prefix || chown portage:portage "${EROOT}var/cache/${PN}" local obs="${EROOT}var/cache/eix.previous" ! test -f "${obs}" || ewarn "Found obsolete ${obs}, please remove it" }
