We have fixed a bug where the maintainers of feedstocks listed in the
meta.yaml
did not match those listed in the GitHub team. Due to this
change, you may notice emails from GitHub informing you that you have
been removed from a GitHub team if you have recently removed yourself
from a feedstock via changing the meta.yaml
. A similar fix has been
applied for maintenance teams as well, though you will not see emails
from this fix.
CentOS 7 sysroot Now Available for linux-64 Builds
We are very excited to announce that new compilers based on repackaged
sysroot
's from CentOS 7 are now available for all linux-*
platforms.
These compilers will be the default going forward for any gcc
, gxx
,
and gfortran
versions past 8.4.0
on ppc64le
and 7.5.0
on
x86_64
/aarch64
.
On the linux-64
platform, we have also built the CentOS 6 sysroot
and set it as the default, consistent with our current compilers. To use
the CentOS 7 sysroot
on linux-64
, add a requirement of
sysroot_linux-64 2.17
to the build section of your recipe. You also
need to set the proper Docker image in your conda_build_config.yaml
.
See Using CentOS 7 <centos7>
for details.
NumPy 1.16 is the minimal NumPy version on all platforms
In accordance with
NEP-29, we
have switched to have numpy 1.16
as the minimum supported version on
all platforms.
Strict channel priority in builds for OSX and Linux
We have changed the OSX and Linux platforms to enforce strict channel
priority in package builds. This change means that if a package is
available in the conda-forge channels, the conda
solver will not
consider any versions of the package from other channels. Users can
disable this by setting channel_priority: flexible
in their
conda-forge.yml
.
Conda-forge is building openblas with both pthreads and openmp on Linux
The main change is that openblas
will use pthreads for threading by
default on Linux instead of the previous openmp
default. The openmp
builds can be recovered by installing libopenblas=*=*openmp*
.
Core Dependency Tree Package Changes
conda-forge is moving to a new system for generating Core Dependency Tree (CDT) packages. These changes include:
- CDT packages will no longer be built using feedstocks and this practice is officially deprecated.
- Any current CDT packages in feedstocks will be moved to the new conda-forge/cdt-builds repo and the feedstock will be archived. Members of core will be doing this slowly on an as-needed basis, so it may not happen right away.
- Requests for new CDTs should be submitted as PRs to the conda-forge/cdt-builds repo.
These changes are being made so that conda-forge can provide access to
CentOS 7 / glibc 2.17 for linux-64
builds. They will also move more of
the packages needed for conda-forge builds into the conda-forge channels
making builds more reliable.
Moving from clang 9 to clang 10
conda-forge is moving to clang 10 on macOS! Check the release notes for what is new, breaking, or deprecated.
CFEP-18: Removing static libraries from the main build
With CFEP-18
we now have a policy on how to deal with static packages. The most
important change here is that we will be removing static libraries from
the main packages and moving them to -static
suffixed packages.
-static
packages will not be built by default but only on request.
cf-mark-broken renamed to admin-requests
The cf-mark-broken
repo has been renamed to admin-requests
. It still
serves the same purpose. However, we have expanded the capabilities of
the repo to be able to mark packages as not broken.
New Process for Marking Packages as Broken
We are changing the way we mark packages as broken
to better match the defaults
channel and to
better enable reproducible environments that depended on broken packages. We will now be adding the
broken
label to packages but leaving them on the main
channel. In order to make sure they do
not appear in the repodata.json
for the main
channel, we will be patching the repo data to
remove them using the removals
feature. Users will notice the following changes
- The packages on
anaconda.org
will now have both themain
and thebroken
labels. - All requests to mark packages as broken must be sent to the
cf-mark-broken
repo. - Members of
core
can no longer mark things as broken by hand since the repo data patching must be done as well. - The package metadata for broken packages may differ slightly from when they were on the
main
channel. - The only correct source of package metadata is now the
repodata.json
etc onanaconda.org
. Any other sources may be missing critical changes.