Hi Frederic, all,
On 2018-05-15 10:50, SCHAER Frederic wrote:
> Repoquery tells me it is indeed ca-policy-lcg which obsoleted lcg-CA – that
> one is hosted on the IGFT repo indeed.
That should have been in the annoucement sent to the sites. It has in
the readme accompanying it:
With the introduction of combined assurance/adequacy, the EGEE compatibility
RPM (lcg-CA) can no longer be supported, and - when still installed - will
be obsoleted. The proper dependency packages are: ca-policy-_body_-_class_
and these have been installed automatically as dependencies since 2010.
The thing is: with the "differentiated assurance" there is actually a choice
to be made when installing the trust anchors - and you should have that
choice after you've installed and configured the proper software (that's
what was introduced in release 1.81 last year, the "-cam" package for EGI).
With that change, it is no longer possible to have that single joint package
from the EGEE days. In 2010 this joint package was superseded by the
ca-policy-egi-core and ca-policy-lcg packages, and now (finally) the old
joint package has also gone - out of necessity.
Just make sure you install both ca-policy-lcg as well as ca-policy-egi-core
if you are part of both WLCG and EGI. Either of these packages
obsoleted the old lcg-CA joint EGEE package.
Cheers,
DavidG.
>
>
>
> Thanks
>
>
>
> *De :*LHC Computer Grid - Rollout [mailto:[log in to unmask]] *De la
> part de* Linda Cornwall - UKRI STFC
> *Envoyé :* mardi 15 mai 2018 10:43
> *À :* [log in to unmask]
> *Objet :* [LCG-ROLLOUT] FW: what happened to the lcg-CA package ?
>
>
>
> Forwarding to David Groep in case he has a comment
>
>
>
> *From:*LHC Computer Grid - Rollout <[log in to unmask]
> <mailto:[log in to unmask]>> *On Behalf Of *SCHAER Frederic
> *Sent:* 15 May 2018 09:35
> *To:* [log in to unmask] <mailto:[log in to unmask]>
> *Subject:* [LCG-ROLLOUT] what happened to the lcg-CA package ?
>
>
>
> It apparently decided to go away with latest CA updates probably replaced by
> ca-policy-lcg…
>
>
>
> Thing is: the puppet/fetchcrl module still references it, and this breaks all
> setups…
>
> https://github.com/voxpupuli/puppet-fetchcrl/blob/master/manifests/params.pp#L40
>
>
>
> What am I missing ?
>
>
>
> Thanks
>
--
David Groep
** Nikhef, Dutch National Institute for Subatomic Physics, PDP programme **
** Room: H1.50 Phone: +31 20 5922179, PObox 41882, NL-1009DB Amsterdam NL **
** PGP: 0xD80134C2 308E076A FP: 2facebea12803ba145685a21d80134c2308e076a **
|