[oe-commits] [bitbake] branch python3 updated (8f6ec3e -> 48a2852)
git at git.openembedded.org
git at git.openembedded.org
Tue May 24 21:34:53 UTC 2016
rpurdie pushed a change to branch python3
in repository bitbake.
discards 8f6ec3e xmlrpc: add parameter use_builtin_types
discards 4579f07 toaster: use knotty when working with bitbake server
discards 4f0fe78 toaster: fix migrations
discards 90414a6 toaster: moved import bb.server.xmlrpc
discards 90fd249 toaster: read timezone files in binary mode
discards e22c887 toaster: use re.sub() instead of translate()
discards f1f6219 toaster: replace map with list comprehensions
discards 5783596 toaster: use items and range instead of old APIs
discards 4df7863 toaster: use decode('utf-8') for binary data
discards 08d14a2 toaster: modified list of dependencies
discards fc6fb69 toaster: fix local imports
discards 0f06eac toaster: fix imports to work for python 3
discards 90d1c6e toaster: get rid of using reduce
discards f140617 toaster: use force_text instead of force_bytes
discards f6b291f data/event/siggen: Fix various exceptions [FIXME]
discards e2dd378 google/image-writer: Drop since bitrotting and no longer used
discards 53a5657 image-writer/goggle: Disable pygtkcompat problems
discards d9f88da lib/bb: Set required python 3 version to 3.4.0
discards 774004f data_smart: Simplify ExpansionError exception
discards 8cc7a52 bitbake: Convert to python 3 megacommit This needs breaking up into smaller changes.
discards 85d94b7 bitbake: Drop futures usage since we're python 3
discards e78ef7a bitbake/pyinotify.py: Upgrade to py3 version
discards b18b9bc bitbake/bs4: Upgrade 4.3.2 -> 4.4.1 (python 3 version)
adds d830dcc classes/base.bbclass: Fix missing getVarFlag parameter
new 2f4b98a bitbake/bs4: Upgrade 4.3.2 -> 4.4.1 (python 3 version)
new 5ee80d7 bitbake/pyinotify.py: Upgrade to py3 version
new bf25f05 bitbake: Drop futures usage since we're python 3
new c4525ba bitbake: Convert to python 3 megacommit This needs breaking up into smaller changes.
new f4b130b data_smart: Simplify ExpansionError exception
new b506f3d lib/bb: Set required python 3 version to 3.4.0
new 9546c41 image-writer/goggle: Disable pygtkcompat problems
new 7b54437 google/image-writer: Drop since bitrotting and no longer used
new c4cd03e data/event/siggen: Fix various exceptions [FIXME]
new f9c5880 toaster: use force_text instead of force_bytes
new f8091e4 toaster: get rid of using reduce
new b96d0f7 toaster: fix imports to work for python 3
new 7675f16 toaster: fix local imports
new 46d50bd toaster: modified list of dependencies
new 97821ed toaster: use decode('utf-8') for binary data
new 336067f toaster: use items and range instead of old APIs
new fa80241 toaster: replace map with list comprehensions
new b64a9a8 toaster: use re.sub() instead of translate()
new 5f41f83 toaster: read timezone files in binary mode
new 86984d6 toaster: moved import bb.server.xmlrpc
new af51483 toaster: fix migrations
new 2150301 toaster: use knotty when working with bitbake server
new 48a2852 xmlrpc: add parameter use_builtin_types
This update added new revisions after undoing existing revisions.
That is to say, some revisions that were in the old version of the
branch are not in the new version. This situation occurs
when a user --force pushes a change and generates a repository
containing something like this:
* -- * -- B -- O -- O -- O (8f6ec3e)
\
N -- N -- N refs/heads/python3 (48a2852)
You should already have received notification emails for all of the O
revisions, and so the following emails describe only the N revisions
from the common base, B.
Any revisions marked "omits" are not gone; other references still
refer to them. Any revisions marked "discards" are gone forever.
The 23 revisions listed above as "new" are entirely new to this
repository and will be described in separate emails. The revisions
listed as "adds" were already present in the repository and have only
been added to this reference.
Summary of changes:
classes/base.bbclass | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
--
To stop receiving notification emails like this one, please contact
the administrator of this repository.
More information about the Openembedded-commits
mailing list