Update to 3.16

Bug #1345884 reported by Robert Ancell on 2014-07-21
This bug affects 4 people
Affects Status Importance Assigned to Milestone
gnome-bluetooth (Ubuntu)
Lars Karlitski

Bug Description

Update to 3.16

Robert Ancell (robert-ancell) wrote :

Requires bluez 5 (bug 1162781)

Changed in gnome-bluetooth (Ubuntu):
status: New → Triaged
importance: Undecided → Wishlist
Changed in gnome-bluetooth (Ubuntu):
assignee: nobody → Robert Ancell (robert-ancell)
status: Triaged → In Progress
Changed in gnome-bluetooth (Ubuntu):
assignee: Robert Ancell (robert-ancell) → Lars Uebernickel (larsu)
summary: - Update to 3.12
+ Update to 3.16
description: updated
Amr Ibrahim (amribrahim1987) wrote :

Any news for packaging this for wily? I think bluez 5 needs broad testing in 15.10 before 16.04 LTS.

tags: added: wily
tags: added: bluez5
Launchpad Janitor (janitor) wrote :

This bug was fixed in the package gnome-bluetooth - 3.16.1-1ubuntu1~ppa1

gnome-bluetooth (3.16.1-1ubuntu1~ppa1) wily; urgency=medium

  * Merge with debian, remaining changes:
    + debian/control.in:
      - Build-dep on dh_autoreconf
      - Recommends unity-control-center | gnome-control-center, gnome-user-share
    + debian/rules:
      - don't build with -Wl,-Bsymbolic-functions that creates issues when
        the --as-needed option is used
      - use dh-autoreconf
    + debian/gnome-bluetooth.maintscript
    + debian/patches/logitech_ultrathin_touch_pin.patch: specify a default PIN
      for the Logitech Ultrathin Touch mice. Thanks to Ralph Meijer for the
      patch. (LP: #1237355)
  * Drop ConsoleKit Rules from rfkill
  * Drop patches included in new release

 -- Tim Lunn <email address hidden> Thu, 06 Aug 2015 12:40:13 +1000

Changed in gnome-bluetooth (Ubuntu):
status: In Progress → Fix Released
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers