From: github-actions[bot] <github-actions[bot]@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [PR PATCH] [Closed]: New package: yabridgectl-4.0.2
Date: Sun, 15 Jan 2023 03:00:19 +0100 [thread overview]
Message-ID: <20230115020019.IQ8KJnabMLbPA_m-8ncC2h1pYYEbu8xD6em4-kkfrQ0@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-39476@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 871 bytes --]
There's a closed pull request on the void-packages repository
New package: yabridgectl-4.0.2
https://github.com/void-linux/void-packages/pull/39476
Description:
<!-- Uncomment relevant sections and delete options which are not applicable -->
#### Testing the changes
- I tested the changes in this PR: **YES**
#### New package
- This new package conforms to the [package requirements](https://github.com/void-linux/void-packages/blob/master/CONTRIBUTING.md#package-requirements):
-
xlint check complains about the wrksrc not being top level. The source of yabridgectl is distributed within the yabridge source and is several levels down. Compiles and works well by keeping the origin source in the correct locations and having the multilevel wrksrc set.
#### Local build testing
- I built this PR locally for my native architecture, (ARCH-LIBC)
prev parent reply other threads:[~2023-01-15 2:00 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-26 8:17 [PR PATCH] " ajtcode71
2022-09-26 8:39 ` paper42
2022-09-26 8:40 ` [PR REVIEW] " paper42
2022-09-26 10:22 ` [PR PATCH] [Updated] " ajtcode71
2022-09-26 11:08 ` [PR REVIEW] " paper42
2022-09-26 11:10 ` paper42
2022-09-26 23:38 ` [PR PATCH] [Updated] " ajtcode71
2022-09-26 23:45 ` ajtcode71
2022-09-27 0:35 ` [PR REVIEW] " paper42
2022-10-01 8:10 ` [PR PATCH] [Updated] " ajtcode71
2022-10-01 8:16 ` ajtcode71
2022-10-01 8:19 ` ajtcode71
2022-10-01 8:25 ` ajtcode71
2022-10-01 10:57 ` [PR REVIEW] " paper42
2022-12-31 1:55 ` github-actions
2023-01-15 2:00 ` 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=20230115020019.IQ8KJnabMLbPA_m-8ncC2h1pYYEbu8xD6em4-kkfrQ0@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).