public inbox for gentoo-commits@lists.gentoo.org
 help / color / mirror / Atom feed
From: "Ionen Wolkens" <ionen@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/gentoo:master commit in: dev-python/python-dbusmock/
Date: Tue, 28 May 2024 22:28:53 +0000 (UTC)	[thread overview]
Message-ID: <1716935218.69034be58d016004331abbfbab9822b20ceac4f1.ionen@gentoo> (raw)

commit:     69034be58d016004331abbfbab9822b20ceac4f1
Author:     Matoro Mahri <matoro_gentoo <AT> matoro <DOT> tk>
AuthorDate: Tue May 28 19:47:22 2024 +0000
Commit:     Ionen Wolkens <ionen <AT> gentoo <DOT> org>
CommitDate: Tue May 28 22:26:58 2024 +0000
URL:        https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=69034be5

dev-python/python-dbusmock: Keyword 0.31.1-r1 hppa, #927405

Signed-off-by: Matoro Mahri <matoro_gentoo <AT> matoro.tk>
Signed-off-by: Ionen Wolkens <ionen <AT> gentoo.org>

 dev-python/python-dbusmock/python-dbusmock-0.31.1-r1.ebuild | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/dev-python/python-dbusmock/python-dbusmock-0.31.1-r1.ebuild b/dev-python/python-dbusmock/python-dbusmock-0.31.1-r1.ebuild
index 33f15293fb01..d35ffc722d51 100644
--- a/dev-python/python-dbusmock/python-dbusmock-0.31.1-r1.ebuild
+++ b/dev-python/python-dbusmock/python-dbusmock-0.31.1-r1.ebuild
@@ -18,7 +18,7 @@ HOMEPAGE="
 
 LICENSE="LGPL-3+"
 SLOT="0"
-KEYWORDS="~alpha amd64 arm arm64 ~ia64 ~loong ~mips ppc ppc64 ~riscv ~s390 sparc x86"
+KEYWORDS="~alpha amd64 arm arm64 ~hppa ~ia64 ~loong ~mips ppc ppc64 ~riscv ~s390 sparc x86"
 
 RDEPEND="
 	dev-python/dbus-python[${PYTHON_USEDEP}]


             reply	other threads:[~2024-05-28 22:29 UTC|newest]

Thread overview: 68+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-05-28 22:28 Ionen Wolkens [this message]
  -- strict thread matches above, loose matches on Subject: below --
2024-08-03  6:40 [gentoo-commits] repo/gentoo:master commit in: dev-python/python-dbusmock/ Michał Górny
2024-08-03  6:37 Michał Górny
2024-07-14 19:51 Arthur Zamarin
2024-06-30 17:24 Michał Górny
2024-05-29  4:17 Michał Górny
2024-03-24 15:44 Michał Górny
2024-03-21 17:00 Arthur Zamarin
2024-03-21 15:19 Michał Górny
2024-03-09 14:19 Michał Górny
2024-03-09 14:11 Michał Górny
2024-02-24  8:49 Michał Górny
2024-01-18 18:49 Michał Górny
2024-01-18 18:37 Arthur Zamarin
2023-12-31 17:21 Michał Górny
2023-12-23 23:41 Mart Raudsepp
2023-12-15 12:40 Michał Górny
2023-12-15 12:35 Arthur Zamarin
2023-11-30 13:35 Michał Górny
2023-09-01 16:07 Arthur Zamarin
2023-08-29 18:02 Arthur Zamarin
2023-08-29 17:49 Arthur Zamarin
2023-07-27 15:57 Michał Górny
2023-07-27 15:57 Michał Górny
2023-05-23 16:08 Michał Górny
2023-05-23 15:43 Arthur Zamarin
2023-04-21  4:34 Michał Górny
2023-04-21  4:34 Michał Górny
2023-03-09  1:09 Sam James
2023-02-13  6:07 Michał Górny
2023-02-12 20:24 Jakov Smolić
2023-01-05 16:39 Matt Turner
2022-12-01  7:09 Michał Górny
2022-12-01  7:09 Michał Górny
2022-12-01  7:09 Michał Górny
2022-11-05 18:58 Arthur Zamarin
2022-11-05  9:58 Arthur Zamarin
2022-11-05  9:44 Arthur Zamarin
2022-10-12 11:18 Michał Górny
2022-08-19  9:27 Michał Górny
2022-08-19  7:41 Arthur Zamarin
2022-07-25  2:28 Sam James
2022-07-20  5:39 Michał Górny
2022-07-18  7:54 Michał Górny
2022-07-17  7:22 Michał Górny
2022-06-29  6:19 Michał Górny
2022-06-19 18:08 Arthur Zamarin
2022-06-19 18:08 Arthur Zamarin
2022-06-09  2:43 Sam James
2022-06-04  3:20 Sam James
2022-04-26 17:01 Michał Górny
2022-04-26 16:56 Arthur Zamarin
2022-04-05  7:53 Michał Górny
2022-04-01  7:45 Michał Górny
2022-04-01  5:15 Arthur Zamarin
2022-03-22  6:35 Michał Górny
2022-02-25 23:41 Michał Górny
2022-01-26 20:18 Michał Górny
2022-01-26 19:58 Arthur Zamarin
2021-12-25  8:09 Michał Górny
2021-12-02  9:39 Michał Górny
2021-12-02  8:54 Jakov Smolić
2021-12-02  8:29 Agostino Sarubbo
2021-12-02  8:24 Agostino Sarubbo
2021-10-28  7:00 Michał Górny
2021-10-03 19:27 Michał Górny
2021-10-03 18:49 Sam James
2021-08-29  6:57 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=1716935218.69034be58d016004331abbfbab9822b20ceac4f1.ionen@gentoo \
    --to=ionen@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