Search Unity

  1. Megacity Metro Demo now available. Download now.
    Dismiss Notice
  2. Unity support for visionOS is now available. Learn more in our blog post.
    Dismiss Notice

Problem installing latest Linux Editor version.

Discussion in 'Linux' started by erikthunberg, Sep 2, 2017.

  1. erikthunberg

    erikthunberg

    Joined:
    Sep 2, 2017
    Posts:
    4
    Hello!

    I have some trouble installing the latest version of the linux editor on Debian 9 Stretch.

    Code (CSharp):
    1. ➜  Downloads sudo dpkg -i unity-editor_amd64-2017.2.0xb6Linux.deb
    2. Selecting previously unselected package unity-editor.
    3. (Reading database ... 172671 files and directories currently installed.)
    4. Preparing to unpack unity-editor_amd64-2017.2.0xb6Linux.deb ...
    5. Unpacking unity-editor (2017.2.0xb6Linux) ...
    6. dpkg: unity-editor: dependency problems, but configuring anyway as you requested:
    7. unity-editor depends on npm; however:
    8.   Package npm is not installed.
    It seems like its depending on the npm-package which does not exist anymore under Stretch but does under Jessie.
    I know the official support is for Ubuntu, but as it has worked flawless under Debian Jessie I have high hopes for Stretch.

    I've tried both the the --force-all and --ignore-depends=npm options while running the dpkg install. But as soon as I try to install something else with apt-get I get the following:

    Code (CSharp):
    1. Reading package lists... Done
    2. Building dependency tree      
    3. Reading state information... Done
    4. You might want to run 'apt --fix-broken install' to correct these.
    5. The following packages have unmet dependencies:
    6. unity-editor : Depends: npm but it is not installable
    And when I run sudo apt-get install -f I get:

    Code (CSharp):
    1.  
    2. Reading package lists... Done
    3. Building dependency tree      
    4. Reading state information... Done
    5. Correcting dependencies... Done
    6. The following packages will be REMOVED:
    7.   unity-editor
    8. 0 upgraded, 0 newly installed, 1 to remove and 0 not upgraded.
    9. 1 not fully installed or removed.
    10. After this operation, 8,106 MB disk space will be freed.
    11. Do you want to continue? [Y/n]
    Is the only solution to add jessie-backports (or similar) to the sources.list or is there any other way around it?

    Thanks.
     
  2. erikthunberg

    erikthunberg

    Joined:
    Sep 2, 2017
    Posts:
    4
    So this is my solution right now.

    I added "deb http://ftp.se.debian.org/debian/ jessie main" to the end of /etc/apt/sources.list and ran apt-get update && apt-get install npm.
    Then I installed unity and removed the same line from /etc/apt/sources.list.

    Might not be the best solution in the world, but it works.
     
  3. Tak

    Tak

    Joined:
    Mar 8, 2010
    Posts:
    1,001
    That's ... odd - maybe there's something going on with the debian npm package?
    If I search for packages called npm, it shows that it's available for oldstable/jessie and unstable/sid, but nothing in between.
    If I search for packages with a file called npm in stable/stretch, it gives me the npm package as the only result, but then following the link gives "Package not available in this suite."

    So...shrug?
    Your workaround seems ok - alternatively, you could install npm from a non-apt source and install Unity using the .sh installer.
     
  4. erikthunberg

    erikthunberg

    Joined:
    Sep 2, 2017
    Posts:
    4
    I use NVM to install node/npm (as I develop with node) so I will try the .sh-installer on another computer with Stretch which does not yet have the above jessie-solution and report back.
     
  5. erikthunberg

    erikthunberg

    Joined:
    Sep 2, 2017
    Posts:
    4
    Installing with the .sh-installer seems to work like a charm without the npm-package installed but npm installed from other sources.

    Only thing I get after I've started Unity is: "
    Error loading launcher://unity//home/user/.local/share/unity3d/Packages/node_modules/unity-editor-home/dist/index.html?code=...." But as I've read this is a common bug until 2017.2-final?