From: klarasm <klarasm@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: sssd: update to 2.8.2.
Date: Sat, 04 Feb 2023 00:20:27 +0100 [thread overview]
Message-ID: <20230203232027.PPeYIgnO2XZaqmIYcxRxwBpejZry0bah3kCiLQkYYV4@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-40846@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 739 bytes --]
New comment by klarasm on void-packages repository
https://github.com/void-linux/void-packages/pull/40846#issuecomment-1416519702
Comment:
Unfortunately this fails in the same way. I also tried this on a machine without my openldap update on it with the same result.
Interestingly, if I try to run the provided service file from musl-nscd it also complains (after removing -F which is not recognized):
`nscd: libnss_files.so: Error loading shared library libnss_files.so: No such file or directory`
I can't actually find any package that provides libnss_files.so.2 (xbps-query -Ro /usr/lib/libnss_files.so.2 and variations don't return anything).
[sssd.log](https://github.com/void-linux/void-packages/files/10583401/sssd.log)
next prev parent reply other threads:[~2023-02-03 23:20 UTC|newest]
Thread overview: 39+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-29 19:41 [PR PATCH] sssd: update to 2.8.1 kruceter
2022-12-09 23:42 ` [PR PATCH] [Updated] " kruceter
2022-12-12 2:34 ` [PR PATCH] [Updated] sssd: update to 2.8.2 kruceter
2022-12-12 3:25 ` kruceter
2023-01-06 12:29 ` [PR PATCH] [Closed]: " kruceter
2023-02-03 16:37 ` [PR PATCH] [Updated] " kruceter
2023-02-03 16:42 ` klarasm
2023-02-03 16:59 ` klarasm
2023-02-03 18:49 ` [PR PATCH] [Updated] " kruceter
2023-02-03 18:59 ` kruceter
2023-02-03 19:00 ` kruceter
2023-02-03 19:40 ` kruceter
2023-02-03 20:09 ` kruceter
2023-02-03 20:18 ` kruceter
2023-02-03 23:20 ` klarasm [this message]
2023-02-03 23:45 ` kruceter
2023-02-03 23:47 ` kruceter
2023-02-03 23:48 ` kruceter
2023-02-04 0:05 ` klarasm
2023-02-04 0:26 ` kruceter
2023-02-04 0:34 ` klarasm
2023-02-04 0:47 ` [PR PATCH] [Updated] " kruceter
2023-02-04 0:47 ` kruceter
2023-02-04 0:55 ` kruceter
2023-02-04 1:11 ` kruceter
2023-02-04 1:21 ` kruceter
2023-02-04 1:38 ` kruceter
2023-02-04 1:42 ` kruceter
2023-02-04 1:42 ` kruceter
2023-02-04 1:46 ` [PR PATCH] [Updated] " kruceter
2023-02-05 3:17 ` kruceter
2023-02-05 3:18 ` kruceter
2023-02-06 17:20 ` klarasm
2023-02-08 23:53 ` [PR PATCH] [Closed]: " kruceter
2023-02-09 11:44 ` klarasm
2023-02-09 18:42 ` paper42
2023-02-10 19:15 ` klarasm
2023-02-10 19:03 [PR PATCH] " klarasm
2023-02-10 19:16 ` klarasm
2023-02-11 10:47 ` klarasm
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=20230203232027.PPeYIgnO2XZaqmIYcxRxwBpejZry0bah3kCiLQkYYV4@z \
--to=klarasm@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).