fosskers / aura Goto Github PK

These two options are lacking, and are big. Will likely require all sorts of json.

It can't access anything—no searching, no PKGBUILDS, no packages—nothing. It thinks the AUR is empty.

aura -Au

aura >>= Fetching package information...
aura >>= Comparing package versions...
aura >>= AUR Packages to upgrade:
tp_smapi-dkms : 0.6.4-2 => 0.41-7

aura -Qi tp_smapi-dkms

Nimi                    : tp_smapi-dkms
Versio                  : 0.41-7

It keeps offering that update everytime -Au is used.

I'm to be moving Aura off of haskell-curl and fully onto haskell-http. Once complete, haskell-regex-pcre will be the only AUR-only haskell dep for aura. I think that means it's time to move all the haskell deps back to the makedeps field. Many people have brought this up, and despite Aura's fast release cycle, if they don't want ghc installed all the time, I don't think (anymore) that I should force them.

@dkasak @spyhawk @Kwpolska What do you guys think?

The reason an -Syu can check for AUR upgrades in packer so quickly is because it uses & to break of each curl request into its own process. I'll need to do something similar with aura to speed up -Au.

In particular, the recent change of grub to an AUR package breaks this.

Check the output -Qm for packages that are actually AUR packages?
For some reason packer does not explode as Aura is here.

1. User should edit PKGBUILD before aura check or building it.
2. When user using --hotedit option. It no way to edit PKGBUILD.

Details:

1. I was try sudo aura -Aax multiget and aura give me error cause no svn pkg. PKGBUILD need to change makedepens from out-of-date svn to subversion.

so I try again with sudo aura -Aax --hotedit multiget but aura still told me the same error.

2. I'm curious about what exactly --hotedit did. I try install pkg that I known it's work well (eg. sudo aura -A --hotedit renameutils).

Result is aura give me an option to edit PKGBUILD but when I said yes. it no Text Editor or something like that. since I wonder how can I edit PKGBUILD, aura don't care and skip to building process.

Hello. I'm trying to install gstreamer0.10-good-plugins-slim and I find the following error

[carlos@sunspear ~]$ sudo aura -Aux gstreamer0.10-good-plugins-slim
aura >>= Fetching package information...
aura >>= Comparing package versions...
aura >>= No AUR package upgrades necessary.
aura >>= Determining dependencies...
aura >>= Dependency checking failed for these reasons:
The dependency gstreamer0.10-good demands version =0.10.31but the most recent version is .10.31-1.

Maybe it's due to the odd package name?

Thanks for the help.

Take a look at it. (the most interesting number is the the one that has **’s around it, added by yours truly.)

[kwpolska@kwpolska-lin ~]% time yes 'n' | pkgbuilder -Syu
:: Gathering data about packages...
Targets (1): libgnomecups
Proceed with installation? [Y/n] yes 'n'  0.00s user 0.00s system 0% cpu 17.912 total
pkgbuilder -Syu  0.77s user 0.43s system 6% cpu **17.911** total
[kwpolska@kwpolska-lin ~]% time yes 'n' | sudo aura -Au
aura >>= Fetching package information...
aura >>= Comparing package versions...
aura >>= Determining dependencies...
aura: Prelude.head: empty list
yes 'n'  0.00s user 0.00s system 0% cpu 7:35.78 total
sudo aura -Au  52.39s user 12.26s system 14% cpu **7:35.78** total

So, pkgbuilder -Syu took only under 18 seconds and returned one package, that is, in fact, outdated. Aura, though, wasted 7:35 minutes and did not tell me what packages are outdated.

But those 18 seconds are not the best time I can get. Right after aura -Au, I did pkgbuilder -Syu again, clocking 3.500 at the first attempt and 1.575 at the best one.

3.500
1.575
1.750

Now, looking at how aura works now, i.e. downloading a PKGBUILD and reading stuff from it¹, you won’t get as fast, because PB checks dependencies later and installs missing ones during the build process of the package wanting it rather than before it, and never reads the PKGBUILD file on its own.

¹ IIRC, you are doing this by hand rather than asking bash to do some parsing, which is not the best idea, as custom parsers often choke on bash. PKGBUILDer ran for exactly 365 days with a custom parser, and it liked to break, especially on easy stuff like an empty string in (make)depends (pyload until few releases ago) or makedepends before depends. Right now, I do it like this:

        pkgbuild = '/tmp/pkgbuilder-1000/pkgbuilder/PKGBUILD' #sample
        pb = subprocess.Popen('source ' + pkgbuild + '; for i in ${depends'
                              '[*]}; do echo $i; done; for i in '
                              '${makedepends[*]}; do echo $i; done',
                              shell=True, stdout=subprocess.PIPE)
        deps = pb.stdout.read()
        deps = deps.decode('utf-8')
        deps = deps.split('\n')

In other words, packages with suffixes such as -git, -hg, -bzr, etc which track a remote repository, such as described here: https://wiki.archlinux.org/index.php/VCS_PKGBUILD_Guidelines. The option could either be a "standalone" suboption to rebuild all such packages (e.g. -A) or an -Au "modifier" which rebuilds such packages along with upgrading regular packages (e.g. -Ayu).

I'm trying to install cavestory+ from the AUR. However, even with quotes, aura won't recognize cavestory+. It shows up in an aura AUR search (with the + lacking color), but it won't do anything with the name when I try to install, get info, or get the PKGBUILD.

I get the following output preceding every aura command I enter:

"(color.conf)" (line 47, column 1):
unexpected end of input
expecting space, "#" or valid colour variable name

This wasn't the case with 1.0.7.0.
This doesn't have any impact on functionality, so I'm guessing it might be related to pacman-color.

I'm currently running into the following error when trying to install shutter from AUR.

$ sudo aura -Ax shutter
[sudo] password for rwallace: 
aura >>= Determining dependencies...
aura: Prelude.head: empty list

Installation of a package fails when trying to install when pacman's
signature trust level is set to "PackageRequired".

Specifically, makepkg successfully creates the *.tar.xz and the
*.tar.xz.sig file, but the following error occurs (irrelevant sections
elided)

==> Tidying install...
  -> Purging unwanted files...
  -> Compressing man and info pages...
  -> Stripping unneeded symbols from binaries and libraries...
==> Creating package...
  -> Generating .PKGINFO file...
  -> Adding install file...
  -> Compressing package...
==> Signing package...

You need a passphrase to unlock the secret key for
user: "Sung Pae <[email protected]>"
1024-bit DSA key, ID C8C835A2, created 2011-03-21

  -> Created signature file /var/cache/pacman/pkg/gpodder3-11488/gpodder3/gpodder3-3.3.0-2-any.pkg.tar.xz.sig.
==> Leaving fakeroot environment.
==> Finished making: gpodder3 3.3.0-2 (Thu Oct  4 21:00:18 CDT 2012)
loading packages...
error: '/var/cache/pacman/pkg/gpodder3-3.3.0-2-any.pkg.tar.xz.sig': cannot open package file

The signature file is present in /var/cache/pacman, but the actual
package is not.

Thank you for building an excellent AUR build tool.

Let's use a simple example.
The AUR package "packer" has an binary dependency "jshon" which depends itself on the binary package "jansson".

With "packer" in IgnoredPkg variable in pacman.conf:

sudo aura -A packer
aura >>= The following packages will be ignored:
packer

aura >>= Determining dependencies...
aura >>= Dependency checking failed for these reasons:
No AUR packages specified for install.

This works as expected :)

With jshon in IgnorePkg variable in pacman.conf:

$ sudo aura -A packer
aura >>= Determining dependencies...
aura >>= Dependency checking failed for these reasons:
`jshon` is an ignored package! See your `pacman.conf` file.

This works as expected :)

With jansson in IgnorePkg variable in pacman.conf:

sudo aura -A packer
[sudo] password for remy: 
aura >>= Determining dependencies...
aura >>= Repository dependencies:
jshon

aura >>= Main AUR packages:
packer

aura >>= Continue? [Y/n] y
resolving dependencies...
warning: ignoring package jansson-2.4-1
warning: cannot resolve "jansson", a dependency of "jshon"
:: The following package cannot be upgraded due to unresolvable dependencies:
      jshon

Do you want to skip the above package for this upgrade? [y/N]
[...]

Edit: Don't know if this is what would be expected. Aura doesn't check for the ignore dep, but pacman does the job afterward.

With an empty IgnoredPkg in pacman.conf, but using the --ignore flag:

$ sudo aura -A packer --ignore packer
aura >>= Determining dependencies...
aura >>= Main AUR packages:
packer

aura >>= Continue? [Y/n] y
aura >>= Building `packer`...
error: no targets specified (use -h for help)

The build fails, but the --ignore flag doesn't work as expected. I guess a check must be done before prompting with "Continue?", similarly to the first example above.

sudo aura -A packer --ignore jshon
aura >>= Determining dependencies...
aura >>= Repository dependencies:
jshon

aura >>= Main AUR packages:
packer

aura >>= Continue? [Y/n] y
error: no targets specified (use -h for help)
aura >>= Building `packer`...
aura >>= Well, building `packer` failed.
aura >>= Dumping makepkg output in 3.. 2.. 1..
==> Determining latest git revision...
  -> Version found: 20121205
==> ERROR: A package has already been built. (use -f to overwrite)


aura >>= Building failed.

Failed :(
Same comment as above here. The binary dep "jansson" of the binary dep "jshon" seems not taken into account here.

sudo aura -A packer --ignore jansson
aura >>= Determining dependencies...
aura >>= Repository dependencies:
jansson
jshon

aura >>= Main AUR packages:
packer

aura >>= Continue? [Y/n] y

Failed :(
Same comment as above here.

Decide.

[kwpolska@kwpolska-lin ~]% aura -Au
aura >>= You have to use `sudo` for that.
[kwpolska@kwpolska-lin ~]% sudo aura -Au
[sudo] password for root: 
aura >>= You should never build packages as the true root. Are you okay with this? [y/n] ^C%
[kwpolska@kwpolska-lin ~]% 
[kwpolska@kwpolska-lin ~]% sudo visudo
[`Defaults targetpw` disabled]
[kwpolska@kwpolska-lin ~]% sudo aura -Au
[sudo] password for kwpolska: 
aura >>= You should never build packages as the true root. Are you okay with this? [y/n] ^C%

The AUR wrapper yaourt has a feature that if /var/lib/pacman/db.lck exists, it does not quit with an error, instead it waits for /var/lib/pacman/db.lck to be removed, and then continues as if nothing has happened. Sometimes I run several package builds in parallell to get it done faster, or install a package while another one is building, and adding this feature would save a lot of time in these cases.

Does aura support bash/zsh completion? I can't find it in the docs or the manpages. I personally use zsh and I'd love to have completion enabled.

There seems to be problem with makepkg invocation and its environment. I have MAKEFLAGS="-j2" but it is being ignored when building through aura.

It'd be very handy if you can type

$ aura <search pattern>

and get matching packages from aur and the repositories. You can then choose the ones to install by their numbers. (This feature of yaourt is worth considering. It makes finding and installing new packages very easy.)

[kwpolska@kwpolska-lin ~]% aura -A pkgbuilder
aura >>= You have to use `sudo` for that.

Sure, will do.

[root@kwpolska-lin kwpolska]# aura -A pkgbuilder
aura >>= You have to use `sudo` for that.

WTF? I am root, I can do EVERYTHING I want on this system!

You don’t always need it, and a more generic root message would be better (some people hate sudo for some reason or don’t have it installed).

[kwpolska@kwpolska-lin ~]% time sudo aura -A pkgbuilder
aura >>= Determining dependencies...
aura >>= Main AUR packages:
pkgbuilder

aura >>= Continue? [y/n] y
aura >>= Building `pkgbuilder`...
aura: pkgbuilder-2.1.4.3-1-any.pkg.tar.xz: rename: unsupported operation (Invalid cross-device link)
sudo aura -A pkgbuilder  2.12s user 0.76s system 17% cpu 16.089 total

Broken. With everything I tried. That “determining dependencies” stage was taking ages for me before. Also, showing makepkg output may be vital to your success. A default of y for the Continue prompt may be a good idea, too.

If my shell was dumber (that isn’t the case with bash nor zsh), my shell would be green. And I do not like that.

[kwpolska@kwpolska-lin ~]% aura -Ah
aura >>= Conflicting flags given!

How am I supposed to know how to use aura, then? Read the manpage? It isn’t as easily discoverable as a help message.

When there are backslashes for line breaks in the dependencies of the PKGBUILD, Aura takes them as dependencies and requires "". For example (from ruby-rspec),

depends=("ruby" \
  "ruby-rspec-core>=2.11.0" "ruby-rspec-core<2.12" \
  "ruby-rspec-expectations>=2.11.0" "ruby-rspec-expectations<2.12" \
  "ruby-rspec-mocks>=2.11.0" "ruby-rspec-mocks<2.12")

I lost my network connection* before hitting “y” for Continue. And aura did some weird stuff.

(also, this inspired me to validate PB’s behavior, and it does a very human thing of telling the actual error and a human-friendly message.)

[kwpolska@kwpolska-lin testtest]% sudo aura -A pkgbuilder trashman
[sudo] password for root: 
aura >>= Determining dependencies...
aura >>= Main AUR packages:
pkgbuilder
trashman

aura >>= Continue? [y/n] y
aura >>= Building `pkgbuilder`...
aura: readProcess: curl "https://aur.archlinux.org/packages/pk/pkgbuilder/pkgbuilder.tar.gz" "-L" "--fail" "--silent" "--output" "/var/cache/pacman/pkg/pkgbuilder-6884/pkgbuilder.tar.gz" (exit 6): failed
[kwpolska@kwpolska-lin testtest]% sudo aura -A pkgbuilder trashman
aura >>= The following are not packages:
pkgbuilder
trashman

aura >>= Determining dependencies...
aura >>= Dependency checking failed for these reasons:
No AUR packages specified for install.

[kwpolska@kwpolska-lin testtest]%

New major feature.

Every name and version of currently installed packages will be saved in a file upon using the --save option. Running --restore will present a choice of which saved state to revert to, and then attempt to downgrade to those versions via packages in the cache. Installed packages that weren't installed at the time of the save will be removed.

This is important because it can sometimes be useful to rollback the overall state of installed software on one's machine, perhaps after a large upgrade breaks something.

This is due to switching out regex-posix with regex-pcre. This is a bug in pcre. I sent a bug report to the maintainer and am waiting for a reply.

Everything is in the title: "aura -Ss", and of course "aura -As" shouldn't need any root privileges.

Users on the Arch Forums have reported that this isn't working.

For people who have slow internet and don't want to be cloning git hub repos over and over. This request comes from zxo0oxz on reddit.

I wonder which ones? My method for animating pacman is pretty reliant on manually moving the cursor around. If the terminal is ignoring that I don't really know what else to do.

[kwpolska@kwpolska-lin ~]% pkgbuilder -S spacechem 
==> Building spacechem...
  -> games/spacechem 1012-2 (24 votes)
  ->     an obscenely addictive, design-based puzzle game about building machines and fighting monsters in the name of science!
==> Downloading the tarball...
  -> 1.695 kB downloaded
==> Extracting...
  -> 4 files extracted
==> Checking dependencies...
  -> sdl: found in system
  -> mono: found in system
  -> sdl_image: found in system
  -> sdl_mixer: found in system
  -> xclip: found in system
==> Making package: spacechem 1012-2 (Thu Sep 20 18:00:22 CEST 2012)
==> Checking runtime dependencies...
==> Checking buildtime dependencies...
==> Retrieving Sources...
  -> Found spacechem.sh
  -> Found spacechem.desktop
==> Validating source files with md5sums...
    spacechem.sh ... Passed
    spacechem.desktop ... Passed
==> Extracting Sources...
==> Starting build()...
==> You need a full copy of this game in order to install it
==> Searching for spacechem_1012_amd64.tar.gz or SpaceChem-1012.tar.gz or spacechem-linux-1345144627-amd64.deb in dir: "/tmp/pkgbuilder-1000/spacechem/src"
==> ERROR: Game package not found, please type absolute path to spacechem_1012_amd64.tar.gz or SpaceChem-1012.tar.gz or spacechem-linux-1345144627-amd64.deb (/home/joe):

Now, let’s try the same with aura.

[kwpolska@kwpolska-lin ~]% sudo aura -A spacechem
aura >>= Determining dependencies...
aura >>= Main AUR packages:
spacechem

aura >>= Continue? [y/n] y
aura >>= Building `spacechem`...
aura >>= Well, building `spacechem` failed.
aura >>= Dumping makepkg output in 3.. 2.. 1..
==> You need a full copy of this game in order to install it
==> Searching for spacechem_1012_amd64.tar.gz or SpaceChem-1012.tar.gz or spacechem-linux-1345144627-amd64.deb in dir: "/var/cache/pacman/pkg/spacechem-6499/spacechem/src"
==> ERROR: Game package not found, please type absolute path to spacechem_1012_amd64.tar.gz or SpaceChem-1012.tar.gz or spacechem-linux-1345144627-amd64.deb (/home/joe):
==> ERROR: A failure occurred in build().
    Aborting...

==> Making package: spacechem 1012-2 (Thu Sep 20 18:02:57 CEST 2012)
==> Checking runtime dependencies...
==> Checking buildtime dependencies...
==> Retrieving Sources...
  -> Found spacechem.sh
  -> Found spacechem.desktop
==> Validating source files with md5sums...
    spacechem.sh ... Passed
    spacechem.desktop ... Passed
==> Extracting Sources...
==> Starting build()...

aura >>= Some packages may have built properly.
aura >>= Would you like to install them? [y/n] 

Now, that is not right. And this is not easily discoverable. (it failed immediately when the read was done)

Now, I am aware of -Ax. It works. But then I tried to quit. I had to hit ^C three times. THREE. This is too much.

[kwpolska@kwpolska-lin ~]% sudo aura -Ax spacechem
aura >>= Determining dependencies...
aura >>= Main AUR packages:
spacechem

aura >>= Continue? [y/n] y
aura >>= Building `spacechem`...
==> Making package: spacechem 1012-2 (Thu Sep 20 18:11:28 CEST 2012)
==> Checking runtime dependencies...
==> Checking buildtime dependencies...
==> Retrieving Sources...
  -> Found spacechem.sh
  -> Found spacechem.desktop
==> Validating source files with md5sums...
    spacechem.sh ... Passed
    spacechem.desktop ... Passed
==> Extracting Sources...
==> Starting build()...
==> You need a full copy of this game in order to install it
==> Searching for spacechem_1012_amd64.tar.gz or SpaceChem-1012.tar.gz or spacechem-linux-1345144627-amd64.deb in dir: "/var/cache/pacman/pkg/spacechem-12460/spacechem/src"
==> ERROR: Game package not found, please type absolute path to spacechem_1012_amd64.tar.gz or SpaceChem-1012.tar.gz or spacechem-linux-1345144627-amd64.deb (/home/joe):
^C
Session terminated, killing shell...
==> ERROR: TERM signal caught. Exiting...
^C ...killed.
aura >>= Well, building `spacechem` failed.
aura >>= Some packages may have built properly.
aura >>= Would you like to install them? [y/n] ^C%                                                                                                                                                                                           

(% is printed, with reversed colors, when a command ended execution without a \n. This becomes a # as root, and it represents the prompt that would normally get printed there if you used a dumber shell (bash/sh).

Also, about that “built properly” thing, it would be a good idea to show a list of those packages and ignore it altogether if empty.

-- This should be at ~/.config/aura/aura-conf.hs
-- How do I get it there? And what about `.pacnew`s?

This is how I do it in PB and Trashman*, and how 99% of the universe does that:

1. check if ~/.config/, ~/.config/aura/ exist. If not, create. Bonus points if you check the env variable XDG_CONFIG_HOME and work according to it, falling back on ~/.config/.
2. check if ~/.config/aura/aura-conf.hs exists. If not, copy over from an existing file somewhere in the system (I suggest somewhere like /etc/)
3. Finally, read the file. Bonus points if you use /etc/ as a global config file.

Also, I don't think you need to bother with pacnews, but if you do, man PKGBUILD.

* I actually do XDG_CONFIG_HOME/kwpolska/{pkgbuilder,trashman}.

Hello,

I have a problem when using aura:
If I update a couple of AUR Packages, and something goes wrong in the later packages (so the first few have already been build, but not installed), aura will fail to install these already build packages, instead aborting with:
"""
aura >>= Building caledonia-bundle...
aura >>= Well, building caledonia-bundle failed.
aura >>= Dumping makepkg output in 3.. 2.. 1..
==> ERROR: A package has already been built. (use -f to overwrite)

aura >>= Also, the following weren’t built:
something more...
"""

I think in this case, aura should just install that package.

Thank you!

aura -Ad xmobar-git gives very strange output for the Pacman deps.

Need to do some studying before that happens though.

GPL, baby.

When I build this using packer it builds and installs both dolphinviewer and lib32-pangox-compat successfully. Aura throws an error instead of building lib32-pangox-compat.

$ sudo aura -A dolphinviewer
aura >>= Determining dependencies...
aura >>= Main AUR packages:
dolphinviewer

aura >>= Continue? [Y/n]
aura >>= Building dolphinviewer...
aura >>= Well, building dolphinviewer failed.
aura >>= Dumping makepkg output in 3.. 2.. 1..
==> Making package: dolphinviewer 3.4.3.26620-1 (Mon Nov 19 11:47:15 EST 2012)
==> Checking runtime dependencies...
==> Missing Dependencies:
-> lib32-pangox-compat
==> Checking buildtime dependencies...
==> ERROR: Could not resolve all dependencies.

Need to learn how to write one.

aura >>= Building `boost.process`...
chown: cannot access ‘/var/cache/pacman/pkg/boost.process-14850/boost’: No such file or directory
aura: readProcess: chown "-R" "colin" "/var/cache/pacman/pkg/boost.process-14850/boost" (exit 1): failed

or

aura >>= Building `gstreamer0.10-good-plugins-slim`...
chown: cannot access ‘/var/cache/pacman/pkg/gstreamer0.10-good-plugins-slim-15050/gstreamer0’: No such file or directory
aura: readProcess: chown "-R" "colin" "/var/cache/pacman/pkg/gstreamer0.10-good-plugins-slim-15050/gstreamer0" (exit 1): failed

This feature request is influenced by my usage of yaourt, but I think it's a good feature.

Currently, any update is found, but only the new versions are displayed.
Here is an example (knowing that I still use the old version of ibus).

aura -Syu

:: Starting full system upgrade...
resolving dependencies...
looking for inter-conflicts...

Targets (4): ibus-1.4.99.20121109-1  ibus-pinyin-1.4.99.20120808-1  ibus-table-1.4.99.20121112-1  pyzy-1.0-1

Total Installed Size:   16.04 MiB
Net Upgrade Size:       -23.74 MiB

Well, this is basically pacman's output.

Here is what yaourt gives:
yaourt -Syu

==> Software upgrade (new version) :
extra/ibus            1.4.2-2          -> 1.4.99.20121109-1
community/ibus-pinyin 1.4.0-2          -> 1.4.99.20120808-1
community/ibus-table  1.3.9.20110827-1 -> 1.4.99.20121112-1

==> New package :
community/pyzy        1.0-1            (required by ibus-pinyin)

==> Continue upgrade ? [Y/n]
==> [V]iew package detail   [M]anually select packages
==> --------------------------------------------------

It gives way more informations:

1. it has colours
2. Upgrades are divided into sections (new revisions & new versions)
3. each repo is displayed
4. we clearly see that a new package will be installed, since needed by the upgrade of another one.

Therefore, I would like to ask if this could be done in any way. I have not written anything about the last two lines, because I think they are useless.

Need to connect to the AUR using it's API and JSON. This should speed up -Au significantly.

This would make it consistent with pacman behaviour.

Just type aura -As pkgbuild and you'll see what I mean.

There must be some regex magic to easily fix this.

Aura should be using a Haskell library for internet connection.

I think it's far more important for users to learn what is going on in AUR conceptually, 
and to get into a habit of checking/researching what they are installing, 
than to be forced to download a PKGBUILD manually and run "makepkg" 
(since those are rather trivial things to grasp). So I think the way forward is to think of functionality 
that will make this conceptual understanding easier and encourage it, 
rather than sacrificing convenience. 

The man has a point.

$ makepkg -s
==> Making package: aura 1.0.3.1-1 (Wed  7 Nov 19:10:12 GMT 2012)
==> Checking runtime dependencies...
==> Checking buildtime dependencies...
==> Retrieving Sources...
  -> Downloading aura-1.0.3.1.tar.gz...
  % Total    % Received % Xferd  Average Speed   Time    Time     Time  Current
                                 Dload  Upload   Total   Spent    Left  Speed
100   133  100   133    0     0     24      0  0:00:05  0:00:05 --:--:--   302
100 54737  100 54737    0     0   5124      0  0:00:10  0:00:10 --:--:--  473k
==> Validating source files with md5sums...
    aura-1.0.3.1.tar.gz ... Passed
==> Extracting Sources...
  -> Extracting aura-1.0.3.1.tar.gz with bsdtar
==> Removing existing pkg/ directory...
==> Starting build()...
Configuring aura-1.0.3.1...
Setup: At least the following dependencies are missing:
curl -any, json -any, regex-pcre -any
==> ERROR: A failure occurred in build().
    Aborting...

$ cabal install curl json regex-pcre
Resolving dependencies...
All the requested packages are already installed:
curl-1.3.7
json-0.7
regex-pcre-0.94.4
Use --reinstall if you want to reinstall anyway.

(Reinstalling the packages makes no difference.)

Does anybody know what I'm doing wrong?

Make this tail call? There should be a way to show what packages actually succeeded. 返って, no message should be shown if no packages were built before the fail.

When you find a package that didn't build, please explain how the building failed. Thank you!
Here they are:

UNSOLVED (as of 2018 June)

Currently there are no reported unbuildable packages with the aura-1.5 branch.

New major feature.
When performing a -Au, PKGBUILDs will now be saved. When ran with a new suboption, a diff will be performed between the new PKGBUILD and the most recent one, and then outputted.

This is important because while the aura philosophy advocates thorough research into packages before initial installation, this becomes impossible (or just really long and annoying) when running a mass update with -Au.
With this new functionality, upon every update the user will be able to see what changes were made to the PKGBUILDs, and thus will notice if something is amiss.

pacman-color gives some nice colours when we search for a package, but aura doesn't use that version.

Even with "alias pacman='pacman-color' ", aura still uses the normal version.
It should integrate nicely with it.

Moreover, It would be better if the colours in -As could match the one of pacman-color (for the repo's colour, and add the right colour for the version number, the package name could also be in bold as with pacman-color).

This would bring more consistancy.