Package: python3.6-dedupsqlfs Version: 1.2.948-0rusoft7.4~16.04.1 Architecture: amd64 Maintainer: Sergey Dryabzhinsky Installed-Size: 3265 Depends: libc6 (>= 2.14), 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/amd64/python3.6-dedupsqlfs/python3.6-dedupsqlfs_1.2.948-0rusoft7.4~16.04.1_amd64.deb Size: 831138 MD5sum: d7536208f445177cb3eec17ee32210ee SHA1: e202a218c26ddf6218e2d574bf98f947e113485d SHA256: 6543330476331b540c9f58f3332820b1a405032cb1d331cd05faff76e3ef420e 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: amd64 Maintainer: Sergey Dryabzhinsky Installed-Size: 13482 Depends: libc6 (>= 2.14), 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/amd64/python3.6-dedupsqlfs/python3.6-dedupsqlfs-binary_1.2.948-0rusoft7.4~16.04.1_amd64.deb Size: 2805752 MD5sum: 5f58e30c0e999ee2ab9c295ee5e4367b SHA1: 70b2a9f555e6f4f87a8feef34162a3aff8266933 SHA256: 54380560f4acee92c0217587663db03e9c1b2406b89f0bc62d565a8ef260a7d2 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: amd64 Maintainer: Sergey Dryabzhinsky Installed-Size: 3238 Depends: libc6 (>= 2.14), 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/amd64/python3.7-dedupsqlfs/python3.7-dedupsqlfs_1.2.948-0rusoft7.3~16.04.1_amd64.deb Size: 823414 MD5sum: c6731360cd71e14a3cbaf22865310b7a SHA1: efe9a12a4b6cc31587233e2fc5f43f2adf2bfcb2 SHA256: 296f03e16142d106559811041731a95b75ab0cbc140391cd68ebeb6fbc81709c 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: amd64 Maintainer: Sergey Dryabzhinsky Installed-Size: 13505 Depends: libc6 (>= 2.14), 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/amd64/python3.7-dedupsqlfs/python3.7-dedupsqlfs-binary_1.2.948-0rusoft7.3~16.04.1_amd64.deb Size: 2807682 MD5sum: da8a0cab020a73052440ae7e6f5a020a SHA1: b36bb5d50b2bae8cd3a38fcb0a9513f3e417b7ef SHA256: e63b4ba0e4d524f2b6fbd0fcdf7ffb5dc86c6f4221251674e027723d5e4c1dfe 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: amd64 Maintainer: Sergey Dryabzhinsky Installed-Size: 3192 Depends: libc6 (>= 2.14), 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/amd64/python3.8-dedupsqlfs/python3.8-dedupsqlfs_1.2.948-0rusoft7.3~16.04.1_amd64.deb Size: 818408 MD5sum: 3ec7ad318970ec7fc0ce2cc16239e10f SHA1: cc2508c8f515115d07c3a6d9c75832df854aed7e SHA256: 09e40f23f128b657767e8ebb54258b695c11b679c9c69ab771e89e50c692c9c0 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: amd64 Maintainer: Sergey Dryabzhinsky Installed-Size: 13372 Depends: libc6 (>= 2.14), 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/amd64/python3.8-dedupsqlfs/python3.8-dedupsqlfs-binary_1.2.948-0rusoft7.3~16.04.1_amd64.deb Size: 2879616 MD5sum: 29ce81c5ad4f147469f743fe1215c98d SHA1: b3dfef1e7e69470a253b1784e731bef0e44e77bb SHA256: 3e951ba4c1047a5fa78ab6b1ee661e68caeb270e2a0f8fb56733df8fdb2a49c4 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.