Source: dfvfs Version: 20190128-2.1 Severity: serious Justification: FTBFS on amd64 Tags: bullseye sid ftbfs Usertags: ftbfs-20200926 ftbfs-bullseye
Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > ====================================================================== > ERROR: testOpenCloseInode (file_io.bde_file_io.BDEFileWithKeyChainTest) > Test the open and close functionality using an inode. > ---------------------------------------------------------------------- > Traceback (most recent call last): > File "/<<PKGBUILDDIR>>/tests/file_io/bde_file_io.py", line 40, in > testOpenCloseInode > self._TestOpenCloseInode(self._bde_path_spec) > File "./tests/file_io/test_lib.py", line 38, in _TestOpenCloseInode > file_object.open(path_spec=path_spec) > File "./dfvfs/file_io/file_io.py", line 76, in open > self._Open(path_spec=path_spec, mode=mode) > File "./dfvfs/file_io/tsk_file_io.py", line 60, in _Open > file_entry = file_system.GetFileEntryByPathSpec(path_spec) > File "./dfvfs/vfs/tsk_file_system.py", line 136, in GetFileEntryByPathSpec > return tsk_file_entry.TSKFileEntry( > File "./dfvfs/vfs/tsk_file_entry.py", line 452, in __init__ > self._file_system_type = tsk_file.info.fs_info.ftype > AttributeError: 'pytsk3.TSK_FS_INFO' object has no attribute 'ftype' The full build log is available from: http://qa-logs.debian.net/2020/09/26/dfvfs_20190128-2.1_unstable.log A list of current common problems and possible solutions is available at http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute! About the archive rebuild: The rebuild was done on EC2 VM instances from Amazon Web Services, using a clean, minimal and up-to-date chroot. Every failed build was retried once to eliminate random failures.
