E06263: dependency is not installed in the library

Category: E06xxx Type hierarchy checks · Reported in phase: SYMBOL_DEFINITION · Classification: DEPENDENCY_NOT_INSTALLED · All error codes

What went wrong

A dependency named in your 'defines package' block ('deps' or 'devDeps') is not installed in the library, so nothing can resolve it. The library is the folder ~/.ek9/lib: a dependency is there either unpacked, as the directory '<module>-<version>', or zipped, as '<module>-<version>.zip'. The compiler, the language server, the IDE and the tools all report it, on the dependency's own line (the message starts "In '<module>' package:"); 'ek9 -c' reports the same fact when it resolves dependencies and stops with exit code 17.

Only your DIRECT dependencies are checked here. A dependency of a dependency is resolved by 'ek9 -Dp' when the library holds the dependency that names it. 'excludeDeps' entries are not dependencies and are never checked. There is no remote repository to fetch from yet: a dependency gets into the library only by being installed from its package.

How to fix it

  1. Install the package into the library. If you have the project that defines it, run 'ek9 -I <its main file>.ek9' by hand: that packages it and unpacks it into ~/.ek9/lib. If you were given its zip, put it in ~/.ek9/lib.
  2. Check the name and the version against what is installed: the library folder name is '<module>-<version>' exactly (a version of 3.2.1-0 is not 3.2.1).
  3. Run 'ek9 -Dp <your main file>.ek9' by hand to resolve every dependency, transitive ones included (in the IDE: Resolve Dependencies).
  4. If you do not need the dependency, remove it from the block.

The [EXAMPLE] section below shows a package that depends on a version that is not installed, and the same package depending on one that is.

Common causes

  • A dependency just added to the block, before anything has installed it (the normal first step of adding one)
  • A version that is not the one installed ('9.9.9-9' for '3.2.1-0')
  • A misspelt module name
  • A library folder that is not the one you expect (a fresh machine, or a different user: the library is per user)

See also

Examples

Every example is compiled by the EK9 compiler: the first fails exactly as captioned, the others fix it.

Fails with E06263: dependency is not installed in the library

#!ek9
defines module error.e06263.bad

  defines package
    version <- 1.0.0-0
    description <- "A library"

    deps <- {
      "ek9open.net.handy.tools": "9.9.9-9"
    }

Fixed: Depend on a version that is installed

#!ek9
defines module error.e06263.good

  defines package
    version <- 1.0.0-0
    description <- "A library"

    deps <- {
      "ek9open.net.handy.tools": "3.2.1-0"
    }

Found a problem?

If EK9 reported E06263 for a program you think is valid, or did not report it where it should have, use the compiler form with the smallest program that shows it. If this page is wrong or unclear, use the documentation form. Both are at github.com/ek9lang/ek9-issues.