public inbox for gentoo-commits@lists.gentoo.org
 help / color / mirror / Atom feed
From: "Arsen Arsenović" <arsen@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/gentoo:master commit in: dev-util/poke/
Date: Tue, 24 Jan 2023 23:46:26 +0000 (UTC)	[thread overview]
Message-ID: <1674603794.c1a98219958b6eb1bbc9026ffae8d2f9e82ae711.arsen@gentoo> (raw)

commit:     c1a98219958b6eb1bbc9026ffae8d2f9e82ae711
Author:     Arsen Arsenović <arsen <AT> gentoo <DOT> org>
AuthorDate: Tue Jan 24 23:30:44 2023 +0000
Commit:     Arsen Arsenović <arsen <AT> gentoo <DOT> org>
CommitDate: Tue Jan 24 23:43:14 2023 +0000
URL:        https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=c1a98219

dev-util/poke: Fix minor typo in alpha check

This has no effect in any current version, but is bothering me.

Signed-off-by: Arsen Arsenović <arsen <AT> gentoo.org>

 dev-util/poke/poke-9999.ebuild | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/dev-util/poke/poke-9999.ebuild b/dev-util/poke/poke-9999.ebuild
index 77f62ea257d8..6bb0f34eb2c4 100644
--- a/dev-util/poke/poke-9999.ebuild
+++ b/dev-util/poke/poke-9999.ebuild
@@ -20,7 +20,7 @@ if [[ ${PV} == 9999 ]]; then
 		sys-devel/bison
 		sys-devel/flex
 	"
-elif [[ $(ver_cut 2) -ge 90 || $(ver_cut 3) ]]; then
+elif [[ $(ver_cut 2) -ge 90 || $(ver_cut 3) -ge 90 ]]; then
 	SRC_URI="https://alpha.gnu.org/gnu/poke/${P}.tar.gz"
 	REGEN_BDEPEND=""
 else


             reply	other threads:[~2023-01-24 23:46 UTC|newest]

Thread overview: 45+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-01-24 23:46 Arsen Arsenović [this message]
  -- strict thread matches above, loose matches on Subject: below --
2024-06-14 14:42 [gentoo-commits] repo/gentoo:master commit in: dev-util/poke/ Arthur Zamarin
2024-06-14 13:36 Arsen Arsenović
2024-04-02 11:55 Arsen Arsenović
2024-04-02 11:55 Arsen Arsenović
2024-02-11 13:23 Arsen Arsenović
2024-01-22 14:04 Arsen Arsenović
2024-01-20 15:56 Arsen Arsenović
2023-11-23 19:53 Sam James
2023-11-21 19:37 Arsen Arsenović
2023-08-20 16:31 Arsen Arsenović
2023-05-14 16:42 Arsen Arsenović
2023-05-14  9:32 Arsen Arsenović
2023-04-18  0:22 Arsen Arsenović
2023-04-01 16:30 Arthur Zamarin
2023-01-25 21:10 Arsen Arsenović
2023-01-25  0:29 Arsen Arsenović
2023-01-25  0:29 Arsen Arsenović
2023-01-24 23:46 Arsen Arsenović
2023-01-24 23:46 Arsen Arsenović
2023-01-21 18:00 Arsen Arsenović
2023-01-21 18:00 Arsen Arsenović
2022-12-05 19:00 Arthur Zamarin
2022-12-04 21:15 Sam James
2022-12-03 11:06 Sam James
2022-11-22  8:11 Sam James
2022-09-17 14:34 Sam James
2022-09-17 14:34 Sam James
2022-04-17 19:00 Sam James
2022-04-10 15:12 Florian Schmaus
2022-04-10 15:12 Florian Schmaus
2022-04-10 15:12 Florian Schmaus
2022-02-23  4:05 Sam James
2022-02-23  4:05 Sam James
2021-07-30  8:55 Sergei Trofimovich
2021-06-12 10:07 Sergei Trofimovich
2021-06-06  9:20 Sergei Trofimovich
2021-04-24 12:37 Sergei Trofimovich
2021-04-19 23:41 Sergei Trofimovich
2021-04-02  9:54 Sergei Trofimovich
2021-03-27 22:18 Sergei Trofimovich
2021-03-25 20:31 Sergei Trofimovich
2021-02-26 22:38 Sergei Trofimovich
2021-02-26 22:01 Sergei Trofimovich
2021-02-26 19:59 Sergei Trofimovich

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=1674603794.c1a98219958b6eb1bbc9026ffae8d2f9e82ae711.arsen@gentoo \
    --to=arsen@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