Skip to main content

conda-forge core meeting 2023-11-15

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


NameInitialsGitHub IDAffiliation
Marcel BargullMBmbargullBioconda/cf
Bianca HendersonBHbeeankhaAnaconda
Mark AndersonMAAmarkanAnaconda
Marcelo TrevisaniMDTmarcelotrevisaniconda-forge
Isuru FernandoIFisurufQuansight
Dave ClementsDPCtnabtafAnaconda
Jaime Rodríguez-GuerraJRGjaimergpQuansight/cf
Matthew R BeckerMRBbeckermrcf
John KirkhamJKjakirkhamNVIDIA/cf
14 people total

Standing items

  • [ ]

From previous meeting(s)

  • (HV) archspec-packages, next steps (feel free to discuss in my absence)
    • we have microarch-level package now 🎉
    • are we ready/willing to build packages for different arches?
    • do we want to set minimal guidelines to avoid CI explosion from feedstocks indiscriminately wanting to build v2,v3,v4 because "it's obviously faster"?
      • need to go through and check whether runtime dispatching is available
      • how to detect macroarchitecture (x86_64 for example)? This was in __arch, but is now not there. how should this be included?
        • Change existing string to include with micro architecture?
        • New virtual package?
        • Discussion continues in issue
  • (JK) m2 recipes
  • (JK) Windows ARM
    • (IF) Call last week with Finn (from Microsoft)
    • (IF) ARM-64 windows CI set up.
    • (IF) Not the whole things, but progress
      • Use ARM64 image using an X86 installer, then use emulation
    • (IF) Will also need m2 recipes (as Python needs these to build)

Active votes

  • [ ]

Your __new__() agenda items

  • (HV) / (WV) Discuss {{ stdlib("c") }} vs. {{ compiler("c", stlib=...) }}, see here.
    • (WV)
      • Still in favor of one Jinja function. Having 2 makes it messy
      • Can try and fix it later if there is demand.
    • (IF)
      • This would add more technical debt to conda-build (?)
    • (WV)
      • conda-build is so much technical debt already.
      • how much should we worry about it.
    • (MB)
      • agree with both
    • (IF)
      • One jinja function would be good, but there isn't a way to do that now.
  • (JK) Travis CI update
    • Hit issues a week ago with staged recipes because Travis gave us API issues
    • Also long term issues with token resets from Travis.
    • Had us resync the bots
    • GitHub bots couldn' start CI...
    • (MB) Did anyone from conda-forge ask for linux-arm?
      • (JK) We haven't even discussed it.
    • (IF) JRG addded a feature to admin-requests.
  • (JK) Windows CUDA 12
  • (JK) Results from conda-smithy 3.28.0
  • (HV) libboost 1.82 migration update & next steps
    • almost 200 PRs merged
    • long tail of packages that don't build (e.g. have open PRs for old boost migrations)
    • ~70% are estimated to be done
    • do one last pass for bot errors and unsolved feedstocks, then should be close
  • (JK) Custom license discussion

Pushed to next meeting


  • [ ]