Github messages for voidlinux
 help / color / mirror / Atom feed
From: unspecd <unspecd@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: [PR PATCH] bluez: update to 5.63.
Date: Wed, 12 Jan 2022 18:40:10 +0100	[thread overview]
Message-ID: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-35014@inbox.vuxu.org> (raw)

[-- Attachment #1: Type: text/plain, Size: 1174 bytes --]

There is a new pull request by unspecd against master on the void-packages repository

https://github.com/unspecd/void-packages pkg/bluez
https://github.com/void-linux/void-packages/pull/35014

bluez: update to 5.63.
<!-- Uncomment relevant sections and delete options which are not applicable -->

#### Testing the changes
- I tested the changes in this PR: **briefly**

<!--
#### 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, (x86_64-musl)
- I built this PR locally for these architectures (if supported. mark crossbuilds):
  - ppc64le-musl


A patch file from https://github.com/void-linux/void-packages/pull/35014.patch is attached

[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: github-pr-pkg/bluez-35014.patch --]
[-- Type: text/x-diff, Size: 1811 bytes --]

From f62197b4a88009faea455aece9b89b671ff6621b Mon Sep 17 00:00:00 2001
From: Evgeny Ermakov <evgeny.v.ermakov@gmail.com>
Date: Thu, 13 Jan 2022 04:19:10 +1100
Subject: [PATCH] bluez: update to 5.63.

---
 .../0009-include-limits.h-for-musl-build.patch        | 11 +++++++++++
 srcpkgs/bluez/template                                |  4 ++--
 2 files changed, 13 insertions(+), 2 deletions(-)
 create mode 100644 srcpkgs/bluez/patches/0009-include-limits.h-for-musl-build.patch

diff --git a/srcpkgs/bluez/patches/0009-include-limits.h-for-musl-build.patch b/srcpkgs/bluez/patches/0009-include-limits.h-for-musl-build.patch
new file mode 100644
index 000000000000..c6627b90ac8d
--- /dev/null
+++ b/srcpkgs/bluez/patches/0009-include-limits.h-for-musl-build.patch
@@ -0,0 +1,11 @@
+--- a/tools/mesh-cfgtest.c
++++ b/tools/mesh-cfgtest.c
+@@ -34,6 +34,8 @@
+ #include "mesh/mesh-defs.h"
+ #include "mesh/mesh.h"
+ 
++#include <limits.h>
++
+ #define MAX_CRPL_SIZE	0x7fff
+ #define CFG_SRV_MODEL	0x0000
+ #define CFG_CLI_MODEL	0x0001
diff --git a/srcpkgs/bluez/template b/srcpkgs/bluez/template
index f6788a81ec46..8c89a244586b 100644
--- a/srcpkgs/bluez/template
+++ b/srcpkgs/bluez/template
@@ -1,6 +1,6 @@
 # Template file for 'bluez'
 pkgname=bluez
-version=5.62
+version=5.63
 revision=2
 build_style=gnu-configure
 configure_args="--with-udevdir=/usr/lib/udev --disable-systemd
@@ -15,7 +15,7 @@ maintainer="Érico Nogueira <ericonr@disroot.org>"
 license="GPL-2.0-or-later, LGPL-2.1-or-later"
 homepage="http://www.bluez.org/"
 distfiles="${KERNEL_SITE}/bluetooth/$pkgname-$version.tar.xz"
-checksum=38090a5b750e17fc08d3e52178ed8d3254c5f4bd2c48830d5c1955b88e3bc0c2
+checksum=9349e11e8160bb3d720835d271250d8a7424d3690f5289e6db6fe07cc66c6d76
 conf_files="/etc/bluetooth/main.conf"
 system_groups="bluetooth"
 

             reply	other threads:[~2022-01-12 17:40 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-01-12 17:40 unspecd [this message]
2022-01-12 17:44 ` [PR PATCH] [Updated] " unspecd
2022-01-17  8:40 ` [PR PATCH] [Merged]: " ericonr

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=gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-35014@inbox.vuxu.org \
    --to=unspecd@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).