From: Sinan Kaya <okaya@kernel.org>
To: sscott@san.rr.com, 'Stefano Cappa' <stefano.cappa.ks89@gmail.com>
Cc: yocto@yoctoproject.org
Subject: Re: [selinux] sumo compilation
Date: Thu, 18 Oct 2018 12:15:31 -0400 [thread overview]
Message-ID: <0be242c4-86ab-e9d9-fb22-9150e41621fa@kernel.org> (raw)
In-Reply-To: <006901d466f9$b86b0be0$294123a0$@san.rr.com>
Thanks Steve,
We'll give it a try.
On 10/18/2018 11:46 AM, Steve Scott wrote:
> You may also need
> PREFERRED_PROVIDER_virtual/refpolicy = "refpolicy-standard"
> in local.conf.
>
> -steve
>
>> -----Original Message-----
>> From: Sinan Kaya [mailto:okaya@kernel.org]
>> Sent: Thursday, October 18, 2018 8:06 AM
>> To: sscott@san.rr.com; 'Stefano Cappa' <stefano.cappa.ks89@gmail.com>
>> Cc: yocto@yoctoproject.org
>> Subject: Re: [yocto] [selinux] sumo compilation
>>
>> Sorry for confusing names, not enough coffee yet...
>>
>> I was trying to say that Steve's suggestion to use
>>
>> PREFERRED_VERSION_refpolicy-standard = "2.20170204"
>>
>> didn't work on sumo branch.
>>
>> On 10/18/2018 10:49 AM, Sinan Kaya wrote:
>>> CC'ing the selinux maintainers:
>>>
>>> I was told that using the master branch and reverting the e2fs change
>>> (http://git.yoctoproject.org/cgit/cgit.cgi/meta-selinux/commit/?id=78e
>>> ca8242ea5397c4dc0654d62244453b4260151)
>>> works on sumo.
>>>
>>> Stefano's suggestion unfortunately didn't work.
>>>
>>> Maybe, it is time to create the sumo branch?
>>>
>>> On 10/18/2018 9:48 AM, Steve Scott wrote:
>>>> I did not try it on sumo.
>>>>
>>>>
>>>> From: Stefano Cappa [mailto:stefano.cappa.ks89@gmail.com]
>>>> Sent: Wednesday, October 17, 2018 11:15 PM
>>>> To: sscott@san.rr.com
>>>> Cc: Sinan Kaya <okaya@kernel.org>; yocto@yoctoproject.org
>>>> Subject: Re: [yocto] [selinux] sumo compilation
>>>>
>>>>
>>>> Exactly the same issue since September.
>>>>
>>>>
>>>> Here is my discussion
>>>> https://lists.yoctoproject.org/pipermail/yocto/2018-
>> September/042711.html.
>>>> With that trick did you find a solution also on sumo?
>>>>
>>>>
>>>> Il gio 18 ott 2018, 01:42 <sscott@san.rr.com
>>>> <mailto:sscott@san.rr.com> > ha
>>>> scritto:
>>>>
>>>>
>>>> It was broken in rocko too. I added this to local.conf to workaround the
>> problem:
>>>>
>>>> PREFERRED_VERSION_refpolicy-standard = "2.20170204"
>>>>
>>>> -steve
>>>>
>>>> ---- Sinan Kaya <okaya@kernel.org <mailto:okaya@kernel.org> > wrote:
>>>>> Hi,
>>>>>
>>>>> We realized today that SELinux does not compile on sumo branch.
>>>>>
>>>>> Is it possible for someone to branch the last working version to a sumo
>> branch?
>>>>>
>>>>> http://git.yoctoproject.org/cgit/cgit.cgi/meta-selinux/refs/
>>>>>
>>>>> NOTE: Running task 352 of 2707
>>>>> (virtual:native:/sources/poky/meta/recipes-devtools/e2fsprogs/e2fspr
>>>>> ogs_1.43.8.bb <http://e2fsprogs_1.43.8.bb> :do_patch)
>>>>> NOTE: recipe e2fsprogs-native-1.43.8-r0: task do_patch: Started
>>>>> NOTE: Running task 1413 of 2707
>>>>> (/sources/poky/meta/recipes-
>> devtools/e2fsprogs/e2fsprogs_1.43.8.bb:d
>>>>> o_patch)
>>>>> NOTE: recipe e2fsprogs-1.43.8-r0: task do_patch: Started
>>>>> ERROR: e2fsprogs-native-1.43.8-r0 do_patch: Command Error: 'quilt
>>>>> --quiltrc Applying patch misc_create_inode.c-label_rootfs.patch
>>>>> patching file misc/create_inode.c
>>>>> Hunk #1 FAILED at 979.
>>>>> Hunk #2 FAILED at 987.
>>>>>
>>>>> Sinan
>>>>> --
>>>>> _______________________________________________
>>>>> yocto mailing list
>>>>> yocto@yoctoproject.org <mailto:yocto@yoctoproject.org>
>>>>> https://lists.yoctoproject.org/listinfo/yocto
>>>>
>>>
>
>
next prev parent reply other threads:[~2018-10-18 16:15 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-17 23:00 [selinux] sumo compilation Sinan Kaya
2018-10-17 23:27 ` sscott
2018-10-18 6:14 ` Stefano Cappa
2018-10-18 13:48 ` Steve Scott
2018-10-18 14:49 ` Sinan Kaya
2018-10-18 15:05 ` Sinan Kaya
2018-10-18 15:46 ` Steve Scott
2018-10-18 16:15 ` Sinan Kaya [this message]
2018-10-18 16:00 ` Mark Hatle
2018-10-18 19:08 ` Joe MacDonald
2018-10-18 20:48 ` Sinan Kaya
2018-10-18 21:13 ` Stefano Cappa
2018-10-20 23:18 ` Stefano Cappa
2018-10-21 8:13 ` Mark Hatle
2018-10-24 23:49 ` Joe MacDonald
2018-10-30 13:45 ` Sinan Kaya
2018-12-30 11:28 ` Stefano Cappa
2018-12-30 14:31 ` MacDonald, Joe
2018-12-31 2:46 ` Joe MacDonald
2018-12-31 2:52 ` MacDonald, Joe
2019-01-09 20:55 ` Stefano Cappa
2019-01-14 23:28 ` Stefano Cappa
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=0be242c4-86ab-e9d9-fb22-9150e41621fa@kernel.org \
--to=okaya@kernel.org \
--cc=sscott@san.rr.com \
--cc=stefano.cappa.ks89@gmail.com \
--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.