<div dir="ltr"><div dir="ltr">This stable/sumo-nmut?<div><a href="http://git.openembedded.org/openembedded-core-contrib/log/?h=stable/sumo-nmut">http://git.openembedded.org/openembedded-core-contrib/log/?h=stable/sumo-nmut</a><br></div><div><br></div><div>I'm sorry, but I still don't see it there.</div></div></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Sat, Mar 23, 2019 at 9:58 PM akuster808 <<a href="mailto:akuster808@gmail.com">akuster808@gmail.com</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
<div bgcolor="#FFFFFF">
<br>
<br>
<div class="gmail-m_-6627059004469126089moz-cite-prefix">On 3/23/19 1:37 PM, Martin Jansa wrote:<br>
</div>
<blockquote type="cite">
<div dir="ltr">
<div dir="ltr">>
Why would I reference patchwork? How does that work if this is
the only message sent out?
<div><br>
</div>
<div>I don't want you to reference patchwork.</div>
<div><br>
</div>
<div>I'm only asking why you haven't included this change (<a href="http://lists.openembedded.org/pipermail/openembedded-core/2019-March/279999.html" target="_blank">http://lists.openembedded.org/pipermail/openembedded-core/2019-March/279999.html</a>
if you don't like the link to patchwork) in the pull
request, or in sumo-next branch when patchwork status says
"sumo-next".</div>
</div>
</div>
</blockquote>
<br>
its in the next series. I had build failures that put everything on
old for two weeks while I troubleshot the failures Adding new
changes would have just added to the problem. if you look at
stable/sumo-nmut, it has your changes and a few more.<br>
<br>
- armin<br>
<blockquote type="cite"><br>
<div class="gmail_quote">
<div dir="ltr" class="gmail_attr">On Sat, Mar 23, 2019 at 3:40
PM akuster <<a href="mailto:akuster@mvista.com" target="_blank">akuster@mvista.com</a>> wrote:<br>
</div>
<blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
<div bgcolor="#FFFFFF"> <br>
<br>
<div class="gmail-m_-6627059004469126089gmail-m_7305473577171404396moz-cite-prefix">On
3/23/19 1:32 AM, Martin Jansa wrote:<br>
</div>
<blockquote type="cite">
<div dir="ltr">Hi,
<div><br>
</div>
<div>is there a reason for not including</div>
<div><a href="https://patchwork.openembedded.org/patch/159465/" target="_blank">https://patchwork.openembedded.org/patch/159465/</a><br>
</div>
<div>?</div>
<div><br>
</div>
</div>
</blockquote>
Why would I reference patchwork? How does that work if this
is the only message sent out?<br>
<br>
<blockquote type="cite">
<div dir="ltr">
<div>It says sumo-next on patchwork, but I don't know
which sumo-next it is, I don't see it in:</div>
<div><a href="http://git.openembedded.org/openembedded-core/log/?h=sumo-next" target="_blank">http://git.openembedded.org/openembedded-core/log/?h=sumo-next</a><br>
</div>
</div>
</blockquote>
I don't have write access to core.<br>
<br>
the changes are in contrib:
<a class="gmail-m_-6627059004469126089gmail-m_7305473577171404396moz-txt-link-freetext" href="https://git.openembedded.org/openembedded-core-contrib/log/?h=stable/sumo-next" target="_blank">https://git.openembedded.org/openembedded-core-contrib/log/?h=stable/sumo-next</a><br>
- armin<br>
<blockquote type="cite"><br>
<div class="gmail_quote">
<div dir="ltr" class="gmail_attr">On Sat, Mar 23, 2019
at 3:12 AM Armin Kuster <<a href="mailto:akuster808@gmail.com" target="_blank">akuster808@gmail.com</a>>
wrote:<br>
</div>
<blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">Please consider
this for the next sumo update<br>
<br>
The following changes since commit
6d56e912fbbaa22830b4da5ab230586a3d15b23e:<br>
<br>
package_rpm/archiver: Apply bandaid to src.rpm
creation (2019-02-25 22:13:08 +0000)<br>
<br>
are available in the git repository at:<br>
<br>
git://<a href="http://git.openembedded.org/openembedded-core-contrib" rel="noreferrer" target="_blank">git.openembedded.org/openembedded-core-contrib</a>
stable/sumo-next<br>
<a href="http://cgit.openembedded.org/openembedded-core-contrib/log/?h=stable/sumo-next" rel="noreferrer" target="_blank">http://cgit.openembedded.org/openembedded-core-contrib/log/?h=stable/sumo-next</a><br>
<br>
Chen Qi (2):<br>
systemd: fix CVE-2018-15686<br>
systemd: fix CVE-2018-15688<br>
<br>
George McCollister (5):<br>
systemd: fix CVE-2018-15687<br>
systemd: Security fix CVE-2018-16864<br>
systemd: Security fix CVE-2018-16865<br>
systemd: fix CVE-2018-6954<br>
systemd: fix CVE-2019-6454<br>
<br>
Marcus Cooper (1):<br>
systemd: Security fix CVE-2018-16866<br>
<br>
Mingli Yu (1):<br>
logrotate.py: restore /etc/logrotate.d/wtmp<br>
<br>
ROGEZ Matthieu (1):<br>
systemd: Fix typo in root home variable.<br>
<br>
Richard Purdie (1):<br>
oeqa/runtime/dnf: Fix test error when static libs
are enabled<br>
<br>
Stefan Agner (1):<br>
run-postinsts: for dpkg/opkg, do not rely on
/etc/*-postinsts<br>
<br>
meta/lib/oeqa/runtime/cases/dnf.py |
2 +-<br>
meta/lib/oeqa/runtime/cases/logrotate.py |
6 +-<br>
...sive-let-s-rework-the-recursive-logic-to-.patch |
252 +++<br>
...eserializing-state-always-use-read_line-L.patch |
250 +++<br>
...sure-we-have-enough-space-for-the-DHCP6-o.patch |
39 +<br>
...n-t-resolve-pathnames-when-traversing-rec.patch |
643 +++++++<br>
.../systemd/systemd/0002-Make-tmpfiles-safe.patch |
1828 ++++++++++++++++++++<br>
...-not-store-the-iovec-entry-for-process-co.patch |
193 +++<br>
...ld-set-a-limit-on-the-number-of-fields-1k.patch |
60 +<br>
...ote-set-a-limit-on-the-number-of-fields-i.patch |
79 +<br>
...nal-fix-out-of-bounds-read-CVE-2018-16866.patch |
49 +<br>
.../systemd/systemd/CVE-2019-6454.patch |
210 +++<br>
...e-receive-an-invalid-dbus-message-ignore-.patch |
61 +<br>
meta/recipes-core/systemd/<a href="http://systemd_237.bb" rel="noreferrer" target="_blank">systemd_237.bb</a>
| 13 +-<br>
.../run-postinsts/run-postinsts/run-postinsts |
21 +-<br>
.../run-postinsts/run-postinsts.service |
1 -<br>
16 files changed, 3694 insertions(+), 13 deletions(-)<br>
create mode 100644
meta/recipes-core/systemd/systemd/0001-chown-recursive-let-s-rework-the-recursive-logic-to-.patch<br>
create mode 100644
meta/recipes-core/systemd/systemd/0001-core-when-deserializing-state-always-use-read_line-L.patch<br>
create mode 100644
meta/recipes-core/systemd/systemd/0001-dhcp6-make-sure-we-have-enough-space-for-the-DHCP6-o.patch<br>
create mode 100644
meta/recipes-core/systemd/systemd/0001-tmpfiles-don-t-resolve-pathnames-when-traversing-rec.patch<br>
create mode 100644
meta/recipes-core/systemd/systemd/0002-Make-tmpfiles-safe.patch<br>
create mode 100644
meta/recipes-core/systemd/systemd/0024-journald-do-not-store-the-iovec-entry-for-process-co.patch<br>
create mode 100644
meta/recipes-core/systemd/systemd/0025-journald-set-a-limit-on-the-number-of-fields-1k.patch<br>
create mode 100644
meta/recipes-core/systemd/systemd/0026-journal-remote-set-a-limit-on-the-number-of-fields-i.patch<br>
create mode 100644
meta/recipes-core/systemd/systemd/0027-journal-fix-out-of-bounds-read-CVE-2018-16866.patch<br>
create mode 100644
meta/recipes-core/systemd/systemd/CVE-2019-6454.patch<br>
create mode 100644
meta/recipes-core/systemd/systemd/sd-bus-if-we-receive-an-invalid-dbus-message-ignore-.patch<br>
<br>
-- <br>
2.7.4<br>
<br>
-- <br>
_______________________________________________<br>
bitbake-devel mailing list<br>
<a href="mailto:bitbake-devel@lists.openembedded.org" target="_blank">bitbake-devel@lists.openembedded.org</a><br>
<a href="http://lists.openembedded.org/mailman/listinfo/bitbake-devel" rel="noreferrer" target="_blank">http://lists.openembedded.org/mailman/listinfo/bitbake-devel</a><br>
</blockquote>
</div>
<br>
<fieldset class="gmail-m_-6627059004469126089gmail-m_7305473577171404396mimeAttachmentHeader"></fieldset>
</blockquote>
<br>
</div>
</blockquote>
</div>
</blockquote>
<br>
</div>
</blockquote></div>