conda/conda-build

Commands and tools for building conda packages

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!

Antoine Prouvost

@AntoinePrv

Hello,
How can I skip a whole output for windows ? Do I have to add # [not win] to all the lines?

3 replies

Or maybe soemthing with Jinja?

{% if false %}  # [win]
{% if true %}  # [not win]

Marcelo Duarte Trevisani

@marcelotrevisani

Hello,
How can I skip a whole output for windows ? Do I have to add # [not win] to all the lines?

inside of the output you can add a :

outputs:
  ...
  build:
    skip: True  # [win]

1 reply

George Breyiannis

@brey

Hi all. I have an issue with my package. The name is "pyPoseidon" which creates an issue with

test:
    imports:
       - pyPoseidon

returning
ModuleNotFoundError: No module named 'pyPoseidon'
Anyway to overcome this or do I need to change the package's name to all lowercase?

Where communities thrive

People

Repo info

Activity