Package Details: kalu 4.5.2-2

Git Clone URL: https://aur.archlinux.org/kalu.git (read-only, click to copy)
Package Base: kalu
Description: Upgrade notifier w/ AUR support, watched (AUR) packages, news
Upstream URL: https://github.com/Thulinma/kalu
Licenses: GPL3+
Submitter: jjacky
Maintainer: Thulinma
Last Packager: Thulinma
Votes: 182
Popularity: 0.000248
First Submitted: 2012-02-14 18:03 (UTC)
Last Updated: 2024-09-15 21:24 (UTC)

Latest Comments

« First ‹ Previous 1 .. 11 12 13 14 15 16 17 Next › Last »

mrbit commented on 2012-09-15 12:04 (UTC)

nice..thanks

PhotonX commented on 2012-07-21 11:44 (UTC)

Problem has been solved by itself. It might be because I didn't have my glibc updated and some modules were still in /lib rather then in /usr/lib. Now after the update of glibc the package builds and works fine. :)

jjacky commented on 2012-07-21 11:13 (UTC)

Afraid not. I assume you have pacman 4.0 correctly installed; you could try `gcc -print-search-dirs` and make sure that /usr/lib is on the libraries list. You could also try adding it, e.g. running `export LIBRARY_PATH=/usr/lib:$LIBRARY_PATH` before you ran configure/makepkg...

PhotonX commented on 2012-07-21 07:35 (UTC)

I see. Have you any hints about how to find the cause of the problem? Thanks!

jjacky commented on 2012-07-20 20:29 (UTC)

Not sure why you get that, but it seems like some error/problem on your side though; libalpm is a dep, since it is provided by pacman.

PhotonX commented on 2012-07-20 19:53 (UTC)

Seems like libalpm is missing as dep, at least I get checking for alpm_db_get_pkg in -lalpm... no configure: error: libalpm is required ==> ERROR: An error occured in build(). Aborting ... ==> ERROR: Makepkg was unable to build kalu. ==> Restart building kalu ? [y/N] Installed packages that might be interesting: $ yaourt alpm 1 extra/pyalpm 0.5.3-1 [installed] Libalpm bindings for Python 3 2 archlinuxfr/package-query 1.0.1-1 [installed] Query ALPM and AUR 8 aur/package-query 1.0.1-1 [installed] (1623)

jjacky commented on 2012-05-20 17:19 (UTC)

@denoyse: right, your policy file got overwritten during the update. I believe this could be avoided by putting the file in the backup array of the PKGBUILD, however i don't really see it as a configuration file, so I won't do that. Of course, you can add it yourself before making the package.

denoyse commented on 2012-05-20 14:01 (UTC)

After the update to 1.0 - of course - the system asks for the password again. would it be possible to add an option to maybe 1.1 where you can set up permissions to allow a passwordless update? Greetz

chadberg commented on 2012-05-11 22:59 (UTC)

Had to ln -s pod2man into /usr/bin for it to compile (I think lightdm is screwing up my path), but it's in, and I love it! Was using yapan, but kalu just shot to the top of my list....

denoyse commented on 2012-05-06 11:13 (UTC)

Yep, i got that (yaourt -Syua) I allready wondered why i was asked for a password, as i tryed to allow everything via sudo. I will try the policy file, thx for the tip! EDIT: Works perfectly, thanks!

« First ‹ Previous 1 .. 11 12 13 14 15 16 17 Next › Last »