# Juliaup in PATH, but julia not in PATH

**URL:** <https://discourse.julialang.org/t/juliaup-in-path-but-julia-not-in-path/92889>\
**Category:** Package Management\
**Tags:** path, juliaup\
**Created:** [January 12, 2023, 6:55pm UTC](https://discourse.julialang.org/t/juliaup-in-path-but-julia-not-in-path/92889 "2023-01-12T18:55:10Z")\
**Posts on this page:** 19\
**Page:** 1

<div class="post-metadata">

**Author:** ![wakelin-g](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/wakelin-g/32/45811_2.png) [@wakelin-g](https://discourse.julialang.org/u/wakelin-g)\
**Post date:** [January 12, 2023, 6:55pm UTC](https://discourse.julialang.org/t/juliaup-in-path-but-julia-not-in-path/92889/1 "2023-01-12T18:55:10Z")

</div>

Just deleted Julia from my computer and reinstalled via juliaup. All seemed to work well, no issues installing or accessing juliaup from the shell, but for some reason I can’t access julia itself.

![image](https://global.discourse-cdn.com/julialang/original/3X/9/9/99528f0e39f86a60372313de9e740d85fc7720de.png)

Anyone have any idea as to why this would be happening?

Thanks,

GW

---

<div class="post-metadata">

**Author:** ![wakelin-g](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/wakelin-g/32/45811_2.png) [@wakelin-g](https://discourse.julialang.org/u/wakelin-g)\
**Post date:** [January 12, 2023, 6:55pm UTC](https://discourse.julialang.org/t/juliaup-in-path-but-julia-not-in-path/92889/2 "2023-01-12T18:55:43Z")

</div>

And yes, I’ve restarted the shell many times.

---

<div class="post-metadata">

**Author:** ![StefanKarpinski](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/stefankarpinski/32/24_2.png) [@StefanKarpinski](https://discourse.julialang.org/u/StefanKarpinski)\
**Post date:** [January 12, 2023, 6:56pm UTC](https://discourse.julialang.org/t/juliaup-in-path-but-julia-not-in-path/92889/3 "2023-01-12T18:56:23Z")

</div>

What’s in your PATH?

---

<div class="post-metadata">

**Author:** ![mkitti](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/mkitti/32/12459_2.png) [@mkitti](https://discourse.julialang.org/u/mkitti)\
**Post date:** [January 12, 2023, 8:08pm UTC](https://discourse.julialang.org/t/juliaup-in-path-but-julia-not-in-path/92889/4 "2023-01-12T20:08:33Z")

</div>

How did you install juliaup? Can you access `julialauncher`?

---

<div class="post-metadata">

**Author:** ![jdad](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/jdad/32/4739_2.png) [@jdad](https://discourse.julialang.org/u/jdad)\
**Post date:** [January 12, 2023, 8:44pm UTC](https://discourse.julialang.org/t/juliaup-in-path-but-julia-not-in-path/92889/5 "2023-01-12T20:44:09Z")

</div>

What does `juliaup status` shows? (to be sure that the `release` version has been `add`ed)

---

<div class="post-metadata">

**Author:** ![wakelin-g](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/wakelin-g/32/45811_2.png) [@wakelin-g](https://discourse.julialang.org/u/wakelin-g)\
**Post date:** [January 12, 2023, 9:05pm UTC](https://discourse.julialang.org/t/juliaup-in-path-but-julia-not-in-path/92889/6 "2023-01-12T21:05:25Z")

</div>

Just `/home/user/.juliaup/bin` as it relates to julia or juliaup.

---

<div class="post-metadata">

**Author:** ![wakelin-g](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/wakelin-g/32/45811_2.png) [@wakelin-g](https://discourse.julialang.org/u/wakelin-g)\
**Post date:** [January 12, 2023, 9:07pm UTC](https://discourse.julialang.org/t/juliaup-in-path-but-julia-not-in-path/92889/7 "2023-01-12T21:07:50Z")

</div>

![image](https://global.discourse-cdn.com/julialang/original/3X/a/1/a1b8242c28ff4f2aaf3f3ac34072970d3df43bfa.png)

I’ve tried both using default and specifying the julia build (julia +release), neither seem to work.

---

<div class="post-metadata">

**Author:** ![StefanKarpinski](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/stefankarpinski/32/24_2.png) [@StefanKarpinski](https://discourse.julialang.org/u/StefanKarpinski)\
**Post date:** [January 12, 2023, 9:10pm UTC](https://discourse.julialang.org/t/juliaup-in-path-but-julia-not-in-path/92889/8 "2023-01-12T21:10:27Z")

</div>

What’s in that directory?

---

<div class="post-metadata">

**Author:** ![wakelin-g](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/wakelin-g/32/45811_2.png) [@wakelin-g](https://discourse.julialang.org/u/wakelin-g)\
**Post date:** [January 12, 2023, 9:17pm UTC](https://discourse.julialang.org/t/juliaup-in-path-but-julia-not-in-path/92889/9 "2023-01-12T21:17:35Z")

</div>

The binaries for juliaup and julialauncher, both of which are functional.

@mkitti Actually, yes…I can access julialauncher from the shell. I guess an easy fix would be to add an alias “julia” that points to julialauncher?

---

<div class="post-metadata">

**Author:** ![davidanthoff](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/davidanthoff/32/223493_2.png) [@davidanthoff](https://discourse.julialang.org/u/davidanthoff)\
**Post date:** [January 12, 2023, 9:19pm UTC](https://discourse.julialang.org/t/juliaup-in-path-but-julia-not-in-path/92889/10 "2023-01-12T21:19:36Z")

</div>

The normal setup routine for Juliaup should have placed a symlink `julia` to `julialauncher` into the `/home/user/.juliaup/bin` folder. So the real question is why that didn’t happen 🙂 Was there an error message during setup? How exactly did you install?

---

<div class="post-metadata">

**Author:** ![jdad](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/jdad/32/4739_2.png) [@jdad](https://discourse.julialang.org/u/jdad)\
**Post date:** [January 12, 2023, 9:21pm UTC](https://discourse.julialang.org/t/juliaup-in-path-but-julia-not-in-path/92889/11 "2023-01-12T21:21:49Z")

</div>

I am surprised, in my installations `juliaup` folder is not at the home directory but inside the `.julia` one. How did you get it and installed it? What is the version used?

---

<div class="post-metadata">

**Author:** ![davidanthoff](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/davidanthoff/32/223493_2.png) [@davidanthoff](https://discourse.julialang.org/u/davidanthoff)\
**Post date:** [January 12, 2023, 9:26pm UTC](https://discourse.julialang.org/t/juliaup-in-path-but-julia-not-in-path/92889/12 "2023-01-12T21:26:55Z")

</div>

This change a while ago, i.e. the current version now puts the `julialauncher` and `juliaup` binaries and `julia` symlink into a folder called `~/.juliaup` by default, but the actual Julia versions still get installed into the depot, i.e. `~/.julia/juliaup`. There is no need to change this for you, though, you can just stick with the installation you have.

---

<div class="post-metadata">

**Author:** ![wakelin-g](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/wakelin-g/32/45811_2.png) [@wakelin-g](https://discourse.julialang.org/u/wakelin-g)\
**Post date:** [January 12, 2023, 9:29pm UTC](https://discourse.julialang.org/t/juliaup-in-path-but-julia-not-in-path/92889/13 "2023-01-12T21:29:43Z")

</div>

@jdad @davidanthoff Sorry guys, just having the realization now that I accidentally closed the terminal a few hours ago which I had assumed didn’t affect the installation process at all as when I reopened it, I could use `juliaup` just fine.

I’m guessing the routine finished everything except for creating that symlink…

---

<div class="post-metadata">

**Author:** ![davidanthoff](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/davidanthoff/32/223493_2.png) [@davidanthoff](https://discourse.julialang.org/u/davidanthoff)\
**Post date:** [January 12, 2023, 9:35pm UTC](https://discourse.julialang.org/t/juliaup-in-path-but-julia-not-in-path/92889/14 "2023-01-12T21:35:16Z")

</div>

I would just do a `juliaup self uninstall` and then reinstall again and make sure you let it finish. If it still doesn’t work, could you copy everything it prints to the output and paste it here?

---

<div class="post-metadata">

**Author:** ![wakelin-g](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/wakelin-g/32/45811_2.png) [@wakelin-g](https://discourse.julialang.org/u/wakelin-g)\
**Post date:** [January 13, 2023, 4:52pm UTC](https://discourse.julialang.org/t/juliaup-in-path-but-julia-not-in-path/92889/15 "2023-01-13T16:52:59Z")

</div>

I can confirm that after doing `juliaup self uninstall` followed by `curl -fsSL https://install.julialang.org | sh` that julia was acessible via the PATH without any issues.

Sorry again for my own mistake.

---

<div class="post-metadata">

**Author:** ![hraftery](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/hraftery/32/45263_2.png) [@hraftery](https://discourse.julialang.org/u/hraftery)\
**Post date:** [June 5, 2026, 5:01am UTC](https://discourse.julialang.org/t/juliaup-in-path-but-julia-not-in-path/92889/16 "2026-06-05T05:01:58Z")

</div>

FWIW, I didn’t interrupt any processes and ended up in the same situation as you (`juliaup` works, reports release is installed and default, but no `julia`). I wasn’t able to repair, but your reinstall steps did the trick.

What I had done recently was upgrade to 1.12. It worked fine afterwards. Today, it worked once, and then failed!

```julia-auto
% julia script1.jl # no problems
% julia script2.jl # command not found

```

So I suspect it’s possible to get into this state when upgrading to 1.12. Perhaps the auto-update thing triggered between the two invocations?

---

<div class="post-metadata">

**Author:** ![czylabsonasa](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/czylabsonasa/32/8663_2.png) [@czylabsonasa](https://discourse.julialang.org/u/czylabsonasa)\
**Post date:** [June 5, 2026, 5:46am UTC](https://discourse.julialang.org/t/juliaup-in-path-but-julia-not-in-path/92889/17 "2026-06-05T05:46:11Z")

</div>

same issue here.  
only `juliaup self uninstall` + `install` solved it  
x

---

<div class="post-metadata">

**Author:** ![hadrien.theveneau](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/hadrien.theveneau/32/218699_2.png) [@hadrien.theveneau](https://discourse.julialang.org/u/hadrien.theveneau)\
**Post date:** [June 5, 2026, 4:18pm UTC](https://discourse.julialang.org/t/juliaup-in-path-but-julia-not-in-path/92889/18 "2026-06-05T16:18:37Z")

</div>

Indeed, just had same problem. At least it seems to be a common bug and not just a mistake I would have made.

---

<div class="post-metadata">

**Author:** ![mkitti](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/mkitti/32/12459_2.png) [@mkitti](https://discourse.julialang.org/u/mkitti)\
**Post date:** [June 6, 2026, 3:21am UTC](https://discourse.julialang.org/t/juliaup-in-path-but-julia-not-in-path/92889/19 "2026-06-06T03:21:38Z")

</div>

There was a buggy release. Running `juliaup self update` now resolves the issue.