This update has been submitted for testing by branto.
"stable threshold: 1" is not good for EPEL
We need this ASAP for ceph upstream testing !
@ktdreyer: I was not too happy to use it either but it is pretty safe given there is no actual source code change and the similar (drop two packages) change went through the usual 14-days long testing period without anyone arguing about it.
This update has been pushed to testing.
btw: Testing on a rhel 7.2 with ceph + epel-testing repo enabled (and epel repo disabled), the 'yum install ceph-devel' command that failed previously works just fine, now.
@branto, how about yum install python-cephfs ?
yum install python-cephfs
or yum install python-ceph
yum install python-ceph
@ktdreyer: Both of these work as expected (*). It were only the packages that were in the repos twice (base + epel) and did not exist in upstream firefly repo (i.e. were split) that posed a problem, here.
(*) yum install python-cephfs won't install anything in that case -- python-cephfs is masked properly by yum-plugin-priorities wih check_obsoletes on. On the other hand, if you disable upsream repo and enable epel, it will install python-cephfs (with deps) as expected.
(*) yum install python-ceph will simply install python-ceph package from upstream firefly repo. On the other hand, if you disable upsream repo and enable epel repo, it will install python-ceph-compat (with deps) as expected.
Cool, thanks for testing that.
Would like to see this land
This update has been submitted for stable by bodhi.
This looks good here
This update has been pushed to stable.
Please login to add feedback.
Confirm request to re-trigger tests.
Copyright © 2007-2019 Red Hat, Inc. and
bodhi is Free Software.
if you have any problems. Read the documentation.