public inbox for docs@lists.yoctoproject.org
 help / color / mirror / Atom feed
From: "Antonin Godard" <antonin.godard@bootlin.com>
To: <quentin.schulz@cherry.de>, <docs@lists.yoctoproject.org>
Cc: "Thomas Petazzoni" <thomas.petazzoni@bootlin.com>
Subject: Re: [docs] [PATCH 1/2] set_versions.py: skip laverne branch for closest branch
Date: Thu, 02 Apr 2026 10:28:47 +0200	[thread overview]
Message-ID: <DHIJ01UHFNCM.3PGI9MA9GAFV2@bootlin.com> (raw)
In-Reply-To: <9955c1bf-c6ea-4e6b-aa68-f0a6df16ac95@cherry.de>

Hi,

On Thu Apr 2, 2026 at 10:22 AM CEST, Quentin Schulz via lists.yoctoproject.org wrote:
> Hi Antonin,
>
> On 4/2/26 10:13 AM, Antonin Godard via lists.yoctoproject.org wrote:
>> The laverne branch was created but never branched off, which breaks the
>> algorithm trying to determine the closest branch as it always gets count
>> 0. Skip this branch as it is old and we'll never branch off of it now.
>> 
>> This fixes the following issue:
>> 
>> Branch laverne has count 0
>> Nearest release branch estimated to be laverne
>> Traceback (most recent call last):
>>    File "/data/yoctoproject/ws/repos/yocto-docs/documentation/./set_versions.py", line 167, in <module>
>>      bitbakeversion = bitbake_mapping[ourseries]
>>                       ~~~~~~~~~~~~~~~^^^^^^^^^^^
>> KeyError: 'laverne'
>> 
>> Signed-off-by: Antonin Godard <antonin.godard@bootlin.com>
>> ---
>>   documentation/set_versions.py | 5 +++++
>>   1 file changed, 5 insertions(+)
>> 
>> diff --git a/documentation/set_versions.py b/documentation/set_versions.py
>> index 29638b324..465204998 100755
>> --- a/documentation/set_versions.py
>> +++ b/documentation/set_versions.py
>> @@ -142,6 +142,11 @@ if ourversion is None:
>>               result = subprocess.run(["git", "log", "--format=oneline", "HEAD..origin/" + b],
>>                                       stdout=subprocess.PIPE, stderr=subprocess.PIPE,
>>                                       universal_newlines=True)
>> +            # The laverne branch was created but never branched off, which
>> +            # breaks this algorithm as this always gets count 0. Skip this
>> +            # branch as it is old and we'll never branch off of it now.
>> +            if b == "laverne":
>> +                continue
>
> Why run the command if we're gonna skip the loop regardless of the 
> result of the command? Just do the continue before the subprocess.run?

An oversight, I'll move it above, thanks

Antonin


  reply	other threads:[~2026-04-02  8:28 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-04-02  8:13 [PATCH 0/2] set_versions.py fixes Antonin Godard
2026-04-02  8:13 ` [PATCH 1/2] set_versions.py: skip laverne branch for closest branch Antonin Godard
2026-04-02  8:22   ` [docs] " Quentin Schulz
2026-04-02  8:28     ` Antonin Godard [this message]
2026-04-02  8:13 ` [PATCH 2/2] set_versions.py: fix get_latest_tag and milestone tags 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=DHIJ01UHFNCM.3PGI9MA9GAFV2@bootlin.com \
    --to=antonin.godard@bootlin.com \
    --cc=docs@lists.yoctoproject.org \
    --cc=quentin.schulz@cherry.de \
    --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