Here's the error message we are getting:
Downloading [Unsup-Dccp-1.8.1.tar.gz] from
[http://vdt.cs.wisc.edu/software/questions/1.8.1]...
Package [/usr/local/osg-wn:OSG:wn-client] not [installed]:
Package
[/usr/local/osg-wn:http://vdt.cs.wisc.edu/vdt_181_cache:Unsup-Dccp] not
[installed]:
None of the following alternatives succeeded:
Your os is [SL-3] but it must satisfy [linux-rhel-4].
Your os is [SL-3] but it must satisfy [linux-fedora-4].
Your os is [SL-3] but it must satisfy [linux-suse-9].
None of the following alternatives succeeded:
system processor [x86_64] is not equal to [i686].
Environment variable [VDT_PRETEND_32] has not been set.
None of the following alternatives succeeded:
system processor [x86_64] is not equal to [i686].
Environment variable [VDT_PRETEND_32] has not been set.
None of the following alternatives succeeded:
system processor [x86_64] is not equal to [i686].
Environment variable [VDT_PRETEND_32] has not been set.
Your os is [SL-3] but it must satisfy [linux-debian-3.1].
Your os is [SL-3] but it must satisfy [linux-rhel-5].
Your os is [SL-3] but it must satisfy [linux-sl-fermi-4.0].
Your os is [SL-3] but it must satisfy [linux-rhel-4].
Your os is [SL-3] but it must satisfy [linux-rhel-5].
Your os is [SL-3] but it must satisfy [linux-sl-fermi-4.0].
No download for your platform
Pacman install failed
[root@gaia osg-wn]#
As noted in the previous e-mail, VDT_PRETEND_32 isn't an option here
because the system in question is missing a lot of the other 32-bit
compatibility libraries that this would take.
Steve Timm
On Tue, 6 Nov 2007, VDT support tickets via RT wrote:
> Greetings from the VDT support system!
>
> This message was generated automatically in response to the creation of a
> ticket regarding:
>
> Last-minute addition of Unsup-DCCP
>
> Your original request is copied below for reference.
>
> There is no need to reply to this message right now -- someone from the VDT
> team will respond to you as soon as possible. If you wish to view your
> support ticket online, visit:
>
> http://vdt.cs.wisc.edu/rt/Ticket/Display.html?user=guest&pass=guest&id=3091
>
> Your ticket has been assigned an ID as follows:
>
> [vdt-support #3091]
>
> Please include the ticket ID in the subject line of all future email about
> this issue. To do so, you may reply to this message.
>
> Thank you for your interest in the VDT.
>
>
>
> -------------------------------------------------------------------------
> The last-minute addition of the Unsup-DCCP package to the
> OSG worker node client had the following unexpected effect
> Since Unsup-DCCP apparently is not available for the SL3/x86_64
> platform according to the pacman package, the whole worker
> node client install errors out on a SL3/X86_64 platform.
> I say "apparently" because there's nothing on the VDT matrix
> of supported platforms that says anything about DCCP, I am just
> going with the error messages I got and what I can find from
> looking at the pacman package itself.
>
> This forces us to set
>
> VDT_PRETEND_32=TRUE
> and install a full 32-bit worker node client on a 64-bit machine
> when in fact we should only have to install the one dccp package
> as 32.bit.
>
> This was very shoddy to throw a package in on the very day
> of the OSG release and not having tested it. It's not
> acceptable and we need a fix. You should not be able to break
> a whole OSG package like WN-client just because one piece
> of software is unavailable as 32-bit is just unacceptable. WE expect
> better. In this case, a 64-bit sl3 package for dccp must be provided.
>
> It turns out the install doesn't work either with VDT_PRETEND_32=true
> either because it breaks for other reasons. Which means
> any SL3+x86_64 people are out of luck if they want to install
> a worker node client. Why do we bother to put 2 months of effort
> into participating in the ITB if people are just going to break
> everything on the day of the release?
>
> Steve Timm
>
>
--
------------------------------------------------------------------
Steven C. Timm, Ph.D (630) 840-8525
timm@fnal.gov http://home.fnal.gov/~timm/
Fermilab Computing Division, Scientific Computing Facilities,
Grid Facilities Department, FermiGrid Services Group, Assistant Group Leader.