Patch 2393 update stack.yaml to use lts-22.22

Title update stack.yaml to use lts-22.22
Superseder Nosy List bfrk
Related Issues
Status accepted Assigned To

Created on 2024-05-19.17:52:26 by bfrk, last changed 2024-05-24.15:04:03 by bfrk.

File name Status Uploaded Type Edit Remove
patch-preview.txt bfrk, 2024-05-19.17:52:26 text/x-darcs-patch
update-stack_yaml-to-use-lts_22_22.dpatch bfrk, 2024-05-19.17:52:26 application/x-darcs-patch
See mailing list archives for discussion on individual patches.
msg23854 (view) Author: bfrk Date: 2024-05-19.17:52:26
The previously listed lts-21.6 would require lots of extra-deps entries
for most of the reverse dependencies of crypton-connection, due to our >=
0.4.0 constraint.

1 patch for repository https://darcs.net/screened:

patch 1b47f05f0403a88b0faf4ff72104d68de01afeff
Author: Ben Franksen <ben.franksen@online.de>
Date:   Sun May 19 19:45:57 CEST 2024
  * update stack.yaml to use lts-22.22
msg23891 (view) Author: ganesh Date: 2024-05-22.11:50:23
No objections (though I don't know if anyone actually relies on this
file? I don't use stack at all personally, and I think for supporting
stackage we should be thinking about the latest snapshots instead)
msg23895 (view) Author: bfrk Date: 2024-05-22.20:52:44
It is convenient to be able to just run 'stack build' and have it 
working, even though we do not officially support that. I try to check 
that it works every now and then, especially before releases.

Getting darcs (back) into stackage is another issue. Yes, for that we 
want to target a recent nightly snapshot, but it hardly makes sense to 
write that into our stack.yaml since it will be out-dated rather 
Date User Action Args
2024-05-19 17:52:26bfrkcreate
2024-05-19 17:53:09bfrksetstatus: needs-screening -> needs-review
2024-05-22 11:50:23ganeshsetstatus: needs-review -> accepted-pending-tests
messages: + msg23891
2024-05-22 20:52:46bfrksetmessages: + msg23895
2024-05-24 15:04:03bfrksetstatus: accepted-pending-tests -> accepted