Package Details: kalu 4.3.0-1

Git Clone URL: https://aur.archlinux.org/kalu.git (read-only)
Package Base: kalu
Description: Upgrade notifier w/ AUR support, watched (AUR) packages, news
Upstream URL: https://jjacky.com/kalu
Licenses: GPL3+
Submitter: jjacky
Maintainer: jjacky
Last Packager: jjacky
Votes: 182
Popularity: 1.147648
First Submitted: 2012-02-14 18:03
Last Updated: 2018-06-04 17:45

Latest Comments

« First ‹ Previous ... 8 9 10 11 12 13 14 Next › Last »

jjacky commented on 2012-07-21 11:13

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

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

Thanks!

jjacky commented on 2012-07-20 20:29

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

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

@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

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

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

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!

denoyse commented on 2012-05-05 11:44

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!

jjacky commented on 2012-05-05 10:16

kalu-dbus is started automatically w/ root privileges already, that's not the issue. If you really want to allow sysupgrade w/out password check, I think you'll need to change the policy (in /usr/share/polkit-1/actions/org.jjk.kalu.policy) and replace auth_admin with yes

As for AUR upgrade, that's not gonna happen. kalu's updater simply provides a little GUI for libalpm's sysupgrade, nothing more. But you can have a button (on AUR notifications) to start an (AUR) helper of your choice to take care of it.