Hi,
Some Papyrus Neon bundles are version 1.2 because they don’t have API-breaking changes and others are at 2.0 because they have API-breaking changes.
This is probably just the usual case of trying to run the Oomph setup to pull content from a p2 repository that is in the process of being replaced. While the Papyrus build is publishing its repository, the repository is at least partially non-existent and so an update from it will fail like this.
If the problem still occurs on a re-try ten minutes later, then maybe there’s a problem in the Oomph set-up.
But, the Oomph setup is currently referencing the Papyrus nightly build repositories on the assumption that we need to keep up-to-date with Papyrus development as closely as possible, given the intimate nature of our dependency on that project. If Papyrus had a policy of publishing weekly integration builds as many Eclipse projects do, that would help a lot because then then we wouldn’t have these repositories that are temporarily unavailable several times a day. Or, if the Papyrus-RT development team is content with only picking up the latest stable milestone build of Papyrus, we can change the setup model accordingly.