GNU bug report logs -
#74597
[PATCH] gnu: bluez: Update to 5.79.
Previous Next
Reported by: Julian Flake <flake <at> uni-koblenz.de>
Date: Thu, 28 Nov 2024 21:13:01 UTC
Severity: normal
Tags: patch
Done: Leo Famulari <leo <at> famulari.name>
Bug is archived. No further changes may be made.
Full log
View this message in rfc822 format
[Message part 1 (text/plain, inline)]
Your message dated Tue, 20 May 2025 20:45:02 -0400
with message-id <aC0iDqEs47r7eg-T <at> jasmine.lan>
and subject line Re: [bug#76311] Request for merging "kernel-team" branch
has caused the debbugs.gnu.org bug report #74597,
regarding [PATCH] gnu: bluez: Update to 5.79.
to be marked as done.
(If you believe you have received this mail in error, please contact
help-debbugs <at> gnu.org.)
--
74597: https://debbugs.gnu.org/cgi/bugreport.cgi?bug=74597
GNU Bug Tracking System
Contact help-debbugs <at> gnu.org with problems
[Message part 2 (message/rfc822, inline)]
* gnu/packages/linux.scm (bluez): Update to 5.79.
Change-Id: I5928664f929d1bda6e8c8c5e37cb9020a9889881
---
gnu/packages/linux.scm | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/gnu/packages/linux.scm b/gnu/packages/linux.scm
index f7e7126c3d..a7c2678540 100644
--- a/gnu/packages/linux.scm
+++ b/gnu/packages/linux.scm
@@ -6203,7 +6203,7 @@ (define-public sbc
(define-public bluez
(package
(name "bluez")
- (version "5.72")
+ (version "5.79")
(source (origin
(method url-fetch)
(uri (string-append
@@ -6211,7 +6211,7 @@ (define-public bluez
version ".tar.xz"))
(sha256
(base32
- "0vjk4ihywzv8k07bxq7clqgi2afrw54nfp0gcnxw35m98nipz7a9"))))
+ "12pal1m4xlr8k7kxb6isv5lbaca2wc5zcgy0907wfwcz78qaar21"))))
(build-system gnu-build-system)
(arguments
(list
base-commit: 294386674c417355a24586fab5528c643d495b86
--
2.46.0
[Message part 3 (message/rfc822, inline)]
On Sat, May 17, 2025 at 09:06:29AM +0200, Julian Flake wrote:
> Thanks for merging this already into master. Everything that worked before,
> still works, but my issue remains. However, the error message seems to have
> changed (now it's "Connection Failed: Operation already in progress bluez").
That's too bad. Unfortunatley I don't use Bluetooth on Linux so I don't
know how to help.
> Since this issue's original subject was to update bluez to 5.79 , it can be
> closed now? Or should we leave it open, until my (and others') issue is
> resolved?
Yes, since this ticket was about updating the package, we can close it.
This bug report was last modified today.
Previous Next
GNU bug tracking system
Copyright (C) 1999 Darren O. Benham,
1997,2003 nCipher Corporation Ltd,
1994-97 Ian Jackson.