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: gnome-base/gdm/
Date: Wed, 23 Nov 2022 17:52:46 +0000 (UTC)	[thread overview]
Message-ID: <1669225950.195a87822060d9a830a9caa089e0edba556d6e4a.jsmolic@gentoo> (raw)

commit:     195a87822060d9a830a9caa089e0edba556d6e4a
Author:     Jakov Smolić <jsmolic <AT> gentoo <DOT> org>
AuthorDate: Wed Nov 23 17:52:30 2022 +0000
Commit:     Jakov Smolić <jsmolic <AT> gentoo <DOT> org>
CommitDate: Wed Nov 23 17:52:30 2022 +0000
URL:        https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=195a8782

gnome-base/gdm: Stabilize 43.0 x86, #879807

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

 gnome-base/gdm/gdm-43.0.ebuild | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/gnome-base/gdm/gdm-43.0.ebuild b/gnome-base/gdm/gdm-43.0.ebuild
index ce5557813473..d369e079f7c2 100644
--- a/gnome-base/gdm/gdm-43.0.ebuild
+++ b/gnome-base/gdm/gdm-43.0.ebuild
@@ -23,7 +23,7 @@ IUSE="accessibility audit bluetooth-sound branding elogind fprint plymouth selin
 RESTRICT="!test? ( test )"
 REQUIRED_USE="^^ ( elogind systemd )"
 
-KEYWORDS="amd64 ~arm arm64 ~ppc64 ~riscv ~x86"
+KEYWORDS="amd64 ~arm arm64 ~ppc64 ~riscv x86"
 
 # dconf, dbus and g-s-d are needed at install time for dconf update
 # keyutils is automagic dep that makes autologin unlock login keyring when all the passwords match (disk encryption, user pw and login keyring)


             reply	other threads:[~2022-11-23 17:52 UTC|newest]

Thread overview: 72+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-11-23 17:52 Jakov Smolić [this message]
  -- strict thread matches above, loose matches on Subject: below --
2025-01-28 17:04 [gentoo-commits] repo/gentoo:master commit in: gnome-base/gdm/ Sam James
2025-01-26 17:32 Pacho Ramos
2024-12-01 11:18 Pacho Ramos
2024-11-24 22:24 Sam James
2024-06-01  1:42 Erik Mackdanz
2024-02-18  6:08 Arthur Zamarin
2024-01-08 17:27 Sam James
2024-01-08 17:27 Sam James
2023-09-14 19:19 Matt Turner
2023-07-27  5:11 WANG Xuerui
2023-06-19 15:30 Matt Turner
2023-06-17 17:10 Arthur Zamarin
2023-06-03 18:01 Arthur Zamarin
2023-06-03  3:23 Sam James
2023-05-06  0:40 Matt Turner
2023-05-05  6:16 Arthur Zamarin
2023-05-02 19:55 Arthur Zamarin
2023-05-02 18:28 Arthur Zamarin
2022-11-05  5:59 Arthur Zamarin
2022-10-30 16:34 Matt Turner
2022-09-25  1:49 Matt Turner
2022-06-16 16:30 Sam James
2022-03-26 18:01 Matt Turner
2022-02-20  0:04 Matt Turner
2021-08-27 15:19 Yixun Lan
2021-08-20 23:51 Sam James
2021-07-23 19:53 Matt Turner
2021-07-11 20:48 Sam James
2021-06-12  8:07 Pacho Ramos
2021-04-30 19:56 Matt Turner
2021-04-12 23:11 Sam James
2021-03-25 16:20 Sam James
2021-03-04  0:23 Sam James
2021-01-18 21:10 Matt Turner
2020-12-14 16:47 Mike Gilbert
2020-11-08 10:17 Mart Raudsepp
2020-07-17 20:23 Mart Raudsepp
2020-07-13 13:12 Mart Raudsepp
2020-04-25 21:14 Mart Raudsepp
2020-03-15 17:38 Mart Raudsepp
2019-10-13 10:32 Mart Raudsepp
2019-10-12 18:36 Mikle Kolyada
2019-08-03 19:04 Aaron Bauman
2019-03-30 21:56 Mart Raudsepp
2019-02-27  0:11 Mart Raudsepp
2018-09-28 13:51 Mart Raudsepp
2018-08-17  0:36 Mart Raudsepp
2018-08-17  0:17 Mikle Kolyada
2018-08-16 12:03 Thomas Deutschmann
2018-01-18  2:35 Mikle Kolyada
2017-09-13 22:28 Gilles Dartiguelongue
2017-09-03  1:15 Mike Gilbert
2017-08-22 15:57 Michał Górny
2017-07-14  8:52 Mart Raudsepp
2017-07-14  8:52 Mart Raudsepp
2017-07-14  8:52 Mart Raudsepp
2017-04-20 16:14 Michał Górny
2017-03-19 11:43 Mart Raudsepp
2017-03-19 11:43 Mart Raudsepp
2017-03-19 11:43 Mart Raudsepp
2017-02-04 15:26 Pacho Ramos
2016-12-30  3:48 Mart Raudsepp
2016-11-12  0:37 Gilles Dartiguelongue
2016-04-17 11:13 Pacho Ramos
2016-04-17 11:13 Pacho Ramos
2016-03-06 17:23 Mikle Kolyada
2015-11-19 19:23 Pacho Ramos
2015-11-19 19:23 Pacho Ramos
2015-11-15 22:30 Pacho Ramos
2015-11-15 22:30 Pacho Ramos
2015-09-20 16:19 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=1669225950.195a87822060d9a830a9caa089e0edba556d6e4a.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