Announcement Announcement Module
Collapse
No announcement yet.
Solution for failing update from STS 2.5.0 to 2.5.1 Page Title Module
Move Remove Collapse
X
Conversation Detail Module
Collapse
  • Filter
  • Time
  • Show
Clear All
new posts

  • Solution for failing update from STS 2.5.0 to 2.5.1

    Hi,

    if you're trying to update your STS 2.5.0.RELEASE to 2.5.1.RELEASE the update process might fail with the following error:

    Code:
    An error occurred while unconfiguring the items to uninstall
    session context was:(profile=com.springsource.sts.ide, phase=org.eclipse.equinox.internal.p2.engine.phases.Unconfigure, operand=[R]com.springsource.sts.ide 2.5.0.201010241000-RELEASE --> [R]com.springsource.sts.ide 2.5.1.201011111000-RELEASE, action=org.eclipse.equinox.internal.p2.touchpoint.natives.actions.RmdirAction).
    Could not remove directory /home/user/bin/springsource/sts-2.5.0.RELEASE/dropins.
    A simple work-around for this error is to add an empty file into the dropins folder of your STS installation. This error has been fixed and will not happen again when updating 2.5.1 to 2.5.2 in the future.

    For more details see the following bug reports:

    STS-1345: Upgrading 2.5.0 to 2.5.1 does not work
    https://issuetracker.springsource.com/browse/STS-1345

    STS-1242: Failed to update product from 2.3.3.M2 to 2.5.0.M3
    https://issuetracker.springsource.com/browse/STS-1242

    Sorry for the inconvenience.

    Christian

  • #2
    I have the same problem on Windows 7
    Code:
    An error occurred while unconfiguring the items to uninstall
    session context was:(profile=com.springsource.sts.ide, phase=org.eclipse.equinox.internal.p2.engine.phases.Unconfigure, operand=[R]com.springsource.sts.package.feature.group 2.5.0.201010241000-RELEASE --> [R]com.springsource.sts.package.feature.group 2.5.1.201011111000-RELEASE, action=org.eclipse.equinox.internal.p2.touchpoint.natives.actions.RmdirAction).
    Could not remove directory D:\prg\springsource.2.5.0\sts-2.5.0.RELEASE/dropins.
    Petr

    Comment


    • #3
      Thanks! This fix works fine for me.

      Comment


      • #4
        Solution for failing update from STS 2.5.0 to 2.5.1

        If you're using Windows 7, try to add a file "temp.txt" inside the dropins folder. It should work.

        Cheers,
        Last edited by archetype; Dec 3rd, 2010, 10:30 AM.

        Comment


        • #5
          Originally posted by Christian Dupuis View Post
          Hi,

          if you're trying to update your STS 2.5.0.RELEASE to 2.5.1.RELEASE the update process might fail with the following error:

          Code:
          An error occurred while unconfiguring the items to uninstall
          session context was:(profile=com.springsource.sts.ide, phase=org.eclipse.equinox.internal.p2.engine.phases.Unconfigure, operand=[R]com.springsource.sts.ide 2.5.0.201010241000-RELEASE --> [R]com.springsource.sts.ide 2.5.1.201011111000-RELEASE, action=org.eclipse.equinox.internal.p2.touchpoint.natives.actions.RmdirAction).
          Could not remove directory /home/user/bin/springsource/sts-2.5.0.RELEASE/dropins.
          A simple work-around for this error is to add an empty file into the dropins folder of your STS installation. This error has been fixed and will not happen again when updating 2.5.1 to 2.5.2 in the future.

          For more details see the following bug reports:

          STS-1345: Upgrading 2.5.0 to 2.5.1 does not work
          https://issuetracker.springsource.com/browse/STS-1345

          STS-1242: Failed to update product from 2.3.3.M2 to 2.5.0.M3
          https://issuetracker.springsource.com/browse/STS-1242

          Sorry for the inconvenience.

          Christian
          Same issue still exists when updating from 2.5.1 to 2.5.2, but solution still works!

          Comment


          • #6
            Hm, this is strange, I checked this and the update from 2.5.1 to 2.5.2 works without that specific problem. I will play around with some more situations to verify this.

            Comment


            • #7
              I now tried several settings, also installing 2.5.0, updating to 2.5.1 (using the workaround) and then to 2.5.2 (without the workaround), all without any problems. So it seems like a very specific situation that you have here. Do you have more details?

              Comment


              • #8
                Originally posted by Christian Dupuis View Post
                Hi,

                if you're trying to update your STS 2.5.0.RELEASE to 2.5.1.RELEASE the update process might fail with the following error:

                Code:
                An error occurred while unconfiguring the items to uninstall
                session context was:(profile=com.springsource.sts.ide, phase=org.eclipse.equinox.internal.p2.engine.phases.Unconfigure, operand=[R]com.springsource.sts.ide 2.5.0.201010241000-RELEASE --> [R]com.springsource.sts.ide 2.5.1.201011111000-RELEASE, action=org.eclipse.equinox.internal.p2.touchpoint.natives.actions.RmdirAction).
                Could not remove directory /home/user/bin/springsource/sts-2.5.0.RELEASE/dropins.
                A simple work-around for this error is to add an empty file into the dropins folder of your STS installation
                free online movies. This error has been fixed and will not happen again when updating 2.5.1 to 2.5.2 in the future.

                For more details see the following bug reports:

                STS-1345: Upgrading 2.5.0 to 2.5.1 does not work
                https://issuetracker.springsource.com/browse/STS-1345

                STS-1242: Failed to update product from 2.3.3.M2 to 2.5.0.M3
                https://issuetracker.springsource.com/browse/STS-1242

                Sorry for the inconvenience.

                Christian
                Great post! It's very nice. Thank you so much for your post.

                Comment


                • #9
                  I have the same problem updating from 2.5.2 to 2.6.0.M1 on Mac OS Snow Leopard

                  Comment


                  • #10
                    That is strange, this should be solved for quite some time now. Did the workaround work for you as well?

                    Comment


                    • #11
                      Late reply but the workaround worked for me.

                      Comment

                      Working...
                      X