# ANN: Julia 0.6.1 is here!

**URL:** https://discourse.julialang.org/t/ann-julia-0-6-1-is-here/6713
**Category:** Announcements
**Tags:** release
**Created:** [October 26, 2017, 9:57pm UTC](https://discourse.julialang.org/t/ann-julia-0-6-1-is-here/6713 "2017-10-26T21:57:06Z")
**Posts on this page:** 15
**Page:** 2

<div class="post-metadata">

### Author: ![joaquimg](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/joaquimg/32/223_2.png) [@joaquimg](https://discourse.julialang.org/u/joaquimg)
#### Post date: [October 30, 2017, 9:06pm UTC](https://discourse.julialang.org/t/ann-julia-0-6-1-is-here/6713/21 "2017-10-30T21:06:14Z")

</div>

can we still download 0.6.0 windows binaries?

---

<div class="post-metadata">

### Author: ![fredrikekre](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/fredrikekre/32/1688_2.png) [@fredrikekre](https://discourse.julialang.org/u/fredrikekre)
#### Post date: [October 30, 2017, 9:17pm UTC](https://discourse.julialang.org/t/ann-julia-0-6-1-is-here/6713/22 "2017-10-30T21:17:18Z")

</div>

Checkout [Releases · JuliaLang/julia · GitHub](https://github.com/JuliaLang/julia/releases)

---

<div class="post-metadata">

### Author: ![mauro3](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/mauro3/32/292_2.png) [@mauro3](https://discourse.julialang.org/u/mauro3)
#### Post date: [October 30, 2017, 9:17pm UTC](https://discourse.julialang.org/t/ann-julia-0-6-1-is-here/6713/23 "2017-10-30T21:17:41Z")

</div>

Adjust edit the links on [Download Julia](https://julialang.org/downloads/) from 0.6.1 to 0.6.0: e.g. [https://julialang-s3.julialang.org/bin/winnt/x64/0.6/julia-0.6.0-win64.exe](https://julialang-s3.julialang.org/bin/winnt/x64/0.6/julia-0.6.0-win64.exe)

---

<div class="post-metadata">

### Author: ![joaquimg](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/joaquimg/32/223_2.png) [@joaquimg](https://discourse.julialang.org/u/joaquimg)
#### Post date: [October 30, 2017, 9:19pm UTC](https://discourse.julialang.org/t/ann-julia-0-6-1-is-here/6713/24 "2017-10-30T21:19:02Z")

</div>

thank you both!  
I could not find them here [https://julialang.org/downloads/oldreleases.html](https://julialang.org/downloads/oldreleases.html) so I began to worry

---

<div class="post-metadata">

### Author: ![BLI](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/bli/32/37206_2.png) [@BLI](https://discourse.julialang.org/u/BLI)
#### Post date: [October 30, 2017, 11:11pm UTC](https://discourse.julialang.org/t/ann-julia-0-6-1-is-here/6713/25 "2017-10-30T23:11:31Z")

</div>

I downloaded v0.6.1 on my home computer (not JuliaPro, but the basic 64bit Julia download). Prior to this, I’ve updated 4 computers to Win10 Fall Creators Update, and I use OneDrive to sync files among these computers. Some observations from an unexperienced Julia user.

1. I thought that “Pkg.update()” would update Julia from v0.6.0 to v.0.6.1. Didn’t happen; I had to uninstall v0.6.0 and then install v0.6.1. No problem, I’m sure it is mentioned somewhere in the documentation.
2. I assumed that packages also had been uninstalled. Not so – when I tried to “Pkg.add()” a package, I was told it was already installed. No problem.
3. “using IJulia” and then “notebook()” – caused some problems. IJulia tried to use Julia v0.6.0 as kernel, which was not there any longer. So I had to remove ("Pkg.rm(“IJulia”)) and re-add it.
4. Key remaining problem: “include” function doesn’t work properly with files stored under the “OneDrive” subdirectory on the C drive (c:\Users\Username\OneDrive\…). Same problem with v0.6.0. I assume this problem is due to a flaw in OneDrive on the first version of Win10 Fall Creators Update?

---

<div class="post-metadata">

### Author: ![fredrikekre](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/fredrikekre/32/1688_2.png) [@fredrikekre](https://discourse.julialang.org/u/fredrikekre)
#### Post date: [October 30, 2017, 11:30pm UTC](https://discourse.julialang.org/t/ann-julia-0-6-1-is-here/6713/26 "2017-10-30T23:30:07Z")

</div>

> [@BLI](#):
>
> thought that “Pkg.update()” would update Julia from v0.6.0 to v.0.6.1.

As the module identifier `Pkg` indicates, this only updates packages.

> [@BLI](#):
>
> I assumed that packages also had been uninstalled. Not so – when I tried to “Pkg.add()” a package, I was told it was already installed. No problem.

Packages are divided into subfolders based on minor releases, typically in `~/.julia/v0.6/` so those packages are installed for all v0.6.x versions.

> [@BLI](#):
>
> using IJulia” and then “notebook()” – caused some problems. IJulia tried to use Julia v0.6.0 as kernel, which was not there any longer. So I had to remove ("Pkg.rm(“IJulia”)) and re-add it.

As per the [IJulia README](https://github.com/JuliaLang/IJulia.jl#updating-julia-and-ijulia), you have to `Pkg.build("IJulia")`.

---

<div class="post-metadata">

### Author: ![SylvainCorlay](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/sylvaincorlay/32/923_2.png) [@SylvainCorlay](https://discourse.julialang.org/u/SylvainCorlay)
#### Post date: [October 31, 2017, 12:29pm UTC](https://discourse.julialang.org/t/ann-julia-0-6-1-is-here/6713/27 "2017-10-31T12:29:48Z")

</div>

It seems that the official build for Julia 0.6.1 requires a different libc version than Julia 0.6.0 on linux, which causes a number of link issues when building extension modules.

Errors such as:

```julia
/home/travis/julia/lib/julia/libLLVM-3.9.so: undefined reference to `std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> >::append(char const*, unsigned long)@GLIBCXX_3.4.21'

```

and many more of the like.

---

<div class="post-metadata">

### Author: ![BLI](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/bli/32/37206_2.png) [@BLI](https://discourse.julialang.org/u/BLI)
#### Post date: [October 31, 2017, 8:42pm UTC](https://discourse.julialang.org/t/ann-julia-0-6-1-is-here/6713/28 "2017-10-31T20:42:02Z")

</div>

Thanks for clarification. Is it only IJulia that needs to be built? I was thinking of running a script with removing and adding the packages, but since there is a problem with Win 10 Fall Creators Update, the include statement doesn’t work for script files stored under the OneDrive directory. Hopefully, MS fixes this soon, though.

---

<div class="post-metadata">

### Author: ![Daneel](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/daneel/32/175_2.png) [@Daneel](https://discourse.julialang.org/u/Daneel)
#### Post date: [November 1, 2017, 8:30am UTC](https://discourse.julialang.org/t/ann-julia-0-6-1-is-here/6713/29 "2017-11-01T08:30:25Z")

</div>

Thanks for the ARM builds as well. I successfully tested it on my Raspberry Pi 3 running Raspbian over the weekend. I was even able to use PyPlot and DataFrames.

👍

---

<div class="post-metadata">

### Author: ![NickM](https://avatars.discourse-cdn.com/v4/letter/n/58f4c7/32.png) [@NickM](https://discourse.julialang.org/u/NickM)
#### Post date: [November 13, 2017, 5:23am UTC](https://discourse.julialang.org/t/ann-julia-0-6-1-is-here/6713/30 "2017-11-13T05:23:28Z")

</div>

Thanks for your work to keep progress on the march!  
I downloaded julia-0.6.1-win64.exe and found that the sha256 from sha_deep_.exe doesn’t match the value listed on the website for the new release for Win-64. This is a first for me.  
Has there been an update to the executable since the sha value was posted.  
I get 2e653519be1986b35814f593d60aa7937f28f2ec158b6f66b040a02af5693069,  
not 776687fc2023b67fd5ee33a4a61417460e88477ef5bed1afcf3007cdd5b9e5bc as the site indicates.  
If my sha calculator is on the fritz, please let me know.

---

<div class="post-metadata">

### Author: ![ararslan](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/ararslan/32/3825_2.png) [@ararslan](https://discourse.julialang.org/u/ararslan)
#### Post date: [November 16, 2017, 9:14pm UTC](https://discourse.julialang.org/t/ann-julia-0-6-1-is-here/6713/31 "2017-11-16T21:14:52Z")

</div>

Good catch. The Windows binaries had to be code signed again with an updated certificate but the SHAs were not updated after that.

---

<div class="post-metadata">

### Author: ![ararslan](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/ararslan/32/3825_2.png) [@ararslan](https://discourse.julialang.org/u/ararslan)
#### Post date: [November 16, 2017, 11:20pm UTC](https://discourse.julialang.org/t/ann-julia-0-6-1-is-here/6713/32 "2017-11-16T23:20:51Z")

</div>

I’ve updated the checksums. Please let me know if you run into any more issues with that.

---

<div class="post-metadata">

### Author: ![NickM](https://avatars.discourse-cdn.com/v4/letter/n/58f4c7/32.png) [@NickM](https://discourse.julialang.org/u/NickM)
#### Post date: [November 16, 2017, 11:36pm UTC](https://discourse.julialang.org/t/ann-julia-0-6-1-is-here/6713/33 "2017-11-16T23:36:43Z")

</div>

I checked the sha265 hashes on the Julia site, but they look the same as they were.

Could you check the results I sent for the win64 executable vs. the one you got?

---

<div class="post-metadata">

### Author: ![ararslan](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/ararslan/32/3825_2.png) [@ararslan](https://discourse.julialang.org/u/ararslan)
#### Post date: [November 17, 2017, 9:07pm UTC](https://discourse.julialang.org/t/ann-julia-0-6-1-is-here/6713/34 "2017-11-17T21:07:41Z")

</div>

Ah sorry, I had forgotten to purge the Fastly cache, so it was still pointing to the old file. It now reflects the updated checksums.

---

<div class="post-metadata">

### Author: ![NickM](https://avatars.discourse-cdn.com/v4/letter/n/58f4c7/32.png) [@NickM](https://discourse.julialang.org/u/NickM)
#### Post date: [November 17, 2017, 10:38pm UTC](https://discourse.julialang.org/t/ann-julia-0-6-1-is-here/6713/35 "2017-11-17T22:38:18Z")

</div>

The hashes now match.  
Thanks.

[Previous page](https://discourse.julialang.org/t/ann-julia-0-6-1-is-here/6713.md?page=1)