Arch Linux User Repository

You should have a config.log, probably in src/kalu-4.2.0, with more info about what actually failed. Also, looking at that output it even says you don't have pkg-config, which clearly seems wrong as well, so that might be what needs looking into...

• full log https://privatebin.net/?d33aa6a513d84d70#oZxb693D0TCwE13npFGJX2tRXHHO1TN1j8xzu6R0+Vc=, I don't have a config.log
• my system is fully updated with pacman -Syu

pkg-config --cflags --libs libnotify
-pthread -I/usr/include/gdk-pixbuf-2.0 -I/usr/include/glib-2.0 -I/usr/lib/glib-2.0/include -lnotify -lgdk_pixbuf-2.0 -lgio-2.0 -lgobject-2.0 -lglib-2.0

Sorry about the delay, I've been having connectivity issues. Anyhow,

• looks more like configure's output than full log, as in don't you have a config.log with more details?

• is your system fully updated? maybe a shot in the dark, but I've seen some "weird" issues somewhat similar due to issues with libdrm, though I believe the latest package in Arch should fix it. What do you get from this: pkg-config --cflags --libs libnotify

Same, I have libnotify installed but it is complaining.

Here are full logs: https://hastebin.com/raw/odonusozod

I'm not in chroot.

hmm, that is strange. Full logs might be helpful to know more... Is libnotify "fully" installed (e.g. including headers, etc)? Any chance you're building in a chroot? And if so, did you make sure libnotify was installed in said chroot as well?

Compiling is complaining about libnotify.

configure: error: libnotify is required

But it is installed.

$ pacman -Qs notify

local/libnotify 0.7.7-1

Library for sending desktop notifications

Why do you use "chmod" and "chown" commands in PKGBUILD ? these are bad practices because "/usr/share/polkit-1/rules.d" already exists, it seems weird to change access permissions for an existing directory ( "/usr/share/polkit-1/rules.d" )

No, it doesn't already exist, and nothing is changed. It might exists in your system, sure, but not in the package we're creating. And the point actually is to remain consistent with what's likely to be on your system, i.e. use the same permissions/ownership as polkit. Because otherwise, when installing kalu you'd get a warning from pacman that permissions differ between system & package.

if kalu really needs these commands then this kind of thing shoud be done manually by the user,

Nonsense; Again you seem to be confusing things, we're creating a package here, not touching anything in the system.

As for the group kalu, it is created because a polkit rule is installed, to allow members of said group to perform sysupgrade (via kalu's updater) without authentication, as explained in the man page.

noraj: About namcap's output, thanks, those are all fine/expected.

Why do you use "chmod" and "chown" commands in PKGBUILD ?

these are bad practices because "/usr/share/polkit-1/rules.d" already exists, it seems weird to change access permissions for an existing directory ( "/usr/share/polkit-1/rules.d" )

if kalu really needs these commands then this kind of thing shoud be done manually by the user,

I see also that you have created a new group called "kalu",

it would be interesting to avoid these commands, kalu should be able to run with the current user and existing permissions for /usr/share/polkit-1/rules.d

Thanks for this very useful tool.

namcap told me some stuff about kalu:

• kalu E: File (usr/share/polkit-1/rules.d) is owned by root:polkitd
• kalu E: GPL3+ is not a common license (it's not in /usr/share/licenses/common/)
• kalu W: File (usr/share/polkit-1/rules.d) does not have the world readable bit set.
• kalu W: Directory (usr/share/polkit-1/rules.d) does not have the world executable bit set.
• kalu W: Dependency dbus included but already satisfied
• kalu W: Dependency polkit included but already satisfied
• kalu W: Dependency curl included but already satisfied
• kalu W: Dependency included and not needed ('notification-daemon')

Happy to know it's useful :)

So, I'm glad you got it resolved, but since there was no version change, any idea what caused the segfault? If you were to rebuild kalu, would it crash again? If so, any indications/backtraces/logs that could help figure out what's the problem & how to fix it is welcome, obviously.