On 1/16/21 9:44 AM, Martin Jansa wrote: > Aren't the missing spaces in appends fixes also needed for meta-oe > recipes?
> > I think at least top 5 commits from: > https://git.openembedded.org/meta-openembedded/log/?qt=grep&q=space.*append > were also follow-up from these changes in oe-core. > Do you mean something beyond the meta-openembedded commits mentioned near the bottom of the email? I need clarity so I can open an issue in gitlab for tracking purposes as I am sure I will forget this -armin > On Thu, Jan 14, 2021 at 6:50 PM Peter Kjellerstedt > <peter.kjellerst...@axis.com <mailto:peter.kjellerst...@axis.com>> wrote: > > [ Cross-posting since these changes affect all of bitbake, > openembedded-core > and meta-openembedded and need to be made (at least somewhat) in > sync. ] > > Can the solution for _PYTHON_SYSCONFIGDATA_NAME please be > backported to > Gatesgarth and Dunfell? We are seeing problems for developers who > have > updated the python3 version on their hosts when they try to do > devtool > modify on recipes that inherit python3native. The following relevant > changes should cherry-pick cleanly to the respective repositories for > both gatesgarth and dunfell: > > openembedded-core: > 5a118d4e python3: split python target configuration into own class > dadf001c python3-pycairo: use python3targetconfig > 9c8f6660 distutils3-base.bbclass: use python3targetconfig > d3a81dd0 meta: drop _PYTHON_SYSCONFIGDATA_NAME hacks > 38ecb83c gpgme: use python3targetconfig > c99bb790 python3targetconfig.bbclass: Make py3 dep and tasks only > for target recipes > > bitbake: > 47b64cfa lib/bb/fetch2/__init__.py: drop > _PYTHON_SYSCONFIGDATA_NAME unsetting > > meta-openembedded: > a06cdf5a gedit: Inherit python3targetconfig > 59f817bb openipmi: Inherit python3targetconfig > be7d2286 libplist: Inherit python3targetconfig > c499aaee postgresql: Inherit python3targetconfig > > I guess there may be some controversy regarding whether these > changes should > be backported to the stable branches since they modify what > python3native > does and may require existing recipes to be modified to inherit > the new > python3targetconfig class. However, I believe that having devtool > modify > fail on random recipes without an easy solution for the user is > much worse > than having to update a recipe or two once due to a build failure > after > upgrading to a new version of OE-Core (in my book that is pretty > normal and > something I always have to do anyway when we update OE-Core). And > based on > the number of recipes in openembedded-core and meta-openembedded > that needed > to be updated (2+4), I do not expect there to be many other > recipes in the > first place that actually need to be updated. > > //Peter > > > >
-=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#88794): https://lists.openembedded.org/g/openembedded-devel/message/88794 Mute This Topic: https://lists.openembedded.org/mt/79732587/21656 Group Owner: openembedded-devel+ow...@lists.openembedded.org Unsubscribe: https://lists.openembedded.org/g/openembedded-devel/unsub [arch...@mail-archive.com] -=-=-=-=-=-=-=-=-=-=-=-
