While building an rpm as regular user I see the following
message:
scrollkeeper-update -p /usr/var/scrollkeeper
-o /tmp/making_of_synaptic-0.47/opt/gnome/share/omf/synaptic
Could not create directory /usr/var : Permission denied
Cannot write to log file: /var/log/scrollkeeper.log : Permission
denied
Could not create database. Aborting update.
Cannot write to log file: /var/log/scrollkeeper.log : Permission
denied
make[4]: [install-data-hook-omf] Error 1 (ignored)
The command above is needed when the application is installed
using e.g. ./configure, make, make install. But when
an rpm is being created as regular user the the above command
format should not result in an error as it is confusing for the
package maintainer. Or at least there should be a way to
avoid the error (check for uid == 0 perhaps?).
Logged In: NO
This also occurs with automake's make distcheck.
The issue is that scrollkeeper always tries to write to
/var/log/scrollkeeper.log when it is run. In the make
idstcheck or packaging scenarios, scrollkeeper-update is
being run as a non-root user so scrollkeeper is unable to
write to the log file.