Arch Linux User Repository

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

My bad. Seems that i'm using an old version of aura. My version is 1.1.6.0-1. I will update my version.

Which version of aura? I am using curl 7.35.0 which aura 1.2.3.0 and I do not have this issue.

After a system update my aura stopped working. Any action with '-A' would get an error message. $ aura -As test aura >>= AUR API lookup failed. Please check your connection. If i execute the command bellow the problem disappear. $ sudo pacman -U /var/cache/pacman/pkg/curl-7.33.0-2-i686.pkg.tar.xz The problem happens with curl-7.34.0-1 and with curl-7.35.0-1. I'm the only one with this problem? I had put the curl in the IgnorePkg of the /etc/pacman.conf for now. Sorry for any mistakes, english isn't my mother tongue.

For c0rtex It happent when you are in aterminal in a directory that doesn't exist (you deleted it with some file manager for example), so change the directory.

Found a bug: When pacman experiences a download error retrieving a dependency, aura continues to build the AUR package when it shouldn't.

I get this with version 1.2.2.0 and community repos: ==> Extracting sources... -> Extracting aura-1.2.2.0.tar.gz with bsdtar ==> Starting build()... Setup: The following installed packages are broken because other packages they depend on are missing. These broken packages must be rebuilt before they can be used. package json-0.7 is broken due to missing package syb-0.4.0-c48d52f3188b986ddaa9dd9ae40072f8 ==> ERROR: A failure occurred in build(). Adding the haskell-core repo fixed this for me

1.2.2.0 ------- - Happy New Year! - makepkg's `--ignorearch` flag is now visible to Aura. This allows users to build AUR packages on ARM devices without worrying about architecture restrictions in PKGBUILDs. - Use `--head` and `--tail` to truncate `-As` results. - `-B` now uses local time. - Bug fixes and translation updates

Deletion happens automatically. I have no control over it. However, I could copy the files out before deletion. I suppose the saved files could go in `/var/cache/aura`. Would you mind opening an Issue on github about this? It would be much easier to track.

Hi @fosskers, back in March I suggested: === Comment by trusktr 2013-03-24 22:49 Hi fosskers, I have a feature Request. When a build fails, sometimes the fix is simple, but Aura will start the build over from scratch, which can be annoying if the build takes an hour. Maybe you can give the user the option to try again instead of just quitting, keeping the build files (compiled files) intact for the next attempt so files that have already been compiled won't be compiled again. For example, I had a problem where a build failed due to a missing lib.so file because the file was installed in /opt/package-name/lib instead of /usr/lib/ by it's dependency... To fix the problem, I created a symlink in /usr/lib/ to the file in /opt/package-name/lib/, but it was annoying because compiling the source took a half hour before the error was encountered, so I had to wait a half hour re-compiling only to encounter another missing .so file, so I symlinked it, then started over again, hoping for no more errors... Ideally, instead of quitting, maybe aura can do something like "Build failed. Try again? [y/n]", and that way, before I try again, I can go into another terminal and fix the problem, then try again, and aura won't have to re-compile everything for a whole hour (literally). Aura can keep the build environment intact until the user selects not to continue. Maybe you can create a setting that users can set in a config file for aura (.aurarc?) telling aura not to erase temporary files when it quits, so that if you try installing a package again, it does not have to re-compile the whole thing again. And to make things even better, maybe provide a command line flag to that would tell aura to clear all temporary files. I believe that if the build process pulls new code (e.g. using git), that the make process will only re-compile files that have changed, so this should work. Can you add something like this to Aura? === and you replied with === It seems you've put some thought into your request and I thank you for that. How would this be handled manually? Say you were building something big and had all the source you downloaded yourself. The build fails partway through. You try again. Where does that second build start? Does it recognize a good part of the work is already done? (I imagine this depends on the build system) It if does, then I could implement this into Aura. If it doesn't, then I wouldn't even know where to begin. At the moment everything is done in temporary folders. When the build is complete, the .pkg.tar.gz is moved to the cache and everything else is automatically deleted. This could be changed, if the answer to my above question is that it's possible. === I don't know if you've done anything about this recently, but I have an idea. Does aura have a config file? ~/.aurarc or something? If not, then a command line setting could suffice. But my idea is that there be a setting/command option that prevents aura from deleting the temporary files. In most cases, things are compiled using make which reads a makefile. You can keep track of tmp folders somehow (e.g. placing a flag in the folder with the name of the package so if you are installing something with aura and it sees a folder for the package you are installing then use that folder instead of making a new one) so if you leave those files in tact, make will handle the rest and would not recompile things if not necessary. So basically, this is what you'd have to implement: if using this new "save temporary folder" option, then aura would store the name of the package in the temp folder. e.g. when I do "sudo aura -A whatever", then aura would check all the temp folders made by aura to see if there's already one for the "whatever" package. If one exists, aura would not make a new one, else if it doesn't exist, aura would make a new one. You could also add a "clear temporary folders" option so the user can have aura automatically delete temporary folders on demand. That's all you'd need to do. The rest would usually be handled by the user's build system (e.g. make will no recompile if not necessary).