You are not logged in.
During the installation of http://aur.archlinux.org/packages/cddb-py/ I get this error
[user@bir dl]$ tar -xvzf cddb-py.tar.gz
cddb-py/
cddb-py/PKGBUILD
[user@bir dl]$ cd cddb-py
[user@bir cddb-py]$ makepkg
==> ERROR: cddb-py is not available for the 'i686' architecture.
Note that many packages may need a line added to their PKGBUILD
such as arch=('i686').
python is allready installed. makepkg -s causes the same error
What is wrong?
Offline
During the installation of http://aur.archlinux.org/packages/cddb-py/ I get this error
[user@bir dl]$ tar -xvzf cddb-py.tar.gz
cddb-py/
cddb-py/PKGBUILD
[user@bir dl]$ cd cddb-py
[user@bir cddb-py]$ makepkg
==> ERROR: cddb-py is not available for the 'i686' architecture.
Note that many packages may need a line added to their PKGBUILD
such as arch=('i686').python is allready installed. makepkg -s causes the same error
What is wrong?
I have bolded the pertinent part of the error message. Add arch=('i686') to the pkgbuild, or if arch=('x86_64') is already there, just add it like so: arch=('x86_64' 'i686')
Offline
Thanks a million, it works fine. Exaile from CD works now too :-). My pkgbuild looks like
...
license=""
arch=('i686')
depends=(python)
...
Is the order ok? Anybody else, who wonders how to deal with AUR packages: there is a wiki http://wiki.archlinux.org/index.php/Makepkg
Offline
The order doesn't matter, it all just gets sourced through your shell.
I am a gated community.
Offline
It's true that, as far as making the PKGBUILD work is concerned, order doesn't matter. However, some people prefer PKGBUILDs that are all uniform in order, which makes them easier to read. I'd suggest looking in the wiki for PKGBUILD.proto (or, if you're using abs, it'll exist in /var/abs/core I think) for a suggested style guide for ordering your vars.
Offline