Github messages for voidlinux
 help / color / mirror / Atom feed
From: RangHo <RangHo@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [PR PATCH] [Updated] libportal: update to 0.9.0
Date: Tue, 04 Feb 2025 07:14:58 +0100	[thread overview]
Message-ID: <20250204061458.5838928B37@inbox.vuxu.org> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-53691@inbox.vuxu.org>

[-- Attachment #1: Type: text/plain, Size: 827 bytes --]

There is an updated pull request by RangHo against master on the void-packages repository

https://github.com/RangHo/void-packages update-libportal
https://github.com/void-linux/void-packages/pull/53691

libportal: update to 0.9.0
<!-- Uncomment relevant sections and delete options which are not applicable -->

#### Testing the changes
- I tested the changes in this PR: **briefly**

#### Local build testing
- I built this PR locally for my native architecture, `x86_64-glibc`

#### Notes
- This PR is marked as draft because Vala 0.56.16 does not recognize `pid_t` as a valid type[^1]. As such, #53689 must be merged beforehand.

[^1]: https://github.com/GNOME/vala/blob/0732bb119d968a8bab154c308d1498a31aa7d6af/NEWS#L20

A patch file from https://github.com/void-linux/void-packages/pull/53691.patch is attached

[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: github-pr-update-libportal-53691.patch --]
[-- Type: text/x-diff, Size: 3489 bytes --]

From 05b7cc6f7224e7a830e6c4149f1437d6660a123f Mon Sep 17 00:00:00 2001
From: RangHo Lee <hello@rangho.me>
Date: Thu, 26 Dec 2024 19:05:08 +0900
Subject: [PATCH] libportal: update to 0.9.0

---
 srcpkgs/libportal/patches/fix-pytest.patch | 47 ----------------------
 srcpkgs/libportal/template                 |  4 +-
 2 files changed, 2 insertions(+), 49 deletions(-)
 delete mode 100644 srcpkgs/libportal/patches/fix-pytest.patch

diff --git a/srcpkgs/libportal/patches/fix-pytest.patch b/srcpkgs/libportal/patches/fix-pytest.patch
deleted file mode 100644
index ea055c832dc8e3..00000000000000
--- a/srcpkgs/libportal/patches/fix-pytest.patch
+++ /dev/null
@@ -1,47 +0,0 @@
-From 6cd7c2ab82575b76f876ee2bd2d31f6cb77f022f Mon Sep 17 00:00:00 2001
-From: Simon McVittie <smcv@debian.org>
-Date: Tue, 26 Dec 2023 14:35:46 +0000
-Subject: [PATCH] pyportaltest: Only create one session bus per DBusTestCase
- subclass
-
-DBusTestCase.start_session_bus() is a class method, and can only be
-called once per class, because DBusTestCase.tearDownClass() will only
-clean up one session bus. In older versions of dbusmock, calling it more
-than once will result in dbus-daemon processes being leaked; since
-0.30.0, calling it more than once will result in an assertion failure.
-
-Resolves: https://github.com/flatpak/libportal/issues/136
-Bug-Debian: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1058245
-Signed-off-by: Simon McVittie <smcv@debian.org>
----
- tests/pyportaltest/__init__.py | 10 +++++++++-
- 1 file changed, 9 insertions(+), 1 deletion(-)
-
-diff --git a/tests/pyportaltest/__init__.py b/tests/pyportaltest/__init__.py
-index af053c2a..80f04a91 100644
---- a/tests/pyportaltest/__init__.py
-+++ b/tests/pyportaltest/__init__.py
-@@ -83,6 +83,14 @@ def setUpClass(cls):
-         except AttributeError:
-             pytest.skip("Updated version of dbusmock required")
- 
-+        cls.__have_session_bus = False
-+
-+    @classmethod
-+    def ensure_session_bus(cls):
-+        if not cls.__have_session_bus:
-+            cls.__have_session_bus = True
-+            cls.start_session_bus()
-+
-     def setUp(self):
-         self.p_mock = None
-         self._mainloop = None
-@@ -96,7 +104,7 @@ def setup_daemon(self, params=None, extra_templates: List[Tuple[str, Dict]] = []
-         portal name as first value and the param dict to be passed to that
-         template as second value, e.g. ("ScreenCast", {...}).
-         """
--        self.start_session_bus()
-+        self.ensure_session_bus()
-         self.p_mock, self.obj_portal = self.spawn_server_template(
-             template=f"pyportaltest/templates/{self.PORTAL_NAME.lower()}.py",
-             parameters=params,
diff --git a/srcpkgs/libportal/template b/srcpkgs/libportal/template
index 22e83cc40716d4..a3cffa0a51ee99 100644
--- a/srcpkgs/libportal/template
+++ b/srcpkgs/libportal/template
@@ -1,6 +1,6 @@
 # Template file for 'libportal'
 pkgname=libportal
-version=0.7.1
+version=0.9.0
 revision=1
 build_style=meson
 build_helper="gir"
@@ -16,7 +16,7 @@ maintainer="Orphaned <orphan@voidlinux.org>"
 license="LGPL-2.0-or-later"
 homepage="https://github.com/flatpak/libportal"
 distfiles="https://github.com/flatpak/${pkgname}/releases/download/${version}/${pkgname}-${version}.tar.xz"
-checksum=297b90b263fad22190a26b8c7e8ea938fe6b18fb936265e588927179920d3805
+checksum=113910f06f39387328805397053d20c7acafb7388d8e6cd5e06e05efb9690735
 make_check_pre="xvfb-run"
 
 build_options="gir gtk_doc"

  reply	other threads:[~2025-02-04  6:14 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-12-26 13:10 [PR PATCH] " RangHo
2025-02-04  6:14 ` RangHo [this message]
2025-02-04  6:17 ` RangHo

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=20250204061458.5838928B37@inbox.vuxu.org \
    --to=rangho@users.noreply.github.com \
    --cc=ml@inbox.vuxu.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;
as well as URLs for NNTP newsgroup(s).