Package: python3.6-dedupsqlfs Version: 1.2.948-0rusoft7.4~14.04.1 Architecture: i386 Maintainer: Sergey Dryabzhinsky Installed-Size: 3005 Depends: libc6 (>= 2.4), libgcc1 (>= 1:4.1.1), 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-trusty/i386/python3.6-dedupsqlfs/python3.6-dedupsqlfs_1.2.948-0rusoft7.4~14.04.1_i386.deb Size: 799580 MD5sum: 89e9eef8191ee3d3d9f424cd36a5ab2b SHA1: 20579b5a0129d012b8e5e40fdc8f1485852e5325 SHA256: e52d3cf9251ba28b0c68ae8bf3cabe9eeed881d2e1d29a180167b77b1379840f 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~14.04.1 Architecture: i386 Maintainer: Sergey Dryabzhinsky Installed-Size: 12287 Depends: libc6 (>= 2.4), libgcc1 (>= 1:4.1.1), 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-trusty/i386/python3.6-dedupsqlfs/python3.6-dedupsqlfs-binary_1.2.948-0rusoft7.4~14.04.1_i386.deb Size: 2607990 MD5sum: c3172d97514b55ab16c6cf7b5942b3c4 SHA1: 13983e56390ee3e4a7bbdb3e3232f59b494adc1f SHA256: 17a05f09f8d1ecc87bbe15cc46e2320ec924cc0ae12404938f9f4443413264b2 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~14.04.1 Architecture: i386 Maintainer: Sergey Dryabzhinsky Installed-Size: 3039 Depends: libc6 (>= 2.4), libgcc1 (>= 1:4.1.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-trusty/i386/python3.7-dedupsqlfs/python3.7-dedupsqlfs_1.2.948-0rusoft7.3~14.04.1_i386.deb Size: 802844 MD5sum: 722af679f86a2504be72c0fbee55b921 SHA1: 1165f59308bfe0139299eea40d030a3febc930cc SHA256: 39bcc63535b7262d76e50bd99d103ecaf9c643f4c17ec1c7a810cc9b234fb5e9 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~14.04.1 Architecture: i386 Maintainer: Sergey Dryabzhinsky Installed-Size: 12280 Depends: libc6 (>= 2.4), libgcc1 (>= 1:4.1.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-trusty/i386/python3.7-dedupsqlfs/python3.7-dedupsqlfs-binary_1.2.948-0rusoft7.3~14.04.1_i386.deb Size: 2632946 MD5sum: 2ebbaf28648ea7a0353141729883de61 SHA1: 9575a9bd56015be62be9e697357f1afdcd9aaf9d SHA256: 7653ff68c5c2b00f435ccc67eaa8083e467803d27f8ca366bf5cb15c3db30fb7 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~14.04.1 Architecture: i386 Maintainer: Sergey Dryabzhinsky Installed-Size: 3003 Depends: libc6 (>= 2.4), libgcc1 (>= 1:4.1.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-trusty/i386/python3.8-dedupsqlfs/python3.8-dedupsqlfs_1.2.948-0rusoft7.3~14.04.1_i386.deb Size: 801734 MD5sum: 44592cbc145cc8322d26874447fb351c SHA1: 3e5d2c3a2a015c13b33a4322004c86f8f913e8bf SHA256: 3e43b72944a8ce0f10d2f848ca489c97a35762f94dc6b280a97dea65120aa352 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~14.04.1 Architecture: i386 Maintainer: Sergey Dryabzhinsky Installed-Size: 11744 Depends: libc6 (>= 2.4), libgcc1 (>= 1:4.1.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-trusty/i386/python3.8-dedupsqlfs/python3.8-dedupsqlfs-binary_1.2.948-0rusoft7.3~14.04.1_i386.deb Size: 2597996 MD5sum: 67783076a460b9a6d552e632b91c575f SHA1: 1c89af8b8310c467c23c0f9e0e1dd2867c706f9a SHA256: 664cd98c7fa8dbd21eb9ec12506ff20a6d5d7575b0cf06ddefb41fd6560ffe0b 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.