Package: python3.6-dedupsqlfs Version: 1.2.948-0rusoft7.4~16.04.1 Architecture: i386 Maintainer: Sergey Dryabzhinsky Installed-Size: 3207 Depends: libc6 (>= 2.4), libgcc1 (>= 1:3.0), liblzma5 (>= 5.1.1alpha+20120614), liblzo2-2 (>= 2.02), libsnappy1v5, libstdc++6 (>= 4.1.1), python3.6, python3.6-pip-llfuse (>= 1.3.6), python3.6-pip-pymysql, python3.6-pip-recordclass Suggests: mysql-client | mariadb-client, mysql-server | mariadb-server Conflicts: dedupsqlfs-binary Provides: dedupsqlfs Filename: pool/ubuntu-xenial/i386/python3.6-dedupsqlfs/python3.6-dedupsqlfs_1.2.948-0rusoft7.4~16.04.1_i386.deb Size: 830460 MD5sum: dc42384fea209fffa2c04b28f8d6107b SHA1: b405e1b1ab94def28e88f4369a6de2b248262d0d SHA256: 481af1938398f2f7ec3514827fc38bf60045ce96cc4b3a82b37576aabff833ee Section: otherosfs Priority: extra Homepage: https://github.com/sergey-dryabzhinsky/dedupsqlfs Description: Deduplicating filesystem via FUSE and SQLite written in Python Development on DedupSqlFS began as a proof of concept to find out how much disk space the author could free by employing deduplication to store his daily backups. Since then it's become more or less usable as a way to archive old backups, i.e. for secondary storage deduplication. It's not recommended to use the file system for primary storage though, simply because the file system is too slow. I also wouldn't recommend depending on DedupFS just yet, at least until a proper set of automated tests has been written and successfully run to prove the correctness of the code. . What's new . - Filesystem data stored in multiple SQLite files. - Tuned SQLite connections. - Delayed writes for blocks (hashing and compression too). - Use "stream"-like writes and read of data blocks, don't store complete files in memory. - Cached filesystem tree nodes, inodes and data blocks. - New compression methods (some ported for python3): lzo, lz4, quicklz, zstd (ported); lzma, snappy. - Support for data storage in localy started MySQL server. Package: python3.6-dedupsqlfs-binary Source: python3.6-dedupsqlfs Version: 1.2.948-0rusoft7.4~16.04.1 Architecture: i386 Maintainer: Sergey Dryabzhinsky Installed-Size: 13693 Depends: libc6 (>= 2.4), libgcc1 (>= 1:3.0), liblzma5 (>= 5.1.1alpha+20120614), liblzo2-2 (>= 2.02), libsnappy1v5, libstdc++6 (>= 4.1.1), python3.6, python3.6-pip-llfuse (>= 1.3.6), python3.6-pip-pymysql, python3.6-pip-recordclass Suggests: mysql-client | mariadb-client, mysql-server | mariadb-server Conflicts: dedupsqlfs Provides: dedupsqlfs-binary Filename: pool/ubuntu-xenial/i386/python3.6-dedupsqlfs/python3.6-dedupsqlfs-binary_1.2.948-0rusoft7.4~16.04.1_i386.deb Size: 2696674 MD5sum: 1e1c5db94dec9a8ddff4a68e9530c7d8 SHA1: 08ebcfd477c370eef7e16077dc05ee8a8c3cbde9 SHA256: 301a197ab7d8c2c5cf8057cdd317dc4d8f4aa97f2c15d00da8177909a8f57506 Section: otherosfs Priority: extra Homepage: https://github.com/sergey-dryabzhinsky/dedupsqlfs Description: Deduplicating filesystem via FUSE and SQLite written in Python Development on DedupSqlFS began as a proof of concept to find out how much disk space the author could free by employing deduplication to store his daily backups. Since then it's become more or less usable as a way to archive old backups, i.e. for secondary storage deduplication. It's not recommended to use the file system for primary storage though, simply because the file system is too slow. I also wouldn't recommend depending on DedupFS just yet, at least until a proper set of automated tests has been written and successfully run to prove the correctness of the code. . What's new . - Build with Cython - Filesystem data stored in multiple SQLite files. - Tuned SQLite connections. - Delayed writes for blocks (hashing and compression too). - Use "stream"-like writes and read of data blocks, don't store complete files in memory. - Cached filesystem tree nodes, inodes and data blocks. - New compression methods (some ported for python3): lzo, lz4, quicklz, zstd (ported); lzma, snappy. - Support for data storage in localy started MySQL server. Package: python3.7-dedupsqlfs Version: 1.2.948-0rusoft7.3~16.04.1 Architecture: i386 Maintainer: Sergey Dryabzhinsky Installed-Size: 3188 Depends: libc6 (>= 2.4), libgcc1 (>= 1:3.3.1), liblzma5 (>= 5.1.1alpha+20120614), liblzo2-2 (>= 2.02), libsnappy1v5, libstdc++6 (>= 4.1.1), python3.7, python3.7-pip-llfuse (>= 1.3.6), python3.7-pip-pymysql, python3.7-pip-recordclass Suggests: mysql-client | mariadb-client, mysql-server | mariadb-server Conflicts: dedupsqlfs-binary Provides: dedupsqlfs Filename: pool/ubuntu-xenial/i386/python3.7-dedupsqlfs/python3.7-dedupsqlfs_1.2.948-0rusoft7.3~16.04.1_i386.deb Size: 827618 MD5sum: 2d86454ea5c96ed6082022a714355304 SHA1: c2b7f8bd2c9a711f9fe6a6483bfde2bbd34f1ca1 SHA256: df54b32038bdea3320a132e9d537ce7dd8b4848c75c903200140e9d0cb85920a Section: otherosfs Priority: extra Homepage: https://github.com/sergey-dryabzhinsky/dedupsqlfs Description: Deduplicating filesystem via FUSE and SQLite written in Python Development on DedupSqlFS began as a proof of concept to find out how much disk space the author could free by employing deduplication to store his daily backups. Since then it's become more or less usable as a way to archive old backups, i.e. for secondary storage deduplication. It's not recommended to use the file system for primary storage though, simply because the file system is too slow. I also wouldn't recommend depending on DedupFS just yet, at least until a proper set of automated tests has been written and successfully run to prove the correctness of the code. . What's new . - Filesystem data stored in multiple SQLite files. - Tuned SQLite connections. - Delayed writes for blocks (hashing and compression too). - Use "stream"-like writes and read of data blocks, don't store complete files in memory. - Cached filesystem tree nodes, inodes and data blocks. - New compression methods (some ported for python3): lzo, lz4, quicklz, zstd (ported); lzma, snappy. - Support for data storage in localy started MySQL server. Package: python3.7-dedupsqlfs-binary Source: python3.7-dedupsqlfs Version: 1.2.948-0rusoft7.3~16.04.1 Architecture: i386 Maintainer: Sergey Dryabzhinsky Installed-Size: 13788 Depends: libc6 (>= 2.4), libgcc1 (>= 1:3.3.1), liblzma5 (>= 5.1.1alpha+20120614), liblzo2-2 (>= 2.02), libsnappy1v5, libstdc++6 (>= 4.1.1), python3.7, python3.7-pip-llfuse (>= 1.3.6), python3.7-pip-pymysql Suggests: mysql-client | mariadb-client, mysql-server | mariadb-server Conflicts: dedupsqlfs, python3.7-pip-recordclass Provides: dedupsqlfs-binary Filename: pool/ubuntu-xenial/i386/python3.7-dedupsqlfs/python3.7-dedupsqlfs-binary_1.2.948-0rusoft7.3~16.04.1_i386.deb Size: 2713902 MD5sum: 39660e70f6f67086b9b07cfbdf9df6d7 SHA1: a634cfb481e4211513f362b5990fc9d6823e6388 SHA256: d688ff92ae82d054e6ac65465f64b3b733a7bd9681c625e04197168dbe63a8d5 Section: otherosfs Priority: extra Homepage: https://github.com/sergey-dryabzhinsky/dedupsqlfs Description: Deduplicating filesystem via FUSE and SQLite written in Python Development on DedupSqlFS began as a proof of concept to find out how much disk space the author could free by employing deduplication to store his daily backups. Since then it's become more or less usable as a way to archive old backups, i.e. for secondary storage deduplication. It's not recommended to use the file system for primary storage though, simply because the file system is too slow. I also wouldn't recommend depending on DedupFS just yet, at least until a proper set of automated tests has been written and successfully run to prove the correctness of the code. . What's new . - Build with Cython - Filesystem data stored in multiple SQLite files. - Tuned SQLite connections. - Delayed writes for blocks (hashing and compression too). - Use "stream"-like writes and read of data blocks, don't store complete files in memory. - Cached filesystem tree nodes, inodes and data blocks. - New compression methods (some ported for python3): lzo, lz4, quicklz, zstd (ported); lzma, snappy. - Support for data storage in localy started MySQL server. Package: python3.8-dedupsqlfs Version: 1.2.948-0rusoft7.3~16.04.1 Architecture: i386 Maintainer: Sergey Dryabzhinsky Installed-Size: 3154 Depends: libc6 (>= 2.4), libgcc1 (>= 1:3.3.1), liblzma5 (>= 5.1.1alpha+20120614), liblzo2-2 (>= 2.02), libsnappy1v5, libstdc++6 (>= 4.1.1), python3.8, python3.8-pip-llfuse (>= 1.3.6), python3.8-pip-pymysql, python3.8-pip-recordclass Suggests: mysql-client | mariadb-client, mysql-server | mariadb-server Conflicts: dedupsqlfs-binary Provides: dedupsqlfs Filename: pool/ubuntu-xenial/i386/python3.8-dedupsqlfs/python3.8-dedupsqlfs_1.2.948-0rusoft7.3~16.04.1_i386.deb Size: 822226 MD5sum: 99fc293211ae537d96de9ca7057c3015 SHA1: a9be17757496ddf82302419ce7f7a0a43e1eaaff SHA256: 61601894050fe8d2b6d02872ba4ae13e7a155b0aa2b65684580dd98594f367a1 Section: otherosfs Priority: extra Homepage: https://github.com/sergey-dryabzhinsky/dedupsqlfs Description: Deduplicating filesystem via FUSE and SQLite written in Python Development on DedupSqlFS began as a proof of concept to find out how much disk space the author could free by employing deduplication to store his daily backups. Since then it's become more or less usable as a way to archive old backups, i.e. for secondary storage deduplication. It's not recommended to use the file system for primary storage though, simply because the file system is too slow. I also wouldn't recommend depending on DedupFS just yet, at least until a proper set of automated tests has been written and successfully run to prove the correctness of the code. . What's new . - Filesystem data stored in multiple SQLite files. - Tuned SQLite connections. - Delayed writes for blocks (hashing and compression too). - Use "stream"-like writes and read of data blocks, don't store complete files in memory. - Cached filesystem tree nodes, inodes and data blocks. - New compression methods (some ported for python3): lzo, lz4, quicklz, zstd (ported); lzma, snappy. - Support for data storage in localy started MySQL server. Package: python3.8-dedupsqlfs-binary Source: python3.8-dedupsqlfs Version: 1.2.948-0rusoft7.3~16.04.1 Architecture: i386 Maintainer: Sergey Dryabzhinsky Installed-Size: 13725 Depends: libc6 (>= 2.4), libgcc1 (>= 1:3.3.1), liblzma5 (>= 5.1.1alpha+20120614), liblzo2-2 (>= 2.02), libsnappy1v5, libstdc++6 (>= 4.1.1), python3.8, python3.8-pip-llfuse (>= 1.3.6), python3.8-pip-pymysql, python3.8-pip-recordclass Suggests: mysql-client | mariadb-client, mysql-server | mariadb-server Conflicts: dedupsqlfs Provides: dedupsqlfs-binary Filename: pool/ubuntu-xenial/i386/python3.8-dedupsqlfs/python3.8-dedupsqlfs-binary_1.2.948-0rusoft7.3~16.04.1_i386.deb Size: 2767774 MD5sum: e36cac0a4fe9229b89d54f6a848c8d61 SHA1: bd113a6e5f840360c44f952caa8ef625098832f8 SHA256: c8734ea9b21e68edbb840b57e09564ec5c97410772332e4aa98c56b0ce03d20b Section: otherosfs Priority: extra Homepage: https://github.com/sergey-dryabzhinsky/dedupsqlfs Description: Deduplicating filesystem via FUSE and SQLite written in Python Development on DedupSqlFS began as a proof of concept to find out how much disk space the author could free by employing deduplication to store his daily backups. Since then it's become more or less usable as a way to archive old backups, i.e. for secondary storage deduplication. It's not recommended to use the file system for primary storage though, simply because the file system is too slow. I also wouldn't recommend depending on DedupFS just yet, at least until a proper set of automated tests has been written and successfully run to prove the correctness of the code. . What's new . - Build with Cython - Filesystem data stored in multiple SQLite files. - Tuned SQLite connections. - Delayed writes for blocks (hashing and compression too). - Use "stream"-like writes and read of data blocks, don't store complete files in memory. - Cached filesystem tree nodes, inodes and data blocks. - New compression methods (some ported for python3): lzo, lz4, quicklz, zstd (ported); lzma, snappy. - Support for data storage in localy started MySQL server.