Eclipse Community Forums
Forum Search:

Search      Help    Register    Login    Home
Home » Eclipse Projects » P2 » Cannot complete the install because of a conflicting dependency.
Cannot complete the install because of a conflicting dependency. [message #826040] Wed, 21 March 2012 15:25 Go to next message
Christian Eugster is currently offline Christian Eugster
Messages: 134
Registered: July 2009
Location: St. Gallen Switzerland
Senior Member
Hi,

I am sorry to bother you, but I find no documentation that helps me! I am trying to setup a working update site using p2 (eclipse 3.6.2). I have a product version 1.0.0.qualifier. I set up a release and an update site for this application. Then I changed some plugins, set their versions from 1.0.1 to 1.0.2, updated the correspondent features to 1.0.2 too plus the product version to 1.0.2. I then exported the product and put the resulting repository on my releases site, built the respective site and put that result to my update site. When I start my application and try to update it through to version 1.0.2 I get an error saying: The operation cannot be completed. See the details. And:

Cannot complete the install because of a conflicting dependency.
Software being installed: ColibriTS II 1.0.0.201203211314 (ch.eugster.colibri.product.product 1.0.0.201203211314)
Only one of the following can be installed at once:
Cache 1.0.1 (ch.eugster.colibri.persistence 1.0.1)
Cache 1.0.2 (ch.eugster.colibri.persistence 1.0.2)
Cannot satisfy dependency:
From: Modul Code 128 Barcode 1.0.2 (ch.eugster.colibri.barcode.code128.feature.feature.group 1.0.2)
To: ch.eugster.colibri.persistence [1.0.2]
Cannot satisfy dependency:
From: Basismodul Anbindung Datenbank 1.0.1 (ch.eugster.colibri.persistence.feature.feature.group 1.0.1)
To: ch.eugster.colibri.persistence [1.0.1]
Cannot satisfy dependency:
From: ColibriTS II 1.0.0.201203211314 (ch.eugster.colibri.product.product 1.0.0.201203211314)
To: ch.eugster.colibri.barcode.code128.feature.feature.group [1.0.2]
Cannot satisfy dependency:
From: ColibriTS II 1.0.0.201203211314 (ch.eugster.colibri.product.product 1.0.0.201203211314)
To: ch.eugster.colibri.report.receipt.feature.feature.group [1.0.1]
Cannot satisfy dependency:
From: Modul Auswertungen Belegliste 1.0.1 (ch.eugster.colibri.report.receipt.feature.feature.group 1.0.1)
To: ch.eugster.colibri.persistence.feature.feature.group [1.0.1]

Thanks a lot!

Christian Eugster
Re: Cannot complete the install because of a conflicting dependency. [message #826684 is a reply to message #826040] Thu, 22 March 2012 11:27 Go to previous messageGo to next message
Paul Webster is currently offline Paul Webster
Messages: 6859
Registered: July 2009
Location: Ottawa
Senior Member

That says your product is at ch.eugster.colibri.product.product 1.0.0.201203211314 (not 102 as you mentioned). Did you rename your product IU when moving to this version? What product is currently installed in your app from Help>About>Installation Details?

PW


Re: Cannot complete the install because of a conflicting dependency. [message #828140 is a reply to message #826684] Sat, 24 March 2012 09:05 Go to previous messageGo to next message
Christian Eugster is currently offline Christian Eugster
Messages: 134
Registered: July 2009
Location: St. Gallen Switzerland
Senior Member
Hi Paul,

first: Thank you for answering!

There are several points that I do not understand (after searching the web, reading tutorials and so on):

What I understand is:

That the version of a changed plugin, the feature that contains the plugin and the product must be raised before a new product export.

When I use the term .qualifier after the major.minor.service version, then the qualifier is computed while exporting the product for ALL plugins, features and the product. That means (as I understand) everything is exported and my repository doubles in size.

My questions are:

When I want only changed parts be exported then I have to use fixed versions (I mean versions where qualifier is removed or replaced by a constant value (e.g. 1.0.0.201203231623). I only update the versions of the plugins, the features containing those plugins I want to include in a reexport of the product (whose version I update also). Is that right (do I understand this right)?

To reexport a product, the version of the product must be the same as the plugins/features that I want to export?

When I have exported a product with "generate repository" checked, I get a repository. When I reexport an updated product with "generate repository" checked, the repository will be updated with the new information, as I understand.

Where do I find precise information about the conditions that must be met to perform an update successfully?

I changed the versions as I described above and get now the following message:

8<------------------------
Cannot complete the install because of a conflicting dependency.
Software being installed: ColibriTS II 1.0.0.201203231621 (ch.eugster.colibri.product.product 1.0.0.201203231621)
Only one of the following can be installed at once:
Basismodul Kundendisplay 1.0.0.201203221102 (ch.eugster.colibri.periphery.display.feature.feature.jar 1.0.0.201203221102)
Basismodul Kundendisplay 1.0.0.201203231621 (ch.eugster.colibri.periphery.display.feature.feature.jar 1.0.0.201203231621)
8<------------------------

But I WANT to replace the version 1.0.0.201203221102 with 1.0.0.201203231621
What is the problem here?

8<------------------------
Cannot satisfy dependency:
From: Basismodul Kundendisplay 1.0.0.201203221102 (ch.eugster.colibri.periphery.display.feature.feature.group 1.0.0.201203221102)
To: ch.eugster.colibri.periphery.display.feature.feature.jar [1.0.0.201203221102]
8<------------------------

What is meant by "ch.eugster.colibri.periphery.display.feature.feature.group 1.0.0.201203221102"? Are here the plugins of the feature meant?

And what by "ch.eugster.colibri.periphery.display.feature.feature.jar [1.0.0.201203221102]"? Is here the feature meant?

These are the old versions that I want to replace with the newer ones (1.0.0.201203231621). Why does the update manager complain here?

8<------------------------
Cannot satisfy dependency:
From: Basismodul Kundendisplay 1.0.0.201203231621 (ch.eugster.colibri.periphery.display.feature.feature.group 1.0.0.201203231621)
To: ch.eugster.colibri.periphery.display.feature.feature.jar [1.0.0.201203231621]
8<------------------------

The same question as above.

8<------------------------
Cannot satisfy dependency:
From: Modul Kundendisplay Star Scd122u 1.0.0.201203221102 (ch.eugster.colibri.periphery.display.serial.scd122u.feature.feature.group 1.0.0.201203221102)
To: ch.eugster.colibri.periphery.display.feature.feature.group [1.0.0.201203221102]
Cannot satisfy dependency:
From: ColibriTS II 1.0.0.201203231621 (ch.eugster.colibri.product.product 1.0.0.201203231621)
To: ch.eugster.colibri.periphery.display.feature.feature.group [1.0.0.201203231621]
Cannot satisfy dependency:
From: ColibriTS II 1.0.0.201203231621 (ch.eugster.colibri.product.product 1.0.0.201203231621)
To: ch.eugster.colibri.periphery.display.serial.scd122u.feature.feature.group [1.0.0.201203221102]
8<------------------------

To the following: I don't understand why the product of the new version must satisfy the dependency to the feature of old version. Why is that so?

Cannot satisfy dependency:
From: ColibriTS II 1.0.0.201203231621 (ch.eugster.colibri.product.product 1.0.0.201203231621)
To: ch.eugster.colibri.periphery.display.serial.scd122u.feature.feature.group [1.0.0.201203221102]

I hope I made my problems clearer. If you know a reader (in the cloud or as book) that clarifies this to me, let me know.

Thank you, Paul

Christian

[Updated on: Sat, 24 March 2012 09:29]

Report message to a moderator

Re: Cannot complete the install because of a conflicting dependency. [message #828861 is a reply to message #828140] Sun, 25 March 2012 12:25 Go to previous message
Brian de Alwis is currently offline Brian de Alwis
Messages: 189
Registered: January 2012
Senior Member

Christian, try reading the following text from the p2 FAQ:

wiki.eclipse.org/Equinox/p2/FAQ#Why_am_I_getting_dependency_satisfaction_errors_when_I_update_my_feature.3F


Eclipse Platform committer. Ask me about Eclipse support, training, and consulting.
Previous Topic:Character corruption in the content.xml
Next Topic:How do I include source bundles in my p2 site?
Goto Forum:
  


Current Time: Sun Sep 21 22:31:53 GMT 2014

Powered by FUDForum. Page generated in 0.01664 seconds
.:: Contact :: Home ::.

Powered by: FUDforum 3.0.2.
Copyright ©2001-2010 FUDforum Bulletin Board Software