On Thu, Feb 18, 2016 at 9:18 PM, Kevin Kofler
wrote:
> Yet another completely avoidable fatal error caused by SELinux. How many
> such show stoppers will it take until people finally realize that enabling
> SELinux by default was a horrible idea?
>
Not to put too fine a point on it, but I see S
Adam Williamson wrote:
> It looks like the same systemd/selinux issue that affects the
> Workstation live is also affecting KDE live, though the effects are a
> bit less predictable. When you boot a KDE live without enforcing=0 it
> kinda-sorta reaches a desktop, and you might even be able to run t
On Thu, 2016-02-18 at 23:35 +, Fedora compose checker wrote:
> Missing expected images:
>
> Cloud disk raw i386
>
> Images in this compose but not Rawhide 20160217:
>
> Kde disk raw armhfp
> Kde live i386
> Scientific_kde live x86_64
> Cloud_atomic vagrant virtualbox x86_64
> Scientific_kde
Missing expected images:
Cloud disk raw i386
Images in this compose but not Rawhide 20160217:
Kde disk raw armhfp
Kde live i386
Scientific_kde live x86_64
Cloud_atomic vagrant virtualbox x86_64
Scientific_kde live i386
Cloud_atomic vagrant libvirt x86_64
Kde live x86_64
Images in Rawhide 201602
On Thu, 2016-02-18 at 17:43 +, Fedora compose checker wrote:
> Missing expected images:
>
> Cloud disk raw i386
>
> Images in this compose but not Rawhide 20160217:
>
> Kde disk raw armhfp
> Kde live i386
> Scientific_kde live x86_64
> Cloud_atomic vagrant virtualbox x86_64
> Scientific_kde
Missing expected images:
Cloud disk raw i386
Images in this compose but not Rawhide 20160217:
Kde disk raw armhfp
Kde live i386
Scientific_kde live x86_64
Cloud_atomic vagrant virtualbox x86_64
Scientific_kde live i386
Cloud_atomic vagrant libvirt x86_64
Kde live x86_64
Images in Rawhide 201602
