Hi Guys, I’ve been looking into the conda feedstock for the package which is not publishing the package, the issues are: 1. daft version 2.33 introduces the use of Simd::load_or_default which is a nightly feature found since rust 1.79, rust 1.79 nightly is not found in conda, the only nightly rust compiler found in conda since 1.79 is 1.81. 2. daft version 0.2.33 locks the time crate to 0.3.29, which is incompatible with rust 1.81. what do you suggest?

I think we might need @Sammy Sidhu’s input here, but my 2c: • `the only nightly rust compiler found in conda since 1.79 is 1.81`: I think we can probably bump our version to 1.81? • We can also bump our

time

crate

In our next release we will be upgrading to a newer version of nightly (compiled on August 1), which includes time being bumped to 0.3.36. Would this fix your problem?

This will solve this issue, but I think that if there is a conda package publishing, there needs to be a conda build test, because for version 0.2.33, there is currently no conda build for rust that is compatible

I’m not familiar at all with conda unfortunately, but seems like your build did publish the right files to conda-forge? https://anaconda.org/conda-forge/rust/files

as far as I understand conda builds, the channel sources should do the trick, the issue is that when I specify version 1.79 of the rust compiler it cannot use the correct rust compiler build due to strict channel priority, that my guess is happening due to the conda-build command. I am wondering wether there is someone who has experience building a conda package from the rust nightly, which is from the rust dev conda channel

Hmm, that’s perhaps a good question for the folks on https://github.com/conda-forge/rust-feedstock?

I will take a look later next week. Thanks 🙂

Thanks for taking a stab at this!

Sure 🙂

Not familiar with that unfortunately 😧 let’s see what they say!

I haven't seen the linker segfault before! That's a new one