conda/conda-build

Commands and tools for building conda packages

Ray Donnelly

@mingwandroid

That's what I'm looking at now, no idea why that'd have broken.

Isuru Fernando

@isuruf

Thanks. Here's a PR conda/conda-build#4176

Ray Donnelly

@mingwandroid

yeah, stupid me

ok two mins

I'll undo the pointless _ addition

I did that as I thought it unused.

sorry for the trouble

Isuru Fernando

@isuruf

Thanks @mingwandroid

Curtis Mayberry

@curtisma

Do I need to include the "entry_points" entry in the "build" section of the meta.yaml if I already have it defined as a entry_point in setup.py, called as part of my build.sh script?

Uwe L. Korn

@xhochy

Yes, you will need to do that.

Curtis Mayberry

@curtisma

What does that do since setup.py already created the entry point?

setuptools already created the command line script for the command, so what does this entry in the meta.yaml do?

Uwe L. Korn

@xhochy

It will take care that the entrypoint are correctly created when the package is installed on the system. Entrypoints are located in different locations between Windows and Unixes but noarch: python packages are typically build on Linux, thus the contained entrypoints won't work on Windows.

Curtis Mayberry

@curtisma

I see

thanks!

Benjamin Bertrand

@beenje

Trying to build a recipe with several subpackages. Using:

outputs:
  - name: taurus-core
    script: "{{ PYTHON }} -m pip install . --no-deps -vv"
    build:
      noarch: python

Gives me:

INFO conda_build.metadata:finalize_outputs_pass(748): Attempting to finalize metadata for taurus-core
Error: Failed to render jinja template in /home/conda/staged-recipes-copy/recipes/taurus/meta.yaml:
'PYTHON' is undefined

Is this expected? External script has to be used? Or is that a conda-build bug?

Recipe is here: conda-forge/staged-recipes#13756

Ray Donnelly

@mingwandroid

Recipe looks ok from initial eyeballing

Benjamin Bertrand

@beenje

Looking at the warning above:

WARNING conda_build.metadata:_get_used_vars_output_script(2312): Not detecting used variables in output script /home/conda/staged-recipes/build_artifacts/taurus_1611351737826/_h_env_placehold_..._placehold_plac/bin/python -m pip install . --no-deps -vv;
conda-build only knows how to search .sh and .bat files right now.

And reading the documentation again:

Scripts that create or move files into the build prefix can be any kind of script. Known script types need only specify the script name.

It sounds like in outputs, script has to be a file. It can't be a command. Or I'm missing something?

Jaime Rodríguez-Guerra

@jaimergp

Yep that issue sounds familiar.

Ray Donnelly

@mingwandroid

Ah yeahh

script:
  commands:
     - echo blah

Faustin Carter

@FaustinCarter

I'm running into a scenario where installing my freshly built package doesn't install all the deps

requirements:
    host:
        - python
        - pip
        - setuptools
    run:
        - knobs
        - pywin32
        - typer

knobs is a package I also built

And installing the package built with the above requirements list refuses to install knobs

Rather, it installs just fine, without any complaints, even if knobs doesn't exist!

The knobs package is just a generic package with some files in it, which builds just fine.

And is sitting in my local channel

Faustin Carter

@FaustinCarter

knobs installs just fine, btw

Faustin Carter

@FaustinCarter

Also, is there a way to suppress the inclusion of about.json in the resulting package?

We encode API keys for our channel URLs into our condarc file, and those API keys are getting stored in the package metadata which is not cool

Benjamin Bertrand

@beenje

Are you installing from a channel or using the package filename? Using a filename implies the --no-deps option.

Faustin Carter

@FaustinCarter

Using the local channel (after building both)

conda install -c local mypkg

Faustin Carter

@FaustinCarter

OK, I sorted it out

I had to do conda build purge-all

And rebuild everything from scratch

Faustin Carter

@FaustinCarter

I think there is some kind of bug

Shouldn't conda build be totally ignoring the local channel unless I'm passing --use-local to it?

Cheng H. Lee

@chenghlee

In general, it should, unless you've configured otherwise. Use conda config --show channels use_local to check.

Note that conda-build may implicitly use local.

Faustin Carter

@FaustinCarter

Yeah, use_local is false

So conda-build must be including it implicitly

It would be nice if there was a --no-local flag or something...

Christopher Barber

@analog-cbarber

Is there any way to build just one subpackage (with no dependencies on other subpackages) from a multiple-output recipe?

cmhulbert

@cmhulbert_gitlab

Hi everyone, I have a package that I have been building with conda-smithy, which needs to target linux,mac and windows. I've gotten it almost entirely worky, but for some reason when installing on windows, it tryies to pull in the # [unix] dependencies still. I think I may be creating the windows package incorreectly though. I'm using conda convert ... -p win-64 which outputs the package, but seemingly the contents of that still seem to mention that it requires the unix dependency. Any suggestiosn where I'm going wrong?

Benjamin Bertrand

@beenje

I don't think conda convert is made for this use case. It will take the same dependencies as the package given in input. If you have specific OS dependencies, you should build your package on each platform.

cmhulbert

@cmhulbert_gitlab

Thanks, I ended up doing just that. Misunderstanding with how conda convert worked. Thanks!

Where communities thrive

People

Repo info

Activity