From: github-actions[bot] <github-actions[bot]@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [PR PATCH] [Closed]: New packages: fl{aa,amp,cluster,log,msg,net,wkey,wrap}
Date: Thu, 13 Apr 2023 03:50:52 +0200 [thread overview]
Message-ID: <20230413015052.ctcEBAJbpOWSIM71fihs8b_inZPk_kRcoreU0Pd71yo@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-38816@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 957 bytes --]
There's a closed pull request on the void-packages repository
New packages: fl{aa,amp,cluster,log,msg,net,wkey,wrap}
https://github.com/void-linux/void-packages/pull/38816
Description:
/label new-package wip
@classabbyamp (https://github.com/void-linux/void-packages/pull/38771#issuecomment-1221202322)
I need help with:
1. ~~picking a good name for the meta-package (`fldigi-full` was a wild guess),~~
2. ~~`fl{amp,cluster,msg}` failing to set `USE_X` (I left a writeup in the `flamp` template), and~~
3. the applications that _do_ build presenting an all-black theme: black font on black background. Just my machine (running sway), or something wrong with the way I built the programs?
#### Testing the changes
- I tested the changes in this PR: **briefly**
#### New package
- This new package conforms to the [package requirements](https://github.com/void-linux/void-packages/blob/master/CONTRIBUTING.md#package-requirements): **YES**
prev parent reply other threads:[~2023-04-13 1:50 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-21 19:29 [PR PATCH] New packages: fl{aa,amp,cluster,log,msg,net,wkey,wrap,digi-full} Goorzhel
2022-08-21 19:34 ` classabbyamp
2022-08-21 20:28 ` [PR PATCH] [Updated] " Goorzhel
2022-08-21 20:43 ` New packages: fl{aa,amp,cluster,log,msg,net,wkey,wrap} Goorzhel
2022-08-21 20:44 ` Goorzhel
2022-08-21 22:49 ` classabbyamp
2022-08-21 22:53 ` classabbyamp
2022-09-07 6:43 ` Goorzhel
2022-09-07 6:43 ` Goorzhel
2022-09-07 6:45 ` classabbyamp
2022-09-07 6:47 ` Goorzhel
2022-09-07 6:48 ` Goorzhel
2022-09-07 6:49 ` Goorzhel
2022-09-22 5:02 ` [PR PATCH] [Updated] " Goorzhel
2022-09-22 5:02 ` Goorzhel
2022-09-22 5:32 ` Goorzhel
2022-09-23 6:00 ` Goorzhel
2022-09-25 3:08 ` Goorzhel
2022-12-25 1:58 ` github-actions
2022-12-27 19:17 ` [PR PATCH] [Closed]: " Goorzhel
2022-12-27 19:46 ` Goorzhel
2022-12-27 21:10 ` Goorzhel
2022-12-27 21:14 ` Goorzhel
2023-03-29 1:59 ` github-actions
2023-04-13 1:50 ` github-actions [this message]
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=20230413015052.ctcEBAJbpOWSIM71fihs8b_inZPk_kRcoreU0Pd71yo@z \
--to=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).