From: Alejandro Hernandez <alejandro.hernandez@linux.intel.com>
To: Richard Purdie <richard.purdie@linuxfoundation.org>
Cc: OE-core <openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH 1/1] python3: Upgrade from 3.4.2 to 3.4.3
Date: Thu, 14 May 2015 10:42:44 -0500 [thread overview]
Message-ID: <5554C274.5050202@linux.intel.com> (raw)
In-Reply-To: <1431600879.30971.211.camel@linuxfoundation.org>
On 14/05/15 05:54, Richard Purdie wrote:
> On Tue, 2015-05-12 at 17:35 -0500, Alejandro Hernandez wrote:
>> On 12/05/15 17:30, Martin Jansa wrote:
>>> On Tue, May 12, 2015 at 03:09:50PM +0000, Alejandro Hernandez wrote:
>>>> Modifies:
>>>> python3-native_3.4.2.bb -> python3-native_3.4.3.bb: Updates checksums, LICENSE did not change,
>>>> dates were updated.
>>>> python3_3.4.2.bb -> python3_3.4.3.bb: Updates checksums, LICENSE did not change,
>>>> dates were updated.
>>>> generate-manifest-3.4.py: fixes asyncio and net-tools.
>>>> python-3.4-manifest.inc: fixes asyncio and net-tools.
>>>> This upgrade contains a fix for CVE-2014-9365.
>>> There is still that textrel issue I've reported earlier:
>>> python3-3.4.2: ELF binary '/home/jenkins/oe/world/shr-core/tmp-glibc/work/i586-oe-linux/python3/3.4.2-r1.0/packages-split/python3-audio/usr/lib/python3.4/lib-dynload/ossaudiodev.cpython-34m.so' has relocations in .text [textrel]
>> [...]
>>> IIRC you've already sent some patch to fix it, do you know what's the status of it, if it was applied or not (why?)?
>> Oh nice, I had not seen your patch, I was aware the issue still existed
>> but I upgraded first, mainly to include the CVE fix and I was just
>> gonna start to work on that issue, no I don't know what the status of it
>> is, RP was probably waiting for the Autobuilder issues to be fixed, but
>> now they are, so it'll probably be applied soon.
> I think there is some misunderstanding here. I don't think there is a
> patch to fix the textrel issues as yet. If there is, someone needs to
> point me at it as I can't find it.
>
> Cheers,
>
> Richard
Oh, my bad, apparently I read that wrong, I have NOT sent any patch to
fix the textrel issues yet.
prev parent reply other threads:[~2015-05-14 15:43 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <cover.1431443215.git.alejandro.hernandez@linux.intel.com>
2015-05-12 15:09 ` [PATCH 1/1] python3: Upgrade from 3.4.2 to 3.4.3 Alejandro Hernandez
2015-05-12 22:30 ` Martin Jansa
2015-05-12 22:35 ` Alejandro Hernandez
2015-05-14 10:54 ` Richard Purdie
2015-05-14 15:42 ` Alejandro Hernandez [this message]
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=5554C274.5050202@linux.intel.com \
--to=alejandro.hernandez@linux.intel.com \
--cc=openembedded-core@lists.openembedded.org \
--cc=richard.purdie@linuxfoundation.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.