[gnome-software/mwleeds/fix-deprecated-install] flatpak: Update remote name for flatpakref unit test
- From: Phaedrus Leeds <mwleeds src gnome org>
- To: commits-list gnome org
- Cc:
- Subject: [gnome-software/mwleeds/fix-deprecated-install] flatpak: Update remote name for flatpakref unit test
- Date: Wed, 13 Oct 2021 18:22:48 +0000 (UTC)
commit 7c456c614c34feb85a9f4953fc230c048fb34bac
Author: Phaedrus Leeds <mwleeds protonmail com>
Date: Wed Oct 13 11:19:56 2021 -0700
flatpak: Update remote name for flatpakref unit test
Now that we are using the FlatpakTransaction API instead of
FlatpakInstallation to install flatpakref files, the RuntimeRepo= key is
properly handled and Flatpak uses it to create a remote. In the case of
the unit test for flatpakref installation, the RuntimeRepo file is
called "test.flatpakrepo" so "test" becomes the name of the remote, and
the remote is then used as the origin for the app as well since it has
both the app and the runtime in it. So, update an assertion to account
for the new origin remote name for the test flatpakref file.
plugins/flatpak/gs-self-test.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
---
diff --git a/plugins/flatpak/gs-self-test.c b/plugins/flatpak/gs-self-test.c
index 525b45487..0fece1e68 100644
--- a/plugins/flatpak/gs-self-test.c
+++ b/plugins/flatpak/gs-self-test.c
@@ -1208,7 +1208,7 @@ flatpak_bundle_or_ref_helper (GsPluginLoader *plugin_loader,
#if FLATPAK_CHECK_VERSION(1,1,2)
g_printerr ("app unique ID = %s\n", gs_app_get_unique_id (app));
g_assert_true (as_utils_data_id_equal (gs_app_get_unique_id (app),
- "user/flatpak/chiron-origin/org.test.Chiron/master"));
+ "user/flatpak/test/org.test.Chiron/master"));
#else
g_assert_true (as_utils_data_id_equal (gs_app_get_unique_id (app),
"user/flatpak/org.test.Chiron-origin/org.test.Chiron/master"));
[
Date Prev][
Date Next] [
Thread Prev][
Thread Next]
[
Thread Index]
[
Date Index]
[
Author Index]