Mailinglist Archive: opensuse-packaging (135 mails)
| < Previous | Next > |
[opensuse-packaging] Re: [opensuse-gnome] Using scrollkeeper: /var/lib/scrollkeeper missing?
- From: Stanislav Brabec <sbrabec@xxxxxxx>
- Date: Tue, 21 Aug 2007 11:16:32 +0200
- Message-id: <1187687792.27799.34.camel@xxxxxxxxxxxxxx>
Michel Salim wrote:
> On 20/08/07, Stanislav Brabec <sbrabec@xxxxxxx> 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.
--
Best Regards / S pozdravem,
Stanislav Brabec
software developer
---------------------------------------------------------------------
SUSE LINUX, s. r. o. e-mail: sbrabec@xxxxxxx
Lihovarská 1060/12 tel: +420 284 028 966
190 00 Praha 9 fax: +420 284 028 951
Czech Republic http://www.suse.cz/
---------------------------------------------------------------------
To unsubscribe, e-mail: opensuse-packaging+unsubscribe@xxxxxxxxxxxx
For additional commands, e-mail: opensuse-packaging+help@xxxxxxxxxxxx
> On 20/08/07, Stanislav Brabec <sbrabec@xxxxxxx> 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.
--
Best Regards / S pozdravem,
Stanislav Brabec
software developer
---------------------------------------------------------------------
SUSE LINUX, s. r. o. e-mail: sbrabec@xxxxxxx
Lihovarská 1060/12 tel: +420 284 028 966
190 00 Praha 9 fax: +420 284 028 951
Czech Republic http://www.suse.cz/
---------------------------------------------------------------------
To unsubscribe, e-mail: opensuse-packaging+unsubscribe@xxxxxxxxxxxx
For additional commands, e-mail: opensuse-packaging+help@xxxxxxxxxxxx
| < Previous | Next > |