On Mar 01 2016, Steven Chamberlain <[email protected]> wrote: > Nikolaus Rath wrote: >> I noticed that the kfreeBSD build of python-llfuse is failing because of >> >> build/temp.gnukfreebsd-10.1-0-amd64-x86_64-3.5/src/llfuse.o: In function >> `getxattr_p': >> /«BUILDDIR»/python-llfuse-0.43+dfsg/src/xattr.h:38: warning: getxattr is not >> implemented and will always fail >> build/temp.gnukfreebsd-10.1-0-amd64-x86_64-3.5/src/llfuse.o: In function >> `setxattr_p': >> /«BUILDDIR»/python-llfuse-0.43+dfsg/src/xattr.h:42: warning: setxattr is not >> implemented and will always fail > > Thanks for figuring that out!
You got me confused there for a second :-). Actually I totally forgot about the previous issue with the test discovery (because I am still waiting for an account on one of the porter boxes). But it seems that just uploading the new upstream release fixed that issue, nice! >> What's the proper way to work with extended attributes under kFreeBSD? > > We still need to implement it, I think :( > > It was mentioned recently: > https://lists.debian.org/debian-bsd/2015/12/msg00027.html > but will likely take some weeks before it is available. Seems best to just skip the tests then. Can you tell me how to detect GNU/kFreeBSD from Python? sys.platform and os.uname are potential candidates, but the Python docs unfortunately don't mention what the values of those variables are for GNU/kFreeBSD (and if they differ from the one for FreeBSD and GNU/Linux). (Please don't send Cc's, I'm reading the list). 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.«
