Re: systemd again

2016-01-03 Thread Mark Morgan Lloyd
Ulrich Teichert wrote: Actually, I tend to disagree here. I'm arguing against systemd specifically, not against similar solutions. I think it's telling that Oracle and Apple both have invented their own solutions. I don't know why, but I know that systemd is not portable by design, which I

Re: xsltproc: bus error on some architectures

2016-01-03 Thread John Paul Adrian Glaubitz
Hi! We are constantly running into this issue on sparc64 as well. I have already updated the kernel to 4.3.3 from unstable as well as tried the patch that Peter De Wachter suggested for docbook-xsl as well as changing the permissions for /dev/shm, to no avail. xsltproc still randomly segfaults:

Re: Bug#750593: xsltproc: bus error on some architectures

2016-01-03 Thread John Paul Adrian Glaubitz
On 01/03/2016 03:05 PM, Jelmer Vernooij wrote: > On Sun, Jan 03, 2016 at 11:45:45AM +0100, John Paul Adrian Glaubitz wrote: >> We are constantly running into this issue on sparc64 as well. > Thank you for taking the time to look into this in more detail, much > appreciated. No problem. It

Re: Bug#750593: xsltproc: bus error on some architectures

2016-01-03 Thread Jelmer Vernooij
Hi Adrian, On Sun, Jan 03, 2016 at 11:45:45AM +0100, John Paul Adrian Glaubitz wrote: > We are constantly running into this issue on sparc64 as well. Thank you for taking the time to look into this in more detail, much appreciated. > I have already updated the kernel to 4.3.3 from unstable as

Re: New working sparc64 netinst image

2016-01-03 Thread John Paul Adrian Glaubitz
On 01/02/2016 07:55 PM, John Paul Adrian Glaubitz wrote: >> Jan 2 18:15:07 debootstrap: dpkg: regarding .../ifupdown_0.8.5_sparc64.deb >> containing ifupdown: >> Jan 2 18:15:07 debootstrap: ifupdown breaks systemd (<< 228-3~) >> Jan 2 18:15:07 debootstrap: systemd (version 228-2) is present

Re: Bug#750593: xsltproc: bus error on some architectures

2016-01-03 Thread John Paul Adrian Glaubitz
On 01/03/2016 03:59 PM, John Paul Adrian Glaubitz wrote: > Further research shows that it might actually be a glibc bug which > occurred first with glibc_2.21. The problem never occurred with > glibc_2.19. Ok, more information: Downgrading libxml2 from 2.9.3+dfsg1-1 to 2.9.2+zdfsg1-4 fixes the