|
17 | 17 | Exited with code 128
|
18 | 18 |
|
19 | 19 | open a new issue with a comment :ref:`ci_update_circle`.
|
20 |
| - Once our web services updated the circle configuration, restart the build. |
| 20 | + Once our web services have updated the circle configuration, restart the build. |
21 | 21 |
|
22 | 22 |
|
23 | 23 | .. _mfaq_py37_selector:
|
|
28 | 28 |
|
29 | 29 | conda-build has changed the selector syntax.
|
30 | 30 | You are now encouraged to use ``py==<version>``, instead of ``py<version>``.
|
31 |
| - While the legacy selectors ``py27`` and ``py36`` are still valid, ``py37`` and higher are not available anymore. |
| 31 | + While the legacy selectors ``py27`` and ``py36`` are still valid, selectors ``py37`` and higher are no longer valid. |
32 | 32 |
|
33 | 33 | Please use the new syntax ``py==27``, ``py==36`` and ``py==37`` to avoid confusion.
|
34 | 34 |
|
|
44 | 44 |
|
45 | 45 | TL;DR: there is no need for build numbers larger than 1000 anymore.
|
46 | 46 |
|
47 |
| - When you update a feedstock that still uses build numbers > 1000, following rules apply: |
| 47 | + When you update a feedstock that still uses build numbers > 1000, the following rules apply: |
48 | 48 |
|
49 | 49 | - when you increase the version, reset the build number back to 0 (e.g. ``1005 -> 0``).
|
50 | 50 | - when the version stays the same and you need to upload a new package, increase the build number by 1 (e.g. ``1005 -> 1006``).
|
|
67 | 67 |
|
68 | 68 | :ref:`(Q) <mfaq_anaconda_delay>` **Why does my new version appear on Anaconda Cloud, but is not installable with conda?**
|
69 | 69 |
|
70 |
| - For certain, high-traffic channels (main & conda-forge), Anaconda uses a CDN to decrease costs. The CDN is only reindexed every 20 min, however Anaconda.org uses the original channel that the CDN mirrors. Therefore, packages will show up on the anaconda.org ~20-40 min before they are downloadable by conda. You can use conda search <pkg> to see if the package is installable, because this command reads from the CDN. |
| 70 | + For certain, high-traffic channels (main & conda-forge), Anaconda uses a `CDN <https://cloudflare.com/learning/cdn/what-is-a-cdn/>`_ to decrease costs. The CDN is only reindexed every 20 minutes, however `Anaconda.org https://anaconda.org>`_ uses the original channel that the CDN mirrors. Therefore, packages will show up on the `Anaconda Cloud https://anaconda.org>`_ about 20 to 40 minutes before they are downloadable via conda. You can use ``conda search <pkg>`` to see if the package is installable, because this command reads from the CDN. |
0 commit comments