|Re: [cross-project-issues-dev] weird MPC versions causing grief|
Oh, dang! I think I found the issue... Looking at the code for this: > One thing that I think should be fixed regardless of the current grief is that in > the process of checking for updates, MPC potentially adds new repos to the > list and doesn't clean them up again (as so aptly expressed in > https://bugs.eclipse.org/bugs/show_bug.cgi?id=560062#c12). I'll open a new > bug for this. I noticed that for the update check we only ever load the metadata repository - and then leave it lying around (and it's been like that since the dawn of time, or MPC 1.0 in Helios to be precise). That isn't harmful as long as the repo was already in the list of available update sites, which is the case most of the time. But if it wasn't (my previous example with version-specific sites, and also frequently the case with MPC itself, since it came from simrel and not its own repo), then we now have an update site list with just a metadata repo and no corresponding artifact repo, which would completely explain the observed errors.
Back to the top