public inbox for gentoo-commits@lists.gentoo.org
 help / color / mirror / Atom feed
From: "Mart Raudsepp" <leio@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/gentoo:master commit in: gnome-extra/gnome-software/
Date: Sat,  6 Jan 2024 15:32:57 +0000 (UTC)	[thread overview]
Message-ID: <1704554204.a82ee9a963684e9c8a7ab0824519319fbb075223.leio@gentoo> (raw)

commit:     a82ee9a963684e9c8a7ab0824519319fbb075223
Author:     Mart Raudsepp <leio <AT> gentoo <DOT> org>
AuthorDate: Sat Jan  6 15:16:44 2024 +0000
Commit:     Mart Raudsepp <leio <AT> gentoo <DOT> org>
CommitDate: Sat Jan  6 15:16:44 2024 +0000
URL:        https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=a82ee9a9

gnome-extra/gnome-software: drop unintended src_test changes

These didn't help solve a flatpak plugin test failure for me and thus weren't
meant to be included in the bump, but had forgotten to clean it up before
pushing.

Signed-off-by: Mart Raudsepp <leio <AT> gentoo.org>

 gnome-extra/gnome-software/gnome-software-45.3.ebuild | 2 --
 1 file changed, 2 deletions(-)

diff --git a/gnome-extra/gnome-software/gnome-software-45.3.ebuild b/gnome-extra/gnome-software/gnome-software-45.3.ebuild
index 3955b249234f..029c629a83c8 100644
--- a/gnome-extra/gnome-software/gnome-software-45.3.ebuild
+++ b/gnome-extra/gnome-software/gnome-software-45.3.ebuild
@@ -92,8 +92,6 @@ src_configure() {
 }
 
 src_test() {
-	gnome_environment_reset
-	export XDG_DATA_DIRS="${EPREFIX}"/usr/share
 	virtx dbus-run-session meson test -C "${BUILD_DIR}" || die
 }
 


             reply	other threads:[~2024-01-06 15:33 UTC|newest]

Thread overview: 65+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-01-06 15:32 Mart Raudsepp [this message]
  -- strict thread matches above, loose matches on Subject: below --
2024-08-06  9:21 [gentoo-commits] repo/gentoo:master commit in: gnome-extra/gnome-software/ Pacho Ramos
2024-08-06  9:21 Pacho Ramos
2024-06-16  7:18 Pacho Ramos
2024-06-16  7:18 Pacho Ramos
2024-06-16  7:18 Pacho Ramos
2024-01-05 18:55 Mart Raudsepp
2024-01-05 18:55 Mart Raudsepp
2023-12-16  9:58 Pacho Ramos
2023-10-21 21:52 Mart Raudsepp
2023-09-22  2:33 Matt Turner
2023-09-15 16:52 Matt Turner
2023-09-01 15:13 Matt Turner
2023-08-08 15:25 Matt Turner
2023-08-02 14:51 Matt Turner
2023-07-07 22:03 Matt Turner
2023-06-19 15:30 Matt Turner
2023-05-26  1:44 Matt Turner
2023-05-17  7:49 Sam James
2023-04-22  3:08 Matt Turner
2023-03-16 17:42 Matt Turner
2023-03-04  1:15 Matt Turner
2023-02-20 17:32 Matt Turner
2023-02-10 19:18 Matt Turner
2023-01-18 20:22 Mart Raudsepp
2023-01-07 17:42 Matt Turner
2022-12-02 14:35 Matt Turner
2022-10-30 22:29 Matt Turner
2022-10-25 15:25 Matt Turner
2022-08-05 20:49 Matt Turner
2022-07-02  2:53 Matt Turner
2022-05-30 18:22 Matt Turner
2022-04-28 15:31 Matt Turner
2022-04-24 22:45 Matt Turner
2022-02-19 23:55 Matt Turner
2021-08-13 16:34 Mart Raudsepp
2021-07-10 16:24 Mart Raudsepp
2021-06-13 20:25 Sam James
2021-06-06 21:49 Matt Turner
2021-06-06 21:49 Matt Turner
2021-05-01  2:59 Matt Turner
2021-04-18  4:21 Matt Turner
2020-11-27 12:19 David Seifert
2020-07-12 21:32 Mart Raudsepp
2020-04-18  7:37 Mart Raudsepp
2020-04-04 20:48 Mart Raudsepp
2020-02-19 22:01 Mart Raudsepp
2019-07-28 17:41 Mart Raudsepp
2019-03-30 22:50 Mart Raudsepp
2019-03-22 12:20 Mart Raudsepp
2019-03-22 12:20 Mart Raudsepp
2018-12-11 13:07 Gilles Dartiguelongue
2017-08-26 10:07 Gilles Dartiguelongue
2017-08-12  9:42 Gilles Dartiguelongue
2017-03-23  6:54 Mart Raudsepp
2017-01-04 22:37 Gilles Dartiguelongue
2017-01-04 22:37 Gilles Dartiguelongue
2016-11-12 12:23 Gilles Dartiguelongue
2016-10-24  7:22 Gilles Dartiguelongue
2016-10-24  7:22 Gilles Dartiguelongue
2016-10-08  9:51 Pacho Ramos
2016-10-08  9:51 Pacho Ramos
2016-10-08  9:51 Pacho Ramos
2016-09-06 22:10 Gilles Dartiguelongue
2016-01-03 13:32 Gilles Dartiguelongue

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=1704554204.a82ee9a963684e9c8a7ab0824519319fbb075223.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