RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Bug 1978841 - crypto-policies suddenly BuildRequires unwanted python3-coverage
Summary: crypto-policies suddenly BuildRequires unwanted python3-coverage
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Deadline: 2021-07-19
Product: Red Hat Enterprise Linux 9
Classification: Red Hat
Component: crypto-policies
Version: 9.0
Hardware: Unspecified
OS: Unspecified
low
unspecified
Target Milestone: beta
: ---
Assignee: Alexander Sosedkin
QA Contact: Ondrej Moriš
URL:
Whiteboard:
Depends On:
Blocks: 1887522 1897523
TreeView+ depends on / blocked
 
Reported: 2021-07-02 23:30 UTC by Miro Hrončok
Modified: 2021-12-07 21:53 UTC (History)
2 users (show)

Fixed In Version: crypto-policies-20210707-1.git29f6c0b.el9
Doc Type: No Doc Update
Doc Text:
If this bug requires documentation, please select an appropriate Doc Type value.
Clone Of:
Environment:
Last Closed: 2021-12-07 21:50:14 UTC
Type: Bug
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker CRYPTO-5568 0 None None None 2021-12-02 13:05:36 UTC

Description Miro Hrončok 2021-07-02 23:30:16 UTC
Description of problem:
In this commit:

https://gitlab.com/redhat/centos-stream/rpms/crypto-policies/-/commit/7c076748f30246f7f94d6af03de8e4c95f99841c

crypto-policies added BuildRequires on python3-coverage.

But python3-coverage is an unwanted package in RHEL 9 and we are trying to remove the dependencies, so we can remove it.

Version-Release number of selected component (if applicable):
crypto-policies-0:20210628-1.gitdd7d273.el9

How reproducible: Easy


Steps to Reproduce:
1. $ repoquery --repo=RHEL9-BaseOS-source --requires crypto-policies

Actual results:
contains python3-coverage

Expected results:
does not contain python3-coverage

Additional info:
Please remove the BuildRequires. If not possible, let us know ASAP, so we can figure out what to do.

Thanks

Comment 1 Alexander Sosedkin 2021-07-03 11:02:40 UTC
Pity. RHEL already is missing half of the linters we use, what's the deal with that?? Will remove in the next update.

Comment 2 Miro Hrončok 2021-07-03 11:11:39 UTC
I guess the deal is that Red Hat is not in the business of supporting Python code liners for more than a decade, but that is just my personal opinion.

Comment 3 Alexander Sosedkin 2021-07-03 11:15:22 UTC
Well, it's a builddep, so we could abstain from shipping it and offer no customer support. And changes to packages a decade later shouldn't be drastic enough to break decade-old linters anyway... Whatever, down with the likes of flake8, pylint and codespell it goes =(

Comment 5 Miro Hrončok 2021-07-03 16:26:42 UTC
> Well, it's a builddep, so we could abstain from shipping it and offer no customer support.

Internal customers (such as other packagers who use it as BuildRequires, like you just did) exist as well. If you want to keep using is as build dependency, you take over the maintenance of it instead. Do let us know.


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