#!/usr/bin/env python in those cases. Adding a configuration option to override this rewrite would be reasonable.
I see below error while building a recipe:
Fixing permissions
execute(sys.argv[1:])
File "<mypath>/lib/python2.7/site-packages/conda_build/cli/main_build.py", line 430, in execute
verify=args.verify, variants=args.variants)
File "<mypath>/lib/python2.7/site-packages/conda_build/api.py", line 201, in build
notest=notest, need_source_download=need_source_download, variants=variants)
File "<mypath>/lib/python2.7/site-packages/conda_build/build.py", line 2275, in build_tree
notest=notest,
File "<mypath>/lib/python2.7/site-packages/conda_build/build.py", line 1654, in build
newly_built_packages = bundlers[output_d.get('type', 'conda')](output_d, m, env, stats)
File "<mypath>/lib/python2.7/site-packages/conda_build/build.py", line 972, in bundle_conda
output['checksums'] = create_info_files(metadata, files, prefix=metadata.config.host_prefix)
File "<mypath>/lib/python2.7/site-packages/conda_build/build.py", line 665, in create_info_files
copy_recipe(m)
File "<mypath>/lib/python2.7/site-packages/conda_build/build.py", line 301, in copy_recipe
_copy_output_recipe(m, recipe_dir)
File "<mypath>/lib/python2.7/site-packages/conda_build/build.py", line 270, in _copy_output_recipe
_copy_top_level_recipe(src_dir, m.config, dest_dir, 'parent')
File "<mypath>/lib/python2.7/site-packages/conda_build/build.py", line 264, in _copy_top_level_recipe
locking=config.locking, clobber=True)
File "<mypath>/lib/python2.7/site-packages/conda_build/utils.py", line 502, in copy_into
_copy_with_shell_fallback(src, dst_fn)
File "<mypath>/lib/python2.7/site-packages/conda_build/utils.py", line 435, in _copy_with_shell_fallback
raise OSError("Failed to copy {} to {}. Error was: {}".format(src, dst, e))
OSError: Failed to copy <path>/meta.yaml to <envpath>/info/recipe/parent/meta.yaml.
Error was: Command 'cp -a <path>/meta.yaml <envpath>/info/recipe/parent/meta.yaml' returned non-zero exit status 1
Any hints on how to get to the cause of this? I have just shortened the paths here.
sbin is mainly for administrator control, I was just wondering if ‘don’t use sbin’ is a conda policy, or just nobody has tried it until now
My understanding is that the sbin folder on Linux systems is for segregating binaries meant to be run by privileged users. (generally speaking, sysadmins)
But conda is a generic package manager and doesn't make such distinctions, so the need for segregating binaries doesn't make much sense here.
