2018-06-26 conda-forge meeting

Pinned Items

New items

  • CJ: report on June 18-20 NYC sprint

    • Sprint in NYC June 18th through 20th for REST API for conda-forge graph and better inspection of CLI/imports/includes for conda-forge packages.

    • Potential place for additional metadata in conda recipes?

      • (from @Jonathan H ) you can clobber/append portions of a recipe with an extra file with conda-build 3

      • recipe_url info for recording repo where a recipe came from: https://github.com/conda/conda-build/pull/2489

  • Moving compiler syntax

    • Run syntax in topo order https://github.com/regro/cf-scripts/issues/214

    • Run compiler move as soon as syntax has moved

    • Formalize pushing to different label (maybe as optional arg to conda-smithy?) (this would also help with RC releases)

Existing Items

  • Finding a good solution to sharing passwords among core

  • Run_exports etc: https://github.com/conda-forge/conda-forge-pinning-feedstock/pull/58

  • Michael Sarahan to document and give demo on how to transition old recipes to new style - https://github.com/conda-forge/AnacondaRecipesSync - 5/1: Will wait for more people on the dev call before Mike talks about this

  • Build packages on C3I and upload to conda-forge

    • Make is missing from the base image for PowerPC internal to Anaconda. Fun times!

    • Mike is open to other people helping with this. If interested, reach out! Helping means trying recipes, debugging any issues, and resolving any merge conflicts that have happened since Mike pulled them in last. Moving target.

    • Packages that have been built https://anaconda.org/cf-cb3 - these may need more work regarding versions. The graph was computed with the versions, but probably should have ignored them. When a pin is older than a newer recipe, the upstream recipe gets missed as a real dependency because of the version mismatch.

  • switch to cb3

    • what kind of things are going to break when we change compilers?

      • (@Jonathan H had a great response that I hope he’ll clarify here:) tl;dr C++ ABI

      • Some details on libstdc++ dual ABI, https://gcc.gnu.org/onlinedocs/libstdc++/manual/using_dual_abi.html

  • Making the agenda and notes public again.

    • John will see if we can make dropbox paper readable by the world

    • other options are to just post the notes somewhere public after the meeting

  • conda-forge blog

Discussed Items

Done

  • add something to the bot to add new PRs that manage the cb2 → cb3

    • e.g., if a compiler is detected, add the right compilers for the right files (Justin, nominally — @Christopher W @Mike S and @Anthony S will probably be reviewing those PRs) See issue: https://github.com/regro/cf-scripts/issues/162