From: RandallFlagg <RandallFlagg@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [PR REVIEW] New package: goldendict-ng-24.05.05
Date: Thu, 11 Jul 2024 13:01:18 +0200 [thread overview]
Message-ID: <20240711110118.98324229FE@inbox.vuxu.org> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-51071@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 670 bytes --]
New review comment by RandallFlagg on void-packages repository
https://github.com/void-linux/void-packages/pull/51071#discussion_r1673664663
Comment:
I ran the following command after running the bootstrap which is similar to what I did for MUSL:
`./xbps-src -A aarch64 pkg goldendict-ng`
The bootstrap command ended with the same error.
What should I do different? Can you point me to the right documentation?
I am looking currentlly at this documents:
https://github.com/void-linux/void-packages/blob/master/Manual.md
https://github.com/void-linux/void-packages?tab=readme-ov-file
https://github.com/void-linux/void-packages/blob/master/CONTRIBUTING.md
next prev parent reply other threads:[~2024-07-11 11:01 UTC|newest]
Thread overview: 76+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-02 1:04 [PR PATCH] Inital commit for goldendict-ng RandallFlagg
2024-07-02 1:07 ` abenson
2024-07-02 1:11 ` [PR REVIEW] " classabbyamp
2024-07-02 1:11 ` classabbyamp
2024-07-02 1:11 ` classabbyamp
2024-07-02 11:07 ` [PR PATCH] [Updated] " RandallFlagg
2024-07-02 15:11 ` [PR PATCH] [Updated] New package: goldendict-ng-LiXia.240505 RandallFlagg
2024-07-02 23:53 ` RandallFlagg
2024-07-03 12:06 ` RandallFlagg
2024-07-04 8:37 ` New package: goldendict-ng-24.05.05 RandallFlagg
2024-07-04 9:15 ` [PR PATCH] [Updated] " RandallFlagg
2024-07-04 22:15 ` RandallFlagg
2024-07-04 22:56 ` [PR PATCH] [Updated] " RandallFlagg
2024-07-04 23:03 ` classabbyamp
2024-07-04 23:50 ` [PR PATCH] [Updated] " RandallFlagg
2024-07-05 0:13 ` [PR REVIEW] " classabbyamp
2024-07-05 0:13 ` classabbyamp
2024-07-05 0:13 ` classabbyamp
2024-07-05 14:27 ` RandallFlagg
2024-07-05 14:27 ` RandallFlagg
2024-07-05 14:28 ` [PR PATCH] [Updated] " RandallFlagg
2024-07-05 16:14 ` [PR REVIEW] " classabbyamp
2024-07-05 16:16 ` classabbyamp
2024-07-05 16:16 ` classabbyamp
2024-07-10 14:44 ` RandallFlagg
2024-07-10 14:49 ` RandallFlagg
2024-07-10 14:50 ` classabbyamp
2024-07-10 14:56 ` [PR PATCH] [Updated] " RandallFlagg
2024-07-10 18:38 ` RandallFlagg
2024-07-10 18:39 ` [PR REVIEW] " RandallFlagg
2024-07-10 18:44 ` classabbyamp
2024-07-11 9:00 ` RandallFlagg
2024-07-11 11:01 ` RandallFlagg [this message]
2024-07-11 12:27 ` classabbyamp
2024-07-12 10:37 ` RandallFlagg
2024-07-12 10:41 ` RandallFlagg
2024-07-12 13:56 ` classabbyamp
2024-07-13 19:51 ` RandallFlagg
2024-07-13 19:52 ` RandallFlagg
2024-07-13 20:02 ` classabbyamp
2024-07-13 22:21 ` RandallFlagg
2024-07-13 22:25 ` shenlebantongying
2024-07-13 22:39 ` RandallFlagg
2024-07-13 22:40 ` RandallFlagg
2024-07-13 22:47 ` shenlebantongying
2024-07-13 23:24 ` shenlebantongying
2024-07-13 23:29 ` shenlebantongying
2024-07-13 23:39 ` classabbyamp
2024-07-13 23:40 ` classabbyamp
2024-07-13 23:45 ` RandallFlagg
2024-07-13 23:56 ` shenlebantongying
2024-07-13 23:59 ` [PR PATCH] [Updated] " RandallFlagg
2024-07-14 0:41 ` [PR REVIEW] " classabbyamp
2024-07-25 10:35 ` slymattz
2024-07-28 11:54 ` [PR REVIEW] " mvf
2024-07-28 11:54 ` mvf
2024-07-28 14:03 ` classabbyamp
2024-07-28 14:34 ` slymattz
2024-07-28 14:39 ` slymattz
2024-07-28 14:49 ` mvf
2024-07-28 14:53 ` mvf
2024-07-28 14:58 ` slymattz
2024-07-28 15:00 ` slymattz
2024-07-28 15:03 ` classabbyamp
2024-07-28 16:34 ` mvf
2024-07-28 16:35 ` mvf
2024-07-28 18:32 ` slymattz
2024-07-29 5:38 ` mvf
2024-07-29 10:10 ` slymattz
2024-07-29 13:43 ` classabbyamp
2024-07-29 14:44 ` slymattz
2024-07-29 14:51 ` slymattz
2024-07-29 14:55 ` slymattz
2024-08-01 13:24 ` slymattz
2024-08-02 17:49 ` slymattz
2024-08-05 14:01 ` slymattz
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=20240711110118.98324229FE@inbox.vuxu.org \
--to=randallflagg@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).