xpra icon
Bug tracker and wiki

Opened 8 months ago

Closed 6 months ago

#2725 closed defect (wontfix)

libjpeg-turbo packaging version semantics collides with CentOS 7 (base repo)

Reported by: Alex Owned by: Antoine Martin
Priority: major Milestone: 4.1
Component: packaging Version: 3.0.x
Keywords: centos rhel libjpeg-turbo packaging buildbot Cc:

Description

Since #2568 libjpeg-turbo and supplemental packages are included in xpra's repositories for RHEL/CentOS 7, because they're no in the "standard" repository on RHEL.

However, those packages are well in the CentOS Base repository.
Thus identical versions are shipped with xpra to avoid collisions/problems.
Unfortunately, exactly such problems can occur now.

In the xpra-repository the offended package is libjpeg-turbo-1.2.90-8.el7_7.x86_64.
The package in the CentOS 7 base repository is libjpeg-turbo-1.2.90-8.el7.x86_64
Unfortunately the CentOS' variant is el7, so yum considers el7_7 to be a newer version and tries to install that update.
If the system also has the i686-version of the package installed,
yum won't install due to the "protected multilib"-mechanics (Error message: see below).

IMHO xpra should switch to the el7-semantic.
As far as I've got it, it's Buildbot setting %{dist} to el7_7.

MWE:

  1. Install libjpeg-turbo.x86_64 and libjpeg-turbo.i686 on CentOS 7
  2. Enable xpra repository and try to yum install xpra

Expected retult:

  • xpra is installed

Result:

  • xpra is not installed
  • yum update doesn't work anymore

Reason:

Protected multilib versions: libjpeg-turbo-1.2.90-8.el7_7.x86_64 != libjpeg-turbo-1.2.90-8.el7.i686

Change History (2)

comment:1 Changed 8 months ago by Antoine Martin

Status: newassigned

Will switch %{dist} for 4.1.

But... to fix this, I will also need to replace the packages in the repository, deleting the ones with the old filename.

comment:2 Changed 6 months ago by Antoine Martin

Resolution: wontfix
Status: assignedclosed

FYI: CentOS 8.0 needed the package, but 8.1 onwards do not...
It has also appeared in 7.8!

For that reason, I am closing this ticket as wontfix: using the latest version of either branch gives you a working system, without using our home-made libjpeg-turbo packages.

This saves me from a round of package updates and the potential breakage that goes with it.

Note: See TracTickets for help on using tickets.