public inbox for gentoo-commits@lists.gentoo.org
 help / color / mirror / Atom feed
From: "Arthur Zamarin" <arthurzam@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/gentoo:master commit in: dev-php/smarty/
Date: Fri,  8 Dec 2023 16:29:43 +0000 (UTC)	[thread overview]
Message-ID: <1702052976.f65ddd555cd0668d15786ddabaeb58a297b0345b.arthurzam@gentoo> (raw)

commit:     f65ddd555cd0668d15786ddabaeb58a297b0345b
Author:     Matoro Mahri <matoro_gentoo <AT> matoro <DOT> tk>
AuthorDate: Fri Dec  8 16:23:28 2023 +0000
Commit:     Arthur Zamarin <arthurzam <AT> gentoo <DOT> org>
CommitDate: Fri Dec  8 16:29:36 2023 +0000
URL:        https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=f65ddd55

dev-php/smarty: unkeyword 4.3.1 for ~alpha

Bug: https://bugs.gentoo.org/873523
Signed-off-by: Matoro Mahri <matoro_gentoo <AT> matoro.tk>
Signed-off-by: Arthur Zamarin <arthurzam <AT> gentoo.org>

 dev-php/smarty/smarty-4.3.1.ebuild | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/dev-php/smarty/smarty-4.3.1.ebuild b/dev-php/smarty/smarty-4.3.1.ebuild
index b968f0fd2181..0279c030906a 100644
--- a/dev-php/smarty/smarty-4.3.1.ebuild
+++ b/dev-php/smarty/smarty-4.3.1.ebuild
@@ -9,7 +9,7 @@ SRC_URI="https://github.com/smarty-php/${PN}/archive/v${PV}.tar.gz -> ${P}.tar.g
 
 LICENSE="LGPL-3"
 SLOT="0"
-KEYWORDS="~alpha amd64 ~hppa ~ia64 ppc ppc64 sparc x86"
+KEYWORDS="amd64 ~hppa ~ia64 ppc ppc64 sparc x86"
 IUSE="doc examples"
 
 # PHP unicode support is detected at runtime, and the cached templates


             reply	other threads:[~2023-12-08 16:29 UTC|newest]

Thread overview: 36+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-12-08 16:29 Arthur Zamarin [this message]
  -- strict thread matches above, loose matches on Subject: below --
2024-06-11 11:36 [gentoo-commits] repo/gentoo:master commit in: dev-php/smarty/ Arthur Zamarin
2023-05-02 22:49 Michael Orlitzky
2023-05-02 22:49 Michael Orlitzky
2023-04-04  1:36 Michael Orlitzky
2023-01-31 13:41 Michael Orlitzky
2022-09-16 12:38 Michael Orlitzky
2022-09-16 12:38 Michael Orlitzky
2022-09-14 13:17 Michael Orlitzky
2022-05-27 12:43 Michael Orlitzky
2022-05-27 12:43 Michael Orlitzky
2022-05-17 23:29 Michael Orlitzky
2022-02-08 13:24 Brian Evans
2022-02-08  7:22 Agostino Sarubbo
2022-02-07 15:00 Brian Evans
2022-01-11 16:05 Brian Evans
2021-02-24 17:57 Brian Evans
2021-02-24 16:22 Sam James
2021-02-23 14:32 Brian Evans
2021-02-23  3:41 Michael Orlitzky
2020-12-17  3:40 Michael Orlitzky
2020-01-21 23:36 Michael Orlitzky
2019-05-02 22:40 Michael Orlitzky
2019-05-02 21:09 Mikle Kolyada
2019-03-27 23:44 Thomas Deutschmann
2019-03-14 21:14 Agostino Sarubbo
2019-03-11 22:42 Sergei Trofimovich
2019-03-11 19:58 Sergei Trofimovich
2019-03-10 22:17 Sergei Trofimovich
2018-09-17 21:21 Michael Orlitzky
2018-06-07 19:22 Aaron Bauman
2018-05-14 17:47 Brian Evans
2016-12-20 17:42 Brian Evans
2016-11-24  1:52 Michael Orlitzky
2016-11-20 11:39 Aaron Bauman
2016-10-03 18:44 Brian Evans

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=1702052976.f65ddd555cd0668d15786ddabaeb58a297b0345b.arthurzam@gentoo \
    --to=arthurzam@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