conda-forge / boa-feedstock

A conda-smithy repository for boa.

About boa-feedstock

Feedstock license: BSD-3-Clause

Home: https://github.com/mamba-org/boa

Package license: BSD-3-Clause

Summary: The mamba-powered conda package builder

Current build status

All platforms:

Current release info

Name	Downloads	Version	Platforms

Installing boa

Installing boa from the conda-forge channel can be achieved by adding conda-forge to your channels with:

conda config --add channels conda-forge
conda config --set channel_priority strict

Once the conda-forge channel has been enabled, boa can be installed with conda:

conda install boa

or with mamba:

mamba install boa

It is possible to list all of the versions of boa available on your platform with conda:

conda search boa --channel conda-forge

or with mamba:

mamba search boa --channel conda-forge

Alternatively, mamba repoquery may provide more information:

# Search all versions available on your platform:
mamba repoquery search boa --channel conda-forge

# List packages depending on `boa`:
mamba repoquery whoneeds boa --channel conda-forge

# List dependencies of `boa`:
mamba repoquery depends boa --channel conda-forge

About conda-forge

conda-forge is a community-led conda channel of installable packages. In order to provide high-quality builds, the process has been automated into the conda-forge GitHub organization. The conda-forge organization contains one repository for each of the installable packages. Such a repository is known as a feedstock.

A feedstock is made up of a conda recipe (the instructions on what and how to build the package) and the necessary configurations for automatic building using freely available continuous integration services. Thanks to the awesome service provided by Azure, GitHub, CircleCI, AppVeyor, Drone, and TravisCI it is possible to build and upload installable packages to the conda-forge anaconda.org channel for Linux, Windows and OSX respectively.

To manage the continuous integration and simplify feedstock maintenance conda-smithy has been developed. Using the conda-forge.yml within this repository, it is possible to re-render all of this feedstock's supporting files (e.g. the CI configuration files) with conda smithy rerender.

For more information please check the conda-forge documentation.

Terminology

feedstock - the conda recipe (raw material), supporting scripts and CI configuration.

conda-smithy - the tool which helps orchestrate the feedstock. Its primary use is in the construction of the CI .yml files and simplify the management of many feedstocks.

conda-forge - the place where the feedstock and smithy live and work to produce the finished article (built conda distributions)

Updating boa-feedstock

If you would like to improve the boa recipe or build a new package version, please fork this repository and submit a PR. Upon submission, your changes will be run on the appropriate platforms to give the reviewer an opportunity to confirm that the changes result in a successful build. Once merged, the recipe will be re-built and uploaded automatically to the conda-forge channel, whereupon the built conda packages will be available for everybody to install and use from the conda-forge channel. Note that all branches in the conda-forge/boa-feedstock are immediately built and any created packages are uploaded, so PRs should be based on branches in forks and branches in the main repository should only be used to build distinct package versions.

In order to produce a uniquely identifiable distribution:

• If the version of a package is not being increased, please add or increase the build/number.
• If the version of a package is being increased, please remember to return the build/number back to 0.

Feedstock Maintainers

• @JohanMabille
• @isuruf
• @mbargull
• @wolfv

boa-feedstock's Issues

Backport fix to unpin conda-build again

The current meta.yaml does not have an upper bound for conda-build, but one was recently imposed by conda-forge/conda-forge-repodata-patches-feedstock#657 due to mamba-org/boa#392.

This keeps us from using the newest conda-build in CI (and thus some relevant fixes; c.f. conda-forge/conda-smithy#1844). Looking at mamba-org/boa#393, it shouldn't be a big issue to backport this PR?

CC @jaimergp @mbargull

@conda-forge-admin, please rerender

Additional comment:

update for conda-build=3.23.2

@conda-forge-admin, please rerender

Additional comment:

Opening a PR for
conda/conda-build#4750
conda/conda-index#89

Allow mamba 1.4.0 ?

cc @JohanMabille

Enable (resp. support) conda-build 3.26

Conda-build 3.26 has a couple relevant fixes, but is currently suppressed by this feedstock

boa-feedstock/recipe/meta.yaml

Line 26 in 0dfeb48

- conda-build >=3.24,<3.26

which still causes conda-build 3.25 to be pulled in, in the context of a vanilla usage of the ci setup.

CC @conda-forge/boa
FYI @conda-forge/core

Is boa 0.6.2 really incompatible with mamba 0.16.0?

Latest mamba release bumped minor version to 16, meanwhile recent boa releases constrain to below 16. Is this latter constraint warranted? Was there breaking API that needs to be adjusted for in boa?

If not, we should add a new 0.6.2 build here to adjust the bound to mamba >=0.15,<0.17.

Either way, users may be prone to getting a mamba=0.16.0 boa=0.5.0 environment, which would presumably be more likely to be incompatible than mamba=0.16.0 boa=0.6.2.

Is mamba 0.26 supported?

Additional comment:

@conda-forge-admin please rerender

Symlink boa into condabin

• [ x] I read the conda-forge documentation and could not find the solution for my problem there.

Issue:
boa that is installed in the base environment is not accessible from another conda environment.
Should boa work like mamba and conda build?

Conda build's access gets included by conda's location in condabin.

mamba gets sim linked on linux here:
https://github.com/conda-forge/mamba-feedstock/blob/master/recipe/build.sh

Environment (conda list):

```

(ros2) greg@greg5:/Downloads$ which mamba
/opt/greg/mambaforge/condabin/mamba
(ros2) greg@greg5:/Downloads$ ls -l /opt/greg/miniconda3/condabin
total 4
-rwxrwxr-x 1 greg greg 521 Jul 17 11:46 conda
lrwxrwxrwx 1 greg greg 12 Jul 17 11:46 mamba -> ../bin/mamba
(ros2) greg@greg5:~/Downloads$ ls -l /opt/greg/mambaforge/condabin
total 4
-rwxrwxr-x 1 greg greg 521 Jul 19 12:00 conda
lrwxrwxrwx 1 greg greg 12 Jul 19 12:00 mamba -> ../bin/mamba

(ros2) greg@greg5:~/Downloads$ conda list boa -n base

packages in environment at /opt/greg/mambaforge:

Name Version Build Channel

boa 0.6.2 py39hf3d152e_0 conda-forge

<br/>
Details about  <code>conda</code> and system ( <code>conda info</code> ):
<details>

Note have both miniconda and mambaforge installed.   
Saw same behaviour with only miniconda installed too.   

$ mamba info

</details>
     active environment : base
    active env location : /opt/greg/miniconda3
            shell level : 1
       user config file : /home/greg/.condarc
 populated config files : /home/greg/.condarc
          conda version : 4.10.3
    conda-build version : 3.21.4
         python version : 3.8.10.final.0
       virtual packages : __linux=5.4.0=0
                          __glibc=2.31=0
                          __unix=0=0
                          __archspec=1=x86_64
       base environment : /opt/greg/miniconda3  (writable)
      conda av data dir : /opt/greg/miniconda3/etc/conda
  conda av metadata url : None
           channel URLs : https://conda.anaconda.org/conda-forge/linux-64
                          https://conda.anaconda.org/conda-forge/noarch
                          https://conda.anaconda.org/robostack-experimental/linux-64
                          https://conda.anaconda.org/robostack-experimental/noarch
                          https://repo.anaconda.com/pkgs/main/linux-64
                          https://repo.anaconda.com/pkgs/main/noarch
                          https://repo.anaconda.com/pkgs/r/linux-64
                          https://repo.anaconda.com/pkgs/r/noarch
          package cache : /opt/greg/miniconda3/pkgs
                          /home/greg/.conda/pkgs
       envs directories : /opt/greg/miniconda3/envs
                          /home/greg/.conda/envs
               platform : linux-64
             user-agent : conda/4.10.3 requests/2.26.0 CPython/3.8.10 Linux/5.4.0-77-generic ubuntu/20.04.2 glibc/2.31
                UID:GID : 1000:1000
             netrc file : None
           offline mode : False

Allowing install with `conda-build` version `3.23`

Currently conda-build version 3.23 is excluded. Would it be possible to relax this?

boa-feedstock/recipe/meta.yaml

Line 29 in dae38b0

- conda-build >=3.20,<3.23

cc @beckermr @mbargull @wolfv

osx boa problems in ci, not sure if widespread

Solution to issue cannot be found in the documentation.

• I checked the documentation.

Issue

https://dev.azure.com/conda-forge/feedstock-builds/_build/results?buildId=556707&view=results

cc @wolfv @isuruf

Installing ['conda-forge-ci-setup=3', 'conda-forge/label/lief_dev::py-lief', 'conda-forge/label/lief_dev::liblief'] and conda-build.
+ mamba install --update-specs --quiet --yes --channel conda-forge conda-build pip boa conda-forge-ci-setup=3 conda-forge/label/lief_dev::py-lief conda-forge/label/lief_dev::liblief
Encountered problems while solving:
  - package boa-0.10.0-pyha770c72_0 requires conda-build >=3.20,<3.22, but none of the providers can be installed

##[error]Bash exited with code '1'.
Finishing: Run OSX build

Installed packages

n/a

Environment info

n/a

Update mamba pin

mamba pin is >=0.19,<0.20, but mamba is now at 0.21.

@wolfv, is there a new release on the way that supports mamba 0.21?

Allow mamba 1.3.1?

Comment:

@conda-forge-admin please rerender

Conflict with conda-libmamba-solver

boa depends on mamba <0.22 which means libmamba <0.22, but conda-libmamba-solver depends on libmamba>=0.22.

cc @jaimergp, @jezdez, @wolfv

old boa versions get pulled with latest mamba

The latest mamba pulls an old boa version that didn't have the mamba version constraints:

$ mamba install -c conda-forge mamba=0.19

                  __    __    __    __
                 /  \  /  \  /  \  /  \
                /    \/    \/    \/    \
███████████████/  /██/  /██/  /██/  /████████████████████████
              /  / \   / \   / \   / \  \____
             /  /   \_/   \_/   \_/   \    o \__,
            / _/                       \_____/  `
            |/
        ███╗   ███╗ █████╗ ███╗   ███╗██████╗  █████╗
        ████╗ ████║██╔══██╗████╗ ████║██╔══██╗██╔══██╗
        ██╔████╔██║███████║██╔████╔██║██████╔╝███████║
        ██║╚██╔╝██║██╔══██║██║╚██╔╝██║██╔══██╗██╔══██║
        ██║ ╚═╝ ██║██║  ██║██║ ╚═╝ ██║██████╔╝██║  ██║
        ╚═╝     ╚═╝╚═╝  ╚═╝╚═╝     ╚═╝╚═════╝ ╚═╝  ╚═╝

        mamba (0.15.3) supported by @QuantStack

        GitHub:  https://github.com/mamba-org/mamba
        Twitter: https://twitter.com/QuantStack

█████████████████████████████████████████████████████████████


Looking for: ['mamba=0.19']

WARNING conda.lock:touch(51): Failed to create lock, do not run conda in parallel processes [errno 13]
conda-forge/linux-64     Using cache
conda-forge/noarch       Using cache
pkgs/main/linux-64       [====================] (00m:00s) No change
pkgs/main/noarch         [====================] (00m:00s) No change
pkgs/r/linux-64          [====================] (00m:00s) No change
pkgs/r/noarch            [====================] (00m:00s) No change

Pinned packages:
  - python 3.8.*
  - su-exec 0.2
  - tini 0.18.0


Transaction

  Prefix: /opt/conda

  Updating specs:

   - mamba=0.19
   - ca-certificates
   - certifi
   - openssl


  Package       Version  Build           Channel                    Size
──────────────────────────────────────────────────────────────────────────
  Install:
──────────────────────────────────────────────────────────────────────────

  + libmambapy   0.19.0  py38h908000c_0  conda-forge/linux-64     313 KB

  Upgrade:
──────────────────────────────────────────────────────────────────────────

  - mamba        0.15.3  py38h2aa5da1_0  installed                      
  + mamba        0.19.0  py38h1abaa86_0  conda-forge/linux-64      41 KB

  Downgrade:
──────────────────────────────────────────────────────────────────────────

  - boa           0.6.2  py38h578d9bd_0  installed                      
  + boa           0.5.0  py38h578d9bd_0  conda-forge/linux-64      81 KB

  Summary:

  Install: 1 packages
  Upgrade: 1 packages
  Downgrade: 1 packages

  Total download: 435 KB

──────────────────────────────────────────────────────────────────────────

Confirm changes: [Y/n] n
Aborted.

We need to go back and patch those versions with something sensible so they don't get pulled into our CI scripts.