Bug#845081: Bug #845081: wmbiff FTBFS on s390x: test failure

2016-12-21 Thread Doug Torrance
Control: severity -1 important With wmbiff version 0.4.30-2, just uploaded to sid, the offending test (test_wmbiff) is now skipped on big endian archs like s390x. Therefore, the package now builds on these archs. The underlying problem still exists, but I am reducing the severity to importa

Bug#845081: Bug##845081: wmbiff FTBFS on s390x: test failure

2016-12-02 Thread Doug Torrance
On 12/02/2016 12:58 PM, Bastian Blank wrote: On Fri, Dec 02, 2016 at 10:44:05AM -0500, Doug Torrance wrote: On 12/02/2016 09:26 AM, Bastian Blank wrote: You know, Debian actually has a s390x porter machine. You can use it to test such problems. Yeah, I've used porterboxes in the past. I'm no

Bug#845081: Bug##845081: wmbiff FTBFS on s390x: test failure

2016-12-02 Thread Bastian Blank
Hi Doug On Fri, Dec 02, 2016 at 10:44:05AM -0500, Doug Torrance wrote: > On 12/02/2016 09:26 AM, Bastian Blank wrote: > >You know, Debian actually has a s390x porter machine. You can use it to > >test such problems. > Yeah, I've used porterboxes in the past. I'm not a DD or DM, and > the process

Bug#845081: Bug##845081: wmbiff FTBFS on s390x: test failure

2016-12-02 Thread Doug Torrance
On 12/02/2016 09:26 AM, Bastian Blank wrote: On Thu, Dec 01, 2016 at 09:37:23AM -0500, Doug Torrance wrote: Thanks for your reply! I've changed all the shorts to uint16_t's -- hopefully this works! You know, Debian actually has a s390x porter machine. You can use it to test such problems. Y

Bug#845081: Bug##845081: wmbiff FTBFS on s390x: test failure

2016-12-02 Thread Bastian Blank
Hi Doug On Thu, Dec 01, 2016 at 09:37:23AM -0500, Doug Torrance wrote: > Thanks for your reply! > I've changed all the shorts to uint16_t's -- hopefully this works! You know, Debian actually has a s390x porter machine. You can use it to test such problems. Regards, Bastian -- Actual war is a

Bug#845081: Bug##845081: wmbiff FTBFS on s390x: test failure

2016-12-01 Thread Doug Torrance
On 11/24/2016 08:25 AM, Bastian Blank wrote: On Tue, Nov 22, 2016 at 12:46:27PM -0500, Doug Torrance wrote: Error connecting: Invalid argument connect(0.0.3.255:-7907) failed: Invalid argument I would start here. The IP/port information is converted incorrectly. I assume it's this function:

Bug#845081: Bug##845081: wmbiff FTBFS on s390x: test failure

2016-11-24 Thread Bastian Blank
Hi Doug On Tue, Nov 22, 2016 at 12:46:27PM -0500, Doug Torrance wrote: > > Error connecting: Invalid argument > > connect(0.0.3.255:-7907) failed: Invalid argument I would start here. The IP/port information is converted incorrectly. I assume it's this function: | static int ipv4_sock_connect(s

Bug#845081: Bug##845081: wmbiff FTBFS on s390x: test failure

2016-11-22 Thread Doug Torrance
Hello! I am copying the RC bug below to the s390 mailing list. I am stumped as to what is going on. Does anyone have any suggestions? Thank you! On Sun, 20 Nov 2016 11:30:55 +0200 Adrian Bunk wrote: > Source: wmbiff > Version: 0.4.29-1 > Severity: serious > > https://buildd.debian.org/sta