[oe-commits] [openembedded-core] branch master-next updated (00a5c7c -> 4b31521)

git at git.openembedded.org git at git.openembedded.org
Mon Apr 10 22:33:20 UTC 2017


This is an automated email from the git hooks/post-receive script.

rpurdie pushed a change to branch master-next
in repository openembedded-core.

 discard 00a5c7c  scripts: Drop cleanup-workdir
 discard b20ed70  oeqa/selftest: Don't use cleanup-workdir
     add a668570  oeqa/selftest: Don't use cleanup-workdir
     add 809b23c  scripts: Drop cleanup-workdir
     add cd5e0a3  staging: Fix sysroot problem with populate_sysroot dependencies on do_fetch
     new b71687b  classutils.py: deterministic sorting
     new 1beccb5  libsolve: 0001-Add-fallback-fopencookie-implementation.patch fix attribution
     new 1e09a35  gnu-efi: copy header files for x32 build
     new 3572a54  openssl: fix the reference to native perl in ptests
     new 85a9dcf  package_manager.py: Split feed_archs for RPM repo URIs
     new 5681c62  buildhistory.bbclass: do not influence sstate of do_rootfs
     new 62de7ff  python2/3: Move config/Makefile from core package to dev package
     new 451bbd8  logrotate: replace fedorahosted.org SRC_URI with github.com source
     new b9e0f65  yocto-compat-layer: include bitbake-diffsigs output
     new 01c6e3e  yocto-compat-layer: also determine tune flags for each task
     new e863c87  musl: Upgrade to latest tip
     new 68d0dfc  buildhistory-diff: operate from buildhistory directory
     new f1b5664  classes/buildhistory: write out task signatures on every build
     new 019820c  buildhistory-diff: add option to compare task signature list
     new 9409503  buildhistory-diff: add option to compare actual signature differences
     new fa5c83f  classes/uninative: set SSTATEPOSTUNPACKFUNCS[vardepvalueexclude] properly
     new 4b31521  classes/buildhistory: save output file signatures for sstate tasks

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   (00a5c7c)
            \
             N -- N -- N   refs/heads/master-next (4b31521)

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 "omit" are not gone; other references still
refer to them.  Any revisions marked "discard" are gone forever.

The 17 revisions listed above as "new" are entirely new to this
repository and will be described in separate emails.  The revisions
listed as "add" were already present in the repository and have only
been added to this reference.


Summary of changes:
 meta/classes/buildhistory.bbclass                  |  50 +++++-
 meta/classes/staging.bbclass                       |   5 +
 meta/classes/uninative.bbclass                     |   2 +-
 meta/lib/oe/buildhistory_analysis.py               | 109 +++++++++++-
 meta/lib/oe/classutils.py                          |   2 +-
 meta/lib/oe/package_manager.py                     |   2 +-
 meta/lib/oe/sstatesig.py                           |  10 ++
 meta/recipes-bsp/gnu-efi/gnu-efi_3.0.5.bb          |   5 +
 meta/recipes-connectivity/openssl/openssl.inc      |   4 +
 meta/recipes-core/musl/musl_git.bb                 |   2 +-
 .../python/python-2.7-manifest.inc                 |   4 +-
 .../python/python-3.5-manifest.inc                 |   4 +-
 ...1-Add-fallback-fopencookie-implementation.patch | 186 +++++++++++++++++----
 meta/recipes-extended/logrotate/logrotate_3.9.1.bb |  19 ++-
 scripts/buildhistory-diff                          |  13 +-
 scripts/lib/compatlayer/__init__.py                |   9 +-
 scripts/lib/compatlayer/cases/common.py            |  14 +-
 scripts/yocto-compat-layer.py                      |   2 +-
 18 files changed, 384 insertions(+), 58 deletions(-)

-- 
To stop receiving notification emails like this one, please contact
the administrator of this repository.


More information about the Openembedded-commits mailing list