Upgrading from unsupported Globus Toolkit 5.2 packages to Globus Toolkit 6.0

Fedora/CentOS/RHEL/Scientific

There is no issue here because all supported repo versions are using GT 6.

Debian/Ubuntu

This is an issue for Debian 7, 8 and Ubuntu 12.04, 14.04.

For Debian 7 and 8, GT 6 has been added to the versions backports repo. See instructions below for upgrading.

For Ubuntu 12.04, we do not have plans for adding GT6 to its' backport repo because it will be going out of support soon and to our knowledge, this is not needed by the Globus community.

For Ubuntu 14.04, no one has needed support for this yet. We will if there is sufficient need. Contact me if you will need support for this.

Upgrade from Debian distro repo versions to either backports or GT repo versions

The Globus repo is recommended if you will be using the Globus packages only, and aren't using other packages from backports that depend on Globus packages. The packages in this repo will probably be updated faster/more frequently than the packages in backports, but there could be compatibility issues if you are using other packages in backports that depend on the Globus packages in backports.

To go from distro repo to Globus repo:

  1. Remove packages currently on system that were installed from distro repo that will be replaced by packages from the Globus repo
    • If all Globus packages were installed from distro repo then something like: apt-get remove ".*globus.*"
    • For MyProxy: apt-get remove ".*myproxy.*"
    • For gsi-openssh: apt-get remove gsi-openssh.*
    • This will remove packages but preserve config files
  2. Install Globus repo
    • wget http://toolkit.globus.org/ftppub/gt6/installers/repo/globus-toolkit-repo_latest_all.deb
    • dpkg -i globus-toolkit-repo_latest_all.deb
  3. Install desired Globus packages from Globus repo
    • e.g. - apt-get install globus-gridftp-server-progs myproxy-server myproxy-admin
    • If/when prompted, keep old config files
  4. Start services and test functionality
    • There is a chance that there may have been changes to the syntax for certain options in the config files for some components of the Globus Toolkit from the version of the Globus Toolkit you were using to GT6. If any of the services don't start or don't function properly, then check the config files for that service against the GT 6 documentation for that service here:

The backports repo is recommended if you are using other packages from backports that depend on the Globus packages you want to use.

To go from distro repo to backports repo:

  1. Remove Globus packages currently on system that were installed from distro repo
    • If all Globus packages were installed from distro repo then something like: apt-get remove ".*globus.*"
    • This will remove packages but preserve config files
  2. Enable backports repo
  3. Install desired Globus packages from backports repo
    • e.g. - apt-get -t NAME_OF_BACKPORTS_REPO globus-gridftp-server-progs
      • Alternately, it is possible to create a .pref file in /etc/apt/preferences.d/ and specify a set of packages you'd like to automatically be pulled from the backports repo without having to use the -t option to explicitly declare this when installing the package - e.g.:
          Package: globus-* libglobus-*
          Pin: release a=NAME_OF_BACKPORTS_REPO
          Pin-Priority: 500
      • With a file in /etc/apt/preferences.d/ specifying the above config, the following command would then automatically pull the specified packages from the backports repo:
        • apt-get globus-gridftp-server-progs globus-core globus-gram-job-manager
      • This method should only be used if you're certain that you want any package matching the specified pattern to automatically be pulled from the backports repo.
    • If/when prompted, keep old config files
  4. Start services and test functionality
    • There is a chance that there may have been changes to the syntax for certain options in the config files for some components of the Globus Toolkit from the version of the Globus Toolkit you were using to GT6. If any of the services don't start or don't function properly, then check the config files for that service against the GT 6 documentation for that service here: