From: Emru1 <Emru1@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [PR PATCH] [Closed]: openldap: update to 2.6.3.
Date: Sun, 26 Feb 2023 23:48:18 +0100 [thread overview]
Message-ID: <20230226224818.7X8MS8qVxm4Zu6Oghs4q_y3MgfNmXhF22pcD-PHlFW0@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-40812@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 744 bytes --]
There's a closed pull request on the void-packages repository
openldap: update to 2.6.3.
https://github.com/void-linux/void-packages/pull/40812
Description:
OpenLDAP update to 2.6.3
This update changes naming of libraries, from `libldap-2.4.so.2` to `libldap.so.2`, so it demanded changes in `common/shlibs`
Also, `libldap_r` was deprecated and merged with `libldap` [https://lists.openldap.org/hyperkitty/list/openldap-announce@openldap.org/thread/BH3VDPG6IYYF5L5U6LZGHHKMJY5HFA3L/](url)
I've built new version and checked build status on x86_64 for those packages which were given by `xrevshlib` as dependent on `openldap` or `libldap`.
I've never made PR this big to void-packages, please, check if everything with this PR is ok
next prev parent reply other threads:[~2023-02-26 22:48 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-27 20:46 [PR PATCH] " Emru1
2022-11-29 21:33 ` [PR PATCH] [Updated] " Emru1
2022-12-06 19:01 ` Emru1
2022-12-14 22:20 ` [PR PATCH] [Updated] " Emru1
2022-12-14 23:07 ` [PR REVIEW] " CameronNemo
2022-12-14 23:15 ` classabbyamp
2022-12-14 23:27 ` [PR PATCH] [Updated] " Emru1
2022-12-14 23:27 ` [PR REVIEW] " Emru1
2022-12-14 23:27 ` Emru1
2022-12-14 23:37 ` [PR PATCH] [Updated] " Emru1
2022-12-15 10:31 ` Emru1
2022-12-15 11:48 ` Emru1
2022-12-15 16:03 ` [PR REVIEW] " paper42
2022-12-16 2:43 ` ahesford
2022-12-22 11:22 ` [PR PATCH] [Updated] " Emru1
2023-01-03 13:17 ` Emru1
2023-02-09 19:53 ` Emru1
2023-02-09 20:11 ` Emru1
2023-02-10 12:52 ` Emru1
2023-02-25 19:57 ` mhmdanas
2023-02-26 22:48 ` Emru1 [this message]
2023-02-28 16:23 ` klarasm
2023-03-01 8:52 ` Emru1
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=20230226224818.7X8MS8qVxm4Zu6Oghs4q_y3MgfNmXhF22pcD-PHlFW0@z \
--to=emru1@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).