Package Details: auracle-git r427.33f9097-1

Git Clone URL: https://aur.archlinux.org/auracle-git.git (read-only, click to copy)
Package Base: auracle-git
Description: A flexible client for the AUR
Upstream URL: https://github.com/falconindy/auracle
Keywords: aur
Licenses: MIT
Conflicts: auracle
Provides: auracle
Submitter: Foxboron
Maintainer: artafinde (falconindy)
Last Packager: falconindy
Votes: 128
Popularity: 1.20
First Submitted: 2017-07-02 16:40 (UTC)
Last Updated: 2025-04-16 17:39 (UTC)

Required by (10)

Sources (1)

Pinned Comments

artafinde commented on 2022-01-26 09:15 (UTC) (edited on 2022-01-29 10:24 (UTC) by artafinde)

If the build fails:

  • Clear your aur helper cache and SRCPKGDEST directory
  • Rebuild in clean chroot 1
  • If it still fails, use a paste bin 2 to show full build logs

There's a package build already which you can try out from my repo.

falconindy commented on 2020-05-31 15:35 (UTC) (edited on 2025-04-28 14:23 (UTC) by falconindy)

FAQ:

  • If you think pod2man is missing, it's a configuration problem on your end. pod2man is part of the perl package, but in a perl-specific PATH handled by /etc/profile.d/perlbin.sh
  • I'm only able to test auracle on i686 and x86_64, so that's what I'm willing to commit to in the PKGBUILD. If you want to build this on some other architecture, use makepkg -A. The "any" architecture is reserved for packages with architecture independent files (and compiled C++ is not).

Latest Comments

« First ‹ Previous 1 .. 18 19 20 21 22 23 24 25 26 27 28 .. 30 Next › Last »

SanskritFritz commented on 2019-10-24 08:46 (UTC)

@lisu_ml: This is a -git package, where the version does not reflect the current status anyway. Git package users are expected to follow upstream development and rebuild the package themselves when necessary. This way the version will automatically updated locally independently from the package version on the AUR.

lisu_ml commented on 2019-10-24 08:42 (UTC) 

That's not how this works. That's not how any of this works. Rebuild auracle yourself.

@falconindy: and what do you mean by that? It's a common practice to bump pkgrel when there is new version of shared library the package depends on. IMO, bumping pkgrel is not something difficult to do and can save other users' time as it would trigger automatic rebuild on their end. I don't understand what is the problem with simple pkgrel bump? Please elaborate.

Cthulhu82 commented on 2019-10-24 07:03 (UTC)

@HiImTye "auracle sync -q | xargs auracle clone" should do it. Of course, it is a little bit more verbose.

HiImTye commented on 2019-10-24 06:01 (UTC)

is there an equivalent operation to cower -ud, or do we need to write a custom script to facilitate that functionality?

falconindy commented on 2019-10-24 00:22 (UTC)

That's not how this works. That's not how any of this works. Rebuild auracle yourself.

lisu_ml commented on 2019-10-24 00:05 (UTC) (edited on 2019-10-24 00:12 (UTC) by lisu_ml)

@falconindy: please bump the pkgrel to resolve libalpm.so.11 issue.

gj545rndmu commented on 2019-10-23 10:50 (UTC)

For everyone who just updated pacman and is wondering why they get following error:

auracle: error while loading shared libraries: libalpm.so.11: cannot open shared object file: No such file or directory

Just recompile auracle-git and install it again ;)

gonsoos commented on 2019-10-01 23:47 (UTC)

Thank you very much! Though I have rwx ownership of the drive, it is indeed ntfs formatted. Building it on my ext4 partition worked as intended :) I hadn't thought about that...

falconindy commented on 2019-10-01 22:53 (UTC)

If I had to guess, I'd say you're attempting to build auracle on an ntfs or vfat filesystem and mounted it with a mode or fmask that disables the executable bit.

« First ‹ Previous 1 .. 18 19 20 21 22 23 24 25 26 27 28 .. 30 Next › Last »