Bug#832713: Systemd version 231-1 (current in Sid) doesn't work on arm

Thanks, Christian! What is your armel box? I *do* see it on my SheevaPlug (armel), so there may be a clue. Is your armel kernel customized in some way? Enjoy! Rick > On Jul 30, 2016, at 11:33 PM, Christian Marillat wrote: > > On 30 juil. 2016 23:02, Rick Thomas wrote: > >> Has anyone else

Bug#832713: Systemd version 231-1 (current in Sid) doesn't work on arm

On 30 juil. 2016 23:02, Rick Thomas wrote: > Has anyone else noticed this bug? > > Bug#832713: systemd: after "systemd (231-1) unstable" update > systemd-jurnald.service fails to start > > I’ve tried it on armel (SheevaPlug) and armmp (Cubox-i4Pro). It fails on > both. > I’ve also tried it on a

Bug#832945: marked as done (update-rc.d defaults does not respect disabled state of a sysv init script)

Your message dated Sat, 30 Jul 2016 22:24:34 + with message-id and subject line Bug#832945: fixed in init-system-helpers 1.42 has caused the Debian Bug report #832945, regarding update-rc.d defaults does not respect disabled state of a sysv init script to be marked as done. This means that y

init-system-helpers_1.42_amd64.changes ACCEPTED into unstable

Accepted: -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Sat, 30 Jul 2016 17:04:28 -0400 Source: init-system-helpers Binary: init-system-helpers dh-systemd init Architecture: source all amd64 Version: 1.42 Distribution: unstable Urgency: medium Maintainer: Debian systemd Main

Processing of init-system-helpers_1.42_amd64.changes

init-system-helpers_1.42_amd64.changes uploaded successfully to localhost along with the files: init-system-helpers_1.42.dsc init-system-helpers_1.42.tar.xz dh-systemd_1.42_all.deb init-system-helpers_1.42_all.deb init_1.42_amd64.deb Greetings, Your Debian queue daemon (running

Bug#832713: Systemd version 231-1 (current in Sid) doesn't work on arm

Has anyone else noticed this bug? Bug#832713: systemd: after "systemd (231-1) unstable" update systemd-jurnald.service fails to start I’ve tried it on armel (SheevaPlug) and armmp (Cubox-i4Pro). It fails on both. I’ve also tried it on amd64 and powerpc hardware. The bug is not present there.

Bug#832945: update-rc.d defaults does not respect disabled state of a sysv init script

Am 30.07.2016 um 20:47 schrieb Michael Biebl: > Am 30.07.2016 um 19:52 schrieb Felipe Sateler: >> On 29 July 2016 at 17:05, Michael Biebl wrote: >>> Am 29.07.2016 um 22:44 schrieb Michael Biebl: Package: init-system-helpers Version: 1.41 Severity: serious Running upda

Bug#832945: update-rc.d defaults does not respect disabled state of a sysv init script

On 30 July 2016 at 14:47, Michael Biebl wrote: > Am 30.07.2016 um 19:52 schrieb Felipe Sateler: >> On 29 July 2016 at 17:05, Michael Biebl wrote: >>> Am 29.07.2016 um 22:44 schrieb Michael Biebl: Package: init-system-helpers Version: 1.41 Severity: serious Running up

Re: How to securely load a firewall before networking gets up?

On 30 Jul 2016 2:46 p.m., "Patrick Schleizer" < patrick-mailingli...@whonix.org> wrote: > > Felipe Sateler: > > On 30 July 2016 at 13:58, Patrick Schleizer > > wrote: > >> How to securely load a firewall before networking gets up? > >> > >> Can you provide a secure, recommended or even canonical e

Bug#832945: update-rc.d defaults does not respect disabled state of a sysv init script

Am 30.07.2016 um 19:52 schrieb Felipe Sateler: > On 29 July 2016 at 17:05, Michael Biebl wrote: >> 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 >>> wil

Re: How to securely load a firewall before networking gets up?

Felipe Sateler: > On 30 July 2016 at 13:58, Patrick Schleizer > wrote: >> How to securely load a firewall before networking gets up? >> >> Can you provide a secure, recommended or even canonical example of such >> a firewall.service? >> >> It does not become clear from systemd documentation [0] th

Re: How to securely load a firewall before networking gets up?

On 30 July 2016 at 13:58, Patrick Schleizer wrote: > How to securely load a firewall before networking gets up? > > Can you provide a secure, recommended or even canonical example of such > a firewall.service? > > It does not become clear from systemd documentation [0] that > DefaultDependencies=n

How to securely load a firewall before networking gets up?

How to securely load a firewall before networking gets up? Can you provide a secure, recommended or even canonical example of such a firewall.service? It does not become clear from systemd documentation [0] that DefaultDependencies=no should be used. I also asked about this on the system mailing

Bug#832945: update-rc.d defaults does not respect disabled state of a sysv init script

On 29 July 2016 at 17:05, Michael Biebl wrote: > 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 fo

unexpected surprise

Yo! I know you're gonna be surprised by that news, just take a look Sincerely yours, Samuel Thibault ___ Pkg-systemd-maintainers mailing list Pkg-systemd-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/

Bug#832713: systemd: after "systemd (231-1) unstable" update systemd-jurnald.service fails to start

As I replied to that (did you see it? There may have been some problems with my email about that time), commenting out the “SystemCallFilter” did not make the problem go away on either of the ARM systems. Another interesting datapoint: I upgraded my PowerMac G4 powerpc machine to latest Sid (i