heimdal has gss_store_cred_into implementation in the git (commits from the start of January 2019). However, this hasn't been released yet. This makes >=postgresql-16[kerberos] fail in configure phase.
The title is kind of interesting because it implies it fails with a newer version, but we're in the unusual situation here of something needing an API which is in no released version. I wonder why they've done that. Does app-crypt/mit-krb5 provide the needed API? I assume it must do.
Can't read their minds. Yet, the closed merge request (https://github.com/heimdal/heimdal/issues/451) references the (now implemented) proposal in MIT implementation. Given that it's close to 5 years old, it's likely this falls under bad release cycle choices on the part of heimdal team - given that they did have an implementation shortly afterwards and postgresql team likely just decided 5 years should be enough.
The bug has been closed via the following commit(s): https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=9ca835d2b722f3612180172ff8f8675fad19b017 commit 9ca835d2b722f3612180172ff8f8675fad19b017 Author: Patrick Lauer <patrick@gentoo.org> AuthorDate: 2024-01-16 08:19:18 +0000 Commit: Patrick Lauer <patrick@gentoo.org> CommitDate: 2024-01-16 08:22:05 +0000 dev-db/postgresql: Fix kerberos support for >=16 According to upstream heimdal is actively not supported anymore. Switch from virtual/krb5 to app-crypt/mit-krb5 Closes: https://bugs.gentoo.org/919096 Signed-off-by: Patrick Lauer <patrick@gentoo.org> dev-db/postgresql/postgresql-16.0.ebuild | 2 +- dev-db/postgresql/postgresql-16.1.ebuild | 2 +- dev-db/postgresql/postgresql-9999.ebuild | 2 +- 3 files changed, 3 insertions(+), 3 deletions(-)
