# New tidal 1.51 not available

**URL:** <https://uzu.lurk.org/t/new-tidal-1-51-not-available/1189>\
**Category:** TidalCycles\
**Tags:** installation\
**Created:** [26 May 2020 03:51 UTC](https://uzu.lurk.org/t/new-tidal-1-51-not-available/1189 "2020-05-26T03:51:46Z")\
**Posts on this page:** 8\
**Page:** 1

<div class="post-metadata">

**Author:** ![artheist](https://uzu.lurk.org/user_avatar/uzu.lurk.org/artheist/32/594_2.png) [@artheist](https://uzu.lurk.org/u/artheist)\
**Post date:** [26 May 2020 03:51 UTC](https://uzu.lurk.org/t/new-tidal-1-51-not-available/1189/1 "2020-05-26T03:51:46Z")

</div>

Hi,

It is just me or upgrading tidal just broke my install.  
Weird thing is that the cabal update and new tidal install actually installed version 1.49 and not 1.51, but it says it is up to date ... I am on Mac OSX. Anyone experiencing the same issue and actually solved it.

Help appreciated

@

---

<div class="post-metadata">

**Author:** ![yaxu](https://uzu.lurk.org/user_avatar/uzu.lurk.org/yaxu/32/2_2.png) [@yaxu](https://uzu.lurk.org/u/yaxu)\
**Post date:** [26 May 2020 08:52 UTC](https://uzu.lurk.org/t/new-tidal-1-51-not-available/1189/2 "2020-05-26T08:52:13Z")

</div>

Hi can you share the commands you're running and anything you get back, thanks

---

<div class="post-metadata">

**Author:** ![DanD](https://uzu.lurk.org/user_avatar/uzu.lurk.org/dand/32/484_2.png) [@DanD](https://uzu.lurk.org/u/DanD)\
**Post date:** [26 May 2020 14:14 UTC](https://uzu.lurk.org/t/new-tidal-1-51-not-available/1189/3 "2020-05-26T14:14:43Z")

</div>

I had a similar issue (also on Mac here). Running...

```
cabal v1-update
cabal v1-install tidal

```

...seemed to properly install 1.51 for me. The plain 'cabal update' etc led to all sorts of issues. @yaxu talks about this at the beginning of the latest live stream, with a few different ways of upgrading.

Only issue was then Atom complained about 'multiple packages', but that can be fixed easily as detailed here:

[https://club.tidalcycles.org/t/live-stream-6-tidal-1-5-0-release-party-and-q-a/1152/6?u=dand](https://club.tidalcycles.org/t/live-stream-6-tidal-1-5-0-release-party-and-q-a/1152/6)

---

<div class="post-metadata">

**Author:** ![artheist](https://uzu.lurk.org/user_avatar/uzu.lurk.org/artheist/32/594_2.png) [@artheist](https://uzu.lurk.org/u/artheist)\
**Post date:** [26 May 2020 14:57 UTC](https://uzu.lurk.org/t/new-tidal-1-51-not-available/1189/4 "2020-05-26T14:57:52Z")

</div>

Note : I am on v2 not v1  
Ok, first I did that :  
`cabal update`  
`cabal install tidal --lib` which says I am up to date.  
Now, I gave it a try and did :  
`cabal v2-update`  
`cabal v2-install tidal`  
which gave me this :

```haskell
Resolving dependencies...
Build profile: -w ghc-8.8.3 -O1
In order, the following will be built (use -v for more details):
 - tidal-1.5.2 (lib) (requires download & build)
Downloading tidal-1.5.2
Downloaded tidal-1.5.2
Starting tidal-1.5.2 (lib)
Building tidal-1.5.2 (lib)
Installing tidal-1.5.2 (lib)
Completed tidal-1.5.2 (lib)
Warning: You asked to install executables, but there are no executables in
target: tidal. Perhaps you want to use --lib to install libraries instead.

```

And now if I add the `--lib ` to the command it says it is up to date, and it is still broken when trying to use tidal in vscode. I went a little further but still stuck for the moment ...

---

<div class="post-metadata">

**Author:** ![artheist](https://uzu.lurk.org/user_avatar/uzu.lurk.org/artheist/32/594_2.png) [@artheist](https://uzu.lurk.org/u/artheist)\
**Post date:** [26 May 2020 15:06 UTC](https://uzu.lurk.org/t/new-tidal-1-51-not-available/1189/5 "2020-05-26T15:06:41Z")

</div>

OK, great thanks it worked by removing the default env, so in the end the right combination of commands was :

```haskell
cabal v2-update
cabal v2-install tidal
rm ~/.ghc/x86_64-darwin-8.8.3/environments/default 

```

Ready to Rave  
Thanks very much @yaxu @DanD

---

<div class="post-metadata">

**Author:** ![nuntxaku](https://uzu.lurk.org/user_avatar/uzu.lurk.org/nuntxaku/32/1205_2.png) [@nuntxaku](https://uzu.lurk.org/u/nuntxaku)\
**Post date:** [21 September 2020 16:15 UTC](https://uzu.lurk.org/t/new-tidal-1-51-not-available/1189/7 "2020-09-21T16:15:47Z")

</div>

I've had the same problem trying to update last version. Even if I type that code below

```
cabal v2-update
cabal v2-install tidal
rm ~/.ghc/x86_64-darwin-8.8.3/environments/default 

```

It doesn't work appearing this message in the terminal window:

```
Resolving dependencies...
Up to date
    Warning: You asked to install executables, but there are no executables in
    target: tidal. Perhaps you want to use --lib to install libraries instead.

```

If I use --lib, this message appears again.

When I boot tidal package in atom this message appears

```
Load BootTidal.hs from /Users/eloi/.atom/packages/tidalcycles/lib/BootTidal.hs
t>Loaded package environment from /Users/eloi/.ghc/x86_64-darwin-8.6.5/environments/default
t>: error:
    Ambiguous module name ‘Sound.Tidal.Context’:
      it was found in multiple packages: tidal-1.5.2 tidal-1.5.2

```

Terminal says that if I run this code below

`cabal v2-update 'hackage.haskell.org,2020-09-21T14:43:35Z'`

I'll revert previous state, but I still didn't do it.  
What can I do?

---

<div class="post-metadata">

**Author:** ![nuntxaku](https://uzu.lurk.org/user_avatar/uzu.lurk.org/nuntxaku/32/1205_2.png) [@nuntxaku](https://uzu.lurk.org/u/nuntxaku)\
**Post date:** [21 September 2020 16:53 UTC](https://uzu.lurk.org/t/new-tidal-1-51-not-available/1189/8 "2020-09-21T16:53:41Z")

</div>

I've got it. I just erased the package environement

`/Users/eloi/.ghc/x86_64-darwin-8.6.5/environments/default`

and then cabal install tidal --lib

---

<div class="post-metadata">

**Author:** ![yaxu](https://uzu.lurk.org/user_avatar/uzu.lurk.org/yaxu/32/2_2.png) [@yaxu](https://uzu.lurk.org/u/yaxu)\
**Post date:** [22 September 2020 18:13 UTC](https://uzu.lurk.org/t/new-tidal-1-51-not-available/1189/9 "2020-09-22T18:13:38Z")

</div>

Yes as you probably spotted it tells you the location of the package file to delete when you start `ghci`, including when you start tidal in atom.

I hope these cabal bugs will be fixed soon. In the meantime I recommend using `cabal v1-update` then `cabal v1-install tidal` instead.
