From: "Sergei Trofimovich" <slyfox@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/gentoo:master commit in: x11-misc/colord/
Date: Mon, 22 Jul 2019 21:24:03 +0000 (UTC) [thread overview]
Message-ID: <1563830632.c977a773076880a28df76353f165243b14b35389.slyfox@gentoo> (raw)
commit: c977a773076880a28df76353f165243b14b35389
Author: Rolf Eike Beer <eike <AT> sf-mail <DOT> de>
AuthorDate: Mon Jul 22 15:37:07 2019 +0000
Commit: Sergei Trofimovich <slyfox <AT> gentoo <DOT> org>
CommitDate: Mon Jul 22 21:23:52 2019 +0000
URL: https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=c977a773
x11-misc/colord: stable 1.3.5 for hppa, bug #685254
Signed-off-by: Rolf Eike Beer <eike <AT> sf-mail.de>
Package-Manager: Portage-2.3.66, Repoman-2.3.11
RepoMan-Options: --include-arches="hppa"
Signed-off-by: Sergei Trofimovich <slyfox <AT> gentoo.org>
x11-misc/colord/colord-1.3.5.ebuild | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/x11-misc/colord/colord-1.3.5.ebuild b/x11-misc/colord/colord-1.3.5.ebuild
index 112cce6f6a7..ced318c57ec 100644
--- a/x11-misc/colord/colord-1.3.5.ebuild
+++ b/x11-misc/colord/colord-1.3.5.ebuild
@@ -13,7 +13,7 @@ SRC_URI="https://www.freedesktop.org/software/colord/releases/${P}.tar.xz"
LICENSE="GPL-2+"
SLOT="0/2" # subslot = libcolord soname version
-KEYWORDS="alpha amd64 ~arm arm64 ~hppa ~ia64 ~mips ~ppc ~ppc64 ~sparc x86 ~x86-fbsd"
+KEYWORDS="alpha amd64 ~arm arm64 hppa ~ia64 ~mips ~ppc ~ppc64 ~sparc x86 ~x86-fbsd"
# We prefer policykit enabled by default, bug #448058
IUSE="argyllcms examples extra-print-profiles +gusb +introspection +policykit scanner systemd +udev vala"
next reply other threads:[~2019-07-22 21:24 UTC|newest]
Thread overview: 65+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-22 21:24 Sergei Trofimovich [this message]
-- strict thread matches above, loose matches on Subject: below --
2024-04-09 22:46 [gentoo-commits] repo/gentoo:master commit in: x11-misc/colord/ Sam James
2024-04-07 10:11 Arthur Zamarin
2024-04-07 10:11 Arthur Zamarin
2024-04-07 7:25 Arthur Zamarin
2024-04-06 21:07 Arthur Zamarin
2024-03-13 22:55 Mart Raudsepp
2024-03-12 21:50 Arthur Zamarin
2024-03-12 21:49 Arthur Zamarin
2024-02-22 20:47 Arthur Zamarin
2024-02-22 20:47 Arthur Zamarin
2024-02-10 18:53 Arthur Zamarin
2024-02-10 18:53 Arthur Zamarin
2024-01-22 13:24 Sam James
2023-12-02 21:29 Sam James
2022-08-19 3:38 Sam James
2022-06-17 17:45 Matt Turner
2022-05-26 9:44 Pacho Ramos
2022-05-17 13:07 WANG Xuerui
2022-04-09 22:05 Jason Zaman
2022-03-25 2:03 Sam James
2022-03-18 19:24 Matt Turner
2022-02-17 4:33 Matt Turner
2022-01-24 22:43 Matt Turner
2022-01-24 14:49 Sam James
2022-01-24 14:45 Sam James
2022-01-20 9:42 Arthur Zamarin
2021-12-26 0:24 Georgy Yakovlev
2021-12-19 18:15 Mart Raudsepp
2021-11-18 20:38 Mike Gilbert
2021-11-18 20:38 Mike Gilbert
2021-08-02 12:33 Marek Szuba
2021-06-04 1:14 Matt Turner
2021-06-02 23:53 Matt Turner
2021-05-31 2:00 Matt Turner
2021-05-29 15:27 Sam James
2021-05-28 19:20 Sam James
2021-05-28 19:11 Sam James
2021-04-27 14:39 Matt Turner
2021-04-20 1:53 Matt Turner
2021-01-25 0:43 Sam James
2021-01-18 21:10 Matt Turner
2020-12-13 12:16 Sergei Trofimovich
2020-04-11 10:20 Sergei Trofimovich
2019-07-23 18:34 Mart Raudsepp
2019-06-17 10:07 Mikle Kolyada
2019-05-10 21:36 Aaron Bauman
2019-05-10 17:49 Mikle Kolyada
2019-05-08 9:33 Mikle Kolyada
2019-02-08 16:51 Dennis Lamm
2017-10-30 22:26 Mart Raudsepp
2017-03-16 13:24 Jeroen Roovers
2017-02-21 9:16 Tobias Klausmann
2017-02-11 18:31 Pacho Ramos
2016-11-26 21:50 Lars Wendler
2016-11-26 21:50 Lars Wendler
2016-09-17 13:51 Pacho Ramos
2016-08-10 19:06 Pacho Ramos
2016-07-03 17:01 Pacho Ramos
2016-01-11 14:26 Pacho Ramos
2015-09-20 6:11 Jeroen Roovers
2015-09-16 8:43 Tobias Klausmann
2015-09-12 9:11 Agostino Sarubbo
2015-09-05 17:31 Pacho Ramos
2015-09-05 17:31 Pacho Ramos
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=1563830632.c977a773076880a28df76353f165243b14b35389.slyfox@gentoo \
--to=slyfox@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