Don Armstrong wrote:
That's basically because the policy wasn't fixed in time for the jessie
release (see #756729 and #771484). If you're using selinux on Debian, it
would probably be good to participate in the development of the default
policy and refpolicy packages.
Yes please
On Wed, 07 Sep 2016, Marko Randjelovic wrote:
> setenforce 0 works, there is no need to reboot the whole system. On
> the other hand, I cannot upgrade selinux policy from jessie because
> there is no selinux-policy-default in jessie, although there is in
> testing.
That's basically because the pol
On Wed, 07 Sep 2016 18:24:29 +0200
Sven Joachim wrote:
> On 2016-09-07 17:13 +0200, Marko Randjelovic wrote:
>
> > On Wed, 07 Sep 2016 15:17:23 +0200
> > Sven Joachim wrote:
> >
> >> File a bug against dpkg. In the meantime, rebooting with the
> >> "selinux=0" kernel parameter should give you
On 2016-09-07 17:13 +0200, Marko Randjelovic wrote:
> On Wed, 07 Sep 2016 15:17:23 +0200
> Sven Joachim wrote:
>
>> File a bug against dpkg. In the meantime, rebooting with the
>> "selinux=0" kernel parameter should give you a working dpkg.
>
> After rebooting with 'selinux=0' I reinstalled dpkg
On Wed, 07 Sep 2016, Marko Randjelovic wrote:
> I have mixed wheezy/jessie system. When tried to upgrade cmake from
> jessie, apt pulled other packages including dpkg which gave error
> during configure:
[...]
> dpkg (subprocess): cannot set security execution context for maintainer
> script: Inva
On Wed, 07 Sep 2016 15:17:23 +0200
Sven Joachim wrote:
> File a bug against dpkg. In the meantime, rebooting with the
> "selinux=0" kernel parameter should give you a working dpkg.
After rebooting with 'selinux=0' I reinstalled dpkg with success:
dpkg -i /var/cache/apt/archives/dpkg_deb
H
On Wed, 07 Sep 2016 15:17:23 +0200
Sven Joachim wrote:
> This might be a bug in dpkg or in one of the libraries it depends on
> (libselinux1 comes to mind). What are the versions of libselinux1 and
> libpcre3 on your system?
They are both latest jessie versions.
--
http://markorandjelovic.hop
On 2016-09-07 10:16 +0200, Marko Randjelovic wrote:
> I have mixed wheezy/jessie system.
This is not really recommended, since your particular combination of
packages might not have been tested by anyone. Having all packages
from the same distribution avoids this source of problems.
> When trie
8 matches
Mail list logo