Package Details: blueman-git 2.1.alpha3.r5.g088da0c7-1

Git Clone URL: (read-only, click to copy)
Package Base: blueman-git
Description: A GTK+ Bluetooth Manager (BlueZ 5) - git
Upstream URL:
Keywords: bluetooth network
Licenses: GPL
Conflicts: blueman, blueman-bzr
Provides: blueman
Submitter: flexiondotorg
Maintainer: silvio
Last Packager: silvio
Votes: 107
Popularity: 0.34
First Submitted: 2014-09-09 13:53
Last Updated: 2019-04-06 14:09

Required by (2)

Sources (1)

Latest Comments

1 2 3 4 5 6 Next › Last »

MrHritik commented on 2017-11-17 12:29

PKGBUILD: line 36: ./configure: No such file or directory

txus commented on 2015-10-28 13:17

Blueman doesn't start per default at least with newer git versions. You should add

glib-compile-schemas /usr/share/glib-2.0/schemas

at the end of the install file. Thanks!

WhyNotHugo commented on 2015-05-15 23:54

Please update the package, upstream has supported python3 for some time now.

WhyNotHugo commented on 2015-04-12 18:54

The latest code from upstream merges python3 support:

I'd advise that we now use python3 for this package:

1) Make the PKGBUILD simpler.
2) It'll use our default python.
3) Help upstream find any undetected issues.

WhyNotHugo commented on 2015-03-22 00:00

makepends extra/intltool is missing.

WhyNotHugo commented on 2015-03-14 12:31

makedepends intltool is missing.

morgenstern commented on 2015-03-07 08:51

If blueman-manager fails to run and does a core dump because one of the settings schemas is not loaded, run the following as root to compile the appropriate settings schema, then run blueman-manager again.

# /usr/bin/glib-compile-schemas /usr/share/glib-2.0/schemas/

Note that glib-2.0/ may be located in a different folder on your system, such as /usr/local, for example.

WhyNotHugo commented on 2015-03-05 10:42

==> Starting prepare()... installing './compile' installing './config.guess' installing './config.sub' installing './install-sh' installing './missing' error: required file 'blueman/plugins/config/' not found

Anyone else having this issue?

JP-Ellis commented on 2015-01-26 23:50

The pkgver() function uses the current date which is causing makepkg to identify a new version every single day (even with no changes to the code). It should be updated to track more accurately the repository.

Taken from the Arch Wiki, this should work:
pkgver() {
git describe --long --tags 2>/dev/null | sed 's/\([^-]*-g\)/r\1/;s/-/./g'
At the time of writing this, this will produce version `1.99.alpha1.r94.g4797888`.

flexiondotorg commented on 2014-11-04 10:10

@dot - python2-cairo has been added.