From: oreo639 <oreo639@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [PR PATCH] [Merged]: libportal: update to 0.7.1, enable qt5 backend, add check
Date: Mon, 04 Mar 2024 14:21:37 +0100 [thread overview]
Message-ID: <20240304132137.AAE1522015@inbox.vuxu.org> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-48662@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 596 bytes --]
There's a merged pull request on the void-packages repository
libportal: update to 0.7.1, enable qt5 backend, add check
https://github.com/void-linux/void-packages/pull/48662
Description:
New apps requires the current `libportal`.
Also I enabled qt5 backend, and added check via pytest.
#### 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)
- I built this PR locally for these architectures (if supported. mark crossbuilds):
- aarch64-musl x
- armv7l x
- armv6l-musl x
prev parent reply other threads:[~2024-03-04 13:21 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-11 22:33 [PR PATCH] " chrysos349
2024-02-12 0:42 ` [PR REVIEW] " oreo639
2024-02-12 4:49 ` [PR PATCH] [Updated] " chrysos349
2024-02-12 4:56 ` [PR REVIEW] " chrysos349
2024-02-12 14:34 ` [PR PATCH] [Updated] " chrysos349
2024-02-15 11:57 ` [PR REVIEW] " sgn
2024-02-15 11:57 ` sgn
2024-02-15 19:49 ` chrysos349
2024-02-15 20:46 ` oreo639
2024-02-15 20:47 ` oreo639
2024-02-15 20:53 ` oreo639
2024-02-15 21:35 ` [PR PATCH] [Updated] " chrysos349
2024-02-15 21:46 ` [PR REVIEW] " chrysos349
2024-03-04 11:24 ` oreo639
2024-03-04 11:24 ` oreo639
2024-03-04 13:01 ` [PR PATCH] [Updated] " chrysos349
2024-03-04 13:10 ` chrysos349
2024-03-04 13:11 ` [PR PATCH] [Updated] " chrysos349
2024-03-04 13:21 ` oreo639 [this message]
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=20240304132137.AAE1522015@inbox.vuxu.org \
--to=oreo639@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).