Am 29.07.2016 um 23:10 schrieb Felipe Sateler:
> I was going to ask this. I think we should register interest in
> insserv in the reportbug configuration.
Good idea. Added a bug-control script and pushed to master.
--
Why is it that all of the instruments seeking intelligent life in the
universe
Am 29.07.2016 um 23:29 schrieb Rick Thomas:
> Hmmm… Curiouser and curiouser!
>
> I upgraded a VM (amd64) to latest Sid (with systemd version 231-1). The
> problem is *not* present there.
>
> The problem may be specific to arm hardware? I’ll try it on a PowerPC G4
> (Apple Mac PPC) machine la
Hmmm… Curiouser and curiouser!
I upgraded a VM (amd64) to latest Sid (with systemd version 231-1). The
problem is *not* present there.
The problem may be specific to arm hardware? I’ll try it on a PowerPC G4
(Apple Mac PPC) machine later today.
Rick
On Jul 28, 2016, at 5:18 PM, Rick Thoma
Am 29.07.2016 um 22:44 schrieb Michael Biebl:
> Package: init-system-helpers
> Version: 1.41
> Severity: serious
>
> Running
> update-rc.d foo disable
> update-rc.d foo defaults
> will create start symlinks although this should not happen for a
> disabled service.
This happens when insserv is not
Package: init-system-helpers
Version: 1.41
Severity: serious
Running
update-rc.d foo disable
update-rc.d foo defaults
will create start symlinks although this should not happen for a
disabled service.
-- System Information:
Debian Release: stretch/sid
APT prefers unstable-debug
APT policy: (
Processing commands for cont...@bugs.debian.org:
> forcemerge 832713 832893
Bug #832713 [systemd] systemd: after "systemd (231-1) unstable" update
systemd-jurnald.service fails to start
Bug #832893 [systemd] Failed at step SECCOMP spawning systemd-networkd
Added tag(s) moreinfo.
Merged 832713 832
On Fri, Jul 29, 2016 at 02:42:55PM +0200, Michael Biebl wrote:
> Am 29.07.2016 um 14:08 schrieb Marc Haber:
> > systemd 231-1 on Banana Pi fails with a bunch of "Failed at step
> > SECCOMP spawning systemd-food: Invalid Argument". This at least
> > applies to logind and networkd. Here is the output
Am 29.07.2016 um 14:42 schrieb Michael Biebl:
> Am 29.07.2016 um 14:08 schrieb Marc Haber:
>> [ 113.379297] systemd[1]: Failed to start Network Service.
>> [ 113.444174] systemd[1565]: systemd-networkd.service: Failed at step
>> SECCOMP spawning /lib/systemd/systemd-networkd: Invalid argument
>
Am 29.07.2016 um 14:08 schrieb Marc Haber:
> systemd 231-1 on Banana Pi fails with a bunch of "Failed at step
> SECCOMP spawning systemd-food: Invalid Argument". This at least
> applies to logind and networkd. Here is the output of trying to restart
> systemd-networkd:
>
> [ 113.060755] systemd[1
On Thu, Jul 28, 2016 at 04:43:41PM +0200, Michael Biebl wrote:
> Am 28.07.2016 um 16:39 schrieb Michael Biebl:
> > Maybe Felipe's helper could be generalized and added to gbp pq, like
> > gbp pq cherry-pick
>
> Or more generally gbp pq cherry-pick --before|after
>
> This will cherry-pick a giv
Am 29.07.2016 um 09:17 schrieb Michael Biebl:
> That's not a bug in systemd but in your service file.
> If you want to run in early boot, you'll need to use
> DefaultDependencies=yes and specify your dependencies/orderings carefully.
I've filed an upstream RFE bug at [1]. Maybe they have an idea h
Your message dated Fri, 29 Jul 2016 09:17:28 +0200
with message-id <2479ebcf-0542-8e6b-4826-2ac5a4989...@debian.org>
and subject line Re: usage of network-pre.target results in systemd ordering
cycle
has caused the Debian Bug report #832802,
regarding usage of network-pre.target results in systemd
12 matches
Mail list logo
