From: "Christian Schaefer" <christian.schaefer@at.abb.com>
To: bitbake-devel@lists.openembedded.org
Subject: Re: bitbake-setup: sync layers to branch HEAD
Date: Wed, 17 Jun 2026 08:33:07 -0700 [thread overview]
Message-ID: <203383.1781710387657029391@lists.openembedded.org> (raw)
In-Reply-To: <CANNYZj_nQiHUjVvips9+kn7XV1JZquZDJs-5RCZ6RpDAHgCYRw@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 580 bytes --]
Thanks for the hint. I found the error.
To test the ``update`` functionality originally, I additionally used ``--source-overrides`` to pin a certain lock file, which referenced (on purpose) an older commit in the oe-core wrynose branch.
Then, I assumed, by calling ``bitbake-setup update`` this would then sync the layer to the latest upstream HEAD (fast-forward from the older commit to the latest).
However, it seems that the ``bitbake-setup update`` does not work in that combination (if the revs are initially pinned). Which is fine for me.
Thanks for the fast help!
[-- Attachment #2: Type: text/html, Size: 637 bytes --]
prev parent reply other threads:[~2026-06-17 15:33 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-06-17 12:01 bitbake-setup: sync layers to branch HEAD Christian Schaefer
2026-06-17 12:37 ` [bitbake-devel] " Alexander Kanavin
2026-06-17 15:33 ` Christian Schaefer [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=203383.1781710387657029391@lists.openembedded.org \
--to=christian.schaefer@at.abb.com \
--cc=bitbake-devel@lists.openembedded.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox