First Last Prev Next    No search results available      Search page      Enter new bug
Bug#: 237973
Alias:
Product:
Component:
Status: RESOLVED
Resolution: FIXED
Assigned To: Java team <java@gentoo.org>
Hardware:
OS:
Version:
Priority:
Severity:
Reporter: Jason Komar <jkomar@lubecorp.com>
Add CC:
CC:
URL:
Summary:
Status Whiteboard:
Keywords:

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

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

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


Not eligible to see or edit group visibility for this bug.






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


Description:   Opened: 2008-09-17 23:57 0000
If eclipse-sdk-3.4-r2 is installed with swt-3.4_pre6-r1, Eclipse will not start
complaining of not being able to create a configuration file.

The symptom of this was reported in bug 236407, but not the cause which I have
discovered after much messing around.

Reproducible: Always

Steps to Reproduce:
1.emerge dev-util/eclipse-sdk-3.4-r2
2.(with dev-java/swt-3.4_pre6-r1 installed)
3.

Actual Results:  
The package merges fine, but eclipse-sdk fails after the splash screen
complaining of not being able to create a configuration file.

Expected Results:  
Eclipse-sdk starts and runs as intended.

If the dependency on dev-java/swt is further refined to exclude
dev-java/swt-3.4_pre6-r1 and the require 3.4 and above, this could save someone
else a lot of messing around.

------- Comment #1 From Jean-Noël Rivasseau 2008-10-09 11:02:09 0000 -------
Fixed by removing old swt ebuilds.

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