All of lore.kernel.org
 help / color / mirror / Atom feed
From: Alexander Kanavin <alex.kanavin@gmail.com>
To: Tim Orling <ticotimo@gmail.com>
Cc: "Jens Rehsack" <sno@netbsd.org>,
	"Sven Hädrich" <svenha@external.miltenyibiotec.de>,
	"Igor Kreps" <igork@miltenyibiotec.de>,
	openembedded-core <openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH v2] python3{,-native}: update to 3.7.0
Date: Mon, 10 Sep 2018 11:35:59 +0200	[thread overview]
Message-ID: <CANNYZj8dyfuOnHxqE7V5n3sz=3XjqPS98E2n=t2uJbPkvczKyw@mail.gmail.com> (raw)
In-Reply-To: <CANx9H-BfgTfmNs+oGxC-Cm=Tp464=fpZnMb17vbTWsRg2LTZdg@mail.gmail.com>

Large parts of dnf and friends have been rewritten in c++. I have not
yet updated and reviewed that, that will happen in the next cycle.
There's already enough disruption to deal with (postinsts errors,
openssl 1.1, both caused by me :)

Good that we got all the way to do_rootfs though with 3.7.

Alex

2018-09-10 0:38 GMT+02:00 Tim Orling <ticotimo@gmail.com>:
> I did not review the patches closely, but I did try to build
> core-image-full-cmdline with the tip of poky and these patches applied.
> Everything was fine until do_rootfs... I've attached the log.
>
> Essentially, there are some bits of dnf and so on which are not ready for
> Python 3.7. We have dnf version 2.7.5, but the latest upstream release is
> 3.4.0 (with a 3.5.0 just 3 days ago). Not sure yet if that would have
> helped.
>
> --
> _______________________________________________
> Openembedded-core mailing list
> Openembedded-core@lists.openembedded.org
> http://lists.openembedded.org/mailman/listinfo/openembedded-core
>


  reply	other threads:[~2018-09-10  9:35 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-09-07 14:55 [PATCH v2] python3{,-native}: update to 3.7.0 Jens Rehsack
2018-09-07 14:59 ` Jens Rehsack
2018-09-09 22:38   ` Tim Orling
2018-09-10  9:35     ` Alexander Kanavin [this message]
2018-09-10 16:36       ` Jens Rehsack
2018-09-10 16:38         ` Burton, Ross
2018-09-10 20:17           ` Alejandro Enedino Hernandez Samaniego
2018-09-10 21:05             ` Jens Rehsack
2018-09-10 21:33               ` Alejandro Enedino Hernandez Samaniego
2018-09-11  6:58                 ` Jens Rehsack
2018-09-11 18:56                   ` Alejandro Enedino Hernandez Samaniego
2018-09-12 11:53                     ` Jens Rehsack
2018-09-12 21:02                       ` Alejandro Hernandez
2018-09-17 19:00                         ` Jens Rehsack
2018-09-19  6:11                           ` Alejandro Hernandez
2018-09-11  7:09           ` Jens Rehsack
2018-09-10 16:44         ` Alexander Kanavin
2018-09-10 16:42       ` Jens Rehsack
2018-09-10 18:10       ` Jens Rehsack
2018-09-07 15:03 ` ✗ patchtest: failure for python3{,-native}: update to 3.7.0 (rev2) Patchwork

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='CANNYZj8dyfuOnHxqE7V5n3sz=3XjqPS98E2n=t2uJbPkvczKyw@mail.gmail.com' \
    --to=alex.kanavin@gmail.com \
    --cc=igork@miltenyibiotec.de \
    --cc=openembedded-core@lists.openembedded.org \
    --cc=sno@netbsd.org \
    --cc=svenha@external.miltenyibiotec.de \
    --cc=ticotimo@gmail.com \
    /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.