# Pkg can't load packages present in Manifest.toml?
**URL:** https://discourse.julialang.org/t/pkg-cant-load-packages-present-in-manifest-toml/13636
**Category:** General Usage
**Tags:** question
**Created:** [August 17, 2018, 6:49pm UTC](https://discourse.julialang.org/t/pkg-cant-load-packages-present-in-manifest-toml/13636 "2018-08-17T18:49:11Z")
**Posts on this page:** 12
**Page:** 1
### Author:  [@tlnagy](https://discourse.julialang.org/u/tlnagy)
#### Post date: [August 17, 2018, 6:49pm UTC](https://discourse.julialang.org/t/pkg-cant-load-packages-present-in-manifest-toml/13636/1 "2018-08-17T18:49:11Z")
I was playing around with Julia 1.0 and noticed a weird behavior. Given I have an environment that looks like this
```julia
(v1.0) pkg> st
Status `~/.julia/environments/v1.0/Project.toml`
[a81c6b42] Compose v0.6.0+ [`~/.julia/dev/Compose`]
[e30172f5] Documenter v0.19.5
[c91e804a] Gadfly v0.7.0
(v1.0) pkg> st -m
Status `~/.julia/environments/v1.0/Manifest.toml`
...
...
[5ae59095] Colors v0.9.2
...
...
```
I find it surprising that I can’t load `Colors.jl`:
```julia
julia> using Colors
ERROR: ArgumentError: Package Colors not found in current path:
- Run `Pkg.add("Colors")` to install the Colors package.
Stacktrace:
[1] require(::Module, ::Symbol) at ./loading.jl:817
```
despite the fact that it’s in the Manifest and is explicitly required by `Compose.jl`. Instantiate and resolve don’t do anything either.
This came up when we load `Colors` inside the Compose docs. On Julia v0.6, it would load fine, but now I would have to explicitly install Colors despite it being required to be installed.
---
### Author:  [@00vareladavid](https://discourse.julialang.org/u/00vareladavid)
#### Post date: [August 17, 2018, 7:48pm UTC](https://discourse.julialang.org/t/pkg-cant-load-packages-present-in-manifest-toml/13636/2 "2018-08-17T19:48:07Z")
> [@tlnagy](#):
>
> I would have to explicitly install Colors despite it being required to be installed.
Yes, I’m pretty sure this is the intended behavior. For a given environment, you can only load packages which are explicitly declared for that environment.
---
### Author:  [@Sukera](https://discourse.julialang.org/u/Sukera)
#### Post date: [August 17, 2018, 8:23pm UTC](https://discourse.julialang.org/t/pkg-cant-load-packages-present-in-manifest-toml/13636/3 "2018-08-17T20:23:52Z")
Adding on to that, it may be that the package that has Colors.jl as a dependency is depending on a specific version of it. This version could conflict with a version needed by another package or even the environment directly, which is why dependencies of dependencies are not automatically available.
Edit: Only half true, see below.
---
### Author:  [@StefanKarpinski](https://discourse.julialang.org/u/StefanKarpinski)
#### Post date: [August 17, 2018, 8:43pm UTC](https://discourse.julialang.org/t/pkg-cant-load-packages-present-in-manifest-toml/13636/4 "2018-08-17T20:43:13Z")
You can only have one version of a given package at a time. You can, however, have different packages with the same name in the overall dependency graph. It is intentional that you must explicitly declare your dependencies at the top level. These are connected facts since the top-level `Colors` could be totally unrelated to an indirect `Colors` dependency.
---
### Author:  [@Sukera](https://discourse.julialang.org/u/Sukera)
#### Post date: [August 17, 2018, 8:47pm UTC](https://discourse.julialang.org/t/pkg-cant-load-packages-present-in-manifest-toml/13636/5 "2018-08-17T20:47:24Z")
> You can only have one version of a given package at a time.
So the following would not be possible? Say package A depends on version 0.1 of package B, I am developing package with a dependency on version 0.2 of package B and a dependency on package A. In this scenario, package C would both directly and indirectly depend on two different versions of package B respectively.
---
### Author:  [@StefanKarpinski](https://discourse.julialang.org/u/StefanKarpinski)
#### Post date: [August 17, 2018, 8:48pm UTC](https://discourse.julialang.org/t/pkg-cant-load-packages-present-in-manifest-toml/13636/6 "2018-08-17T20:48:47Z")
Correct, that is not possible. It is quite rare for Julia packages to depend on a specific version of a dependency.
---
### Author:  [@Sukera](https://discourse.julialang.org/u/Sukera)
#### Post date: [August 17, 2018, 8:50pm UTC](https://discourse.julialang.org/t/pkg-cant-load-packages-present-in-manifest-toml/13636/7 "2018-08-17T20:50:36Z")
Hmm, that seems unfortunate, though I must admit it also seems a bit contrived as an example. What would be a good workaround should this situation show up?
---
### Author:  [@StefanKarpinski](https://discourse.julialang.org/u/StefanKarpinski)
#### Post date: [August 17, 2018, 8:52pm UTC](https://discourse.julialang.org/t/pkg-cant-load-packages-present-in-manifest-toml/13636/8 "2018-08-17T20:52:23Z")
Fix A, B or your own package so that there is a common version of A that works with both.
---
### Author:  [@tlnagy](https://discourse.julialang.org/u/tlnagy)
#### Post date: [August 17, 2018, 9:00pm UTC](https://discourse.julialang.org/t/pkg-cant-load-packages-present-in-manifest-toml/13636/9 "2018-08-17T21:00:43Z")
> [@StefanKarpinski](#):
>
> It is intentional that you must explicitly declare your dependencies at the top level.
So this is a change from how things were done in the previous package manager, right? So now, even though `Compose` requires `Colors`, you need to also `Pkg.add("Colors")` to explicitly list it in the `Project.toml`
---
### Author:  [@StefanKarpinski](https://discourse.julialang.org/u/StefanKarpinski)
#### Post date: [August 17, 2018, 9:02pm UTC](https://discourse.julialang.org/t/pkg-cant-load-packages-present-in-manifest-toml/13636/10 "2018-08-17T21:02:08Z")
Yes, precisely. It’s actually deeper than the package manager and is baked into how code loading itself works.
---
### Author:  [@GunnarFarneback](https://discourse.julialang.org/u/GunnarFarneback)
#### Post date: [August 18, 2018, 7:12am UTC](https://discourse.julialang.org/t/pkg-cant-load-packages-present-in-manifest-toml/13636/11 "2018-08-18T07:12:44Z")
In an emergency I guess you could make a fork of B with a different UUID and specify different versions for B and B’.
---
### Author:  [@Sukera](https://discourse.julialang.org/u/Sukera)
#### Post date: [August 18, 2018, 11:08am UTC](https://discourse.julialang.org/t/pkg-cant-load-packages-present-in-manifest-toml/13636/12 "2018-08-18T11:08:08Z")
A fork wouldn’t even be necessary - if you’re going to fix the package anyway, you can just as well use the local branch temporarily and make a PR. After it’s merged, you can track the original package again.