From: "Gilles Dartiguelongue" <eva@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] proj/gnome:master commit in: gnome-base/gnome-control-center/
Date: Mon, 10 Sep 2018 21:33:54 +0000 (UTC) [thread overview]
Message-ID: <1536577431.0ba862c6c0b28c90d5f98a94408b85c75a0f658e.eva@gentoo> (raw)
commit: 0ba862c6c0b28c90d5f98a94408b85c75a0f658e
Author: Gilles Dartiguelongue <eva <AT> gentoo <DOT> org>
AuthorDate: Mon Sep 10 11:03:51 2018 +0000
Commit: Gilles Dartiguelongue <eva <AT> gentoo <DOT> org>
CommitDate: Mon Sep 10 11:03:51 2018 +0000
URL: https://gitweb.gentoo.org/proj/gnome.git/commit/?id=0ba862c6
gnome-base/gnome-control-center: remove unneeded QA check workaround
Package-Manager: Portage-2.3.49, Repoman-2.3.10
RepoMan-Options: --force
Manifest-Sign-Key: 0x5A56C8CD0C13248A
gnome-base/gnome-control-center/gnome-control-center-3.26.2.ebuild | 3 ---
1 file changed, 3 deletions(-)
diff --git a/gnome-base/gnome-control-center/gnome-control-center-3.26.2.ebuild b/gnome-base/gnome-control-center/gnome-control-center-3.26.2.ebuild
index cd5abacb..cbf8f1dc 100644
--- a/gnome-base/gnome-control-center/gnome-control-center-3.26.2.ebuild
+++ b/gnome-base/gnome-control-center/gnome-control-center-3.26.2.ebuild
@@ -16,9 +16,6 @@ SLOT="2"
IUSE="+bluetooth +colord +cups debug +gnome-online-accounts +ibus input_devices_wacom kerberos networkmanager v4l wayland"
KEYWORDS="~alpha ~amd64 ~arm ~arm64 ~ia64 ~ppc ~ppc64 ~sh ~x86 ~x86-fbsd ~amd64-linux ~x86-linux ~x86-solaris"
-# False positives caused by nested configure scripts
-QA_CONFIGURE_OPTIONS=".*"
-
# gnome-session-2.91.6-r1 is needed so that 10-user-dirs-update is run at login
# g-s-d[policykit] needed for bug #403527
# kerberos unfortunately means mit-krb5; build fails with heimdal
next reply other threads:[~2018-09-10 21:34 UTC|newest]
Thread overview: 39+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-09-10 21:33 Gilles Dartiguelongue [this message]
-- strict thread matches above, loose matches on Subject: below --
2018-09-28 17:58 [gentoo-commits] proj/gnome:master commit in: gnome-base/gnome-control-center/ Mart Raudsepp
2018-09-26 20:29 Mart Raudsepp
2018-09-26 20:29 Mart Raudsepp
2018-04-16 16:28 Sobhan Mohammadpour
2018-02-09 15:55 Sobhan Mohammadpour
2018-01-12 12:09 Dennis Lamm
2015-05-17 15:39 Gilles Dartiguelongue
2015-05-12 22:20 Gilles Dartiguelongue
2014-12-22 23:11 Gilles Dartiguelongue
2014-11-23 22:28 Gilles Dartiguelongue
2014-10-15 22:26 Gilles Dartiguelongue
2014-10-11 23:30 Gilles Dartiguelongue
2014-04-25 23:35 Gilles Dartiguelongue
2014-02-12 20:58 Gilles Dartiguelongue
2013-01-22 8:12 Alexandre Rostovtsev
2012-12-25 22:01 Gilles Dartiguelongue
2012-11-18 19:33 Gilles Dartiguelongue
2012-10-25 6:30 Priit Laes
2012-09-30 0:15 Alexandre Rostovtsev
2012-09-08 0:37 Alexandre Restovtsev
2012-04-06 9:00 Alexandre Restovtsev
2011-10-02 19:11 Alexandre Restovtsev
2011-06-02 17:39 Nirbheek Chauhan
2011-05-30 18:39 Nirbheek Chauhan
2011-04-27 22:22 Gilles Dartiguelongue
2011-04-08 10:52 Gilles Dartiguelongue
2011-04-07 13:44 Nirbheek Chauhan
2011-04-05 0:57 Nirbheek Chauhan
2011-03-26 5:10 Jonathan Callen
2011-03-26 2:54 Nirbheek Chauhan
2011-03-23 5:20 Nirbheek Chauhan
2011-03-15 13:08 Nirbheek Chauhan
2011-03-09 11:34 Nirbheek Chauhan
2011-03-04 14:57 Nirbheek Chauhan
2011-02-28 20:25 Nirbheek Chauhan
2011-02-28 10:19 Nirbheek Chauhan
2011-02-27 3:02 Jonathan Callen
2011-02-22 19:44 Nirbheek Chauhan
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=1536577431.0ba862c6c0b28c90d5f98a94408b85c75a0f658e.eva@gentoo \
--to=eva@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