All of lore.kernel.org
 help / color / mirror / Atom feed
From: Joe MacDonald <Joe_MacDonald@mentor.com>
To: Lorenz Kofler <lorenz@sigma-star.at>
Cc: yocto@yoctoproject.org
Subject: Re: meta-selinux thud compatibility
Date: Tue, 17 Sep 2019 10:11:01 -0400	[thread overview]
Message-ID: <20190917141101.GC28098@mentor.com> (raw)
In-Reply-To: <1286559489.33897.1568725712049.JavaMail.zimbra@sigma-star.at>

[-- Attachment #1: Type: text/plain, Size: 1354 bytes --]

Hi Lorenz,

[meta-selinux thud compatibility] On 19.09.17 (Tue 15:08) Lorenz Kofler wrote:

> Hello,
> 
> according to your layer.conf file is the meta-selinux layer compatible with
> thud, however it did not build successfully.
> I had to revert the patch eafe868098f52b061422bffc13fbc582d687d4ed.
> Is it possible to make a Yocto version dependent .bbappend file? Or maybe just
> remove compatibility for thud.

Thanks for bringing this to our attention.  I haven't built thud in
ages, so it's definitely helpful to hear about any issues someone may
be having.

That said, I don't see eafe868098f52b061422bffc13fbc582d687d4ed on the
'thud' branch.  I did a fresh clone into a new workspace from
git://git.yoctoproject.org/meta-selinux just to be sure.  Are you sure
your tree is in sync with the meta-selinux thud brach?  The HEAD commit
there, as I see it, is:

commit fb6192aa2c5df8e80c5e6d4fa5448d574332f68f (HEAD -> thud,
origin/thud)
Author: Khem Raj <raj.khem@gmail.com>
Date:   Tue Feb 26 11:44:43 2019 -0800

    refpolicy: Forward patch to apply cleanly on thud
    
    Also fix devtool generated warnings by refreshing patches
    
    Signed-off-by: Khem Raj <raj.khem@gmail.com>
    Signed-off-by: Joe MacDonald <joe@deserted.net>

-- 
-Joe MacDonald.
Linux Architect | Mentor® A Siemens Business
:wq

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 499 bytes --]

      reply	other threads:[~2019-09-17 14:12 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-09-17 13:08 meta-selinux thud compatibility Lorenz Kofler
2019-09-17 14:11 ` Joe MacDonald [this message]

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=20190917141101.GC28098@mentor.com \
    --to=joe_macdonald@mentor.com \
    --cc=lorenz@sigma-star.at \
    --cc=yocto@yoctoproject.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.