On 3/23/19 5:03 PM, Martin Jansa wrote: > This stable/sumo-nmut? > http://git.openembedded.org/openembedded-core-contrib/log/?h=stable/sumo-nmut > > I'm sorry, but I still don't see it there. So true. The contrib I used to build out of for Yocto AB. http://git.yoctoproject.org/cgit/cgit.cgi/poky-contrib/log/?h=stable/sumo-nmut Sorry, I am in the middle of re-aligning my processes from what was easier for me to what works better for the community. it will be corrected soon. - armin > > On Sat, Mar 23, 2019 at 9:58 PM akuster808 > wrote: > > > > On 3/23/19 1:37 PM, Martin Jansa wrote: >> >  Why would I reference patchwork? How does that work if this is >> the only message sent out? >> >> I don't want you to reference patchwork. >> >> I'm only asking why you haven't included this change >> (http://lists.openembedded.org/pipermail/openembedded-core/2019-March/279999.html >> if you don't like the link to patchwork) in the pull request, or >> in sumo-next branch when patchwork status says "sumo-next". > > 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. > > - armin >> >> On Sat, Mar 23, 2019 at 3:40 PM akuster > > wrote: >> >> >> >> On 3/23/19 1:32 AM, Martin Jansa wrote: >>> Hi, >>> >>> is there a reason for not including >>> https://patchwork.openembedded.org/patch/159465/ >>> ? >>> >> Why would I reference patchwork? How does that work if this >> is the only message sent out? >> >>> 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 >> I don't have write access to core. >> >> the changes are in contrib: >> https://git.openembedded.org/openembedded-core-contrib/log/?h=stable/sumo-next >> - armin >>> >>> On Sat, Mar 23, 2019 at 3:12 AM Armin Kuster >>> > 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 >>> >>> >> >