bitbake-setup: sync layers to branch HEAD

bitbake-setup: sync layers to branch HEAD

[Christian Schaefer]

Hi, I have a question regarding bitbake-setup.

In a *.conf.json file, I can configure bitbake-setup to use the latest commit
on a branch by setting `rev` to the same value as `branch`. For example:

"sources": {
    "openembedded-core": {
        "git-remote": {
            "uri": "https://git.openembedded.org/openembedded-core",
            "branch": "wrynose",
            "rev": "wrynose"
        }
    },
    ...
}

Over time, new commits are pushed to the upstream branch (wrynose). Is there a
way to sync my local checkout to the updated upstream branch without running
`git pull` manually for each layer? Originally, I assumed this would be done by
running `bitbake-setup update`, but no changes are detected, as the *.conf.json
file is still the same.

Regards, Christian

Re: [bitbake-devel] bitbake-setup: sync layers to branch HEAD

[Alexander Kanavin]

On Wed, 17 Jun 2026 at 14:01, Christian Schaefer via
lists.openembedded.org
<christian.schaefer=at.abb.com@lists.openembedded.org> wrote:
> Over time, new commits are pushed to the upstream branch (wrynose). Is there a
> way to sync my local checkout to the updated upstream branch without running
> `git pull` manually for each layer? Originally, I assumed this would be done by
> running `bitbake-setup update`, but no changes are detected, as the *.conf.json
> file is still the same.

This should be happening in 'update', particularly this bit of code handles it:

           upstream_revision = fetcher.method.latest_revision(fetcher,
d, 'default')
            if upstream_revision != local_revision:
                changed = True
                logger.info('Layer repository {} checked out into {}
updated revision {} from {} to {}'.format(remote,
os.path.join(layerdir, repodir), rev, local_revision,
upstream_revision))

Can you check why it isn't triggering?

Alex

Re: bitbake-setup: sync layers to branch HEAD

[Christian Schaefer]

[-- 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 --]