All of lore.kernel.org
 help / color / mirror / Atom feed
From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: "Maxin B. John" <maxin.john@intel.com>,
	bitbake-devel@lists.openembedded.org
Subject: Re: [RFC][PATCH] bitbake: fetch2: fix warning while switching from master to krogoth
Date: Fri, 29 Jul 2016 12:56:29 +0100	[thread overview]
Message-ID: <1469793389.9142.59.camel@linuxfoundation.org> (raw)
In-Reply-To: <1469780615-1657-1-git-send-email-maxin.john@intel.com>

On Fri, 2016-07-29 at 11:23 +0300, Maxin B. John wrote:
> While switching from master to krogoth build with a common download
> directory,
> got a large number of warnings like the one listed below:
> 
> WARNING: freetype-2.6.3-r0 do_fetch: Couldn't load checksums from
> donestamp /home/maxin/downloads/freetype-2.6.3.tar.bz2.done:
> ValueError
> (msg: unsupported pickle protocol: 4)
> 
> These warnings are caused by the difference in pickle module
> implementation in python3(master) and python2(krogoth). Python2
> supports
> 3 different protocols (0, 1, 2) and pickle.HIGHEST_PROTOCOL is 2
> where as
> Python3 supports 5 different protocols (0, 1, 2, 3, 4) and
> pickle.HIGHEST_PROTOCOL is obviously 4.
> 
> My suggestion is to use 2 since it is backward compatible with
> python2
> (all the supported distros for krogoth provides python2 which
> supports
> pickle protocol version 2)

This looks good to me, well spotted. I've merged it since the
autobuilder is likely spending a lot of time churning sources around at
the moment due to this.

Ideally we'd use a better data format in these files so I'd welcome
other improvements but this fixes the immediate problem.

Cheers,

Richard


      reply	other threads:[~2016-07-29 11:56 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-07-29  8:23 [RFC][PATCH] bitbake: fetch2: fix warning while switching from master to krogoth Maxin B. John
2016-07-29 11:56 ` Richard Purdie [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=1469793389.9142.59.camel@linuxfoundation.org \
    --to=richard.purdie@linuxfoundation.org \
    --cc=bitbake-devel@lists.openembedded.org \
    --cc=maxin.john@intel.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.