Bug#981648: tor FTBFS on hppa
On 2/3/21 8:55 AM, Peter Palfrader wrote: >> I've sent a patch/pull-request to upstream tor development: >> https://github.com/torproject/tor/pull/2128 >> >> Maybe this patch can be applied in debian before upstream picks it up? > > Thanks for the patch. We expect 0.4.5.5-rc to be the last RC of the > series, and a 0.4.5.6 (final) to show soon, certainly within February. > > As such, I'm tempted to wait for 0.4.5.6 which should almost certainly > include your change. Would that be ok? Sure, that's Ok. Thanks, Helge
Bug#981648: tor FTBFS on hppa
Helge Deller schrieb am Tuesday, dem 02. February 2021: > tor fails to run the testsuite on hppa architecture, as can be seen here: > util/socket_ipv4: [forking] > FAIL ../src/test/test_util.c:5989: assert(fd_is_nonblocking(fd2) OP_EQ 1): > 0 vs 1 > [socket_ipv4 FAILED] > util/socket_ipv6: [forking] > FAIL ../src/test/test_util.c:5989: assert(fd_is_nonblocking(fd2) OP_EQ 1): > 0 vs 1 > [socket_ipv6 FAILED] > > https://buildd.debian.org/status/fetch.php?pkg=tor&arch=hppa&ver=0.4.5.5-rc-1&stamp=1612278093&raw=0 > > Reason for this is, that on hppa the value of O_NONBLOCK > has been changed upstream Linux kernel. > > I've sent a patch/pull-request to upstream tor development: > https://github.com/torproject/tor/pull/2128 > > Maybe this patch can be applied in debian before upstream picks it up? Thanks for the patch. We expect 0.4.5.5-rc to be the last RC of the series, and a 0.4.5.6 (final) to show soon, certainly within February. As such, I'm tempted to wait for 0.4.5.6 which should almost certainly include your change. Would that be ok? Cheers, -- | .''`. ** Debian ** Peter Palfrader | : :' : The universal https://www.palfrader.org/ | `. `' Operating System | `-https://www.debian.org/
Bug#981648: tor FTBFS on hppa
Package: tor Version: 0.4.5.5-rc-1 Severity: important Tags: hppa, patch tor fails to run the testsuite on hppa architecture, as can be seen here: util/socket_ipv4: [forking] FAIL ../src/test/test_util.c:5989: assert(fd_is_nonblocking(fd2) OP_EQ 1): 0 vs 1 [socket_ipv4 FAILED] util/socket_ipv6: [forking] FAIL ../src/test/test_util.c:5989: assert(fd_is_nonblocking(fd2) OP_EQ 1): 0 vs 1 [socket_ipv6 FAILED] https://buildd.debian.org/status/fetch.php?pkg=tor&arch=hppa&ver=0.4.5.5-rc-1&stamp=1612278093&raw=0 Reason for this is, that on hppa the value of O_NONBLOCK has been changed upstream Linux kernel. I've sent a patch/pull-request to upstream tor development: https://github.com/torproject/tor/pull/2128 Maybe this patch can be applied in debian before upstream picks it up? Helge
