From: Quentin Schulz <quentin.schulz@theobroma-systems.com>
To: michael.opdenacker@bootlin.com, yocto@lists.yoctoproject.org
Subject: Re: [yocto] [PATCH yocto-autobuilder-helper] run-docs-build: allow build warnings again
Date: Mon, 4 Jul 2022 15:24:56 +0200 [thread overview]
Message-ID: <4828a5c0-59c1-ef5e-385f-1b563d3577ee@theobroma-systems.com> (raw)
In-Reply-To: <20220622153201.2734009-1-michael.opdenacker@bootlin.com>
Hi Michael,
On 6/22/22 17:32, Michael Opdenacker via lists.yoctoproject.org wrote:
> From: Michael Opdenacker <michael.opdenacker@bootlin.com>
>
> This allows to switch to a more recent of Sphinx
> which will generate warnings with old versions of docs.
>
> This way, it's not immediately necessary to patch
> all such versions.
>
> This commit reverts
> https://urldefense.proofpoint.com/v2/url?u=https-3A__git.yoctoproject.org_yocto-2Dautobuilder-2Dhelper_commit_-3Fid-3D8273124feb9da2ffe93fcee7c4529d5597e1684a&d=DwIDAg&c=_sEr5x9kUWhuk4_nFwjJtA&r=LYjLexDn7rXIzVmkNPvw5ymA1XTSqHGq8yBP6m6qZZ4njZguQhZhkI_-172IIy1t&m=je4C362aUVxZ2rdozdrQVTgzhi9iRYrxNfYtH5LHkXdlsay9SEphJ_ekBm4830_n&s=9u5-2R_NLEQy5w0pFgklKIUQnAvVLuHX1ASaeEBBJJ4&e=
> which originally reverted
> https://urldefense.proofpoint.com/v2/url?u=https-3A__git.yoctoproject.org_yocto-2Dautobuilder-2Dhelper_commit_-3Fid-3D931d409b255a85f2217ca093d8391a678ce00ddb&d=DwIDAg&c=_sEr5x9kUWhuk4_nFwjJtA&r=LYjLexDn7rXIzVmkNPvw5ymA1XTSqHGq8yBP6m6qZZ4njZguQhZhkI_-172IIy1t&m=je4C362aUVxZ2rdozdrQVTgzhi9iRYrxNfYtH5LHkXdlsay9SEphJ_ekBm4830_n&s=bTED2gTptfT6bSvLayy3fEpQJyUdbo5gLlt7ZGKkD1c&e=
>
> Signed-off-by: Michael Opdenacker <michael.opdenacker@bootlin.com>
> ---
> scripts/run-docs-build | 4 ++--
> 1 file changed, 2 insertions(+), 2 deletions(-)
>
> diff --git a/scripts/run-docs-build b/scripts/run-docs-build
> index 648a29d..0f74520 100755
> --- a/scripts/run-docs-build
> +++ b/scripts/run-docs-build
> @@ -63,7 +63,7 @@ for branch in 1.46 $(git branch --remote --contains "$first_sphinx_commit" --for
> git checkout $branch
> git checkout master releases.rst
> make clean
> - make publish
> + SPHINXOPTS="-j auto" make publish
>
> if [ "$branch" = "master-next" ]; then
> branch="next"
> @@ -136,7 +136,7 @@ for branch in dunfell $(git branch --remote --contains "$first_sphinx_commit" --
> fi
>
> make clean
> - make publish
> + SPHINXOPTS="-j auto" make publish
>
What about doing this for all branches except master? To have at least
some checks and not completely disable the warnings.
I'm a bit afraid we'll just not care about warnings anymore since they
won't fail the autobuilder anymore. I also understand it's not really
sustainable to leave them on for old docs since they won't be maintained
at one point in time but we still very mnuch would like to be able to
build them.
Not sure what's the best solution here right now unfortunately :/
Cheers,
Quentin
next prev parent reply other threads:[~2022-07-04 13:25 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-22 15:32 [PATCH yocto-autobuilder-helper] run-docs-build: allow build warnings again michael.opdenacker
2022-07-04 13:24 ` Quentin Schulz [this message]
2022-07-04 14:23 ` [yocto] " Richard Purdie
2022-07-05 11:21 ` Quentin Schulz
2022-07-05 11:58 ` Richard Purdie
2022-07-19 17:35 ` Michael Opdenacker
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4828a5c0-59c1-ef5e-385f-1b563d3577ee@theobroma-systems.com \
--to=quentin.schulz@theobroma-systems.com \
--cc=michael.opdenacker@bootlin.com \
--cc=yocto@lists.yoctoproject.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.