Package Details: kalu 4.3.0-1

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

Latest Comments

« First ‹ Previous 1 2 3 4 5 6 7 8 9 ... Next › Last »

jjacky commented on 2016-02-04 08:25

hmm... I guess that's what happens when you're tired. Stupid mistake on my part, just pushed a fix on branch next. Sorry about that.

Will have to release 4.0.2 very soon....

adam777 commented on 2016-02-04 05:29

I'm getting empty notifications with 4.0.1 for some reason.
Worked fine in 4.0.0

* EDIT *
Weird, it's working now after a few reinstalls.

N3mesis98 commented on 2016-02-01 20:14

Am I the only one getting this error when trying to launch the latest version of kalu (4.0.0-1) ?

(kalu:12930): Gdk-CRITICAL **: gdk_window_thaw_toplevel_updates: assertion 'window->update_and_descendants_freeze_count > 0' failed
Segmentation fault (core dumped)

jghodd commented on 2016-02-01 18:23

This is no longer building. Even when the 'pacman<4.3' dependency is removed from the PKGBUILD file, it's running into an issue with the latest pacman changes (

- alpm_siglevel_t - removed members ALPM_SIG_PACKAGE_SET, ALPM_SIG_PACKAGE_TRUST_SET

- alpm_event_pacorig_created_t
- alpm_event_t.pacorig_created

It's interesting that kalu-kde does build with the 'pacman<4.3' dependency removed, but kalu does not.

[Edit: the other comments weren't here when I started this post. I've used the pacman-5 branch to rebuild kalu and kalu-kde and both appear to be working fine.]

Pinerto commented on 2016-02-01 14:36

Works. >> ""pacman-5" instead of "next"
Only this
"warning: directory permissions differ on /usr/share/polkit-1/rules.d/
filesystem: 750 package: 700"


jjacky commented on 2016-02-01 14:24

You can't build this package because it requires a new upstream version, which doesn't exist yet; This is to be expected.

Again, you can simply use the PKGBUILD from kalu-git but using branch "pacman-5" instead of "next" to build a pacman 5-compatible kalu, while waiting for the new version.

Pinerto commented on 2016-02-01 14:20

Pls update at least your PKGBUILD.
Pacaur and aura are unable to build, because of the PKGBUILD.

jjacky commented on 2016-02-01 14:13

Not sure what you did, there's no actual error message here, but no: building from branch pacman-5 works fine with pacman 5.0
Obviously you need to build from git, so again using kalu-git's PKGBUILD but editing it to use the right branch (plus tweak dependencies).

I have to admit I was expecting pacman-5 to stay in testing a little bit longer, and I'm not ready just yet... but a new release of kalu will come soon. Meanwhile, you can build kalu from branch pacman-5 on github for a compatible version.

Pinerto commented on 2016-02-01 12:53

"simply build from that branch (e.g. using kalu-git from the AUR only changing the branch name in the PKGBUILD) "

Even with these changes, the build stop at:

Makefile:1118: recipe for target 'src/kalu-dbus/kalu_dbus-kalu-dbus.o' failed
make[2]: *** [src/kalu-dbus/kalu_dbus-kalu-dbus.o] Error 1
make[2]: Leaving directory '/home/archie/Downloads/kalu/src/kalu-3.0.0'
Makefile:1380: recipe for target 'all-recursive' failed
make[1]: *** [all-recursive] Error 1
make[1]: Leaving directory '/home/archie/Downloads/kalu/src/kalu-3.0.0'
Makefile:615: recipe for target 'all' failed
make: *** [all] Error 2
==> ERROR: A failure occurred in build().

It is the same for kalu and kalu-git too.

adam777 commented on 2016-02-01 07:21

I'll have a look, thanks.