From: leahneukirchen <leahneukirchen@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [PR PATCH] [Merged]: i2c-tools: change upstream and add python subpkg
Date: Mon, 13 Jun 2022 10:27:13 +0200 [thread overview]
Message-ID: <20220613082713.k4bg2sEeNOPMo0128hJIKmeFzDFG_toyPAo6-IcNjkY@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-36304@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 1452 bytes --]
There's a merged pull request on the void-packages repository
i2c-tools: change upstream and add python subpkg
https://github.com/void-linux/void-packages/pull/36304
Description:
~~Things I am still unsure about:~~
- ~~The subpackage name and short_desc~~
- ~~How to ensure the subpackage's version is the version of the python module (it is versioned separately)~~
Closes #36156
#### Testing the changes
- I tested the changes in this PR: **briefly**
- [x] Distfile location change had no impact (same exact file as debian's)
- [x] Package builds fine and with the right files in the right place
- [x] Crossbuilds fine
- [x] Tested the python bindings
@leahneukirchen
<!--
#### New package
- This new package conforms to the [quality requirements](https://github.com/void-linux/void-packages/blob/master/Manual.md#quality-requirements): **YES**|**NO**
-->
<!-- Note: If the build is likely to take more than 2 hours, please [skip CI](https://github.com/void-linux/void-packages/blob/master/CONTRIBUTING.md#continuous-integration)
and test at least one native build and, if supported, at least one cross build.
Ignore this section if this PR is not skipping CI.
-->
<!--
#### Local build testing
- I built this PR locally for my native architecture, (ARCH-LIBC)
- I built this PR locally for these architectures (if supported. mark crossbuilds):
- aarch64-musl
- armv7l
- armv6l-musl
-->
prev parent reply other threads:[~2022-06-13 8:27 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-23 21:23 [PR PATCH] " 0x5c
2022-03-23 21:44 ` leahneukirchen
2022-03-29 11:11 ` [PR PATCH] [Updated] " 0x5c
2022-03-29 11:16 ` 0x5c
2022-05-07 9:11 ` [PR PATCH] [Updated] " 0x5c
2022-05-07 9:26 ` 0x5c
2022-05-07 22:55 ` [PR PATCH] [Updated] " 0x5c
2022-05-22 19:33 ` [PR REVIEW] " classabbyamp
2022-05-22 19:34 ` classabbyamp
2022-05-23 4:52 ` [PR PATCH] [Updated] " 0x5c
2022-05-23 4:57 ` [PR REVIEW] " 0x5c
2022-05-23 4:59 ` 0x5c
2022-05-23 4:59 ` 0x5c
2022-05-27 22:54 ` [PR PATCH] [Updated] " 0x5c
2022-05-27 23:05 ` 0x5c
2022-05-27 23:22 ` 0x5c
2022-06-12 1:14 ` 0x5c
2022-06-12 1:19 ` 0x5c
2022-06-13 8:27 ` leahneukirchen [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=20220613082713.k4bg2sEeNOPMo0128hJIKmeFzDFG_toyPAo6-IcNjkY@z \
--to=leahneukirchen@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).