Package Details: bluez-alsa-git 4.2.0.r17.g14670ed-1

Git Clone URL: https://aur.archlinux.org/bluez-alsa-git.git (read-only, click to copy)
Package Base: bluez-alsa-git
Description: Bluetooth audio ALSA backend
Upstream URL: https://github.com/Arkq/bluez-alsa
Keywords: alsa bluetooth bluez
Licenses: MIT
Submitter: nheird
Maintainer: morgenstern
Last Packager: morgenstern
Votes: 26
Popularity: 0.000000
First Submitted: 2016-10-28 17:41 (UTC)
Last Updated: 2024-06-26 23:15 (UTC)

Dependencies (15)

Required by (0)

Sources (1)

Latest Comments

1 2 3 4 Next › Last »

morgenstern commented on 2025-05-19 23:14 (UTC) (edited on 2025-05-19 23:19 (UTC) by morgenstern)

@fvdb06 I am merely suggesting a possible avenue of investigation. I have no clue how your system is set up, how you have configured yay, or what other options or settings you are using. If you build this package using makepkg in a clean chroot, you should not see any issues.

If I go to Google and I search for some combination of yay arch linux permission denied /tmp there are many relevant results (e.g., here and here). I suggest you start there. If you need further help, I recommend starting a post on the Arch Linux forums for AUR issues, which is a better forum for figuring this out.

fvdb06 commented on 2025-05-19 15:33 (UTC)

I don't understand wht you mean with => Please check your yay setup. Can you explain?

And this is my /tmp setting:

/etc/fstab

tmpfs /tmp tmpfs rw,nodev,nosuid,size=2G 0 0

morgenstern commented on 2025-05-17 09:41 (UTC) 

 /tmp/yay/bluez-alsa-git/PKGBUILD: line 66: ./configure: Permission denied

You do not appear to have permission to execute configure from /tmp on your system. Please check your yay setup.

fvdb06 commented on 2025-05-16 08:33 (UTC)

==> no candidate packages found for pruning ==> Making package: bluez-alsa-git 4.2.0.r17.g14670ed-1 (Fri 16 May 2025 10:29:27 AM CEST) ==> Checking runtime dependencies... ==> Checking buildtime dependencies... ==> Retrieving sources... -> Updating bluez-alsa-git git repo... ==> Validating source files with sha512sums... bluez-alsa-git ... Skipped ==> Removing existing $srcdir/ directory... ==> Extracting sources... -> Creating working copy of bluez-alsa-git git repo... Cloning into 'bluez-alsa-git'... done. ==> Starting pkgver()... ==> Updated version: bluez-alsa-git 4.3.1.r64.g20bae74-1 ==> Sources are ready. ==> Making package: bluez-alsa-git 4.3.1.r64.g20bae74-1 (Fri 16 May 2025 10:29:30 AM CEST) ==> Checking runtime dependencies... ==> Checking buildtime dependencies... ==> WARNING: Using existing $srcdir/ tree ==> Starting pkgver()... ==> Starting build()... aclocal: warning: couldn't open directory 'm4': No such file or directory libtoolize: putting auxiliary files in '.'. libtoolize: copying file './ltmain.sh' libtoolize: putting macros in AC_CONFIG_MACRO_DIRS, 'm4'. libtoolize: copying file 'm4/libtool.m4' libtoolize: copying file 'm4/ltoptions.m4' libtoolize: copying file 'm4/ltsugar.m4' libtoolize: copying file 'm4/ltversion.m4' libtoolize: copying file 'm4/lt~obsolete.m4' configure.ac:20: installing './ar-lib' configure.ac:14: installing './compile' configure.ac:22: installing './config.guess' configure.ac:22: installing './config.sub' configure.ac:8: installing './install-sh' configure.ac:8: installing './missing' src/Makefile.am: installing './depcomp' parallel-tests: installing './test-driver' /tmp/yay/bluez-alsa-git/PKGBUILD: line 66: ./configure: Permission denied ==> ERROR: A failure occurred in build(). Aborting... -> error making: bluez-alsa-git-exit status 4 -> Failed to install the following packages. Manual intervention is required: bluez-alsa-git - exit status 4

morgenstern commented on 2025-05-10 01:26 (UTC) (edited on 2025-05-10 01:33 (UTC) by morgenstern)

@fvdb06 I cannot recreate this. You appear to have omitted key build log lines from before the ==> ERROR line, so I have no idea why your build failed. Package builds without issue for me from the head of the master branch in a clean chroot.

fvdb06 commented on 2025-05-09 21:17 (UTC)

==> ERROR: A failure occurred in build(). Aborting... -> error making: bluez-alsa-git-exit status 4 -> Failed to install the following packages. Manual intervention is required: bluez-alsa-git - exit status 4

morgenstern commented on 2022-11-23 06:25 (UTC) (edited on 2022-11-23 06:31 (UTC) by morgenstern)

@amateur I would recommend opening an issue upstream to see if the developer would be willing to add support for libfreeaptx.

As for the ALT Linux package you referenced, I am not sure how it makes use of libfreeaptx, as I cannot see any evidence of patching and the upstream documentation makes no reference to libfreeaptx support.

amateur commented on 2022-11-19 07:47 (UTC)

(I have no idea about who started the libfreeaptx or libopenaptx drama, I just know something happened, but not what)

The official arch repositories provide libfreeaptx.

This upstream repository uses libopenaptx.

There exists a bluez-alsa repository that uses libfreeaptx instead:

https://packages.altlinux.org/en/sisyphus/srpms/bluez-alsa/

I don't think I have the skills to reliably replace the library in the code (I started grepping through and making changes, but I quickly realized theres a few other differences, but not many, but still enough to make me doubt I would get it to compile properly)

neoresin commented on 2022-07-26 20:11 (UTC)

@morgenstern My mistake! Not sure how I missed the message.

morgenstern commented on 2022-07-26 20:09 (UTC)

@neorsein do not flag VCS packages as out-of-date. Please re-run makepkg if you need the latest version.

1 2 3 4 Next › Last »