From: Martin Jansa <martin.jansa@gmail.com>
To: Armin Kuster <akuster808@gmail.com>
Cc: bitbake-devel <bitbake-devel@lists.openembedded.org>
Subject: Re: [PATCH 00/12] Sumo pull request
Date: Sat, 23 Mar 2019 09:32:09 +0100 [thread overview]
Message-ID: <CA+chaQcb_6aOd7Xv6D-yNtMobrU81MBSvw=0uvqjMr1-HzOS3w@mail.gmail.com> (raw)
In-Reply-To: <cover.1553306877.git.akuster808@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 4070 bytes --]
Hi,
is there a reason for not including
https://patchwork.openembedded.org/patch/159465/
?
It says sumo-next on patchwork, but I don't know which sumo-next it is, I
don't see it in:
http://git.openembedded.org/openembedded-core/log/?h=sumo-next
On Sat, Mar 23, 2019 at 3:12 AM Armin Kuster <akuster808@gmail.com> wrote:
> Please consider this for the next sumo update
>
> The following changes since commit
> 6d56e912fbbaa22830b4da5ab230586a3d15b23e:
>
> package_rpm/archiver: Apply bandaid to src.rpm creation (2019-02-25
> 22:13:08 +0000)
>
> are available in the git repository at:
>
> git://git.openembedded.org/openembedded-core-contrib stable/sumo-next
>
> http://cgit.openembedded.org/openembedded-core-contrib/log/?h=stable/sumo-next
>
> Chen Qi (2):
> systemd: fix CVE-2018-15686
> systemd: fix CVE-2018-15688
>
> George McCollister (5):
> systemd: fix CVE-2018-15687
> systemd: Security fix CVE-2018-16864
> systemd: Security fix CVE-2018-16865
> systemd: fix CVE-2018-6954
> systemd: fix CVE-2019-6454
>
> Marcus Cooper (1):
> systemd: Security fix CVE-2018-16866
>
> Mingli Yu (1):
> logrotate.py: restore /etc/logrotate.d/wtmp
>
> ROGEZ Matthieu (1):
> systemd: Fix typo in root home variable.
>
> Richard Purdie (1):
> oeqa/runtime/dnf: Fix test error when static libs are enabled
>
> Stefan Agner (1):
> run-postinsts: for dpkg/opkg, do not rely on /etc/*-postinsts
>
> meta/lib/oeqa/runtime/cases/dnf.py | 2 +-
> meta/lib/oeqa/runtime/cases/logrotate.py | 6 +-
> ...sive-let-s-rework-the-recursive-logic-to-.patch | 252 +++
> ...eserializing-state-always-use-read_line-L.patch | 250 +++
> ...sure-we-have-enough-space-for-the-DHCP6-o.patch | 39 +
> ...n-t-resolve-pathnames-when-traversing-rec.patch | 643 +++++++
> .../systemd/systemd/0002-Make-tmpfiles-safe.patch | 1828
> ++++++++++++++++++++
> ...-not-store-the-iovec-entry-for-process-co.patch | 193 +++
> ...ld-set-a-limit-on-the-number-of-fields-1k.patch | 60 +
> ...ote-set-a-limit-on-the-number-of-fields-i.patch | 79 +
> ...nal-fix-out-of-bounds-read-CVE-2018-16866.patch | 49 +
> .../systemd/systemd/CVE-2019-6454.patch | 210 +++
> ...e-receive-an-invalid-dbus-message-ignore-.patch | 61 +
> meta/recipes-core/systemd/systemd_237.bb | 13 +-
> .../run-postinsts/run-postinsts/run-postinsts | 21 +-
> .../run-postinsts/run-postinsts.service | 1 -
> 16 files changed, 3694 insertions(+), 13 deletions(-)
> create mode 100644
> meta/recipes-core/systemd/systemd/0001-chown-recursive-let-s-rework-the-recursive-logic-to-.patch
> create mode 100644
> meta/recipes-core/systemd/systemd/0001-core-when-deserializing-state-always-use-read_line-L.patch
> create mode 100644
> meta/recipes-core/systemd/systemd/0001-dhcp6-make-sure-we-have-enough-space-for-the-DHCP6-o.patch
> create mode 100644
> meta/recipes-core/systemd/systemd/0001-tmpfiles-don-t-resolve-pathnames-when-traversing-rec.patch
> create mode 100644
> meta/recipes-core/systemd/systemd/0002-Make-tmpfiles-safe.patch
> create mode 100644
> meta/recipes-core/systemd/systemd/0024-journald-do-not-store-the-iovec-entry-for-process-co.patch
> create mode 100644
> meta/recipes-core/systemd/systemd/0025-journald-set-a-limit-on-the-number-of-fields-1k.patch
> create mode 100644
> meta/recipes-core/systemd/systemd/0026-journal-remote-set-a-limit-on-the-number-of-fields-i.patch
> create mode 100644
> meta/recipes-core/systemd/systemd/0027-journal-fix-out-of-bounds-read-CVE-2018-16866.patch
> create mode 100644 meta/recipes-core/systemd/systemd/CVE-2019-6454.patch
> create mode 100644
> meta/recipes-core/systemd/systemd/sd-bus-if-we-receive-an-invalid-dbus-message-ignore-.patch
>
> --
> 2.7.4
>
> --
> _______________________________________________
> bitbake-devel mailing list
> bitbake-devel@lists.openembedded.org
> http://lists.openembedded.org/mailman/listinfo/bitbake-devel
>
[-- Attachment #2: Type: text/html, Size: 5276 bytes --]
next prev parent reply other threads:[~2019-03-23 8:32 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-23 2:11 [PATCH 00/12] Sumo pull request Armin Kuster
2019-03-23 2:13 ` Armin Kuster
2019-03-23 2:14 ` akuster808
2019-03-23 8:32 ` Martin Jansa [this message]
2019-03-23 8:33 ` Martin Jansa
2019-03-23 14:41 ` akuster
2019-03-23 14:40 ` akuster
2019-03-23 20:37 ` Martin Jansa
2019-03-23 20:58 ` akuster808
2019-03-24 0:03 ` Martin Jansa
2019-03-24 1:12 ` akuster808
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='CA+chaQcb_6aOd7Xv6D-yNtMobrU81MBSvw=0uvqjMr1-HzOS3w@mail.gmail.com' \
--to=martin.jansa@gmail.com \
--cc=akuster808@gmail.com \
--cc=bitbake-devel@lists.openembedded.org \
/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.