|Re: [cross-project-issues-dev] weird MPC versions causing grief|
Matthias,It's certainly related, but here the list of not-found things is much larger suggesting that not just MPC's artifact repository is missing...
Another potential source of unpaired-preference problems is the addRepository touchpoint which must specifies pairs of repos, e.g.,
https://git.eclipse.org/c/platform/eclipse.platform.releng.aggregator.git/tree/eclipse.platform.releng.tychoeclipsebuilder/sdk/sdk.p2.infSo ill-specified touchpoints could also lead to problems, but I don't see any of such bad touchpoints on the 2020-03 release train so that's probably a red herring...
The bug you point to has a hack workaround Gerrit patch that makes bad assumptions about 1:1 mapping of content and artifact repositories. So that leaves one wondering how could this problem (at least the problem of inconsistently paired repository preferences) be more generally addresses? Only actually trying to load each enabled content repo's URI also as an artifact repo URI and verifying that there is a corresponding one at that same location would be safe, though potentially expensive. And when/where should that "fixup pass" be done?
It's also unfortunate that the improper preference state is not something that the user can actually see in the preferences page. I believe the Reload button would fix it, but there are bugs open that claim that this does not even property refresh either one but rather uses the cache in the file system, though I doubt that claim.
In general, p2 is much used yet receives too little care and attention. I've managed to triage the list of open problems from ~635 down to a more manageable ~225, but that was more than a week of effort. Here's what left now:
https://bugs.eclipse.org/bugs/buglist.cgi?bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&classification=Eclipse%20Project&component=p2&list_id=19260862&order=bug_id%20DESC&product=Equinox&query_format=advanced And then a new problem like this is opened, also directly related: https://bugs.eclipse.org/bugs/show_bug.cgi?id=560795But good luck getting a response from the reporter. I'll dup it to 410721 if there is no response...
Regards, Ed On 06.03.2020 09:50, Becker, Matthias wrote:
Hi all, is this maybe also the cause for https://bugs.eclipse.org/bugs/show_bug.cgi?id=410721? Regards, Matthias On 05.03.20, 20:12, "cross-project-issues-dev-bounces@xxxxxxxxxxx on behalf of Leif Geiger" <cross-project-issues-dev-bounces@xxxxxxxxxxx on behalf of leif.geiger@xxxxxxxx> wrote: Hi,thanks, Carsten, for your work on this issue and Ed for your input. Great that you found the root cause and are able to provide a fix. Once you have committed the fix, I will test it and include it for RC2. Regarding the mechanism to fix the update sites: I have tested a bit more and found out that restarting eclipse does in fact add the artifact repositories for MPC. So after restart (which most users will do after an update to the fixed MPC), everything works fine. So I guess, such a repair mechanism does not help much. Best regards,Leif-----Original Message-----From: cross-project-issues-dev-bounces@xxxxxxxxxxx <cross-project-issues-dev-bounces@xxxxxxxxxxx> On Behalf Of Carsten Reckord Sent: Thursday, March 5, 2020 6:11 PM To: Cross project issues <cross-project-issues-dev@xxxxxxxxxxx> Subject: Re: [cross-project-issues-dev] weird MPC versions causing grief> I noticed that for the update check we only ever load the metadata> repository [...] we now have an update site list with just a metadata > repo and no corresponding artifact repo, which would completely > explain the observed errors.Now I'm wondering if we should attempt to fix the update site list retroactively, i.e. scan for all metadata repos in the list that don't have a corresponding artifact repo, and add it. Theoretically, there could be cases where there is no 1:1 mapping between the two, but I think the common case is that both should exist. Opinions? _______________________________________________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_______________________________________________ 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
Back to the top