On Feb 21 2016, Steven Chamberlain <ste...@pyro.eu.org> wrote:
> Andreas Beckmann wrote:
>> python-llfuse cannot be built on kfreebsd-amd64 and kfreebsd-i386 since
>> the fuse binary package does not exist there (but libfuse-dev is
>> available).
>
> The package already Build-Depends on libfuse-dev. fuse is mentioned
> here so that it can try to run the testsuite (though I'm not sure it
> can really do that on the buildds?)
Not on the buildds, but on e.g. a local pbuilder or sbuilder.
>
> In order to support kfreebsd as well, the dependency should be:
> fuse [linux-any] | fuse4bsd [kfreebsd-any]
Thanks for investigating!
> When I try that on kfreebsd (fuse kernel module loaded or not), I get
> the following FTBFS whereas on Linux it continues past this:
>
> | dh_auto_test -O--buildsystem=pybuild -Npython-llfuse -Npython-llfuse-dbg
> -Npython3-llfuse -Npython3-llfuse-dbg
> | pybuild --test -i python{version} -p 2.7 --dir .
> | I: pybuild base:184: cd
> /build/python-llfuse-0.41.1+dfsg/.pybuild/pythonX.Y_2.7/build; python2.7 -m
> pytest --installed "/build/python-llfuse-0.41.1+dfsg/test/"
> | ============================================================ test session
> starts =============================================================
> | platform gnukfreebsd10 -- Python 2.7.11, pytest-2.8.7, py-1.4.31,
> pluggy-0.3.1 -- /usr/bin/python2.7
> | cachedir: ../../../test/.cache
> | rootdir: /build/python-llfuse-0.41.1+dfsg/test, inifile: pytest.ini
> | collected 0 items / 1 skipped
> |
> | ========================================================= 1 skipped in 0.07
> seconds ==========================================================
> | E: pybuild pybuild:274: test: plugin distutils failed with: exit code=5: cd
> /build/python-llfuse-0.41.1+dfsg/.pybuild/pythonX.Y_2.7/build; python2.7 -m
> pytest --installed "{dir}/test/"
> | dh_auto_test: pybuild --test -i python{version} -p 2.7 --dir . returned
> exit code 13
> | debian/rules:10: recipe for target 'binary' failed
> | make: *** [binary] Error 25
This looks odd.. something fails, but I don't actually see any error
message (skipping a test shouldn't result in a test failure). Is this
from a buildd or from your local system?
In the latter case, can you try running 'py.test-3 -s test/' directly to
see if that gives a more helpful message?
Best,
-Nikolaus
--
GPG encrypted emails preferred. Key id: 0xD113FCAC3C4E599F
Fingerprint: ED31 791B 2C5C 1613 AF38 8B8A D113 FCAC 3C4E 599F
»Time flies like an arrow, fruit flies like a Banana.«
