Where communities thrive


  • Join over 1.5M+ people
  • Join over 100K+ communities
  • Free without limits
  • Create your own community
People
Repo info
Activity
  • Jun 21 15:31
    anaconda-issue-bot labeled #4239
  • Jun 21 15:31
    jezdez commented #4239
  • Jun 21 09:25
    ChristofKaufmann commented #4239
  • Jun 21 09:19
    anaconda-issue-bot commented #4239
  • Jun 21 09:19
    ChristofKaufmann opened #4239
  • Jun 19 20:05
    jrsmith3 commented #3259
  • Jun 18 20:32
    joeyfezster commented #3259
  • Jun 16 14:20
    anaconda-issue-bot labeled #4238
  • Jun 16 14:20
    katietz opened #4238
  • Jun 15 13:55
    ltalirz commented #1553
  • Jun 14 21:58
    anaconda-issue-bot labeled #4237
  • Jun 14 21:58
    bnemanich opened #4237
  • Jun 14 21:48
    bethune-bryant closed #4236
  • Jun 14 21:48
    bethune-bryant commented #4236
  • Jun 14 21:38
    anaconda-issue-bot commented #4236
  • Jun 14 21:38
    bethune-bryant opened #4236
  • Jun 14 12:42
    kfuku52 commented #3499
  • Jun 13 01:34
    bryevdv commented #4207
  • Jun 11 15:21
    Zaharid commented #1674
  • Jun 10 13:38
    bkreider commented #3058
Matthew R. Becker
@beckermr
just warning
also extract without --dest threw an error for me
Krishna Bhogaonker
@00krishna
@mingwandroid say, I saw you released a new version of conda-build. I am noticing some error or warning that I had not seen before on my build process Failed to rename work directory despite sleeping and retrying. This is some Windows file locking mis-bahaviour. Would this be a result of the update, or would you or anyone know what is the cause of this strange error?
Krishna Bhogaonker
@00krishna
Hey folks, what is the correct way to specify the python version dependency in a conda package? I had a python >3.5in my requirements section, but apparently this could be the cause of the strange message : Failed to rename work directory despite sleeping and retrying. This is some Windows file locking mis-bahaviour., according to conda/conda-build#3006
Ray Donnelly
@mingwandroid
Argh, thought I'd fixed that. Well, it's far from fatal.
Ignore it until next release?
Ray Donnelly
@mingwandroid
But no, the docs are not talking about anything related to this problem. That's just an old problem. Are you running Windows?
Other OSes can have trouble with this though so the message should just not mention Windows. It's also to do with the filesystem you're mounted on as well as the OS.
Krishna Bhogaonker
@00krishna
@mingwandroid Oh thanks for responding. I am actually running and building on Linux, so not sure why it mentions Windows. I guess I do have some test cases that reference Windows though, but not sure if that matters. Here is my meta.yaml if that helps. But I will take your word for it that there is no problem.
{% set name = "nyuki" %}
{% set version = "0.0.3" %}

package:
  name: {{ name|lower }}
  version: {{ version }}

source:
  url: https://github.com/00krishna-tools/nyuki/archive/v{{ version }}.tar.gz
  sha256: 480867706d8f77408892559ba162f2a7c716b5c4ecbf32135f246e86cac4fbe1

build:
  noarch: python
  number: 0
  entry_points:
    - nyuki = nyuki.nyuki:nyuki

requirements:
  host:
    - python >3.5
    - pip
    - numpy >=1.18.5
    - pandas
    - rasterio
    - click >=7
    - tqdm
    - geopandas
    - pillow
    - libwebp
    - libtiff >4.0
  run:
    - python >3.5
    - numpy >=1.18.5
    - pandas
    - rasterio
    - click >=7
    - tqdm
    - geopandas
    - pillow
    - libwebp
    - libtiff >4.0

test:
  imports:
    - nyuki
  commands:
    - test -f ${PREFIX}/lib/libtiff.a  # [not win]
    - test -f ${PREFIX}/lib/libtiffxx.a  # [not win]
    - test -f ${PREFIX}/lib/libtiff{{ SHLIB_EXT }}  # [not win]
    - test -f ${PREFIX}/lib/libtiffxx{{ SHLIB_EXT }}  # [not win]
    - if not exist %PREFIX%\\Library\\bin\\tiff.dll exit 1  # [win]
    - if not exist %PREFIX%\\Library\\bin\\tiffxx.dll exit 1  # [win]
    - if not exist %PREFIX%\\Library\\bin\\libtiff.dll exit 1  # [win]
    - if not exist %PREFIX%\\Library\\bin\\libtiffxx.dll exit 1  # [win]

about:
  home: https://github.com/00krishna-tools/nyuki
  license: MIT
  license_family: MIT
  license_file: LICENSE.txt
  summary: "A geospatial library for humans. "

  description: "Nyuki: a geospatial library for humans"
  doc_url: https://nyuki-a-geospatial-toolkit-for-humans.readthedocs.io/en/latest/
  dev_url: https://github.com/00krishna-tools/nyuki

extra:
  recipe-maintainers:
    - 00krishna
I was wondering about this error with the Windows thing because I am getting another error at the end of the build process, and I thought they might be related. I am getting this error about TypeError: expected str, bytes or os.PathLike object, not list then the package tries to upload to Anaconda.org. I have not figured out the cause of that yet. Here is the traceback if you are interested.
Uploading nyuki-0.0.3-py_0.tar.bz2 to anaconda.org
Traceback (most recent call last):
  File "/media/krishnab/lakshmi/anaconda3/bin/conda-build", line 11, in <module>
    sys.exit(main())
  File "/media/krishnab/lakshmi/anaconda3/lib/python3.7/site-packages/conda_build/cli/main_build.py", line 474, in main
    execute(sys.argv[1:])
  File "/media/krishnab/lakshmi/anaconda3/lib/python3.7/site-packages/conda_build/cli/main_build.py", line 465, in execute
    verify=args.verify, variants=args.variants)
  File "/media/krishnab/lakshmi/anaconda3/lib/python3.7/site-packages/conda_build/api.py", line 210, in build
    notest=notest, variants=variants)
  File "/media/krishnab/lakshmi/anaconda3/lib/python3.7/site-packages/conda_build/build.py", line 3155, in build_tree
    handle_anaconda_upload(tarballs, config=config)
  File "/media/krishnab/lakshmi/anaconda3/lib/python3.7/site-packages/conda_build/build.py", line 3236, in handle_anaconda_upload
    subprocess.call(cmd + [package])
  File "/media/krishnab/lakshmi/anaconda3/lib/python3.7/subprocess.py", line 339, in call
    with Popen(*popenargs, **kwargs) as p:
  File "/media/krishnab/lakshmi/anaconda3/lib/python3.7/subprocess.py", line 800, in __init__
    restore_signals, start_new_session)
  File "/media/krishnab/lakshmi/anaconda3/lib/python3.7/subprocess.py", line 1465, in _execute_child
    executable = os.fsencode(executable)
  File "/media/krishnab/lakshmi/anaconda3/lib/python3.7/os.py", line 812, in fsencode
    filename = fspath(filename)  # Does type-checking of `filename`.
TypeError: expected str, bytes or os.PathLike object, not list
I was not sure if this error on upload was related to the previous error on Failed to rename work directory despite sleeping and retrying.
Ray Donnelly
@mingwandroid
Looking now..
Krishna Bhogaonker
@00krishna
@mingwandroid Oh thanks so much. Yeah, if you can figure out where this is coming from that would totally help. The odd thing is that the error seems to happen after the build process completes, so it is tricky to figure out where something went wrong. But if you have any luck, please let me know. And thanks again.
Will Wray
@willwray
Hi builders; I'm attempting to write a conda-forge recipe for pyflux
in running conda-build locally, to check the recipe, it fails persistently with:
An HTTP error occurred when trying to retrieve this URL.
HTTP errors are often intermittent, and a simple retry will get you on your way.
Could not download https://github.com/RJT1990/pyflux/releases/download/0.4.17/pyflux-0.4.17.tar.gz
The url is usable directly with curl, e.g.:
curl -sL https://github.com/RJT1990/pyflux/releases/download/0.4.17/pyflux-0.4.17.tar.gz | openssl sha256
Will Wray
@willwray
solved by using an archive url
Downloading https://github.com/RJT1990/pyflux/archive/0.4.17.tar.gz
Will Wray
@willwray
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
@jaimergp
but yeah, archive urls are more commonly used, so use that one
Ray Donnelly
@mingwandroid
@00krishna It's odd that it's trying to upload, that's not the default
Ah, well, actually:
--no-anaconda-upload
Krishna Bhogaonker
@00krishna
@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
@FaustinCarter
@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
@mingwandroid
@FaustinCarter I'm not sure. It's a task we need to do at some point but there's lots of those.
Faustin Carter
@FaustinCarter
@mingwandroid LOL. Sounds like business as usual where I work, too.
Ray Donnelly
@mingwandroid
@FaustinCarter Oh I seem to carry this problem from job to job, thinking it's something more intrinsic!
Phil Reinhold
@PhilReinhold
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?
smnemeth
@smnemeth

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.
Scott
Cheng H. Lee
@chenghlee
@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
@AndrewAnnex
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
@mingwandroid
commented, thanks for the pin
ping
mike
@mike91500553_twitter
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
@mingwandroid
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
@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.