Please note that you should *at least* also build an image and an SDK
with the updated dnf. And run testimage package management tests, and
oe-selftest. And upgrade the rest of the dnf stack, particularly
libdnf, as there might be subtle breakage otherwise.
I'll get to this but not right now :)
Hey Tim,
Yup, it should be just another one line patch, just saying that it needs
to be provided so we don't break functionality of other parts of the
build system, as you say, we expect breakages with the upgrade, but we
need a working dnf to even be able to test what may have broken.
FWIW, the dnf upgrade appears to be trivial (I did not rebase python3 3.7.0
patches, but it probably won’t change much):
http://git.openembedded.org/openembedded-core-contrib/commit/?h=timo/python37=94d4bba43097ec22f120f4327e5d13a52c1724fd
NOTE: I used a hammer and overwrote Alex Kanavin’s
Hello Jens,
It literally seems that you didn't even read the email, I am not asking
whether or not it builds correctly for you, it clearly says that the
fact that something builds correctly, doesn't necessarily means it runs
properly, and it also says thanks because it contains some of the
Hi Alejandro,
on my system it builds without any problem. And I run the create_manifest task.
Cheers,
Jens
Am Mi., 19. Sep. 2018 um 21:19 Uhr schrieb Alejandro Hernandez
:
>
> Hello Jens,
>
> I appreciate the effort of submitting a v4, this version has (mostly
> all) the required manifest
Update python3 to recent 3.7.0 release.
Details about new features and bug-fixes can be taken from
* https://docs.python.org/3/whatsnew/3.7.html
* https://docs.python.org/3/whatsnew/3.6.html
Remove patches when they were fixed upstream and rebase the
remaining ones. If necessary, the patches are
