The trick to installing update bundles is that they need to be installed all at the same time. If they aren't then GPT may complain about version mis-matches of packages that are shared between the bundles and refuse to do the upgrade. The following exercise illustrates this:
Start with an empty installation location. Download the bundles newfoo-2.0-i686-pc-linux-gnu-bin.tar.gz, newfee-2.0-i686-pc-linux-gnu-bin.tar.gz, newfoo-2.2.3-i686-pc-linux-gnu-bin.tar.gz, and newfee-2.2.3-i686-pc-linux-gnu-bin.tar.gz.
Run gpt-install newfoo-2.0-i686-pc-linux-gnu-bin.tar.gz newfee-2.0-i686-pc-linux-gnu-bin.tar.gz to install the older set of bundles.
Run gpt-install newfoo-2.2.3-i686-pc-linux-gnu-bin.tar.gz to install one bundle upgrade and see the following complaint:
bash$ gpt-install newfoo-2.2.3-i686-pc-linux-gnu-bin.tar.gz ERROR: The following package conflicts were found: globus_openssl-gcc32-rtl ver: 0.10 in bundle newfoo conflicts with globus_openssl-gcc32-rtl ver: 0.1 in bundle newfee globus_openssl-gcc32-pgm ver: 0.10 in bundle newfoo conflicts with globus_openssl-gcc32-pgm ver: 0.1 in bundle newfee globus_common_setup-noflavor-pgm ver: 2.1 in bundle newfoo conflicts with globus_common_setup-noflavor-pgm ver: 2.0 in bundle newfee globus_common-gcc32-rtl ver: 3.5 in bundle newfoo conflicts with globus_common-gcc32-rtl ver: 2.0 in bundle newfee globus_common-gcc32-pgm ver: 3.5 in bundle newfoo conflicts with globus_common-gcc32-pgm ver: 2.0 in bundle newfee
This shows the shared package version mis-match which requires bundle upgrades to be installed at the same time.
Run gpt-install newfoo-2.2.3-i686-pc-linux-gnu-bin.tar.gz newfee-2.2.3-i686-pc-linux-gnu-bin.tar.gz to install the bundle upgrades at the same time..