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/pdm-backend/
Date: Sat, 13 Jan 2024 09:38:20 +0000 (UTC)	[thread overview]
Message-ID: <1705138688.357644c540fa16890b94cb56bc76b2ccc34355e7.arthurzam@gentoo> (raw)

commit:     357644c540fa16890b94cb56bc76b2ccc34355e7
Author:     Arthur Zamarin <arthurzam <AT> gentoo <DOT> org>
AuthorDate: Sat Jan 13 09:38:08 2024 +0000
Commit:     Arthur Zamarin <arthurzam <AT> gentoo <DOT> org>
CommitDate: Sat Jan 13 09:38:08 2024 +0000
URL:        https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=357644c5

dev-python/pdm-backend: Stabilize 2.1.8 ALLARCHES, #921993

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

 dev-python/pdm-backend/pdm-backend-2.1.8.ebuild | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/dev-python/pdm-backend/pdm-backend-2.1.8.ebuild b/dev-python/pdm-backend/pdm-backend-2.1.8.ebuild
index 8f4cf7b5dcd5..feddb5abeab3 100644
--- a/dev-python/pdm-backend/pdm-backend-2.1.8.ebuild
+++ b/dev-python/pdm-backend/pdm-backend-2.1.8.ebuild
@@ -1,4 +1,4 @@
-# Copyright 2022-2023 Gentoo Authors
+# Copyright 2022-2024 Gentoo Authors
 # Distributed under the terms of the GNU General Public License v2
 
 EAPI=8
@@ -20,7 +20,7 @@ SRC_URI="
 
 LICENSE="MIT"
 SLOT="0"
-KEYWORDS="~alpha ~amd64 ~arm ~arm64 ~hppa ~ia64 ~loong ~ppc ~ppc64 ~riscv ~s390 ~sparc ~x86"
+KEYWORDS="~alpha amd64 arm arm64 hppa ~ia64 ~loong ppc ppc64 ~riscv ~s390 sparc x86"
 
 RDEPEND="
 	>=dev-python/packaging-22.0[${PYTHON_USEDEP}]


             reply	other threads:[~2024-01-13  9:38 UTC|newest]

Thread overview: 64+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-01-13  9:38 Arthur Zamarin [this message]
  -- strict thread matches above, loose matches on Subject: below --
2024-11-09 12:01 [gentoo-commits] repo/gentoo:master commit in: dev-python/pdm-backend/ Michał Górny
2024-11-09 11:13 Sam James
2024-10-26 11:52 Michał Górny
2024-10-23 19:33 Arthur Zamarin
2024-10-10 18:25 Michał Górny
2024-09-28 13:35 Michał Górny
2024-09-28 13:11 Michał Górny
2024-09-22  3:02 Michał Górny
2024-09-21  7:41 Michał Górny
2024-08-03  6:37 Michał Górny
2024-08-03  6:24 Michał Górny
2024-07-20  9:01 Michał Górny
2024-07-20  7:39 Arthur Zamarin
2024-07-16  5:30 Michał Górny
2024-07-06  6:35 Michał Górny
2024-07-06  6:26 Sam James
2024-07-05 18:41 Arthur Zamarin
2024-07-05 16:29 Arthur Zamarin
2024-06-19  4:36 Michał Górny
2024-06-13 10:31 Michał Górny
2024-06-13  5:18 Sam James
2024-06-13  4:54 Sam James
2024-06-12 18:19 Michał Górny
2024-06-12 10:33 Arthur Zamarin
2024-06-12  8:42 Jakov Smolić
2024-06-12  7:05 Arthur Zamarin
2024-06-12  6:51 Sam James
2024-06-12  6:50 Arthur Zamarin
2024-05-13 18:45 Michał Górny
2024-05-04 12:00 Sam James
2024-05-04 12:00 Sam James
2024-05-04 11:38 Sam James
2024-05-04 11:38 Sam James
2024-05-04 10:01 Arthur Zamarin
2024-05-04  7:55 Arthur Zamarin
2024-05-04  7:32 Arthur Zamarin
2024-05-01 11:48 Michał Górny
2024-05-01  4:06 Michał Górny
2024-04-18  5:34 Michał Górny
2024-04-15 12:19 Michał Górny
2024-01-13 10:04 Michał Górny
2023-12-27 13:00 Michał Górny
2023-12-06 17:57 Ionen Wolkens
2023-11-24 21:53 Sam James
2023-11-16 17:17 Arthur Zamarin
2023-11-16 16:22 Sam James
2023-11-15 17:40 Sam James
2023-11-15 16:45 Arthur Zamarin
2023-11-15 16:34 Arthur Zamarin
2023-11-15 16:34 Arthur Zamarin
2023-11-15 15:55 Michał Górny
2023-10-08 17:48 Michał Górny
2023-08-30  3:15 Michał Górny
2023-08-09  3:09 Michał Górny
2023-07-24 11:32 Michał Górny
2023-07-19 11:10 Michał Górny
2023-07-13  5:28 Michał Górny
2023-07-12  4:04 Michał Górny
2023-06-27  3:54 Michał Górny
2023-06-26  4:51 Michał Górny
2023-06-23  6:17 Michał Górny
2023-06-08 10:21 Michał Górny
2023-06-03  6:48 Michał Górny

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=1705138688.357644c540fa16890b94cb56bc76b2ccc34355e7.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