Arch Linux

Well, that's good to know.

I tried it, and aurbuild seems to work with Haskell packages.

I'm not exactly sure what feature related to provides you require.
Could you describe your requirements in greater detail?
There are some features that may be challenging because of the implementation
of the AUR itself which I'd hope to change (some day).

Please try out aurbuild and if it doesn't meet your needs please let us know.

Does aurbuild support "provides"? This is a big issue with yaourt and Haskell packages, and the developers are telling us "yaourt is entirely broken with Haskell packages".
http://haskell.org/haskellwiki/Arch_Linux/Preferred_Package_Tools

Ok, it's not an aurbuild bug. I opened another PKGBUILD from my local ABS tree and got the same issue. The reason was the file /usr/share/nano/arch.nanorc for syntax highlighting of the PKGBUILDs. After disabling it works again.

There are no error messages. Which program or script shall I debug?

Can you provide some error messages or backtrace?
I cannot reproduce this. What package are you trying to build?

Since the latest nano update to nano 2.2.0 aurbuild doesn't work with nano anymore. If a file like a PKGBUILD is opened with the menu entry 1 e.g. the menu is still displayed, the cursor is shown at the top left position of the screen and nothing happens, either aurbuild, python or nano crashes. nano and aurbuild have to be killed by root.

This is because that PKGBUILD uses undefined functions and aurbuild sources
the PKGBUILD when you confirm that you want to build it.

Actually, those functions are defined in makepkg itself.
I'm not really sure if they're meant to be accessed within the PKGBUILD itself.

Thanks for the report. I'll look into fixing it.

I tried to install chromium-browser-bin, but got the following error messages.

PKGBUILD error:
/var/tmp/aurbuild/build/chromium-browser-bin/chromium-browser-bin/PKGBUILD: line 37: msg: command not found
/var/tmp/aurbuild/build/chromium-browser-bin/chromium-browser-bin/PKGBUILD: line 40: msg2: command not found
/var/tmp/aurbuild/build/chromium-browser-bin/chromium-browser-bin/PKGBUILD: line 43: devel_update: command not found

Then I used yaourt and everything worked fine. Also, doing it by hand using makepkg worked.

Yeah cyberpatrol, that's on the TODO list...
but it's a pretty low priority for me right now.
If you can provide a patch though I will gladly review it.

-v1.8.8 (July 6, 2009)
* Fix app detection
* Fix searching and installing packages named with a plus sign.
* Change menu options and add save option.

I think, I found another issue.
aurbuild seems to look for missing dependencies only in the repos, but not in AUR.
See the package virt-manager, which needs libvirt and virtinst from AUR.

It would be nice, if aurbuild would also install dependencies from AUR.

> Ah you're just saying you don't like that behaviour.

Not quite. I was wondering, why it shows one of the files instead of the menu, which asks me, if I want to view one of the files or not. So I thought it could be a bug. Didn't know, that this was intentionally.

As I now know your intention, I can happily live with it. I usually look at the files anyway. ;-)
I don't know, if a switch to disable it is necessary.

> What package are you installing that doesn't show the install file the first time?

I didn't pay attention, which file was displayed. As I recall correctly it was sometimes the PKGBUILD and sometimes - in most cases - the install file, but I can be mistaken. I need to watch it during the next package updates. If a different file than the install file will be displayed, I'll tell you, which package it was.

When I saw, that there was no file opened for the first package but for the second, I installed `aurbuild -s xf86-video-ati-git xf86-video-radeonhd-git`. I just looked at the packages again and found out, that xf86-video-ati-git doesn't have an install file. So the behaviour was correctly and intentionally.

Maybe I was just a bit confused. ;-)

Ah you're just saying you don't like that behaviour. Maybe I could add a switch to disable it.
aurbuild will actually prompt for an EDITOR now, and use `less` if you have nothing to say about it.

What package are you installing that doesn't show the install file the first time?
Remember, the editor is only started if there's an install file.
What's the first package in your updates?

> Just quit nano, then the menu will show.
I know. ;-)

> If anything other than an install file is automatically displayed, then something is weird.
I'll have a look at it.

> Install files will always be displayed if present, so you can ensure there are no nasty commands.
I'm not quite sure, if I always want to see the .install file, because there are some (not all) packages and maintainers, which I suppose to be trustworthy.

Btw., if I install a package for the first time by running `aurbuild -s <packagename>` the menu is shown at once without opening nano for the first package.
And if I recall correctly, the menu is also shown instead of the editor, if $EDITOR is not set.

But as I've written it's a minor issue. It's up to you. ;-)
I just wondered.

Just quit nano, then the menu will show.

Install files will always be displayed if present, so you can ensure there are no nasty commands.
If anything other than an install file is automatically displayed, then something is weird.

I have a new minor issue with aurbuild.

I added 'alias aurbuild="sudo env EDITOR=\$EDITOR aurbuild"' to ~/.bashrc.

If I now run `aurbuild -su`, it asks me to update a package, and I press Enter (for Y), then it downloads the package, but opens one of the package files (PKGBUILD, *.install or whatever) in nano instead of showing the menu.

Adding user root to group abs helps. Thanks.

Alright, that's telling...
Adding root to the abs group solves the problem.
I think this may be a bug in fakeroot.

It isn't properly checking user groups and using those
permissions before becoming the fake root user.

Hmm I'll try to look into it.

I've been able to reproduce it though.
Things seem to work properly when running makepkg as aurbuild manually.

When entering fakeroot, everything becomes root:root, so that's where it
may be coming from.

If you can figure anything else out that would be appreciated.

I've got a problem with aurbuild. I can compile the sources of an AUR package, but I can't build the packages.
I'm always getting this error message:

==> Creating package...
-> Generating .PKGINFO file...
-> Compressing package...
bsdtar: Failed to open '/var/cache/pacman/pkg/gtk-theme-shiki-colors-murrine-4.0-1-x86_64.pkg.tar.gz'
==> ERROR: Failed to create package file.
aurbuild: could not build gtk-theme-shiki-colors-murrine with makepkg.
Build directory retained at /var/tmp/aurbuild/build/gtk-theme-shiki-colors-murrine
You can visit the directory, fix the problem, and run makepkg.

The access rights for the directory /var/cache/pacman/pkg are root:abs 775, and I've put the user aurbuild into the group abs.
Is there a way, how to fix this?

Thanks! Great job.

Everything OK now.

-v1.8.7 (March 29, 2009)
* Fix building official packages.
* Fix building packages when the save path doesn't exist.

Also, I cant use aurbuild -sf

#aurbuild -sf mysql
Traceback (most recent call last):
File "/usr/bin/aurbuild", line 1078, in <module>
val = main()
File "/usr/bin/aurbuild", line 841, in main
if aurpkg and UPGRADE:
UnboundLocalError: local variable 'aurpkg' referenced before assignment

The problem is with packages which have been deleted from aur.
With previous version I get a
"Package foo: not found in AUR"
now it stops with this error.

If i create the directory /var/tmp/aurbuild/pkgbuilds, I get a "No result found" for packages not in aur and aurbuild continues normally.

You can temporarily work around that bug by creating the directory.
I will look into making a proper fix though.

When I try to aurbuild -su, I get a few results (up to date) and then it stops with
"No result found
Error: /var/tmp/aurbuild/pkgbuilds not found or read permissions denied."

woot! upgrade is _really_ fast now!! :D
great work!

Try that one. :D
Upgrade should be a little faster too now.

-v1.8.6 (March 18, 2009)
* Compensate for bad URLPath when fetching tarballs.
* Support multiple search terms.
* Reduce indent in search output formatting.

Ah I found the problem with 'not a gzip archive'.
For some packages the URLPath is wrong:

"URLPath":"\/packages\/tomatoes\/tomatoes-1.55-8.src.tar.gz"

Latest release fixes the search bug.

-v1.8.5 (March 17, 2009)
* Rework PKGBUILD retrieval code.
* Prompt for editor if EDITOR isn't defined.
Use less if the specified editor isn't found.
* Update searching to use the JSON interface.
* More code reorganisation and clean up.

I contacted the developer to report a bug and was told this application is no longer under development. Just as a note to anyone else who ends up here. I recommend aurpac as a replacement, as it is fast and simple like aurbuild but uses the same general syntax as pacman. Another option is yaourt, but it is too slow and cumbersome for me.

please, use this link for report a new bug
http://developer.berlios.de/bugs/?group_id=7176
hello

Search is broken for me now. I believe recent AUR site changes have confused the code that scrapes the website. The error message I receive is below:

username@machine:~$ aurbuild -S packagename
list index out of range

And I receive this for anything I search for.

Whats the reason to add one more deped in aurbuild?
If you dont want to log in as root, maybe you should try
su -c 'aurbuilb -su'

Then I ask for implementing a json interface in aurbuild.

I think putting pacman into sudoers is not such a big deal. I have it in there anyway, because I usually don't want to login as root, when I'm online. And so I have to add both pacman and aurbuild to sudoers.

Yeah the problem is that aurbuild is scraping the html for info and the out of date packages are throwing it off. Changes in the markup are also the reason it's failing to show package descriptions.

The ideal fix would be to use the json interface for the search.

When you run aurbuild as root it doesn't actually run makepkg as root. It creates a special aurbuild user to run makepkg, so running aurbuild with root privileges is pretty safe. It should be even safer than running as your regular user because your data is safe as well.

Yeah it would be nice if you could run as a regular user and have it change to the special user for building, but that would still require set up of sudo. I guess it could install aurbuild as setuid, setgid aurbuild perhaps.

aurbuild doesn't find every package in AUR.

$ aurbuild -S qdvdauthor
unsupported/qdvdauthor-templates 1.0.0-1 (multimedia)

It should also find the package qdvdauthor.

$ aurbuild -S arson
arson: search results empty

But there is a package arson in AUR.

And it should be possible to run aurbuild as unprivileged user to install a package.

$ aurbuild -su
requires root access.

Instead it should be possible to run aurbuild -su as an unprivileged user. aurbuild should then call pacman with sudo to install the dependencies and the built packages, because running makepkg as root is not recommended.

Huh? Are you using yaourt or something?
Try this:
pacman -U ftp://ftp.berlios.de/pub/aurbuild/aurbuild-1.8.4-1-any.pkg.tar.gz

Or see http://aurbuild.berlios.de

*I am getting this error when trying to install
Downloading 1.8.4-1 PKGBUILD from AUR...
Error: 1.8.4-1 not found in AUR.

Thanks for the report SickHate.
That's a known limitation. aurbuild can't easily build/install dependencies from AUR yet. I do plan on adding that feature in the next couple of releases.

Cheers!

aurbuild fails to search packages on aur..


Enter a selection: [B]
==> Checking Buildtime Dependencies...

==> Checking Runtime Dependencies...

- libglade: ok [D]
- perlxml: ok [D]
- revel: missing [D]
revel: not found in ABS

and revel its on aur...

Hey Ho. New 1.8.4 Release out now!
Please see
http://developer.berlios.de/project/shownotes.php?release_id=14503

Also, the aurbuild repo has moved to ftp://ftp.berlios.de/pub/aurbuild
Please update your pacman.conf

Cheers!

Hi there I did some digging and I figured out an easy way to pass the EDITOR variable through sudo and use aurbuild.

Issue this command:
sudo env EDITOR=$EDITOR aurbuild <whatever>

To make this easy for every day use make a bash alias:
alias aurbuild="sudo env EDITOR=\$EDITOR aurbuild"

And you're good to go!

Yeah I wouldn't support running aurbuild as a regular user necessarily.

You should be running aurbuild with root or root permissions from the start. Unless it's just for searching or something.

Another way that would be nice is with sudo `sudo aurbuild <arguments>`. Unfortunately this method doesn't work right now and I can't vouch for it's stability/security.

If you ran aurbuild as a regular user and there was a problem with the PKGBUILD then it might clobber your home directory. You don't want that to happen I assume?

One possibility where it could work is if your user has permissions to become the 'aurbuild' user. That would be alright I think.

Just clarifying what I meant by 'added to TODO'
Cheers.

@maci: I disagree. This was in fact the way aurbuild used to run: Build the package as the underprivileged user than call on sudo to install the package.. and a few other need operations. The way aurbuild works now is that it must be run as root user. This way when it comes time to build the package, it drops down into the underprivileged aurbuild user and back to root to install the package. The nice thing about this is that the other root required operations (think of storage, package retrieval and build preparations) do not need to be configured for sudo. Again, aurbuild drops down to an underpriviledged build user when it comes time to build the package so there is no real danger the way it is setup now.

@louipic: If the editor variable is not showing up while calling on aurbuild by sudo, search the forums. There was at one point an upgrade to sudo that lost some variables when called upon.

Cool I've added it to the TODO list.
One of the problems right now is that the $EDITOR variable isn't recognised. If you have any ideas on how to solve that please let me know. Thanks!

excelent tool!

but aurbuild should use sudo to install the packages instead of requireing to be root all the time

New release, new webpage, new repo!?

See http://aurbuild.berlios.de
and
http://developer.berlios.de/project/shownotes.php?release_id=14405

aurbuild does not work correctly with packages which have "arch=('any')" (for instance biblatex, emacs-planner, emacs-remember, etoolbox..)

Over forty patches in this release. The codebase is a bit bigger than it should be because a lot of functions were copied to aurbuild.utils but haven't been fully implemented yet.

The main script is a smaller.

-v1.8.2 (March 4, 2008)
* Fancy new search output
* Fixed bug that prevented --sync from working properly
Package repo database wasn't being found. (moved in pacman 3.1.0)
* Disabled --vote and --unvote again
* Moved a bunch of functions out of the main script
* Fix bug that makes builddeps fail if the package has been previously
built by aurbuild
* Got rid of annoying pkgname.pid dirs in /var/tmp/aurbuild/build
Now it's just /var/tmp/aurbuild/build/pkgname and it gets
overwritten if you try to build via aurbuild again.
* Remove makepkgv2 support
* Remove all uses of versionpkg. (makepkg has assimilated its function)
* --revision removed. It's made obsolete by makepkg
* Added BUGS file to help keep track of bugs
* Made more files in /var/tmp/aurbuild owned by aurbuild
rather than root

http://prdownload.berlios.de/aurbuild/aurbuild-1.8.1.tar.gz
-v1.8.1 (February 29, 2008)
* Fixed a lot of stuff in README and the man page
* Restored --auto-build and --upgrade
* --upgrade output shows versions and alerts to non-AUR foreign
packages.

PS: Thanks for the alert shining. I'll keep --asdeps in mind for future functionality

Penguin made that comment a while ago, but the answer is rather destined to louipc ;)

> This was a functionality removed from pacman
> itself in the 3.x series and thus removed from
> aurbuild. The only solution is to hack pacman's
> database which would be messy and dangerous.

3.1 now has an --asdeps flag.

http://download.berlios.de/aurbuild/aurbuild-1.8.0.tar.gz

Notes:
This release is to give the users *something* to work with while I figure out how to fix the rest of the app.

Changes:
-v1.8.0 (February 21 2008)
* Updates to make aurbuild compatible with AUR 1.5.0
* Cleaned up directory structure
* Tweaked setup script, and some other files (more to come)
* Added aurbuild's own PKGBUILD to misc/
* Removed safe flagging notices and checks.
(Removed from AUR web interface)
* Temporarily removed --vote --unvote --upgrade and --auto-build

Additional notes:
There's a PKGBUILD in misc/ to help build the pkg
just move to that directory and run makepkg

I'm making some good progress now. Have a look here:
http://git.louipc.dontexist.org/?p=aurbuild;a=summary

Hey folks. I just downloaded the aurbuild source code and I've just been hacking at it a bit cleaning things up here and there. I'll try to tackle a couple of the bugs and then I'll release the code for anyone who is interested to review it. I'm no expert so it'll be good if someone can spot any mistakes I might make. Cheers.

Hey there..

aurbuild -us is soooooooo slow these days.. is there a reason for that ? i have ~15 packages that has been installed from AUR via aurbuild..

Yeam, you're right.

No, it shouldn't.
It's not aurbuild's fault when some AUR PKGBUILDs have incomplete makedepends.
I'd even go so far to consider it mandatory that everyone wanting to build packages has at least the "base-devel" group installed. make and patch are of course included there.

And also a dependancy should be set to "patch" package.

It should depend on the make pkg.

I think this had something to do with the new sudo and not accepting environment variables by default. Search the user forums for the fix.

aurbuild doesn't see the EDITOR (or VISUAL) variables defined in .bashrc..?

I want to use VI but it doesn't see that choice and try nano instead..

This was a functionality removed from pacman itself in the 3.x series and thus removed from aurbuild. The only solution is to hack pacman's database which would be messy and dangerous.
Unfortunately, I'm no longer maintaining this project and don't have arch installed to even try anything. There are several aur building tools out there (yaourt) actively maintained you may be happier with.
As always I'm willing to accept patches and even hand over the project to someone else better fit, just shoot me an email.

I usually do aurbuild -surm to update packages from aur that I install with aurbuild. I noticed that when aurbuild installs make dependencies (i.e. swig and guile for museek-svn) it installs them explicitly (instead of as dependencies). This makes sense b/c they aren't really dependencies, but if aurbuild crashed, or there was a problem and I had to kill aurbuild, then wouldn't the make dependencies stayed installed?

Also, if I didn't use the -m option to remove uneeded make dependencies after aurbuild is done running, and I later decided to remove a package, how do I easily remove the make dependencies as well if they aren't tagged as dependencies?

If make dependencies installed by aurbuild were installed as dependencies (as orphans), I could just do pacman -Qe to remove any uneeded make dependencies

will there come out a new version of aurbuild that fixes this problem? Its really annoying...

The man page shows -S to unvote, it should be -U.

it means you probably built that package manually as root once before or as some other user. chown it aurbuild:aurbuild and it should work. This is the problem with the new makepkg. I can no longer have aurbuild build the package in a writable directory using -w THEN move it to PKGDEST because its been removed (actually there is a way but it would require a messy hack to be backwards compatible with makepkg v2).
If it makes it any more convenant, you should be able to build any package with aurbuild using the regular switches or --official. Just make sure the PKGBUILD is in /var/abs. Otherwise follow behind yourself using chown..

it happens on every package :P

tar: /home/k0cAin/ArchLives/keepassx-0.2.2-3-i686.pkg.tar.gz: Cannot open: Permission denied
tar: Error is not recoverable: exiting now

gzip: stdout: Broken pipe
tar: /home/k0cAin/ArchLives/keepassx-0.2.2-3-i686.pkg.tar.gz: Wrote only 4096 of 10240 bytes
tar: Error is not recoverable: exiting now
==> ERROR: Failed to create package file.

aurbuild: could not build \"keepassx\" with makepkg.
build directory retained at `/var/tmp/aurbuild/build/keepassx.7920\'
In some cases you may be able to cd into the directory, fix the problem and run makepkg with success.

ok, found the problem. Thanks for your help! (By the way: aurbuild is a great tool, gook work!)

there\'s probably something wrong with aur\'s tarball for the package it is evaluating to upgrade. Add:
print argo
below line 1077 to see which one it is.

I always get this error when doing a \"aurbuild -su\" as root:

[root@localhost aurbuild]# aurbuild -su
Editor environmental variable not set. Using nano...
aurbuild......................................up2date

could not extract tarfile: not a gzip file

At the beginning this worked, suddendly it doesn\'t anymore. (Maybe due to the upgrading of fakeroot?)

Anyone knows what to do?
Cheers
Jan

it got my vote :D its a GREAT app...keep up the good work

First of all, thanks for this indispensable app.

I would suggest that, when doing a -su, aurbuild should interpret every -svn pkg to be newer than installed version and ask for an update.

-v1.7.8 (March 29, 2007)
* USE_FAKEROOT fix due to makepkg v3
* USE_COLOR fix due to makepkg v3
* lost PKGDEST due to makepkg v3

i found the little bug for PKGDEST problem.

it was in def_getpkgpath(), this line:

if os.path.exists(v2_pkgpath):
pkgpath = v2_pkgpath
-->> elif os.path.exists(v2_pkgpath):
pkgpath = v3_pkgpath
else:
:: some error\'s string ::

change elif os.path.exists(v2_pkgpath): in elif os.path.exists(v3_pkgpath)

it should be work ;)

I agree with sickhate.

i allready had tryed that...but its better to ajust it to the new pacman

simple workaround for last questions:

echo \"USE_FAKEROOT=y\" >> /etc/makepkg.conf

USE_FAKEROOT variable in /etc/makepkg.conf is not set to \"y\". Refusing to proceed.



same here.

here too ;)

pacman3 has released into testing repo. I think it\'s necessary to change into the new style makepkg.conf which uses BUILDENV setting instead of USE_FAKEROOT now. :)

doing what I can..

AURBUILD
-v1.7.7 (March 24, 2007)
* Fixed lost permissions in AUR tarball.

When using aurbuild to build nspluginwrapper on my Arch64 system, it does not set permissions for downloaded files. There is a shell script which is needed by nspluginwrapper but was not set to chmod +x after it was downloaded by aurbuild, and therefore the build failed.

\"Looking for aurbuild developers\" - http://bbs.archlinux.org/viewtopic.php?id=30809

i tryed it, but is the same.....
and another thing, i have python2.5, and when i type makepkg for install aurbuild, it says that it want python2.4 :-| (I changed the pkgbuild for install it)

Galdona: it should be ok to alias it like that as long as you use that alias for build operations only.

brainwasher: PKGDEST variable is set in makepkg.conf. You need to set it to something valid and ensure it has write and execute rights to aurbuild user or group. This is all documented in the man page.

i ve the latest version, but with all package i have this :

Error: could not find the built package.
In some cases this might mean the PKGDEST location does not have write and execute permissions
for the `aurbuild\' user or group.

i look into /var/tmp but seems all ok, i tried also to remove /var/tmp/aurbuild but is the same...

Is it okay to alias \"aurbuild\" to \"aurbuild -m\" in .bashrc ?

-v1.7.6 (March 3, 2007)
* Fixed failed C compliler checks during .configure due to an unwritable HOME location for ccache. HOME will be passed as
/var/tmp/aurbuild and thus ccache data will reside in /var/tmp/aurbuild/.ccache for aurbuilds.

$ cat config.log
This file contains any messages produced by compilers while
running configure, to aid debugging if configure makes a mistake.

configure:611: checking host system type
configure:632: checking target system type
configure:650: checking build system type
configure:705: checking for a BSD compatible install
configure:758: checking whether ln works
configure:782: checking whether ln -s works
configure:1867: checking for gcc
configure:1980: checking whether the C compiler (gcc -march=i686 -O2 -pipe ) works
configure:1996: gcc -o conftest -march=i686 -O2 -pipe conftest.c 1>&5
ccache: failed to create /home/dpc/.ccache (Permission denied)
configure: failed program was:

#line 1991 \"configure\"
#include \"confdefs.h\"

main(){return(0);}


Seems that everything gets clear. After removing ccache package from my system things are working again. The question is - what envs are still pointing at my user.

I\'m not able to reproduce the error from rlocate on my machine. Could you please post the relevant info from config.log?

Purch\'s problem is mine problem too.

checking whether the C compiler (gcc -march=i686 -O2 -pipe ) works... no

That was not happening before and is not one PKGBUILD specific problem.

dpc5:
I would love to use makepkg -w but unfortunately makepkg3 mindlessly removed that option. The work around is to set a PKGDEST environment variable before handing off to makepkg. The problem with this is makepkg2 does not except an environment PKGDEST variable, as it is overwritten once makepkg sources /etc/makepkg.conf.
Writing to a specified location can be done in both versions but it will required some hackish and potentially unreliable parsing to determine which version of makepkg we\'re using and I\'m not prepared to waste any more of time on it. Makepkg is becoming an obstacle to this program and its limitations are being reached because of it.

Sorry for my previous comment. Resolution was quite obvious and simple.

But - if aurbuild uses his own user - wouldn\'t be better if it use his own home dir to write destination packages? makepgk -w will probably do the job.

Did you build it with makepkg as user or root? If it only worked with root then its a PKBUILD issue.

Aurbuild wont work. See http://pastebin.archlinux.org/1754 for details.

I compiled rlocate successfully with makepkg in a users ~ /build/rlocate/

==> ERROR: Package destination directory does not exist or permission denied.

aurbuild: could not build \"geda-libs\" with makepkg.
build directory retained at `/var/tmp/aurbuild/build/geda-libs.6143\'
In some cases you may be able to cd into the directory, fix the problem and run makepkg with success.

added arch field.

arch field is missing.

-v1.7.5 (February 26, 2007)
* Fixed broken Maintainer field in --search due to AUR upgrade.
* Spelling corrections in manual page.

It seems that the data format of AUR has some little changes.

Here it is. When you use aurbuild -S somepackage, you\'ll see something like this:
Maintainer: <a href=\'packages.php?K=guital&SeB=m\'>guital</a>

I think the HTML code should be removed.

-v1.7.4 (February 10, 2007)
* Fixed permission errors while extracting the AUR tarball.
* Corrected message about needing write AND EXECUTE permissions on the $PKGDEST in main script and man page.
* Added -f, --official to build official packages found in /var/abs/.
* Added [community] package support by calling on aurbuild --official as needed (see COMMUNITY PACKAGES in man page for more details).

Yes, I think I had a retard attack when I wrote that.

Ok, thanks for clarifying, works great now :-) btw, shouldn\'t this be \"+wx\"? (just in case others are wondering)

Ok it needs to have at least write and execute rights to aurbuild user or group. That means somebody:aurbuild will work with chmod g+we, aurbuild:somebody will work with chmod u+we, or somebody:somebody will work with chmod o+we

Oh, and ownership is rabyte:users, btw.

By \"correctly\" I actually meant 755. Well, at least that\'s the default :-) Didn\'t work with 775, but with 777. Seems like I missed something...

Ok guys try giving that directory write AND EXECUTE rights not just write all by itself. My bad I assume write would be enough.

correct as in what? I need to see the output of ls -la PKGDEST!

I\'ve got the same problem, permissions are set correctly.

sickhate: are you still having issues? If so please post the output of ls -l PKGDEST

but i do have permissions...dunno why but the last version complains about it...im going to try this lastest one and seen if the result is the same..

sickhate you need to have write permissions to PKGDEST for aurbuild user or group.

-v1.7.3 (January 22, 2007)
* Spelling correction for versionpkg().

libtranslate-0.99-1.pkg.tar.gz: Cannot write: Broken pipe
tar: Error is not recoverable: exiting now...i cannot right on my directories...starnge bug..downgrading

-v1.7.2 (January 21, 2007)
* Fixed missing -f option to versionpkg.
* Fixed makepkg v3 missing -w option.
* Added --rm-make-deps to remove uneeded make dependencies after a successful build.

s4rg.on: set PKGDEST variable in /etc/makepkg.conf to the directory, where you want the packages to be saved.

>s4rg.on: there are no binary packages in unsupported . You have to use pacman for everything else :)
Ok, again. When I build an package with aurbuild in the moment where build process finished and aurbuild would like to install result of build process. I want to have the result! Usually aurbuild would now install the pkg makepkg has generated with pacman. Sry, my english is horrible

sickhate: you\'ll need to do aurbuild -s aurbuild to upgrade

s4rg.on: there are no binary packages in unsupported . You have to use pacman for everything else :)

The problem is aur\'s inconsistant and dopy permissions and ownership on the tarballs. Should be fixed now.

this happens on a update...whats wrong?

could not transfer extracted tarball contents to destination:
[(\'/tmp/aurbuild/checkinstall.5123.extract/checkinstall/PKGBUILD\', \'/var/tmp/aurbuild/build/checkinstall.5123/checkinstall/PKGBUILD\', <exceptions.IOError instance at 0xb7a240ac>)].....errr...error?

Is there a way to get a pkg instead of installing the build result.

-v1.7 (January 16, 2007)
* Running as regular user is no longer needed. Root access will be required to drop down to a designated under-privaledged
user for building. This will enable greater future scalability while adding a higher level of security to the build process.
* build directory location now in /var/tmp/aurbuild/build/<pkgname>.<pid>
* PKGBUILD save location now in /var/tmp/aurbuild/pkgbuilds/<pkgname>
* sudo/su -c are no longer needed.
* options --wait-sudo, --no-sudo removed.
* option --keep-build-dir removed. Failed builds are retained by default now.
* option -c, --clean added to clean the build directory (for failed builds).
* source files are copied into /var/cache/pacman/src to prevent unnecessary multiple downloads.
* Makepkg v2 and v3 compatibility.
* Manpage spelling correction.

No I\'m sorry but there isn\'t support for building community packages. My primary focus is strickly with unsupported. You can use srcpac from the standard repos build packages like this. Just enable community in abs.conf and run it.

maybe its been said somewhere, but how can i make it continue to build packages which are already in [community]? sometimes i dont want to install the binary. is there a switch or ???

-v1.6.1.1 (November 21, 2006)
* Fixed failed logins with --vote and --unvote due to non-english language settings in the AUR account.

-v1.6.1 (November 17, 2006)
* Extended package search with build operations. If package is not found in aur, repeat search with an appended space.
This finds \"lost\" packages for those with short names, ie. rar, not descriptive enough to be found in standard search queries.
* Fixed duplicate package build directories within the master build directory.

-v1.6 (November 5, 2006)
* Replaced makepkg-opts with builder-opts. This passes OPTS to the builder of choice (makepkg or versionpkg) selected from the menu.
Note the syntax has changed: --makepkg-opts=\"ab bla foo\" --> --builder-opts=\"-a -b --bla --foo\"
* sudo is no longer a required dependency. su -c \"CMD\" will be invoked if sudo is not installed, requiring a
root password.
* -t, --no-sudo switch added to disable the use of sudo and use su -c \"CMD\" for root operations.
* -r, --revision switch added to check SVN/CVS/MERCURIAL servers for the latest revisions on qualified PKGBUILDS
during an --upgrade session.
* Absolute environmental editor path and switches supported.
* Preferred builder autodetection implemented. Variables in the PKGBUILD are examined and a star is placed next to the preferred
builder as well as being pre-selected in the choice field.

I installed aurbuild and I tried. I find that it is a nice piece of software and it seems to have a lot of good options that allow you to manage aur pakages so well. Addiotanlly, it seems to be very oriented to safeness. However there are three things that I don\'t like so much:

* Why is the sudo command needed? Maybe it just can use the su command with -c option. Unless you want to allow some users to install programs (I don\'t agree with that but everybody is different).
* I don\'t see why to use an editor to see the PKGBUILD and the install file. I think, maybe it is enough with less (Maybe we can use the one supported with enscipt to color the files).
* If you set up your own EDITOR variable with flags or an absolute path of the editor, aurbuild fails. I solved this and you can get the patch here: http://www.cs.fiu.edu/~lusec001/software/apath_flags_editor_aurbuild.patch

Any comments will be welcome.

Added to my repo:

[darwin]
Server = http://darwin.info.tm/arch/i686

-v1.5.2 (September 28, 2006)
*Fixed \'Index out of range\' errors when running --upgrade due to corrupt database files.
*Removed redundant \'Category:\' field in --search. Should be displayed in \'Location:\'.

s/packages/PKGBUILDs/

Just thought of a feature.

Maybe it\'d be nice to someway automagically set _kernver in packages to `uname -r` - it\'d usable when building modules.

It\'s http://developer.berlios.de/projects/aurbuild ... just in case somebody\'s totally lost.

updated new server location at download.berlios.de/projects/aurbuild

Please use that for any bug reports/feature requests/etc.

-v1.5.1 (August 8, 2006)
*Fixed inhereted setgid bit in the built the package resulting from AUR\'s set mode of the parent directory in the tarball.
The unwanted inhereted bit occured only under the following circumstances:
- user was root.
- a \'install -m<MODE NUMBER>\' line was excuted in the PKGBUILD without explicitly setting the first pair of octets, ie 644 instead of 0644
- Any other type of \'chmod\' command without the first octet set.
If you have built any packages meeting the criteria list above, rebuild and install offending packages now. Run the update command to get the list of all
packages built from AUR. String them together in a space separated line to aurbuild and use the menu to see if any install/chmod lines were used. You can
use (s) from the menu to skip the current package and move on to the next.

Problem found.. The package that i was building doesn\'t had the \"normal\" configure script (netwib) so it uses gcc instead distcc.
I\'ve tryed with other packages and all seems to compile properly.
The diference in distcc and gcc is simple, just look at the make compile comand, if it shows gcc or distcc.

gothicknight:
I know nothing about distcc. What indication do you get that distcc compiles are working when you use makepkg alone so I can troubleshoot?

PS:
one thing you could try is to make the call to makepkg use the shell:
on line 446, add shell=True
code = Popen([\'makepkg\', \'-f\' + optarg], shell=True).wait()
do the same for 448:
code = Popen([\'makepkg\', \'-f\'], shell=True).wait()

makepkg alone compiles with distcc. I thought that it maybe fakeroot enviroment. I don\'t have the knowledge for testing using fakeroot to test it. So if someone can try to replicate this error would be great. I\'ll try to find out more on my one and post here.

It calls on makepkg to build the package and makepkg reads its config file so I don\'t really see what the problem could be.
Looking at the relevant code in makepkg wheen it sees the distcc variable set, it tries to update the PATH variable and set DISTCC_DIR. For me those variables are never changed whether I run makpekg by itself or aurbuild. Yes I installed distcc.

Can you confirm those variables are being updated with makepkg alone?

Problem here... aurbuild isn\'t using makepkg.etc distcc option wich means that i can\'t use distcc in aurbuild compilations.

mucknert:
I did this intentionally as autohandling/installing dependencies that are from unsupported AUR can be inherently dangerous by nature. We can\'t always assume unsupported PKGBUILD\'s are safe to use. If the user has to go through a little more work to add these unsupported deps, then surely they will know what packages are suspect in the case of failure rather than not knowing at all because a program did it automatically.
Remember you can always string all the deps including the target package as one line to aurbuild just as you can to pacman, but they must be in order.

This tool is great! But I miss an option to install dependencies from AUR instead of ABS or using pacman. You know, some packages like engage-cvs depend on other packages that can only be optained via AUR, too.

-v1.5 (July 26, 2006)
*Added -w, --wait-sudo to wait for the user to hit enter before using sudo.
*Added -k, --keep-build-dir to keep the build directory if a package fails to build.
*Added versionpkg to the menu for CVS/SVN/Mercurial packages.
*Fixed \'aur[1]\' traceback calls when using --upgrade due to PKGBUILD\'s with syntax errors on the AUR server.
The default action is to skip the package and relay the package name and syntax errors back to the user.
*--search now matches first 100 results instead of 25.
*version.py: alpha-numeric recombination logic re-worked. A rare few may find new upgrades.

n0gabor: AFAIK, no. See my comment several posts above for the reason.

Penguin: You might want to remove the old comments that are no longer relevant. It\'ll be easier to know what are the current issues.

will it moved to community?

f aurbuild is used for CVS/SVN packages, does it call versionpkg? If not, perhaps it should - versionpkg is the recommended way to handle them.

-v1.4 (July 15, 2006)
*Added -V, --vote and -U, --unvote switches to vote or un-vote for packages.
*Support for multiple running instances by using unique build directories, ~/.aurbuild.<PID>
*Manpage typos corrected.
*More module refactoring for a (hopefully) smoother and quicker upgrade process to pacman3 and further AUR updates.

It uses AUR\'s search engine to find the package you specify and qu didn\'t come up with anything even though it does exist. It would seem more logical to download it directly by specifying the path it should be ie: http://aur.archlinux.org/packages/pkgname/pkgname.tar.gz but unfortunately not everyone follows the upload standards so you can have wrong parent folders and even different compressions. I originally wrote aurbuild to behave this way but ran across these problems several times and thus ended up with using AUR\'s search engine. Its proven to be far more accurate even with these few hiccups. Also without using AUR\'s interface, I wouldn\'t be able to determine if the package is safe.

aurbuild -s qu
doesn\'t work (didn\'t find the package even it exists :)

yeah...or you can run aurbuild -su or aurbuild -bu and update all the packages you\'ve installed from aur including aurbuild -its like doing a pacman -Syu.

BTW: I greatly appreciate everyone\'s kind comments and votes.

Tools like aurbuild or qpkg will never go in the community repo because they install packages that are unsupported. If they would be in the community repo, some users might get the impression that they can start to install any unsupported package without first examining the PKGBUILD, .install file and other files that comes with them. I\'m not saying that aurbuild or qpkg are bad (they can be quite useful) but they will remain in unsupported.

BTW, once you\'ve got aurbuild installed, you can easily update it with:
aurbuild -s aurbuild

I ahve to say i used qpkg, but switched to aurbuild and am amazed with it. What a great job have you made!!!

I still can\'t get why it isn\'t already in community...

uncomment your export PKGDEST= in makepkg.conf and set it to where you like -make sure it has user rights.
I\'d rather keep it simple and tie in with makepkg configs than creating a seperate designated cache folder.
Its all explained in the manpage.

Could be very useful somthing like pacman cache

e.g. a /var/cache/aurbuild/pkg folder where to store all compiled packages after installed.

-v0.5 (September 18, 2005)
*Search AUR with a single keyword.

Could everyone please note that this is not an officially endorsed \"product\" - the \"use PKGBUILDs in UNSUPPORTED at your own risk\" disclaimer still applies!

Aurbuild is a continuation of a project originally created by Dusty Phillips. It will safely build and install packages from AUR as regular user through the use of fakeroot to build the package, and sudo to install it through pacman.