[oe-commits] [openembedded-core] branch master-next updated (9eb795c -> 62da6ad)
git at git.openembedded.org
git at git.openembedded.org
Thu Nov 22 23:44:13 UTC 2018
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 9eb795c dnf: update to 4.0.9
discard 59cdb60 libdnf: update to 0.22.3
discard 7dfee3b lighttpd: update to 1.4.51
discard bfa7aa2 libwebp: update to 1.0.1
discard f9ce904 sysprof: update to 3.30.2
discard fa3a6ea psmisc: update to 23.2
discard e53523e webkitgtk: update to 2.22.4
discard c7792e5 vala: update to 0.42.3
discard 8308656 btrfs-tools: update to 4.19
new 0bbd83a vala: update to 0.42.3
new a0d2154 webkitgtk: update to 2.22.4
new d6a3916 psmisc: update to 23.2
new 8fd2239 sysprof: update to 3.30.2
new 4866b10 libwebp: update to 1.0.1
new f7a62f4 lighttpd: update to 1.4.51
new c913a32 socat: fix LICENSE
new da9e7ca boost-context: Reproducibility: Set .file section for all *_elf_gas.S files
new 83a4a70 reproducible: Refactor: Break out fixed_source_date_epoch() function
new 9f2cea2 reproducible: Don't look for youngest file when no source tarball
new f6aa993 arc: Disable LTTng
new 3184500 dmidecode: fix the Upstream-Status in a custom patch
new 62da6ad u-boot: Add mkenvimage tool
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 (9eb795c)
\
N -- N -- N refs/heads/master-next (62da6ad)
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 13 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/image_types.bbclass | 2 +-
meta/classes/kernel-fitimage.bbclass | 2 +-
meta/classes/kernel-uimage.bbclass | 2 +-
meta/classes/reproducible_build.bbclass | 22 +-
meta/conf/distro/include/distro_alias.inc | 2 +-
meta/conf/distro/include/maintainers.inc | 2 +-
...-mkimage_2018.07.bb => u-boot-tools_2018.07.bb} | 27 ++-
meta/recipes-connectivity/socat/socat_1.7.3.2.bb | 2 +-
.../packagegroup-core-tools-profile.bb | 3 +
.../{btrfs-tools_4.19.bb => btrfs-tools_4.17.1.bb} | 2 +-
...1-Committing-changes-from-do_unpack_extra.patch | 2 +-
.../dnf/{dnf_4.0.9.bb => dnf_4.0.4.bb} | 2 +-
meta/recipes-devtools/gdb/gdb-common.inc | 1 +
.../libdnf/{libdnf_0.22.3.bb => libdnf_0.22.0.bb} | 2 +-
meta/recipes-kernel/lttng/lttng-tools_2.10.5.bb | 1 +
...e_x86_64_sysv_elf_gas.S-set-.file-section.patch | 48 ----
...ucibility-add-file-directive-to-assembler.patch | 243 +++++++++++++++++++++
meta/recipes-support/boost/boost_1.68.0.bb | 2 +-
18 files changed, 297 insertions(+), 70 deletions(-)
rename meta/recipes-bsp/u-boot/{u-boot-mkimage_2018.07.bb => u-boot-tools_2018.07.bb} (55%)
rename meta/recipes-devtools/btrfs-tools/{btrfs-tools_4.19.bb => btrfs-tools_4.17.1.bb} (96%)
rename meta/recipes-devtools/dnf/{dnf_4.0.9.bb => dnf_4.0.4.bb} (98%)
rename meta/recipes-devtools/libdnf/{libdnf_0.22.3.bb => libdnf_0.22.0.bb} (95%)
delete mode 100644 meta/recipes-support/boost/boost/0001-make_x86_64_sysv_elf_gas.S-set-.file-section.patch
create mode 100644 meta/recipes-support/boost/boost/reproducibility-add-file-directive-to-assembler.patch
--
To stop receiving notification emails like this one, please contact
the administrator of this repository.
More information about the Openembedded-commits
mailing list