From: "José Fonseca" <j_r_fonseca@yahoo.co.uk>
To: gentoo-dev@gentoo.org
Subject: [gentoo-dev] Failure to emerge scrollkeeper with gnome2 and gcc-3.1
Date: Thu, 30 May 2002 18:55:46 +0100 [thread overview]
Message-ID: <20020530175546.GM2359@localhost> (raw)
I already filled a bug ( http://bugs.gentoo.org/show_bug.cgi?id=3229 ),
but perhaps someone could provide more feedback here.
When emerging scrollkeeper with gnome2 and gcc-3.1 profile the following
error
occurs:
...
installing catalog
>>> Rebuilding Scrollkeeper database...
scrollkeeper-update: /usr/local/share/omf: No such file or directory
scrollkeeper-update: /opt/gnome/share/omf: No such file or directory
scrollkeeper-update: /opt/gnome-2.0/share/omf: No such file or directory
scrollkeeper-update: /opt/kde/omf: No such file or directory
Registering
/usr/share/omf/scrollkeeper/writing_scrollkeeper_omf_files-C.omf
>>> Updating Scrollkeeper database...
Could not create database. Aborting update.
!!! pkg_postinst() script failed; exiting.
Creating those directories eliminate the warnings but it still fails to
create
the database. And all gnome packages with use scrollkeeper fail in that
point
as well, always ending with a message like:
...
>>> Updating Scrollkeeper database...
Could not create database. Aborting update.
!!! pkg_postinst() script failed; exiting.
Although in every case the package is considered emerged.
Doing on the commandline
scrollkeeper-rebuilddb
works well, but still doing
scroolkeeper-update
fails.
Can someone here make sense out of this?
Regards,
José Fonseca
next reply other threads:[~2002-05-30 17:54 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-05-30 17:55 José Fonseca [this message]
2002-05-31 15:41 ` [gentoo-dev] Failure to emerge scrollkeeper with gnome2 and gcc-3.1 Spider
2002-07-11 20:17 ` [gentoo-dev] Failure to emerge scrollkeeper for gnome2 Christian HOFFMANN
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20020530175546.GM2359@localhost \
--to=j_r_fonseca@yahoo.co.uk \
--cc=gentoo-dev@gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox