From: "Mart Raudsepp" <leio@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/gentoo:master commit in: net-wireless/gnome-bluetooth/
Date: Fri, 9 Feb 2024 22:27:32 +0000 (UTC) [thread overview]
Message-ID: <1707517606.55fcc6095a43d33d906f1646624a30308286a74f.leio@gentoo> (raw)
commit: 55fcc6095a43d33d906f1646624a30308286a74f
Author: Mart Raudsepp <leio <AT> gentoo <DOT> org>
AuthorDate: Fri Feb 9 22:26:46 2024 +0000
Commit: Mart Raudsepp <leio <AT> gentoo <DOT> org>
CommitDate: Fri Feb 9 22:26:46 2024 +0000
URL: https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=55fcc609
net-wireless/gnome-bluetooth: fix gnome2_env_reset typo
Signed-off-by: Mart Raudsepp <leio <AT> gentoo.org>
net-wireless/gnome-bluetooth/gnome-bluetooth-42.8.ebuild | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/net-wireless/gnome-bluetooth/gnome-bluetooth-42.8.ebuild b/net-wireless/gnome-bluetooth/gnome-bluetooth-42.8.ebuild
index c09f8f7bf93a..bb80dbb3a638 100644
--- a/net-wireless/gnome-bluetooth/gnome-bluetooth-42.8.ebuild
+++ b/net-wireless/gnome-bluetooth/gnome-bluetooth-42.8.ebuild
@@ -68,7 +68,7 @@ src_configure() {
src_test() {
# Workaround test failures caused by flatpak being installed that adds to XDG_DATA_DIRS
- gnome_environment_reset
+ gnome2_environment_reset
export XDG_DATA_DIRS="${EPREFIX}"/usr/share
meson_src_test
next reply other threads:[~2024-02-09 22:27 UTC|newest]
Thread overview: 79+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-09 22:27 Mart Raudsepp [this message]
-- strict thread matches above, loose matches on Subject: below --
2024-10-17 8:51 [gentoo-commits] repo/gentoo:master commit in: net-wireless/gnome-bluetooth/ Pacho Ramos
2024-10-17 8:51 Pacho Ramos
2024-07-15 20:36 Pacho Ramos
2024-07-15 20:36 Pacho Ramos
2024-05-06 7:09 Mart Raudsepp
2024-05-01 5:28 Joonas Niilola
2024-04-07 9:14 Arthur Zamarin
2024-04-07 5:55 Arthur Zamarin
2024-02-11 14:21 Mart Raudsepp
2024-02-11 8:09 Arthur Zamarin
2024-02-09 22:26 Mart Raudsepp
2023-11-24 12:37 Pacho Ramos
2023-09-05 20:28 Matt Turner
2023-08-15 14:39 Matt Turner
2023-07-27 5:11 WANG Xuerui
2023-02-20 17:32 Matt Turner
2023-02-17 8:23 Arthur Zamarin
2022-12-14 3:20 Matt Turner
2022-12-04 3:03 Matt Turner
2022-12-04 2:41 Matt Turner
2022-10-30 13:10 Pacho Ramos
2022-10-29 17:44 Matt Turner
2022-10-15 15:01 Sam James
2022-10-15 15:01 Sam James
2022-10-14 14:29 Matt Turner
2022-09-12 16:01 Sam James
2022-09-12 16:00 Sam James
2022-09-05 21:44 Matt Turner
2022-08-24 14:36 Matt Turner
2022-07-29 2:59 Sam James
2022-07-21 2:04 Matt Turner
2022-07-18 23:41 Sam James
2022-07-07 18:06 Matt Turner
2022-06-17 17:45 Matt Turner
2022-06-10 13:28 Matt Turner
2022-05-20 19:16 Pacho Ramos
2022-05-07 18:28 Arthur Zamarin
2022-03-21 0:53 Matt Turner
2022-03-20 22:45 Matt Turner
2022-03-20 19:54 Matt Turner
2021-08-27 15:19 Yixun Lan
2021-05-31 2:00 Matt Turner
2021-04-17 22:49 Matt Turner
2021-04-16 1:47 Matt Turner
2021-04-13 16:12 Matt Turner
2021-04-12 23:11 Sam James
2021-04-01 16:44 Thomas Deutschmann
2021-03-12 8:01 Mikle Kolyada
2020-11-11 4:30 Matt Turner
2020-04-25 20:17 Mart Raudsepp
2020-04-20 18:16 Agostino Sarubbo
2020-04-20 17:03 Agostino Sarubbo
2020-03-15 11:40 Mart Raudsepp
2019-12-23 22:23 Mart Raudsepp
2019-12-08 11:52 Mikle Kolyada
2019-12-08 11:41 Mikle Kolyada
2019-09-23 10:39 Mart Raudsepp
2019-09-13 12:58 Michał Górny
2019-04-19 10:42 Mart Raudsepp
2019-04-18 20:32 Thomas Deutschmann
2019-04-14 10:23 Agostino Sarubbo
2019-04-13 9:47 Mart Raudsepp
2018-12-06 20:51 Mart Raudsepp
2018-11-02 23:07 Mart Raudsepp
2018-11-02 23:07 Mart Raudsepp
2018-05-12 0:33 Matt Turner
2017-07-25 12:27 Alexis Ballier
2017-04-01 16:31 Agostino Sarubbo
2017-04-01 13:16 Agostino Sarubbo
2017-03-21 1:46 Mart Raudsepp
2017-03-21 1:46 Mart Raudsepp
2016-06-28 20:30 Pacho Ramos
2016-06-28 20:30 Pacho Ramos
2016-06-11 19:39 Pacho Ramos
2016-06-11 12:06 Pacho Ramos
2016-03-06 17:23 Mikle Kolyada
2016-01-30 12:23 Pacho Ramos
2015-09-12 9:11 Agostino Sarubbo
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=1707517606.55fcc6095a43d33d906f1646624a30308286a74f.leio@gentoo \
--to=leio@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