Touchpoint error in setup of PlatformSDKConfiguration via oomph

[peterkir]

Hi all,
when trying to setup the PlatformSDKConfiguration via latest oomph on win32
using this link

I'm getting the following error ERROR: org.eclipse.equinox.p2.touchpoint.natives code=0 The artifact for binary,org.eclipse.sdk.ide.executable.win32.win32.x86_64,4.38.0.I20250925-1800 is not available.

Also when switching Product version to Latest Release, the error persists.

Any help appreciated...

An error was detected while performing the engine operation and the changes are being rolled back. See the log for details.
ERROR: org.eclipse.equinox.p2.engine code=4 An error occurred while installing the items
  at org.eclipse.oomph.util.OomphPlugin.coreException(OomphPlugin.java:296)
  at org.eclipse.oomph.p2.internal.core.ProfileTransactionImpl$3.commit(ProfileTransactionImpl.java:578)
  at org.eclipse.oomph.p2.internal.core.ProfileTransactionImpl.commit(ProfileTransactionImpl.java:359)
  at org.eclipse.oomph.setup.p2.impl.P2TaskImpl.perform(P2TaskImpl.java:916)
  at org.eclipse.oomph.setup.internal.core.SetupTaskPerformer.doPerformNeededSetupTasks(SetupTaskPerformer.java:3876)
  at org.eclipse.oomph.setup.internal.core.SetupTaskPerformer.performNeededSetupTasks(SetupTaskPerformer.java:3804)
  at org.eclipse.oomph.setup.internal.core.SetupTaskPerformer.performTriggeredSetupTasks(SetupTaskPerformer.java:3785)
  at org.eclipse.oomph.setup.internal.core.SetupTaskPerformer.perform(SetupTaskPerformer.java:3663)
  at org.eclipse.oomph.setup.ui.wizards.ProgressPage$10.run(ProgressPage.java:612)
  at org.eclipse.oomph.setup.ui.wizards.ProgressPage$12$1.run(ProgressPage.java:741)
  at org.eclipse.core.internal.jobs.Worker.run(Worker.java:63)
  ERROR: org.eclipse.equinox.p2.engine code=0 session context was:(profile=C__IDEfix_platform-sdk_eclipse, phase=org.eclipse.equinox.internal.p2.engine.phases.Install, operand=null --> [R]org.eclipse.sdk.ide.executable.win32.win32.x86_64 4.38.0.I20250925-1800, action=org.eclipse.equinox.internal.p2.touchpoint.natives.actions.UnzipAction).
  ERROR: org.eclipse.equinox.p2.touchpoint.natives code=0 The artifact for binary,org.eclipse.sdk.ide.executable.win32.win32.x86_64,4.38.0.I20250925-1800 is not available.
Took 33 seconds.
There are failed tasks

[iloveeclipse]

I assume this is result of #3361.

[merks]

Usually when that happens I just try again. If that still doesn't work, then I try to clear the cache:

If that still doesn't work, then sometimes you have a wait a while:

https://gitlab.eclipse.org/eclipsefdn/helpdesk/-/issues/6088

Generally the underlying problem here is that the server is not serving the pair of files in a consistent state:

https://download.eclipse.org/justj/?file=eclipse/updates/4.38-I-builds/I20250925-1800

It might also be that the cache is not updated to this proper state, but that's controlled by the mod timestamp the server returns so also mostly a server caching issue.

In any case, looking in the artifacts.jar, that artifact with that version is in that repository:

So I don't expect this to a repeatable/persistent problem.

[merks]

ok. But why is it also affecting the installation, even if I select the Latest Release product.
I would expect that installation to be stable.

The SDK setup is designed to be eat your own dog food.

[peterkir]

Thx for the comprehensive anwser. I highly appreciate your time and the eat-your-own-dogfoot theme!
I think I got explanations (I alreay gave it multiple tries).

But still, one remark remaining.
While, using the own dogfoot, the release version of the product could reference the stable version of the oomph build instead of bleeding edge oomph (see attached pic 1).
This way it would be a stable "working" solution and backup for broken bleading edge cases, like today morning.
My assumption is that due to this oomph repo ref, the overall I build repos are dragged inside and a successful product installation is not feasible. (see attached pic 2)

Everything is working now. Thx again for your feedback.
I haven't closed it yet, do give you the chance to read my remarks ;-)

[merks]

It's the SWT setup that installs its own tools from the latest website:

I'm not 100% sure what these tools are for.

---

Which Oomph is used depends on which installer you use.

The default is this which points at the latest Oomph release

• https://download.eclipse.org/oomph/updates/milestone/latest

The nightly installers use this:

• https://download.eclipse.org/oomph/updates/latest

It's not unlikely that Oomph develops features used by the Platform "immediately" and I cannot remember the last time that Oomph has a regression because it's tested and used daily by many.

---

This morning had nothing to do with broken bleeding edge features, at least in the software itself. It's a perennial problem that the content and artifact metadata might be served out of sync for some period of time and in recent months the server increased the caching time making this problem more likely on composites that change. Of course pointing to a stable composite would avoid that.

But this really is not a frequent problem because many of us regularly pull all the repos and use Help -> Perform Setup tasks to update to the latest dog food.