Aah. There was a very weird bug where py3 was dropping .pyc files around that was upsetting py2. The solution is not pretty and it only impacts people who downgrade in a git repo.
A fresh clone should solve it, or do git clean -Xn to list files that git is ignoring and can be deleted (just -X will delete) them. I suspect they'll be a load of .pyc files in meta/lib/oe/ and Py2 can't import them (because this is another instance of where the py2/py3 migration was a disaster). Ross On 18 September 2017 at 02:16, Paul D. DeRocco <pdero...@ix.netcom.com> wrote: > I thought this was a morty->pyro upgrade issue, but trying morty again, on > a freshly installed Ubuntu system, didn't change anything. In > meta/classes/patch.bbclass, patch_do_patch() is barfing when it tries to > import oe.patch. I carefully reinstalled poky, meta-intel, and > meta-openembedded from git, and I get this error, and a bunch more related > to the oe package. The package is there, in poky/meta/lib/oe, so why isn't > it being found? Am I supposed to have a non-empty PYTHONPATH somehow? What > kind of misconfiguration could cause this? This worked on morty before I > had to do a fresh Ubuntu install, so I doubt it's anything in my own > simple layers. > > -- > > Ciao, Paul D. DeRocco > Paul mailto:pdero...@ix.netcom.com > > -- > _______________________________________________ > yocto mailing list > yocto@yoctoproject.org > https://lists.yoctoproject.org/listinfo/yocto >
-- _______________________________________________ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
