Openembedded Core Discussions
 help / color / mirror / Atom feed
From: Saul Wold <sgw@linux.intel.com>
To: Artur Wroblewski <wrobell@pld-linux.org>,
	 openembedded-core@lists.openembedded.org
Subject: Re: python 3.4.2 patch
Date: Tue, 04 Nov 2014 07:56:35 -0800	[thread overview]
Message-ID: <5458F733.2010600@linux.intel.com> (raw)
In-Reply-To: <20141103235157.GC19739@greymatter>

On 11/03/2014 03:51 PM, Artur Wroblewski wrote:
> Hi,
>
> As advised at
>
>      https://bugzilla.yoctoproject.org/show_bug.cgi?id=6857
>
> I am attaching a patch to replace Python 3.3.x with Python 3.4.2. This also
> fixes issue with missing basic Python 3.x modules, see
>
>      https://bugzilla.yoctoproject.org/show_bug.cgi?id=6831
>
> Build tested with git master:
>
>      $ tar tvjf tmp/deploy/images/qemux86/core-image-minimal-qemux86.tar.bz2 | grep python3.4 | wc -l
>      2028
>
> Regards,
>
> w
>
>
>
Thanks for working up the patch.

Your patch needs a Signed-off-by: tag and alittle more explaination in 
the commit message as to what you did (removed patches, rebased patches, 
...), It's also important to note why the LIC_FILES_CHKSUM changed, it 
might be as simple as version or date changes, but we need to flag them 
in case the actual License changed.

Would it make sense to use a PYTHON_MAJMIN in the manifest generator 
instead of hardcoding the python version? This would allow for the 
manifest.inc changeset to be much smaller.

Sau!




  reply	other threads:[~2014-11-04 15:56 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-11-03 23:51 python 3.4.2 patch Artur Wroblewski
2014-11-04 15:56 ` Saul Wold [this message]
2014-11-05 21:57   ` Artur Wroblewski

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=5458F733.2010600@linux.intel.com \
    --to=sgw@linux.intel.com \
    --cc=openembedded-core@lists.openembedded.org \
    --cc=wrobell@pld-linux.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox