Stuck on an issue?
Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
build and process `.conda` artifacts
See original GitHub issueThis issue is to track to-do items for building and handling .conda artifacts.
to dos:
- adjust repodata patching (https://github.com/conda-forge/conda-forge-repodata-patches-feedstock/issues/215)
- adjust instances where
.tar.bz2is assumed to be at the tail end of packages- artifact validation (https://github.com/conda-forge/artifact-validation/pull/790)
- webservices (https://github.com/conda-forge/conda-forge-webservices/pull/487)
- ci setup package (https://github.com/conda-forge/conda-forge-ci-setup-feedstock/pull/182)
- repodata tools (https://github.com/conda-forge/repodata-tools/pull/8)
- admin requests (https://github.com/conda-forge/admin-requests/pull/384)
- libcfgraph (https://github.com/regro/libcflib/pull/75)
- conda-smithy (https://github.com/conda-forge/conda-smithy/pull/1693)
- wait for support from
anaconda.org( https://github.com/conda/infra/issues/637#issuecomment-1307776730 ) - figure out story on transmutation of old artifacts (not going to)
- test uploads on the cf-autotick-test-feedstock and copy of ci setup package from PR above (https://github.com/conda-forge/cf-autotick-bot-test-package-feedstock/pull/439)
- test we can mark .conda artifacts as broken (https://github.com/conda-forge/admin-requests/pull/511)
- test we can mark .conda artifacts as unbroken (https://github.com/conda-forge/admin-requests/pull/512)
- test we can make the repodata patches for them properly (https://github.com/conda-forge/conda-forge-repodata-patches-feedstock/pull/356)
- test for no duplicate uploads for packages of the same name but different extensions (https://github.com/conda-forge/cf-autotick-bot-test-package-feedstock/pull/441, https://github.com/conda-forge/cf-autotick-bot-test-package-feedstock/pull/442)
- merge all PRs
- make an announcement (https://github.com/conda-forge/conda-forge.github.io/pull/1852)
- start admin migration to switch over feedstocks (do this slowly to look for breakages, https://github.com/conda-forge/admin-migrations/pull/82)
- set default as .conda in ci-setup package (https://github.com/conda-forge/conda-forge-ci-setup-feedstock/pull/212)
Issue Analytics
- State:
- Created 2 years ago
- Reactions:5
- Comments:25 (24 by maintainers)
Top Results From Across the Web
Conda-build recipes
Conda -build process ... Conda-build performs the following steps: ... Tests the new conda package if the recipe includes tests: ... The conda-recipes...
Read more >How to build Conda packages?
The conda build process · Reads the metadata. · Downloads the source into a cache. · Extracts the source into the source directory....
Read more >Conda Repositories - JFrog Documentation
Artifactory natively supports Conda repositories for Python, R, Ruby, Lua, Scala, Java, JavaScript, C/ C++, FORTRAN and additional programming ...
Read more >Anaconda Content Trust: Conda Signature Verification
When conda verifies artifact signatures, it assures users that packages they are about to install are exactly as they were when produced on ......
Read more >Knowledge Base — conda-forge 2022.12.21 documentation
If you are using cmake, be sure to make it a build requirement in the build section. You may also need to include...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
If you run
zstd -b1 -e19 somefileit will tell you how long each level took.Related to this have filed an issue to create a CEP spelling out the
.condaspec more fully ( https://github.com/conda-incubator/ceps/issues/42 )