# ERROR: Unsatisfiable requirements detected for package TreeViews \[a2a6695c\]

**URL:** <https://discourse.julialang.org/t/error-unsatisfiable-requirements-detected-for-package-treeviews-a2a6695c/37117>\
**Category:** Juno\
**Tags:** bug\
**Created:** [April 6, 2020, 4:48pm UTC](https://discourse.julialang.org/t/error-unsatisfiable-requirements-detected-for-package-treeviews-a2a6695c/37117 "2020-04-06T16:48:11Z")\
**Posts on this page:** 10\
**Page:** 1

<div class="post-metadata">

**Author:** ![Henderson](https://avatars.discourse-cdn.com/v4/letter/h/f6c823/32.png) [@Henderson](https://discourse.julialang.org/u/Henderson)\
**Post date:** [April 6, 2020, 4:48pm UTC](https://discourse.julialang.org/t/error-unsatisfiable-requirements-detected-for-package-treeviews-a2a6695c/37117/1 "2020-04-06T16:48:11Z")

</div>

Hi, when i start Julia in Atom, the REPL returns me the following (I installed the version 1.4.0):

"Hold on tight while we are installing some packages for you.  
This should only take a few seconds…

Activating environment at `C:\Users\hende\.julia\environments\v1.4\Project.toml`  
Updating registry at `C:\Users\hende\.julia\registries\General`  
┌ Warning: Some registries failed to update:  
│ — `C:\Users\hende\.julia\registries\General` — registry dirty  
└ @ Pkg.Types D:\buildbot\worker\package\_win64\build\usr\share\julia\stdlib\v1.4\Pkg\src\Types.jl:1122  
Resolving package versions…  
ERROR: LoadError: Unsatisfiable requirements detected for package TreeViews [a2a6695c]:  
TreeViews [a2a6695c] log:  
├─TreeViews [a2a6695c] has no known versions!  
└─found to have no compatible versions left with Atom [c52e3926]  
└─Atom [c52e3926] log:  
├─possible versions are: [0.8.0-0.8.8, 0.9.0-0.9.1, 0.10.0-0.10.2, 0.11.0-0.11.3, 0.12.0-0.12.10] or uninstalled  
└─restricted to versions \* by an explicit requirement, leaving only versions [0.8.0-0.8.8, 0.9.0-0.9.1, 0.10.0-0.10.2, 0.11.0-0.11.3, 0.12.0-0.12.10]"

I tried “rm -m DebuggerFramework” (in the Pkg REPL) as suggested here: “[Atom compatibility problem when installing julia packages](https://discourse.julialang.org/t/atom-compatibility-problem-when-installing-julia-packages/22198)” or here: “[Error to install Pkg.add Unsatisfiable requirements detected for package DebuggerFramework · Issue #1118 · JuliaLang/Pkg.jl · GitHub](https://github.com/JuliaLang/Pkg.jl/issues/1118)” and the REPL shows:

"(@v1.4) pkg\> rm -m DebuggerFramework  
ERROR: The following package names could not be resolved:

- DebuggerFramework (not found in project or manifest)"

it seems to me a question of “incompatibility” between the version of Atom with version 1.4 of Julia anyway, any ideas?

thanks.

---

<div class="post-metadata">

**Author:** ![bashonubuntu](https://avatars.discourse-cdn.com/v4/letter/b/f19dbf/32.png) [@bashonubuntu](https://discourse.julialang.org/u/bashonubuntu)\
**Post date:** [April 6, 2020, 4:56pm UTC](https://discourse.julialang.org/t/error-unsatisfiable-requirements-detected-for-package-treeviews-a2a6695c/37117/2 "2020-04-06T16:56:49Z")

</div>

See @chakravala’s comment here [Julia v1.4.0 has been released - #18 by ablaom](https://discourse.julialang.org/t/julia-v1-4-0-has-been-released/36324/18)

You could do `rm -rf ~/.julia` and try again from scratch but I would back up you repl history to not lose anything important.

---

<div class="post-metadata">

**Author:** ![Henderson](https://avatars.discourse-cdn.com/v4/letter/h/f6c823/32.png) [@Henderson](https://discourse.julialang.org/u/Henderson)\
**Post date:** [April 6, 2020, 8:51pm UTC](https://discourse.julialang.org/t/error-unsatisfiable-requirements-detected-for-package-treeviews-a2a6695c/37117/3 "2020-04-06T20:51:23Z")

</div>

I didn’t understand, I’m new to Julia, I haven’t worked with him yet. Because of that, should I be concerned with history? failed to see the difference between ‘rm -rf ~ / .jullia’ and ‘mv ~ / .julia ~ / .julia.bak’ and why you recommended the second and not the first, could you explain it better?

---

<div class="post-metadata">

**Author:** ![bashonubuntu](https://avatars.discourse-cdn.com/v4/letter/b/f19dbf/32.png) [@bashonubuntu](https://discourse.julialang.org/u/bashonubuntu)\
**Post date:** [April 6, 2020, 9:08pm UTC](https://discourse.julialang.org/t/error-unsatisfiable-requirements-detected-for-package-treeviews-a2a6695c/37117/4 "2020-04-06T21:08:41Z")

</div>

When you do `rm -rf ~/.julia` on the command line you are removing the entire` .julia` folder. I would recommend doing this here since your stacktrace suggests that registries within `.julia` folder are dirty ( `C:\Users\hende\.julia\registries\General` — registry dirty`). Best to start afresh.

Now in case you don’t want to start from scratch (sometimes you have commands you have run on your REPL which you don’t want to type out afresh), you can save your `repl_history.jl` etc. For example, your `repl_history.jl` will be in `~/.julia/logs` so you can just save it somewhere else and then copy-back on the new `~/.julia/logs` which will be formed when you install all the packages again from scratch.

`mv ~/.julia ~/.julia.bak` just backs up the `.julia` folder somewhere else. The `rm -rf ~/.julia` command actually removes the` .julia` folder.

---

<div class="post-metadata">

**Author:** ![j2b2](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/j2b2/32/3387_2.png) [@j2b2](https://discourse.julialang.org/u/j2b2)\
**Post date:** [April 7, 2020, 5:09pm UTC](https://discourse.julialang.org/t/error-unsatisfiable-requirements-detected-for-package-treeviews-a2a6695c/37117/5 "2020-04-07T17:09:24Z")

</div>

I don’t think that deleting the .julia directory is a good idea. Generally speaking, “delete anything and restart from scratch” is not a good advice 🙂

The message “`TreeViews has no known versions`” is very strange. Try:

```julia
(@v1.4) pkg> st -m Atom

```

The answer should be something like that:

```julia
Status `~/.julia/environments/v1.4/Manifest.toml`
  [c52e3926] Atom v0.12.10
  [...]
  [e5e0dc1b] Juno v0.8.1
  [7c4cb9fa] LNR v0.2.1
  [50d2b5c4] Lazy v0.15.0
  [...]
  [a2a6695c] TreeViews v0.3.0
  [...]

```

---

<div class="post-metadata">

**Author:** ![Henderson](https://avatars.discourse-cdn.com/v4/letter/h/f6c823/32.png) [@Henderson](https://discourse.julialang.org/u/Henderson)\
**Post date:** [April 8, 2020, 4:20pm UTC](https://discourse.julialang.org/t/error-unsatisfiable-requirements-detected-for-package-treeviews-a2a6695c/37117/6 "2020-04-08T16:20:51Z")

</div>

hey bash, i tried to uninstall and reinstall everything (but it didn’t work out by the command ‘rm’, i assumed it was because this command is for “linux”, but i’m not sure … i forgot to comment that i’m using windows) and the error persisted … I had already given up on Atom and was going to try to install JuliaPro … but, I saw the j2b2 comment and decided to try it … apparently, it’s working now! thanks for your help!

---

<div class="post-metadata">

**Author:** ![Henderson](https://avatars.discourse-cdn.com/v4/letter/h/f6c823/32.png) [@Henderson](https://discourse.julialang.org/u/Henderson)\
**Post date:** [April 8, 2020, 4:30pm UTC](https://discourse.julialang.org/t/error-unsatisfiable-requirements-detected-for-package-treeviews-a2a6695c/37117/7 "2020-04-08T16:30:41Z")

</div>

hello j2b2, I tried ‘st -m Atom’ and REPL presented me with another problem, I researched it and found a similar question that said to try:  
rm (joinpath (homedir (), “.julia”, “registries”); recursive = true),  
found here (kristoffer.carlsson reply):

> [@\* Atom (not found in project, manifest or registry)](https://discourse.julialang.org/t/atom-not-found-in-project-manifest-or-registry/13380):
>
> Press Enter to start Julia. Hold on tight while we’re installing some packages for you. This should only take a few seconds… ERROR: LoadError: The following package names could not be resolved: Atom (not found in project, manifest or registry) Please specify by known name=uuid. // win10 ; julia:１．０

after executing this command, I restarted Atom and it no longer presented the error “ERROR: Unsatisfiable requirements detected for package TreeViews [a2a6695c]”  
and then I ran the command you recommended and it worked as you said it would work!  
I’m just finding the computer and Atom a little slow, except this … all seemingly right.  
Thanks a lot for the help! I will try to do what I wanted to do now LOL

---

<div class="post-metadata">

**Author:** ![j2b2](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/j2b2/32/3387_2.png) [@j2b2](https://discourse.julialang.org/u/j2b2)\
**Post date:** [April 8, 2020, 5:17pm UTC](https://discourse.julialang.org/t/error-unsatisfiable-requirements-detected-for-package-treeviews-a2a6695c/37117/8 "2020-04-08T17:17:05Z")

</div>

All is well ! At the beginning of a Juno session, some evaluations are incredibly slow – five seconds or more for `n = 100` ☹ but after some warm up (i.e. compilations in the background, I presume), everything runs quickly.

---

<div class="post-metadata">

**Author:** ![pfitzseb](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/pfitzseb/32/45566_2.png) [@pfitzseb](https://discourse.julialang.org/u/pfitzseb)\
**Post date:** [April 8, 2020, 7:24pm UTC](https://discourse.julialang.org/t/error-unsatisfiable-requirements-detected-for-package-treeviews-a2a6695c/37117/9 "2020-04-08T19:24:35Z")

</div>

> [@j2b2](#):
>
> At the beginning of a Juno session, some evaluations are incredibly slow – five seconds or more for `n = 100`

Yeah, we’re doing a lot of stuff in the background that needs to be compiled initially. A bit unfortunate, but we’ll try to do better.

---

<div class="post-metadata">

**Author:** ![j2b2](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/j2b2/32/3387_2.png) [@j2b2](https://discourse.julialang.org/u/j2b2)\
**Post date:** [April 9, 2020, 11:39am UTC](https://discourse.julialang.org/t/error-unsatisfiable-requirements-detected-for-package-treeviews-a2a6695c/37117/10 "2020-04-09T11:39:26Z")

</div>

For me it’s not a problem. The situation is the same with Plots (another fantastic package). Waiting 20 or 30 seconds before working during one hour or two is not an issue 🙂 But new users have to be clearly warned that it’s not a crazy bug.