see https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2017-a4e3aae817
The package build I made with a README.deprecated has reached 14+ days in testing in bodhi.
There was a single comment by anonymous to the effect that RHEL7 has ceph-94.5 with a -1 karma vote which appears to have not been registered in the overall karma somehow. (Last version shipped in epel was 0.80.7.)
What's the next step?
Do I push it to stable and then retire it as soon as it gets pushed?
Just retire it now?
Something else?
Thanks,
On 11 September 2017 at 11:33, Kaleb S. KEITHLEY kkeithle@redhat.com wrote:
see https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2017-a4e3aae817
The package build I made with a README.deprecated has reached 14+ days in testing in bodhi.
There was a single comment by anonymous to the effect that RHEL7 has ceph-94.5 with a -1 karma vote which appears to have not been registered in the overall karma somehow. (Last version shipped in epel was 0.80.7.)
What's the next step?
I would push to stable and then retire it 2 weeks later to make sure it actually gets put in the repository. Otherwise the ceph packages will just disappear before actually you got it there. [This is the 'nature' of the EPEL trees at the moment. There is only a live rawhide build.. something gets retired its gone.]
Do I push it to stable and then retire it as soon as it gets pushed?
Just retire it now?
Something else?
Thanks,
--
Kaleb _______________________________________________ epel-devel mailing list -- epel-devel@lists.fedoraproject.org To unsubscribe send an email to epel-devel-leave@lists.fedoraproject.org
epel-devel@lists.fedoraproject.org