AG 2.3 Packaging

[Douglas Kosovic]

Hi Chris,

> > See the new BuildSnapshot.py output at:
> > 
> >  http://www.itee.uq.edu.au/~douglask/log/
> > 
> 
> With new build sucking down latest CVS, my build errors are about the
> same as at Doug's link above.

Except in my case, the final product works, although I do get a lot of
"Couldn't find a valid proxy" error messages, see below. I've put up a
new BuildSnapshot.py output on the above link.

> The disturbing thing is the number of references to "No module named
> pyGlobus". That seems to occur while doing some tests, but they are
> significant - during package post-installation phase (compiling AG
> Python modules), I have the following error also related to pyGlobus:

Sounds like pyGlobus isn't getting built. I had to change all references
of gcc32pthr to gcc32dbgpthr in the packaging/linux/fedora dir, because
of the new gcc32dbgpthr Globus flavor before pyGlobus would build
correctly.

> Also, when running certmgr.py, I have:

This is what I get:

$ certmgr.py
 
 
ERROR: Couldn't find a valid proxy.
 
 
ERROR: Couldn't read proxy from:
/etc/AccessGrid/Config/CAcertificates/45cc9e80.0
 
 
ERROR: Couldn't find a valid proxy.
 
 
ERROR: Couldn't read proxy from:
/etc/AccessGrid/Config/CAcertificates/d1b603c3.0
 
 
ERROR: Couldn't find a valid proxy.
 
 
ERROR: Couldn't read proxy from:
/etc/AccessGrid/Config/CAcertificates/1c3f2ca8.0
 
 
ERROR: Couldn't find a valid proxy.
 
 
ERROR: Couldn't read proxy from:
/etc/AccessGrid/Config/CAcertificates/f18fa857.0
(ID mode) >



Doug