| Summary: | app-portage/eix-0.25.3 file collision /var/cache/eix | ||
|---|---|---|---|
| Product: | Gentoo Linux | Reporter: | Samuli Suominen (RETIRED) <ssuominen> |
| Component: | Current packages | Assignee: | Martin Väth <martin> |
| Status: | RESOLVED FIXED | ||
| Severity: | normal | CC: | darkside |
| Priority: | Normal | ||
| Version: | unspecified | ||
| Hardware: | All | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Package list: | Runtime testing required: | --- | |
| Attachments: |
build.log
Provide migration path |
||
|
Description
Samuli Suominen (RETIRED)
2012-03-15 01:21:57 UTC
-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" } |