Note: This web site is only kept up to date for OSG Software 1.2 (VDT 2.0.0). If you are looking for information for the most recent release, the RPM-based OSG Software 3.0, please see the OSG documentation web site

Pacman tips

Tips from Saul:

> pacman -fetch
> pacman -l -d 0 src cmp

to display the compiled source of the offending package.  Nate is
preprocessing heavily these days, so the Pacman source (-d src) is
unreadable.  However, the compiled code (-d cmp) is OK.  Looking at
this, you see a big OR branch on platforms. 

    I don't think it's relevant here, but if you needed Jerry's
processor, you could ask him to do

> pacman -get Demo:system

and send the output of 

> pacman -l system -d cmp

This would give you a list of all the system properties.  

    I tried the install on my RHEL-3 machine here and it's failing in
the same place.  To see the place where it's failing, do

> pacman -l -d 0 

I see the following.  The [*] means that the shell command worked
(defined to mean returning without an error code).  The [X] means that
that is the shell command that fails.

[*] shell vdt-begin-install Globus-RLS-Server
[*] shell gunzip -c vdt_globus_rls_server* | tar xvf -
globus/ > /dev/null
[*] shell globus/ >> vdt-install.log
[*] shell vdt/sbin/vdt-untar vdt_globus_rls_server*
[*] shell globus/ >> vdt-install.log
[*] shell gpt/sbin/gpt-postinstall >> vdt-install.log
[*] shell rm globus/ globus/
[*] shell chmod 644 $VDT_LOCATION/globus/etc/globus-rls-server.conf
[X] shell . $VDT_LOCATION/; .
$VDT_LOCATION/globus/etc/; vdt/setup/configure_rls
[ ] shell vdt/bin/vdt-version -add RLS_SERVER
[ ] shell vdt-end-install

The question is, then, why does this shell command fail?

   I hope that helps.  - Saul

p.s. Also, if you're trying to debug that one shell command, what I
usually do is

$ pacman --fetch

$ pacman -install -ask shell