Package Details: bluez-utils-compat 5.51-1

Git Clone URL: (read-only)
Package Base: bluez-utils-compat
Description: Development and debugging utilities for the bluetooth protocol stack. Includes deprecated tools.
Upstream URL:
Keywords: hciconfig hcidump hcitool
Licenses: GPL2
Conflicts: bluez-hcidump, bluez-hcitool, bluez-utils
Provides: bluez-hcidump, bluez-hcitool, bluez-utils
Replaces: bluez<=4.101, bluez-hcidump
Submitter: thurstylark
Maintainer: twa022
Last Packager: twa022
Votes: 24
Popularity: 0.508917
First Submitted: 2017-03-02 17:34
Last Updated: 2019-09-25 01:04

Required by (31)

Sources (3)

Latest Comments

1 2 3 4 5 Next › Last »

parkerlreed commented on 2019-10-22 01:20

Anybody found a way to reenable gatttool? Seems it was even removed from compat

thisischrys commented on 2019-07-15 15:45

Still Unable to find a built tarball for bluez-utils-compat

naraesk commented on 2019-07-11 09:14

"Skip the test cases" doesn't sound like a good workaronud. Most likely there is a reason why they fail. Is there an upstream bug report about this?

TheSaint commented on 2019-07-08 13:07

@KoaTravis You were right. It worked, but wouldn't it be better to see what these tests are about?

jonas.koeritz commented on 2019-07-08 09:30

@KoaTravis, removing the check() part worked for me as well, but this should really be fixed to allow installation without manual intervention. "yay" users: use "yay -Syua --editmenu" to allow editing of PKGBUILD before installation attempts.

mokman commented on 2019-07-07 15:06

i try to compile on raspberry zero as a dependency for pi-bluetooth, this comes up: Unable to find a built tarball for bluez-utils-compat

satcom886 commented on 2019-07-06 13:04

@thisischrys I also believe there should be no manual intervention needed. It is just inconvenient.

KoaTravis commented on 2019-07-05 13:31

@TheSaint I had the same problem. After removing the check function from the PKGBUILD I was able to successfully build and install it.

TheSaint commented on 2019-07-03 11:51

I can finish the installation, the unittest are failing ./test-driver: line 107: 14099 Aborted (core dumped) "$@" > $log_file 2>&1 FAIL: unit/test-sdp PASS: unit/test-gobex-apparam ./test-driver: line 107: 14119 Aborted (core dumped) "$@" > $log_file 2>&1 FAIL: unit/test-avrcp ./test-driver: line 107: 14098 Aborted (core dumped) "$@" > $log_file 2>&1 FAIL: unit/test-avctp PASS: unit/test-lib PASS: unit/test-gattrib PASS: unit/test-midi PASS: unit/test-gobex ./test-driver: line 107: 14212 Aborted (core dumped) "$@" > $log_file 2>&1 FAIL: unit/test-gatt ./test-driver: line 107: 14229 Aborted (core dumped) "$@" > $log_file 2>&1 FAIL: unit/test-hog =============================================================================== Then it takes a long time and doesn't quit. I have to interrupt it manually.

yekm commented on 2019-06-30 12:32

It is not only the signal.h. The api in ell is also changed