[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [p2-dev] how to make p2 install fail gracefully
- From: Andrew Eisenberg <andrew@xxxxxxxxxxxx>
- Date: Tue, 7 Dec 2010 14:03:56 -0800
- Delivered-to: email@example.com
- Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:sender:reply-to:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:cc:content-type :content-transfer-encoding; b=Ji3I8OYvF5fCmHRyJCEF861S7ZVtW3Qesw4G8GI2K7CIqSYqpG/yADMk38RSlVPmpA P0aDaNRM60X01Qjn9gI8IJMCrF1MA7WQt8XHHg2h0m5DfgtAH6ggJAe9dUqVewo9PRB6 tBAQeW8P8dRbZklFpTGu5qd7DK/yFWqbaWiAU=
I believe that this is a problem with feature patches specifically. I
was aware of the shared install bug that was fixed for 3.6.1, but it
doesn't seem to have fixed the feature patches issue (it only made
diagnosing the problem more cryptic :( ). I have not actually
reproduced this on my machine. I just know from users that when they
changed their install directory to writable, then they were able to
If there's not a straightforward solution, then should I write up some
steps to reproduce and raise a bug?
On Tue, Dec 7, 2010 at 9:56 AM, Ian Bull <irbull@xxxxxxxxxxxxxxxxx> wrote:
> This should work (install in a read-only directory). In this case, Eclipse
> actually does the install ~<username>/.eclipse. Of course, if that is also
> read-only, then we are probably out of luck.
> There was a bug in 3.6.0 that caused some problems, but that was fixed in
> So a few questions, are you using 3.6.1? If you are using 3.6.1, are the
> results predictable (or do you get different behavior based on the weather
> ;)? I wonder if there is a problem with feature-patches and shared
> On Tue, Dec 7, 2010 at 8:45 AM, Andrew Eisenberg <andrew@xxxxxxxxxxxx>
>> Hi all,
>> Is there some way that I can force a p2 install to fail gracefully
>> when there is an attempt to use the update manager to install some
>> features in a read-only directory?
>> Longer explanation:
>> Groovy-Eclipse installs with a feature patch for jdt.core. When the
>> install directory is read-only, the installation fails, but in
>> unpredictable ways. Sometimes the installation itself is
>> "successful", but the features fail to load on restart (and worse,
>> sometimes this causes JDT to fail to load).
>> So, I would like p2 to generate an error message and abort the
>> installation if it detects that the install directory is read only.
>> Of course, I'd prefer to be able to successfully install even when
>> read-only, but my thinking is that the graceful failure is an easier
>> p2-dev mailing list
> R. Ian Bull | EclipseSource Victoria | +1 250 477 7484
> http://eclipsesource.com | http://twitter.com/eclipsesource