Skip to content

Commit e268515

Browse files
committed
fix miscellaneous sphinx warnings
1 parent 7a9a525 commit e268515

File tree

8 files changed

+7
-10
lines changed

8 files changed

+7
-10
lines changed

misc/DEV_MEETING_TEMPLATE.md

Lines changed: 0 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -1,6 +1,5 @@
11
# YYYY-MM-DD conda-forge core meeting
22

3-
****
43
## Attendees
54
List the attendees for the meeting
65

src/maintainer/adding_pkgs.rst

Lines changed: 2 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -754,10 +754,9 @@ Jinja expressions serve following purposes in the meta.yaml:
754754

755755
- They allow defining variables to avoid code duplication. Using a variable for the ``version`` allows changing the version only once with every update.
756756

757-
.. code-block:: yaml
757+
.. code-block:: yaml+jinja
758758

759759
{% set version = "3.7.3" %}
760-
[...]
761760

762761
package:
763762
name: python
@@ -769,7 +768,7 @@ Jinja expressions serve following purposes in the meta.yaml:
769768

770769
- They can call `conda-build functions <https://docs.conda.io/projects/conda-build/en/latest/resources/define-metadata.html#conda-build-specific-jinja2-functions>`__ for automatic code generation. Examples are the compilers, cdt packages or the ``pin_compatible`` function.
771770

772-
.. code-block:: yaml
771+
.. code-block:: yaml+jinja
773772

774773
requirements:
775774
build:

src/maintainer/pinning_deps.rst

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -106,7 +106,7 @@ be added by hand. To do this, follow these steps:
106106

107107
#. Create a new migration yaml by copying `example.exyaml <https://github.com/conda-forge/conda-forge-pinning-feedstock/blob/master/recipe/migrations/example.exyaml>`__ in the ``conda-forge/conda-forge-pinning`` repository.
108108
#. Change the migration yaml to reflect the package and version to be migrated
109-
#. Write a :ref:`migrator <pin_migrator>` for propagating the pin changes.
109+
#. Write a migrator for propagating the pin changes.
110110
#. Propose the changes as a :term:`PR` to `conda-forge/conda-forge-pinning-feedstock`_.
111111
#. Once accepted the migration will begin. The migration status can be monitored at https://conda-forge.org/status.
112112
#. After the migration is complete, a new PR can be issued to `conda-forge/conda-forge-pinning-feedstock`_ to:

src/orga/minutes/2018-04-17.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -29,7 +29,7 @@
2929
- John: Get a pygdf-feedstock on conda-forge and ping the Nvidia folks
3030
- Adding people to cf/staged-recipes
3131
- ~~Marius van Niekerk offered to help review on staged-recipes~~ Invited to staged recipes
32-
~~~~ - Igor T. Ghisi (igortg) was also interested in helping
32+
- Igor T. Ghisi (igortg) was also interested in helping
3333
- Adding people to core
3434
- Invite one or more from bioconda.
3535
- Bjorn (Filipe will invite)

src/orga/minutes/2018-10-30.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -14,7 +14,7 @@
1414
- Compiler rebuild status
1515
- python done for both compiler stacks
1616
- ~~pending: openblas (numeric stack currently held up)~~
17-
~~~~ - Qt: try to build on Azure?
17+
- Qt: try to build on Azure?
1818
- New approach to reducing CI load https://github.com/conda-forge/conda-forge.github.io/issues/647
1919
- Might be possible to not be totally insecure with work. But nobody is volunteering to do that work right now. :)
2020
- Pushing PR builds to a staging channel might be a nice UX improvement so you can test anyway.

src/orga/minutes/2019-05-29.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -19,7 +19,7 @@
1919
- Coordinate more SciPy activities: lightning talks, lunch/dinner?
2020
- ~~TODO: Open an issue on github conda-forge.github.io to keep track of who is going to Scipy 2019~~
2121
- https://github.com/conda-forge/conda-forge.github.io/issues/791
22-
~~~~- Discuss a strategy to manage qt patches (23!) and new version builds in the CIs.
22+
- Discuss a strategy to manage qt patches (23!) and new version builds in the CIs.
2323
- ESIP update:
2424
- balance: 3827.78 USD
2525
- use part of the money to pay for Azure dedicated machines: Windows and Linux to build Qt.

src/orga/minutes/2019-07-24.md

Lines changed: 0 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -1,7 +1,6 @@
11
# 2017-07-24 conda-forge core meeting
22

33
[HackMD link](https://hackmd.io/P8on5P8wR3q3WslwrJzOEg)
4-
[Zoom link]()
54
## Attendees
65
List the attendees for the meeting
76

src/user/ci-skeleton.rst

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -68,7 +68,7 @@ you can use the ``-r`` option to supply an alternative.
6868

6969
The **meta.yaml** looks like:
7070

71-
.. code-block:: yaml
71+
.. code-block:: yaml+jinja
7272

7373
{% set name = "myproj" %}
7474
{% set version = environ.get('GIT_DESCRIBE_TAG', 'untagged')|string|replace('-','_') %}

0 commit comments

Comments
 (0)