public inbox for docs@lists.yoctoproject.org
 help / color / mirror / Atom feed
From: Quentin Schulz <quentin.schulz@cherry.de>
To: antonin.godard@bootlin.com, docs@lists.yoctoproject.org
Cc: Thomas Petazzoni <thomas.petazzoni@bootlin.com>,
	Robert Berger <pokylinux@reliableembeddedsystems.com>
Subject: Re: [docs] [PATCH] dev-manual/packages.rst: pr server: fix and explain why r0.X increment on srcrev change
Date: Tue, 20 Jan 2026 17:59:23 +0100	[thread overview]
Message-ID: <2ffff554-09a1-42eb-ab2b-de1254983776@cherry.de> (raw)
In-Reply-To: <20260120-pr-server-increment-details-v1-1-fa5d288def24@bootlin.com>

Hi Antonin,

On 1/20/26 3:39 PM, Antonin Godard via lists.yoctoproject.org wrote:
> The current example of the SRCREV change triggering a gitX bump is
> wrong, as both gitX and r0.X get incremented.
> 
> Why this is happening is explained in bug 15729, which I copy here:
> 
>> +gitX+ is indeed related to changes in the source code.
>>
>> r0.X is bumped each time the checksum of the do_package task of the
>> simple-hello-world-git recipe changes. This happens here:
>> https://git.openembedded.org/openembedded-core/tree/meta/classes-global/package.bbclass?id=235e6d49e5888ad04416219e10b6df91a738661a#n306
>>
>> This line sets the value of PRAUTO and represents the number X found in
>> r0.X. It will in the end make it into EXTENDPRAUTO, which itself makes
>> to PKGR == r0.X.
>>
>> This line calls getPR(version, pkgarch, checksum). Between test case 5
>> and 6, only the checksum changes. This checksum is the checksum of the
>> do_package task (gotten from get_do_package_hash() above).
>>
>> Now, let's dump what changed with regards to this task between two
>> consecutive runs, using the sigdata file in build/tmp/stamps/:
>>
>> ```
>> [...]
>> Variable fetcher_hashes_dummyfunc value changed from '2650ad6714c3f3248abfe9d3daf1196f307ed494' to '4af682a50174f5deb0397847da97d7cdba4ad067'
>> ```
>>
>> The last line shows that the value of fetcher_hashes_dummyfunc changed
>> from '2650ad6714c3f3248abfe9d3daf1196f307ed494' to
>> '4af682a50174f5deb0397847da97d7cdba4ad067'. Those are the commit hashes
>> in the git history of the simple-hello-world-git repository.
>>
>> Now you can see why this 0.X gets bumped, is because of the SRCREV change.
> 
> Fix the example, and detail what gets changed and why.
> 
> [YOCTO #15729]
> 
> Cc: Robert Berger <pokylinux@reliableembeddedsystems.com>
> Signed-off-by: Antonin Godard <antonin.godard@bootlin.com>
> ---
>   documentation/dev-manual/packages.rst | 15 ++++++++++++++-
>   1 file changed, 14 insertions(+), 1 deletion(-)
> 
> diff --git a/documentation/dev-manual/packages.rst b/documentation/dev-manual/packages.rst
> index 8bd48c8e8..9c38bc39b 100644
> --- a/documentation/dev-manual/packages.rst
> +++ b/documentation/dev-manual/packages.rst
> @@ -275,7 +275,20 @@ with a number. The number used depends on the state of the PR Service:
>      .. code-block:: none
>   
>         hello-world-git_0.0+git0+b6558dd387-r0.0_armv7a-neon.ipk
> -      hello-world-git_0.0+git1+dd2f5c3565-r0.0_armv7a-neon.ipk
> +      hello-world-git_0.0+git1+dd2f5c3565-r0.1_armv7a-neon.ipk
> +
> +   Two numbers got incremented here:
> +
> +   -  ``gitX`` changed from ``git0`` to ``git1``. This is because there was a
> +      change in the source code (``SRCREV``).
> +
> +   -  ``r0.X`` changed from ``r0.0`` to ``r0.1``. This is because there was a
> +      change in the recipe, which ultimately the hash of the
> +      :ref:`ref-tasks-package` task (the variable ``SRCREV`` changed value).
> +

Missing verb in the second part of the sentence.

Cheers,
Quentin


      reply	other threads:[~2026-01-20 16:59 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-01-20 14:39 [PATCH] dev-manual/packages.rst: pr server: fix and explain why r0.X increment on srcrev change Antonin Godard
2026-01-20 16:59 ` Quentin Schulz [this message]

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=2ffff554-09a1-42eb-ab2b-de1254983776@cherry.de \
    --to=quentin.schulz@cherry.de \
    --cc=antonin.godard@bootlin.com \
    --cc=docs@lists.yoctoproject.org \
    --cc=pokylinux@reliableembeddedsystems.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