From: Ola x Nilsson <ola.x.nilsson@axis.com>
To: "bitbake-devel@lists.openembedded.org"
<bitbake-devel@lists.openembedded.org>
Subject: Re: [PULL] *** Fix build issue with html5lib in bitbake 1.26/1.28 ***
Date: Wed, 28 Mar 2018 09:41:52 +0000 [thread overview]
Message-ID: <1522230112838.18244@axis.com> (raw)
In-Reply-To: <cover.1522085586.git.soemoe.a@gmail.com>
This has already been fixed on a few branches with
bitbake: lib/bs4: Fix imports from html5lib >= 0.9999999/1.0b8
It might be better to backport that where needed.
--
Ola Nilsson
________________________________________
From: bitbake-devel-bounces@lists.openembedded.org <bitbake-devel-bounces@lists.openembedded.org> on behalf of Soemoe Aung <soemoe.a@gmail.com>
Sent: Tuesday, March 27, 2018 23:15
To: bitbake-devel@lists.openembedded.org
Subject: [bitbake-devel] [PULL] *** Fix build issue with html5lib in bitbake 1.26/1.28 ***
When I was running yocto-poky on the fido and jethro branches, I was getting build errors caused by the included html5lib in bitbake. It seems like a class is being called incorrectly there. I noticed the issue is resolved in the krogoth branch and the html5lib is indeed different there.
yocto-poky fido includes bitbake version 1.26 and jethro includes bitbake version 1.28. Looking at the bitbake source repo for these versions confirms that these files are the same. yocto-poky krogoth, which has the issue fixed, uses bitbake 1.30, which also has the issue fixed in the bitbake repo.
I originally created this patch in the yocto-poky contrib repo and was directed to send it to bitbake instead. Can someone here take a look at this and accept the changes into the 1.26 and 1.28 branches? Can you also send these changes upstream to the yocto-poky fido and jethro branches?
Let me know if you need any changes here, like creating this patch from the bitbake repo directly instead of indirectly through yocto-poky.
The following changes since commit ea6d21066a7cce2fef08ad66287170c5995bb1e2:
bitbake: bitbake-user-manual: Fixed porno hack for hello world example (2018-01-17 22:32:46 +0000)
are available in the Git repository at:
git://push.yoctoproject.org/poky-contrib saung/bitbake-html5lib
Soemoe Aung (2):
fix build error in included html5lib in bitbake
fix html5lib fix to be the same as in the krogoth branch
bitbake/lib/bs4/builder/_html5lib.py | 17 ++++++++++++-----
1 file changed, 12 insertions(+), 5 deletions(-)
--
2.17.0.rc0.231.g781580f067-goog
--
_______________________________________________
bitbake-devel mailing list
bitbake-devel@lists.openembedded.org
http://lists.openembedded.org/mailman/listinfo/bitbake-devel
next prev parent reply other threads:[~2018-03-28 9:41 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-26 20:51 [PULL] *** Fix build issue with html5lib in bitbake *** Soemoe Aung
2018-03-27 21:15 ` [PULL] *** Fix build issue with html5lib in bitbake 1.26/1.28 *** Soemoe Aung
2018-03-26 20:55 ` [PULL] *** Fix build issue with html5lib in bitbake *** Burton, Ross
2018-03-26 21:00 ` Soemoe Aung
2018-03-27 9:28 ` Burton, Ross
2018-03-30 15:49 ` Soemoe Aung
2018-03-26 21:02 ` Ruica Cristina
2018-03-28 9:41 ` Ola x Nilsson [this message]
2018-03-28 16:47 ` [PULL] *** Fix build issue with html5lib in bitbake 1.26/1.28 *** Soemoe Aung
2018-03-29 17:43 ` Peter Kjellerstedt
2018-03-30 15:46 ` Soemoe Aung
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=1522230112838.18244@axis.com \
--to=ola.x.nilsson@axis.com \
--cc=bitbake-devel@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 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.