On Tue, Oct 26, 2021 22:52:40 -0400, Matthew Miller wrote:
> On Fri, Oct 22, 2021 at 03:56:42PM +0100, Ankur Sinha wrote:
> > If it's a general issue, it'll break kinit etc. for all package
> > maintainers as soon as they get the update. (Running `fedpkg
> > new-sources` was how I ran into the
On Fri, Oct 22, 2021 at 03:56:42PM +0100, Ankur Sinha wrote:
> If it's a general issue, it'll break kinit etc. for all package
> maintainers as soon as they get the update. (Running `fedpkg
> new-sources` was how I ran into the issue).
I can't reproduce, but I'm _just_ using Fedora kerberos.
On Mon, Oct 25, 2021 10:41:44 +0200, Pavel Březina wrote:
>
> I've unpushed the package so far, so it won't be pushed to stable. Please
> open a bugzilla with KCM logs attached. Also please, provide output of
> failing klist with krb5 tracing enabled (KRB5_TRACE=/dev/stderr).
Thanks very much. I
On 10/22/21 16:56, Ankur Sinha wrote:
Hi folks,
I just updated two F35 systems with updates-testing enabled and then
`klist` etc. stopped working for me. Some investigation seems to
indicate that the sssd-2.6.0 update may be involved---downgrading back
to 2.5.2 immediately fixes the issue on
On Sat, Oct 23, 2021 14:09:55 +0300, Otto Urpelainen wrote:
> Ankur Sinha kirjoitti 22.10.2021 klo 17.56:
>
>
> Hi,
Hi,
>
> I am sure exactly what should break, but I could not reproduce this:
Thanks for testing it out.
> 1. $ sudo dnf upgrade --enablerepo=updates-testing
>
Ankur Sinha kirjoitti 22.10.2021 klo 17.56:
Hi folks,
I just updated two F35 systems with updates-testing enabled and then
`klist` etc. stopped working for me. Some investigation seems to
indicate that the sssd-2.6.0 update may be involved---downgrading back
to 2.5.2 immediately fixes the issue
Hi folks,
I just updated two F35 systems with updates-testing enabled and then
`klist` etc. stopped working for me. Some investigation seems to
indicate that the sssd-2.6.0 update may be involved---downgrading back
to 2.5.2 immediately fixes the issue on both systems. The update
however, has 3+
