From: DragonGhost7 <DragonGhost7@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [PR REVIEW] etesync-dav: update to 0.32.1
Date: Thu, 13 Oct 2022 23:00:51 +0200 [thread overview]
Message-ID: <20221013210051.Pa1Y7BEj9gowM4Q4pFpdmQ_fAkhBDHuBjvR39cF14co@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-39818@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 584 bytes --]
New review comment by DragonGhost7 on void-packages repository
https://github.com/void-linux/void-packages/pull/39818#discussion_r995118732
Comment:
I marked etesync-dav as x86_64 only because python3-etebase was marked x86_64 only, and since it's a depends I though no point in building it for more arches if it can't be used on them, but It seems I don't seem to remember why I wrote python3-etebase as x86_64 only, since pypi page does contain already built packages for different architectures. I'll change it and run builds, and see what happens, no reason for it not to work.
next prev parent reply other threads:[~2022-10-13 21:00 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-08 20:44 [PR PATCH] " DragonGhost7
2022-10-08 20:55 ` [PR PATCH] [Updated] " DragonGhost7
2022-10-08 21:02 ` DragonGhost7
2022-10-11 5:04 ` [PR REVIEW] " classabbyamp
2022-10-11 5:06 ` classabbyamp
2022-10-11 5:09 ` classabbyamp
2022-10-11 14:38 ` [PR PATCH] [Updated] " DragonGhost7
2022-10-11 17:16 ` [PR PATCH] [Merged]: " classabbyamp
2022-10-13 20:19 ` [PR REVIEW] " ahesford
2022-10-13 20:35 ` classabbyamp
2022-10-13 20:35 ` classabbyamp
2022-10-13 20:39 ` ahesford
2022-10-13 21:00 ` DragonGhost7 [this message]
2022-10-16 14:30 ` paper42
2022-10-16 14:30 ` paper42
2022-10-16 14:30 ` paper42
2022-10-16 14:30 ` paper42
2022-10-16 14:30 ` paper42
2022-10-16 14:30 ` paper42
2022-10-16 14:30 ` paper42
2022-10-16 14:30 ` paper42
2022-10-16 14:30 ` paper42
2022-10-16 14:30 ` paper42
2022-10-16 18:35 ` DragonGhost7
2022-10-19 13:48 ` ahesford
2022-10-19 13:51 ` ahesford
2022-10-19 14:14 ` DragonGhost7
2022-10-19 14:21 ` ahesford
2022-10-19 14:25 ` DragonGhost7
2022-10-19 14:27 ` DragonGhost7
2022-10-19 14:32 ` 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=20221013210051.Pa1Y7BEj9gowM4Q4pFpdmQ_fAkhBDHuBjvR39cF14co@z \
--to=dragonghost7@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).