From: Geoff Parker <geoffhp@gmail.com>
To: Khem Raj <raj.khem@gmail.com>
Cc: openembedded-devel@lists.openembedded.org,
akuster808 <akuster808@gmail.com>
Subject: Re: [oe] [PATCH] nodejs-oe-cache: fix offline install of dependencies
Date: Tue, 14 May 2024 10:39:40 -0700 [thread overview]
Message-ID: <CAHNuFG+VTPkL3zqaMh8a46atjC21GcgQgJ7GTix9BNsMzm88rA@mail.gmail.com> (raw)
In-Reply-To: <CAMKF1sqtpdSbdNKGsvsJOd2q7xRs6UoU1rCfHUYVUbTjK2Bhow@mail.gmail.com>
Thanks Khem for the link to openembedded-contrib and information on
how scarthgap updates
are staged. However, I'm not seeing the nodejs-os-cache commit in the
stable/scarthgap-nut
branch which is needed to fix nodejs builds on scarthgap also. Are
recent fixes in
meta-openembedded master backported also?
cc: Armin
On Mon, May 13, 2024 at 9:48 AM Khem Raj <raj.khem@gmail.com> wrote:
>
> On Sun, May 12, 2024 at 11:57 PM Geoff Parker via
> lists.openembedded.org <geoffhp=gmail.com@lists.openembedded.org>
> wrote:
> >
> > When is the expected next update to the scarthgap branch? I've watched the patch move from master-next to master, but there does not seem to be a visible scarthgap-next branch to watch.
>
> Usually there is a monthly release update to stable branches that
> Armin queues up in contrib repo e.g.
>
> https://git.openembedded.org/meta-openembedded-contrib/log/?h=stable/scarthgap-nut
>
> eventually when this branch is gone through some level of testing, it
> is proposed to upstream
> branch via scarthgap-next in main repo.
>
> > -=-=-=-=-=-=-=-=-=-=-=-
> > Links: You receive all messages sent to this group.
> > View/Reply Online (#110334): https://lists.openembedded.org/g/openembedded-devel/message/110334
> > Mute This Topic: https://lists.openembedded.org/mt/105884883/1997914
> > Group Owner: openembedded-devel+owner@lists.openembedded.org
> > Unsubscribe: https://lists.openembedded.org/g/openembedded-devel/unsub [raj.khem@gmail.com]
> > -=-=-=-=-=-=-=-=-=-=-=-
> >
next prev parent reply other threads:[~2024-05-14 17:39 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-03 9:42 [PATCH] nodejs-oe-cache: fix offline install of dependencies Martin Hundebøll
2024-05-03 9:44 ` Martin Hundebøll
2024-05-03 9:51 ` [oe] " Martin Jansa
[not found] ` <17CBF1C9439E153E.14737@lists.openembedded.org>
2024-05-03 12:43 ` Martin Jansa
2024-05-06 7:15 ` Martin Hundebøll
2024-05-06 14:37 ` [oe] " Khem Raj
2024-05-13 6:57 ` Geoff Parker
2024-05-13 16:48 ` [oe] " Khem Raj
2024-05-14 17:39 ` Geoff Parker [this message]
2024-05-21 19:33 ` Ferry Toth
2024-05-30 19:29 ` Ferry Toth
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=CAHNuFG+VTPkL3zqaMh8a46atjC21GcgQgJ7GTix9BNsMzm88rA@mail.gmail.com \
--to=geoffhp@gmail.com \
--cc=akuster808@gmail.com \
--cc=openembedded-devel@lists.openembedded.org \
--cc=raj.khem@gmail.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).