| Summary: | dev-util/eclipse-sdk-3.2.1-r1 - failed eclipse-sdk-3.2.1-build.patch | ||
|---|---|---|---|
| Product: | Gentoo Linux | Reporter: | Amine Haddad <aminehaddad> |
| Component: | New packages | Assignee: | Development Tools Team <dev-tools> |
| Status: | RESOLVED FIXED | ||
| Severity: | normal | ||
| Priority: | High | ||
| Version: | unspecified | ||
| Hardware: | x86 | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Package list: | Runtime testing required: | --- | |
| Attachments: | eclipse-sdk-3.2.1-build.patch-12604.out | ||
|
Description
Amine Haddad
2007-01-26 19:44:54 UTC
Created attachment 108227 [details]
eclipse-sdk-3.2.1-build.patch-12604.out
The weirdest thing is that this has not been touched in a while: http://viewcvs.gentoo.org/viewcvs.py/gentoo-x86/dev-util/eclipse-sdk/ Ok. I found a workaround. For some reason the behaviour of popd ad pushd has changed in the ebuild. Might have something to do with a newer bash version etc. Will leave this open to investigate why it actually fails. I have also tried to install previous version of eclipse and they also fail upon using their own patches. I figured it was the patch program being corrupt, so I ran emerge -1 patch and it was still failing to apply the patch. It's strange, yesterday (28.1.07) I got the same error... Today (29.1.07) it works, although nothing changed in portage concerning eclipse or java, I even made no update. The ebuild was updated around 19 hours ago, an emerge --sync would have downloaded the latest ebuild (although no eclipse version change has occured), which applies the patch just fine. The problem had something to do with popd not going back to the working directory (for more information, check the cvs repo that Petteri pointed out earlier). Ok. The cause was recent a change breaking java-pkg-jar-from. There was one conditional return which did not call popd before the return. |