Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 325093 - Eclipse successfully updates broken bundle ending with missing eclipse.exe or libcairo-swt.so
Summary: Eclipse successfully updates broken bundle ending with missing eclipse.exe or...
Status: RESOLVED WONTFIX
Alias: None
Product: Equinox
Classification: Eclipse Project
Component: p2 (show other bugs)
Version: 3.6   Edit
Hardware: PC Mac OS X - Carbon (unsup.)
: P3 normal (vote)
Target Milestone: ---   Edit
Assignee: P2 Inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2010-09-13 05:52 EDT by Jacek Pospychala CLA
Modified: 2020-02-19 04:18 EST (History)
2 users (show)

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Jacek Pospychala CLA 2010-09-13 05:52:24 EDT
hi,

in our Eclipse 3.6 based product users go to "Help->Check for updates".
On Windows, update is performed successfully, but then after the restart, product is not started because eclipse.exe file is missing.
On Linux, update fails with criptic message:

session context was:(profile=studioProfile, phase=org.eclipse.equinox.internal.p2.engine.phases.Install, operand=null --> [R]com.zend.php.ide.launcher.gtk.linux.x86 8.0.0.v20100907190, action=org.eclipse.equinox.internal.p2.touchpoint.natives.actions.ChmodAction).
The action chmod failed - file /home/zend/Zend/ZendStudio-188/libcairo-swt.so does not exist 


To our surprise, Apache server with P2 repository, was configured to pass all files in "binary/" folders to PHP extension.
Unfortunately, p2 binary/ files are not PHP code, so Apache server is always sending back php errors page instead of real binaries.
This doesn't stop P2 from installing broken responses as real bundles.


Could p2 perform some integrity check before trying to install bundles?
Comment 1 Eclipse Webmaster CLA 2019-09-06 15:30:52 EDT
This bug hasn't had any activity in quite some time. Maybe the problem got resolved, was a duplicate of something else, or became less pressing for some reason - or maybe it's still relevant but just hasn't been looked at yet.

If you have further information on the current state of the bug, please add it. The information can be, for example, that the problem still occurs, that you still want the feature, that more information is needed, or that the bug is (for whatever reason) no longer relevant.
Comment 2 Ed Merks CLA 2020-02-19 04:18:18 EST
I'll assume this issue is stale and is not a problem with recent releases.