windows: Resolver lts-19.16 still causes trouble with Win32 for stack buildsjkniivhttp://git-annex.branchable.com/bugs/Resolver_lts-19.16_still_causes_trouble_with_Win32/git-annexikiwiki2022-08-04T16:20:11Zlts versionhttp://git-annex.branchable.com/bugs/Resolver_lts-19.16_still_causes_trouble_with_Win32/comment_1_7fc0ffa7787353cf40fff0bc8da43c1d/Ilya_Shlyakhter2022-07-31T17:25:27Z2022-07-31T17:25:27Z
Did the resolver change to lts-19.16? <a href="https://hackage.haskell.org/package/git-annex-10.20220724/src/stack.yaml"><code>stack.yaml</code> on hackage</a> still seems to say lts-18.
comment 2http://git-annex.branchable.com/bugs/Resolver_lts-19.16_still_causes_trouble_with_Win32/comment_2_0b96112c5d57886add62d79e7bf6044e/jkniiv2022-07-31T18:00:59Z2022-07-31T18:00:59Z
<p>@Ilya: Yes, the change took place in commit <a href="http://source.git-annex.branchable.com/?p=source.git;a=commitdiff;h=b5dc04099efd8b1bd2dbfa09a288518eabf8ceec">b5dc04099efd8b1bd2dbfa09a288518eabf8ceec</a> which was some 24 hours after
release 10.20220724. <img src="http://git-annex.branchable.com/smileys/smile.png" alt=":)" /></p>
comment 3http://git-annex.branchable.com/bugs/Resolver_lts-19.16_still_causes_trouble_with_Win32/comment_3_79cafc76eb23e54ff70c72c2f528e724/joey2022-08-04T16:20:11Z2022-08-01T17:13:22Z
<p>Hey, thanks and sorry for inflicting that stack change on you a second
time. I hypothesized that the toolchain installation, that failed before,
might have been a transient problem, and it seems it was, but now these other
problems surface..</p>
<p>Surprisingly, putting Win32 in the stack file does not break stack build
on linux. But I don't like putting it in there regardless, and needing
to downgrade the other dependencies for it is also suboptimal.</p>
<p>I'll revert the stack.yaml change again, and it seems we'll need to wait for
<span class="createlink"><a href="http://git-annex.branchable.com/ikiwiki.cgi?do=create&from=bugs%2FResolver_lts-19.16_still_causes_trouble_with_Win32%2Fcomment_3_79cafc76eb23e54ff70c72c2f528e724&page=todo%2Fwindows__60__strong__62__58__60__%2Fstrong__62____60__em__62__prepare_for_Win32_not_export_c__60__strong__62__95__60__%2Fstrong__62____60__%2Fem__62__entities" rel="nofollow">?</a>em>entities</span>
to be fixed before updating it.</p>
comment 4http://git-annex.branchable.com/bugs/Resolver_lts-19.16_still_causes_trouble_with_Win32/comment_4_07f1b2eacf7e9e58809ee44fc1d6b574/jkniiv2022-08-03T15:47:07Z2022-08-03T15:47:07Z
<p>@joey: No problem. Most of my git-annex use is rather vanilla (apart from annexing huge files) so I
don't usually need the very latest in git-annex so I can always fall back to an earlier release/build.
It's just that I like to keep track of git-annex's development and make sure it works on Windows most
of the time which means I feel a need to build fresh versions and then kind of dogfood them as soon
as possible. As a non-developer being able to report build errors and other bugs is my way of taking
part in this project and hopefully in the process help make things smoother for the Windows user constituent
that I represent.</p>
<p>PS. Ikiwiki broke that link you made to my related todo. What's with that? The backlink appears in the todo,
however.</p>