From: "Jan Čermák" <sairon@sairon.cz>
To: buildroot@buildroot.org
Cc: "Jan Čermák" <sairon@sairon.cz>
Subject: [Buildroot] [PATCH] package/linux-pam: bump to version 1.6.1
Date: Fri, 26 Apr 2024 09:13:03 +0200 [thread overview]
Message-ID: <20240426071304.2564147-1-sairon@sairon.cz> (raw)
Bump to latest version, fixing couple of bugs. Remove patch already
included in this release.
https://github.com/linux-pam/linux-pam/releases/tag/v1.6.1
Signed-off-by: Jan Čermák <sairon@sairon.cz>
---
.../0001-pam_namespace-include-stdint-h.patch | 42 -------------------
package/linux-pam/linux-pam.hash | 4 +-
package/linux-pam/linux-pam.mk | 2 +-
3 files changed, 3 insertions(+), 45 deletions(-)
delete mode 100644 package/linux-pam/0001-pam_namespace-include-stdint-h.patch
diff --git a/package/linux-pam/0001-pam_namespace-include-stdint-h.patch b/package/linux-pam/0001-pam_namespace-include-stdint-h.patch
deleted file mode 100644
index 5eda619505..0000000000
--- a/package/linux-pam/0001-pam_namespace-include-stdint-h.patch
+++ /dev/null
@@ -1,42 +0,0 @@
-From cc9d40b7cdbd3e15ccaa324a0dda1680ef9dea13 Mon Sep 17 00:00:00 2001
-From: Jacob Heider <jacob@pkgx.dev>
-Date: Wed, 17 Jan 2024 11:49:26 -0500
-Subject: [PATCH] pam_namespace: include stdint.h
-
-pam_namespace.c makes use of SIZE_MAX but doesn't include stdint.h,
-resulting in the following build failures on 1.6.0:
-
- pam_namespace.c: In function 'process_line':
- pam_namespace.c:649:41: error: 'SIZE_MAX' undeclared (first use in this function)
- 649 | if (count > UINT_MAX || count > SIZE_MAX / sizeof(uid_t)) {
- | ^~~~~~~~
- pam_namespace.c:41:1: note: 'SIZE_MAX' is defined in header '<stdint.h>'; did you forget to '#include <stdint.h>'?
- 40 | #include "argv_parse.h"
- +++ |+#include <stdint.h>
- 41 |
- pam_namespace.c:649:41: note: each undeclared identifier is reported only once for each function it appears in
- 649 | if (count > UINT_MAX || count > SIZE_MAX / sizeof(uid_t)) {
- | ^~~~~~~~
-
-Fixes: v1.6.0~100 ("pam_namespace: validate amount of uids in config")
-Resolves: https://github.com/linux-pam/linux-pam/issues/733
-
-Upstream: https://github.com/linux-pam/linux-pam/commit/cc9d40b7cdbd3e15ccaa324a0dda1680ef9dea13
-Signed-off-by: Fabrice Fontaine <fontaine.fabrice@gmail.com>
----
- modules/pam_namespace/pam_namespace.c | 2 ++
- 1 file changed, 2 insertions(+)
-
-diff --git a/modules/pam_namespace/pam_namespace.c b/modules/pam_namespace/pam_namespace.c
-index f72d67189..b16731c22 100644
---- a/modules/pam_namespace/pam_namespace.c
-+++ b/modules/pam_namespace/pam_namespace.c
-@@ -34,6 +34,8 @@
-
- #define _ATFILE_SOURCE
-
-+#include "config.h"
-+#include <stdint.h>
- #include "pam_cc_compat.h"
- #include "pam_inline.h"
- #include "pam_namespace.h"
diff --git a/package/linux-pam/linux-pam.hash b/package/linux-pam/linux-pam.hash
index cd882715cb..353613e6e6 100644
--- a/package/linux-pam/linux-pam.hash
+++ b/package/linux-pam/linux-pam.hash
@@ -1,6 +1,6 @@
# Locally computed hashes after checking signature at
-# https://github.com/linux-pam/linux-pam/releases/download/v1.6.0/Linux-PAM-1.6.0.tar.xz.asc
+# https://github.com/linux-pam/linux-pam/releases/download/v1.6.1/Linux-PAM-1.6.1.tar.xz.asc
# signed with the key 8C6BFD92EE0F42EDF91A6A736D1A7F052E5924BB
-sha256 fff4a34e5bbee77e2e8f1992f27631e2329bcbf8a0563ddeb5c3389b4e3169ad Linux-PAM-1.6.0.tar.xz
+sha256 f8923c740159052d719dbfc2a2f81942d68dd34fcaf61c706a02c9b80feeef8e Linux-PAM-1.6.1.tar.xz
# Locally computed
sha256 133d98e7a2ab3ffd330b4debb0bfc10fea21e4b2b5a5b09de2e924293be5ff08 Copyright
diff --git a/package/linux-pam/linux-pam.mk b/package/linux-pam/linux-pam.mk
index 89a46e81df..a205d67c54 100644
--- a/package/linux-pam/linux-pam.mk
+++ b/package/linux-pam/linux-pam.mk
@@ -4,7 +4,7 @@
#
################################################################################
-LINUX_PAM_VERSION = 1.6.0
+LINUX_PAM_VERSION = 1.6.1
LINUX_PAM_SOURCE = Linux-PAM-$(LINUX_PAM_VERSION).tar.xz
LINUX_PAM_SITE = https://github.com/linux-pam/linux-pam/releases/download/v$(LINUX_PAM_VERSION)
LINUX_PAM_INSTALL_STAGING = YES
--
2.34.1
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
next reply other threads:[~2024-04-26 7:13 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-26 7:13 Jan Čermák [this message]
2024-05-01 20:47 ` [Buildroot] [PATCH] package/linux-pam: bump to version 1.6.1 Thomas Petazzoni via buildroot
2024-05-16 11:08 ` Peter Korsgaard
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=20240426071304.2564147-1-sairon@sairon.cz \
--to=sairon@sairon.cz \
--cc=buildroot@buildroot.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 read-only IMAP folder(s) and NNTP newsgroup(s).