From: chexum <chexum@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [PR PATCH] [Closed]: New package: libteam 1.31.git20210222
Date: Fri, 06 May 2022 15:57:38 +0200 [thread overview]
Message-ID: <20220506135738.BxRd17vzsdPLfPwJiAtyRJlkcETFWsUCvzXUcIEA_-4@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-33028@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 1986 bytes --]
There's a closed pull request on the void-packages repository
New package: libteam 1.31.git20210222
https://github.com/void-linux/void-packages/pull/33028
Description:
<!-- Mark items with [x] where applicable -->
libteam, the user-space counterpart of the ethernet teaming/bonding device is the modern tool to provide link aggregation for ethernet devices. Unfortunately, the most recent proper release misses a few important fixes, so I opted to use the git version instead of providing the patches from github.
It also has some incompatibility with musl, TIPC is always enabled, but it uses a header, sys/queue.h which does not seem to be provided by musl, so I disabled all musl platforms for the time being.
#### General
- [x] This is a new package and it conforms to the [quality requirements](https://github.com/void-linux/void-packages/blob/master/Manual.md#quality-requirements)
#### Have the results of the proposed changes been tested?
- [x] I use the packages affected by the proposed changes on a regular basis and confirm this PR works for me
- [ ] I generally don't use the affected packages but briefly tested this PR
<!--
If GitHub CI cannot be used to validate the build result (for example, if the
build is likely to take several hours), make sure to
[skip CI](https://github.com/void-linux/void-packages/blob/master/CONTRIBUTING.md#continuous-integration).
When skipping CI, uncomment and fill out the following section.
Note: for builds that are likely to complete in less than 2 hours, it is not
acceptable to skip CI.
-->
<!--
#### Does it build and run successfully?
(Please choose at least one native build and, if supported, at least one cross build. More are better.)
- [x] I built this PR locally for my native architecture, (x86-64-glibc)
- [x] I built this PR locally for these architectures (if supported. mark crossbuilds):
- [x] aarch64-glibc
- [ ] aarch64-musl
- [x] armv7l-glibc
- [ ] armv6l-musl
-->
prev parent reply other threads:[~2022-05-06 13:57 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-09-19 16:55 [PR PATCH] " chexum
2021-09-20 0:57 ` ericonr
2021-09-20 0:57 ` [PR REVIEW] " ericonr
2021-09-20 0:58 ` ericonr
2021-09-20 15:46 ` chexum
2021-09-20 17:29 ` ericonr
2022-05-06 13:57 ` chexum [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=20220506135738.BxRd17vzsdPLfPwJiAtyRJlkcETFWsUCvzXUcIEA_-4@z \
--to=chexum@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).