Yes, sorry about that. It's fixed now and `stack upgrade` once again works on Linux x86_64.
On Wed, Apr 29, 2020 at 12:33 PM Simon Jakobi <simon.jak...@googlemail.com> wrote: > Hi Manny, > > I just gave "stack upgrade" a try: > > $ stack upgrade >> Current Stack version: 2.1.3, available download version: 2.3.1 >> Newer version detected, downloading >> Querying for archive location for platform: linux-x86_64-static >> Downloading from: >> https://github.com/commercialhaskell/stack/releases/download/v2.3.1/stack-2.3.1-linux-x86_64-static.tar.gz >> Warning: Exception occured when trying to perform binary upgrade: >> Stack executable "stack-2.3.1-linux-x86_64-static/stack" not >> found in archive from >> https://github.com/commercialhaskell/stack/releases/download/v2.3.1/stack-2.3.1-linux-x86_64-static.tar.gz >> CallStack (from HasCallStack): >> error, called at src/Stack/Setup.hs:2012:33 in >> stack-2.1.3-HEoMsL9gvgt2vNexTWWwGx:Stack.Setup >> >> Falling back to source upgrade > > > I'd rather not recompile stack myself. Is the problem with the archive > something that could be fixed? > > Thanks, > Simon > > > > > Am Mi., 29. Apr. 2020 um 21:05 Uhr schrieb Emanuel Borsboom < > ma...@fpcomplete.com>: > >> See https://haskellstack.org/ for installation and upgrade instructions. >> >> Release notes: >> >> - >> >> We have reduced the number of platforms that we support with binary >> releases. >> The reason behind this is that we've been slowed down in our release >> process >> until now with issues trying to build binaries for less common >> platforms. In >> order to make sure we can address issues more quickly (like >> supporting new >> GHC versions), we're limiting support from the Stack team to: >> - Linux 64-bit (static) >> - macOS >> - Windows 64-bit >> >> If others want to provide additional binaries, we will definitely be >> happy >> for the support. But since our CI system is currently able to produce >> these >> three bindists only, that's what we will be providing with the next >> release. >> - >> >> Since we no longer have dynamically linked Linux binaries, we are >> removing >> removing the -static suffix from the static Linux binaries. If you >> have >> scripts to download the latest stable Linux binary, update them to use >> linux-x86_64 instead of linux-x86_64-static (if you are already using >> the >> former, nothing needs to change). For this release, both are >> supported, but >> the next release will no longer have the -static variant. >> - >> >> We are also deprecating the download links at >> https://stackage.org/stack. >> See this page for the current installation instructions: >> https://docs.haskellstack.org/en/stable/install_and_upgrade/. >> - >> >> These are the canonical locations to download the latest stable >> binaries >> from, and will continue to be supported going forward: >> - Linux 64-bit (static): >> https://get.haskellstack.org/stable/linux-x86_64.tar.gz >> - macOS: https://get.haskellstack.org/stable/osx-x86_64.tar.gz >> - Windows 64-bit: >> https://get.haskellstack.org/stable/windows-x86_64.zip >> >> As always, binaries for specific versions are available from the >> Github >> releases: https://github.com/commercialhaskell/stack/releases. >> >> *Changes since v2.1.3.1* >> >> Major changes: >> >> - >> >> setup-info-locations yaml configuration now allows overwriting the >> default locations of stack-setup-2.yaml. >> #5031 <https://github.com/commercialhaskell/stack/pull/5031> >> #2983 <https://github.com/commercialhaskell/stack/issues/2983> >> #2913 <https://github.com/commercialhaskell/stack/issues/2913> >> - >> >> The setup-info configuration key now allows overwriting parts of the >> default setup-info >> - >> >> The --setup-info-yaml command line flag now may be used in all stack >> commands such as stack build, and not only in stack setup >> - >> >> The --setup-info-yaml may specify multiple locations for >> stack-setup.yaml files. >> - >> >> The stack upload can read first reads environment Variable >> $HACKAGE_USERNAME and $HACKAGE_PASSWORD if they are missing only then >> asks for username or password >> - >> >> Fully remove GHCJS support. >> - >> >> Remove the freeze command. It has been replaced by lock files. >> >> Behavior changes: >> >> - >> >> Remove the deprecated --stack-setup-yaml command line argument in >> favor of --setup-info-yaml >> #2647 <https://github.com/commercialhaskell/stack/issues/2647> >> - >> >> We now recommend checking in generated cabal files for repos. When >> generating lock files for >> extra-deps that only include package.yaml files, a deprecation >> warning will be generated. >> Also, those packages will no longer be included in the generated lock >> files. >> See #5210 <https://github.com/commercialhaskell/stack/issues/5210>. >> >> Other enhancements: >> >> - >> >> Add build-output-timestamps flag in yaml. Setting it to true >> prefixes each build log output line with a timestamp. >> - >> >> Show warning about local-programs-path with spaces on windows >> when running scripts. See >> #5013 <https://github.com/commercialhaskell/stack/pull/5013> >> - >> >> Add ls dependencies json which will print dependencies as JSON. >> ls dependencies --tree is now ls dependencies tree. See >> #4424 <https://github.com/commercialhaskell/stack/pull/4424> >> - >> >> Remove warning for using Stack with GHC 8.8-8.10, and Cabal 3.0-3.2. >> - >> >> Allow relative paths in --setup-info-yaml and tool paths >> #3394 <https://github.com/commercialhaskell/stack/issues/3394> >> - >> >> Added the --only-locals flag. See >> #5272 <https://github.com/commercialhaskell/stack/issues/5272> >> >> Bug fixes: >> >> - >> >> Upgrade pantry: module mapping insertions into the database are now >> atomic. >> Previously, if you SIGTERMed at the wrong time while running a >> script, you >> could end up with an inconsistent database state. >> - >> >> --resolver global doesn't retrieve snapshots list from the internet >> beause doesn't need it. See #5103 >> <https://github.com/commercialhaskell/stack/issues/5103> >> - >> >> Fix using relative links in haddocks output. See >> #4971 <https://github.com/commercialhaskell/stack/issues/4971>. >> - >> >> Do not include generated cabal file information in lock files. See >> #5045 <https://github.com/commercialhaskell/stack/issues/5045>. >> - >> >> Use proper Hoogle executable path when installed automatically. See >> #4905 <https://github.com/commercialhaskell/stack/issues/4905> >> - >> >> Fix GHC version for batched package unregistration. See >> #4951 <https://github.com/commercialhaskell/stack/issues/4951> >> - >> >> Use Hoogle from the snapshot used and not the latest version. See >> #4905 <https://github.com/commercialhaskell/stack/issues/4905> >> - >> >> Resolve "'stty' is not recognized". See >> #4901 <https://github.com/commercialhaskell/stack/issues/4901> >> - >> >> Fix missing reconfigure check causing errors when a package gets >> used in multiple projects. See >> #5147 <https://github.com/commercialhaskell/stack/issues/5147> >> >> *Thanks to all our contributors for this release:* >> >> - Adam McCullough >> - Akshay Mankar >> - Brian Wignall >> - Cheah Jer Fei >> - Chris Done >> - David Baynard >> - davit nalchevanidze >> - Dino Morelli >> - Emanuel Borsboom >> - Felix Yan >> - flip111 >> - Flowers Safety >> - Fred Miller >> - Fyrbll >> - gdziadkiewicz >> - Good boy >> - Hypnoes.Liu >> - Iisus >> - Iustin Pop >> - ivanbakel >> - Javier Neira >> - Jeff Happily >> - jeffhappily >> - jneira >> - Justin Le >> - Kirill Zaborsky >> - Leif Metcalf >> - Leonhard Markert >> - Lokesh Mohanty >> - Matt Audesse >> - Michael Snoyman >> - Mihai Maruseac >> - NightRa >> - Phil Ruffwind >> - qinzhenlong >> - Robert Hensing >> - Sasha Bogicevic >> - Sibi >> - Sibi Prabakaran >> - Simon Michael >> - Steve Mao >> - Vlad Ki >> - Xia Li-yao >> >> _______________________________________________ >> Haskell-Cafe mailing list >> To (un)subscribe, modify options or view archives go to: >> http://mail.haskell.org/cgi-bin/mailman/listinfo/haskell-cafe >> Only members subscribed via the mailman list are allowed to post. > > -- You received this message because you are subscribed to the Google Groups "haskell-stack" group. To unsubscribe from this group and stop receiving emails from it, send an email to haskell-stack+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/haskell-stack/CACGj5vKEsQr%3Dp75Qd1gZnGuzL4P7jFCG0Wyp1S1pVwd-zyzpHQ%40mail.gmail.com.
