From: inzanez <inzanez@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: sssd: update to 2.2.3.
Date: Sat, 19 Sep 2020 20:19:09 +0200 [thread overview]
Message-ID: <20200919181909.KqJzjUqNvNgCzxZgtu6bboMswmC79ZP2aoQ22tIBCHw@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-24969@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 1121 bytes --]
New comment by inzanez on void-packages repository
https://github.com/void-linux/void-packages/pull/24969#issuecomment-695340327
Comment:
Well, what I meant is basically that the sssd client did not start up with package 2.0. It logged an error message and exited.
Building package 2.3 without kerberos support did build well, but did not start up sssd either. It exited with errors again.
To build sssd with kerberos support, it requires a version of bind with kerberos support. That‘s one reason I submitted a PR for the bind upgrade to include kerberos support.
I have not built and tested your PR, so I cant say if I will face the same issues as before with version 2.0. I have built 2.3 myself including kerberos support and that changed the binary from ‚not running‘ to ‚working as expected‘. And as your PR doesnt seem to include kerberos, I fear that I might not be able to run the resulting binary, even if it compiles.
I will test this PR tonight. I wonder how you managed to build 2.3 without patching code. I needed to patch because of some ‚openssl‘ vs. ‚libressl‘ incompatibility.
next prev parent reply other threads:[~2020-09-19 18:19 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-18 14:43 [PR PATCH] " ahesford
2020-09-18 16:14 ` inzanez
2020-09-18 21:43 ` inzanez
2020-09-19 17:12 ` ahesford
2020-09-19 18:16 ` inzanez
2020-09-19 18:19 ` inzanez [this message]
2020-09-19 18:38 ` ahesford
2020-09-20 8:39 ` inzanez
2020-09-20 13:56 ` [PR PATCH] [Updated] " ahesford
2020-09-20 13:57 ` ahesford
2020-09-20 15:04 ` [PR PATCH] [Merged]: " ahesford
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20200919181909.KqJzjUqNvNgCzxZgtu6bboMswmC79ZP2aoQ22tIBCHw@z \
--to=inzanez@users.noreply.github.com \
--cc=ml@inbox.vuxu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).