Package Details: pulseaudio-bluetooth-git 17.0.r38.gcba313d8f-1

Git Clone URL: https://aur.archlinux.org/pulseaudio-git.git (read-only, click to copy)
Package Base: pulseaudio-git
Description: Bluetooth support for PulseAudio (development)
Upstream URL: http://pulseaudio.org/
Licenses: LGPL-2.1-or-later
Conflicts: pulseaudio-bluetooth
Provides: pulseaudio-bluetooth
Submitter: None
Maintainer: SolarAquarion
Last Packager: SolarAquarion
Votes: 38
Popularity: 0.000000
First Submitted: 2009-02-09 14:33 (UTC)
Last Updated: 2024-08-14 04:29 (UTC)

Latest Comments

« First ‹ Previous 1 2 3 4 5 6 7 .. 10 Next › Last »

nika commented on 2021-02-22 15:13 (UTC)

Seems like libelogind should be added as dep

pulseaudio/meson.build:658:0: ERROR: Dependency "libelogind" not found, tried pkgconfig and cmake

sentriz commented on 2021-02-12 23:44 (UTC)

seems like I had to install valgrind and libwrap before installing. perhaps they should be added as deps?

professed commented on 2021-01-20 17:39 (UTC)

@beroal: Thank you, this is good to know for the future. For now, the updated version of pulseaudio in the official repo now seems to work with my system, so I've uninstalled the AUR package.

beroal commented on 2021-01-20 10:29 (UTC)

@professed You can upgrade with --nodeps. This may break database consistency. Then check database consistency with -D --check.

professed commented on 2021-01-20 09:03 (UTC)

I'm on Manjaro GNOME and I cannot perform the latest stable update (2021-01-19) due to a tricky package conflict pulseaudio-git, which I need for hardware support. I get the following message when attempting 'pacman -Syu':

looking for conflicting packages...
:: libpulse and pulseaudio-git are in conflict (libpulse.so). Remove pulseaudio-git? [y/N]

Declining to remove pulseaudio-git aborts the upgrade ("error: unresolvable package conflicts detected"), and opting to remove it also causes the update to error out with the following dependency errors:

error: failed to prepare transaction (could not satisfy dependencies)
:: removing pulseaudio-git breaks dependency 'pulseaudio-bluetooth' required by gnome-bluetooth
:: removing pulseaudio-git breaks dependency 'pulseaudio-bluetooth' required by manjaro-bluetooth
:: removing pulseaudio-git breaks dependency 'pulseaudio-equalizer' required by manjaro-pulse
:: removing pulseaudio-git breaks dependency 'pulseaudio-jack' required by manjaro-pulse
:: removing pulseaudio-git breaks dependency 'pulseaudio-zeroconf' required by manjaro-pulse
:: removing pulseaudio-git breaks dependency 'pulseaudio-lirc' required by manjaro-pulse

I can't temporarily remove any of the packages that require pulseaudio-git, either, as they're required by yet other packages, which are required by yet other packages.

Attempting to install vanilla pulseaudio in place of pulseaudio-git is also a non-starter, as it yields the same initial error message as above ("libpulse and pulseaudio-git are in conflict (libpulse.so).", etc.).

Any help climbing out of this rabbit hole would be greatly appreciated.

professed commented on 2020-12-10 20:05 (UTC) (edited on 2020-12-10 20:06 (UTC) by professed)

Update: Installing the valgrind package prior to build solves the dependency problem and allows for a successful install. Suggest adding it to the list of dependencies.

professed commented on 2020-12-09 19:54 (UTC) (edited on 2020-12-09 19:54 (UTC) by professed)

Build of pulseaudio-git 14.0.r41.g6bf178d79-1 fails, erroring out with the following message:

pulseaudio/meson.build:234:6: ERROR: C header 'valgrind/memcheck.h' not found

A full log can be found at /home/username/.cache/yay/pulseaudio-git/src/build/meson-logs/meson-log.txt
==> ERROR: A failure occurred in build().
    Aborting...
error making: pulseaudio-git

The meson log file mentioned in the output above is here in the event it's helpful.

bwv549 commented on 2020-11-20 18:04 (UTC)

Same issue as @alwyns42 (and I definitely have pulseaudio running before build)

woopstar commented on 2020-10-12 13:29 (UTC)

Same issue as @alwyns42

rross101 commented on 2020-10-09 19:52 (UTC)

Same issue as @alwyns42