Sure, but there's no point doing that until FEDORA-EPEL-2019-b9d90e26c9 is stable, so you're going to have to wait.
Can you link to docs on how to do this correctly, or file actual bugs? The epel7+epel8 code doesn't work on epel6.
Worked for me on s390x server, thanks.
Also please note that RHEL does not provide ABI (or even API) compat for libkadm5. We only provide compatability for krb5-libs.
Hi, krb5 maintainer here. The rubygem-rkerberos dependency discussion happened on https://bugzilla.redhat.com/show_bug.cgi?id=1330431
Please respond either here or in the bug, not both.
As I mentioned there, there is a separate ticket for KCM failures - https://bugzilla.redhat.com/show_bug.cgi?id=1521110 because gssproxy is not responsible for KCM bugs.
Also -1ing the bug in question is just incorrect as I understand it, since the issue indicated is fixed by the patch (unless I applied it wrong, at which point please say so).
You... reviewed this patch upstream. You can either fix sssd now, or when the next ding-libs release happens, but waiting is just being a stick in the mud. Let's keep working together, please.
Please keep comments to the bugzilla you have filed. The changes are working as intended, and we will work to fix it over there, not in the comments of an update that was submitted to stable a day before you necro'd the comment thread.
krb5 test suite passes on ppc64le; no regressions noted. Thanks!
This update has been unpushed.
Since bodhi didn't do this automatically: obsolete, replaced by FEDORA-2017-9e64a52f34
In #1440885 and #1431272 it is specifically requested that gssproxy be sent SIGHUP, not restarted. Please use systemctl try-reload-or-restart for this purpose.
Resolves issues with previous version (#1445998).
Stack trace on reboot in VM: https://rharwood.fedorapeople.org/screenshots/2017-04-24-153656_3840x1080_scrot.png
Copyright © 2007-2019 Red Hat, Inc. and
bodhi is Free Software.
if you have any problems. Read the documentation.