[arch-general] New to Arch with problems with AUR
Hi list !
First i present myself. My name is Mario and i was reading this list for a few weeks. I'm coming from Debian, and i have to say that Arch was the first distro that replaced it in my computer. Arch rocks, it gives a really updated and stable kde desktop. Yes, it's a little hard to configure, but one can learn with it. And the AUR system was one of the main reasons for me to change.
I was trying to install some programs from AUR, and it worked in some cases. But in many other cases, the programs do not compile. And i talk about programs with so much votes.
For instance, i couldn't compile shaman. Actually i can't compile aqpm or libaqpm, wich is a dependency of shaman, and it isn't in the pacman repositories.
So, in general, how must i face these problems ? Do i have to post errors in the AUR pages ? Is it always so common to have problems in building AUR packages ?
By the way, i will stay with Arch. I like it's descentralized package philosophy.
Thank you
On 23.07.2010 12:27, Mario Daniel Carugno wrote:
First i present myself. My name is Mario and i was reading this list for a few weeks. I'm coming from Debian, [...]
Welcome :)
For instance, i couldn't compile shaman. Actually i can't compile aqpm or libaqpm, wich is a dependency of shaman, and it isn't in the pacman repositories.
Try to find out what's wrong (Maybe it's as easy as changing pkgver because upstream already fixed the problem in a newer release. Always check that first!) and if possible fix it yourself. If you can't, try asking on IRC or write a comment on the package's page.
Is it always so common to have problems in building AUR packages ?
There is software that's buggy and troublesome, but also one that just works™. At least those packages I use work most of the time.
On 23/07/10 11:36, Florian Pritz wrote:
On 23.07.2010 12:27, Mario Daniel Carugno wrote:
First i present myself. My name is Mario and i was reading this list for a few weeks. I'm coming from Debian, [...]
Welcome :)
For instance, i couldn't compile shaman. Actually i can't compile aqpm or libaqpm, wich is a dependency of shaman, and it isn't in the pacman repositories.
Try to find out what's wrong (Maybe it's as easy as changing pkgver because upstream already fixed the problem in a newer release. Always check that first!) and if possible fix it yourself. If you can't, try asking on IRC or write a comment on the package's page.
Is it always so common to have problems in building AUR packages ?
There is software that's buggy and troublesome, but also one that just works™. At least those packages I use work most of the time.
in the shaman case. IIRC shaman et al. is a dead horse, and shaman2 and friends are not ready yet.
Am 23.07.2010 12:39, schrieb Nathan Wayde:
On 23/07/10 11:36, Florian Pritz wrote:
On 23.07.2010 12:27, Mario Daniel Carugno wrote:
First i present myself. My name is Mario and i was reading this list for a few weeks. I'm coming from Debian, [...]
Welcome :)
For instance, i couldn't compile shaman. Actually i can't compile aqpm or libaqpm, wich is a dependency of shaman, and it isn't in the pacman repositories.
Try to find out what's wrong (Maybe it's as easy as changing pkgver because upstream already fixed the problem in a newer release. Always check that first!) and if possible fix it yourself. If you can't, try asking on IRC or write a comment on the package's page.
Is it always so common to have problems in building AUR packages ?
There is software that's buggy and troublesome, but also one that just works™. At least those packages I use work most of the time.
in the shaman case. IIRC shaman et al. is a dead horse, and shaman2 and friends are not ready yet.
... and probably never will be, since the chakra people want to write their own package manager.
Regards Stefan
Am Fri, 23 Jul 2010 12:36:12 +0200 schrieb Florian Pritz bluewind@server-speed.net:
Try to find out what's wrong (Maybe it's as easy as changing pkgver because upstream already fixed the problem in a newer release. Always check that first!) and if possible fix it yourself. If you can't, try asking on IRC or write a comment on the package's page.
Better writing a comment on the package's page in AUR. Not every maintainer of AUR packages is in IRC.
If you're unsure if it's an upstream or a downstream bug, ask the maintainer of an AUR package by writing a comment. If you won't get an answer try sending him an e-mail.
Heiko
participants (5)
-
Florian Pritz
-
Heiko Baums
-
Mario Daniel Carugno
-
Nathan Wayde
-
Stefan Husmann