On 08/14/2017 08:31 AM, Paul Howarth wrote:
On 2017-08-11 19:00, Stephen John Smoogen wrote:
> I have opened 2 tickets in RELENG to have these packages
> removed/blocked for EPEL.
> Packages which are newer in EPEL than RHEL-7.4
> Packages which are older in EPEL than RHEL-7.4 but exist in aarch64,
> x86_64, ppc64, and ppc64le
> The remaining packages which are not in all architectures BUT are very
> old (and may break other things). These need some sort of
> update/rebuild I expect.
I took a look at the three I am maintainer of:
This package is unchanged from the EPEL package, just rebuilt (apart from the
EPEL package having a "0." release prefix to indicate that it's one of the
limited arch packages). I don't really think anything needs to be done with this.
This is basically a clone of the existing EPEL package, with conditionals
added around the python3 package so it doesn't get built for RHEL, which
doesn't have python3.x. Updating this to match the RHEL package would result
in dropping the python3 support, so I think this should be left alone too.
python2-crypto.x86_64 2.6.1-13.el7 epel
python2-crypto.x86_64 2.6.1-15.el7 rhel-7-server-extras-rpms
python34-crypto.x86_64 2.6.1-13.el7 epel
If this is a "limited arch package", shouldn't the release have 0. prefix as
This one has had a version bump to a major new version that uses a different
crypto backend (python-cryptography rather than python-crypto). This one
should be cloned into the epel7 branch, a "0." prepended to Release: and the
python3 package enabled I think.
python-paramiko.noarch 2.1.1-2.el7 rhel-7-server-extras-rpms
python2-paramiko.noarch 1.16.1-2.el7 epel
python34-paramiko.noarch 1.16.1-2.el7 epel
I think you're correct.
Technical Manager 720-772-5637
NWRA, Boulder/CoRA Office FAX: 303-415-9702
3380 Mitchell Lane orion(a)nwra.com
Boulder, CO 80301 http://www.nwra.com