** Tags removed: sts-sponsor
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to bluez in Ubuntu.
https://bugs.launchpad.net/bugs/1674680
Title:
Deprecated rfcomm.conf still mentioned in bluetooth.conf and README
Status in bluez package in
** Tags removed: patch
** Changed in: bluez (Ubuntu Xenial)
Status: New => Won't Fix
** Changed in: bluez (Ubuntu Artful)
Assignee: (unassigned) => Dariusz Gadomski (dgadomski)
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to
This bug was fixed in the package bluez - 5.45-0ubuntu4
---
bluez (5.45-0ubuntu4) artful; urgency=medium
* Drop deprecated rfcomm.conf and upstart config. (LP: #1674680)
-- Dariusz Gadomski Mon, 07 Aug 2017
13:29:41 +0200
** Changed in: bluez (Ubuntu Artful)
Status: New
Sponsored artful.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to bluez in Ubuntu.
https://bugs.launchpad.net/bugs/1674680
Title:
Deprecated rfcomm.conf still mentioned in bluetooth.conf and README
Status in bluez package in Ubuntu:
Patch proposal for Artful.
** Patch added: "artful_bluez_5.45-0ubuntu3.debdiff"
https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1674680/+attachment/4928420/+files/artful_bluez_5.45-0ubuntu3.debdiff
** Patch removed: "artful_bluez_5.45-0ubuntu3.debdiff"
https://bugs.launchpad.net/ubun
** Also affects: bluez (Ubuntu Artful)
Importance: Low
Status: New
** Tags removed: sts-sponsor-chiluk
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to bluez in Ubuntu.
https://bugs.launchpad.net/bugs/1674680
Title:
Deprecated
Artful patch proposal.
** Patch added: "artful_bluez_5.45-0ubuntu3.debdiff"
https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1674680/+attachment/4928336/+files/artful_bluez_5.45-0ubuntu3.debdiff
** Patch removed: "zesty_bluez_5.43-0ubuntu2.debdiff"
https://bugs.launchpad.net/ubuntu/+s
Hi Dariusz,
Accordint to : https://merges.ubuntu.com/main.html
Jeremy Bicha is the one that did the last merge for bluez.
You could also asked him if there is any plan to merge bluez debian
upstream to Artful before the freeze.
bluez | 5.43-0ubuntu1 | zesty | source, amd64, arm64,
Hi Dariusz,
Since no upload has been done since last April for this particular bug,
this now need to be in devel release, thus Artful, before proceeding
with affected stable releases (if relevant).
I would suggest you prepare a debdiff for Artful get it sponsored by a
CoreDev, and then I'll be ab
** Summary changed:
- Deprecated rfcomm.conf still mentioned
+ Deprecated rfcomm.conf still mentioned in bluetooth.conf and README
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to bluez in Ubuntu.
https://bugs.launchpad.net/bugs/1674680
T
** Also affects: bluez (Debian)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to bluez in Ubuntu.
https://bugs.launchpad.net/bugs/1674680
Title:
Deprecated rfcomm.conf still mentioned
Status i
Just so you know I'm waiting for zesty release before uploading this. I
don't want to risk causing issues on the release media. Additionally
policy is to only push high priority bug fixes for the few weeks leading
up to release.
--
You received this bug notification because you are a member of
** Tags added: sts-sponsor-chiluk
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to bluez in Ubuntu.
https://bugs.launchpad.net/bugs/1674680
Title:
Deprecated rfcomm.conf still mentioned
Status in bluez package in Ubuntu:
New
Status in
** Changed in: bluez (Ubuntu Xenial)
Importance: Undecided => Low
** Changed in: bluez (Ubuntu Yakkety)
Importance: Undecided => Low
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to bluez in Ubuntu.
https://bugs.launchpad.net/bugs/16
** Description changed:
+ [Impact]
+
+ * The package contains misleading documentation mentioning the use of
+ /etc/bluetooth/rfcomm.conf for rfcomm setup while the support for config
+ file has been dropped after 14.04 release. I have directly received a
+ question about it from a user mislead
** Also affects: bluez (Ubuntu Xenial)
Importance: Undecided
Status: New
** Also affects: bluez (Ubuntu Yakkety)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to bluez in Ubuntu.
https:
** Changed in: bluez (Ubuntu)
Importance: Undecided => Low
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to bluez in Ubuntu.
https://bugs.launchpad.net/bugs/1674680
Title:
Deprecated rfcomm.conf still mentioned
Status in bluez packag
The attachment "zesty_bluez_5.43-0ubuntu2.debdiff" seems to be a
debdiff. The ubuntu-sponsors team has been subscribed to the bug report
so that they can review and hopefully sponsor the debdiff. If the
attachment isn't a patch, please remove the "patch" flag from the
attachment, remove the "patc
Patch proposal for Zesty.
** Tags added: sts sts-sponsor
** Patch added: "zesty_bluez_5.43-0ubuntu2.debdiff"
https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1674680/+attachment/4841667/+files/zesty_bluez_5.43-0ubuntu2.debdiff
--
You received this bug notification because you are a memb
** Summary changed:
- Dropped rfcomm.conf still mentioned
+ Deprecated rfcomm.conf still mentioned
** Description changed:
Support for config files has been dropped upstream in 2012 (however
version shipped with Trusty still supports it), but the latest versions
(including Xenial and Zest
20 matches
Mail list logo
