Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [cross-project-issues-dev] p2 <-> aggregator sync.


I'm concerned about how these new repos will impact older installations.  I've been assured that older installations (older versions of p2) will not see the newer metadata so that this is not a problem.  But I have yet to fully test how an Eclipse Installer running with Photon p2 behaves in terms of creating an Oxygen installation; a Profile is a p2 repository so it is likely to contain the new form of metadata.  (It was definitely failing for early Photon versions of p2, so I'm concerned too about the installer being stuck on Oxygen.) When the Oxygen runtime starts up with the Profile produced by Photon p2 containing the new p2 metadata, does that actually work?  I believe and hope with the current modified approach taken in p2 that that does work, but I remain concerned nevertheless.

Similarly for moving the CBI aggregator up, and for producing repos with the new format.  We really do want to be 100% sure that Oxygen can update to Photon, right?   If that doesn't work, p2 likely needs more attention, but in the meantime it would be good to avoid producing so many repos (long lived ones) that might be problematic...

In any case, the M4 version of Oomph should work with the latest version of p2, so it's not Oomph that you need to update but rather just p2.


On 28.01.2018 18:48, Stephan Herrmann wrote:
I've been observing conflicts between recent changes in p2
and the CBI aggregator for some weeks [1].

Today, I triggered a gerrit test with latest from Object Teams,
which is provided as a repo created by latest from p2 (as of M5).

Result [2]:
Unable to load repository p2:file:///home/data/httpd/
While I don't see the actual root error, this appears to be the case
were the aggregator cannot handle current format of p2 meta data.
(Any chance to access any details of this failure?)

When I locally install the latest CBI aggregator from
I can successfully validate and build the aggregation.
Smoke tests of installing from that locally built repo show
no problems.

How do folks feel about either of
 A upgrading to latest from CBI aggregator?
 B ensuring that no project in simrel uses p2 > Photon M3 for their contribution?
   B.1: how long can be "freeze" p2 at Oxygen level??

We have no plan C for M5.

BTW, kudos to David Williams for doing the necessary maintenance
to keep the aggregator alive [3].

A fine point: I found no way to upgrade the Oomph-based SimRel
workbench to latest from p2 and aggregator, because we'd need versions
from M5 of which no EPP exists at this point. Chicken-and-egg?


cross-project-issues-dev mailing list
To change your delivery options, retrieve your password, or unsubscribe from this list, visit

Back to the top