All of lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla at busybox.net <bugzilla@busybox.net>
To: buildroot@busybox.net
Subject: [Buildroot] [Bug 11706] binman (U-boot tool) cannot find libfdt "binman: No module named _libfdt" if python3 selected
Date: Tue, 16 Feb 2021 21:48:06 +0000	[thread overview]
Message-ID: <bug-11706-163-OdxVbhSjR0@https.bugs.busybox.net/> (raw)
In-Reply-To: <bug-11706-163@https.bugs.busybox.net/>

https://bugs.busybox.net/show_bug.cgi?id=11706

Thomas Petazzoni <thomas.petazzoni@bootlin.com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
         Resolution|---                         |FIXED
             Status|ASSIGNED                    |RESOLVED

--- Comment #4 from Thomas Petazzoni <thomas.petazzoni@bootlin.com> ---
I indeed think this issue is resolved now that binman uses python3 in more
recent versions of U-Boot. Also Buildroot has been enhanced to be able to
describe U-Boot configurations that depend on python2 or python3.

Let's assume this is fixed.

-- 
You are receiving this mail because:
You are on the CC list for the bug.

      parent reply	other threads:[~2021-02-16 21:48 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-02-27  8:07 [Buildroot] [Bug 11706] New: binman (U-boot tool) cannot find libfdt "binman: No module named _libfdt" if python3 selected bugzilla at busybox.net
2019-08-13  1:17 ` [Buildroot] [Bug 11706] " bugzilla at busybox.net
2019-08-15 14:03 ` bugzilla at busybox.net
2020-03-03 21:22 ` bugzilla at busybox.net
2020-05-29 21:04 ` bugzilla at busybox.net
2021-02-16 21:48 ` bugzilla at busybox.net [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=bug-11706-163-OdxVbhSjR0@https.bugs.busybox.net/ \
    --to=bugzilla@busybox.net \
    --cc=buildroot@busybox.net \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.