From: "Davide Pesavento" <pesa@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/gentoo:master commit in: dev-util/qbs/
Date: Fri, 20 Jul 2018 02:58:21 +0000 (UTC) [thread overview]
Message-ID: <1532055013.7d1311e3db7d1e3dcead9247fea6d2f5670c24b4.pesa@gentoo> (raw)
commit: 7d1311e3db7d1e3dcead9247fea6d2f5670c24b4
Author: Davide Pesavento <pesa <AT> gentoo <DOT> org>
AuthorDate: Fri Jul 20 02:50:13 2018 +0000
Commit: Davide Pesavento <pesa <AT> gentoo <DOT> org>
CommitDate: Fri Jul 20 02:50:13 2018 +0000
URL: https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=7d1311e3
dev-util/qbs: stabilize 1.11.1 on amd64
Package-Manager: Portage-2.3.41, Repoman-2.3.9
dev-util/qbs/qbs-1.11.1.ebuild | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/dev-util/qbs/qbs-1.11.1.ebuild b/dev-util/qbs/qbs-1.11.1.ebuild
index 4971aeed820..9a19d31b66e 100644
--- a/dev-util/qbs/qbs-1.11.1.ebuild
+++ b/dev-util/qbs/qbs-1.11.1.ebuild
@@ -13,7 +13,7 @@ SRC_URI="http://download.qt.io/official_releases/${PN}/${PV}/${MY_P}.tar.gz"
LICENSE="|| ( LGPL-2.1 LGPL-3 )"
SLOT="0"
-KEYWORDS="~amd64 ~arm ~x86"
+KEYWORDS="amd64 ~arm ~x86"
IUSE="doc examples test"
# see bug 581874 for the qttest dep in RDEPEND
next reply other threads:[~2018-07-20 2:58 UTC|newest]
Thread overview: 76+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-07-20 2:58 Davide Pesavento [this message]
-- strict thread matches above, loose matches on Subject: below --
2024-11-04 16:15 [gentoo-commits] repo/gentoo:master commit in: dev-util/qbs/ Ionen Wolkens
2024-10-22 8:04 Jakov Smolić
2024-10-02 4:35 Ionen Wolkens
2024-09-25 12:48 Joonas Niilola
2024-09-13 23:25 Ionen Wolkens
2024-08-31 13:53 Ionen Wolkens
2024-05-30 15:52 Ionen Wolkens
2024-05-13 5:49 Ionen Wolkens
2024-05-12 20:25 Ionen Wolkens
2024-05-07 19:34 Ionen Wolkens
2024-05-05 2:41 Ionen Wolkens
2024-05-05 2:41 Ionen Wolkens
2023-08-30 6:33 Sam James
2022-08-08 9:40 Andreas Sturmlechner
2021-07-10 21:00 Davide Pesavento
2021-07-10 21:00 Davide Pesavento
2021-01-13 7:02 Davide Pesavento
2021-01-13 7:02 Davide Pesavento
2020-06-30 23:31 Davide Pesavento
2020-01-03 5:57 Davide Pesavento
2020-01-03 5:57 Davide Pesavento
2019-11-28 19:24 Davide Pesavento
2019-11-28 18:53 Davide Pesavento
2019-06-23 18:51 Davide Pesavento
2019-06-23 0:49 Davide Pesavento
2019-06-07 5:10 Davide Pesavento
2019-06-07 5:10 Davide Pesavento
2019-04-28 19:37 Davide Pesavento
2018-12-23 18:42 Davide Pesavento
2018-12-15 22:01 Davide Pesavento
2018-07-20 4:46 Davide Pesavento
2018-07-20 2:58 Davide Pesavento
2018-05-13 3:26 Davide Pesavento
2018-04-30 3:09 Davide Pesavento
2018-04-30 3:09 Davide Pesavento
2018-03-24 1:29 Davide Pesavento
2018-03-24 1:25 Davide Pesavento
2018-03-16 20:07 Davide Pesavento
2018-01-23 23:06 Davide Pesavento
2017-12-11 1:23 Davide Pesavento
2017-10-05 19:33 Davide Pesavento
2017-10-05 19:08 Davide Pesavento
2017-09-16 21:02 Davide Pesavento
2017-09-16 21:02 Davide Pesavento
2017-08-19 17:15 Davide Pesavento
2017-07-18 18:43 Davide Pesavento
2017-07-18 18:23 Davide Pesavento
2017-05-27 16:48 Davide Pesavento
2017-05-27 0:25 Davide Pesavento
2017-05-26 10:30 David Seifert
2017-05-26 10:00 David Seifert
2017-05-26 5:00 Davide Pesavento
2017-03-14 22:33 Davide Pesavento
2016-12-17 5:06 Davide Pesavento
2016-11-22 9:08 Davide Pesavento
2016-11-21 20:18 Davide Pesavento
2016-09-11 11:44 Davide Pesavento
2016-07-09 14:06 Davide Pesavento
2016-06-16 15:03 Davide Pesavento
2016-06-16 13:57 Michael Palimaka
2016-06-16 11:31 Davide Pesavento
2016-06-16 6:07 Patrick Lauer
2016-06-16 0:57 Davide Pesavento
2016-06-10 1:45 Davide Pesavento
2016-06-10 1:45 Davide Pesavento
2016-06-10 0:54 Davide Pesavento
2016-06-10 0:54 Davide Pesavento
2016-05-12 17:39 Davide Pesavento
2016-05-12 14:13 Davide Pesavento
2016-05-12 14:13 Davide Pesavento
2016-04-02 18:40 Davide Pesavento
2015-12-17 2:34 Davide Pesavento
2015-11-20 0:04 Davide Pesavento
2015-10-18 1:48 Davide Pesavento
2015-09-13 23:00 Davide Pesavento
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=1532055013.7d1311e3db7d1e3dcead9247fea6d2f5670c24b4.pesa@gentoo \
--to=pesa@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