First Last Prev Next    No search results available      Search page      Enter new bug
Bug#: 188577
Alias:
Product:
Component:
Status: RESOLVED
Resolution: FIXED
Assigned To: Gentoo Linux Gnome Desktop Team <gnome@gentoo.org>
Hardware:
OS:
Version:
Priority:
Severity:
Reporter: Markus Rothe <corsair@gentoo.org>
Add CC:
CC:
Remove selected CCs
URL:
Summary:
Status Whiteboard:
Keywords:

Filename Description Type Creator Created Size Actions
Create a New Attachment (proposed patch, testcase, etc.) View All

Bug 188577 depends on: Show dependency tree
Show dependency graph
Bug 188577 blocks:
Votes: 0    Show votes for this bug    Vote for this bug

Additional Comments: (this is where you put emerge --info)







View Bug Activity   |   Format For Printing   |   XML   |   Clone This Bug


Description:   Opened: 2007-08-12 12:15 0000
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 From Gilles Dartiguelongue 2007-08-12 13:34:57 0000 -------
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.

First Last Prev Next    No search results available      Search page      Enter new bug