hi Massimo

I would like to know what is the position of the developers of glite 
(and the EMT) in general about the use of "external" repositories/packages.

I see two different alternatives, either

1 - current situation, is to use as much as possible the external repos 
(dag, jpackage, etc.), means the developers don't have to "worry" about
support updates of those packages, but: It can break things, 
dependencies, etc. if the external updates are not followed carefully
since such changes can occur.

2 - past situation, glite (developers/integrators) itself, provide the 
needed external packages through glite/external repo. In this way they 
control which versions to use for the several services, though it's an 
additional burden to eventually support updates (security, others) on 
those packages.

The situation as it occurred, and as I see it, is;
developers (EMT) choose the number 1 above, without the "worries", 
meaning, no checks if new versions of the external packages break anything.

I see this same email thread from time to time in the lcg-rollout
roughly since the situation as changes from #2 to #1, most of the time
having to do with jpackage-utils, bc, jdk, etc.

bear in mind I am trying to clarify things and being constructive, 
because if the EMT choose #1, one as also to worry with it's 
consequences, moreover of course I don't know what is more or less work
if #1 or #2.

I will raise this issue in our RC report because I think it's quite 
relevant from the site admin's point of view

cheers

Mario David


Massimo Sgaravatto - INFN Padova wrote:
> This is being discussed in the EMT mailing list.
> 
> This problem affects other node types (e.g. CREAM).
> 
> Basically the (first) problem is that glite-apel-core requires 
> bouncycastle-jdk1.5.
> In the jpackage repository there is bouncycastle-jdk1.5-1.37-5jpp
> 
> which requires:
> 
>  bouncycastle = 0:1.37
> 
> but in that jpackage repo there isn't anymore  bouncycastle v. 1.37; 
> there is just:
> 
>  bouncycastle-1.41-1.jpp5.noarch.rpm 
> 
> (its date is 13 Nov)
> 
> 
> Even worst, the new bouncyastle v. 1.41 differs wrt the one of version 
> 1.37 (e.g. some jars are installed in different directories) which means 
> that the existing configuration procedures don't work anymore with bc v. 
> 1.41
> 
> 				Cheers, Massimo	
> 
> 
> 
> On Wed, 19 Nov 2008, Ruben diez wrote:
> 
>> Hi...
>>
>> Seems to be a mistake in the yum repository "jpackage.repo" downloaded from
>> http://grid-deployment.web.cern.ch/grid-deployment/glite/repos/
>> according with the documentation at
>> https://twiki.cern.ch/twiki/bin/view/LCG/GenericInstallGuide310#jpackage_and_the_JAVA_repositoryIt provide a bad packed version of the packages "bouncycastle-1.37" and
>> "bouncycastle-jdk1.5-1.37", that produce errors when you attempt to do a
>> "yum update" or, for example, a "yum install lcg-CE".
>>
>> These errors looks like this:
>>
>> Error: Missing Dependency: bouncycastle-jdk1.5 is needed by package
>> glite-apel-core
>>
>> For running fine, you must first:
>>
>> 1- Remove the  jpackage.repo from the "/etc/yum.repos.d" directory.
>>
>> 2- Download and install the files "bouncycastle-1.37-5jpp.noarch.rpm" and
>> "bouncycastle-jdk1.5-1.37-5jpp.noarch.rpm"
>>
>> Can somebody fix this repository mistake???
>>
>> Best regards.
>>
>