From: "Mathieu Dubois-Briand" <mathieu.dubois-briand@bootlin.com>
To: <richard.purdie@linuxfoundation.org>,
<openembedded-core@lists.openembedded.org>
Subject: Re: [OE-core] [PATCH 45/48] shaderc: upgrade 2024.3 -> 2025.1
Date: Wed, 02 Apr 2025 15:45:36 +0200 [thread overview]
Message-ID: <D8W75RR7HN8B.LDDI93NM4URS@bootlin.com> (raw)
In-Reply-To: <20250402071017.2157620-45-richard.purdie@linuxfoundation.org>
On Wed Apr 2, 2025 at 9:10 AM CEST, Richard Purdie via lists.openembedded.org wrote:
> Add tag to SRC_URI to verify SRCREV.
>
> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
> ---
Hi Richard,
It looks like we have a revision error:
ERROR: shaderc-native-2025.1-r0 do_unpack: Bitbake Fetcher Error: FetchError("The revision the git tag 'v2025.1' resolved to didn't match the SRCREV in use (0968768c61d4eb7dd861114412e904bb3d59b7b6 vs 7f68b1cf6f35f518febf36d425365bb8e6ad224a)", 'git://github.com/google/shaderc.git;protocol=https;branch=main;tag=v2025.1')
Appears in a lot of builders:
https://autobuilder.yoctoproject.org/valkyrie/#/builders/2/builds/1322
https://autobuilder.yoctoproject.org/valkyrie/#/builders/3/builds/1360
https://autobuilder.yoctoproject.org/valkyrie/#/builders/4/builds/1321
https://autobuilder.yoctoproject.org/valkyrie/#/builders/6/builds/1336
https://autobuilder.yoctoproject.org/valkyrie/#/builders/9/builds/1298
...
--
Mathieu Dubois-Briand, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
next prev parent reply other threads:[~2025-04-02 13:45 UTC|newest]
Thread overview: 53+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-02 7:09 [PATCH 01/48] at-spi2-core: upgrade 2.56.0 -> 2.56.1 Richard Purdie
2025-04-02 7:09 ` [PATCH 02/48] barebox-tools: upgrade 2025.02.0 -> 2025.03.0 Richard Purdie
2025-04-02 7:09 ` [PATCH 03/48] base-passwd: upgrade 3.6.6 -> 3.6.7 Richard Purdie
2025-04-02 7:09 ` [PATCH 04/48] bind: upgrade 9.20.6 -> 9.20.7 Richard Purdie
2025-04-02 7:09 ` [PATCH 05/48] btrfs-tools: upgrade 6.13 -> 6.14 Richard Purdie
2025-04-02 7:17 ` [OE-core] " Alexander Kanavin
2025-04-02 8:32 ` Richard Purdie
2025-04-03 1:00 ` Khem Raj
2025-04-02 7:09 ` [PATCH 06/48] ccache: upgrade 4.11 -> 4.11.2 Richard Purdie
2025-04-02 7:09 ` [PATCH 07/48] connman: upgrade 1.43 -> 1.44 Richard Purdie
2025-04-02 7:09 ` [PATCH 08/48] createrepo-c: upgrade 1.2.0 -> 1.2.1 Richard Purdie
2025-04-02 7:09 ` [PATCH 09/48] diffoscope: upgrade 289 -> 293 Richard Purdie
2025-04-02 7:09 ` [PATCH 10/48] ed: upgrade 1.21 -> 1.21.1 Richard Purdie
2025-04-02 7:09 ` [PATCH 11/48] ell: upgrade 0.74 -> 0.75 Richard Purdie
2025-04-02 7:09 ` [PATCH 12/48] gtk4: upgrade 4.18.1 -> 4.18.3 Richard Purdie
2025-04-02 7:09 ` [PATCH 13/48] harfbuzz: upgrade 10.4.0 -> 11.0.0 Richard Purdie
2025-04-02 7:09 ` [PATCH 14/48] iproute2: upgrade 6.13.0 -> 6.14.0 Richard Purdie
2025-04-02 7:09 ` [PATCH 15/48] kmod: upgrade 34.1 -> 34.2 Richard Purdie
2025-04-02 7:09 ` [PATCH 16/48] libevdev: upgrade 1.13.3 -> 1.13.4 Richard Purdie
2025-04-02 7:09 ` [PATCH 17/48] libinput: upgrade 1.27.1 -> 1.28.1 Richard Purdie
2025-04-02 7:09 ` [PATCH 18/48] libnotify: upgrade 0.8.4 -> 0.8.6 Richard Purdie
2025-04-02 7:09 ` [PATCH 19/48] libsdl2: upgrade 2.32.2 -> 2.32.4 Richard Purdie
2025-04-02 7:09 ` [PATCH 20/48] libsoup: upgrade 3.6.4 -> 3.6.5 Richard Purdie
2025-04-02 7:09 ` [PATCH 21/48] libusb1: upgrade 1.0.27 -> 1.0.28 Richard Purdie
2025-04-02 7:09 ` [PATCH 22/48] lighttpd: upgrade 1.4.77 -> 1.4.78 Richard Purdie
2025-04-02 7:09 ` [PATCH 23/48] llvm: upgrade 20.1.0 -> 20.1.1 Richard Purdie
2025-04-02 7:09 ` [PATCH 24/48] mpfr: upgrade 4.2.1 -> 4.2.2 Richard Purdie
2025-04-02 7:09 ` [PATCH 25/48] ofono: upgrade 2.15 -> 2.16 Richard Purdie
2025-04-02 7:09 ` [PATCH 26/48] pango: upgrade 1.56.2 -> 1.56.3 Richard Purdie
2025-04-02 7:09 ` [PATCH 27/48] piglit: upgrade to latest revision Richard Purdie
2025-04-02 7:09 ` [PATCH 28/48] python3-beartype: upgrade 0.20.0 -> 0.20.2 Richard Purdie
2025-04-02 7:09 ` [PATCH 29/48] python3-calver: upgrade 2022.6.26 -> 2025.04.01 Richard Purdie
2025-04-02 7:09 ` [PATCH 30/48] python3-numpy: upgrade 2.2.3 -> 2.2.4 Richard Purdie
2025-04-02 7:10 ` [PATCH 31/48] python3-poetry-core: upgrade 2.1.1 -> 2.1.2 Richard Purdie
2025-04-02 7:10 ` [PATCH 32/48] python3-pygobject: upgrade 3.52.2 -> 3.52.3 Richard Purdie
2025-04-02 7:10 ` [PATCH 33/48] python3-pyparsing: upgrade 3.2.1 -> 3.2.3 Richard Purdie
2025-04-02 7:10 ` [PATCH 34/48] python3-pytz: upgrade 2025.1 -> 2025.2 Richard Purdie
2025-04-02 7:10 ` [PATCH 35/48] python3-rdflib: upgrade 7.1.3 -> 7.1.4 Richard Purdie
2025-04-02 7:10 ` [PATCH 36/48] python3-rpds-py: upgrade 0.22.3 -> 0.24.0 Richard Purdie
2025-04-02 7:10 ` [PATCH 37/48] python3-scons: upgrade 4.9.0 -> 4.9.1 Richard Purdie
2025-04-02 7:10 ` [PATCH 38/48] python3-setuptools-scm: upgrade 8.2.0 -> 8.2.1 Richard Purdie
2025-04-02 7:10 ` [PATCH 39/48] python3-setuptools: upgrade 76.0.0 -> 78.1.0 Richard Purdie
2025-04-02 7:10 ` [PATCH 40/48] python3-trove-classifiers: upgrade 2025.3.13.13 -> 2025.3.19.19 Richard Purdie
2025-04-02 7:10 ` [PATCH 41/48] python3-typing-extensions: upgrade 4.12.2 -> 4.13.0 Richard Purdie
2025-04-02 7:10 ` [PATCH 42/48] python3-yamllint: upgrade 1.36.0 -> 1.37.0 Richard Purdie
2025-04-02 7:10 ` [PATCH 43/48] qemu: Upgrade 9.2.0 -> 9.2.3 Richard Purdie
2025-04-02 7:10 ` [PATCH 44/48] repo: upgrade 2.52 -> 2.53 Richard Purdie
2025-04-02 7:10 ` [PATCH 45/48] shaderc: upgrade 2024.3 -> 2025.1 Richard Purdie
2025-04-02 13:45 ` Mathieu Dubois-Briand [this message]
2025-04-02 13:50 ` [OE-core] " Richard Purdie
2025-04-02 7:10 ` [PATCH 46/48] stress-ng: upgrade 0.18.11 -> 0.18.12 Richard Purdie
2025-04-02 7:10 ` [PATCH 47/48] sysklogd: upgrade 2.7.1 -> 2.7.2 Richard Purdie
2025-04-02 7:10 ` [PATCH 48/48] wayland-protocols: upgrade 1.41 -> 1.42 Richard Purdie
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=D8W75RR7HN8B.LDDI93NM4URS@bootlin.com \
--to=mathieu.dubois-briand@bootlin.com \
--cc=openembedded-core@lists.openembedded.org \
--cc=richard.purdie@linuxfoundation.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.