From: PoroCYon <PoroCYon@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: [PR PATCH] bluez: update to 5.65
Date: Wed, 24 Aug 2022 19:33:29 +0200 [thread overview]
Message-ID: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-38891@inbox.vuxu.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 766 bytes --]
There is a new pull request by PoroCYon against master on the void-packages repository
https://github.com/PoroCYon/void-packages bluez-5.65
https://github.com/void-linux/void-packages/pull/38891
bluez: update to 5.65
#### Testing the changes
- I tested the changes in this PR: **YES**
- I checked that it fixes a bug present in 5.64 that affects my [Mooltipass](https://www.themooltipass.com/)
#### Local build testing
- I built this PR locally for my native architecture, (x86_64-glibc)
- I built this PR locally for these architectures (if supported. mark crossbuilds):
- aarch64 (cross)
- aarch64-musl (cross)
- armv7l (cross)
- armv6l-musl (cross)
A patch file from https://github.com/void-linux/void-packages/pull/38891.patch is attached
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: github-pr-bluez-5.65-38891.patch --]
[-- Type: text/x-diff, Size: 1043 bytes --]
From 9e746a02d3073d3275fa99da3e0f25031aceb087 Mon Sep 17 00:00:00 2001
From: PoroCYon <p@pcy.be>
Date: Wed, 24 Aug 2022 18:54:03 +0200
Subject: [PATCH] bluez: update to 5.65
---
srcpkgs/bluez/template | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/srcpkgs/bluez/template b/srcpkgs/bluez/template
index e9827e8e1d95..fa05de5091fa 100644
--- a/srcpkgs/bluez/template
+++ b/srcpkgs/bluez/template
@@ -1,6 +1,6 @@
# Template file for 'bluez'
pkgname=bluez
-version=5.64
+version=5.65
revision=1
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=ae437e65b6b3070c198bc5b0109fe9cdeb9eaa387380e2072f9de65fe8a1de34
+checksum=2565a4d48354b576e6ad92e25b54ed66808296581c8abb80587051f9993d96d4
conf_files="/etc/bluetooth/main.conf"
system_groups="bluetooth"
next reply other threads:[~2022-08-24 17:33 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-24 17:33 PoroCYon [this message]
2022-08-24 21:10 ` paper42
2022-08-24 22:43 ` PoroCYon
2022-08-24 22:54 ` PoroCYon
2022-08-26 4:02 ` [PR PATCH] [Closed]: " sgn
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-38891@inbox.vuxu.org \
--to=porocyon@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).