On Wed, 24 Apr 2024 at 12:08, Rasmus Villemoes
wrote:
> How would one know? It's not in master-next, and I don't see any other
> branches containing it. Is there some git repo other than
> https://git.openembedded.org/openembedded-core/ one could follow to see
> that a patch has actually been
On Wed, 2024-04-24 at 12:08 +0200, Rasmus Villemoes wrote:
> On 24/04/2024 10.36, Alexander Kanavin via lists.openembedded.org
> wrote:
> > On Wed, 24 Apr 2024 at 10:19, Christian B. Sørensen via
> > lists.openembedded.org
> > wrote:
> >
> > > Any input on the patchset ? Would appreciate if it
On 24/04/2024 10.36, Alexander Kanavin via lists.openembedded.org wrote:
> On Wed, 24 Apr 2024 at 10:19, Christian B. Sørensen via
> lists.openembedded.org
> wrote:
>
>> Any input on the patchset ? Would appreciate if it could be included in the
>> scarthgap release.
>
> A little patience
On Wed, 24 Apr 2024 at 10:19, Christian B. Sørensen via
lists.openembedded.org
wrote:
> Any input on the patchset ? Would appreciate if it could be included in the
> scarthgap release.
A little patience would help. The patch is fine (and so there's not
input), it's in a staging branch, but
Hi
Added CC's that signed off by on commit ebafe46379 systemd: upgrade to
255.1.
On 4/18/24 07:58, yo...@bsorensen.net wrote:
From: Christian Bräuner Sørensen
Fixes a bug introducted in ebafe46379 systemd: upgrade to 255.1.
Besides updating systemd, that commit also made other changes. One
From: Christian Bräuner Sørensen
Fixes a bug introducted in ebafe46379 systemd: upgrade to 255.1.
Besides updating systemd, that commit also made other changes. One of them
being when to perform the replacement in order to fix ROOT_HOME.
Previously, that happened on a configure prefunc and on
