lsst_sims wanted gfortran to be available on Jenkins so they could build oorb. That's now irrelevant given that gfortran is now part of the conda env. If no-one actually needs gfortran explicitly any more we can close the ticket. This is a low priority since it's an old ticket and gfortran is now there.

But you say above that gfortran isn't listed in the bleed, and neither is oorb as far as I know... so why is gfortran available in the env? What's pulling it in?

Anyway, I think it's not impossible we will want oorb/gfortran back at some point, but I don't think it matters: if neither _sims nor _distrib needs it now, I'm in favour of dropping it (assuming it isn't depended on by something else which we do need). We can always add it back when necessary.

I thought this ticket was asking for gfortran because sims wanted to build oorb, not that they wanted to put oorb in the env.

I don't know what is pulling gfortran into the env. Sounds like we should just INVALID this ticket and forget about it. Not really worth this long debate.

gfortran comes as part of the compilers package. It's not explicit, but neither is gcc/g++ in this case.

If we're getting gfortran because of compilers, then there's certainly no action here. Let's mark it invalid.