Bug#850457: pspp 0.10.2-1 FTBS randomly

2017-06-03 Thread Friedrich Beckmann
> Am 03.06.2017 um 14:10 schrieb John Darrington : > > I presume this error is one that has just recently arisen? and so far as I'm > aware, no uploads > of pspp have recently occured in Debian (am I right Frederich?) If so, then > I suggest that recent >

Bug#850457: pspp 0.10.2-1 FTBS randomly

2017-06-03 Thread Friedrich Beckmann
Hi Lucas, I guess the regression failure for postgresql here https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=863928 and for pspp here https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=850457 https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=863933 which also fails when starting the psql

Bug#850457: pspp 0.10.2-1 FTBS randomly

2017-06-03 Thread John Darrington
Hi Christoph, On Sat, Jun 03, 2017 at 12:27:12PM +0200, Christoph Berg wrote: Re: John Darrington 2017-06-03 <20170603061903.GA30068@jocasta.intra> > If I'm reading that log file correctly, the issue is simply that initdb is dumping that > message on stderr. Our test considers

Bug#850457: pspp 0.10.2-1 FTBS randomly

2017-06-03 Thread Christoph Berg
Re: John Darrington 2017-06-03 <20170603061903.GA30068@jocasta.intra> > If I'm reading that log file correctly, the issue is simply that initdb is > dumping that > message on stderr. Our test considers that a failure. > > This would seem to suggest a problem with debian's postgres package.

Bug#850457: pspp 0.10.2-1 FTBS randomly

2017-06-03 Thread John Darrington
If I'm reading that log file correctly, the issue is simply that initdb is dumping that message on stderr. Our test considers that a failure. This would seem to suggest a problem with debian's postgres package. However I think we can safely ignore it by changing AT_CHECK([initdb -A trust],

Bug#850457: pspp 0.10.2-1 FTBS randomly

2017-06-02 Thread Friedrich Beckmann
Dear Adrian, dear Lucas, thanks for your reports. Maybe you can help me with the analysis as I have problems to reproduce it here locally. As already reported in the bug log https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=863933 I think the problem is due to locale settings in the