From: chilledfrogs <chilledfrogs@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: New package: litterbox-1.6
Date: Tue, 08 Dec 2020 12:51:56 +0100 [thread overview]
Message-ID: <20201208115156.GX14tS9K3knY7hCzF6JgBrPOr33PoZRcyWlo930xFYk@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-25785@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 689 bytes --]
New comment by chilledfrogs on void-packages repository
https://github.com/void-linux/void-packages/pull/25785#issuecomment-740573880
Comment:
@ericonr Thanks for merging this, but I have a very, very stupid question: I wanted this package mainly for my Raspberry Pi, so aarch64, yet it still is indicated as not in the repos for there, but for x86_64 it is, and honestly I can't figure out for the life of me how to navigate the build bot interface to determine what happened... So essentially, did I forget to do something so that it's packaged for all arches (since it should honestly be compatible to my knowledge), or is something hanging on the buildbot's side, or something else?
next prev parent reply other threads:[~2020-12-08 11:51 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-22 10:01 [PR PATCH] " chilledfrogs
2020-10-22 10:35 ` chilledfrogs
2020-10-22 10:35 ` chilledfrogs
2020-10-22 12:40 ` [PR REVIEW] " PaperMountainStudio
2020-10-22 12:40 ` PaperMountainStudio
2020-10-22 14:28 ` [PR PATCH] [Updated] " chilledfrogs
2020-10-22 14:29 ` [PR REVIEW] " chilledfrogs
2020-10-22 14:30 ` chilledfrogs
2020-10-22 14:30 ` chilledfrogs
2020-10-22 14:30 ` [PR PATCH] [Updated] " chilledfrogs
2020-10-22 14:38 ` [PR REVIEW] " chilledfrogs
2020-10-22 23:22 ` [PR PATCH] [Updated] " chilledfrogs
2020-10-25 0:00 ` [PR REVIEW] " chilledfrogs
2020-11-02 22:27 ` chilledfrogs
2020-11-02 23:05 ` [PR REVIEW] " PaperMountainStudio
2020-11-04 11:30 ` chilledfrogs
2020-11-04 11:32 ` [PR PATCH] [Updated] " chilledfrogs
2020-11-09 1:04 ` [PR REVIEW] " sgn
2020-11-09 14:33 ` chilledfrogs
2020-11-11 11:22 ` sgn
2020-11-11 21:56 ` [PR PATCH] [Updated] " chilledfrogs
2020-11-11 21:57 ` chilledfrogs
2020-11-11 21:58 ` [PR REVIEW] " chilledfrogs
2020-11-12 18:14 ` chilledfrogs
2020-12-04 17:24 ` [PR PATCH] [Updated] " chilledfrogs
2020-12-04 17:24 ` chilledfrogs
2020-12-04 18:33 ` paper42
2020-12-04 18:54 ` ericonr
2020-12-04 18:55 ` [PR PATCH] [Merged]: " ericonr
2020-12-08 11:51 ` chilledfrogs [this message]
2020-12-08 14:22 ` ericonr
2020-12-08 17:30 ` chilledfrogs
2020-12-08 17:31 ` chilledfrogs
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=20201208115156.GX14tS9K3knY7hCzF6JgBrPOr33PoZRcyWlo930xFYk@z \
--to=chilledfrogs@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).