Hi,
Can this be uploaded to jessie?
It would be of great help and, in a sense, having to run containers with
full privileges is a security issue.
Thanks,
Stefanos
___
Pkg-systemd-maintainers mailing list
Accepted:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Format: 1.8
Date: Sat, 18 Jun 2016 19:14:17 +0200
Source: init-system-helpers
Binary: init-system-helpers dh-systemd init
Architecture: source all amd64
Version: 1.35
Distribution: unstable
Urgency: medium
Maintainer: Debian systemd
Control: tag -1 -patch pending
Control: severity -1 grave
Hello Mohammad,
Mohammad Razavi [2016-06-13 14:44 +]:
> invoke-rc.d can stop/status systemd units, but start/restart is not working.
>
> After undone the commit mentioned in the bug report #546532 I was able to
> start the systemd
init-system-helpers_1.35_amd64.changes uploaded successfully to localhost
along with the files:
init-system-helpers_1.35.dsc
init-system-helpers_1.35.tar.xz
dh-systemd_1.35_all.deb
init-system-helpers_1.35_all.deb
init_1.35_amd64.deb
Greetings,
Your Debian queue daemon (running
Processing control commands:
> tag -1 -patch pending
Bug #827191 [init-system-helpers] invoke-rc.d don't start systemd services
Removed tag(s) patch.
> severity -1 grave
Bug #827191 [init-system-helpers] invoke-rc.d don't start systemd services
Severity set to 'grave' from 'normal'
--
827191:
It looks like systemd is failing to remount David's filesystems as
read/write on Linux 4.6, but not on 4.5.
Can you suggest how to get a log that would help diagnose this?
Ben.
On Sat, 2016-06-18 at 09:44 -0500, David McMackins wrote:
> Package: src:linux
> Version: 4.6.2-1
> Severity:
