[CREAM-186] Uncompatible packages in EPEL6 Created: 15/Jan/18  Updated: 07/Jan/21  Resolved: 07/Jan/21

Status: Closed
Project: CREAM
Component/s: None
Affects Version/s: None
Fix Version/s: None
Security Level: Public (Visbile by non-authn users.)

Type: Task Priority: Major
Reporter: Paolo Andreetto Assignee: Paolo Andreetto
Resolution: Won't Do Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified


 Description   

There is an update coming to EPEL 6 involving some Java components.
There are updated packages for:

  • bouncycastle-1.58-2.el6: The new package uses the new bouncycastle package build mechanism used in the Fedora bouncycastle package, building all bouncycastle binary packages from the same source RPM:
    • bouncycastle-1.58-2.el6.noarch.rpm
    • bouncycastle-mail-1.58-2.el6.noarch.rpm
    • bouncycastle-pg-1.58-2.el6.noarch.rpm
    • bouncycastle-pkix-1.58-2.el6.noarch.rpm
    • bouncycastle-tls-1.58-2.el6.noarch.rpm
      previously, only bouncycastle itself was in EPEL 6. This update adds the others to the EPEL 6 repository. A bouncycastle-mail package was provided in the UMD repo.
  • jglobus-2.1.0-4.el6 (I guess noone is using this...)
  • voms-api-java-3.2.0-7.el6

The update also adds packages previously not in EPEL 6 due to missing
bouncycastle dependencies:

  • canl-java-2.5.0-1.el6
  • voms-clients-java-3.0.7-6.el6

With this update there are some changes w.r.t. the packages currently
in UMD:

  1. Since voms-api-java is updated to version 3, the voms-api-java3
    currently in UMD becomes obsolete, so references to
    /usr/share/java/voms-api-java3.jar
    should be changed to
    /usr/share/java/voms-api-java.jar
  2. In the new bouncycastle version some classes have moved between the
    different bouncycastle packages.

The new canl-java depends on bouncycastle and bouncycastle-pkix.
The new voms-api-java depends on canl-java (and hence on bouncycastle
and bouncycastle-pkix), but no longer on bouncycastle-mail.

Providers of products depending on these components should investigate
compatibility and see what changes are needed to code and
configuration. The import of this update into UMD will be coordinated.

Packages declaring dependencies on the affected packages in the UMD
repo are:

  • glite-ce-common-java
  • glite-ce-cream-api-java
  • argus-pap
  • argus-pdp
  • argus-pep-server

(These are the directly declared dependencies, some recursive
dependencies might be affected too.)

 Comments   
Comment by Paolo Andreetto [ 21/May/18 ]

I've repackaged the CREAM CE in order to support the latest version of CAnL, Bouncycastle and VOMS api java on SL6.
The following tags are available:

  • cream-parent_R_1_0_4_1
  • canl-java-tomcat_R_0_1_19_1
  • cream-common_R_1_16_5_2
  • cream-api-java_R_1_16_6_3
  • cream_R_1_16_5_4

I've included also the latest version of BLAH stable (v. 1.22.2), already published for CentOS7.

The priority for the YUM repository in certification MUST be the following:

  1. CREAM CE
  2. EPEL
  3. UMD-4
Comment by Paolo Andreetto [ 15/May/18 ]

During the last URT meeting a revision of bouncycastle on SL6 has been scheduled.
So for the moment the release of CREAM on SL6 is suspended, waiting for the outcames of that task.

Comment by Paolo Andreetto [ 14/May/18 ]

With the latest version of voms-api-java there's a broken link in the installation of the CREAM CE:

/var/lib/tomcat6/webapps/ce-cream/WEB-INF/lib/voms-api-java3.jar -> /usr/share/java/voms-api-java3.jar

A temporary workaround is creating a new symbolic link:

ln -s /usr/share/java/voms-api-java.jar /usr/share/java/voms-api-java3.jar

but it is necessary to release a new version of glite-ce-cream

Generated at Sat Apr 27 04:42:53 CEST 2024 using Jira 9.12.5#9120005-sha1:fa8821cdb090f6b5ec0424ddb13fa19bc92d8429.