Your message dated Sat, 30 Jun 2018 01:11:58 +0200 (CEST)
with message-id <[email protected]>
and subject line Re: pyliblo: Build not reliable
has caused the Debian Bug report #819842,
regarding pyliblo: Build not reliable
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)
--
819842: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=819842
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: src:pyliblo
Version: 0.10.0-1
User: [email protected]
Usertags: binary-indep
Severity: important
Dear maintainer:
I tried to build this package with "dpkg-buildpackage -A"
(i.e. only architecture-independent packages), and it failed:
--------------------------------------------------------------------------------
[...]
debian/rules build-indep
dh build-indep --with python2,python3 --buildsystem=pybuild
dh_testdir -i -O--buildsystem=pybuild
dh_update_autotools_config -i -O--buildsystem=pybuild
dh_auto_configure -i -O--buildsystem=pybuild
I: pybuild base:184: python2.7 setup.py config
running config
I: pybuild base:184: python3.5 setup.py config
running config
dh_auto_build -i -O--buildsystem=pybuild
I: pybuild base:184: /usr/bin/python setup.py build
running build
[... snipped ...]
testRandomPort (test.test_liblo.ServerCreationTestCase) ... ok
testSendReceive (test.test_liblo.ServerTCPTestCase) ... ERROR
testBundleCallbacksFire (test.test_liblo.ServerTestCase) ... ok
testMethodAfterFree (test.test_liblo.ServerTestCase) ... ok
testPort (test.test_liblo.ServerTestCase) ... ok
testRecvImmediate (test.test_liblo.ServerTestCase) ... ok
testRecvTimeout (test.test_liblo.ServerTestCase) ... ok
testSendBlob (test.test_liblo.ServerTestCase) ... ok
testSendBundle (test.test_liblo.ServerTestCase) ... ok
testSendInt (test.test_liblo.ServerTestCase) ... ok
testSendInvalid (test.test_liblo.ServerTestCase) ... ok
testSendLong (test.test_liblo.ServerTestCase) ... ok
testSendMessage (test.test_liblo.ServerTestCase) ... ok
testSendOthers (test.test_liblo.ServerTestCase) ... ok
testSendTimestamped (test.test_liblo.ServerTestCase) ... ok
testSendVarious (test.test_liblo.ServerTestCase) ... ok
testSendingLongAsIntOverflows (test.test_liblo.ServerTestCase) ... ok
testURL (test.test_liblo.ServerTestCase) ... ok
testSendAndReceive (test.test_liblo.ServerThreadTestCase) ... ok
======================================================================
ERROR: testSendReceive (test.test_liblo.ServerTCPTestCase)
----------------------------------------------------------------------
Traceback (most recent call last):
File "/<<PKGBUILDDIR>>/test/test_liblo.py", line 225, in testSendReceive
liblo.send(self.server.url, '/foo', 123)
File "src/liblo.pyx", line 186, in liblo.send (src/liblo.c:3321)
_send(target, None, args)
File "src/liblo.pyx", line 160, in liblo._send (src/liblo.c:3180)
raise IOError("sending failed: %s" %
IOError: sending failed: Connection timed out
----------------------------------------------------------------------
Ran 27 tests in 256.358s
FAILED (errors=1)
E: pybuild pybuild:274: test: plugin distutils failed with: exit code=1:
python2.7 setup.py test
dh_auto_test: pybuild --test -i python{version} -p 2.7 --dir . returned exit
code 13
debian/rules:4: recipe for target 'build-indep' failed
make: *** [build-indep] Error 25
dpkg-buildpackage: error: debian/rules build-indep gave error exit status 2
--------------------------------------------------------------------------------
Sorry not to have a fix, as I am reporting many bugs similar to
this one. The common hints are:
* If the only architecture-independent packages are dummy transitional
ones and they were released with jessie, the easy fix is to drop them
now.
* When using "dh", it is allowed to use (independently)
optional targets override_dh_foo-arch and override_dh_foo-indep
(for several values of "foo").
Once that both "dpkg-buildpackage -A" and "dpkg-buildpackage -B" work
properly, the package would be suitable to be uploaded in source-only
form if you wish.
Thanks.
--- End Message ---
--- Begin Message ---
Version: 0.10.0-3
I wrote:
> I have both successful and unsuccessful build logs for this package.
> All of them for version 0.10.0-1.
>
> Status: successful pyliblo_0.10.0-1_amd64-20160225-2103
> Status: successful pyliblo_0.10.0-1_amd64-20160227-1325
> Status: successful pyliblo_0.10.0-1_amd64-20160313-1519
> Status: attempted pyliblo_0.10.0-1_amd64-20160402-0031
> Status: attempted pyliblo_0.10.0-1_amd64-20160402-1951
> Status: attempted pyliblo_0.10.0-1_amd64-20160402-2012
> Status: attempted pyliblo_0.10.0-1_amd64-20160402-2024
> Status: attempted pyliblo_0.10.0-1_amd64-20160521-1427
> Status: successful pyliblo_0.10.0-1_amd64-20160621-2143
However, I can't reproduce this anymore in stretch (version 0.10.0-3),
after trying 100 times, so I hereby declare this issue as fixed,
whatever the original problem could be.
Thanks.
--- End Message ---
