From: tornaria <tornaria@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: owncloudclient: update to 5.2.1.
Date: Thu, 04 Apr 2024 01:03:57 +0200 [thread overview]
Message-ID: <20240403230357.48B0320E02@inbox.vuxu.org> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-47025@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 397 bytes --]
New comment by tornaria on void-packages repository
https://github.com/void-linux/void-packages/pull/47025#issuecomment-2035760269
Comment:
@ahesford it makes a lot of sense, sorry I missed that. I did it in the four templates. I tested locally the cross-build on aarch64 to make sure I got the `hostmakedepends` right (sometimes `qt6-base` suffices, other times `qt6-tools` is also necessary).
next prev parent reply other threads:[~2024-04-03 23:03 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-02 17:24 [PR PATCH] owncloudclient: update to 5.1.0 tornaria
2023-11-02 21:07 ` [PR PATCH] [Updated] " tornaria
2023-11-03 1:52 ` tornaria
2023-11-03 15:08 ` tornaria
2023-11-03 16:19 ` tornaria
2023-11-10 12:08 ` [PR PATCH] [Updated] " tornaria
2023-11-10 23:52 ` [PR PATCH] [Updated] owncloudclient: update to 5.1.1 tornaria
2023-11-11 3:58 ` tornaria
2023-12-01 12:51 ` [PR PATCH] [Updated] owncloudclient: update to 5.1.2 tornaria
2023-12-01 12:52 ` tornaria
2023-12-22 17:49 ` [PR PATCH] [Updated] owncloudclient: update to 5.2.0 tornaria
2024-01-04 13:50 ` tornaria
2024-01-31 19:31 ` [PR PATCH] [Updated] owncloudclient: update to 5.2.1 tornaria
2024-01-31 22:26 ` tornaria
2024-01-31 22:28 ` tornaria
2024-02-02 17:58 ` [PR PATCH] [Updated] " tornaria
2024-03-26 13:49 ` tornaria
2024-04-03 13:10 ` [PR REVIEW] " ahesford
2024-04-03 13:10 ` ahesford
2024-04-03 22:54 ` [PR PATCH] [Updated] " tornaria
2024-04-03 23:03 ` tornaria [this message]
2024-04-05 11:23 ` [PR PATCH] [Merged]: " ahesford
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=20240403230357.48B0320E02@inbox.vuxu.org \
--to=tornaria@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).