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 1580513 - Add python-futures to comps file for release
Summary: Add python-futures to comps file for release
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: releng
Version: 7.6
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: rc
: ---
Assignee: Lubos Kocman
QA Contact: Release Test Team
URL:
Whiteboard:
Depends On:
Blocks: 1545357
TreeView+ depends on / blocked
 
Reported: 2018-05-21 16:52 UTC by Eng Ops Maitai User
Modified: 2018-10-30 07:22 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2018-10-30 07:21:40 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2018:3014 0 None None None 2018-10-30 07:22:35 UTC

Comment 2 Lubos Kocman 2018-05-22 10:05:16 UTC
Let's agree to do it this way,

I'll add python2-futures to additional development once sos package (/usr/sbin/sosreport) will require it, then it will be distributed to all variants where sosreport is present.

There seems to be tendency to add everything to @base just in case, and I'd like to avoid it.

I'll ask Ondrej Vasik for code-review, just in case he'd disagree.

Lubos

Comment 3 Lubos Kocman 2018-05-22 10:17:49 UTC
Agreed with ovasik and cstratak that we'll add it to @additional-devel but it will be available on all variants due a fact that sos package (/usr/sbin/sosreports) will require it in 7.6

Lubos

Comment 6 Alexander Todorov 2018-07-09 12:21:38 UTC
# pwd
/mnt/redhat/rel-eng/RHEL-7.6-20180626.0/compose

# find -name "python*-futures*"
./Server/source/tree/Packages/python-futures-3.1.1-4.el7.src.rpm
./Server/ppc64/os/Packages/python2-futures-3.1.1-4.el7.noarch.rpm
./Server/ppc64le/os/Packages/python2-futures-3.1.1-4.el7.noarch.rpm
./Server/s390x/os/Packages/python2-futures-3.1.1-4.el7.noarch.rpm
./Server/x86_64/os/Packages/python2-futures-3.1.1-4.el7.noarch.rpm
./Client/source/tree/Packages/python-futures-3.1.1-4.el7.src.rpm
./Client/x86_64/os/Packages/python2-futures-3.1.1-4.el7.noarch.rpm
./ComputeNode/source/tree/Packages/python-futures-3.1.1-4.el7.src.rpm
./ComputeNode/x86_64/os/Packages/python2-futures-3.1.1-4.el7.noarch.rpm
./Workstation/source/tree/Packages/python-futures-3.1.1-4.el7.src.rpm
./Workstation/x86_64/os/Packages/python2-futures-3.1.1-4.el7.noarch.rpm

Comment 8 errata-xmlrpc 2018-10-30 07:21:40 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, 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-2018:3014


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