From: tibequadorian <tibequadorian@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [PR PATCH] [Updated] seahorse: depend on cracklib
Date: Mon, 14 Feb 2022 11:16:48 +0100 [thread overview]
Message-ID: <20220214101648.7fvX4Qd04y8IpcBf1TopJOBLfCv6Ix0zba3eFog45Yw@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-35597@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 1390 bytes --]
There is an updated pull request by tibequadorian against master on the void-packages repository
https://github.com/tibequadorian/void-packages seahorse
https://github.com/void-linux/void-packages/pull/35597
seahorse: depend on cracklib
This fixes an issue in which seahorse could not determine the strength of a password:
```
/usr/share/cracklib/pw_dict.pwd: No such file or directory
```
<!-- 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/35597.patch is attached
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: github-pr-seahorse-35597.patch --]
[-- Type: text/x-diff, Size: 1026 bytes --]
From 185b4f8482aae830d5424d06c832d3e3d8ef6b6a Mon Sep 17 00:00:00 2001
From: tibequadorian <tibequadorian@posteo.de>
Date: Sun, 13 Feb 2022 21:51:42 +0100
Subject: [PATCH] libpwquality: depend on cracklib
---
srcpkgs/libpwquality/template | 3 ++-
1 file changed, 2 insertions(+), 1 deletion(-)
diff --git a/srcpkgs/libpwquality/template b/srcpkgs/libpwquality/template
index 5489a4144cc5..9d72a5539baa 100644
--- a/srcpkgs/libpwquality/template
+++ b/srcpkgs/libpwquality/template
@@ -1,11 +1,12 @@
# Template file for 'libpwquality'
pkgname=libpwquality
version=1.4.2
-revision=4
+revision=5
build_style=gnu-configure
configure_args="--disable-static --enable-pam --with-securedir=/usr/lib/security"
hostmakedepends="libtool automake gettext-devel python3-devel"
makedepends="cracklib-devel pam-devel python3-devel"
+depends="cracklib"
conf_files="/etc/security/pwquality.conf"
short_desc="Library for password quality checking and generating random passwords"
maintainer="bra1nwave <bra1nwave@protonmail.com>"
next prev parent reply other threads:[~2022-02-14 10:16 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-13 20:54 [PR PATCH] " tibequadorian
2022-02-14 7:37 ` paper42
2022-02-14 10:16 ` tibequadorian [this message]
2022-02-14 11:11 ` libpwquality: " tibequadorian
2022-02-14 17:36 ` paper42
2022-02-14 17:43 ` [PR PATCH] [Updated] " tibequadorian
2022-02-14 18:25 ` [PR PATCH] [Merged]: " paper42
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=20220214101648.7fvX4Qd04y8IpcBf1TopJOBLfCv6Ix0zba3eFog45Yw@z \
--to=tibequadorian@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).