conda-forge core meeting 2024-10-30

Add new agenda items under the Your __new__() agenda items heading

• Zoom link
• What time is the meeting in my time zone
• Previous meetings

Attendees

Name	Initials	GitHub ID	Affiliation
Daniel J. Ching	DJC	carterbox	NVIDIA/cf
Matthew R Becker	MRB	beckermr	cf
Filipe Fernandes	FF	ocefpaf	conda-forge
Wolf Vollprecht	WV	wolfv	prefix.dev
Klaus Zimmermann	KZ	zklaus	Quansight
John Kirkham	JK	jakirkham	NVIDIA/cf
Jaime Rodríguez-Guerra	JRG	jaimergp	Quansight/cf

X people total

Standing items

• [ ]

From previous meeting(s)

• [ ]

Active votes

• Three CFEP votes ending tomorrow:
  • https://github.com/conda-forge/cfep/pull/56
  • https://github.com/conda-forge/cfep/pull/55
  • https://github.com/conda-forge/cfep/pull/54

Your __new__() agenda items

• (HV) Bump OSX compilers to clang 18
• (HV) Basic infrastructure for Alma 9
  • Thanks to a bunch of consolidation and automation for sysroot, CDTs & images (pending), this became very easy to add now.
  • Note: CDTs do not contain distro or glibc version anymore, just conda. This works because constraints on sysroot_linux-<arch> and __glibc ensure separation.
• (HV) Upgrading default images to alma8 (for finishing alma8 rollout)
  • Last blocker is around usage of yum_requirements.txt, I did a survey and it looks like we can update to alma8 with minimal issues (PR)
  • AFAICT, we should be able to get rid of DEFAULT_LINUX_VERSION completely
  • (MRB) I think we can deprecate the DEFAULT_LINUX_VERSION option in smithy too if we remove it from the pinnings
  • CONCLUSION: reenable it per issue here: https://github.com/conda-forge/conda-forge-pinning-feedstock/issues/6629
• (HV) Lints/warnings for yum_requirements.txt / CDTs
  • Based on cruft found in above survey, we should IMO warn/error on incorrect entries in yum_requirements.txt
  • May even want to go further and warn if yum_requirements don't show up as CDTs in meta.yaml (though this would need some metadata fixes in our CDTs though)
• (HV) Flang (=windows fortran) migration running, propose to update:
  • write a piggyback migrator (to be written) that switches away from m2w64_* compilers (otherwise migration PRs are no-ops) -- example of the kind of rewrite that would be necessary
  • exclude r-feedstocks, as those are consistently on m2w64_* stack
• (MRB) Fixed some bugs in the rerender infra. Had to add --force to git add for the transferred patches.
• (HV) OpenSSL releases reach host environments as soon as they are available with a >=x.y run_exports.
  • xref: https://github.com/conda-forge/conda-forge-pinning-feedstock/pull/6581
  • IF: Package the latest patch version of the last minor when a new minor comes, and then wait a bit til other distros catch up to see what happens with the fresh release.
    • HV: Patch releases usually take longer than a couple weeks, unless there are serious security bugs.

Pushed to next meeting

• [ ]

CFEPs

• [ ]