Hi,
I had a closer look at the issue. I found, that
for the 2019-12 release the version of MPC that was promoted
for Release and Simrel Composite was newer than the one in
the epp-mpc.aggrcon file. That might have caused the problem
to occur even more often. I double checked that this will be
correct for the 2020-03 release.
Also I was able to reproduce the problem:
An error occurred while collecting items to be
installed
session context was:(profile=""
phase=org.eclipse.equinox.internal.p2.engine.phases.Collect,
operand=, action="">
No repository found containing:
osgi.bundle,com.sun.jna,4.5.1.v20190425-1842
No repository found containing:
osgi.bundle,com.sun.jna.platform,4.5.1.v20190425-1842
No repository found containing:
osgi.bundle,org.apache.httpcomponents.httpclient.win,4.5.6.v20190213-1947
No repository found containing:
osgi.bundle,org.eclipse.epp.mpc.core,1.7.7.v20190521-1752
No repository found containing:
osgi.bundle,org.eclipse.epp.mpc.core.win32,1.7.7.v20190521-1752
No repository found containing:
osgi.bundle,org.eclipse.epp.mpc.help.ui,1.7.7.v20190521-1752
No repository found containing:
osgi.bundle,org.eclipse.epp.mpc.ui,1.7.7.v20190521-1752
No repository found containing:
osgi.bundle,org.eclipse.epp.mpc.ui.css,1.7.7.v20190521-1752
No repository found containing:
osgi.bundle,org.apache.httpcomponents.httpclient,4.5.6.v20190503-0009
No repository found containing:
org.eclipse.update.feature,org.eclipse.epp.mpc,1.7.7.v20190521-1752
Updating only MPC to 1.7.7 does not work
directly after the above steps but works after restart of
eclipse and then updating eclipse works like charm.
Being easy reproduceable, I doubt that this is
some kind of caching problem here. As Ed mentioned, it does
not look like a MPC problem either. Of course, we could
deactivate the update mechanism of MPC for RC2, which might
reduce the number of problems, but does not solve the root
problem and of course makes MPC updates harder for all our
users that do not have this problem. Any opinions?
Leif
Product Manager & Software Engineer
--
+49
(0)69 2475666-22 |
leif.geiger@xxxxxxxx
| www.yatta.de
Yatta
Solutions GmbH c/o WeWork · Neue Rothofstraße 13-19 · 60313
Frankfurt a.M. (Germany)
Registered Seat: AG Kassel, HRB 14720 · VAT-ID DE263191529 ·
Managing Director Johannes Jacop
From:
cross-project-issues-dev-bounces@xxxxxxxxxxx
<cross-project-issues-dev-bounces@xxxxxxxxxxx>
On Behalf Of Jonah Graham
Sent: Saturday, February 22, 2020 2:59 PM
To: Cross project issues
<cross-project-issues-dev@xxxxxxxxxxx>
Subject: Re: [cross-project-issues-dev] weird MPC
versions causing grief
Hi Ed.
> Another potential cause is that
the download.eclipse.org server
will continue to serve old cache versions of files that
are actually updated in the file system. So, it's
possible that one updates a repository in the file system,
and then a client might see a newer version of the
compositeContent.jar/content.jar but an older version of
the compositeArtifacts.jar/artifacts.jar.
Stephan,
Having triaged the ~635 p2 bugs down to < 270, and
looking at each report's details, I can see that this is
a recurring theme. No doubt it's aggravated (made more
common) by MPC encouraging an update to their latest
release, that release being slightly newer than what's
on the release train, and that happening right after the
release when the server is likely overloaded making
network failures even more likely. I.e., the users see
this:

In any case, there is an interesting related
observation in this older bug:
https://bugs.eclipse.org/bugs/show_bug.cgi?id=410721#c3
Inevitably this problem is caused by an inconsistency
between the IUs found in the content metadata versus the
corresponding artifacts available in the artifact
metadata. There can be a number of possible causes,
including inconsistencies in the repos themselves, but
that does not appear to be the case with these MPC
repos; I inspected the repos and I tried to reproduce
the problem, unsuccessfully (even when removing the
profile preference for the artifact repository
manually). Another potential cause is that the download.eclipse.org server
will continue to serve old cache versions of files that
are actually updated in the file system. So, it's
possible that one updates a repository in the file
system, and then a client might see a newer version of
the compositeContent.jar/content.jar but an older
version of the compositeArtifacts.jar/artifacts.jar.
In the above bug, apparently p2 has not recorded the
corresponding artifact repository in the profile-scoped
preferences for whatever mysterious reason; perhaps a
network failure loading the artifact repository and that
apparently leads to this same type of problem.
Unfortunately these are generally all scenarios that are
very hard to reproduce, but they leave the user
scrambling why they have a problem but their team mates
do not...
Regards,
Ed
On 20.02.2020 20:32, Stephan
Herrmann wrote:
We've been getting some desperate
bug reports about failing installations, all
mentioning that mpc artifacts cannot be found. This
already happened with version 1.7.7 but today I found
some weirdness regarding version 1.8.1:
Eclipse fails to update saying:
No repository found containing:
osgi.bundle,org.eclipse.epp.mpc.core,1.8.1.v20191107-0507
No repository found containing:
osgi.bundle,org.eclipse.epp.mpc.ui,1.8.1.v20191119-1757
No repository found containing:
org.eclipse.update.feature,org.eclipse.epp.mpc,1.8.1.v20191119-1757
but the published version is actually
1.8.1.v20191106-1317 for all of the above.
How did the above versions leak to users, and what can
they do to fix their updating?
Stephan
https://bugs.eclipse.org/bugs/show_bug.cgi?id=548197
https://bugs.eclipse.org/bugs/show_bug.cgi?id=551641
https://bugs.eclipse.org/bugs/show_bug.cgi?id=560062
https://bugs.eclipse.org/bugs/show_bug.cgi?id=560006
(with duplicate)
_______________________________________________
cross-project-issues-dev mailing list
cross-project-issues-dev@xxxxxxxxxxx
To change your delivery options, retrieve your
password, or unsubscribe from this list, visit
https://www.eclipse.org/mailman/listinfo/cross-project-issues-dev
_______________________________________________
cross-project-issues-dev mailing list
cross-project-issues-dev@xxxxxxxxxxx
To change your delivery options, retrieve your password,
or unsubscribe from this list, visit
https://www.eclipse.org/mailman/listinfo/cross-project-issues-dev