Community
Participate
Working Groups
hi, we're installing our Eclipse product using MSI installer on Windows 7 with UAC enabled. Typically, product is located under c:\Program Files. Unfortunately, when updating it using p2 "Check for Updates", I'm getting following error: Cannot complete the install because of a conflicting dependency. Software being installed: Zend Studio 8.0.0.v20100806 (com.zend.php.ide 8.0.0.v20100806) Software currently installed: Shared profile 1.0.0.1281012004128 (SharedProfile_studioProfile 1.0.0.1281012004128) Only one of the following can be installed at once: Zend Studio 8.0.0.v20100805 (com.zend.php.ide 8.0.0.v20100805) Zend Studio 8.0.0.v20100806 (com.zend.php.ide 8.0.0.v20100806) Cannot satisfy dependency: From: Shared profile 1.0.0.1281012004128 (SharedProfile_studioProfile 1.0.0.1281012004128) To: com.zend.php.ide [8.0.0.v20100805] If I start Eclipse using "Run as Administrator", then the product update process seems successful - there's no any error.
Our product is based on Helios. I saw similar error in bug 315853 but scenario seems different there. Could you please explain why this "SharedProfile" thing allows only one version of our product?
When using e.g. user home folder, instead of c:\Program files for the product installation, then update seems successful as well - no error message.
This is actually by design, and I'm actually happy to see it working :-) (we've had lots of problems where this isn't working). Here is the gist of what's going on. You have a number of plugins under c:\Program Files, and Eclipse can't write here because of UAC. When you install add-ons (no upgrades, just extra bundles) they go in ~/.eclipse, a hidden folder under the users home directory. However, we can't perform any 'updates' in this folder because you are in a shared install mode and it's assumed the admin will 'update' the base. However, in some cases, an install will force an update (new plugin X depends on an update of Y). In this case we can get into trouble, so we 'lock' the shared area so updates don't happen. This is what you're hitting. Now, this opens up some new questions, do you expect to update? In the past, the shared installs were more common on *nix environments, and the thinking is, you need to be an admin to 'update' the system.
Jacek, for some more information see: https://bugs.eclipse.org/bugs/show_bug.cgi?id=287246#c13
thanks for explanation Ian. so you're saying that updates are impossible when shared pool is non-writeable? It makes sense on *nix systems where user really has to make an effort ("su") to install Eclipse as root - it's fine to blame him for that :-) However on Windows with UAC privileges elevation is almost invisible (press "Yes" in this #*$&* dialog), so user will find it very difficult to resolve such issue. And UAC is becoming standard. There's two things that could change in p2: 1. the error message could be saying something along the lines: "To perform updates you need Administrator privileges" 2. p2 could support privileges elevation, to get write permission to shared pool
I opened two bugs for issues mentioned in last comment: Bug 322472 - Don't be shy and warn about missing privileges Bug 322477 - Support for elevated privileges for updates in shared install since this bug seems to fall into "work's as expected", feel free to close it accordingly.
I completely agree with you Janek(In reply to comment #5) > thanks for explanation Ian. > so you're saying that updates are impossible when shared pool is non-writeable? > Yep > It makes sense on *nix systems where user really has to make an effort ("su") > to install Eclipse as root - it's fine to blame him for that :-) However on > Windows with UAC privileges elevation is almost invisible (press "Yes" in this > #*$&* dialog), so user will find it very difficult to resolve such issue. And > UAC is becoming standard. > > There's two things that could change in p2: > 1. the error message could be saying something along the lines: "To perform > updates you need Administrator privileges" > 2. p2 could support privileges elevation, to get write permission to shared > pool I really like option #2. In fact, I brought this up on the p2 mailing list last month ;) [1]. However, it's the summer, and we actually haven't had a p2 meeting in weeks. Hopefully when everyone returns from vacation we can discuss this. Thanks for opening the other bugs. [1] http://dev.eclipse.org/mhonarc/lists/p2-dev/msg03283.html
