conda-forge/conda-forge.github.io

Documentation for conda-forge

Ray Donnelly

@mingwandroid

and I don't intend to back that out at present, it can be slow, so I'm making sure to call it once per sha1 of binary file only (will cache things when done and settled too, somewhere). LIEF's doing good IMHO as a project.

need to find out more about your plans here though

Matthew R. Becker

@beckermr

Bump on this issue: https://github.com/conda/conda-build/issues/3735#issuecomment-532421510

Idk how to fix it and it is really causing problems for me

Ray Donnelly

@mingwandroid

@beckermr our team is completely preocuppied at present, please, if you can dig into it yourself

Matthew R. Becker

@beckermr

sounds good. I’m preoccupied too of course!

Uwe L. Korn

@xhochy

Lately I've seen a lot of PRs where noarch: python was removed because conda-build complained about an exe on Windows that looked like an entrypoint, e.g. here conda-forge/staged-recipes#9588 (build logs don't resolve correctly anymore for me).

Anyone has an idea if this is an undeclared entrypoint or what is happening here?

Chris Burr

@chrisburr

It is an undeclared entry_point

Uwe L. Korn

@xhochy

Thanks!

Duncan Macleod

@duncanmmacleod

@duncanmmacleod - you need to run VsDevCmd.bat -arch=amd64 to set up the correct environment variables for conda build to see the msvc compiler

thanks @dhirschfeld, I tried this and got some new path entries, but still no cl.exe, if I run VsDevCmd.bat -test that fails because it too cannot find cl.exe. I presume I've done something wrong in installing VS in the first place, will investigate

Filipe

@ocefpaf

Folks, what would be the best pattern/practice to make proj.4 (old name) 'conflicts with' proj (new name)?

Chris Burr

@chrisburr

@ocefpaf see here

Duncan Macleod

@duncanmmacleod

@dhirschfeld, I installed an extra set of VS2019 components, and now have VsDevCmd.bat working fine, and conda-build can now see the compiler! thanks for your help!

Filipe

@ocefpaf

Thanks @chrisburr!

Wolf Vollprecht

@wolfv

hey all, i am trying to make ROS's distribution model fit in conda-forge. this is what we came up with so far:

conda-forge/staged-recipes#8994

there is a ROS mutex pacakge that carries the distribution string (e.g. melodic)

and there is a ros-conda-base package that run_constrains some base dependencies (they are specified in this "REP" : https://www.ros.org/reps/rep-0003.html )

maybe someone cares to review this? getting this one merged will be a huge step towards opening the floodgates for the rest of ROS :)

the catkin package is the ROS meta build and workspace tool in the ros ecosystem and therefore basically the most important component

Jaime Rodríguez-Guerra

@jaimergp

Hey! I am seeing some weird differences between Appveyor and Azure for Windows. My package contains some py files with hardcoded prefix paths that should get rewritten by conda-build. In Azure, these are caught, but for some reason they are ignored in Appveyor. The only difference is that Azure uses C:\Miniconda\conda-bld and Appveyor goes for C:\bld... I can reproduce the Appveyor behavior in my windows box, which also uses C:\bld. Is that the reason? The PR is here conda-forge/staged-recipes#9163

Jaime Rodríguez-Guerra

@jaimergp

Well, that was not the reason, but ripgrep! If rg is present, the file is not found.

and the hardcoded prefix gets ignored

Matthew R. Becker

@beckermr

Can someone on core pull conda versions 4.7.11 and 4.7.12? Both of those versions break staged-recipes.

Sylvain Corlay

@SylvainCorlay

conda versions 4.7.11 and 4.7.12 [...] break staged-recipes.

:unamused:

Matthew R. Becker

@beckermr

software is hard :(

Sylvain Corlay

@SylvainCorlay

Trying to resolve some issues with a windows build locally.

And getting some weird conflicts:

Matthew R. Becker

@beckermr

check your version of conda (4.7.10 should be fine)

Sylvain Corlay

@SylvainCorlay

Package vc conflicts for:

vc[version='>=14.1,<15.0a0']
llvmdev==5.0.0 -> vc==14

same conflict with 4.7.10

Matthew R. Becker

@beckermr

k - then it must be the packages and not conda

Sylvain Corlay

@SylvainCorlay

weid because llvmdev 5.0 does not require vc==14

only a skip for [win and vc<14]

Yaroslav Halchenko

@yarikoptic

could someone point me to some doc/example for establishing a channel/label to ship release candidates? There is an outstanding conda-forge/conda-forge.github.io#861 and so far I found no docs of any kind to accomplish the mission
in some elderly attempt I found (https://github.com/conda-forge/sunpy-feedstock/pull/2/files) it boiled to modifying --channel=main to be =pre in all the scripts.

Bradley Lowekamp

@blowekamp

@mingwandroid Where would be best ti discuss the CMake feedstock changes?

Isuru Fernando

@isuruf

@chrisburr, what was the reason for hardcoding MACOS_DEPLOYMENT_TARGET to 10.9 in cling? It prevents CONDA_BUILD_SYSROOT from being used

Chris Burr

@chrisburr

I don't remember but I think it can be dropped

Isuru Fernando

@isuruf

@saraedum, want to send a PR?

Matthew R. Becker

@beckermr

rebump on this in case it got lost in the shuffle:

Can someone on core pull conda versions 4.7.11 and 4.7.12? Both of those versions break staged-recipes.

Duncan Macleod

@duncanmmacleod

:arrow_up: :arrow_up: :arrow_up:

Duncan Macleod

@duncanmmacleod

can someone help me with an appveyor failure on conda-forge/lscsoft-glue-feedstock#12, I am seeing

ModuleNotFoundError: No module named 'libarchive'

from all of the appveyor builds (we still need those, right?), thanks

Chris Burr

@chrisburr

If Azure works you can configure it to upload from there

(you need to rerender to pick up the changes)

Isuru Fernando

@isuruf

@duncanmmacleod, see conda-forge/conda-build-feedstock#112

Duncan Macleod

@duncanmmacleod

thanks both. @isuruf, any reason I shouldn't switch to azure for everything?

Isuru Fernando

@isuruf

@duncanmmacleod, no reason

Duncan Macleod

@duncanmmacleod

:+1:

Where communities thrive

People

Repo info

Activity