Where communities thrive


  • Join over 1.5M+ people
  • Join over 100K+ communities
  • Free without limits
  • Create your own community
People
Repo info
Activity
  • 13:00
    mbargull ready_for_review #4221
  • 13:00
    mbargull edited #4221
  • 12:41
    mbargull synchronize #4221
  • 12:38
    mbargull synchronize #4221
  • 12:35
    anaconda-issue-bot labeled #4221
  • 12:35
    mbargull opened #4221
  • Apr 14 17:54
    h-vetinari commented #4090
  • Apr 10 11:32
    h-vetinari commented #3910
  • Apr 09 21:57
    mingwandroid commented #4220
  • Apr 09 21:56
    mingwandroid commented #4220
  • Apr 09 21:49
    pseudoyim assigned #4220
  • Apr 09 21:49
    pseudoyim labeled #4220
  • Apr 09 21:49
    pseudoyim opened #4220
  • Apr 08 18:35
    xhochy commented #4219
  • Apr 08 18:33
    xhochy opened #4219
  • Apr 01 14:18
    DanVev edited #4218
  • Apr 01 14:17
    DanVev edited #4218
  • Apr 01 14:15
    DanVev opened #4218
  • Mar 30 02:34
    lambdalisue closed #2387
  • Mar 29 06:52
    mingwandroid assigned #4217
Sven Thiele
@sthiele

I need some help setting up my CI. I try to upload my conda package via github action on release. It works for linux but on windows I get an error. This is the corresponding part from my github workflow release.yml

    - name: Upload to Anaconda (Windows)
      if: matrix.os == 'windows-latest'
      env:
        ANACONDA_LOGIN: ${{ secrets.ANACONDA_LOGIN }}
      shell: pwsh
      run: anaconda -v -t "$env:ANACONDA_LOGIN" upload -l dev build/win-64/*.tar.bz2

and I get this error:

2020-12-17T09:12:45.0904898Z ##[group]Run anaconda -v -t "$env:ANACONDA_LOGIN" upload -l dev build/win-64/*.tar.bz2
2020-12-17T09:12:45.0906005Z anaconda -v -t "$env:ANACONDA_LOGIN" upload -l dev build/win-64/*.tar.bz2
2020-12-17T09:12:45.0959683Z shell: C:\Program Files\PowerShell\7\pwsh.EXE -command ". '{0}'"
2020-12-17T09:12:45.0960327Z env:
2020-12-17T09:12:45.0960809Z   CONDA_PKGS_DIR: C:\Users\runneradmin\conda_pkgs_dir
2020-12-17T09:12:45.0962425Z   ANACONDA_LOGIN: ***

2020-12-17T09:12:45.0962882Z ##[endgroup]
2020-12-17T09:12:46.7759756Z Using Anaconda API: https://api.anaconda.org
2020-12-17T09:12:46.7761230Z [DEBUG] Using token from command line args
2020-12-17T09:12:46.8596811Z [ERROR] API server not found. Please check your API url configuration.
2020-12-17T09:12:46.9350900Z ##[error]Process completed with exit code 1.

Any help would be appreciated.

Tobias Fischer
@Tobias-Fischer
Hiya - just a quick question: Is there an estimate when a new release of conda-build will be released? We're waiting for fixes to pyqt/sip on Win which will be fixed with a new release, so we can continue our efforts on RoboStack (ROS+Conda, see https://github.com/RoboStack/ros-noetic) on Windows as well which is currently on hold because of that (see also https://github.com/conda-forge/conda-forge.github.io/issues/1066).
Benjamin Bertrand
@beenje
I have a pure python package with many runtime dependencies (some as extras_require). I think it would be nice to split it in subpackages with just different run requirements. I did some tests but can't make it work with noarch: python. Is using outputs with noarch not supported?
Uwe L. Korn
@xhochy
It should work but you will probably have to put noarch: python into the build section of every output.
Benjamin Bertrand
@beenje

I tried doing something like (noarch at the same level as script):

outputs:
  - name: foo
    noarch: python
    script: build.sh

But got:

  File "/opt/conda/lib/python3.7/site-packages/conda_build/post.py", line 1038, in check_overlinking_impl
    if filetype and filetype in filetypes_for_platform[subdir.split('-')[0]]:
KeyError: 'noarch'

Or do I have to redefine build under each output?

Uwe L. Korn
@xhochy
Yes,
- name: foo
  build:
    noarch: python
Ray Donnelly
@mingwandroid
@Tobias-Fischer as soon as I can. Shouldn't be long.
Fabien Celier
@fabiencelier
Hello,
I am trying to package binaries into a conda package.
It works fine for linux and windows but on macos the binaries are corrupted and cannot be run after packaging
Any idea where that might come from ? Is there any thing I can do to prevent conda from changing my binaries ?
2 replies
Ray Donnelly
@mingwandroid
New conda-build release is in final prep stages. Are there any PRs that people feel I should include? Please look at the current master branch to see what is coming .. I didn't do news entries yet though so you'd need to compare commits between tags to see what's new. There's a lot of stuff so it'll be 3.21.0
Isuru Fernando
@isuruf
@mingwandroid, on unix, patching text files seems to be broken now
package:
  name: test
  version: 0.0.1

build:
  number: 0
  script:
    - mkdir -p $PREFIX/etc/OpenCL/vendors
    - echo $PREFIX/lib > $PREFIX/etc/OpenCL/vendors/pocl.icd

test:
  commands:
    - cat $PREFIX/etc/OpenCL/vendors/pocl.icd
Ray Donnelly
@mingwandroid
Gaah
OK
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.
OK
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?

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