# ubuntu deployment of up to date version

**URL:** https://discourse.julialang.org/t/ubuntu-deployment-of-up-to-date-version/86496
**Category:** General Usage
**Tags:** installation
**Created:** [August 29, 2022, 1:03pm UTC](https://discourse.julialang.org/t/ubuntu-deployment-of-up-to-date-version/86496 "2022-08-29T13:03:16Z")
**Posts on this page:** 7
**Page:** 1

<div class="post-metadata">

### Author: ![eoli3n](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/eoli3n/32/39186_2.png) [@eoli3n](https://discourse.julialang.org/u/eoli3n)
#### Post date: [August 29, 2022, 1:03pm UTC](https://discourse.julialang.org/t/ubuntu-deployment-of-up-to-date-version/86496/1 "2022-08-29T13:03:16Z")

</div>

I need to automate deployment of julia for 800 hosts for a University.  
On latest Ubuntu LTS, when I `apt install julia` it tells me to `snap install julia`.

On snapcraft, julia package seems to be official but it is in a 2019 version : 1.0.4  
[https://snapcraft.io/julia](https://snapcraft.io/julia)

That’s strange because the package is marked as official, so why isn’t it up to date ?  
From the website : Current stable release: v1.8.0 (August 17, 2022)

---

<div class="post-metadata">

### Author: ![Sukera](https://avatars.discourse-cdn.com/v4/letter/s/ce7236/32.png) [@Sukera](https://discourse.julialang.org/u/Sukera)
#### Post date: [August 29, 2022, 1:08pm UTC](https://discourse.julialang.org/t/ubuntu-deployment-of-up-to-date-version/86496/2 "2022-08-29T13:08:23Z")

</div>

> [@eoli3n](#):
>
> That’s strange because the package is marked as official, so why isn’t it up to date ?

Distribution specific installations are not maintained by julia developers - I’m curious how that account got a “verified” state in the first place.

The only supported binaries are provided on [Download Julia](https://julialang.org/downloads/).

---

<div class="post-metadata">

### Author: ![eoli3n](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/eoli3n/32/39186_2.png) [@eoli3n](https://discourse.julialang.org/u/eoli3n)
#### Post date: [August 29, 2022, 1:17pm UTC](https://discourse.julialang.org/t/ubuntu-deployment-of-up-to-date-version/86496/3 "2022-08-29T13:17:42Z")

</div>

Ok, but those are static installations.

On previous Ubuntu LTS, there was julia package in main repo.

> **[Ubuntu – Details of package julia in focal](https://packages.ubuntu.com/focal/julia)**
>
> high-performance programming language for technical computing

I’ll wait for the jammy version.

---

<div class="post-metadata">

### Author: ![Sukera](https://avatars.discourse-cdn.com/v4/letter/s/ce7236/32.png) [@Sukera](https://discourse.julialang.org/u/Sukera)
#### Post date: [August 29, 2022, 1:22pm UTC](https://discourse.julialang.org/t/ubuntu-deployment-of-up-to-date-version/86496/4 "2022-08-29T13:22:24Z")

</div>

That too is not maintained by the julia developers (I believe that particular one is/was maintained by the debian community(?), which recently [got removed](https://tracker.debian.org/pkg/julia) for being unmaintained). Distributions repackaging julia with custom libraries quite often run into [usage](https://github.com/JuliaLang/julia/issues/43682) [problems](https://wiki.archlinux.org/title/Julia#Installation) due to distributions not shipping the patched dependencies julia itself ships with.

The only official venue for binaries is either the linked download page or the releases on [github](https://github.com/JuliaLang/julia/releases).

---

<div class="post-metadata">

### Author: ![oheil](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/oheil/32/220745_2.png) [@oheil](https://discourse.julialang.org/u/oheil)
#### Post date: [August 29, 2022, 1:37pm UTC](https://discourse.julialang.org/t/ubuntu-deployment-of-up-to-date-version/86496/5 "2022-08-29T13:37:09Z")

</div>

Despite

> The Linux and Mac versions [OF JULIAUP !!] are prerelease versions that should not be used in production environments.

I think you should give

> **[GitHub - JuliaLang/juliaup: Julia installer and version multiplexer](https://github.com/JuliaLang/juliaup)**
>
> Julia installer and version multiplexer. Contribute to JuliaLang/juliaup development by creating an account on GitHub.

a try.  
It would certainly be great to have your feedback on how it is working to overcome the prerelease status of juliaup for linux. I ping @davidanthoff for his attention.

---

<div class="post-metadata">

### Author: ![PabloZubieta](https://avatars.discourse-cdn.com/v4/letter/p/ee7513/32.png) [@PabloZubieta](https://discourse.julialang.org/u/PabloZubieta)
#### Post date: [September 1, 2022, 6:57pm UTC](https://discourse.julialang.org/t/ubuntu-deployment-of-up-to-date-version/86496/6 "2022-09-01T18:57:41Z")

</div>

The julia version in the Snap Store has been updated to latest LTS as of today

---

<div class="post-metadata">

### Author: ![Palli](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/palli/32/3380_2.png) [@Palli](https://discourse.julialang.org/u/Palli)
#### Post date: [September 1, 2022, 9:40pm UTC](https://discourse.julialang.org/t/ubuntu-deployment-of-up-to-date-version/86496/7 "2022-09-01T21:40:11Z")

</div>

I see you’re behind the change, so first, thanks, so I do not sound ungrateful:

> **[GitHub - JuliaCI/julia-snap: Snap setup for Julia](https://github.com/JuliaCI/julia-snap)**
>
> Snap setup for Julia. Contribute to JuliaCI/julia-snap development by creating an account on GitHub.

LTS is a step up (still the wrong Julia version for most users), but at least the old snap was a trap, gave you 32-bit Julia on 64-bit OS, leading to cryptic error with PyCall:

> <https://github.com/JuliaCI/julia-snap/issues/6>
>
> The most recent version of Julia in the official Debian repo is 1.5.3 while the …current LTS is 1.6.4. Given the fact that a lot of people will try to install Julia from the official repos first and how easy is to create a snap from the official binaries in contrast to building debs, it would be convenient to maintain a snap version and eventually drop the outdated package in Debian.
> 
> Some of previous problems:
> 
> 1. Problem of getting the Julia 32 bit in a 64 bit machine - is just some small error in the snapcraft.yaml, \[julia-mrcinv\](https://github.com/mrcinv/julia-snap/) seems to work.
> 2. Snap Store bureaucracy - There is a need for manual approval to get \[multiple channels \](https://snapcraft.io/docs/channels)(eg: stable, lts) and to publish the app using \[classic confinement\](https://snapcraft.io/docs/reviewing-classic-confinement-snaps) (instead of the sandbox permissions), both can be a one time thing, allowing to automate the following releases.   
> 3. Install multiple versions of Julia - This isn't needed for those wanting to use snap as replacement of apt but there is already an \[experimental feature for it\](https://snapcraft.io/blog/parallel-installs-test-and-run-multiple-instances-of-snaps).

I second @eoli3n should try juliaup, because, so far it just works for me on Linux. I used to run Ubuntu, just upgraded to Linux Mint today, and it seems to work there to (predictably, since Mint isn’t tooo different).

I would want the Julia snap to change to rather install juliaup, which actually gets you julia the release version. That’s probably the best option rather than giving up on snap.

I know Mint has misgiving with snap, I forget their tech argument against using/promoting snap (wasn’t about Julia), in favor of flatpak.

FYI: I thought you could still choose either:

```julia
$ snap
Command 'snap' not found, but can be installed with:
sudo apt install snapd

$ sudo apt install snapd
[..]
Package snapd is not available, but is referred to by another package.
This may mean that the package is missing, has been obsoleted, or
is only available from another source

E: Package 'snapd' has no installation candidate

```
