public inbox for gentoo-commits@lists.gentoo.org
 help / color / mirror / Atom feed
From: "Agostino Sarubbo" <ago@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/gentoo:master commit in: kde-apps/spectacle/
Date: Sun, 16 Apr 2017 20:58:24 +0000 (UTC)	[thread overview]
Message-ID: <1492376293.d9c4b9cb02ee71a4eb2fc3de58a693845410f373.ago@gentoo> (raw)

commit:     d9c4b9cb02ee71a4eb2fc3de58a693845410f373
Author:     Agostino Sarubbo <ago <AT> gentoo <DOT> org>
AuthorDate: Sun Apr 16 20:56:18 2017 +0000
Commit:     Agostino Sarubbo <ago <AT> gentoo <DOT> org>
CommitDate: Sun Apr 16 20:58:13 2017 +0000
URL:        https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=d9c4b9cb

kde-apps/spectacle: amd64 stable wrt bug #612776

Package-Manager: Portage-2.3.3, Repoman-2.3.1
RepoMan-Options: --include-arches="amd64"
Signed-off-by: Agostino Sarubbo <ago <AT> gentoo.org>

 kde-apps/spectacle/spectacle-16.12.3.ebuild | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/kde-apps/spectacle/spectacle-16.12.3.ebuild b/kde-apps/spectacle/spectacle-16.12.3.ebuild
index 5f892af2e50..68b156b846d 100644
--- a/kde-apps/spectacle/spectacle-16.12.3.ebuild
+++ b/kde-apps/spectacle/spectacle-16.12.3.ebuild
@@ -8,7 +8,7 @@ inherit kde5
 
 DESCRIPTION="Screenshot capture utility"
 LICENSE="LGPL-2+ handbook? ( FDL-1.3 ) kipi? ( GPL-2+ )"
-KEYWORDS="~amd64 ~x86"
+KEYWORDS="amd64 ~x86"
 IUSE="kipi share"
 
 DEPEND="


             reply	other threads:[~2017-04-16 20:58 UTC|newest]

Thread overview: 48+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-04-16 20:58 Agostino Sarubbo [this message]
  -- strict thread matches above, loose matches on Subject: below --
2024-09-02 13:54 [gentoo-commits] repo/gentoo:master commit in: kde-apps/spectacle/ Andreas Sturmlechner
2024-08-24 17:20 Sam James
2024-06-17 17:13 Andreas Sturmlechner
2024-06-16  2:44 Sam James
2024-02-28 13:56 Andreas Sturmlechner
2022-10-31  1:26 WANG Xuerui
2022-04-22 19:18 Sam James
2022-04-15 22:43 Andreas Sturmlechner
2022-03-21 11:04 Andreas Sturmlechner
2021-12-21  3:56 Sam James
2021-08-04  9:01 Agostino Sarubbo
2021-08-04  8:40 Agostino Sarubbo
2021-06-05 10:57 Mikle Kolyada
2021-06-05 10:55 Mikle Kolyada
2021-06-05 10:53 Mikle Kolyada
2021-04-24 16:52 Andreas Sturmlechner
2021-04-06  6:31 Agostino Sarubbo
2021-02-23 20:10 Andreas Sturmlechner
2021-02-23 20:10 Andreas Sturmlechner
2021-01-28 21:53 Andreas Sturmlechner
2021-01-28 18:04 Georgy Yakovlev
2021-01-19 19:17 Sam James
2021-01-08  0:10 Andreas Sturmlechner
2020-07-30  7:21 Agostino Sarubbo
2020-07-30  6:58 Agostino Sarubbo
2020-03-19  6:25 Mikle Kolyada
2020-03-19  0:06 Agostino Sarubbo
2020-03-18 23:48 Agostino Sarubbo
2020-03-08 19:42 Andreas Sturmlechner
2020-01-26 10:26 Georgy Yakovlev
2019-12-02 23:29 Aaron Bauman
2019-12-02 16:33 Mikle Kolyada
2019-12-02 16:12 Mikle Kolyada
2019-07-28  2:45 Mikle Kolyada
2019-07-28  2:33 Mikle Kolyada
2019-03-21 11:34 Mikle Kolyada
2019-03-21 11:14 Mikle Kolyada
2019-02-24 21:37 Andreas Sturmlechner
2018-08-07  7:06 Andreas Sturmlechner
2018-07-29 12:56 Thomas Deutschmann
2018-07-29  0:38 Mikle Kolyada
2018-02-28 19:05 Andreas Sturmlechner
2017-11-30  2:07 Thomas Deutschmann
2017-04-17  8:02 Agostino Sarubbo
2016-05-31 19:06 Johannes Huber
2016-05-24 13:22 Mikle Kolyada
2016-05-20 16:47 Johannes Huber

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=1492376293.d9c4b9cb02ee71a4eb2fc3de58a693845410f373.ago@gentoo \
    --to=ago@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