Bug 1949422

Summary: Installing totem via dnf does not behave as expected
Product: Red Hat Enterprise Linux 9 Reporter: Michal Odehnal <modehnal>
Component: totemAssignee: Kalev Lember <klember>
Status: CLOSED ERRATA QA Contact: Jiri Prajzner <jprajzne>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 9.0CC: james.antill, jkoten, jprajzne, klember, tpelka, vbudikov
Target Milestone: betaKeywords: Reopened, Triaged
Target Release: ---Flags: pm-rhel: mirror+
Hardware: x86_64   
OS: Linux   
Whiteboard:
Fixed In Version: totem-3.38.2-2.el9 Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2023-11-07 08:35:32 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
reproducer none

Description Michal Odehnal 2021-04-14 09:13:20 UTC
Created attachment 1771811 [details]
reproducer

Description of problem:
Installing totem via dnf does not behave as expected.

Version-Release number of selected component (if applicable):
totem-3.38.0-5.el9.x86_64
totem-video-thumbnailer-1:3.38.0-5.el9.x86_64

How reproducible:
100%

Steps to Reproduce:
1. Try to install totem via dnf command.
2. $ dnf install totem
3.

Actual results:
Package totem-video-thumbnailer-1:3.38.0-5.el9.x86_64 is already installed.

Expected results:
Correct totem package to be fetched and installed

Additional info:
'$ dnf erase totem' will erase the correct package and not the totem-video-thumbnailer

I can install the totem if I specify it for example as '$ dnf install totem.x86_64'

Comment 1 Kalev Lember 2021-04-14 09:21:37 UTC
This sounds like a dnf bug to me.

Comment 2 Michal Odehnal 2021-04-14 09:25:49 UTC
Switching to dnf based on Kalev's comment.

Comment 3 Kalev Lember 2021-04-14 09:35:45 UTC
As a bit of background, we added "Obsoletes: totem < 1:3.38.0-4" to both totem and totem-video-thumbnailer packages to get RHEL gating to pass: otherwise it would try to install old totem and new totem-video-thumbnailer and get file conflicts and fail the gating.

So now we have two packages that have "Obsoletes: totem < 1:3.38.0-4". The 'totem' and 'totem-video-thumbnailer' packages are both at EVR 1:3.38.0-5.

With this, dnf somehow seems to think that installed 'totem-video-thumbnailer' package satisfies 'totem' when trying to install it on the command line, even though totem 1:3.38.0-5 is available in the repos.

Note that there are no explicit 'Provides: totem' so the only package that provides the totem name is the 'totem' package.

I suspect dnf is doing something wrong here (we could easily enough "fix" it on the totem side I think by removing the obsoletes; this is however a standard pattern to do package split and dnf should get fixed to handle it correctly).

Comment 4 Lukáš Hrázký 2021-04-20 09:06:07 UTC
Hello Kalev, I don't think your "fix" is correct and therefore likely not standard :)

With an "Obsoletes", you're saying that the obsoleting package is fully replacing the obsoleted one. This clearly isn't the case here. the "totem Obsoletes: totem < 1:3.38.0-4" one seems purely redundant to me. The "totem-video-thumbnailer Obsoletes: totem < 1:3.38.0-4" one basically says that you can now use totem-video-thumbnailer instead of totem to get the same functionality.

It would appear totem-video-thumbnailer was split off totem with a small part of its functionality. You have "Requires: totem-video-thumbnailer(x86-64) = 1:3.38.0-6.el9" in totem, that should be good for the most part.

> ... otherwise it would try to install old totem and new totem-video-thumbnailer and get file conflicts and fail the gating.

From what I can see you need a "Conflicts: totem < 1:3.38.0-4" in totem-video-thumbnailer to prevent that situation.

Comment 5 Lukáš Hrázký 2021-06-03 09:59:35 UTC
Reassigning to totem as it seems to me like a bug in packaging, but feel free to point out any issues with my analysis...

Comment 6 Bastien Nocera 2021-06-08 08:39:42 UTC
Reassigning to Kalev, as he made that change in Fedora as well.

Comment 7 Michal Odehnal 2022-06-23 05:22:34 UTC
I still encounter this issue.

Comment 12 RHEL Program Management 2022-11-01 07:28:58 UTC
After evaluating this issue, there are no plans to address it further or fix it in an upcoming release.  Therefore, it is being closed.  If plans change such that this issue will be fixed in an upcoming release, then the bug can be reopened.

Comment 13 Kalev Lember 2023-05-15 10:33:17 UTC
Sorry, this one completely fell off my radar. Looking back at the git changelog, I apparently pushed a fix for this to Fedora dist-git - https://src.fedoraproject.org/rpms/totem/c/b9f5e4a88777f57913312beb9ca0a5c715f65fde?branch=rawhide , but it never landed in RHEL.

Comment 21 errata-xmlrpc 2023-11-07 08:35:32 UTC
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory (totem bug fix and enhancement update), and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHBA-2023:6495