Re: [cross-project-issues-dev] Neon.3 Update Problems: To Fix and How to Fix?

Ed Merks Tue, 25 Apr 2017 08:19:59 -0700

Fred,

No I didn't try that. It's much harder to try that. Oomph itself isbroken, so I can't run setup tasks. Check for Updates finds no updatesbecause I installed all the categories and their IUs don't have updatedversions. I tried explicitly installing Docker so that it would do anupdate, but that didn't not solve the wiring problem. I also runningthe p2 task in an IDE with Oomph 1.8 where I can run setup tasks(because Oomph's dependency on userstorage is optional in 1.8) and wherethe wiring problems also occurred so that more things got updated, butthis also did not resolve the wiring problem. So it's not clear ifupdates to an already -broken IDE will fix that IDE; it doesn't look sopromising, though I don't understand why that wouldn't work. Ifnothing requires a given bundle, I would expect that bundle to beremoved from the profile, but I don't see the problematic bundles beingremoved...


Regards,
Ed


On 25.04.2017 16:41, Frederic Gurr wrote:

Thanks Ed.

That sounds promising. Did you also test updating a broken ELWMS with
the new repo?

I'm currently trying to reproduce the error with EPP packages, but so
far updating a Neon.2 package to Neon.3 (with "Check for Updates") did
not result in a broken MPC. Not sure what I'm missing.

Regards,

Fred

On 25.04.2017 16:30, Ed Merks wrote:

Fred,

Installing the Eierlegende Wollmilchsau with this additional repository
in the p2 task's repository list results in an installation without
wiring problems.

The profile of the installation contains version 2.3.0.20170421191 of
org.eclipse.linuxtools.docker.core with is indeed the version available
in
https://hudson.eclipse.org/simrel/job/simrel.neon.3_respin.runaggregator.BUILD__CLEAN/3/artifact/aggregation/final
so I think this is a good demonstration that installations creation from
this repository's contents will not have the wiring problems we've been
seeing in Neon.3.

Regards,
Ed

Ed,

The temporary update site URL is:

https://hudson.eclipse.org/simrel/job/simrel.neon.3_respin.runaggregator.BUILD__CLEAN/3/artifact/aggregation/final


Regards,

Fred

On 25.04.2017 15:13, Ed Merks wrote:

Fred,

What update site URL contains these results?

Regards,
Ed


On 25.04.2017 14:28, Frederic Gurr wrote:

Thanks Jeff,

This is the comparison of the non-unique versions list:

neon3_respin aggregation build 20.04.
(https://hudson.eclipse.org/simrel/job/simrel.neon.3_respin.runaggregator.BUILD__CLEAN/2/artifact/aggregation/final/buildInfo/reporeports/reports/nonUniqueVersions.txt):



org.apache.httpcomponents.httpclient
      4.3.6.v201411290715
      4.5.2.v20161115-1643
      4.3.6.v201511171540
      4.2.6.v201311072007
org.apache.httpcomponents.httpcore
      4.3.3.v201411290715
      4.4.6.v20170210-0925
      4.2.5.v201311072007
      neon3_respin aggregation build 25.04.
(https://hudson.eclipse.org/simrel/job/simrel.neon.3_respin.runaggregator.BUILD__CLEAN/3/artifact/aggregation/final/buildInfo/reporeports/reports/nonUniqueVersions.txt):



org.apache.httpcomponents.httpclient
      4.3.6.v201411290715
      4.3.6.v201511171540
      4.2.6.v201311072007
org.apache.httpcomponents.httpcore
      4.3.3.v201411290715
      4.2.5.v201311072007


So o.a.h.httpclient version 4.5.2 and o.a.h.httpcore version 4.4.6 are
not in the repo any more.

@All: Can someone confirm that this fixes the update problem (earlier
version to Neon.3)?

If it is confirmed to work, we have a fix for users that have not
upgraded to Neon.3 yet. Users that already upgraded are unaffected by
this. They still need to wait for a "wiring issue" fix.

Regards,

Fred


On 21.04.2017 23:00, Jeff Johnston wrote:

Just to confirm that the change has been merged to the Neon.3_respin
branch.

-- Jeff J.

On Fri, Apr 21, 2017 at 4:11 PM, Jeff Johnston <jjohn...@redhat.com
<mailto:jjohn...@redhat.com>> wrote:

       I have done another respin.  In this case, I rebuilt the Linux
Tools
       plug-ins to use the older version
       of docker-client and its dependencies which were used in
Neon.2.  I
       have back-versioned the
       Docker tooling plug-ins to 2.3.0 with the current date.

       I have just pushed to gerrit for Neon.3_respin branch.

       https://git.eclipse.org/r/#/c/95501/
       <https://git.eclipse.org/r/#/c/95501/>

       If no-one objects, I will merge into the branch.
Verification is
       already successful.

       -- Jeff J.

       On Fri, Apr 21, 2017 at 11:50 AM, Jeff Johnston
<jjohn...@redhat.com
       <mailto:jjohn...@redhat.com>> wrote:

           Marcel,

           Since the respin didn't fix the problem, we will try
reverting
           the docker-client dependency and keeping as much of the
added
           Neon.3 functionality as possible
           in place and cutting another point release.  I will let the
list
           know when I have something in place.

           -- Jeff J.

           On Fri, Apr 21, 2017 at 6:38 AM, Daniel Megert
           <daniel_meg...@ch.ibm.com <mailto:daniel_meg...@ch.ibm.com>>
wrote:

               Adding eclipse.org-planning-coun...@eclipse.org
               <mailto:eclipse.org-planning-coun...@eclipse.org> to
this
               thread.

               Dani



               From:        "Dr. Marcel Bruch"
<marcel.br...@codetrails.com
               <mailto:marcel.br...@codetrails.com>>
               To:        Cross project issues
               <cross-project-issues-dev@eclipse.org
               <mailto:cross-project-issues-dev@eclipse.org>>
               Date:        21.04.2017 10:17
               Subject:        Re: [cross-project-issues-dev] Neon.3
Update
               Problems: To Fix and        How to Fix?
               Sent by:
cross-project-issues-dev-boun...@eclipse.org
               <mailto:cross-project-issues-dev-boun...@eclipse.org>

------------------------------------------------------------------------





               Hi,

               I’ll briefly summarize the discussion we had at the AC
               yesterday:

               Given that we don’t know how the OSGI resolver will
behave
               (even after Tom back-ported a fix to Neon) it would be
               preferred to just have the Apache HTTP*** versions in
Neon.3
               that were already in Neon.2. This would to some extend
               “ensure" that we are "at least as as stable as Neon.2”.
This
               would require us to rollback the changes that introduced
the
               latest version of HTTPClient. As far as I know this
would
               especially affect the Docker Tooling. (maybe more
changes
               than that are needed)

               My question to the *Docker Tooling project lead*: Is it
               possible to rollback this last minute change and
postpone it
               to Oxygen for the sake of making EGit, MPC, Oomph,
USS, and
               Code Recommenders work reliably again - and giving us
more
               trust that we won’t get into trouble with Neon.3? The
               simplest solution may be to contribute the docker
tooling
               from Neon.2 in Neon.3. WDYT?

               Marcel




               On 20 Apr 2017, at 18:54, Frederic Gurr
               <_frederic.gurr@eclipse.org_
               <mailto:frederic.g...@eclipse.org>> wrote:

               I can see

org.apache.httpcomponents.httpclient_4.5.2.v20170210-0925 in/home/data/httpd/_download.eclipse.org/linuxtools/update-docker-2.3.1/plugins_

<http://download.eclipse.org/linuxtools/update-docker-2.3.1/plugins>,

               but it's definitely not in the aggregated repo.


               On 20.04.2017 18:31, Jeff Johnston wrote:
               Fred,

               The version of httpclient also changed in our
               update-docker-2.3.1 repo from:

org.apache.httpcomponents.httpclient_4.5.2.v20161115-1643

to:

org.apache.httpcomponents.httpclient_4.5.2.v20170210-0925


               Not sure why this change isn't being seen as well.

               -- Jeff J.



               On Thu, Apr 20, 2017 at 12:21 PM, Frederic Gurr
               <_frederic.gurr@eclipse.org_

<mailto:frederic.g...@eclipse.org><_mailto:frederic.gurr@eclipse.org_

               <mailto:frederic.g...@eclipse.org>>> wrote:

                 Thanks Jeff,

                 I ran a SimRel aggregation build. The only change I
can
               see in the list
                 of "Non Unique Versions used in repository" is that a
               different version
                 of org.apache.httpcomponents.httpcore is now used.
Instead of
                 4.4.4.v20161115-1643 it's now 4.4.6.v20170210-0925.

                 I compared

_http://download.eclipse.org/releases/neon/201703231000/buildInfo/reporeports/reports/nonUniqueVersions.txt_

<http://download.eclipse.org/releases/neon/201703231000/buildInfo/reporeports/reports/nonUniqueVersions.txt>

<_http://download.eclipse.org/releases/neon/201703231000/buildInfo/reporeports/reports/nonUniqueVersions.txt_

<http://download.eclipse.org/releases/neon/201703231000/buildInfo/reporeports/reports/nonUniqueVersions.txt>>

and

_https://hudson.eclipse.org/simrel/job/simrel.neon.3_respin.runaggregator.BUILD__CLEAN/ws/aggregation/final/buildInfo/reporeports/reports/nonUniqueVersions.txt_

<https://hudson.eclipse.org/simrel/job/simrel.neon.3_respin.runaggregator.BUILD__CLEAN/ws/aggregation/final/buildInfo/reporeports/reports/nonUniqueVersions.txt>

<_https://hudson.eclipse.org/simrel/job/simrel.neon.3_respin.runaggregator.BUILD__CLEAN/ws/aggregation/final/buildInfo/reporeports/reports/nonUniqueVersions.txt_

<https://hudson.eclipse.org/simrel/job/simrel.neon.3_respin.runaggregator.BUILD__CLEAN/ws/aggregation/final/buildInfo/reporeports/reports/nonUniqueVersions.txt>>




                 @All: is that the intended result?

                 Regards,

                 Fred


                 On 19.04.2017 20:21, Jeff Johnston wrote:
               Hi Fred,

               I have just pushed a change to gerrit:
                  _https://git.eclipse.org/r/#/c/95308/_
               <https://git.eclipse.org/r/#/c/95308/>
                 <_https://git.eclipse.org/r/#/c/95308/_
               <https://git.eclipse.org/r/#/c/95308/>>

               I only changed the docker repository and left the other
               Linux Tools
               features alone
               since they were only bumped as part of the point
release to
               fix the
               Docker Tooling plug-ins.

               I assume I can merge the patch if the gerrit
verification is
               successful.  If this is wrong,
               let me know.

               -- Jeff J.

               On Wed, Apr 19, 2017 at 1:08 PM, Frederic Gurr
               <_frederic.gurr@eclipse.org_

<mailto:frederic.g...@eclipse.org><_mailto:frederic.gurr@eclipse.org_

               <mailto:frederic.g...@eclipse.org>>
                  <_mailto:frederic.gurr@eclipse.org_
               <mailto:frederic.g...@eclipse.org>
                 <_mailto:frederic.gurr@eclipse.org_
               <mailto:frederic.g...@eclipse.org>>>> wrote:

                 Hi,

                 Can you provide a patch for the SimRel build (branch
                  "Neon.3_respin")
                  that references the new version?

                 Regards,

                 Fred

                 On 19.04.2017 17:27, Jeff Johnston wrote:
               Hi Ed,

               Linux tools spun a 5.3.1 release which now has a 2.3.1
                  version of
                  docker
               tooling.  The Linux tools download site has
                  update-docker-2.3.1 and
               update-docker, both which have 2.3.1 versions of the
docker.core
                  plug-in
               and docker feature.  Not sure why you are not seeing
this.

               -- Jeff J.

               On Wed, Apr 19, 2017 at 11:13 AM, Ed Merks
                  <_ed.merks@gmail.com_
               <mailto:ed.me...@gmail.com><_mailto:ed.merks@gmail.com_
               <mailto:ed.me...@gmail.com>>

<_mailto:ed.merks@gmail.com_<_mailto:ed.merks@gmail.com_

               <mailto:ed.me...@gmail.com>>>
               <_mailto:ed.merks@gmail.com_<_mailto:ed.merks@gmail.com_
               <mailto:ed.me...@gmail.com>>

<_mailto:ed.merks@gmail.com_<_mailto:ed.merks@gmail.com_

               <mailto:ed.me...@gmail.com>>>>> wrote:

                 Frederic,

                 There seem to have been no notes/minutes taken during
                  the meeting:

_https://wiki.eclipse.org/Planning_Council/April_05_2017_<https://wiki.eclipse.org/Planning_Council/April_05_2017><_https://wiki.eclipse.org/Planning_Council/April_05_2017_<https://wiki.eclipse.org/Planning_Council/April_05_2017>><_https://wiki.eclipse.org/Planning_Council/April_05_2017_<https://wiki.eclipse.org/Planning_Council/April_05_2017><_https://wiki.eclipse.org/Planning_Council/April_05_2017_<https://wiki.eclipse.org/Planning_Council/April_05_2017>>><_https://wiki.eclipse.org/Planning_Council/April_05_2017_<https://wiki.eclipse.org/Planning_Council/April_05_2017><_https://wiki.eclipse.org/Planning_Council/April_05_2017_<https://wiki.eclipse.org/Planning_Council/April_05_2017>><_https://wiki.eclipse.org/Planning_Council/April_05_2017_<https://wiki.eclipse.org/Planning_Council/April_05_2017><_https://wiki.eclipse.org/Planning_Council/April_05_2017_<https://wiki.eclipse.org/Planning_Council/April_05_2017>>>>


                 I recall agreeing to provide steps for reproducing the
                  problem so
                  that Thomas Watson could test if the wiring
resolution
                  fix he made
                  for Oxygen also solves the problem for Neon.3.
The fact
                  that he
                  encountered "the mirroring problem" didn't help in
that
                  regard:

_https://bugs.eclipse.org/bugs/show_bug.cgi?id=515213_

               <https://bugs.eclipse.org/bugs/show_bug.cgi?id=515213>