public inbox for docs@lists.yoctoproject.org
 help / color / mirror / Atom feed
From: Quentin Schulz <quentin.schulz@cherry.de>
To: Antonin Godard <antonin.godard@bootlin.com>, docs@lists.yoctoproject.org
Cc: Thomas Petazzoni <thomas.petazzoni@bootlin.com>,
	Julien Stephan <jstephan@baylibre.com>
Subject: Re: [PATCH] conf.py: rename :cve: role to :cve_nist:
Date: Mon, 4 Nov 2024 15:06:31 +0100	[thread overview]
Message-ID: <f63a2a9b-5ef2-42d5-b423-e1924e90ad97@cherry.de> (raw)
In-Reply-To: <D5DFJNMJZVEW.HSMGI2KFHB0O@bootlin.com>

Hi Antonin,

On 11/4/24 2:31 PM, Antonin Godard wrote:
> On Mon Nov 4, 2024 at 1:55 PM CET, Quentin Schulz wrote:
>> Hi Antonin,
>>
>> On 11/4/24 1:39 PM, Antonin Godard wrote:
>>> Newer versions of Sphinx already define a :cve: role that points to
>>> cve.org, instead of the role we defined in conf.py that points to
>>> nvd.nist.gov.
>>>
>>> Rename our role to :cve_nist: to avoid warnings (treated as errors).
>>> This is also backwards compatible, meaning we can build the doc with an
>>> older Sphinx if needed.
>>>
>>> Suggested-By: Quentin Schulz <quentin.schulz@cherry.de>
>>> Signed-off-by: Antonin Godard <antonin.godard@bootlin.com>
>>
>> Looks good to me. I assume you didn't change those by hand, maybe add
>> the command you used to do the migration so we can figure out if
>> something's been left out inadvertently? (Would be useful if we figure
>> out in the future that this missed something so we can more easily find
>> a programmatic way of fixing the left-out instead of finding and fixing
>> them by hand?).
> 
> Hmm... I used my editor, but the equivalent one-liner is:
> 
> find . -name '*.rst' -exec sed -i 's/:cve:/:cve_nist:/g' {} \+
> 
> Which I'll add to the commit message.
> 
>> Reviewed-by: Quentin Schulz <quentin.schulz@cherry.de>
>>
>> (Admittedly only reviewed the conf.py part :) ).
>>
>> For backporting, we'll likely need a new patch on the autobuilder, c.f.
>> https://git.yoctoproject.org/yocto-autobuilder-helper/tree/scripts/docs-build-patches
>> since we want to build tags which we cannot move.
> 
> If I understand correctly, these are patches to apply to old documentation
> versions? To extend my reasoning on this, since new tags were added recently for
> old doc versions, should I update `missing_tags` and add corresponding patches
> there? I'm a bit clueless :)
> 

I haven't really checked what the ramifications are for those new tags. 
It's possible it fixes a bunch of stuff that we needed to work around. 
Maybe we don't even need that missing_tags logic anymore at all in 
set_versions.py. But that would only fix the generation of the 
releases.rst file, which is different from fixing content of old 
unmaintained releases for newer Sphinx versions, which is handled in the 
yocto-autobuilder. I think they aren't related here but haven't spent 
some time recently on that so cannot tell right now.

Cheers,
Quentin


  reply	other threads:[~2024-11-04 14:06 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-11-04 12:39 [PATCH] conf.py: rename :cve: role to :cve_nist: Antonin Godard
2024-11-04 12:55 ` Quentin Schulz
2024-11-04 13:31   ` Antonin Godard
2024-11-04 14:06     ` Quentin Schulz [this message]
2024-11-04 14:26       ` Antonin Godard

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=f63a2a9b-5ef2-42d5-b423-e1924e90ad97@cherry.de \
    --to=quentin.schulz@cherry.de \
    --cc=antonin.godard@bootlin.com \
    --cc=docs@lists.yoctoproject.org \
    --cc=jstephan@baylibre.com \
    --cc=thomas.petazzoni@bootlin.com \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox