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-python/cherrypy/
Date: Sat, 29 Jun 2024 07:57:31 +0000 (UTC)	[thread overview]
Message-ID: <1719647822.d3b849e6601161025cb9156d2fadaf965b9dcabc.arthurzam@gentoo> (raw)

commit:     d3b849e6601161025cb9156d2fadaf965b9dcabc
Author:     Arthur Zamarin <arthurzam <AT> gentoo <DOT> org>
AuthorDate: Sat Jun 29 07:57:02 2024 +0000
Commit:     Arthur Zamarin <arthurzam <AT> gentoo <DOT> org>
CommitDate: Sat Jun 29 07:57:02 2024 +0000
URL:        https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=d3b849e6

dev-python/cherrypy: Stabilize 18.10.0 ALLARCHES, #935074

Signed-off-by: Arthur Zamarin <arthurzam <AT> gentoo.org>

 dev-python/cherrypy/cherrypy-18.10.0.ebuild | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/dev-python/cherrypy/cherrypy-18.10.0.ebuild b/dev-python/cherrypy/cherrypy-18.10.0.ebuild
index fcbfeb62a8d3..ec908dcc10b1 100644
--- a/dev-python/cherrypy/cherrypy-18.10.0.ebuild
+++ b/dev-python/cherrypy/cherrypy-18.10.0.ebuild
@@ -18,7 +18,7 @@ HOMEPAGE="
 
 LICENSE="BSD"
 SLOT="0"
-KEYWORDS="~alpha ~amd64 ~arm ~arm64 ~hppa ~ia64 ~loong ~ppc ~ppc64 ~riscv ~sparc ~x86"
+KEYWORDS="~alpha amd64 arm arm64 ~hppa ~ia64 ~loong ppc ppc64 ~riscv ~sparc x86"
 IUSE="ssl test"
 
 RDEPEND="


             reply	other threads:[~2024-06-29  7:57 UTC|newest]

Thread overview: 72+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-06-29  7:57 Arthur Zamarin [this message]
  -- strict thread matches above, loose matches on Subject: below --
2024-07-11 22:28 [gentoo-commits] repo/gentoo:master commit in: dev-python/cherrypy/ James Le Cuirot
2024-06-15 13:47 Michał Górny
2024-06-15  4:22 Michał Górny
2023-12-30 14:25 Arthur Zamarin
2023-12-14 13:58 Michał Górny
2023-11-07 21:10 Michał Górny
2023-01-03  2:53 WANG Xuerui
2022-11-18 15:14 Arthur Zamarin
2022-10-22 14:54 Michał Górny
2022-09-16 10:15 Arthur Zamarin
2022-09-10 18:28 Arthur Zamarin
2022-09-08  5:19 Sam James
2022-07-18 12:52 Sam James
2022-07-18  7:54 Michał Górny
2022-07-11  7:59 Michał Górny
2022-07-11  7:59 Michał Górny
2022-07-11  7:06 Michał Górny
2022-06-23  8:17 Michał Górny
2022-06-23  5:58 Agostino Sarubbo
2022-05-31  7:16 Jakov Smolić
2022-05-22 10:46 Michał Górny
2021-11-28 14:42 Michał Górny
2021-11-02 12:37 Arthur Zamarin
2021-08-07 14:57 Michał Górny
2021-08-07 14:49 Sam James
2021-07-04  8:28 Michał Górny
2021-07-04  7:38 Michał Górny
2020-07-30 21:14 Michał Górny
2020-07-30 20:42 Sam James
2020-07-30 20:40 Sam James
2020-07-13 23:13 Sam James
2020-07-06 11:57 Michał Górny
2020-07-05 15:16 Michał Górny
2020-06-29 13:40 Agostino Sarubbo
2020-06-22 19:05 Mart Raudsepp
2020-06-22  4:33 Michał Górny
2020-06-21 19:23 Michał Górny
2020-06-21 19:23 Michał Górny
2020-06-20 14:20 Thomas Deutschmann
2020-06-04 14:06 Michał Górny
2020-05-30 20:33 Sergei Trofimovich
2020-05-30 16:20 Michał Górny
2020-05-29 17:10 Michał Górny
2020-05-16 11:25 Mikle Kolyada
2020-05-04 10:29 Michał Górny
2020-04-28 19:23 Mart Raudsepp
2020-03-31  7:38 Georgy Yakovlev
2020-03-30 22:06 Patrick McLean
2020-03-27  0:04 Patrick McLean
2020-03-26 23:14 Patrick McLean
2020-03-26 23:14 Patrick McLean
2020-01-27  9:39 Sergei Trofimovich
2020-01-26 17:11 Michał Górny
2019-12-12  2:19 Georgy Yakovlev
2019-04-17 18:07 Aaron Bauman
2019-03-11  2:33 William Hubbs
2019-03-11  2:33 William Hubbs
2019-03-11  2:33 William Hubbs
2019-03-11  2:33 William Hubbs
2019-03-06 22:10 William Hubbs
2019-01-10  1:52 William Hubbs
2018-11-09 14:20 Alexey Shvetsov
2018-04-29  7:35 Michał Górny
2018-03-07 19:47 Markus Meier
2018-01-24 23:12 Sergei Trofimovich
2018-01-11  3:28 Zac Medico
2018-01-10  1:20 Zac Medico
2017-04-18 14:18 Kacper Kowalik
2017-02-20 18:10 Markus Meier
2017-01-17 16:22 Agostino Sarubbo
2016-09-15  7:52 Alexis Ballier

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=1719647822.d3b849e6601161025cb9156d2fadaf965b9dcabc.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