I cannot see that bug report as it is restricted. Can you summarize? Also can't the prior version also be retained and have both available so the masses can pin to a functioning version to install? The new version will still be the default.
Luckily for me I was able to find an epel mirror that had not been update so I have a working system. I also control my clients internal mirror so I can ensure we have a working version until CentOS 7.5 gets released, other would not necessarily have this option. Not having this available totally breaks Foreman installs for the majority of the masses as it currently stands.
The rubygem-rkerberos folks (Satellite) have been aware this was going to happen for several releases now. The rationale for dropping it in general is that we can't actually provide the guarantees that keeping the version locked means. In particular, with this change, we introduce a new admin plugin and there's a good chance that will leak into the kadm5 interface (which is not stable, nor do we guarantee it as such).
BTW the older versions of the package are still available in Koji:
As of yesterday (as I write this) CentOS 7.5 has been released, so I suspect that is the most appropriate way forward at this time. Seems I was just two days ahead on my timing when installing Foreman/Foreman-proxy.
This update has been submitted for testing by vondruch.
This update has been pushed to testing.
+1
karma: +1
+1
+1
+1
karma: +1
This update has reached 14 days in testing and can be pushed to stable now if the maintainer wishes
This update has been submitted for batched by vondruch.
This update has been submitted for stable by bodhi.
This update has been pushed to stable.
-1 It is now broken for CentOS 7.4 since 7.4 still only installs libkadm5clnt_mit.so.8.0. I suspect a there is a better fix for this.
@gpotts: Sorry for breaking CentOS 7.4, but unfortunately, there is no way around it :/ See https://bugzilla.redhat.com/show_bug.cgi?id=1462982#c6 for more information.
I cannot see that bug report as it is restricted. Can you summarize? Also can't the prior version also be retained and have both available so the masses can pin to a functioning version to install? The new version will still be the default.
Luckily for me I was able to find an epel mirror that had not been update so I have a working system. I also control my clients internal mirror so I can ensure we have a working version until CentOS 7.5 gets released, other would not necessarily have this option. Not having this available totally breaks Foreman installs for the majority of the masses as it currently stands.
which epel mirror that not been update so I can download the rpm package? I ran into the same issue here too.
I found it here: https://mirrors.sonic.net/epel/7/x86_64/Packages/r/rubygem-rkerberos-0.1.3-5.el7.x86_64.rpm
Better hurry though.I suspect it just may just be a matter of time before it gets over written with the new one.
Thank you kindly!
No worries. Glad to assist.
This is from the bug:
BTW the older versions of the package are still available in Koji:
https://koji.fedoraproject.org/koji/packageinfo?packageID=17179
@gpotts the comment in BZ should be accessible now.
Actually I was wrong, it is not public :( sorry for the noise.
Hi, krb5 maintainer here. The rubygem-rkerberos dependency discussion happened on https://bugzilla.redhat.com/show_bug.cgi?id=1330431
Also please note that RHEL does not provide ABI (or even API) compat for libkadm5. We only provide compatability for krb5-libs.
As of yesterday (as I write this) CentOS 7.5 has been released, so I suspect that is the most appropriate way forward at this time. Seems I was just two days ahead on my timing when installing Foreman/Foreman-proxy.