Where communities thrive

  • Join over 1.5M+ people
  • Join over 100K+ communities
  • Free without limits
  • Create your own community
Repo info
  • 04:00
    farleylai opened #4226
  • May 06 14:13
    marcelotrevisani commented #4203
  • May 03 14:14
    sdebionne opened #4225
  • May 03 07:25
    anaconda-issue-bot labeled #4224
  • May 03 07:25
    gabm opened #4224
  • Apr 30 12:05
    artforlife commented #3371
  • Apr 29 13:18
    anaconda-issue-bot commented #4223
  • Apr 29 13:18
    samtygier-stfc opened #4223
  • Apr 29 13:07
    samtygier-stfc opened #4222
  • Apr 28 16:00
    srossross closed #1147
  • Apr 27 15:41
    duncanmmacleod commented #4197
  • Apr 24 15:20
    dnanto commented #3992
  • Apr 24 08:04
    kumaraditya303 commented #3992
  • Apr 21 13:35
    DanVev commented #4218
  • Apr 21 13:35
    DanVev closed #4218
  • Apr 19 13:00
    mbargull ready_for_review #4221
  • Apr 19 13:00
    mbargull edited #4221
  • Apr 19 12:41
    mbargull synchronize #4221
  • Apr 19 12:38
    mbargull synchronize #4221
  • Apr 19 12:35
    anaconda-issue-bot labeled #4221
Will Wray
solved by using an archive url
Downloading https://github.com/RJT1990/pyflux/archive/0.4.17.tar.gz
Will Wray
and a tag url works too, just not the download one (seems a common thing)
Downloading https://github.com/RJT1990/pyflux/releases/tag/0.4.17/pyflux-0.4.17.tar.gz
Jaime Rodríguez-Guerra
but yeah, archive urls are more commonly used, so use that one
Ray Donnelly
@00krishna It's odd that it's trying to upload, that's not the default
Ah, well, actually:
Krishna Bhogaonker
@mingwandroid Thanks for getting back to me. I have it set to automatically upload to anaconda after the build--I think that is a setting in my condarc. I have not had a chance to dig too deeply into this issue yet, but I was trying to understand what the issue was. Like it got a List instead of a string or something. But there are no other errors in the build stdout except for that strange Failed to rename work directory despite sleeping and retrying. This is some Windows file locking mis-bahaviour. which everyone told me to ignore.
I was wondering if some of my test cases might be causing an issue. I wanted to make sure libtiff was installed so I emulated some test-cases from the libtiff feedstock. I can try to remove those and see what happens.
Faustin Carter
@mingwandroid Do you know if the msys2 conda packages will sync with the msys2 project again anytime soon?
Also general question for the channel: Does anyone know if setting entry points in setup.py AND meta.yaml for a noarch package will cause any conflicts? I can't seem to find anything in the documentation.
2 replies
Ray Donnelly
@FaustinCarter I'm not sure. It's a task we need to do at some point but there's lots of those.
Faustin Carter
@mingwandroid LOL. Sounds like business as usual where I work, too.
Ray Donnelly
@FaustinCarter Oh I seem to carry this problem from job to job, thinking it's something more intrinsic!
Phil Reinhold
So, if I install conda-build in a conda environment, it appears that suddenly that environment becomes the "base environment" when activated as opposed to the "active environment". This is causing me quite the headache. Is this expected behavior?

Hey folks, I'm trying to build a conda package for OGRE. The application uses both X11 and OpenGL. I've been trying to get this to work for a long time and really would appreciate some advice. I have looked at some of the conda-forge packages out there, but unfortunately we need ogre-1.9.0 which is a little old. Also for some reason, many of the distros either don't have a package for ogre, or they still use the old 1.9.0 (see fedora). So we are stuck with 1.9.0. The Fedora rpms include 12 patches, so it's not an easy one to build, and CMake is not my friend here.

Basically I'm trying to build against packages in conda-forge. I'm using the new Conda compilers too. In terms of structuring and designing the meta.yaml, what is the correct approach to use?

I'm confused on how to build a package for X11 and OpenGL.

Do I use the CDT packages for X11 or use the conda-forge Xorg packages?

Do I try to use mesalib? What about the GLVND libraries for OpenGL and GLX, is there a way to use them instead of the legacy approach?

Thanks for all your help.
Cheng H. Lee
@smnemeth: you may get better help in the conda-forge gitter (https://gitter.im/conda-forge/conda-forge.github.io). I would say that given the choice, use conda-forge packages over CDTs and system-installed libraries.
Andrew Annex
hey all, about a year ago I posted a pr with a failing test showing that downstreams tests do not copy test source files on windows builds, but it doesn't look like whatever the issue was has been fixed yet in more recent releases. I don't have the time to work on this myself, last time I tried I ran into sections of conda-build that are not documented enough for me to quickly find the fix. I was wondering if someone could take it on? here's a link to the pr conda/conda-build#3837
Ray Donnelly
commented, thanks for the pin
How should I deal with packages that depend on each other? For example, package A has B as a running dependency, and B has A as a running dependency. I was able to build both of them, but when I try to install them it doesn't work.
Ray Donnelly
You cannot have cyclic dependencies, sorry
the shared commanlity between these two packages should be extracted to a third package that both A and B then depend upon individually.
But if that involves changing upstreams then it can be hard
Sven Thiele

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'
        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
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
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
It should work but you will probably have to put noarch: python into the build section of every output.
Benjamin Bertrand

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

  - 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
- name: foo
    noarch: python
Ray Donnelly
@Tobias-Fischer as soon as I can. Shouldn't be long.
Fabien Celier
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
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
@mingwandroid, on unix, patching text files seems to be broken now
  name: test
  version: 0.0.1

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

    - cat $PREFIX/etc/OpenCL/vendors/pocl.icd
Ray Donnelly
That's what I'm looking at now, no idea why that'd have broken.
Isuru Fernando
Thanks. Here's a PR conda/conda-build#4176
Ray Donnelly
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
Thanks @mingwandroid
Curtis Mayberry
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
Yes, you will need to do that.