Re: 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 not a DD or DM, and
the process of getting porterbox access is kind of a headache.  If
this fix doesn't work, I'll go that route.


Oh, I'm sorry.  I missed that you only got a guest user; they are not
marked specially on db.debian.org.


No worries.  It looks like the signed short problem was fixed, but the 
build is still failing [1], so I'll be applying for porterbox access 
after all.  :)


Doug

[1] 
https://buildd.debian.org/status/fetch.php?pkg=wmbiff=s390x=0.4.30-1=1480698922




Re: 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 of getting porterbox access is kind of a headache.  If
> this fix doesn't work, I'll go that route.

Oh, I'm sorry.  I missed that you only got a guest user; they are not
marked specially on db.debian.org.

Bastian

-- 
Love sometimes expresses itself in sacrifice.
-- Kirk, "Metamorphosis", stardate 3220.3



Re: 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.


Yeah, I've used porterboxes in the past.  I'm not a DD or DM, and the 
process of getting porterbox access is kind of a headache.  If this fix 
doesn't work, I'll go that route.


Doug



Re: 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 very messy business.  Very, very messy business.
-- Kirk, "A Taste of Armageddon", stardate 3193.0



Re: 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:
| static int ipv4_sock_connect(struct in_addr *address, short port)

short is signed and incapable of carrying a port.


Thanks for your reply!

I've changed all the shorts to uint16_t's -- hopefully this works!

Doug