On Mon 08/27 11:19, Adam Borowski wrote: > On Mon, Aug 27, 2018 at 03:50:05PM +0800, Yanhao Mo wrote: > > Dear mentors, > > > > I am packaging a fuse file system. It called securfs [1][2]. It has some > > test cases under test directory, and these test cases require fuse kernel > > module to be loaded. My system has this module loaded. But when I > > packaging securfs by gpb && cowbuilder, I still get the following error. > > > > > fuse: device not found, try 'modprobe fuse' first > > > > I guess the build environment cannot access /dev/fuse device is the > > reason for this. But I cannot find a way to work around. So I have to > > disable all test cases to let the build process continue. > > I don't think you can reliably run such tests during build -- builds nearly > exclusively run under fakeroot, which is not enough to create missing device > nodes. Installing build-deps uses real root, but I don't think there's a > good way to ensure the device nodes are properly setup in the chroot. > > On the other hand, it's a good match for autopkgtest -- you can then specify > demands such as needs-root, and if that's not enough, isolation-container or > isolation-machine.
thanks! I fixed it with autopkgtest and isolation-machine. -- Yanhao Mo
signature.asc
Description: PGP signature
