Bugzilla – Full Text Bug Listing
| Summary: | [revert] Improve handling of failing to revert | ||
|---|---|---|---|
| Product: | [Eclipse Project] Equinox | Reporter: | Miles Daffin <miles.daffin> |
| Component: | p2 | Assignee: | Pascal Rapicault <pascal> |
| Status: | CLOSED WONTFIX | QA Contact: | |
| Severity: | blocker | ||
| Priority: | P3 | CC: | daniel_megert, irbull, ldubox-coding101, mamacdon, markus.kell.r, pascal, pdecat, simioni.eduardo, thomas |
| Version: | unspecified | ||
| Target Milestone: | --- | ||
| Hardware: | All | ||
| OS: | All | ||
| See Also: | https://bugs.eclipse.org/bugs/show_bug.cgi?id=464700 | ||
| Whiteboard: | stalebug | ||
|
Description
Miles Daffin
Pascal, this is assigned to you. Any thoughts? The fact that this is failing in the collect phase, indicates to me that it's missing the artifacts (or at least the artifact descriptors). I have the same problem, could never revert an update. Updated to Juno yesterday but for some reason I cannot add breakpoints to Aspect code anymore, therefore I tried to revert, no matter which previous installation I select I cannot revert, I get the no repository found for apparently every component that is different between the 2 installations. Could you please provide steps to reproduce the problem? Are you trying to revert from Juno to Indigo? Yes, I'm trying to revert from Juno to Indigo, Windows 7 64bit, Eclipse JEE 64bit also. I cannot tell for sure the steps to reproduce, but my scenario was: - Installed Indigo (sometime ago) - Added some plugins (AJDT, EclEmma, JRebel, SVN, Maven Integration for WTP) - Updated them while using Indigo - Updated to Juno - Tried to revert I believe the error is reproducible even without any plugin. I downloaded a fresh and clean Indigo to try to do that, but when I check for updates it says that "No updates were found", oddly enough my old Indigo offered to update to Juno. Forgot to mention that all plugins were installed from Eclipse Marketplace. The cause of the failure to revert from juno back to indigo is because the indigo repository is not available since updating from indigo to juno removes the indigo repo. You can try adding the http://download.eclipse.org/releases/indigo back and this should help for some cases. Going forward we may want to change p2 to: - explain why the revert is failing. - persist the repositories that were enabled at the time of the install Would be really nice to have a 'continue anyway' option (with warning about knowing what you're doing / things might get messed up, if appropriate). Or even better, an option for a selective revert. Background: I'm trying to troubleshoot a significant performance degradation between 4.4M5 & 4.4M6, and would like to roll back, and then selectively apply updates to work out which feature to log a ticket against. (My initial report was immediately closed as "need more info".) Unfortunately 2 features are unable to roll back: * Java JDK 8 Beta support (repository probably removed now it's official?) * eclemma (code coverage) I _really_ don't care about these features; in fact I uninstalled them hoping that might work around the failure to revert. (Of course I suppose the revert would try to put them back anyway.) (Oh well, for my particular procedure perhaps it'll be faster to keep a zipped copy of a fresh 4.4M5 installation to revert back to anyway.) This is a blocker. Users must be able to either - continue a Revert operation even if some features cannot be reverted - or revert individual features - or install an older version of a specific feature. Eclipse SDK I20150113-0800 is broken, and I don't see a way to go back to I20150106-0800. The problem is that I also updated EGit from 3.7.0.201501080747 to 3.7.0.201501160908 in the same update operation, but now the http://download.eclipse.org/egit/updates-nightly/ update site doesn't contain the old EGit version any more. I20150106-0800 works perfectly with the newer EGit version, but there's no UI to fix my install. !ENTRY org.eclipse.equinox.p2.engine 4 4 2015-01-16 14:13:19.209 !MESSAGE An error occurred while collecting items to be installed !SUBENTRY 1 org.eclipse.equinox.p2.engine 4 0 2015-01-16 14:13:19.209 !MESSAGE session context was:(profile=SDKProfile, phase=org.eclipse.equinox.internal.p2.engine.phases.Collect, operand=, action=). !SUBENTRY 1 org.eclipse.equinox.p2.artifact.repository 4 0 2015-01-16 14:13:19.209 !MESSAGE No repository found containing: org.eclipse.update.feature,org.eclipse.egit,3.7.0.201501080747 !SUBENTRY 1 org.eclipse.equinox.p2.artifact.repository 4 0 2015-01-16 14:13:19.209 !MESSAGE No repository found containing: org.eclipse.update.feature,org.eclipse.jgit,3.7.0.201501071923 !SUBENTRY 1 org.eclipse.equinox.p2.artifact.repository 4 0 2015-01-16 14:13:19.209 !MESSAGE No repository found containing: org.eclipse.update.feature,org.eclipse.jgit.java7,3.7.0.201501071923 (In reply to Markus Keller from comment #8) > This is a blocker. Users must be able to either > - continue a Revert operation even if some features cannot be reverted > - or revert individual features > - or install an older version of a specific feature. Reverting is designed to be an all or nothing operation that takes you back to a state that you once were in, as such reverting partially does not really make sense w/o any user warning / consent (e.g. something like the remediation workflow). As for installing an older version of a feature, this is something that is only supported through the command line. GUI wise, I'm not sure where / how we would allow a user. Note in order to perform something meaningful here, we would have to improve the representation of the download failure in order to find the IU that actually caused the problem, and at this point prompt the user. https://wiki.eclipse.org/FAQ_Revert_an_Update_or_Installation_with_p2#Revert_doesn.27t_work lists manual steps to revert using the p2 director from another Eclipse install. 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. -- The automated Eclipse Genie. |