public inbox for openembedded-core@lists.openembedded.org
 help / color / mirror / Atom feed
From: dev-faha@t-online.de
To: openembedded-core@lists.openembedded.org
Subject: Re: Re: CVE-2022-24765 Git Errors with Bitbake
Date: Mon, 02 May 2022 05:02:45 -0700	[thread overview]
Message-ID: <29673.1651492965545397789@lists.openembedded.org> (raw)
In-Reply-To: <CANNYZj_68ACtcZxAqognRdHE_H8C8dAa2eMHmfHy6PUBDjq8Wg@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 314 bytes --]

Ok thanks. I found the commit id:
https://git.yoctoproject.org/poky/commit/?id=21559199516a31c7635c5f2d874eaa4a92fff0e5

Unfortunately, it will probably take some time until the solution is included on all our build machines.

Until then, we fixed our setup by using PSEUDO_UNLOAD=1 before any git command.

[-- Attachment #2: Type: text/html, Size: 339 bytes --]

      reply	other threads:[~2022-05-02 12:02 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-04-26  8:13 CVE-2022-24765 Git Errors with Bitbake dev-faha
2022-04-26  8:23 ` [OE-core] " Alexander Kanavin
2022-05-02 12:02   ` dev-faha [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=29673.1651492965545397789@lists.openembedded.org \
    --to=dev-faha@t-online.de \
    --cc=openembedded-core@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