Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Cannot update form 4.3.3 to 4.4 #1375

Closed
rlogiacco opened this issue Aug 29, 2021 · 5 comments
Closed

Cannot update form 4.3.3 to 4.4 #1375

rlogiacco opened this issue Aug 29, 2021 · 5 comments

Comments

@rlogiacco
Copy link
Collaborator

Looks like I cannot update from 4.3.3 due to a Sloeber 4.4 dependency which seems no more available, specifically ECF Filetransfer Feature 3.14.1703: I have ECF Filetransfer Feature 3.14.1400 and only 5.0 and 5.1 seem available for download...

Cannot complete the install because of a conflicting dependency.
  Software being installed: Sloeber 4.4.0.202107110422 (io.sloeber.product 4.4.0.202107110422)
  Software currently installed: ECF Filetransfer Feature 3.14.1400.v20200812-2314 (org.eclipse.ecf.filetransfer.feature.feature.group 3.14.1400.v20200812-2314)
  Only one of the following can be installed at once: 
    ECF Filetransfer API 5.1.102.v20210409-2301 (org.eclipse.ecf.filetransfer 5.1.102.v20210409-2301)
    ECF Filetransfer API 5.1.100.v20200611-2221 (org.eclipse.ecf.filetransfer 5.1.100.v20200611-2221)
    ECF Filetransfer API 5.0.100.v20180301-0132 (org.eclipse.ecf.filetransfer 5.0.100.v20180301-0132)
  Cannot satisfy dependency:
    From: Sloeber 4.4.0.202107110422 (io.sloeber.product 4.4.0.202107110422)
    To: org.eclipse.equinox.p2.iu; org.eclipse.ecf.filetransfer.feature.feature.group [3.14.1703.v20210409-2301,3.14.1703.v20210409-2301]
  Cannot satisfy dependency:
    From: ECF Filetransfer Feature 3.14.1400.v20200812-2314 (org.eclipse.ecf.filetransfer.feature.feature.group 3.14.1400.v20200812-2314)
    To: org.eclipse.equinox.p2.iu; org.eclipse.ecf.filetransfer [5.1.100.v20200611-2221,5.1.100.v20200611-2221]
  Cannot satisfy dependency:
    From: ECF Filetransfer Feature 3.14.1703.v20210409-2301 (org.eclipse.ecf.filetransfer.feature.feature.group 3.14.1703.v20210409-2301)
    To: org.eclipse.equinox.p2.iu; org.eclipse.ecf.filetransfer [5.1.102.v20210409-2301,5.1.102.v20210409-2301]
@jantje
Copy link
Member

jantje commented Aug 29, 2021

Seems this is defined in the product.
On my system I see there is no version info given but when I double click on
afbeelding

I get

afbeelding

I am updating my development environment and I hope that version increases
Don't know what else I can do

@jantje
Copy link
Member

jantje commented Aug 29, 2021

After the upgrade I get a newer version
afbeelding

but no git files have been changed so IMHO the server build should be exactly the same
So I do not know how this works :-(
But given it is in the product .... I can remove it :-)

@wimjongman
I see org.eclipse.ecf.filetransfer is referenced in the first version of arduino.product

<feature id="org.eclipse.ecf.filetransfer.feature" installMode="root"/>

Do you know if this is needed?
Can you explain the problem @rlogiacco is experiencing?
Do you know how to fix it?

@wimjongman
Copy link
Member

ECF (Eclipse Communication Framework) is the backbone of all communications in Eclipse. It is needed, e.g., for updating software.

Roberto, you must have another item in your installation that requires this older version of ECF. Did you install Sloeber into an existing Eclipse or are you running the 4.3.3 product?

@wimjongman
Copy link
Member

I downloaded Sloeber 4.3.3 and started it. Then I did a "check for updates" and I could install 4.4. without issues. After restarting, I ran into some other issues [1] but not this specific one.

[1] Old Sloeber product cannot be updated #1376

@wimjongman
Copy link
Member

Closing. Please reopen if you can reproduce the issue on a fresh 4.3.3.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants