public inbox for gentoo-commits@lists.gentoo.org
 help / color / mirror / Atom feed
From: "Jakov Smolić" <jsmolic@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/gentoo:master commit in: media-gfx/simple-scan/
Date: Thu, 20 Jan 2022 10:02:29 +0000 (UTC)	[thread overview]
Message-ID: <1642672920.ced964c7e21808439be3860a9605e7e5b8087b58.jsmolic@gentoo> (raw)

commit:     ced964c7e21808439be3860a9605e7e5b8087b58
Author:     Jakov Smolić <jsmolic <AT> gentoo <DOT> org>
AuthorDate: Thu Jan 20 09:57:59 2022 +0000
Commit:     Jakov Smolić <jsmolic <AT> gentoo <DOT> org>
CommitDate: Thu Jan 20 10:02:00 2022 +0000
URL:        https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=ced964c7

media-gfx/simple-scan: Stabilize 40.7 x86, #831048

Signed-off-by: Jakov Smolić <jsmolic <AT> gentoo.org>

 media-gfx/simple-scan/simple-scan-40.7.ebuild | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/media-gfx/simple-scan/simple-scan-40.7.ebuild b/media-gfx/simple-scan/simple-scan-40.7.ebuild
index 49c10ec79a39..7a7e6ff18d69 100644
--- a/media-gfx/simple-scan/simple-scan-40.7.ebuild
+++ b/media-gfx/simple-scan/simple-scan-40.7.ebuild
@@ -11,7 +11,7 @@ HOMEPAGE="https://gitlab.gnome.org/GNOME/simple-scan"
 
 LICENSE="GPL-3+"
 SLOT="0"
-KEYWORDS="~amd64 ~arm ~arm64 ~ppc ppc64 ~x86"
+KEYWORDS="~amd64 ~arm ~arm64 ~ppc ppc64 x86"
 IUSE="colord webp"
 
 DEPEND="


             reply	other threads:[~2022-01-20 10:02 UTC|newest]

Thread overview: 73+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-01-20 10:02 Jakov Smolić [this message]
  -- strict thread matches above, loose matches on Subject: below --
2024-07-15 19:22 [gentoo-commits] repo/gentoo:master commit in: media-gfx/simple-scan/ Pacho Ramos
2024-05-28 12:35 Sam James
2023-05-04 16:15 Arthur Zamarin
2023-05-03  7:03 Arthur Zamarin
2023-05-02 20:13 Arthur Zamarin
2023-05-02 19:19 Arthur Zamarin
2023-03-19 23:38 Matt Turner
2023-02-15 11:55 Yixun Lan
2022-11-23 17:52 Jakov Smolić
2022-11-07  7:26 Sam James
2022-11-05  9:58 Arthur Zamarin
2022-10-31  2:56 Matt Turner
2022-09-24 15:34 Matt Turner
2022-05-28  5:05 Sam James
2022-05-28  1:27 Sam James
2022-05-28  1:20 Sam James
2022-04-19 17:57 Matt Turner
2022-03-25 21:56 Matt Turner
2022-01-24 14:49 Sam James
2022-01-24  3:39 Sam James
2022-01-20  9:42 Arthur Zamarin
2022-01-13  2:00 Georgy Yakovlev
2021-12-23 11:51 Pacho Ramos
2021-12-19 18:15 Mart Raudsepp
2021-11-11 13:52 Pacho Ramos
2021-09-26 10:34 Pacho Ramos
2021-07-11  9:23 Mart Raudsepp
2021-05-29 15:27 Sam James
2021-05-29  9:02 Sam James
2021-05-29  6:09 Sam James
2021-05-28 19:20 Sam James
2021-05-25 18:51 Matt Turner
2021-04-17 22:23 Matt Turner
2021-04-13 16:12 Matt Turner
2021-04-13 15:00 Sam James
2021-04-01 16:44 Thomas Deutschmann
2021-03-12  8:01 Mikle Kolyada
2020-12-19 15:14 Mart Raudsepp
2020-12-13 12:16 Sergei Trofimovich
2020-11-07 15:23 Mart Raudsepp
2020-08-30 18:09 Sam James
2020-08-30 15:17 Thomas Deutschmann
2020-07-17 20:44 Mart Raudsepp
2020-07-04 15:07 Mart Raudsepp
2020-06-29 15:42 Mikle Kolyada
2020-06-28 14:19 Thomas Deutschmann
2020-06-15 18:04 Sergei Trofimovich
2020-04-29 20:08 Mart Raudsepp
2020-03-21 18:57 Mart Raudsepp
2020-02-19 22:39 Mart Raudsepp
2019-12-23 22:02 Mart Raudsepp
2019-07-28  6:42 Mart Raudsepp
2019-05-18 23:05 Mart Raudsepp
2019-04-25 21:52 Sobhan Mohammadpour
2019-03-22 22:33 Mart Raudsepp
2019-03-22 22:33 Mart Raudsepp
2019-01-12 23:24 Sergei Trofimovich
2019-01-12 23:24 Sergei Trofimovich
2018-02-03 22:46 Mart Raudsepp
2018-01-18  2:44 Mikle Kolyada
2017-08-12 23:15 Gilles Dartiguelongue
2017-04-02 13:03 Mart Raudsepp
2016-10-23 23:01 Gilles Dartiguelongue
2016-10-23 23:01 Gilles Dartiguelongue
2016-07-02 17:12 Pacho Ramos
2016-07-02 17:12 Pacho Ramos
2016-03-06 20:12 Mikle Kolyada
2015-12-14 23:39 Gilles Dartiguelongue
2015-12-12 10:28 Pacho Ramos
2015-11-17 20:23 Pacho Ramos
2015-09-05 17:09 Pacho Ramos
2015-09-05 17:09 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=1642672920.ced964c7e21808439be3860a9605e7e5b8087b58.jsmolic@gentoo \
    --to=jsmolic@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