Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!
Bug 188577 - gnome-extra/gconf-editor-2.18.0 is missing a dep on scrollkeeper
Summary: gnome-extra/gconf-editor-2.18.0 is missing a dep on scrollkeeper
Status: RESOLVED FIXED
Alias: None
Product: Gentoo Linux
Classification: Unclassified
Component: New packages (show other bugs)
Hardware: All Linux
: High normal
Assignee: Gentoo Linux Gnome Desktop Team
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2007-08-12 12:15 UTC by Markus Rothe (RETIRED)
Modified: 2007-08-12 13:34 UTC (History)
1 user (show)

See Also:
Package list:
Runtime testing required: ---


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Markus Rothe (RETIRED) gentoo-dev 2007-08-12 12:15:39 UTC
While installing a fresh gnome-2.18 (i.e. no upgrade) I ran into this problem while compiling gnome-extra/gconf-editor-2.18.0:

[...]
make[2]: Leaving directory `/var/tmp/portage/gnome-extra/gconf-editor-2.18.0/work/gconf-editor-2.18.0/po'
Making all in docs
make[2]: Entering directory `/var/tmp/portage/gnome-extra/gconf-editor-2.18.0/work/gconf-editor-2.18.0/docs'
/bin/sh: scrollkeeper-config: command not found
/bin/sh: line 1: scrollkeeper-config: command not found
The file '/Templates/C/scrollkeeper_cl.xml' does not exist.
Please check your ScrollKeeper installation.
make[2]: *** [gconf-editor-C.omf] Error 1
make[2]: Leaving directory `/var/tmp/portage/gnome-extra/gconf-editor-2.18.0/work/gconf-editor-2.18.0/docs'
make[1]: *** [all-recursive] Error 1
make[1]: Leaving directory `/var/tmp/portage/gnome-extra/gconf-editor-2.18.0/work/gconf-editor-2.18.0'
make: *** [all] Error 2


Installing app-text/scrollkeeper-0.3.14-r2 fixed the problem. I think there should be a dep on scrollkeeper in gconf-editor?

(this is ppc64, but this should be a problem on all arches I think)
Comment 1 Gilles Dartiguelongue (RETIRED) gentoo-dev 2007-08-12 13:34:57 UTC
fixed in CVS, I only updated gconf-editor-2.18 because it seems it wasn't a problem on 2.16 (probably a gnome-doc-utils migration in between).

Thanks for the report.