From: Marius Bakke <mbakke@fastmail.com>
To: Leo Famulari <leo@famulari.name>,
Vincent Legoll <vincent.legoll@gmail.com>
Cc: 40081-done@debbugs.gnu.org
Subject: [bug#40081] [PATCH] gnu: bluez: Update to 5.54.
Date: Mon, 16 Mar 2020 00:45:36 +0100 [thread overview]
Message-ID: <87k13lkwrj.fsf@devup.no> (raw)
In-Reply-To: <20200315182607.GD5561@jasmine.lan>
[-- Attachment #1: Type: text/plain, Size: 1023 bytes --]
Leo Famulari <leo@famulari.name> 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 <vincent.legoll@gmail.com>
>> 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 #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 487 bytes --]
next prev parent reply other threads:[~2020-03-15 23:46 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-15 18:11 [bug#40081] [PATCH] gnu: bluez: Update to 5.54 Vincent Legoll
2020-03-15 18:13 ` Vincent Legoll
2020-03-15 18:24 ` Leo Famulari
2020-03-15 18:26 ` bug#40081: " Leo Famulari
2020-03-15 23:45 ` Marius Bakke [this message]
2020-03-16 1:04 ` [bug#40081] " Leo Famulari
2020-03-16 1:07 ` Leo Famulari
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
List information: https://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87k13lkwrj.fsf@devup.no \
--to=mbakke@fastmail.com \
--cc=40081-done@debbugs.gnu.org \
--cc=leo@famulari.name \
--cc=vincent.legoll@gmail.com \
/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.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/guix.git
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 read-only IMAP folder(s) and NNTP newsgroup(s).