Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [cross-project-issues-dev] Strange p2 behaviour

The "Duplication location" error is a known bug (338495). Unfortunately we could not find an agreement on how to fix it for Indigo.


On 2011-06-21, at 5:53 AM, Eike Stepper wrote:

Hi,

I've invested a lot into our new promotion service that automatically creates composite repositories with nested categories (generated from the content.xml of a build) and everything. The directory layout under download.eclipse.org is the following:

modeling/emf/cdo/

       temp/  --> Used to generate all composite repos

       drops/ --> N-builds filtered for mirrors

             I20110608-1536/

             M20110608-1536/

             S20110608-1536/

             R20110608-1536/

updates/ --> almost atomically replacable with temp/

releases/

4.0/

3.0/

2.0/

1.0/

       integration/

             stable/

             weekly/

       maintenance/

             stable/

             weekly/

Now, when trying these repos out, I encounter some strange things. First, it looks not so bad:

<p2-looks-good.png>

But when I want to expand the categories they're empty:

<p2-but-isnt.png>
This particular repository is a composite of two other composites (stable and weekly integration builds). For a different composite (releases, also a composite of composites) it seems to work:

<moz-screenshot-1.png>

Another problem that I don't understand is that the Install New Software dialog sometimes (but reproducibly) tells me "Duplicate Location":

<p2-duplicate-location.png>

Although I can find this location nowhere in the preferences:

<p2-available-locations.png>

Is there a p2 expert out there who can help me with these problems?

If it helps, here is a preliminary version of the generated downloads page: http://download.eclipse.org/modeling/emf/cdo/updates/downloads.php

Cheers
/Eike

----
http://www.esc-net.de
http://thegordian.blogspot.com
http://twitter.com/eikestepper


_______________________________________________
cross-project-issues-dev mailing list
cross-project-issues-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev


Back to the top