Open jukzi opened 10 months ago
Yes, this happens occasionally with no known way to reproduce the problem unfortunately. I don't even have a good theory for how the artifact got into the pool while at the same time the p2 seems to think it needs to download the artifact because it's not yet in the pool. Perhaps something put the artifact into the pool folder but failed to update the artifact metadata to reflect that fact.
related question: why is the pool used at all? I disabled it:
There's always a pool, even if not a shared one. That setting disables it for the p2 director task, i.e., so that the p2 direct creates an installation where its pool is colocated with (nested in) the installation. This has no affect on targlets.
I was not able to OOmph Platform workspace today on first try. I do not understand the error message: The error message gone when i retried using "back" and "finish"