| Summary: | A revision bump on net-zope/zope will nuke installed Data.fs | ||
|---|---|---|---|
| Product: | Gentoo Linux | Reporter: | Andy Dustman <farcepest> |
| Component: | Current packages | Assignee: | net-zope (OBSOLETE) <net-zope+disabled> |
| Status: | RESOLVED DUPLICATE | ||
| Severity: | critical | ||
| Priority: | High | ||
| Version: | 1.4 | ||
| Hardware: | All | ||
| OS: | All | ||
| URL: | http://www.zope.org/ | ||
| Whiteboard: | |||
| Package list: | Runtime testing required: | --- | |
The ebuild (2.6.2) defines: ZUID=zope ZGID=$(echo ${P} |sed -e "s:\.:_:g") ZS_DIR=${ROOT}/usr/share/zope/ ZI_DIR=${ROOT}/var/lib/zope/ ZSERVDIR=${ZS_DIR}/${PF}/ ZINSTDIR=${ZI_DIR}/${ZGID} Note that ${P} does not have the revision included. Thus ${ZGID} nor ${ZINSTDIR} have the revision. Therefore if you were to bump the ebuild from 2.6.2 to 2.6.2-r1, you would nuke /var/lib/zope/zope-2_6_2/Data.fs, which is the ZODB which contains the site data. CONFIG_PROTECT might be one way to protect Data.fs. pkg_preinst() is another. We've been lucky so far in that this was introduced in 2.6.0-r2, and 2.6.0-r3 came out shortly thereafter, and since then, there have been no revision bumps.