bump stack to latest

[ezzieyguywuf]

• dev-haskell/stack-2.3.3: drop old, including pantry mask
• dev-haskell/stack: bump to 2.5.1.1

Leaving this as [draft] until #1118 is merged, as it depends on some of those
changes.

@trofi, similar to some of the conversations we had in #1118, how would you go
about ordering/squashing these commits?

I want/need to drop the old version, since it has a dependency on a masked
pandoc. However, after dropping the old version, we're left with only the
9999 version in the repository until the next commit which adds 2.5.1.1.
Should I just squash these two commits together?

[solpeth]

Chiming in, as indicated in IRC.

I did a hackport merge stack-2.5.1.1 on master, and the only missing dep/QA issue picked up by either repoman or pkgcheck was missing pantry-0.5.1.3. Which other deps are you saying are required from #1118?

Regardless, my advice is to order your commits as follows:

1. Bump pantry to 0.5.1.4 [latest]
2. Unmask pantry [no inconsistency here: a new stack-2.3.3 merge will only pull <dev-haskell/pantry-0.5 due to upper bound constraint]
3. Bump stack to 2.5.1.1
4. Remove stack-2.3.3

There should be no inter-commit inconsistency with this sequence.

[solpeth]

Left a comment on masks. Thank you!

[solpeth]

The above unmasks do not seem to relate to the stack bump. Could you please explain this one to me?

[ezzieyguywuf]

Hm, these must have been why I thought I needed #1118...I'll need to recreate things, see why I thought this was needed.

[ezzieyguywuf]

2\. no inconsistency here: a new stack-2.3.3 merge will only pull `<dev-haskell/pantry-0.5`

If this results in no inconsistency then...why was the pantry ever masked to begin with?

[solpeth]

@ezzieyguywuf iirc it was masked to avoid having to have --backtrack=n when running emerge, or to speed up the calculation and avoid Portage trying to figure out how to both upgrade to pantry-0.5 as well as keeping stack-2.3.3 happy. Regardless, there was no inconsistency as regards any issues like non-existent deps, or anything like that.