From: ericonr <ericonr@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [PR PATCH] [Merged]: pipewire: update to 0.3.25
Date: Fri, 09 Apr 2021 17:05:01 +0200 [thread overview]
Message-ID: <20210409150501.nIacs_B26Y2Z9V6-nMlAoDZlYw_gZOaIMEH1E4etK88@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-30046@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 1747 bytes --]
There's a merged pull request on the void-packages repository
pipewire: update to 0.3.25
https://github.com/void-linux/void-packages/pull/30046
Description:
* activate bluetooth support only when the bluetooth plugin is installed
* fix README.voidlinux going in pipewire-doc
* disable SDL2 dep, only used in some examples we don't even ship
* rm INSTALL.msg, configs should be stable now (also mark them in xbps)
* ncursesw.patch is now upstream
Fix #29655
<!-- Mark items with [x] where applicable -->
#### General
- [ ] 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.)
- [ ] 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:[~2021-04-09 15:05 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-06 15:52 [PR PATCH] " st3r4g
2021-04-06 15:57 ` [PR PATCH] [Updated] " st3r4g
2021-04-06 16:03 ` st3r4g
2021-04-06 16:07 ` st3r4g
2021-04-06 16:14 ` st3r4g
2021-04-06 16:18 ` [PR PATCH] [Updated] " st3r4g
2021-04-06 16:18 ` st3r4g
2021-04-06 16:50 ` st3r4g
2021-04-06 17:19 ` [PR REVIEW] " ericonr
2021-04-06 17:47 ` st3r4g
2021-04-07 18:10 ` ericonr
2021-04-08 8:46 ` [PR PATCH] [Updated] " st3r4g
2021-04-08 8:57 ` st3r4g
2021-04-08 23:12 ` [PR REVIEW] " st3r4g
2021-04-09 10:26 ` [PR PATCH] [Updated] [nomerge] " st3r4g
2021-04-09 10:28 ` [PR REVIEW] " st3r4g
2021-04-09 15:05 ` ericonr [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=20210409150501.nIacs_B26Y2Z9V6-nMlAoDZlYw_gZOaIMEH1E4etK88@z \
--to=ericonr@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).