[yocto-security] [OE-core CVE] branch master-next updated. uninative-2.2-936-gf1bec34
cve-notice at lists.openembedded.org
cve-notice at lists.openembedded.org
Sat Oct 20 14:41:27 PDT 2018
This is an automated email from the git hooks/post-receive script. It was
generated because a ref change was pushed to the repository containing
the project "".
The branch, master-next has been updated
discards e0d95880c1704c99a01cf43a28c05070c16a9143 (commit)
discards a717cd485241fbcf1c8159a3a483beb4da2ff1e5 (commit)
discards 9f50b9a96e5ca64f32e20ad5c7c8decd9cc2e3b6 (commit)
discards 2a0199c11e026b883ceed2b341a55c44f751631b (commit)
discards d38597cf7615cef01d71d293783864ffb5e0ed1c (commit)
discards 5f44817b8ec9ce164a05d8179c80aaa24cb8bb77 (commit)
discards 9c73d03a01015cc726d043cd147a6c000e4ae5aa (commit)
discards b1f66b1cc67d22fd3f6ffc9c1143271b7c493016 (commit)
discards 51971d6a0e6efe6dbc88073cb967e22a82877a5d (commit)
discards d09c1b51c687ff3ff01724aa10ebd2a9279b4b95 (commit)
discards 31e80bc2558c6d996ae2ba4e096bca335af60071 (commit)
discards cde1682823483c077e12f4b1f3a6a8d40d9199bc (commit)
discards 0534539c3127547f6aa54db4e41470d5d4a6fec5 (commit)
discards 04137b42a83fa8517f74ac0c44d387caf6e1fdfb (commit)
discards 82de44035f6c24cfd0d4cb9b5bedd5299c61ae3e (commit)
discards 040754fa27ee77809ef8851437ac6909c1ec2d79 (commit)
discards f9d4fec76ce08a669020fda91f953c196062f253 (commit)
discards 058681efd06869e8eb44a24d233b75886050a730 (commit)
discards a404bdcacf7dc8c9b1e8f0a8dd7efdbd3aab87f4 (commit)
discards 4f10f63a6206f35e3e78c51980a19c888e156751 (commit)
via f1bec348f76db675d3c69c7b842d2bda0b095c36 (commit)
via fe5988c72ff31729b5d990b04faa24b138841025 (commit)
via d48c8148eae41e613448d78c26516538244cd9c9 (commit)
via d3395418758ed414eee3e95e13d2d8bc5dca88cc (commit)
via 37841ec56d7756ec9ee00e2a2005681b220f6f5d (commit)
via b4976f3cf8cd028f165100b67867adb862da4d7f (commit)
via e028b4457781f60d8491a99a23011996fa913013 (commit)
via 7831d2d3a1069b9d3a8d32e41f0a292e1add56ba (commit)
via 2036137151929b541293154ff529475071cd92b0 (commit)
via 95a921959d340f74b5604df57737c1eeaad0023e (commit)
via e1c6442872c9361b6b61a83adcce9cade2f2ecd2 (commit)
via 52fbf46a32f03266e31811fde7d4466e7ef85fc8 (commit)
via 1cf3aee0ba0fb0c2e8b82f403384a1928a9b03f4 (commit)
via 68e51756f67499081c3c53cff6c5c1efdf4b60f0 (commit)
via c0343f1035af98cb451eea0de94c16fe89ffdf48 (commit)
via 7017cece7f767f0ec9972b6f4e62ca4006c557ad (commit)
via c1a98853f90857a735bacf75ccbdd6f2f7094ccf (commit)
via b7b476efee8c959a0227905e40bd9b5ef493632d (commit)
via 33c8dc08c9b160a0bb1d71d8b421a99de6e6eeee (commit)
via d819e7fa76e2b732aa7c33ab0e9a834781090824 (commit)
This update added new revisions after undoing existing revisions. That is
to say, the old revision is not a strict subset of the new revision. This
situation occurs when you --force push a change and generate a repository
containing something like this:
* -- * -- B -- O -- O -- O (e0d95880c1704c99a01cf43a28c05070c16a9143)
\
N -- N -- N (f1bec348f76db675d3c69c7b842d2bda0b095c36)
When this happens we assume that you've already had alert emails for all
of the O revisions, and so we here report only the revisions in the N
branch from the common base, B.
Those revisions listed above that are new to this repository have
not appeared on any other notification email; so we list those
revisions in full, below.
- Log -----------------------------------------------------------------
commit f1bec348f76db675d3c69c7b842d2bda0b095c36
Author: Richard Purdie <richard.purdie at linuxfoundation.org>
Date: Sat Oct 20 13:44:49 2018 +0100
Revert "systemd: Test revert of patch removal"
This reverts commit bf5c2021fb9e2323471dc79a650cb36bd1db95f3.
commit fe5988c72ff31729b5d990b04faa24b138841025
Author: Richard Purdie <richard.purdie at linuxfoundation.org>
Date: Sat Oct 20 10:59:40 2018 +0100
systemd: Test revert of patch removal
Signed-off-by: Richard Purdie <richard.purdie at linuxfoundation.org>
commit d48c8148eae41e613448d78c26516538244cd9c9
Author: Khem Raj <raj.khem at gmail.com>
Date: Thu Oct 18 18:31:48 2018 -0700
tcmode-default: Drop pinning go to 1.9
This ensures that we default to latest go recipes
1.9 is not supported anymore
Signed-off-by: Khem Raj <raj.khem at gmail.com>
Signed-off-by: Richard Purdie <richard.purdie at linuxfoundation.org>
commit d3395418758ed414eee3e95e13d2d8bc5dca88cc
Author: Mark Hatle <mark.hatle at windriver.com>
Date: Wed Oct 17 12:43:23 2018 -0400
systemd: Remove items that made this machine (qemu) specific
Create a new systemd-conf recipe to contain the specific system/machine
configuration items. This new package is now machine specific.
Without doing this trying to create a single system with multiple BSPs,
one of which was qemu based, would result in the systemd -and- everything that
dependend upon systemd to have their hash changed. The hash changing means
lots of rebuilds, but worse if it's a package based system each different
machine ends with a new PR value and a newly generated package.
Signed-off-by: Mark Hatle <mark.hatle at windriver.com>
Signed-off-by: Richard Purdie <richard.purdie at linuxfoundation.org>
-----------------------------------------------------------------------
Summary of changes:
hooks/post-receive
--
More information about the yocto-security
mailing list