Package: python3.6-dedupsqlfs Version: 1.2.948-0rusoft7.4~debian7.1 Architecture: i386 Maintainer: Sergey Dryabzhinsky Installed-Size: 3125 Depends: libc6 (>= 2.4), libgcc1 (>= 1:4.1.1), liblzma5 (>= 5.1.1alpha+20120614), liblzo2-2 (>= 2.02), libsnappy1, 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/debian-wheezy/i386/python3.6-dedupsqlfs/python3.6-dedupsqlfs_1.2.948-0rusoft7.4~debian7.1_i386.deb Size: 833912 MD5sum: e02ed8d51187cfc02a6a73ff2791312e SHA1: bb8ee74130a290ddfb21ddd9b477a159868db424 SHA256: 037eee795967c6ba7459ff393b74052912953b8f3cf8413203abe0b56220dc73 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~debian7.1 Architecture: i386 Maintainer: Sergey Dryabzhinsky Installed-Size: 12971 Depends: libc6 (>= 2.4), libgcc1 (>= 1:4.1.1), liblzma5 (>= 5.1.1alpha+20120614), liblzo2-2 (>= 2.02), libsnappy1, 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/debian-wheezy/i386/python3.6-dedupsqlfs/python3.6-dedupsqlfs-binary_1.2.948-0rusoft7.4~debian7.1_i386.deb Size: 2732660 MD5sum: 7e5ca405dbe0b6410bf03b97992ca763 SHA1: 88272e56cc5bb5dbe69a2d601290b78f2c9b6154 SHA256: 4c38e49decff698135c62e13d27356953cb03f8ed9b26aaaeebdef32190b2839 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~debian7.1 Architecture: i386 Maintainer: Sergey Dryabzhinsky Installed-Size: 3168 Depends: libc6 (>= 2.4), libgcc1 (>= 1:4.1.1), liblzma5 (>= 5.1.1alpha+20120614), liblzo2-2 (>= 2.02), libsnappy1, 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/debian-wheezy/i386/python3.7-dedupsqlfs/python3.7-dedupsqlfs_1.2.948-0rusoft7.3~debian7.1_i386.deb Size: 838674 MD5sum: 042a3e2c3f7b256b8f6010e8c4d205a9 SHA1: 771b206636bb5e56e39b1334c7ff2c4fda039f36 SHA256: 193c11acbd4c97502859d2d1855d70304d4e5222fd390dfb60c4548f31e4e4a0 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~debian7.1 Architecture: i386 Maintainer: Sergey Dryabzhinsky Installed-Size: 13005 Depends: libc6 (>= 2.4), libgcc1 (>= 1:4.1.1), liblzma5 (>= 5.1.1alpha+20120614), liblzo2-2 (>= 2.02), libsnappy1, 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/debian-wheezy/i386/python3.7-dedupsqlfs/python3.7-dedupsqlfs-binary_1.2.948-0rusoft7.3~debian7.1_i386.deb Size: 2749420 MD5sum: 57f6998b330dfeb08ea619e7cbf30988 SHA1: f714d1542fe760794e0001cbdce9cc4010221864 SHA256: ad02d5ef8e28bfea76307b09b7dbf9015a45aa233ab79e53adc5188f9b4eaf20 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~debian7.1 Architecture: i386 Maintainer: Sergey Dryabzhinsky Installed-Size: 3128 Depends: libc6 (>= 2.4), libgcc1 (>= 1:4.1.1), liblzma5 (>= 5.1.1alpha+20120614), liblzo2-2 (>= 2.02), libsnappy1, 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/debian-wheezy/i386/python3.8-dedupsqlfs/python3.8-dedupsqlfs_1.2.948-0rusoft7.3~debian7.1_i386.deb Size: 832256 MD5sum: bbb3e6df7f94009b08f8b42b06f64964 SHA1: a0709d9ff8598edade5f433567c073f0e3866850 SHA256: fb6d0f19cdaf0f1b2bbb994a2d5c53f8c47a62b328cbd881c6ef2b06206db7b3 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~debian7.1 Architecture: i386 Maintainer: Sergey Dryabzhinsky Installed-Size: 11711 Depends: libc6 (>= 2.4), libgcc1 (>= 1:4.1.1), liblzma5 (>= 5.1.1alpha+20120614), liblzo2-2 (>= 2.02), libsnappy1, 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/debian-wheezy/i386/python3.8-dedupsqlfs/python3.8-dedupsqlfs-binary_1.2.948-0rusoft7.3~debian7.1_i386.deb Size: 2512058 MD5sum: ee27a7e5f0efcf6b8d9a7c12792b6510 SHA1: 027785ff7b11c807aad41000bcd4c3f43855b95e SHA256: 0cd2425ea593edfbdf8699e3d8b27a30cab48ec55275903c7e59494007d3b323 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.