On Mon, Jun 20, 2011 at 12:57:44PM -0700, Manoj Srivastava wrote:
On 06/20/2011 11:20 AM, Roger Leigh wrote:
On Fri, Jun 03, 2011 at 11:25:52AM +0100, Roger Leigh wrote:
Don't allow migration to testing because until SELinux refpolicy
is updated to support /run, the system is rendered unusable
Version: 6.4
On Mon, Jun 20, 2011 at 07:20:35PM +0100, Roger Leigh wrote:
On Fri, Jun 03, 2011 at 11:25:52AM +0100, Roger Leigh wrote:
Don't allow migration to testing because until SELinux refpolicy
is updated to support /run, the system is rendered unusable for
SELinux users.
On Mon, Jun 20, 2011 at 12:57:44PM -0700, Manoj Srivastava wrote:
On 06/20/2011 11:20 AM, Roger Leigh wrote:
On Fri, Jun 03, 2011 at 11:25:52AM +0100, Roger Leigh wrote:
Don't allow migration to testing because until SELinux refpolicy
is updated to support /run, the system is rendered unusable
On Fri, Jun 03, 2011 at 11:25:52AM +0100, Roger Leigh wrote:
Don't allow migration to testing because until SELinux refpolicy
is updated to support /run, the system is rendered unusable for
SELinux users.
base-files would migrate prior to sysvinit/initscripts, which would result
in breakage
On 06/20/2011 11:20 AM, Roger Leigh wrote:
On Fri, Jun 03, 2011 at 11:25:52AM +0100, Roger Leigh wrote:
Don't allow migration to testing because until SELinux refpolicy
is updated to support /run, the system is rendered unusable for
SELinux users.
base-files would migrate prior to
Package: base-files
Version: 6.4
Severity: critical
Justification: breaks the whole system
Hi Santiago,
This is not a bug in base-files!; it's due to #628039 in initscripts:
Don't allow migration to testing because until SELinux refpolicy
is updated to support /run, the system is rendered
6 matches
Mail list logo
