From: oreo639 <oreo639@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: xdg-desktop-portal: update to 1.15.0.
Date: Sun, 02 Oct 2022 14:53:05 +0200 [thread overview]
Message-ID: <20221002125305.SvTz4X7f4ddCuk-BzS1A3UjVwEihk_rqf2pZP_vQA3A@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-39518@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 611 bytes --]
New comment by oreo639 on void-packages repository
https://github.com/void-linux/void-packages/pull/39518#issuecomment-1264635281
Comment:
> Would be more appropriate to do this with the update that would require the pre-release version.
I did. That was a separate PR.
> Also why did you switch to the automatically generated release tar ball instead of the one the developers upload with a known sha256 hash?
The autogen dist was missing test files.
Although I decided to leave pytest disabled since it couldn't find the xdg-desktop-portal executable, so it can be switched back, sorry about that.
next prev parent reply other threads:[~2022-10-02 12:53 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-28 22:54 [PR PATCH] " oreo639
2022-09-28 22:55 ` [PR PATCH] [Updated] " oreo639
2022-09-28 22:58 ` oreo639
2022-09-28 23:03 ` oreo639
2022-09-28 23:35 ` oreo639
2022-09-29 0:50 ` oreo639
2022-09-29 0:56 ` oreo639
2022-09-29 1:28 ` oreo639
2022-09-29 1:34 ` oreo639
2022-09-29 1:38 ` oreo639
2022-10-02 0:57 ` [PR PATCH] [Merged]: " classabbyamp
2022-10-02 12:34 ` Duncaen
2022-10-02 12:37 ` oreo639
2022-10-02 12:39 ` oreo639
2022-10-02 12:43 ` Duncaen
2022-10-02 12:44 ` oreo639
2022-10-02 12:49 ` oreo639
2022-10-02 12:51 ` oreo639
2022-10-02 12:53 ` oreo639 [this message]
2022-10-02 12:54 ` oreo639
2022-10-02 13:00 ` oreo639
2022-10-02 13:13 ` oreo639
2022-10-02 13:13 ` oreo639
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=20221002125305.SvTz4X7f4ddCuk-BzS1A3UjVwEihk_rqf2pZP_vQA3A@z \
--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).