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@eclipse.org
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@eclipse.org
To change your delivery options, retrieve your password, or unsubscribe from
this list, visit
https://www.eclipse.org/mailman/listinfo/cross-project-issues-dev
