From: JamiKettunen <JamiKettunen@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: [PR PATCH] shadow: increase maximum group name length to 32 (from 16).
Date: Sun, 13 Feb 2022 11:40:10 +0100 [thread overview]
Message-ID: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-35579@inbox.vuxu.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 1334 bytes --]
There is a new pull request by JamiKettunen against master on the void-packages repository
https://github.com/JamiKettunen/void-packages shadow-longer-group-names
https://github.com/void-linux/void-packages/pull/35579
shadow: increase maximum group name length to 32 (from 16).
This is already the case for usernames, so why not groups?
<!-- Uncomment relevant sections and delete options which are not applicable -->
#### Testing the changes
- I tested the changes in this PR: **YES**
<!--
#### New package
- This new package conforms to the [quality requirements](https://github.com/void-linux/void-packages/blob/master/Manual.md#quality-requirements): **YES**|**NO**
-->
<!-- Note: If the build is likely to take more than 2 hours, please [skip CI](https://github.com/void-linux/void-packages/blob/master/CONTRIBUTING.md#continuous-integration)
and test at least one native build and, if supported, at least one cross build.
Ignore this section if this PR is not skipping CI.
-->
<!--
#### Local build testing
- I built this PR locally for my native architecture, (ARCH-LIBC)
- I built this PR locally for these architectures (if supported. mark crossbuilds):
- aarch64-musl
- armv7l
- armv6l-musl
-->
A patch file from https://github.com/void-linux/void-packages/pull/35579.patch is attached
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: github-pr-shadow-longer-group-names-35579.patch --]
[-- Type: text/x-diff, Size: 1095 bytes --]
From 46be27d00c24ec327d5bdfc53107db1641061527 Mon Sep 17 00:00:00 2001
From: Jami Kettunen <jami.kettunen@protonmail.com>
Date: Sun, 13 Feb 2022 12:36:33 +0200
Subject: [PATCH] shadow: increase maximum group name length to 32 (from 16).
This is already the case for usernames, so why not groups?
---
srcpkgs/shadow/template | 5 +++--
1 file changed, 3 insertions(+), 2 deletions(-)
diff --git a/srcpkgs/shadow/template b/srcpkgs/shadow/template
index f01181a49bd6..c59d92bfeb54 100644
--- a/srcpkgs/shadow/template
+++ b/srcpkgs/shadow/template
@@ -1,12 +1,13 @@
# Template file for 'shadow'
pkgname=shadow
version=4.8.1
-revision=1
+revision=2
build_style=gnu-configure
configure_args="--bindir=/usr/bin --sbindir=/usr/bin
--enable-shared --disable-static
--with-libpam --without-selinux --with-acl --with-attr --without-su
- --disable-nls --enable-subordinate-ids --disable-account-tools-setuid"
+ --disable-nls --enable-subordinate-ids --disable-account-tools-setuid
+ --with-group-name-max-length=32"
hostmakedepends="libtool"
makedepends="acl-devel pam-devel"
depends="pam"
next reply other threads:[~2022-02-13 10:40 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-13 10:40 JamiKettunen [this message]
2022-02-13 19:04 ` Duncaen
2022-02-13 19:05 ` Duncaen
2022-02-18 16:05 ` JamiKettunen
2022-04-20 19:01 ` [PR PATCH] [Merged]: " the-maldridge
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=gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-35579@inbox.vuxu.org \
--to=jamikettunen@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).