Christopher Nielsen

> Even with `libtorrent-rasterbar` fixed, I'm still seeing the following issue. (And I think I saw the same thing in the previous CI build.) > > ``` > Traceback (most...

In the interim, make Python 3.10 the default, and we'll tackle the Boost fix separately. (It'll potentially need to be applied to all Boost versions, so it's not a 5-minute...

> @mascguy So we pause with this one for a while? Nope, see my later comment, re: making Python 3.10 the default. :-)

Why are you rev-bumping `llvm-15` and `llvm-16`? Unless I'm missing something, that doesn't appear to accomplish anything. (And is something we definitely don't want to do, unless absolutely necessary.)

> Why are you rev-bumping `llvm-15` and `llvm-16`? Unless I'm missing something, that doesn't appear to accomplish anything. (And is something we definitely don't want to do, unless absolutely necessary.)...

From a practical perspective though, rev-bumping even a single `llvm` port will tie up our buildbots for up to 24-ish hours. So we should start with `llvm-16`, and only update...

> From a practical perspective though, rev-bumping even a single `llvm` port will tie up our buildbots for up to 24-ish hours. So we should start with `llvm-16`, and only...

@cjones051073 and @kencu - just a heads-up regarding this impending enhancement. So if you folks are planning to update any of the LLVM ports anytime soon, can you include this...

> what was the reason the addition if these entries was reverted preciously? > > If it was for a good reason we should not add them here again just...

Converting to draft for now, until I've had a chance to test/validate locally.