Bug 1740173 - chromium-libs-media-freeworld conflicts because of chromium's release number mismatch
Summary: chromium-libs-media-freeworld conflicts because of chromium's release number ...
Keywords:
Status: CLOSED RAWHIDE
Alias: None
Product: Fedora
Classification: Fedora
Component: chromium
Version: 31
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Tom "spot" Callaway
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2019-08-12 12:09 UTC by Akarshan Biswas
Modified: 2019-08-14 14:19 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2019-08-14 13:53:25 UTC
Type: Bug
Embargoed:

Attachments (Terms of Use)

Description Akarshan Biswas 2019-08-12 12:09:11 UTC 
Description of problem:

Currently chromium-libs-media-freeworld depends on N-V-R of chromium which occassionally breaks because of release number mismatch between the two.

IMO, it can only needs to build once per chromium version and should be independent of fedora's chromium's release. Removing the dependency on release number will help maintaining chromium-libs-media-freeworld.

Only N-V should be enough instead of N-V-R

Is it possible to remove the dependency on Release?

Please refer:
RPMfusion Bug: https://bugzilla.rpmfusion.org/show_bug.cgi?id=5331

This bug targets all "products" and "version" including epel.
Comment 1 Ben Cotton 2019-08-13 17:04:52 UTC 
This bug appears to have been reported against 'rawhide' during the Fedora 31 development cycle.
Changing version to 31.
Comment 2 Ben Cotton 2019-08-13 17:12:35 UTC 
This bug appears to have been reported against 'rawhide' during the Fedora 31 development cycle.
Changing version to '31'.
Comment 3 Tom "spot" Callaway 2019-08-14 13:53:25 UTC 
I've removed the dependency on Release in rawhide, will be picked up on the next set of builds.
Comment 4 Akarshan Biswas 2019-08-14 14:19:27 UTC 
@Tom Thank you.
Note You need to log in before you can comment on or make changes to this bug.