First Last Prev Next    No search results available      Search page      Enter new bug
Bug#: 192671
Alias:
Product:
Component:
Status: RESOLVED
Resolution: FIXED
Assigned To: Christian Faulhammer <opfer@gentoo.org>
Hardware:
OS:
Version:
Priority:
Severity:
Reporter: Christian Faulhammer <opfer@gentoo.org>
Add CC:
CC:
URL:
Summary:
Status Whiteboard:
Keywords:

Filename Description Type Creator Created Size Actions
x11-libs:gtk+-2.10.14:20070916-131837.log gtk+ log text/plain Christoph Mende 2007-09-16 13:30 0000 449 bytes Details
Create a New Attachment (proposed patch, testcase, etc.) View All

Bug 192671 depends on: Show dependency tree
Show dependency graph
Bug 192671 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-09-16 10:41 0000
Current stable sys-apps/portage-2.1.3.9 has save_summary in ELOG_FEATURES,
causing current stable app-portage/elogv{,iewer} to crash (see bug 187595). 
Please stabilise working versions prematurely.  x86 done

------- Comment #1 From Christoph Mende 2007-09-16 13:30:38 0000 -------
Created an attachment (id=131051) [edit]
gtk+ log

I get a traceback and incomplete output with elogviewer on attached log file -
elogv works and is stable

------- Comment #2 From Christian Faulhammer 2007-09-16 14:49:41 0000 -------
I don't really get why that is relevant for elogviewer...it is a build failure
for gtk+ and it tells you should emerge cairo with USE=X

------- Comment #3 From Christoph Mende 2007-09-16 15:35:49 0000 -------
I know, you're not supposed to read that log, if you try to read that log using
elogviewer you get incomplete output and elogviewer spits out a backtrace on
the commandline which takes me to the assumption that there's a bug in
elogviewer

------- Comment #4 From Christian Faulhammer 2007-09-16 16:51:24 0000 -------
amd64 stable and closing, done by angelos

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