guix-patches
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[bug#40081] [PATCH] gnu: bluez: Update to 5.54.


From: Marius Bakke
Subject: [bug#40081] [PATCH] gnu: bluez: Update to 5.54.
Date: Mon, 16 Mar 2020 00:45:36 +0100
User-agent: Notmuch/0.29.3 (https://notmuchmail.org) Emacs/26.3 (x86_64-pc-linux-gnu)

Leo Famulari <address@hidden> writes:

> On Sun, Mar 15, 2020 at 07:11:35PM +0100, Vincent Legoll wrote:
>> From a84f040fd88b02b556a0fbd207f8edce1a940924 Mon Sep 17 00:00:00 2001
>> From: Vincent Legoll <address@hidden>
>> Date: Sun, 15 Mar 2020 19:07:57 +0100
>> Subject: [PATCH] gnu: bluez: Update to 5.54.
>> 
>> * gnu/packages/linux.scm (bluez) : Update to 5.54.
>> (bluez/fixed): remove variable.
>> * gnu/packages/patches/bluez-CVE-2020-0556.patch: Remove file
>
> Thanks!
>
> I also removed the patch from 'gnu/local.mk' and made some small edits
> to the commit message.
>
> Pushed as f24aaa81de8c709adfda2e89271c562a5ca8d959

BlueZ causes 1000+ rebuilds according to 'guix refresh -l bluez'.
Berlin already failed to build pulseaudio on armhf, leaving ARM users
without substitutes until someone is able to restart all the builds:

https://ci.guix.gnu.org/eval/11627?status=failed
https://ci.guix.gnu.org/build/2390393/details

Should we revert it, or turn it into a graft?

Attachment: signature.asc
Description: PGP signature


reply via email to

[Prev in Thread] Current Thread [Next in Thread]