Package Details: aura 4.0.8-1

Git Clone URL: https://aur.archlinux.org/aura.git (read-only, click to copy)
Package Base: aura
Description: A package manager for Arch Linux and its AUR
Upstream URL: https://github.com/fosskers/aura
Keywords: AUR pacman rust
Licenses: GPL-3.0-or-later
Conflicts: aura-bin, aura-git, aura3-bin
Submitter: fosskers
Maintainer: fosskers
Last Packager: fosskers
Votes: 170
Popularity: 0.041351
First Submitted: 2012-06-13 09:49 (UTC)
Last Updated: 2024-09-29 08:02 (UTC)

Dependencies (13)

Required by (2)

Sources (1)

Pinned Comments

fosskers commented on 2024-07-31 10:21 (UTC)

Aura 4 has been released. If instead you wish you keep using the Haskell-based v3 series, please install:

https://aur.archlinux.org/packages/aura3-bin

Latest Comments

1 2 3 4 5 6 .. 40 Next › Last »

beef commented on 2024-09-21 15:17 (UTC)

Thanks! It worked.

fosskers commented on 2024-09-21 09:55 (UTC)

@beef That should resolve itself if you first update Pacman 7 and then manually rebuild Aura.

beef commented on 2024-09-21 07:41 (UTC) (edited on 2024-09-21 07:43 (UTC) by beef)

aura -Akua gives me this error:

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

I guess this has to do with the release of pacman 7.0.0.

Does anyone else have this problem? Maybe it is just a misconfiguration on my side.

hoppyhopps commented on 2024-09-14 20:56 (UTC) (edited on 2024-09-15 00:07 (UTC) by hoppyhopps)

Cargo still fails to build referencing alpm v3.0.5 using 4.0.6-1 pulled today.

Cargo.lock still references alpm 3.0.5, alpm-sys 3.0.0 and alpm-utils 3.0.2.

This may be user error, but I figured you may like to know.

Edit:

4.0.7 builds properly! Thank you very much, and sorry for the misunderstanding with 4.0.6!

vaurelios commented on 2024-09-14 19:52 (UTC)

Please remove the haskell tag.

fosskers commented on 2024-08-27 00:52 (UTC) (edited on 2024-08-27 00:53 (UTC) by fosskers)

@foxcub: You certainly should be able to.

According to https://wiki.archlinux.org/title/PKGBUILD#arch , I suppose I'd have to add armv7h and aarch64 to the arch field of the PKGBUILD?

It's not any because any implies it can be run on any system after having been built. That's not the case here, as Rust binaries are architecture-dependent (unlike say, Python).

foxcub commented on 2024-08-26 21:58 (UTC)

Why is arch only x86_64 and not any? Can I use this on ARM?

fosskers commented on 2024-08-10 02:51 (UTC) (edited on 2024-08-10 02:51 (UTC) by fosskers)

@foxcub: Citing the PKGBUILD article of the Arch Wiki:

The package base-devel is assumed to be already installed when building with makepkg. Dependencies of this package should not be included in makedepends array.

This includes the packages you've described, so I'll be leaving them out.

See: https://wiki.archlinux.org/title/PKGBUILD#makedepends

foxcub commented on 2024-08-09 23:52 (UTC)

Various packages need gcc and pkginfo installed, so those are two more build-time dependencies.

foxcub commented on 2024-08-07 17:51 (UTC)

makeinfo is in texinfo, so you need that as build-time dependency.

1 2 3 4 5 6 .. 40 Next › Last »