From: icp1994 <icp1994@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [PR PATCH] [Updated] pam: fix libc check
Date: Wed, 01 Mar 2023 21:13:33 +0100 [thread overview]
Message-ID: <20230301201333.oRJ39WnuPsHXDC_E_YznvrAfki0VvAvBVBnD8mNV6zk@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-42535@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 624 bytes --]
There is an updated pull request by icp1994 against master on the void-packages repository
https://github.com/icp1994/void-packages pam
https://github.com/void-linux/void-packages/pull/42535
pam: fix libc check
#### Testing the changes
- I tested the changes in this PR: **NO**
#### Local build testing
- I built this PR locally for my native architecture: **x86_64**
This should be the actual check, right? Although I haven't built/tested it locally. Not even sure if it requires revbump; just making a PR for visibility.
A patch file from https://github.com/void-linux/void-packages/pull/42535.patch is attached
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: github-pr-pam-42535.patch --]
[-- Type: text/x-diff, Size: 1272 bytes --]
From 5a4186d0ae6984f6dc5efd46e12ec7b5b646fadc Mon Sep 17 00:00:00 2001
From: icp <pangolin@vivaldi.net>
Date: Thu, 2 Mar 2023 01:06:21 +0530
Subject: [PATCH] pam: fix libc check
remove version from pam-base dependency.
---
srcpkgs/pam/template | 6 +++---
1 file changed, 3 insertions(+), 3 deletions(-)
diff --git a/srcpkgs/pam/template b/srcpkgs/pam/template
index 70d87f00af90..567e7016428b 100644
--- a/srcpkgs/pam/template
+++ b/srcpkgs/pam/template
@@ -1,7 +1,7 @@
# Template file for 'pam'
pkgname=pam
version=1.5.2
-revision=2
+revision=3
build_style=gnu-configure
configure_args="
--libdir=/usr/lib --sbindir=/usr/bin --docdir=/usr/share/doc/pam
@@ -10,7 +10,7 @@ configure_args="
hostmakedepends="gettext-devel pkg-config"
makedepends="libfl-devel db-devel"
# version of pam-base that doesn't include removed modules
-depends="pam-base>=0.4_1"
+depends="pam-base"
checkdepends="${depends}"
conf_files="
/etc/environment
@@ -32,7 +32,7 @@ distfiles="${homepage}/releases/download/v${version}/Linux-PAM-${version}.tar.xz
checksum=e4ec7131a91da44512574268f493c6d8ca105c87091691b8e9b56ca685d4f94d
lib32disabled=yes
-if [ "$XBPS_CHECK_PKGS" = musl ]; then
+if [ "$XBPS_TARGET_LIBC" = musl ]; then
configure_args+=" ac_cv_search_crypt=no"
fi
next prev parent reply other threads:[~2023-03-01 20:13 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-01 19:39 [PR PATCH] " icp1994
2023-03-01 19:58 ` [PR PATCH] [Updated] " icp1994
2023-03-01 20:13 ` icp1994 [this message]
2023-03-04 19:53 ` icp1994
2023-03-06 20:08 ` paper42
2023-03-06 20:20 ` icp1994
2023-06-05 2:04 ` github-actions
2023-06-20 1:56 ` [PR PATCH] [Closed]: " github-actions
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=20230301201333.oRJ39WnuPsHXDC_E_YznvrAfki0VvAvBVBnD8mNV6zk@z \
--to=icp1994@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).