Bugzilla Bug 58562

See thread http://forums.gentoo.org/viewtopic.php?p=1383051

The leading / in the config is the culprit

Change ebuild lines:
ZS_DIR=${ROOT}/usr/lib/
ZI_DIR=${ROOT}/var/lib/zope/
to
ZS_DIR=${ROOT}usr/lib/
ZI_DIR=${ROOT}var/lib/zope/

Note that the slash has been removed from before usr and var in the above change. This won't work if ${ROOT} isn't or doesn't end in a single /, but I'll defer more general solutions to the ebuild experts. 

# diff -u /usr/portage/net-zope/zope/zope-2.7.2.ebuild /usr/local/portage/net-zope/zope/zope-2.7.2.ebuild
--- /usr/portage/net-zope/zope/zope-2.7.2.ebuild        2004-07-25 05:37:45.000000000 -0500
+++ /usr/local/portage/net-zope/zope/zope-2.7.2.ebuild  2004-07-27 12:12:56.533988704 -0500
@@ -26,8 +26,8 @@
 ZUID=zope
 ZGID=zope
 ZGID_INST="$(echo ${PN}-${PV} | sed -e 's/\./_/g' )"
-ZS_DIR=${ROOT}/usr/lib/
-ZI_DIR=${ROOT}/var/lib/zope/
+ZS_DIR=${ROOT}usr/lib/
+ZI_DIR=${ROOT}var/lib/zope/
 ZSERVDIR=${ZS_DIR}${PN}-${PV}/
 ZINSTDIR=${ZI_DIR}${PN}-${PV}


Reproducible: Always
Steps to Reproduce:

Actual Results:  
With the above edit, Zope instance can be configured easily as the ebuild author
intended.

I wanted to change it from 'blocker' status, since the fix I provided is fairly
small, and some users can do it themselves.

However, I'm finding that there are ripple effects and/or additional
'double-slashes' in the various paths built up from path variables. One example
is the copy command for the skel directory. I'll quote that at the bottom of
the message:

Here's the simplest demonstration of the initial leading extraneous
double-slash. Bash doesn't mind them, but python startup code does:

# ebuild /var/db/pkg/net-zope/zope-2.7.2/zope-2.7.2.ebuild config
 * Creting default zope instance at //var/lib/zope/zope-2.7.2 with command:
 * /usr/sbin/zope-config --zserv=//usr/lib/zope-2.7.2/
--zinst=//var/lib/zope/zope-2.7.2 --zgid=zope-2_7_2 --zinituser
 * Default admin user created with password admin. Please change it.
Adding user zope to group zope-2_7_2
Note: Review settings in //var/lib/zope/zope-2.7.2/etc/zope.conf.
Then you can start your new instance with:
        /etc/init.d/zope-2.7.2 start
 * You can also enable autostart on reboot using: rc-update -a zope-2_7_2
default

# /etc/init.d/zope-2.7.2 start
 * Re-caching dependency info (mtimes differ)...
 * Starting Zope in //var/lib/zope/zope-2.7.2...
Traceback (most recent call last):
  File "//usr/lib/zope-2.7.2/lib/python/Zope/Startup/zopectl.py", line 241, in
?
    main()
  File "//usr/lib/zope-2.7.2/lib/python/Zope/Startup/zopectl.py", line 221, in
main
    options.realize(args)
  File "//usr/lib/zope-2.7.2/lib/python/Zope/Startup/zopectl.py", line 90, in
realize
    ZDOptions.realize(self, *args, **kw)
  File "//usr/lib/zope-2.7.2/lib/python/zdaemon/zdoptions.py", line 271, in
realize
    self.load_schema()
  File "//usr/lib/zope-2.7.2/lib/python/zdaemon/zdoptions.py", line 312, in
load_schema
    self.schema = ZConfig.loadSchema(self.schemafile)
  File "//usr/lib/zope-2.7.2/lib/python/ZConfig/loader.py", line 37, in
loadSchema
    return SchemaLoader().loadURL(url)
  File "//usr/lib/zope-2.7.2/lib/python/ZConfig/loader.py", line 69, in loadURL
    r = self.openResource(url)
  File "//usr/lib/zope-2.7.2/lib/python/ZConfig/loader.py", line 104, in
openResource
    raise error
ZConfig.ConfigurationError: error opening resource
file:////usr/lib/zope-2.7.2/lib/python/Zope/Startup/zopeschema.xml: [Errno ftp
error] no host given                        

The ebuild probably needs a careful audit of trailing-slash use to establish a
consistent convention for all the complex directory building.

I don't know of any way to debug an ebuild other than adding a bunch of einfo
calls to print the expanded path variables.

Ripple Effect
-----------------
Fixing the first case of the double slashes with the following diff

# diff -u /usr/portage/net-zope/zope/zope-2.7.2.ebuild
/usr/local/portage/net-zope/zope/zope-2.7.2.ebuild
--- /usr/portage/net-zope/zope/zope-2.7.2.ebuild        2004-07-27
11:12:26.000000000 -0500
+++ /usr/local/portage/net-zope/zope/zope-2.7.2.ebuild  2004-07-28
11:23:25.222682424 -0500
@@ -26,8 +26,8 @@
 ZUID=zope
 ZGID=zope
 ZGID_INST="$(echo ${PN}-${PV} | sed -e 's/\./_/g' )"
-ZS_DIR=${ROOT}/usr/lib/
-ZI_DIR=${ROOT}/var/lib/zope/
+ZS_DIR=${ROOT}usr/lib/
+ZI_DIR=${ROOT}var/lib/zope/
 ZSERVDIR=${ZS_DIR}${PN}-${PV}/
 ZINSTDIR=${ZI_DIR}${PN}-${PV}

leads to a single error in copying the skel file tree. I have been trying to
track this down, but I don't seem to have any success.

(unmerge portage zope, zope-config, all instances and config files in /etc)

# ebuild /var/db/pkg/net-zope/zope-2.7.2/zope-2.7.2.ebuild config
 * Creting default zope instance at /var/lib/zope/zope-2.7.2 with command:
 * /usr/sbin/zope-config --zserv=/usr/lib/zope-2.7.2/
--zinst=/var/lib/zope/zope-2.7.2 --zgid=zope-2_7_2 --zinituser
 * Default admin user created with password admin. Please change it.
install: cannot stat `/usr/lib/zope-2.7.2//skel/zope.initd': No such file or
directory
Adding user zope to group zope-2_7_2
Note: Review settings in /var/lib/zope/zope-2.7.2/etc/zope.conf.
Then you can start your new instance with:
        /etc/init.d/zope-2.7.2 start
 * You can also enable autostart on reboot using: rc-update -a zope-2_7_2
default

Well, it should be posible to get rid of the optional tailing / in ROOT using:

ZS_DIR=${ROOT%/}/usr/lib/
ZI_DIR=${ROOT%/}/var/lib/zope/

J

Well, it should be posible to get rid of the optional tailing / in ROOT using:

ZS_DIR=${ROOT%/}/usr/lib/
ZI_DIR=${ROOT%/}/var/lib/zope/

Jürgen

I posted a fix to this bug in bug 59217. (I squashed both bugs in one fell
swoop!)

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