It might also be good if CI examples we recommend the best practice of specifying an exact Stack version by pointing directly to a specific Github release rather than using the convenience redirects. What happened here is one example of breakage if CI scripts specify stick to a specific version; another would be that a behaviour change in Stack breaks CI.
> On Dec 7, 2017, at 5:34 AM, Michael Snoyman <[email protected]> wrote: > > We should probably change the way that stackage.org <http://stackage.org/> > finds binaries. All of the old binaries are present on Github still, it's > just the lookup that isn't working, since it only considered the most recent > release. > > Yes, this is an ugly situation, we're still trying to play catch-up. > > On Thu, Dec 7, 2017 at 2:49 PM, Neil Mitchell <[email protected] > <mailto:[email protected]>> 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 > <[email protected] <mailto:[email protected]>> wrote: > > 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 <[email protected] > > <mailto:[email protected]>> wrote: > >> > >> Hi, > >> > >> The page https://www.stackage.org/stack/ <https://www.stackage.org/stack/> > >> links to > >> https://www.stackage.org/stack/windows-i386 > >> <https://www.stackage.org/stack/windows-i386>, which now gives a 404. > >> Where did the 32bit binary disappear to? > >> > >> Thanks, Neil > >> > >> -- > >> 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 [email protected] > >> <mailto:haskell-stack%[email protected]>. > >> To post to this group, send email to [email protected] > >> <mailto:[email protected]>. > >> To view this discussion on the web visit > >> https://groups.google.com/d/msgid/haskell-stack/CAKcFpmJY27nB%3D%2BCiS0_6UZ56ePb-DH_0H7c-0VdommRmWqdD%3Dg%40mail.gmail.com > >> > >> <https://groups.google.com/d/msgid/haskell-stack/CAKcFpmJY27nB%3D%2BCiS0_6UZ56ePb-DH_0H7c-0VdommRmWqdD%3Dg%40mail.gmail.com>. > >> For more options, visit https://groups.google.com/d/optout > >> <https://groups.google.com/d/optout>. > > > > > > > -- > 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 [email protected] > <mailto:[email protected]>. > To post to this group, send email to [email protected] > <mailto:[email protected]>. > To view this discussion on the web visit > https://groups.google.com/d/msgid/haskell-stack/CAKA2Jg%2BzQRVzCGPgSp%3D%2BWRSoREyzZHgNSyCqozODLgtgUpK7vQ%40mail.gmail.com > > <https://groups.google.com/d/msgid/haskell-stack/CAKA2Jg%2BzQRVzCGPgSp%3D%2BWRSoREyzZHgNSyCqozODLgtgUpK7vQ%40mail.gmail.com?utm_medium=email&utm_source=footer>. > For more options, visit https://groups.google.com/d/optout > <https://groups.google.com/d/optout>. -- 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 [email protected]. To post to this group, send email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/haskell-stack/27593670-74D2-4ED9-A870-01972D361F69%40fpcomplete.com. For more options, visit https://groups.google.com/d/optout.
