GSoC 2022 for Stack

Hey all, Jasper Van der Jeugt sent me a message about GSoC. If anyone is interested in participating on behalf of Stack this year, either as a mentor or a student, please let me know and I'll connect you with Jasper. I've sent similar messages on the Haskell Foundation channels #stack-collabora

Re: Can't open `libgmp.so.10` when using `stack build`

I have no experience with Manjaro, so I'm not sure exactly may be happening here. Perhaps setting LD_LIBRARY_PATH to the dir that contains the .so may help? On Sun, Apr 18, 2021, at 9:17 AM, Noah G. wrote: > Hi all, > > I am trying to use Stack on Manjaro 21.0.1 Ornara. When I run stack build, I

Re: Can the GHC LLVM backend be used "universally" with Stack?

I don't personally know anything about this, I've never really used the LLVM backend or related tools. Maybe others have some experience with this. On Fri, Apr 16, 2021, at 10:12 PM, Howard B. Golden wrote: > Hi, > > Is it possible to install and use a version of Stack where everything (e.g., >

Re: GSoC 2021

Designing a solution is definitely part of the project here. We don't have a complete solution in mind yet. I'm sure plenty of people-myself included-would be happy to provide some feedback and thoughts on what it should look like. Expected skills really just come down to the ability to work on

Stack Governance

I’ve written up an initial proposal and a call for participants in my most recent blog post: https://www.snoyman.com/blog/2021/01/stack-governance/ I’m cross-posting this to multiple areas, since there isn’t an official discussion area determined yet. -- You received this message because you ar

Re: How to satisfy Hackage uploading Stack-based packages

On Wed, Dec 9, 2020 at 5:33 PM sshuck wrote: > Fantastic, thanks for the quick reply, digging in, and the suggestions. > > Just to get over the hump, I did two more releases, the first manually > relaxing the text lower bound (failed), and the second removing > --pvp-bounds altogether (succeeded)

Re: How to satisfy Hackage uploading Stack-based packages

You can see the cabal build error by clicking on the "build log" link on your Hackage page, which goes to https://hackage.haskell.org/package/pcre2-1.0.0/reports/2. Here's the juicy bit: [__1] rejecting: text-1.2.3.2/installed-1.2.3.2 (conflict: pcre2 => text>=1.2.4.0 && <1.3) [__1] trying: text-1

Re: How to ghc "Finding imports" on stack

You can use source-dirs (in hpack/package.yaml) or hs-source-dirs (in cabal files) to specify the directory. Though standard practice these days in Haskell projects is to put the code in an src directory. For more information on hpack settings and some examples, check out: https://github.c

Platform support for Stack 2.3 release

Hi all, For the upcoming 2.3 release of Stack, we're going to be reducing 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

Re: Generating fully resolved snapshots

sometimes a need of our own. > > On Wed, Apr 1, 2020 at 7:10 PM Alexander Bondarenko > wrote: > > > > Thanks! This would be most helpful. > > > > On Wednesday, April 1, 2020 at 11:55:44 AM UTC+3, Michael Snoyman wrote: > >> > >> Thanks for rai

Re: Generating fully resolved snapshots

Thanks for raising this before the release :) The functionality for adding complete package information to a snapshot file lives in the pantry package, not in Stack. I think I'd like to go in the direction of exposing this functionality via Pantry instead of Stack, since I don't want to add the co

Re: Specify executable path?

You can use `stack install` or `stack build --copy-bins` with `--local-bin-path` On Thu, Oct 10, 2019 at 11:01 PM Casper T. Hansen wrote: > Is there a way to instruct stack on where to place the executable once it > has been built? > Currently I use: find ./.stack-work/install/x86_64-linux/ -nam

Re: I am not able to use stack

version of ghc. It is > interesting, but new versions of sbcl always work with older programs. Does > Haskell need old compiler versions for older programs? It seems that there > is no effort to keep backward compatibility. > > > Em ter, 23 de jul de 2019 às 11:06, Michael Sn

Re: I am not able to use stack

yi is not present in recent Stackage snapshots. I'm not particularly fond of Stack's behavior in this case; I'd rather it be more explicit about adding packages outside of a snapshot. In any event, if you check out the yi page on stackage.org[1], you can see that the last snapshot to include yi is

mirrors.json is expired

Currently, the mirrors.json file on Hackage is expired, which may cause issues for Stack users, especially for first time users trying to download the package index. There's a full explanation and a workaround available at: https://github.com/commercialhaskell/stack/issues/4928 Even if you're not

Re: Stack 2 release plans

? > How can we migrate? > > 2019年4月25日(木) 12:36 Michael Snoyman : > >> I've published a blog post with plans for changes to Stackage and the >> release of Stack 2. There are some big changes in Stack 2, so I'd strongly >> encourage users to do some testi

Stack 2 release plans

I've published a blog post with plans for changes to Stackage and the release of Stack 2. There are some big changes in Stack 2, so I'd strongly encourage users to do some testing before release to see if any workflows have been significantly impacted. -- You received this message because you are

STACK_LOCK lockfile support in Stack

Hi all, There's a feature which has been available in Stack for a while now: respecting a `STACK_LOCK` environment variable to cause some locking to occur while using Stack. This feature is off by default, and I don't believe is very well documented. I'm also uncertain if it's used at all, or—with

Re: Create docker

I use Docker extensively in Haskell projects, both for builds and deployments. We do this for most work at FP Complete as well, and most of our clients do too. The issue you're running into is that you're using a Haskell _build_ image (which includes GHC and other build tools) for creating a runtim

Re: High CPU usage on Mac OS

ere is a workaround? > Because, I cannot for sure continue like this...! > > Thanks in advance! > > Τη Κυριακή, 20 Ιανουαρίου 2019 - 7:03:56 μ.μ. UTC+1, ο χρήστης Michael > Snoyman έγραψε: >> >> If it's high with both cabal and stack, it's most likely the compil

Re: High CPU usage on Mac OS

If it's high with both cabal and stack, it's most likely the compilation with GHC itself. The best way to check would be to open up Activity Monitor, turn to the CPU tab, sort by CPU usage descending, and then start compiling. The culprit should be readily apparent. On Sat, Jan 19, 2019 at 7:25 PM

Re: Proposal: Stack Code of Conduct

Thanks for bringing it up. We're having a bit of a discussion over on the issue tracker about it: https://github.com/snoyberg/stack-coc/pull/3#issuecomment-437085367 On Fri, Nov 9, 2018, 1:34 AM Magnus Therning On Wed, 7 Nov 2018 at 08:47, Michael Snoyman wrote: > > > > I'

Proposal: Stack Code of Conduct

I've put together a blog post outlining some thoughts around an unofficial code of conduct: https://www.snoyman.com/blog/2018/11/proposal-stack-coc If you're interested, please also see the Github repo: https://github.com/snoyberg/stack

Re: Ask stack for local filepath of downloaded repo after compilation

; If this cannot already be done with the existing CLI, perhaps it would be > worthwhile to open a feature request. It seems like the sort of capability > one might expect to find under `stack path`. > > -- Dan Burton > > > On Sat, Oct 20, 2018 at 1:08 PM Michael Snoyman &

Re: Ask stack for local filepath of downloaded repo after compilation

I think this is too abstract a question to know how to answer it. What questions do you want to ask? Also, most of the usage of that directory will be changing drastically in the next release of Stack due to the introduction of pantry, which handles downloaded packages more efficiently. > On 1

Re: Windows error with LTS 12.6

Running stack upgrade should be sufficient. On Sun, Aug 19, 2018, 9:33 PM aditya siram wrote: > The offending line in bhoogle-0.1.3.4's Cabal file is: > > license: BSD-3-Clause OR Apache-2.0 > > > > On Sunday, August 19, 2018 at 11:20:27 AM UTC-7, aditya siram wrote: >> >> I just upg

Re: Can't build cassava (for csv file I/O) (my first attempt to use stack to build something useful)

What version of Stack are you using? What message do you get if you remove the entire extra-deps section? On Sun, Aug 12, 2018, 6:07 AM Jack Vice wrote: > I am trying to import .csv data and so I am trying to build a simple > example using cassava and I have run out of ideas to get it to work.

Re: stack setup ExitFailure 2 installing ghc os Mac OS High Sierra

ug] Configuration done, ready to 'make > install' > @(src/Stack/Setup.hs:1097:54) > 2018-08-05 02:39:51.247017: [debug] (see README and INSTALL files for > more info.) > @(src/Stack/Setup.hs:1097:54) > 2018-08-05 02:39:51.247327: [debug] > *

Re: stack setup ExitFailure 2 installing ghc os Mac OS High Sierra

Please rerun with --verbose to get more information on how it's failing. On Sun, Aug 5, 2018, 12:54 AM Bryan Dunphy wrote: > stack --version > > Version 1.7.1, Git revision 681c800873816c022739ca7ed14755e85a579565 (5807 > commits) x86_64 hpack-0.28.2 > > > > message is: > > > stack build > > Pr

Re: unrecognized 'configure' option `--with-hpack=

you for responding. > > A minimal project can be found on https://github.com/ > MuratOzsoyler/stack-with-hpack-problem. README explains extensively how > to reproduce the problem. > > Thanks in advance for your kind help. > > 17 Nis 2018 Sal, 09:51 tarihinde, Michael Sno

Re: 'stack build' fails; can't seem to copy over file.

nesday, March 21, 2018 at 1:37:29 AM UTC-5, Michael Snoyman wrote: >> >> Does the directory C:\sr\snapshots\9f8b1558\doc exist? Are you able to >> manually create files in it? >> >> On Mon, Mar 19, 2018 at 9:13 PM, Lance Clark wrote: >> >>> Here’s the o

Re: 'stack build' fails; can't seem to copy over file.

Does the directory C:\sr\snapshots\9f8b1558\doc exist? Are you able to manually create files in it? On Mon, Mar 19, 2018 at 9:13 PM, Lance Clark wrote: > Here’s the output for that: http://pastebin.com/1Kdz3NHX > > On Mar 19, 2018, at 01:06, Michael Snoyman wrote: > > Can you t

Re: 'stack build' fails; can't seem to copy over file.

Can you try running with --cabal-verbose and --verbose? On Mar 16, 2018 5:37 PM, "Lance Clark" wrote: > *bump* > > On Tuesday, March 6, 2018 at 4:45:04 PM UTC-6, Lance Clark wrote: >> >> Yes, I have. I was able to build the same project on OSX, so it seems to >> be specific to Windows 7 64-bit s

Stack patching policy

I've written up a blog post about a policy change in handling patches to upstream dependencies: https://www.snoyman.com/blog/2018/02/stack-patching-policy This will in particular impact those packaging Stack, such as Linux distro package maintainers. There's a designated Github issue for discussi

Re: Using stack to provide a consistent build environment for something that is not a cabal package?

put 'packages: []' and tried to 'stack build' of course I got an > error saying that it could not find a package. But once I figured out that > I have to say 'stack build package1 package2 ...' it works great. Thanks > again for the help --- and also thanks t

Re: Using stack to provide a consistent build environment for something that is not a cabal package?

IIUC, you're looking to define a `stack.yaml` file which will set up all of the packages and settings, and then have a script you run to tell Stack to build the appropriate packages. That sounds fine; I think the pieces you're missing are: * In order to say "I have no local packages," include the

Re: Confused by stack's behaviour when changing targets

It's a bug that was just fixed on master and stable. See https://github.com/commercialhaskell/stack/issues/3732 On Thu, Jan 11, 2018, 5:32 PM Arnaud Bailly wrote: > Hello (and Happy New Year to the list), > > I am a little bit puzzled by stack's behaviour w.r.t to build targets > selection. > >

Re: Adding a stack.yaml to containers, will this break anything?

It will have no impact, for a few reasons: 1. Stackage doesn't pay any attention to stack.yaml files 2. Unless you modify containers.cabal, the stack.yaml file will not be included in the tarball uploaded to Hackage On Thu, Dec 28, 2017 at 6:06 PM, Matt Renaud wrote: > Hey! I've recently starte

Dropped packages following LTS 10

Copied from: https://www.snoyman.com/blog/2017/12/dropped-packages-following-lts-10 tl;dr: Check this pull request to see if your package was just removed from Stackage Nightly. Stackage Nightly maintains a set of upper bounds to give package mai

Re: get source code by module name

I can't think of an easy way to do it. It will come down to: * Looking up which package the module came from (likely in the GHC package database) * Figuring out if it's in the snapshot or local (the `stack query` command may help here) * Finding the relevant source code, checking hs-source-dirs in

Re: Custom snapshot without resolver

You can use a resolver value of ghc-8.2.2 or similar for that case. On Fri, Dec 15, 2017, 10:56 AM Jan von Löwenstein wrote: > Hi, > > would it be possible to support custom snapshots that start kind of empty, > i.e. without resolver? > > I want to provide GHC via --system-ghc anyway and would h

Re: Problems with custom snapshots

Awesome, glad to hear it's working. On Fri, Dec 8, 2017 at 11:17 PM, Mark Fine wrote: > Thanks Michael! > > I was able to workaround the issue by installing the dependencies > independently. These custom snapshots are great! > > Mark > > On Thu, Dec 7, 2017

Re: Problems with custom snapshots

Option 3: try out this PR :) https://github.com/commercialhaskell/stack/pull/3632 On Fri, Dec 8, 2017 at 8:12 AM, Michael Snoyman wrote: > I know this bug :(. It's an old Cabal bug, where build-depends for > non-buildable components are still required. When dealing with older Cabal

Re: Problems with custom snapshots

I know this bug :(. It's an old Cabal bug, where build-depends for non-buildable components are still required. When dealing with older Cabal libraries, we need to make sure those libraries are available, even though they aren't needed. This isn't custom snapshot specific, you can reproduce by wipi

Re: Win32 binary disappeared

On Thu, Dec 7, 2017 at 2:49 PM, Neil Mitchell wrote: > Can I suggest that in future you leave the old binaries around until > the new ones are available? My Windows CI automatically hits that URL, > so it broke :( > > On Thu, Dec 7, 2017 at 12:28 PM, Michael Snoyman > wrote:

Re: Win32 binary disappeared

I believe there are plans to release it still. As the release announcement mentioned, we didn't complete the normal release procedure to rush the fix for GHC 8.2, and some binaries are still being compiled. On Thu, Dec 7, 2017 at 2:13 PM, Neil Mitchell wrote: > Hi, > > The page https://www.stack

Re: ANN: Release candidate for stack-1.6.1

Looks like you're running into https://github.com/commercialhaskell/stack/issues/3624. Since newer versions of GHC are pulling in cabal files in the 2.0 format, versions of Stack without the Cabal-2.0 library (meaning: everything before 1.6) aren't supported. I've requested that such cabal files be

Re: Plugin support

I don’t understand either gitit’s source code or stack’s > philosophy/intent, so have no idea what the correct solution is. > > — Perry > > > On Oct 17, 2017, at 1:52 AM, Michael Snoyman > wrote: > > I can't speak for others, but from this email I don't underst

Re: Native, non-haskell libraries in stack, cabal, haskell

On Tue, Oct 17, 2017 at 3:15 PM, Nehal Patel wrote: > Hi -- I'm new to stack, haskell, etc and I am confused about how to reason > about build repeatability when consuming packages that rely on "native, > non-haskell libraries" (e.g. libcairo). > > * Is it the case that some of the packages in LT

Re: Additional group moderators

Thanks to all the volunteers, we now have three more people as moderators on this list. On Tue, Oct 17, 2017 at 8:43 PM, Michael Snoyman wrote: > Hi all, > > This mailing list is moderated to avoid spam. I've been doing most of the > approvals for first time submitters, but it

Additional group moderators

Hi all, This mailing list is moderated to avoid spam. I've been doing most of the approvals for first time submitters, but it would be nice to have a few others on the team in case I'm unavailable. The workload here is _really_ small: 5-10 minutes a week tops. The basic idea is: * Get a moderator

Re: Plugin support

I can't speak for others, but from this email I don't understand what the question is. I'm personally not familiar with the plugin mechanism provided by Gitit. Perhaps you can provide a little more detail? On Sat, Oct 14, 2017 at 3:25 AM, Perry Wagle wrote: > Gitit is a wiki written in GHC/Haske

Feedback requested: GHC 7.10 support for Stack codebase

I've opened up an issue and would appreciate some simple thumbs-up/thumbs-down feedback for those interested: should we drop support for GHC 7.10 within the Stack codebase so we can use less Template Haskell (favoring CallStacks instead). Note that this does _not_ affect projects using Stack, just

Re: libgmp in non-standard location

I'm not expert on this, but I believe you'll need to set LD_CONFIG appropriately instead of using --extra-lib-dirs. The --extra-lib-dirs is not used during GHC sanity check if I remember correctly. On Sun, Jul 23, 2017 at 11:56 PM, Jan von Löwenstein < jan.loewenst...@gmail.com> wrote: > Hi, > >

Re: Why is stack not using the home directory on Windows?

How did you install Stack? Do you possibly have the STACK_ROOT environment variable set? On Wed, Jul 19, 2017, 2:58 PM Hristo Hristov wrote: > Hello > > On Windows stack is downloading stuff to the root drive C:\sr\config.yaml > > Why isn't stack using %LOCALAPPDATA% or any of the appropiate Win

Re: Extensible snapshots & local paths

d dependencies of > master. Could turn out I would not safe a bit right now. > > Anyway, great to see extensible snapshots will come and will include the > possibility to ship dependencies as tarballs. > > Michael Snoyman schrieb am Di., 18. Juli > 2017, 20:33: > >> Manny

Re: Extensible snapshots & local paths

ild from master > soon. Any idea when the next release is planned? > > 1.4.0 was released in March, wasn't it? Release before that was December. > Not sure if that already makes a three month release schedule... ;) > > Michael Snoyman schrieb am Mo., 17. Juli > 2017, 05:34: >

Re: Extensible snapshots & local paths

kell. This is actually my > first Haskell based project and while I think I learned a lot since > November last year there is still so many things ahead... > > Best > Jan > > Michael Snoyman schrieb am Sa., 15. Juli > 2017, 20:23: > >> On mobile, apologies for brevit

Re: Extensible snapshots & local paths

On mobile, apologies for brevity. Your use case makes sense. I can think of two workarounds. 1. Allow an explicit opt in to say "allow file paths, I know what I'm doing" 2. Support local tarballs, especially if we include a sha256 of the tarball contents (a feature I'm planning to add next week)

Enable --install-ghc by default?

I've received a request from the Haskell website working group to make a modification to Stack to simplify the new user onboarding process. Specifically: change the default behavior to --install-ghc, meaning that if you run a command like `stack build` and the appropriate GHC is not installed, it w

Re: stack setup fails with libgmp in nonstandard location

Does setting LD_LIBRARY_PATH fix the problem? On Fri, Jun 2, 2017 at 5:37 PM, 'Stephan Schiffels' via haskell-stack < haskell-stack@googlegroups.com> wrote: > Sorry, but does someone know any help here? > > Am Dienstag, 11. April 2017 21:18:52 UTC+2 schrieb Stephan Schiffels: >> >> Hi, I am tryin

Re: different cpp-flags to build library?

Unfortunately, I'm not aware of a better solution, I've had to set things up similarly in Warp, for example. On Tue, May 16, 2017, 12:54 PM Baojun Wang wrote: > Hi list, > > My stack project builds a default library-A (Simple build type), it has an > A-exe which uses library A, this works perfec

Re: sharing precompiled binaries between two different stack root directories/homogeneous workstations

askell_for_5_years_and_heres_how_it_was/dh1ed3g/ > > How feasible would it be to integrate network-based binary caching > capability into Stack? > Would you accept pull requests for it? > > Karl > > > On Wednesday, April 26, 2017 at 10:10:28 PM UTC-7, Michael Snoyman wr

Re: sharing precompiled binaries between two different stack root directories/homogeneous workstations

On mobile, so just a short reply: you could try setting the STACK_ROOT environment variable to the same absolute path on all systems and copy that directory around. On Wed, Apr 26, 2017, 5:42 PM Karl Ostmo wrote: > I and the other members of my project are all using using the same LTS > Haskell

Re: Compiling a shared (DLL) library with stack

I can only speak for myself here, but generating Windows DLLs is simply uncharted waters (whether with or without Stack). I'm not sure if anyone else has given this a shot before either. On Thu, Mar 23, 2017 at 11:32 AM, wrote: > Hello all, > > first of all - my thanks to the developers of stack

Re: Using hint with stack-installed packages

I would imagine this is a matter of setting the appropriate package databases. I haven't played with hint in a while, but I think you can do that by setting GHC_PACKAGE_PATH. If you run `stack exec env`, you should see the correct value. On Wed, Mar 22, 2017 at 3:42 PM, Leonardo Taglialegne < cmt.

Git-based package index support

Stack includes support for getting package indices (the collection of packages and their cabal files) from both an HTTP-downloaded tarball and a Git repository. Up until the most recent release of Stack, the default package index used the all-cabal-hashes repo[1]. As I detailed in a recent blog pos

Re: Odd package-id not satisfied for module when testing

I think the issue here is that: * Your hangman package does not define a library stanza * But your test-suite depends on the hangman library Try removing hangman from build-depends. The weird string at the end is (I believe) a package key. Every package gets such an arbitrary string (based on it

Re: How to pass arguments to build tools like happy

I've never passed in parameters to happy, so I may be unaware of this functionality being available. But to my knowledge, there's no such feature in Stack right now. (Someone please correct me if I'm wrong.) The best way forward would probably be to open up a feature request on Github: https://git

Call for new Stackage Curator

I'm copying the text from my blog post today[1]. On behalf of the Stackage curators, I'm putting out a call for a volunteer to join the team. The Stackage curators are responsible for the day-to-day management of the Stackage project: merging PRs, managing builds, reporting bounds issues and build

Re: [Haskell] problem installing Stack on Ubuntu Virtual Machine

Adding the haskell-stack mailing list, that's more focused than hask...@haskell.org. Just leaving this message on that mailing list in case someone in the future wonders where this conversation is moving to. Short answer: try adding the following to ~/.stack/config.yaml: package-indices: - name: H

Re: Stack profiling defeating stream fusion

This isn't in any way a complete answer, but from within your project directory, you can use `stack exec -- ghc` to compile individual main modules, and play around with different profiling settings. My guess here is that -prof-auto it inserting cost centers in such a way that GHC isn't able to inl

Re: -exe in name of executable

Just remove the -exe in the .cabal file. You can name the file whatever you want there. On Wed, Nov 23, 2016 at 12:37 PM, kees Bleijenberg < k.bleijenb...@lijbrandt.nl> wrote: > If I do 'stack build' stack builds the executable X-exe.exe. > Why is that -exe in the name? How do I let stack bui

Re: stack install to get the latest executable from hackage?

Actually, you probably want to stick to the second one to avoid dependency problems. On Fri, Nov 18, 2016, 2:19 PM Michael Snoyman wrote: > stack install cabal-install-1.24.1.0 > > Or > > stack --resolver nightly --install-ghc install cabal-install > > On Fri, Nov 18, 2016

Re: stack install to get the latest executable from hackage?

stack install cabal-install-1.24.1.0 Or stack --resolver nightly --install-ghc install cabal-install On Fri, Nov 18, 2016, 2:02 PM Rob Stewart wrote: > Hi, > > I'd like to update my cabal-install to 1.24.1.0 . Here's my setup: > > $ cabal --version > cabal-install version 1.22.9.0 > > $ which

Re: Cleaning Services in Srirampura /Cleaning Services in Vivek Nagar

I've turned on moderation for new member posts. Sorry for the noise everyone. On Mon, Nov 14, 2016 at 6:33 AM, busybizz bizz wrote: > Cleaning Services in Bangalore - List of expert cleaners in Bangalore and > cleansing businesses, businesses, price, contact addresses, smartphone > numbers, pers

Re: error removeDirectoryRecursive permission denied

vember 9, 2016 at 2:22:55 PM UTC+1, Michael Snoyman wrote: > > Where did you get Git from? Maybe it's mistakenly setting the files to > readonly? > > My guess is next step would be to create a new recursive delete function > that can handle these types of file permissions

Re: error removeDirectoryRecursive permission denied

Elm\\.stack-work\\downloaded\\7A15yVYjrQP7\\" >> This last line is the directory to delete. >> >> Any idea what is going on? >> >> Kees >> >> >> >> On Monday, November 7, 2016 at 5:21:03 PM UTC+1, Michael Snoyman wrote: >>> >&g

Re: error removeDirectoryRecursive permission denied

27;t be deleted. I've searched in the directory of the > program and its subdirs but nothing is read-only. > The log files in the map logs do not change when I get the error after > stack build. > > Kees > > On Monday, November 7, 2016 at 10:55:26 AM UTC+1, Mic

Re: error removeDirectoryRecursive permission denied

D:\Program > Files\Git\cmd\git.EXE reset --hard 2a026e4c3a93a18006595636e783955223f9b98e > -- > @(System\Process\Read.hs:277:3) > 2016-11-07 10:45:16.290741: [info] Failed to reset to commit > 2a026e4c3a93a18006595636e783955223f9b98e, deleting and re-cloning. > @(Stack\Config.hs:580:

Re: error removeDirectoryRecursive permission denied

There's only one call to removeDirectoryRecursive I see in the Stack codebase, and that applies for install MSYS2 on Windows, which is probably _not_ relevant to what you're doing right now. Do you have any indication from the logs of what was happening immediately before or after? Can you run with

Re: stack build vs stack ghci with FFI libraries

id it - didn't realize you could use location on >> vendored projects, but that makes total sense: >> >> resolver: lts-6.20 >> packages: >> - . >> - location: unix >> extra-dep: true >> - location: serialport >> extra-dep: true >> e

Re: stack build vs stack ghci with FFI libraries

cation: serialport > extra-dep: true > extra-deps: [] > flags: {} > > Thanks! > > Mark > > On Thu, Oct 6, 2016 at 10:22 PM, Michael Snoyman > wrote: > > I'm not a ghci expert, but perhaps marking those vendored libraries as > extra-dep: true would

Re: stack build vs stack ghci with FFI libraries

I'm not a ghci expert, but perhaps marking those vendored libraries as extra-dep: true would help. On Fri, Oct 7, 2016, 8:21 AM Mark Fine wrote: > I have a simple project that's vendoring in serialport and unix packages: > > resolver: lts-6.20 > packages: > - '.' > - './unix' > - './serialport'

Re: Logo

I'm not aware of any official _or_ unofficial logo for Stack yet. Is anyone out there interested in creating one? On Wed, Sep 28, 2016 at 4:57 PM, Leander Kurscheidt < leander.kursche...@gmail.com> wrote: > I am currently working on a patch where the problem arises that we need to > communicate t

Re: ghcjs builds with docker

My guess would be that, in your Dockerfile, you're setting this up as the root user, inside a root-user-specific directory. But from `stack build`, it's running it as your host system user, which doesn't have access to the root home directory's files. Perhaps playing with the PATH would help, but I

Re: Simplifying the travis CI .travis.yml file instructions?

I wasn't actually aware of that separate page. I always just copy the content out of the guide from: https://docs.haskellstack.org/en/stable/GUIDE/#travis-with-caching I'd be in favor also of simplifying the story here, but perhaps others who have been involved with putting these docs together wo

Re: stack hackage index out of date?

There's some bug with the Travis CLI tool, which is causing the previous every-30-minute refresh from Hackage to be delayed to around every 24 hours. I'm working on a fix for this, but in the meanwhile I've manually run the relevant jobs. Hopefully this will be back to normal in the next day or two

Re: Why did Stack stop using Shake?

It wasn't made for deep reasons, it was very likely done for bad reasons driven by Chris and my lack of experience with Shake when working on the initial Stack code. We had a lot of trouble getting reliably coordination between Stack's, Cabal's, and (to a lesser extent) GHC's dependency tracking, a