On 20/08/07, Stanislav Brabec
Why to add new user account and another dangerous sgid application? These data were updated by root after the (un)installation and should never be changed by users.
Hm. the %post-un and %post scriplets are run as root anyway, so there is no need for a new sgid application, right?
Sorry. I was thinking you are proposing new UID owning /var/lib/scrollkeeper.
There was another problem during build you have another problem: It (incorrectly) tried to create and access /var/lib/scrollkeeper during %install, but it fails, because build process has no permission there. And the bug caused segfault: https://bugzilla.novell.com/show_bug.cgi?id=230786
If scrollkeeper was used as root, it was working correctly.
Thing is, scrollkeeper _was_ used as root during RPM post-install phase, right? In any case, the problem is the version shipping in 10.2+updates does /not/ initialize /var/lib/scrollkeeper unless scrollkeeper-rebuilddb is run.
Since we're at it, how about update-mime-database? Also not needed?
It's needed if you install anything to /usr/share/mime/packages. You must not install anything to /usr/share/mime except packages directory.
%post if test -x usr/bin/update-mime-database ; then usr/bin/update-mime-database usr/share/mime >/dev/null fi
%postun if test -x usr/bin/update-mime-database ; then usr/bin/update-mime-database usr/share/mime >/dev/null fi
Got it, thanks. Those are already in the original spec. Package is up at openSUSE:Community (drivel-2.0.3-3.1). If anyone wants to get it working for versions lower than 10.2, or for Factory, feel free to dive in. Regards, -- Michel --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-packaging+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-packaging+help@opensuse.org