On Tue, 2007-08-21 at 11:16 +0200, Stanislav Brabec wrote: > Michel Salim wrote: > > On 20/08/07, Stanislav Brabec <[EMAIL PROTECTED]> wrote: > > > > > > > > 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. > > In past, scrollkeeper was used by root in SuSEconfig (and triggered by > RPM postinstall), so /var/lib/scrollkeeper was existing in the build > root and this segfault was hidden. > > Now scrollkeeper is only a development package and nobody calls > scrollkeeper-rebuilddb, so /var/lib/scrollkeeper does not exist. >
I'm having the same problem (when packaging rubrica2) for openSUSE 10.2 when calling scrollkeeper in the %post section Will there be a fix included in the scollkeeper package? Otherwise different solutions/workarounds will show up on various places...(both good and bad solutions) Kind regards, -- Leo Eraly <[EMAIL PROTECTED]> --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
