[PATCH 07/11] gnu: gnome-bluetooth: Update to 3.20.1.

  • Done
  • quality assurance status badge
Details
One participant
  • Kei Kebreau
Owner
unassigned
Submitted by
Kei Kebreau
Severity
normal

Debbugs page

Kei Kebreau wrote 8 years ago
(address . guix-patches@gnu.org)
20170511153021.14972-7-kei@openmailbox.org
* gnu/packages/gnome.scm (gnome-bluetooth): Update to 3.20.1.
---
gnu/packages/gnome.scm | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)

Toggle diff (24 lines)
diff --git a/gnu/packages/gnome.scm b/gnu/packages/gnome.scm
index 4a0274735..17fb6b063 100644
--- a/gnu/packages/gnome.scm
+++ b/gnu/packages/gnome.scm
@@ -4876,7 +4876,7 @@ usage and information about running processes.")
(define-public gnome-bluetooth
(package
(name "gnome-bluetooth")
- (version "3.20.0")
+ (version "3.20.1")
(source (origin
(method url-fetch)
(uri (string-append "mirror://gnome/sources/" name "/"
@@ -4884,7 +4884,7 @@ usage and information about running processes.")
name "-" version ".tar.xz"))
(sha256
(base32
- "0lzbwk2kn7kp39sv5bf4ja92mfkxkc27gxxk8k86i8a8ncbcmcwk"))))
+ "1zlqcz6jz4vzzr8gd1678i9s4015kiwcpr5szrwz4kmryfsm147a"))))
(build-system glib-or-gtk-build-system)
(native-inputs
`(("glib:bin" ,glib "bin") ; for gdbus-codegen, etc.
--
2.13.0
Kei Kebreau wrote 8 years ago
Re: bug#26887: [PATCH 01/11] gnu: libdrm: Update to 2.4.80.
(name . Marius Bakke)(address . mbakke@fastmail.com)
87lgq0gwh3.fsf@openmailbox.org
Kei Kebreau <kei@openmailbox.org> writes:

Toggle quote (38 lines)
> Marius Bakke <mbakke@fastmail.com> writes:
>
>> Kei Kebreau <kei@openmailbox.org> writes:
>>
>>> Marius Bakke <mbakke@fastmail.com> writes:
>>>
>>>> Kei Kebreau <kei@openmailbox.org> writes:
>>>>
>>>>> Kei Kebreau <kei@openmailbox.org> writes:
>>>>>
>>>>> These patches are intended for gnome-updates. The first three are merged
>>>>> from master. Also, the mutter patch is not functional yet, as it
>>>>> probably requires some updated package from master.
>>>>
>>>> I think it's better to merge master directly instead of cherry-picking
>>>> these patches. We'd want to do that before starting it on Hydra anyway.
>>>>
>>>> Would you like to do it? I think we can start building it shortly, Hydra
>>>> seems to have caught up with recent events. Maybe it'll be ready for the
>>>> release :)
>>>>
>>> I can merge master and put these on top, though I can't test my patches
>>> very quickly (building webkitgtk+ repeatedly on 10-year-old hardware \o/).
>>> If your computer(s) are faster, I'd be more than happy to let you finish
>>> this branch.
>>
>> I think these patches look fine (see other comments), at least up to
>> mutter. I'd suggest merging master and adding the patches leading to
>> it, as long as everyone is fine with adding wayland as a hard dependency
>> of gtk+.
>>
>> Then we can start an evaluation on Hydra to get some substitutes before
>> trying the mutter update :)
>
> Last call for objections to wayland as a hard dependency of gtk+ on the
> gnome-updates branch! This will be committed in approximately 24 hours
> otherwise.

The gnome-updates branch has been updated! I'll be closing all of my
related bugs.
-----BEGIN PGP SIGNATURE-----

iQIzBAEBCAAdFiEEg7ZwOtzKO2lLzi2m5qXuPBlGeg0FAlkXmJgACgkQ5qXuPBlG
eg09zBAAkVnreF1hoPm/jT39j1X8jyaxKNFJrM4N3xupQ/BCuvOfbdTHL8jmVOpD
uxHrz9n9oa4Kr5LlnbE2XVbHeUz8WvvusiToHc6mqJ72mY/3YF6VZRsSUwvqD3DI
pyy1AGHq7qFAMHXqiqJ/5hWNClk+hoP3CveB4hJE+xpm2EM3PYmXGvaeAwsZc3RQ
jjD8FJ0pOMeZi8DIjY7HgUaDcjQbIhdUBk7Q23cLMHMLZxd4fD4IKSuVbo6R9i3z
ibdwuewfy2385NKjnBxS5AiEQ3lq8QQcuQyXpzv5o/ZCKEabhBWZ/hiefZ5sZJ3C
pRyJBPy4KLcHvTQ5AAqoLKanQK3/0ncXhlR2PKjBLAesNXpfdRIKHOCBWfgUnWwk
UZ7lpKlVns2o6L7U48gt6ygap8p9ebF6AmNRrJsXbGr4PJ61sDLsycZUF0YkKTjf
QOMUArM2IgpSpVf2C2ILlbf5NN3cK3okDF6aVT4V80aSJg38DoIHCiOagK9BRXaq
VVTsI+z1nTQl0Vcc0TWS90V8UCivI/kcGv2GjWLqcCZdXal8Dj9WSMC8IkI6TF7+
a9tJ2Agi2ezCxbGa8IQ3VzkuwmLaipd9FLlSKzxmt7mkwQ61Xf3fFy7i3zVuqaMI
2BQ7g3ZJgp08ZIVq5AXkUCn2jzx6gZpFU16UuqFgjactgwrmaTw=
=BLVL
-----END PGP SIGNATURE-----

Closed
?
Your comment

This issue is archived.

To comment on this conversation send an email to 26884@debbugs.gnu.org

To respond to this issue using the mumi CLI, first switch to it
mumi current 26884
Then, you may apply the latest patchset in this issue (with sign off)
mumi am -- -s
Or, compose a reply to this issue
mumi compose
Or, send patches to this issue
mumi send-email *.patch
You may also tag this issue. See list of standard tags. For example, to set the confirmed and easy tags
mumi command -t +confirmed -t +easy
Or, remove the moreinfo tag and set the help tag
mumi command -t -moreinfo -t +help