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

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

https://code.engineering.redhat.com/gerrit/gitweb?p=comps.git;a=commit;h=ab1041ac294ead62f9f950a6f68a6a94875e989e

# 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

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