|
| 1 | +--- |
| 2 | +tags: [meeting-notes] |
| 3 | +--- |
| 4 | +# conda-forge core meeting 2023-05-03 |
| 5 | + |
| 6 | +Add new agenda items under the `Your __new__() agenda items` heading |
| 7 | + |
| 8 | +- [Zoom link](https://zoom.us/j/9138593505?pwd=SWh3dE1IK05LV01Qa0FJZ1ZpMzJLZz09) |
| 9 | +- [What time is the meeting in my time zone](https://dateful.com/convert/utc?t=5pm) |
| 10 | +- [Last week's meeting](https://hackmd.io/#REPLACE_ME#) |
| 11 | + |
| 12 | +## Attendees |
| 13 | + |
| 14 | +| Name | Initials | GitHub ID | Affiliation | |
| 15 | +| ----------------------- | -------- | --------------- | --------------------------- | |
| 16 | +| Dave Clements | DPC | tnabtaf | Anaconda | |
| 17 | +| | | | | |
| 18 | +| Filipe Fernandes | FF | ocefpaf | conda-forge | |
| 19 | +| Cheng H. Lee | CHL | chenghlee | conda-forge/Anaconda | |
| 20 | +| Marius van Niekerk | MvN | mariusvniekerk | VoltronData/cf | |
| 21 | +| Ryan May | RMM | dopplershift | Unidata/cf | |
| 22 | +| Jannis Leidel | JL | jezdez | Anaconda/cf | |
| 23 | +| John Kirkham | JK | jakirkham | NVIDIA/cf | |
| 24 | +| Marcel Bargull | MB | mbargull | Bioconda/cf | |
| 25 | +| Avalon | A | uwuvalon | Anaconda | |
| 26 | +| Jaime Rodríguez-Guerra | JRG | jaimergp | Quansight/cf | |
| 27 | +| | | | | |
| 28 | +| | | | | |
| 29 | +| | | | | |
| 30 | +| | | | | |
| 31 | +| | | | | |
| 32 | +| | | | | |
| 33 | + |
| 34 | +18 people total |
| 35 | + |
| 36 | + |
| 37 | +### Introductions |
| 38 | + |
| 39 | +- [x] Andrew Vallette on the packaging team at Anaconda. |
| 40 | + |
| 41 | +### Standing items |
| 42 | + |
| 43 | +- [ ] |
| 44 | + |
| 45 | +### From previous meeting(s) |
| 46 | + |
| 47 | +- [x] (WV) rattler-build - new conda package build tool: https://github.com/prefix-dev/rattler-build |
| 48 | + - builds conda packages from recipe format that looks a lot like BOA |
| 49 | + - Writes metadata in rattler format |
| 50 | + - Did a live demo. |
| 51 | + - Aiming to give better diagnostics |
| 52 | + - MRB: BOA Spec? |
| 53 | + - We need to figure out what to do. |
| 54 | + - Need a defined spec that everyone can write to |
| 55 | + - JL: what do we need to do create a spec? |
| 56 | + - Selectors, |
| 57 | + - MVN: version number in spec. People were in violent agreement. |
| 58 | + - JL: We need a spec |
| 59 | + - WV: we have a JSON schema. |
| 60 | + - JK: argues for a new YAML format. Would be interested in being involved in Spec writing group |
| 61 | + - Some recipes will/may be left behind. |
| 62 | + - ACTION: Discusss this on Conda call next week. |
| 63 | +- [x] (JK) New CTK packages / CUDA 12 |
| 64 | + - Opening CUDA 12 migrator |
| 65 | + - Package layout changes: |
| 66 | + - https://github.com/conda-forge/conda-forge-pinning-feedstock/pull/4400 |
| 67 | + - Document? |
| 68 | + - Message? |
| 69 | + - Incremental rollout? |
| 70 | + - Marius suggested bot message customization |
| 71 | + - May need to go in bot code |
| 72 | + - Could add change to bot code to |
| 73 | + - (IF) Has question about layout |
| 74 | + - (JK) Using `cuda` would be ok |
| 75 | + - (IF) Changes a lot of things for CMake |
| 76 | + - (JK) Discussion to have with Robert Maynard |
| 77 | + - (JK) |
| 78 | + - (Longer-term) CUDA 11 backport? (punted to later meeting) |
| 79 | + - New style packages on older CUDA versions |
| 80 | + - What version to start with (`nvidia` channel has `11.4`)? |
| 81 | + - `cudatoolkit` becomes metapackage? |
| 82 | + - Potential to drop some CUDA specific things |
| 83 | + - Docker images |
| 84 | + - conda-forge-ci-setup simplification |
| 85 | +- [x] (JK) Windows MinGW & UCRT |
| 86 | + - https://github.com/conda-forge/r-base-feedstock/issues/248 |
| 87 | + - https://github.com/conda-forge/conda-forge.github.io/issues/1654 |
| 88 | + - https://github.com/conda-forge/conda-forge.github.io/issues/1044 |
| 89 | + - (AV): Anaconda is looking into ways to fix this issue |
| 90 | + - Do we binary repack MSYS2 packages? Or rebuild? |
| 91 | + - How can we automate UCRT-based MSYS2 Windows? |
| 92 | + - Could even automate recipe generation |
| 93 | + - https://github.com/conda-forge/msys2-recipes |
| 94 | + - (MRB) CDT approach could be reused here |
| 95 | + - https://github.com/conda-forge/cdt-builds |
| 96 | + - (IF) What do we want packaged |
| 97 | + - May need customization; e.g., `run_exports` |
| 98 | + - |
| 99 | + - (AV): Will share work as it progresses |
| 100 | + - (MB): Old MinGW use subfolder? |
| 101 | + - Do we want to change this for UCRT? Or keep the same? |
| 102 | + - (IF) Depends on what we package |
| 103 | +- [x] (JK) GLIBC 2.28 |
| 104 | + - https://github.com/conda-forge/conda-forge.github.io/issues/1941 |
| 105 | + - (MRB) Need review |
| 106 | + - https://github.com/conda-forge/conda-forge-repodata-patches-feedstock/pull/441 |
| 107 | + - https://github.com/conda-forge/linux-sysroot-feedstock/pull/47 |
| 108 | + - (MRB) Downloaded RPM need review |
| 109 | + - Directory level varies / need to confirm that is the right level |
| 110 | + - (MB) Do we need language packs? |
| 111 | + - (MRB) Have English in one |
| 112 | + - (MRB) Have one with many languages |
| 113 | + - (IF) |
| 114 | + - |
| 115 | +- [x] (JK) Windows ARM |
| 116 | + - (SD) Hi :) Happy to answer questions |
| 117 | + - https://github.com/conda-forge/conda-forge.github.io/issues/1940 |
| 118 | + - (IF) https://github.com/conda-forge/vc-feedstock/pull/55 |
| 119 | + - (IF) Question for Steve: What do you plan on building in the first year? |
| 120 | + - (IF) Conda / Mamba / Boa needed to build, Installer? |
| 121 | + - (SD) Installer is ambitious (would be great! not required). Want attempts/CI issues visible |
| 122 | + - (SD) Challenges getting more hardware atm. So just be able to build |
| 123 | + - (IF) Python would be a goal? Maybe NumPy & SciPy? |
| 124 | + - (JK) What would be helpful for finance conversation? |
| 125 | + - (SD) Ask for less? ;) Though nothing has really been asked yet. |
| 126 | + - (SD) Finn can help :) |
| 127 | + - (IF) Can build `zlib`! :tada: |
| 128 | + - Local build |
| 129 | + - (MvN) Maybe macOS ARM list could be a starting point |
| 130 | + - (SD) Rust toolchain should work (testing with cryptography) |
| 131 | + - (IF) Does Clang cross-compilation work? |
| 132 | + - (SD) Using Cygwin (not Clang) atm |
| 133 | +- [ ] (HV) Boost Harmonization |
| 134 | + - Now has PR: https://github.com/conda-forge/boost-feedstock/pull/164 |
| 135 | + - Discussion yielded bikeshed à la: `libboost`, `libboost-headers`, `libboost-python` |
| 136 | +- [ ] (MB) R 4.3 migration |
| 137 | + - https://github.com/conda-forge/conda-forge-pinning-feedstock/pull/4363 |
| 138 | + - Any objections on kicking it off? |
| 139 | + - Windows TeX build issues for 4.1 might need to be resolved due to other non-R migrations? |
| 140 | + |
| 141 | +### Active votes |
| 142 | + |
| 143 | +- [ ] |
| 144 | + |
| 145 | +### Your __new__() agenda items |
| 146 | + |
| 147 | +- [X] (DPC) Package building tutorial at PyCon US 2023 was a success. |
| 148 | + - We had ~25 participants |
| 149 | + - Tutorial will be published online after some cleanup. |
| 150 | +- [X] (JRG) SDG for opt-in CI accepted (related to https://github.com/conda-forge/conda-forge.github.io/issues/1875 and GPU server) |
| 151 | +- [X] (WV) SDG for pubgrub on rattler accepted too |
| 152 | +- [ ] |
| 153 | + |
| 154 | +### Pushed to next meeting |
| 155 | + |
| 156 | +- [ ] |
| 157 | + |
| 158 | +### CFEPs |
| 159 | + |
| 160 | +- [ ] |
0 commit comments