From: "Sam James" <sam@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/gentoo:master commit in: app-crypt/pkcrack/
Date: Thu, 29 Apr 2021 01:52:39 +0000 (UTC) [thread overview]
Message-ID: <1619661117.994b607cfcc1baefd946974e20332143f8cfb323.sam@gentoo> (raw)
commit: 994b607cfcc1baefd946974e20332143f8cfb323
Author: Sam James <sam <AT> gentoo <DOT> org>
AuthorDate: Thu Apr 29 01:43:52 2021 +0000
Commit: Sam James <sam <AT> gentoo <DOT> org>
CommitDate: Thu Apr 29 01:51:57 2021 +0000
URL: https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=994b607c
app-crypt/pkcrack: fix variable reference style
Package-Manager: Portage-3.0.18-prefix, Repoman-3.0.3
Signed-off-by: Sam James <sam <AT> gentoo.org>
app-crypt/pkcrack/pkcrack-1.2.2-r1.ebuild | 6 +++---
1 file changed, 3 insertions(+), 3 deletions(-)
diff --git a/app-crypt/pkcrack/pkcrack-1.2.2-r1.ebuild b/app-crypt/pkcrack/pkcrack-1.2.2-r1.ebuild
index 4354930c764..202b59ce9a9 100644
--- a/app-crypt/pkcrack/pkcrack-1.2.2-r1.ebuild
+++ b/app-crypt/pkcrack/pkcrack-1.2.2-r1.ebuild
@@ -1,4 +1,4 @@
-# Copyright 1999-2019 Gentoo Authors
+# Copyright 1999-2021 Gentoo Authors
# Distributed under the terms of the GNU General Public License v2
EAPI=7
@@ -46,10 +46,10 @@ src_install() {
einstalldocs
cd src
dobin pkcrack zipdecrypt findkey makekey
- newbin extract "$PN-extract"
+ newbin extract "${PN}-extract"
}
pkg_postinst() {
- ewarn "Due to file collision, extract utility was renamed to $PN-extract,"
+ ewarn "Due to file collision, extract utility was renamed to ${PN}-extract,"
ewarn "see bug#247394"
}
next reply other threads:[~2021-04-29 1:52 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-29 1:52 Sam James [this message]
-- strict thread matches above, loose matches on Subject: below --
2024-09-01 21:14 [gentoo-commits] repo/gentoo:master commit in: app-crypt/pkcrack/ Petr Vaněk
2024-03-16 9:26 Joonas Niilola
2018-04-10 19:24 Alon Bar-Lev
2017-02-04 1:31 Alon Bar-Lev
2016-06-12 13:41 Alon Bar-Lev
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=1619661117.994b607cfcc1baefd946974e20332143f8cfb323.sam@gentoo \
--to=sam@gentoo.org \
--cc=gentoo-commits@lists.gentoo.org \
--cc=gentoo-dev@lists.gentoo.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