At this point, I have had no requestes for vegetarian etc. and only a
few responses regarding transportation, so I will NOT be ordering a
bus. If you do need transportation and haven't let me know, please do
so asap. thanks
On Tue, Mar 29, 2016 at 1:03 PM, Rudolf J Streif
wrote:
> We need the fin
This mail was sent out by Recipe reporting system.
This message list those recipes which need to be upgraded. If maintainers
believe some of them needn't to upgrade at this time, they can fill
RECIPE_NO_UPDATE_REASON in respective recipe file to ignore this remainder
until newer upstream version w
On Sun, Apr 3, 2016 at 6:38 PM, Trevor Woerner wrote:
> Thanks to everyone for their help!! It looks like I've got something working,
> not sure if this is a "solution" or if most would just consider it a
> work-around:
>
> 1) use Andrei's meta-raspberrypi layer (which selects linux kernel 4.1 by
Thanks to everyone for their help!! It looks like I've got something working,
not sure if this is a "solution" or if most would just consider it a
work-around:
1) use Andrei's meta-raspberrypi layer (which selects linux kernel 4.1 by
default)
2) add the following to your local.conf:
Use the anonymous python function to be sure the value set for
'SELINUX' in the config file is something useful. In the event that
DEFAULT_ENFORCING isn't set to one of the 3 permissible values we
set it to 'permissive'.
Signed-off-by: Philip Tricca
---
recipes-security/refpolicy/refpolicy_commo
With the virutal package there's no need for a separate recipe to build
the config. This can be generated and included as part of the policy
package.
Signed-off-by: Philip Tricca
---
.../packagegroups/packagegroup-core-selinux.bb | 1 -
.../packagegroups/packagegroup-selinux-minimal.bb |
This allows us to provide a default policy through the
PREFERRED_PROVIDER mechanism for each of the example distro configs.
Consumers of meta-selinux will be able to override this at the config
level instead of having to depend on a specific policy package. We do
lose the ability install more than
We currently require each image to depend on the policy (or multiple
policies) that they want installed and the selinux-config package
enables the DEFAULT_POLICY. Since only one policy can be in effect at a
time, and we're targeting "embedded" systems it makes sense (to me at
least) that we would t
Hi Rikard,
On Fri, 01 Apr 2016 12:59:08 Olsson Rikard wrote:
> Hello Yocto team,
>
> We are receiving bblayer.conf and local.conf from external supplier which
> already have layers/configuration added. Now we want to add our own
> layers/configuration by appending to these files this to avoid man
