From: "Sam James" <sam@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/gentoo:master commit in: app-editors/jupp/
Date: Tue, 6 Dec 2022 09:11:45 +0000 (UTC) [thread overview]
Message-ID: <1670317888.6a02df6f8f73f9d69ec9524f33adf761717118d4.sam@gentoo> (raw)
commit: 6a02df6f8f73f9d69ec9524f33adf761717118d4
Author: Kerin Millar <kfm <AT> plushkava <DOT> net>
AuthorDate: Sun Dec 4 10:42:25 2022 +0000
Commit: Sam James <sam <AT> gentoo <DOT> org>
CommitDate: Tue Dec 6 09:11:28 2022 +0000
URL: https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=6a02df6f
app-editors/jupp: Apply patsub_replacement defences
Per bug #881383, string replacing forms of parameter expansion must take care
to quote - or appropriately escape - any nested parameter expansions, assuming
that their values are intended to be taken literally (as is almost invariably
the case). This has long been the case, but the introduction of the new
patsub_replacement option in bash >=5.2 has brought the issue to the fore.
In the case of the app-editors/jupp package, the improper quoting is not yet
causing any issues. Still, it is better to write the code properly to begin
with, especially considering the demonstrative value of robust code.
Signed-off-by: Kerin Millar <kfm <AT> plushkava.net>
Bug: https://bugs.gentoo.org/881383
Signed-off-by: Sam James <sam <AT> gentoo.org>
app-editors/jupp/jupp-3.1_p41.ebuild | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/app-editors/jupp/jupp-3.1_p41.ebuild b/app-editors/jupp/jupp-3.1_p41.ebuild
index cfdbb37a9585..3e6e016b519c 100644
--- a/app-editors/jupp/jupp-3.1_p41.ebuild
+++ b/app-editors/jupp/jupp-3.1_p41.ebuild
@@ -5,7 +5,7 @@ EAPI=8
DESCRIPTION="Portable version of Joe's Own Editor"
HOMEPAGE="http://www.mirbsd.org/jupp.htm"
-SRC_URI="http://www.mirbsd.org/MirOS/dist/${PN}/joe-${PV/_p/${PN}}.tgz"
+SRC_URI="http://www.mirbsd.org/MirOS/dist/${PN}/joe-${PV/_p/"${PN}"}.tgz"
S="${WORKDIR}/${PN}"
LICENSE="GPL-1"
next reply other threads:[~2022-12-06 9:11 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-06 9:11 Sam James [this message]
-- strict thread matches above, loose matches on Subject: below --
2024-11-20 13:06 [gentoo-commits] repo/gentoo:master commit in: app-editors/jupp/ Ulrich Müller
2024-11-20 13:06 Ulrich Müller
2022-10-01 7:43 Ulrich Müller
2022-10-01 7:43 Ulrich Müller
2020-12-28 0:21 Ulrich Müller
2020-12-28 0:21 Ulrich Müller
2018-11-25 13:02 Ulrich Müller
2018-11-25 13:02 Ulrich Müller
2018-05-23 21:40 Mikle Kolyada
2017-01-12 7:58 Michael Weber
2017-01-12 7:58 Michael Weber
2017-01-12 7:58 Michael Weber
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=1670317888.6a02df6f8f73f9d69ec9524f33adf761717118d4.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