Bug 1973446 - Please put mobile-broadband-provider-info-devel in RHEL8 CRB
Summary: Please put mobile-broadband-provider-info-devel in RHEL8 CRB
Alias: None
Product: Red Hat Enterprise Linux 8
Classification: Red Hat
Component: mobile-broadband-provider-info
Version: 8.5
Hardware: Unspecified
OS: Unspecified
Target Milestone: beta
: ---
Assignee: Beniamino Galvani
QA Contact: Desktop QE
Depends On:
TreeView+ depends on / blocked
Reported: 2021-06-17 20:19 UTC by Troy Dawson
Modified: 2021-11-10 10:21 UTC (History)
7 users (show)

Fixed In Version: mobile-broadband-provider-info-20190618-2.el8
Doc Type: No Doc Update
Doc Text:
Clone Of:
Last Closed: 2021-11-09 20:04:15 UTC
Type: Bug
Target Upstream Version:

Attachments (Terms of Use)

System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2021:4505 0 None None None 2021-11-09 20:04:18 UTC

Internal Links: 1978454

Description Troy Dawson 2021-06-17 20:19:29 UTC
Description of problem:
mobile-broadband-provider-info-devel is needed to build plasma-nm in EPEL8.
plasma-nm is the network manager interface for KDE Plasma Desktop, and is an important part of the desktop.

Please put mobile-broadband-provider-info-devel in RHEL8 CRB for RHEL 8.5.

Version-Release number of selected component (if applicable):

Comment 1 Josh Boyer 2021-06-21 11:13:08 UTC
This is available in CentOS Stream koji here https://koji.mbox.centos.org/koji/buildinfo?buildID=8373 via the download link.  Is there a reason this must be in the Red Hat product to accomplish what you're trying to do?

Comment 2 Troy Dawson 2021-06-21 13:41:15 UTC
regular EPEL is built off real RHEL.  Not CentOS, CentOS Stream, Oracle Linux, Alma, or Rocky.
If EPEL starts pulling from various koji's and/or builds from other releases, even if they are Red Hat sponsored, where does that stop?

In addition, if we pull from where you suggest, that means we have to setup a whole new infrastucture that keeps track of a various list of packages missing from RHEL, figures out where those missing packages are at on the CentOS koji, and then updates itself each time a package is updated.  That is possible, but judging from our current EPEL volunteer workloads, that will take about 2 years to implement.

Comment 3 Thomas Haller 2021-06-21 14:08:16 UTC
mobile-broadband-provider-info-devel is also a build dependency for NetworkManager.
And so ist teamd-devel and libndp-devel (which also are not installable from RHEL8 nor EPEL8).

Not having these packages available on RHEL8 is highly inconvenient (in my opinion). But to my understanding, this is intentional (I don't know why).

This bug is assigned to the NetworkManager team, but it's unclear how we can fix this (RHEL-CRB?) (or whether we even should). Josh, do you know?

Comment 5 Thomas Haller 2021-06-21 20:01:34 UTC
Josh, bug 1760408 (about libndp-devel and teamd-devel) and the associated RCM ticket ([1]) was NACK'ed.

[1] https://projects.engineering.redhat.com/browse/RCM-68105

That ticket ([1]) was already about adding mobile-broadband-provider-info-devel.

Did something now change and the old decision needs to be re-evaluated?

For the record, personally I am in favor of this rhbz and ticket [1]. I still would be happy if we could avoid the workaround of using a copr repository to get libndp/teamd/mobile-broadband-provider-info devel packages (https://copr.fedorainfracloud.org/coprs/nmstate/nm-build-deps/packages/).

Comment 7 Josh Boyer 2021-06-25 15:33:08 UTC
(In reply to Thomas Haller from comment #5)
> Josh, bug 1760408 (about libndp-devel and teamd-devel) 
> Did something now change and the old decision needs to be re-evaluated?

Yes, something changed.  You can reopen that bug if you would like.

Comment 20 errata-xmlrpc 2021-11-09 20:04:15 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 (mobile-broadband-provider-info 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.


Note You need to log in before you can comment on or make changes to this bug.