Where communities thrive


  • Join over 1.5M+ people
  • Join over 100K+ communities
  • Free without limits
  • Create your own community
People
Repo info
Activity
  • Sep 20 23:28
    anaconda-issue-bot commented #4284
  • Sep 20 23:28
    kenodegard opened #4284
  • Sep 20 23:26
    kenodegard commented #4183
  • Sep 20 23:26
    kenodegard commented #4183
  • Sep 20 23:23
    kenodegard synchronize #4183
  • Sep 19 05:13
    lebedov opened #4283
  • Sep 17 17:05
    jezdez commented #4282
  • Sep 17 17:05
    charudatta10 opened #4282
  • Sep 16 16:04
    anaconda-issue-bot labeled #4281
  • Sep 16 16:04
    isuruf opened #4281
  • Sep 16 15:17
    qris opened #4280
  • Sep 14 08:51
    sama2689 edited #4279
  • Sep 14 08:47
    sama2689 opened #4279
  • Sep 14 00:57
    isuruf commented #4104
  • Sep 13 20:17
    DannieSheng closed #4278
  • Sep 13 20:16
    DannieSheng opened #4278
  • Sep 13 17:05
    FaustinCarter commented #4104
  • Sep 09 12:14
    abhiramr commented #4270
  • Sep 08 19:59
    mingwandroid added as member
  • Sep 08 19:59
    jcrist added as member
Ray Donnelly
@mingwandroid
Next PR to conda-build will be #4096 for those who like round numbers.
Gabriel Reis
@gabrielcnr
@mingwandroid if I have a noarch python package, but I want to bring an extra run dependency on Windows only, I can't use selectors for # [win] if I'm building on Linux? Is there a way to achieve that?
Ray Donnelly
@mingwandroid
No, there is not. conda doesn't have separate dependency metadata per-platform for a noarch python package.
That works against the idea frankly
You could have a fake package on the other platforms, but that's kind of horrible. Still ...
There's worse
Gabriel Reis
@gabrielcnr
I see the point... thanks
Faustin Carter
@FaustinCarter
I'm having an issue where specifying a channel_alias in condarc appears to be reordering channel priority during solving of specs.
So the solver creates a list of packages from different channels using the wrong priority order, and then the build process crashes when it tries to create an environment with that spec, because it runs afoul of the strict channel priority.
This is definitely a bug
I'm wondering if anyone has run into anything like this before.
To be clear, this issue is specific to conda-build. conda create collects the right set of specs regardless of channel_alias being specified.
Is there a reason conda-build doesn't use the same solver as conda create?
Faustin Carter
@FaustinCarter
I put some more details in this bug report
Isuru Fernando
@isuruf
@mingwandroid, when cross compiling, the various variant files are read first with build_platform specific selectors even if target_platform was set in a previous variant file. Any workarounds?
Ray Donnelly
@mingwandroid
@isuruf, hmm, no I guess someone will have to spend some time fixing it though.
If you file a bug or a PR with a xfail test to conda-build then it'd help get it on the radar.
1 reply
to me, the selectors are ill-specified anyway for cross.
you really want build=='osx-64', host=='linux-64' etc instead..
2 replies
in fact that'd be my preferred approach here. deprecate the naked platform selectors with this
Isuru Fernando
@isuruf
What do you think about not recording CONDA_BUILD_SYSROOT in the package? When doing building on one machine and testing on another, this directory might not exist
On the other hand, if this is not recorded, testing on the same machine might not work
I can workaround this in the compiler package by unsetting this variable if the directory does not exist and ${CONDA_BUILD_STATE}==TEST, but feels hacky.
Isuru Fernando
@isuruf
I mean something like the following in the compiler activation script
if [ "${CONDA_BUILD_SYSROOT:-0}" != "0" ] && [ "${CONDA_BUILD_STATE:-0}" = "TEST" ] && [ ! -d "${CONDA_BUILD_SYSROOT:-0}" ]; then
  unset CONDA_BUILD_SYSROOT
fi
Ray Donnelly
@mingwandroid
Yeah, maybe.. be good to issue a warning here: "To test with used build-time macOS SDK, populate ${CONDA_BUILD_SYSROOT}"
Matthew R. Becker
@beckermr
any ideas on this one?
looks like text prefix replacement is not working in at least one case in conda-build 3.20.4
Marcelo Duarte Trevisani
@marcelotrevisani
does anyone have any news regarding tensorflow 2.3.1 on the main channels?
AnacondaRecipes/tensorflow_recipes#24
Ray Donnelly
@mingwandroid
Nothing to report @marcelotrevisani
Marcelo Duarte Trevisani
@marcelotrevisani
@mingwandroid thanks!
Ray Donnelly
@mingwandroid
Planning to release a new conda-build towards the end of the day. Any issues / PRs you have please let me know here.
Ray Donnelly
@mingwandroid
Gabriel Reis
@gabrielcnr
How can I make conda-build to spit the conda package in the new format (.conda) instead of the .tar.bz2? I can't seem to find that option... do I need to rely on the cph format conversion?
Ray Donnelly
@mingwandroid
yes
you rely on cph for this
we haven't tested direct creation of .conda packages so wouldn't recommend it. There is a way to enable it though if you want to avoid .bz2s. You cannot upload .conda packages to anaconda.org either.
4 replies
Matthew R. Becker
@beckermr
cph command line tool at 1.7.2 has a bug
will make an issue
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.