Re: Problems with recent versions of s6-rc

2017-05-25 Thread Laurent Bercot
I experienced this when updating Alpine from v3.5.2 to v3.6.0 on these machines; the v3.6.0 release have already covered skalibs v2.5.1.1. Can you then please send me a strace of the failing programs? I can't reproduce. -- Laurent

Re: Problems with recent versions of s6-rc

2017-05-25 Thread Casper Ti. Vector
Additionally, on my machines, which now use freshly compiled databases, when running `s6-rc -u change default' in `rc.init', with a small but significant probability (one in a few) the procedure ends up with this error: > s6-svlisten1: fatal: unable to ftrigr_update: Broken pipe > s6-rc: warning:

Re: Problems with recent versions of s6-rc

2017-05-25 Thread Casper Ti. Vector
On Thu, May 25, 2017 at 10:17:22AM +, Laurent Bercot wrote: > All the problems you report should be fixed with skalibs-2.5.1.1, which > should already be available in Alpine. Are you still experiencing issues > with skalibs-2.5.1.1 ? I experienced this when updating Alpine from v3.5.2 to

Re: Problems with recent versions of s6-rc

2017-05-25 Thread Laurent Bercot
All the problems you report should be fixed with skalibs-2.5.1.1, which should already be available in Alpine. Are you still experiencing issues with skalibs-2.5.1.1 ? * Incompatibility of the compiled database: s6-rc commit 543c1405 breaks the backwards compatibility of the compiled

Re: Problems with recent versions of s6-rc

2017-05-25 Thread Casper Ti. Vector
On Fri, May 26, 2017 at 12:15:39AM +, Laurent Bercot wrote: > When it's about debug information such as strace outputs ;) > Except that when you send a file to a mailing-list Well this is the problem I neglected: it is

Re: Problems with recent versions of s6-rc

2017-05-25 Thread Laurent Bercot
Well I think pastebins really tend to be unreliable (most importantly, content disappearing at unexpected time), so small files (whether text or binary, as long as they are relevant) are best posted directly to the mail list No. When it's about debug information such as strace outputs, the

Re: Problems with recent versions of s6-rc

2017-05-25 Thread Laurent Bercot
A person on this list kindly told that no attachment appeared; but actually I *did* attach a gzip'ed version of the log as `rc-err.log.gz', so we are perhaps facing a problem with some steps in the mail delivery. It is intentional that binary attachments are stripped when sent to the list. I

Re: Problems with recent versions of s6-rc

2017-05-25 Thread Casper Ti. Vector
After reboot-looping a test VM for many times, this is also reproduced successfully; attached is the log. On Thu, May 25, 2017 at 09:07:26PM +0800, Casper Ti. Vector wrote: > The issue with `s6-rc' seems to be difficult to reproduce when `s6-rc' > is debugged by strace, so I am unable to produce

Re: Problems with recent versions of s6-rc

2017-05-25 Thread Casper Ti. Vector
Not even in a VirtualBox VM? Seems more interesting than I thought... Attached is the logs of `s6-rc-compile' for the three cases. The issue with `s6-rc' seems to be difficult to reproduce when `s6-rc' is debugged by strace, so I am unable to produce a log for it now. On Thu, May 25, 2017 at

Re: Problems with recent versions of s6-rc

2017-05-25 Thread Casper Ti. Vector
A person on this list kindly told that no attachment appeared; but actually I *did* attach a gzip'ed version of the log as `rc-err.log.gz', so we are perhaps facing a problem with some steps in the mail delivery. Attached is a tgz version; please do tell me if it disappears again. On Thu, May 25,

Re: Problems with recent versions of s6-rc

2017-05-25 Thread Laurent Bercot
Not even in a VirtualBox VM? Seems more interesting than I thought... I hadn't tried... I cannot reproduce when compiling everything by hand on my machines, but I followed the procedure you outlined and I am indeed able to reproduce on a Virtualbox VM running the Alpine packages. The fact

Re: Problems with recent versions of s6-rc

2017-05-25 Thread Casper Ti. Vector
Well I think pastebins really tend to be unreliable (most importantly, content disappearing at unexpected time), so small files (whether text or binary, as long as they are relevant) are best posted directly to the mail list; and since compression saves space, tarballs and zipballs are suitable