Skip to content

Reinstallation of Code Alpha left it in a bad state #5840

Closed
Closed
Reinstallation of Code Alpha left it in a bad state#5840
Assignees
Tyriar
Labels
bugIssue identified by VS Code Team member as probable buginstall-updateVS Code installation and upgrade system issueslinuxIssues with VS Code on LinuxverifiedVerification succeeded
Milestone
June 2016

Description

@joaomoreno
João Moreno (joaomoreno)
opened on Apr 26, 2016

Fixing #5463

I had Code Alpha installed in CentOS (red hat). Today, I downloaded the latest RPM, installed it and now I can't launch Code nor reinstall it.

It doesn't seem to be installed at all. It is also gone from the Applications menu, where it used to be before installing it today.

image

Can't even reinstall it:

image

Activity

  1. ImageJoão Moreno (joaomoreno)
    assigned
    Daniel Imms (Tyriar)
    on Apr 26, 2016
  2. ImageJoão Moreno (joaomoreno)
    added
    bugIssue identified by VS Code Team member as probable bug
    on Apr 26, 2016

  3. joaomoreno commented on Apr 26, 2016

    @joaomoreno
    João Moreno (joaomoreno)
    on Apr 26, 2016
    ContributorAuthor

    I could fix it by running sudo rpm -ev code-alpha and reinstalling the rpm package.

  4. Tyriar commented on Apr 27, 2016

    @Tyriar
    Daniel Imms (Tyriar)
    on Apr 27, 2016
    Contributor

    I think I've experienced this where the installer didn't work, it seemed like the installer's issue to me. It happened to me pretty consistently whenever I tried to install a second thing. Fresh restart and using it always seemed to work.

  5. ImageDaniel Imms (Tyriar)
    added this to the Backlog milestone on May 31, 2016
  6. ImageDaniel Imms (Tyriar)
    added
    install-updateVS Code installation and upgrade system issues
    linuxIssues with VS Code on Linux
    on May 31, 2016

  7. astitcher commented on Jun 7, 2016

    @astitcher
    Andrew Stitcher (astitcher)
    on Jun 7, 2016
    Contributor

    This issue exists with the 1.2 released rpm too.

    The cause is a misunderstanding about the order of running the scriptlets:

    If you are upgrading the postuninstall scriptlet runs after the upgrade to uninstall anything left over in the old installation. In this case it is removing the /usr/bin/code (or code-alpha) link to /usr/share/code/bin/code just after it was created.

    The postuninstall scriptlet needs to check whether an upgrade is being run and in that case just not do the remove.

    I think the section should look like:

    %postun
f [ $1 = 0 ]; then
  rm -f /usr/bin/code
fi

    Also note that you shouldn't need sudo for any part of the rpm scripts as installing a package runs as root.

  8. ImageDaniel Imms (Tyriar)
    modified the milestones: June 2016, Backlog on Jun 8, 2016

  9. Tyriar commented on Jun 8, 2016

    @Tyriar
    Daniel Imms (Tyriar)
    on Jun 8, 2016
    Contributor

    Should be fixed via PR from Andrew Stitcher (@astitcher)

  10. ImageDaniel Imms (Tyriar)
    closed this as completedon Jun 8, 2016
  11. ImageJoão Moreno (joaomoreno)
    added
    verifiedVerification succeeded
    on Sep 2, 2016
  12. Imagevscodebot
    locked and limited conversation to collaborators on Nov 18, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Labels

bugIssue identified by VS Code Team member as probable buginstall-updateVS Code installation and upgrade system issueslinuxIssues with VS Code on LinuxverifiedVerification succeeded

Type

No type

Projects

No projects

    Milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions