From: Alejandro Hernandez <alejandro.hernandez@linux.intel.com>
To: Martin Jansa <martin.jansa@gmail.com>
Cc: openembedded-core@lists.openembedded.org
Subject: Re: [PATCH 1/1] python3: Upgrade from 3.3.3 to 3.4.2
Date: Mon, 13 Apr 2015 16:24:30 -0500 [thread overview]
Message-ID: <552C340E.4030804@linux.intel.com> (raw)
In-Reply-To: <20150413184018.GL2330@jama>
On 13/04/15 13:40, Martin Jansa wrote:
> On Fri, Feb 27, 2015 at 06:30:52PM -0600, Alejandro Hernandez wrote:
>> Modifies:
>> python3-native_3.3.3.bb -> python3-native_3.4.2.bb: Updates checksums, version, patches
>> and SRC_URIs to use xz format, LICENSE did not change, dates were updated, adds fix for
>> ctypes/libffi needed for pip <- required since Python 3.4 (see PEP #453).
>> python3_3.3.3.bb -> python3_3.4.2.bb: Updates checksums, version, patches and SRC_URIs
>> to use xz format, adds fix for ctypes/libffi, fixes oe_multilib_header() call,
>> adds python3-core as RDEPENDS to python3-misc to avoid QA issue.
>> generate-manifest-3.4.py - > generate-manifest-3.4.py: fixes reprlib,
>> adds _sitebuiltins and _collections_abc <- formerly part of collections, separated since 3.4
>> python-3.3-manifest.inc -> python-3.4-manifest.inc
>>
>> Rebases:
>> 12-distutils-prefix-is-inside-staging-area.patch
>> python-3.3-multilib.patch
>> 04-default-is-optimized.patch
>> avoid-ncursesw-include-path.patch
>>
>> Deletes (fixed upstream):
>> fix-ast.h-dependency.patch
>> python3-fix-build-error-with-Readline-6.3.patch
>> 06-ctypes-libffi-fix-configure.patch
>> remove_sqlite_rpath.patch
> There is a lot of textrel QA warnings in 3.3.3 (you can see them e.g. in
> http://lists.openembedded.org/pipermail/openembedded-core/2015-March/102948.html
> ), is this upgrade fixing them?
>
>> [YOCTO #6857]
>>
>> Signed-off-by: Alejandro Hernandez <alejandro.hernandez@linux.intel.com>
>>
I don't remember there being any warnings when I first did the upgrade,
but I just checked and now they are being shown, something must've
changed , anyway they are still there for 3.4, we can still upgrade and
I'll dig into this later
next prev parent reply other threads:[~2015-04-13 21:24 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <cover.1425076707.git.alejandro.hernandez@linux.intel.com>
2015-02-28 0:30 ` [PATCH 1/1] python3: Upgrade from 3.3.3 to 3.4.2 Alejandro Hernandez
2015-04-13 18:40 ` Martin Jansa
2015-04-13 21:24 ` Alejandro Hernandez [this message]
2015-04-22 13:52 ` Martin Jansa
2015-04-09 20:41 [PATCH 0/1] python3: Upgrade from 3.3.3 to 3.4.2 rebase Alejandro Hernandez
2015-04-09 20:41 ` [PATCH 1/1] python3: Upgrade from 3.3.3 to 3.4.2 Alejandro Hernandez
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=552C340E.4030804@linux.intel.com \
--to=alejandro.hernandez@linux.intel.com \
--cc=martin.jansa@gmail.com \
--cc=openembedded-core@lists.openembedded.org \
/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.