From: "Jeroen Roovers" <jer@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/gentoo:master commit in: x11-wm/openbox/
Date: Sat, 1 Oct 2016 11:50:16 +0000 (UTC) [thread overview]
Message-ID: <1475322590.7fcf60386b1f2d448b412ac6c0f4f2d7d1703a85.jer@gentoo> (raw)
commit: 7fcf60386b1f2d448b412ac6c0f4f2d7d1703a85
Author: Jeroen Roovers <jer <AT> gentoo <DOT> org>
AuthorDate: Sat Oct 1 11:49:50 2016 +0000
Commit: Jeroen Roovers <jer <AT> gentoo <DOT> org>
CommitDate: Sat Oct 1 11:49:50 2016 +0000
URL: https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=7fcf6038
x11-wm/openbox: Stable for HPPA PPC64 (bug #561046).
Package-Manager: portage-2.3.1
RepoMan-Options: --ignore-arches
x11-wm/openbox/openbox-3.6.1.ebuild | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/x11-wm/openbox/openbox-3.6.1.ebuild b/x11-wm/openbox/openbox-3.6.1.ebuild
index 83f9d33..5e32bba 100644
--- a/x11-wm/openbox/openbox-3.6.1.ebuild
+++ b/x11-wm/openbox/openbox-3.6.1.ebuild
@@ -14,12 +14,12 @@ if [[ ${PV} == *9999* ]]; then
EGIT_REPO_URI="git://git.openbox.org/dana/openbox"
SRC_URI="branding? (
https://dev.gentoo.org/~hwoarang/distfiles/surreal-gentoo.tar.gz )"
- KEYWORDS="alpha arm ppc x86"
+ KEYWORDS="alpha arm hppa ppc ppc64 x86"
else
SRC_URI="http://openbox.org/dist/openbox/${P}.tar.gz
branding? ( https://dev.gentoo.org/~hwoarang/distfiles/surreal-gentoo.tar.gz )"
- KEYWORDS="alpha amd64 arm ~arm64 ~hppa ~mips ppc ~ppc64 ~sparc x86 ~x86-fbsd ~arm-linux ~x86-linux"
+ KEYWORDS="alpha amd64 arm ~arm64 hppa ~mips ppc ppc64 ~sparc x86 ~x86-fbsd ~arm-linux ~x86-linux"
fi
LICENSE="GPL-2"
next reply other threads:[~2016-10-01 13:27 UTC|newest]
Thread overview: 65+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-01 11:50 Jeroen Roovers [this message]
-- strict thread matches above, loose matches on Subject: below --
2025-03-29 15:00 [gentoo-commits] repo/gentoo:master commit in: x11-wm/openbox/ Jimi Huotari
2024-06-28 20:33 Jimi Huotari
2024-06-07 16:19 Arthur Zamarin
2024-06-07 7:13 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-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=1475322590.7fcf60386b1f2d448b412ac6c0f4f2d7d1703a85.jer@gentoo \
--to=jer@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