Re: [p2-dev] difference between "Check for updates" and "Install new sof

[Pascal Rapicault <Pascal_Rapicault@xxxxxxxxxx>]

Please open a bug containing:
- the profile containing the state from which you are starting the update
- the metadata repo containing the updates.

With this we should be able to better diagnose what is going on.

Thx

Andrew Eisenberg ---10/19/2009 11:05:48 PM---The failures look something like this (with some slight differences

From:	Andrew Eisenberg <andrew@xxxxxxxxxxxx>
To:	Susan Franklin McCourt <susan_franklin@xxxxxxxxxx>
Cc:	P2 developer discussions <p2-dev@xxxxxxxxxxx>
Date:	10/19/2009 11:05 PM
Subject:	Re: [p2-dev] difference between "Check for updates" and "Install new software"

---

The failures look something like this (with some slight differences
depending on what distro of Eclipse ou are using and what other update
sites are enabled):

Cannot complete the install because of a conflicting dependency.
  Software currently installed: SpringSource Tool Suite
2.1.0.200908021330-RELEASE (com.springsource.sts.ide
2.1.0.200908021330-RELEASE)
  Only one of the following can be installed at once:
    JDT Core patch for Groovy-Eclipse plugin
2.0.0.xx-20091019-1600-M1-e35
(org.codehaus.groovy.jdt.patch.feature.jar
2.0.0.xx-20091019-1600-M1-e35)
    JDT Core patch for Groovy-Eclipse plugin
2.0.0.xx-20091019-0700-e35 (org.codehaus.groovy.jdt.patch.feature.jar
2.0.0.xx-20091019-0700-e35)
  Cannot satisfy dependency:
    From: SpringSource Tool Suite 2.1.0.200908021330-RELEASE
(com.springsource.sts.ide 2.1.0.200908021330-RELEASE)
    To: com.springsource.sts.package.feature.group [2.1.0.200908021330-RELEASE]
  Cannot satisfy dependency:
    From: SpringSource Tool Suite 2.1.0.200908021330-RELEASE
(com.springsource.sts.package.feature.group
2.1.0.200908021330-RELEASE)
    To: org.eclipse.jdt.feature.group [3.5.0,4.0.0)
  Cannot satisfy dependency:
    From: JDT Core patch for Groovy-Eclipse plugin
2.0.0.xx-20091019-0700-e35
(org.codehaus.groovy.jdt.patch.feature.group
2.0.0.xx-20091019-0700-e35)
    To: org.codehaus.groovy.jdt.patch.feature.jar [2.0.0.xx-20091019-0700-e35]
  Cannot satisfy dependency:
    From: JDT Core patch for Groovy-Eclipse plugin
2.0.0.xx-20091019-1600-M1-e35
(org.codehaus.groovy.jdt.patch.feature.group
2.0.0.xx-20091019-1600-M1-e35)
    To: org.codehaus.groovy.jdt.patch.feature.jar
[2.0.0.xx-20091019-1600-M1-e35]
  Cannot satisfy dependency:
    From: Eclipse Java Development Tools
3.5.1.r351_v20090810-0600-7r88FEoFI0WTo6Az-1qFRHm37ChJ
(org.eclipse.jdt.feature.group
3.5.1.r351_v20090810-0600-7r88FEoFI0WTo6Az-1qFRHm37ChJ)
    To: null

What looks like is happening is that the old core patch cannot be
uninstalled because of some dependencies, and so the new one cannot be
installed.  And the update fails.

--a

On Mon, Oct 19, 2009 at 11:45 AM, Susan Franklin McCourt
<susan_franklin@xxxxxxxxxx> wrote:
>
> >However, when
> >a user installs the base feature and child features explicitly as
> >top-level features, check for updates will fail (even though install
> >new software will succeed).
>
> What is the failure?  Are you saying updates are not found, or that an error is reported about the compatibility of the child features with the parent feature? It sounds like a bug to me.
>
> susan
_______________________________________________
p2-dev mailing list
p2-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/p2-dev