Github messages for voidlinux
 help / color / mirror / Atom feed
From: ahesford <ahesford@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [PR PATCH] [Merged]: sssd: update to 2.2.3.
Date: Sun, 20 Sep 2020 17:04:43 +0200	[thread overview]
Message-ID: <20200920150443.BDZWGVoiSrjR948--0fviqhaMnkOszxcddhSzDp5KFA@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: 736 bytes --]

There's a merged pull request on the void-packages repository

sssd: update to 2.2.3.
https://github.com/void-linux/void-packages/pull/24969

Description:
@inzanez I believe you are interested in `sssd`. Please test this update if possible.

Key changes in the template:
1. Move unversioned symlinks to `sssd-devel`.
2. Use `--with-sudo-lib-path` to move `libsss_sudo.so` to `/usr/lib/sssd`, so that unversioned library is not in the top-level `/usr/lib`.
3. Drop `libwbclient`. I'm pretty sure this was never done right in the first place and it causes shlib dependency confusion with `samba` and `cifs-utils`.

In particular, I would like to know if moving the unversioned symlinks to `sssd-devel` causes any obvious breakage.

      parent reply	other threads:[~2020-09-20 15:04 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
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 ` ahesford [this message]

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=20200920150443.BDZWGVoiSrjR948--0fviqhaMnkOszxcddhSzDp5KFA@z \
    --to=ahesford@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).