Package Details: bluez-utils-compat 5.50-6.2

Git Clone URL: https://aur.archlinux.org/bluez-utils-compat.git (read-only)
Package Base: bluez-utils-compat
Description: Development and debugging utilities for the bluetooth protocol stack. Includes deprecated tools.
Upstream URL: http://www.bluez.org/
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.565517
First Submitted: 2017-03-02 17:34
Last Updated: 2019-07-13 13:25

Required by (31)

Sources (4)

Latest Comments

« First ‹ Previous 1 2 3 4 5 Next › Last »

thurstylark commented on 2017-12-25 04:32

I'm unable to continue supporting this package. I have released it so someone can feel free to pick it up if it's still important enough.

jpoppe commented on 2017-12-24 16:16

Package conflicts with: bluez-hcitool

mazieres commented on 2017-07-25 10:53

This package works fine on the Raspberry Pi. Can you add 'armv7h' to the arch= array in the PKGBUILD?

alexei commented on 2017-06-12 02:48

I don't think the key was revoked. To get it run: gpg --recv-key 06CA9F5D1DCF2659

i4c3 commented on 2017-06-08 03:51

This might help: http://allanmcrae.com/2015/01/two-pgp-keyrings-for-package-management-in-arch-linux/

Of course, you could also just skip the pgp check altogether (not recommended):
makepkg -si --skippgpcheck

deisi commented on 2017-05-20 18:55

This package uses a pgp key from Marcel Holtmann, that has been revoked. Anybody knows anything about it? I guess like this one should not install the package or?

NicolasV commented on 2017-05-10 22:39

For people having trouble to build the package, I uploaded mine here.

http://dl.free.fr/tlJJKwmd7

NicolasV commented on 2017-05-10 22:36

I made a diff of the configure step on my laptop (ok) and my desktop (ko)
Here's the result of the diff. The only difference seems to be the paths : /usr/sbin (on my laptop) /usr/bin (on my desktop) but I don't think that's the cause of the problem.


diff --color configure_*
3c3
< checking for a thread-safe mkdir -p... /usr/bin/mkdir -p
---
> checking for a thread-safe mkdir -p... /usr/sbin/mkdir -p
21,22c21,22
< checking for grep that handles long lines and -e... /usr/bin/grep
< checking for egrep... /usr/bin/grep -E
---
> checking for grep that handles long lines and -e... /usr/sbin/grep
> checking for egrep... /usr/sbin/grep -E
39c39
< checking for pkg-config... /usr/bin/pkg-config
---
> checking for pkg-config... /usr/sbin/pkg-config
52,57c52,57
< checking for a sed that does not truncate output... /usr/bin/sed
< checking for fgrep... /usr/bin/grep -F
< checking for ld used by gcc... /usr/bin/ld
< checking if the linker (/usr/bin/ld) is GNU ld... yes
< checking for BSD- or MS-compatible name lister (nm)... /usr/bin/nm -B
< checking the name lister (/usr/bin/nm -B) interface... BSD nm
---
> checking for a sed that does not truncate output... /usr/sbin/sed
> checking for fgrep... /usr/sbin/grep -F
> checking for ld used by gcc... /usr/sbin/ld
> checking if the linker (/usr/sbin/ld) is GNU ld... yes
> checking for BSD- or MS-compatible name lister (nm)... /usr/sbin/nm -B
> checking the name lister (/usr/sbin/nm -B) interface... BSD nm
64c64
< checking for /usr/bin/ld option to reload object files... -r
---
> checking for /usr/sbin/ld option to reload object files... -r
73c73
< checking command to parse /usr/bin/nm -B output from gcc object... ok
---
> checking command to parse /usr/sbin/nm -B output from gcc object... ok
85c85
< checking whether the gcc linker (/usr/bin/ld -m elf_x86_64) supports shared libraries... yes
---
> checking whether the gcc linker (/usr/sbin/ld -m elf_x86_64) supports shared libraries... yes

NicolasV commented on 2017-05-10 15:27

Too long to paste.
Here's a link to check the log file, which seems incomplete.
Last line is just half-written...

http://www.wepaste.com/bluez-utils-compat/

thurstylark commented on 2017-05-10 14:58

Post the contents of the resulting test-suite.log