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: x11-wm/openbox/
Date: Fri,  7 Jun 2024 07:13:44 +0000 (UTC)	[thread overview]
Message-ID: <1717744419.41ea76e7a7aef453be44f4a0ae40763e544c6d98.arthurzam@gentoo> (raw)

commit:     41ea76e7a7aef453be44f4a0ae40763e544c6d98
Author:     Arthur Zamarin <arthurzam <AT> gentoo <DOT> org>
AuthorDate: Fri Jun  7 07:13:39 2024 +0000
Commit:     Arthur Zamarin <arthurzam <AT> gentoo <DOT> org>
CommitDate: Fri Jun  7 07:13:39 2024 +0000
URL:        https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=41ea76e7

x11-wm/openbox: Stabilize 3.6.1-r9 sparc, #933501

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

 x11-wm/openbox/openbox-3.6.1-r9.ebuild | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/x11-wm/openbox/openbox-3.6.1-r9.ebuild b/x11-wm/openbox/openbox-3.6.1-r9.ebuild
index 6a2a2fb25256..daf0a15ecbfc 100644
--- a/x11-wm/openbox/openbox-3.6.1-r9.ebuild
+++ b/x11-wm/openbox/openbox-3.6.1-r9.ebuild
@@ -14,7 +14,7 @@ if [[ ${PV} == *9999* ]]; then
 	EGIT_REPO_URI="https://github.com/Mikachu/openbox.git"
 else
 	SRC_URI="http://openbox.org/dist/openbox/${P}.tar.gz"
-	KEYWORDS="~alpha amd64 arm arm64 ~hppa ~loong ~mips ppc ~ppc64 ~riscv ~sparc x86 ~x86-linux"
+	KEYWORDS="~alpha amd64 arm arm64 ~hppa ~loong ~mips ppc ~ppc64 ~riscv sparc x86 ~x86-linux"
 fi
 
 SRC_URI+=" branding? ( https://dev.gentoo.org/~hwoarang/distfiles/surreal-gentoo.tar.gz )"


             reply	other threads:[~2024-06-07  7:13 UTC|newest]

Thread overview: 64+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-06-07  7:13 Arthur Zamarin [this message]
  -- strict thread matches above, loose matches on Subject: below --
2024-06-28 20:33 [gentoo-commits] repo/gentoo:master commit in: x11-wm/openbox/ Jimi Huotari
2024-06-07 16:19 Arthur Zamarin
2024-06-05 19:59 Arthur Zamarin
2024-06-05 19:59 Arthur Zamarin
2024-06-05 19:59 Arthur Zamarin
2024-06-05 19:59 Arthur Zamarin
2024-06-05 19:59 Arthur Zamarin
2024-05-28 16:01 Jimi Huotari
2024-05-28 16:01 Jimi Huotari
2023-12-23 20:00 Arthur Zamarin
2023-12-18  9:01 Arthur Zamarin
2023-12-17  6:20 Arthur Zamarin
2023-12-17  6:20 Arthur Zamarin
2023-12-17  0:22 Sam James
2023-12-17  0:05 Sam James
2023-12-17  0:05 Sam James
2023-08-10  4:08 Sam James
2023-08-05 23:12 Sam James
2023-08-05 22:35 Sam James
2023-08-05 22:29 Sam James
2023-06-18 14:53 Andreas Sturmlechner
2023-05-05  9:57 Arthur Zamarin
2023-05-05  9:45 Arthur Zamarin
2023-05-05  9:24 Arthur Zamarin
2023-05-04 12:45 Sam James
2023-05-04 12:45 Sam James
2023-05-04 12:23 Arthur Zamarin
2023-05-04 12:12 Sam James
2023-03-09 16:29 Jimi Huotari
2023-03-09 16:29 Jimi Huotari
2022-05-25 11:20 WANG Xuerui
2022-05-25 11:20 WANG Xuerui
2022-02-02  2:36 Craig Andrews
2021-07-17 18:18 David Seifert
2021-05-27 14:34 Yixun Lan
2021-03-14 23:02 Andreas Sturmlechner
2020-08-13 15:47 Andreas Sturmlechner
2020-08-13 15:47 Andreas Sturmlechner
2020-05-18 16:46 Sergei Trofimovich
2020-05-13 10:08 Agostino Sarubbo
2020-05-13 10:06 Agostino Sarubbo
2020-05-13 10:05 Agostino Sarubbo
2020-05-13 10:04 Agostino Sarubbo
2020-05-13 10:04 Agostino Sarubbo
2020-05-12 21:48 Mart Raudsepp
2020-05-12 13:05 Agostino Sarubbo
2020-03-28 13:11 Andreas Sturmlechner
2020-03-28 13:11 Andreas Sturmlechner
2020-03-22 18:21 Hanno Böck
2020-02-15 10:03 David Seifert
2020-02-09 16:42 Michał Górny
2019-11-29  8:17 Michał Górny
2018-05-31  5:38 Johannes Huber
2018-05-30 21:13 Johannes Huber
2018-05-30 21:13 Johannes Huber
2018-05-30 21:13 Johannes Huber
2018-05-30 21:13 Johannes Huber
2018-05-30 21:13 Johannes Huber
2017-11-26 23:33 David Seifert
2016-10-01 11:50 Jeroen Roovers
2016-05-23 14:38 Tobias Klausmann
2016-04-19 15:57 Markus Meier
2016-04-09 13:46 Agostino Sarubbo

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=1717744419.41ea76e7a7aef453be44f4a0ae40763e544c6d98.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