Where communities thrive


  • Join over 1.5M+ people
  • Join over 100K+ communities
  • Free without limits
  • Create your own community
People
Repo info
Activity
  • Oct 22 21:02
    jakirkham commented #903
  • Oct 22 20:21
    saulshanabrook opened #905
  • Oct 22 18:25
    scopatz commented #904
  • Oct 22 18:25

    scopatz on master

    Update license date to include … Merge pull request #904 from ja… (compare)

  • Oct 22 18:25
    scopatz closed #904
  • Oct 22 18:22
    jakirkham commented #904
  • Oct 22 18:21
    jakirkham edited #904
  • Oct 22 18:21
    jakirkham opened #904
  • Oct 22 08:44
    davidbrochart opened #903
  • Oct 19 21:25
    ocefpaf commented #902
  • Oct 19 21:25
    ocefpaf commented #902
  • Oct 19 21:25
    ocefpaf commented #902
  • Oct 19 16:06
    hmaarrfk commented #902
  • Oct 19 16:05
    hmaarrfk edited #902
  • Oct 19 16:05
    hmaarrfk opened #902
  • Oct 18 14:29
    jakirkham commented #900
  • Oct 18 14:18
    isuruf commented #900
  • Oct 18 13:47
    CJ-Wright commented #867
  • Oct 18 13:00
    msarahan commented #900
  • Oct 18 08:41
    mingwandroid commented #900
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:
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
(you need to rerender to pick up the changes)
Isuru Fernando
@isuruf
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:
Dillon Roach
@dillonroach
Hi all - if I have a package and conda install package it will pop out a list of all the packages it will pull to install in my current env/arch - is there a way to test what it would pull for the same package on a different arch? Just trying to avoid having to set up a bunch of VMs to see how a package installs on different architectures
Jonathan J. Helmus
@jjhelmus
CONDA_SUBDIR=win-64 conda create -n test package --dry-run will show you what will be installed on win-64. You can specify other platforms as well.
Leonardo Rosenbach
@lincrosenbach
Hi all. I have added a recipe get-docker-secret yesterday and it was merge. Looking today at its feedstock, there are no build for it. I have created the following issue: conda-forge/get-docker-secret-feedstock#1
Can someone help me to understand what happened?
Dillon Roach
@dillonroach
thanks @jjhelmus - much appreciated
Ray Donnelly
@mingwandroid

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

Raise an issue? @isuruf is there one?

PRs are also good ways of opening the discussion. My work is unfinished and you have other things to add. We also have this new Preload thing that Isuru discovered, I'd like to have a Preload for each SDK/CDT-distro if that works. This could speed up builds a lot I think if cmake caches things right and people stick to the standard cmake bundled modules.
If you want to propose your own way go ahead, if you want to discuss then https://github.com/conda-forge/cmake-feedstock/issues would probably be the place for that.
Ray Donnelly
@mingwandroid
We could even provide mutliple methods and pick the "best" on a per-recipe basis.
there's Preload, specifically named bash array env vars to pass to cmake, toolchain files and changes to cmake itself to consider as options.
deepali-c
@deepali-c
I am trying to write conda recipe for https://github.com/pytorch/fairseq. I see the following error:
RuntimeError: Setuptools downloading is disabled in conda build. Be sure to add all dependencies in the meta.yaml url=https://pypi.org/simple/pycparser/
Although I have pycparser added as dependency in the host section. I have also tried putting it in build section but it still fails.