All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Burton, Ross" <ross.burton@intel.com>
To: Jens Rehsack <sno@netbsd.org>
Cc: "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 17:38:40 +0100	[thread overview]
Message-ID: <CAJTo0LYHhteuX2y0cvW9DWOw1ey31EpWDB1Q8mHHCN2qaxUung@mail.gmail.com> (raw)
In-Reply-To: <6FC71ED0-1800-46FD-9A0D-1664CE908975@netbsd.org>

One thing to be aware of is that I've been fixing up Python's PGO
support and there's a slew of patches in master-next and more just
posted that this needs to be rebased on top of.  Good news is that my
patches remove two of the patches we've been carrying!

Ross

On 10 September 2018 at 17:36, Jens Rehsack <sno@netbsd.org> wrote:
>
>
> Am 10.09.2018 um 11:35 schrieb Alexander Kanavin <alex.kanavin@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.
>
>
> If I can prepare something for you - drop me a note.
> Otherwise - the perl-5.28 update ("." in @INC, regex buffer overflow, ...)
> is also
> awaiting some progress (I can keep "myself" busy).
>
> There's already enough disruption to deal with (postinsts errors,
> openssl 1.1, both caused by me :)
>
>
> You know, corner, ash, ... things happen. But there is progress! Great!
>
> Good that we got all the way to do_rootfs though with 3.7.
>
>
> Yeah, but than came postinst (coreutils :P) :D
>
> Cheers
>
> 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
>
>
> --
> Jens Rehsack - rehsack@gmail.com
>
>
> --
> _______________________________________________
> Openembedded-core mailing list
> Openembedded-core@lists.openembedded.org
> http://lists.openembedded.org/mailman/listinfo/openembedded-core
>


  reply	other threads:[~2018-09-10 16:38 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
2018-09-10 16:36       ` Jens Rehsack
2018-09-10 16:38         ` Burton, Ross [this message]
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=CAJTo0LYHhteuX2y0cvW9DWOw1ey31EpWDB1Q8mHHCN2qaxUung@mail.gmail.com \
    --to=ross.burton@intel.com \
    --cc=igork@miltenyibiotec.de \
    --cc=openembedded-core@lists.openembedded.org \
    --cc=sno@netbsd.org \
    --cc=svenha@external.miltenyibiotec.de \
    /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.