# Juliaup gets stuck at v1.6.12 for MacOS

**URL:** <https://discourse.julialang.org/t/juliaup-gets-stuck-at-v1-6-12-for-macos/85991>\
**Category:** Tooling\
**Tags:** juliaup\
**Created:** [August 19, 2022, 9:15am UTC](https://discourse.julialang.org/t/juliaup-gets-stuck-at-v1-6-12-for-macos/85991 "2022-08-19T09:15:18Z")\
**Posts on this page:** 10\
**Page:** 1

<div class="post-metadata">

**Author:** ![liuyxpp](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/liuyxpp/32/9870_2.png) [@liuyxpp](https://discourse.julialang.org/u/liuyxpp)\
**Post date:** [August 19, 2022, 9:15am UTC](https://discourse.julialang.org/t/juliaup-gets-stuck-at-v1-6-12-for-macos/85991/1 "2022-08-19T09:15:18Z")

</div>

When I use brew to upgrade `juliaup` version, it shows

```bash
$ brew upgrade juliaup
Warning: juliaup 1.6.12 already installed

```

For 1.6.12, I only get 1.8-rc3, neither 1.8-rc4 nor the 1.8 release. Do I have to upgrade `juliaup` to have those? I get a bit confused about `juliaup`. If I have to upgrade `juliaup` before I can get the new release of julia. What is the point of using `juliaup`?

---

<div class="post-metadata">

**Author:** ![ufechner7](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/ufechner7/32/51363_2.png) [@ufechner7](https://discourse.julialang.org/u/ufechner7)\
**Post date:** [August 19, 2022, 9:19am UTC](https://discourse.julialang.org/t/juliaup-gets-stuck-at-v1-6-12-for-macos/85991/2 "2022-08-19T09:19:31Z")

</div>

This might become fixed in juliaup at some point in time. For now, just use [GitHub - johnnychen94/jill.py: A cross-platform installer for the Julia programming language](https://github.com/johnnychen94/jill.py)

---

<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:** [August 19, 2022, 5:17pm UTC](https://discourse.julialang.org/t/juliaup-gets-stuck-at-v1-6-12-for-macos/85991/3 "2022-08-19T17:17:21Z")

</div>

I would try the `brew upgrade juliaup` again, it takes a little while until new Juliaup versions make it through to brew. I think at this point it should be there.

Or if you install Juliaup with the standalone script (`curl -fsSL https://install.julialang.org | sh`) then you can cut out any delays that the brew publishing of new versions has.

---

<div class="post-metadata">

**Author:** ![liuyxpp](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/liuyxpp/32/9870_2.png) [@liuyxpp](https://discourse.julialang.org/u/liuyxpp)\
**Post date:** [August 20, 2022, 3:09am UTC](https://discourse.julialang.org/t/juliaup-gets-stuck-at-v1-6-12-for-macos/85991/4 "2022-08-20T03:09:03Z")

</div>

> [@davidanthoff](#):
>
> a little while

perhaps means WEEKS? It is tooooooooooo long.

`brew` has a self update command `brew update`. Can `juliaup` have the same? Since `update` is used, maybe `juliaup selfupdate`?

---

<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:** [August 20, 2022, 4:13am UTC](https://discourse.julialang.org/t/juliaup-gets-stuck-at-v1-6-12-for-macos/85991/5 "2022-08-20T04:13:09Z")

</div>

When you install Juliaup from brew, then brew handles updates of Juliaup, and things are out of our control.

If you install Juliaup via the standalone command I posted above, then Juliaup will update itself on a regular schedule, and you can also trigger these self updates at any time via `juliaup self update`.

So, if the brew update cycles are too slow for you, then don’t install it via brew but use the standalone installer instead.

I’m also working on some other features that will make Juliaup updates less necessary, but you’ll have to wait still a bit for that.

---

<div class="post-metadata">

**Author:** ![liuyxpp](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/liuyxpp/32/9870_2.png) [@liuyxpp](https://discourse.julialang.org/u/liuyxpp)\
**Post date:** [August 20, 2022, 4:34am UTC](https://discourse.julialang.org/t/juliaup-gets-stuck-at-v1-6-12-for-macos/85991/6 "2022-08-20T04:34:52Z")

</div>

Thanks for clarification. Then I think the README.md of juliaup should be updated to reflect this important point for Mac and Linux. I can’t figure out how to auto update juliaup itself by reading the juliaup README. So I have gone through all posts in the discourse related to juliaup, and those posts and replies give me the impression that juliaup can only self update in Windows. I think the README should expcilitly state that for Mac and Linux, juliaup can only update itself if you install by scripts but not by `brew`.

Even better, a tutorial on the basic workflow (or best practice) of juliaup is provided in the README for Windows, Mac and Linux. Maybe

For Mac and Linux

Installation (recommeded)

```bash
$ curl -fsSL https://install.julialang.org | sh

```

Daily use

```bash
$ juliaup self update
$ juliaup update

```

---

<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:** [August 20, 2022, 4:47am UTC](https://discourse.julialang.org/t/juliaup-gets-stuck-at-v1-6-12-for-macos/85991/7 "2022-08-20T04:47:45Z")

</div>

> [@liuyxpp](#):
>
> Then I think the README.md of juliaup should be updated to reflect this important point for Mac and Linux.

Yeah, we should probably de-emphasize the `brew` option for now, the standalone version is probably a better choice at the moment.

> [@liuyxpp](#):
>
> Even better, a tutorial on the basic workflow (or best practice) of juliaup is provided in the README for Windows, Mac and Linux.

Yes, I hope to write proper documentation soon, but I’ll probably wait until I’m done adding this other feature that really makes this entire point we are discussing here moot because then Juliaup will know about new Julia versions without a self update.

> [@liuyxpp](#):
>
> Daily use
> 
> ```julia
> $ juliaup self update
> $ juliaup update
> 
> ```

The idea is definitely _not_ that regular users execute these commands every day! The idea is that most users never think about `juliaup` at all, and whenever a new Julia version is released, they are just prompted to run `juliaup update` to get it.

---

<div class="post-metadata">

**Author:** ![liuyxpp](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/liuyxpp/32/9870_2.png) [@liuyxpp](https://discourse.julialang.org/u/liuyxpp)\
**Post date:** [August 22, 2022, 5:36am UTC](https://discourse.julialang.org/t/juliaup-gets-stuck-at-v1-6-12-for-macos/85991/8 "2022-08-22T05:36:14Z")

</div>

I am giving up `juliaup`. It is not yet ready at least for my Mac.

I tried

```bash
$curl -fsSL https://install.julialang.org | sh
info: downloading installer
curl: (35) OpenSSL SSL_connect: SSL_ERROR_SYSCALL in connection to julialang-s3.julialang.org:443
juliaup: command failed: downloader https://julialang-s3.julialang.org/juliaup/bin/juliainstaller-1.7.22-x86_64-apple-darwin /var/folders/49/vv1vdsyj4_9g74lfystrkb2w0000gn/T/tmp.L3HE3aRo/juliainstaller x86_64-apple-darwin

```

---

<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:** [August 22, 2022, 7:42pm UTC](https://discourse.julialang.org/t/juliaup-gets-stuck-at-v1-6-12-for-macos/85991/9 "2022-08-22T19:42:48Z")

</div>

@liuyxpp Hm, that is strange. The first thing that happens when you run

```julia
curl -fsSL https://install.julialang.org | sh

```

is that it downloads a very short shell script, and that shell script then spawns `curl` to download the actual installer binary from [https://julialang-s3.julialang.org/juliaup/bin/juliainstaller-1.7.22-x86\_64-apple-darwin](https://julialang-s3.julialang.org/juliaup/bin/juliainstaller-1.7.22-x86_64-apple-darwin). What is happening on your system is that `curl` for some reason errors when it tries to download that last file.

Are you behind some kind of corporate firewall or proxy server? Or an unreliable internet connection? I googled around for this particular error message a bit, and I only found reports that this error appears if there is something incorrectly configured or setup related to that kind of stuff…

Could you try and see whether you can download the file manually from the link in this post?

---

<div class="post-metadata">

**Author:** ![carstenbauer](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/carstenbauer/32/4981_2.png) [@carstenbauer](https://discourse.julialang.org/u/carstenbauer)\
**Post date:** [August 23, 2022, 5:06am UTC](https://discourse.julialang.org/t/juliaup-gets-stuck-at-v1-6-12-for-macos/85991/10 "2022-08-23T05:06:29Z")

</div>

While it doesn’t help you, I’m using juliaup for months now on different systems including Mac OS (both Intel and M1) and pretty much only had a great experience. So I don’t agree with your “it’s not ready yet” and would encourage you to not give up 🙂