Package Details: kalu-git 4.1.0-1

Git Clone URL: https://aur.archlinux.org/kalu-git.git (read-only)
Package Base: kalu-git
Description: Upgrade notifier w/ AUR support, watched (AUR) packages, news [GIT]
Upstream URL: http://jjacky.com/kalu
Licenses: GPL3+
Conflicts: kalu
Provides: kalu
Submitter: jjacky
Maintainer: jjacky
Last Packager: jjacky
Votes: 9
Popularity: 0.011634
First Submitted: 2013-10-20 15:09
Last Updated: 2016-05-12 18:13

Latest Comments

Pinerto commented on 2016-02-01 14:40

For All

*Replace in the PKGBUILD
line 10 'pacman>=4.2' 'pacman<4.3' to
line 10 'pacman>=5.0' 'pacman<5.7'

*Rename in the PKGBUILD line 13 >> "branch=next" to "branch=pacman-5"

makepkg -s
sudo pacman -U ... [ pkg name]

archtom commented on 2016-02-01 08:38

Hey, thanks for kalu, it`s very nice.
Pacman was just updated to 5.0. Would be nice to see an updated pkgbuild.
Thanks

yan12125 commented on 2016-01-04 10:02

Permission of /usr/share/polkit-1/rules.d is changed since [1]. As a result, I got the following warning:

(1/1) installing kalu-git [###########################################] 100%
warning: directory permissions differ on /usr/share/polkit-1/rules.d/
filesystem: 750 package: 700

Could you please fix it?

[1] https://projects.archlinux.org/svntogit/packages.git/commit/trunk?h=packages/polkit&id=6e3a4177f8cecf57e3a02f18238b46e301c30faa

jjacky commented on 2014-12-27 16:46

Yeah, little oversight on my part. For a little while now kalu-git actually requires pacman-4.2 to build...

PKGBUILD updated; Thanks.

yan12125 commented on 2014-12-27 16:27

On my box kalu-git works fine with pacman=4.2.0-3. Why not get rid of the version restriction of pacman in PKGBUILD?

jjacky commented on 2014-08-08 09:12

Alright, thought about this a bit more and realized I was wrong, actually. I can't do it just now, but I'll update the PKGBUILD with a correct/expected pkgver.

jjacky commented on 2014-08-07 21:13

Well, it really sounds like a bug in AURA, you should report it there so it gets fixed. Since the pkgver remains the same, the package should only ever be out of date based on pkgrel. vercmp handles it just fine.

I don't really wanna change the pkgver actually, because a date doesn't mean much, since it's a -git PKGBUILD and should be rebuild to get the latest version even when nothing changed in the actual PKGBUILD.
I feel using a date could give the impression that it would be a meaningful date, while in reality it wouldn't be. Same with a version number.

flamusdiu commented on 2014-08-07 20:47

@jjacky : can you change your package version from "next" to date the pkgfile. Using "next", "current", or anything similar breaks AURA. It keeps thinking the package is out-of-date even though it isn't. Also, this isn't common in AUR.

Thanks!