Set default channel-priority to "strict" due to issues with beta...

Set default channel-priority to "strict" due to issues with beta builds using mixed stable/beta sources

The channel priority is set on the default CONDARC setup. Anything created from bob.devtools, by default will have that ON.

This allows local reproduction of CI builds.

@amohammadi: this does not work.

I'm trying to find the first project that shows the issue (following nightlies order)

then i can try to debug here

I had a suspicion this was a bag of hurt (https://www.engadget.com/2008/10/14/steve-jobs-calls-blu-ray-a-bag-of-hurt/)...

closed

It seems bob.bio.base is the first one https://gitlab.idiap.ch/bob/bob.bio.base/-/jobs/183199

Why do we have c3i_test in our channel list?

           channel URLs : https://conda.anaconda.org/c3i_test/linux-64
                          https://conda.anaconda.org/c3i_test/noarch
                          http://www.idiap.ch/defaults/linux-64
                          http://www.idiap.ch/defaults/noarch

Why doesn't it work? Maybe we have conflicts here.

bob.learn.em just failed https://gitlab.idiap.ch/bob/bob.learn.em/-/jobs/183189

I'm not sure why these ci3_test channels pop up.

I'm not sure why these ci3_test channels pop up.

It's in the /root/.condarc file that comes with the docker image.

@amohammadi: shall we act on this one, or keep it closed?

I thought this is already merged.

reopened

just sorted the list and the rest of changes are from black.

I have checked all the packages needed to build bob.devtools. They either exist in our channel or in the defaults channel. I don't see why enbaling strict channel priority should lead to conflicts.

conda search    alabaster
conda search    appdirs
conda search    asn1crypto
conda search    beautifulsoup4
conda search    black
conda search    bleach
conda search    cffi
conda search    chardet
conda search    click
conda search    cmarkgfm
conda search    conda
conda search    conda-build
conda search    conda-package-handling
conda search    cryptography
conda search    docformatter
conda search    docutils
conda search    future
conda search    icu
conda search    idna
conda search    libarchive
conda search    libedit
conda search    libffi
conda search    libgcc-ng
conda search    liblief
conda search    libstdcxx-ng
conda search    libxml2
conda search    libxslt
conda search    lxml
conda search    lz4-c
conda search    lzo
conda search    markupsafe
conda search    ncurses
conda search    openssl
conda search    pkginfo
conda search    psutil
conda search    py-lief
conda search    pycosat
conda search    pycparser
conda search    pyopenssl
conda search    pysocks
conda search    python-gitlab
conda search    python-libarchive-c
conda search    pyyaml
conda search    readline
conda search    readme_renderer
conda search    requests
conda search    ruamel_yaml
conda search    setuptools
conda search    smmap2
conda search    soupsieve
conda search    tabulate
conda search    termcolor
conda search    tk
conda search    toml
conda search    untokenize
conda search    urllib3
conda search    webencodings
conda search    xz
conda search    yaml
conda search    zlib
conda search    zstd

added 1 commit

• bbec08c6 - increase the build number of packages that we build so that they are built...

Compare with previous version

I found the issue! We used to provide tqdm in our channel but now it's also served in the defaults channel! The version of tqdm that conda-verify needs is not in our channel!

Conclusion is:

1. We create an "archive" label on both public and private channels
2. We move tqdm there
3. We index those to help people install that package if required

I just created the archive label on the public channel and moved tqdm there and enabled indexing there!

merged

mentioned in commit 841bd36b