Hi Ed, upgrades from older EPP packages, such as Mars packages (or to be really precise: all EPP packages with EPP package version <4.6.0.20160301-1200) had to be prevented by p2 because we changed their internal structure in an incompatible way. EPP package upgrades from e.g. M7 to RC3, or RC1 to the final release are expected to work. The details and reasons are covered in bug 332989 [1] and in bug 490515 [2] (and in some mailing list discussions).
If (just in theory!) we would not prevent an exemplary Mars -> Neon upgrade of an EPP package, the user would see a successful upgrade, but loose most of the package content. The reason for this is that we moved the dependencies that used to define the package content from the EPP "feature" to the root of the package. The positive effect is that it is now possible to uninstall unwanted parts from a package, and for projects it is important to realize that they can roll out updates independent from the EPP package. The downside of this structural change is that it was not possible for us to provide a good upgrade story. But if you are using Oomph you should be able to switch between Simultaneous Releases in a smooth way. I hope that helps understand the background better. Thanks, Markus [1] https://bugs.eclipse.org/bugs/show_bug.cgi?id=332989 [2] https://bugs.eclipse.org/bugs/show_bug.cgi?id=490515 On 16 June 2016 at 10:35, Ed Willink <[email protected]> wrote: > Hi David > > I'm confused. Why is "not be allowed to update" expected and what is the > "previous > EPP"? > > I thought that we were trying to ensure that update works. > > I can understand that a Neon RC4 to RC4a update might be undersirable due > to evictions and UUID policies, but surely everything else should work? > Chuck out all old plugins incompatible with the new, or in features > replaced by the new, then go. I have observed that this often fails when > e.g upgrading Xtext without uninstalling all downstream dependencies first, > P2 does not allow the required multiple update from ZIP needed to resolve > this preferring to report a plethora of ambiguities from stale update sites > contributed by projects. But for a SimRel upgrade, all the replacements > should be there, so surely replace and evict should just work? > > Regards > > Ed Willink > On 16/06/2016 00:13, David M Williams wrote: > > My apologies for not communicating more quickly the information back to > this list. Entirely my oversight. > > The final EPP packages themselves are available from: > > > *https://hudson.eclipse.org/packaging/job/neon.epp-tycho-build/388/artifact/org.eclipse.epp.packages/archive/* > <https://hudson.eclipse.org/packaging/job/neon.epp-tycho-build/388/artifact/org.eclipse.epp.packages/archive/> > > If anyone wants to try an "update scenario you should use the following > two repositories. (And have only them enabled.) > > But, remember, the main "test result" ... at least from previous EPP > installations ... is that you should "not be allowed to update". If you > were, the new installation would be broken since there was such a large > change in structure from previous (Mars) version of EPP packages. > > *http://download.eclipse.org/technology/epp/packages/neon/RC4/* > <http://download.eclipse.org/technology/epp/packages/neon/RC4/>and > *http://download.eclipse.org/staging/neon/* > <http://download.eclipse.org/staging/neon/> > > Assuming no "catches the machine on fire" type bugs these will become our > Neon release on 6/22. > > Thanks, > > > > > > From: Matthias Sohn <[email protected]> > <[email protected]> > To: Cross project issues <[email protected]> > <[email protected]>, > Date: 06/15/2016 06:05 PM > Subject: Re: [cross-project-issues-dev] Respin of SimRel > Repository required > Sent by: [email protected] > ------------------------------ > > > > any update on the current status of the repository and availability of > packages for testing ? > > On Mon, Jun 13, 2016 at 6:07 PM, David M Williams < > *[email protected]* <[email protected]>> wrote: > Extended team, > > I am beginning a re-spin of the Sim. Release repository. > > Two major changes: SOA-BPN2 modeler removed and Window Builder removed. > > The former removed because they didn't finish the normal release > requirements. The later was removed because it has not been tested with the > Neon candidate release. (It did recently, after RC4, get a build which > "removed one line of code" which prevented it from running on Neon ... but, > our goal is not for projects to "join at the last minute" but to be part of > the train for many milestones so it can be adequately tested). > > It is my understanding both projects plan to "rejoin the train" in the > September release. > > A minor change: Linux Tools found a major memory leak which would normally > not be "respin worthy", but I told them if we had to respin for other > reasons they could include a fix for that. > > The EPP packages will need to be rebuilt of course -- first because they > always are if the repository changes, but more so this time because Window > Builder was included in two EPP packages and of course will have to be > removed from those packages. > > I will update this list once both steps are complete. > > Thanks, > > > > > _______________________________________________ > cross-project-issues-dev mailing list > *[email protected]* > <[email protected]> > To change your delivery options, retrieve your password, or unsubscribe > from this list, visit > *https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev* > <https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev> > _______________________________________________ > cross-project-issues-dev mailing list > [email protected] > To change your delivery options, retrieve your password, or unsubscribe > from this list, visit > https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev > > > > _______________________________________________ > cross-project-issues-dev mailing [email protected] > To change your delivery options, retrieve your password, or unsubscribe from > this list, > visithttps://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev > > > > _______________________________________________ > cross-project-issues-dev mailing list > [email protected] > To change your delivery options, retrieve your password, or unsubscribe > from this list, visit > https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev >
_______________________________________________ cross-project-issues-dev mailing list [email protected] To change your delivery options, retrieve your password, or unsubscribe from this list, visit https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev
