| Key | Value |
|---|---|
| FileName | ./usr/lib/python3.10/site-packages/duplicity/_librsync.cpython-310-i386-linux-gnu.so |
| FileSize | 15680 |
| MD5 | 9281009F2BDED8773331956CFAE097F1 |
| SHA-1 | 03C7161C06379BFE907D857B03E99C48C6A5ABFF |
| SHA-256 | EC546D1E324502D501CE5409A52D453D6E4EAD71E28C4A5486FFF4EC66311286 |
| SSDEEP | 192:8rN8Wk2VjCIo3hX3Qgc2E5Jn9s1xvakzvJBdXZzXovVmfIqIDj436p2:A46UggWW15xzB7XR4Fj43n |
| TLSH | T19862D683B782CDF1F0A296F5945F2315DB32D12A52B3C2D37F1837896C226949E1636D |
| hashlookup:parent-total | 1 |
| hashlookup:trust | 55 |
The searched file hash is included in 1 parent files which include package known and seen by metalookup. A sample is included below:
| Key | Value |
|---|---|
| MD5 | 10B621FD1F332B6A1F655DA520097F32 |
| PackageArch | i586 |
| PackageDescription | Duplicity incrementally backs up files and directory by encrypting tar-format volumes with GnuPG and uploading them to a remote (or local) file server. In theory many remote backends are possible; right now local, ssh/scp, ftp, and rsync backends are written. Because duplicity uses librsync, the incremental archives are space efficient and only record the parts of files that have changed since the last backup. Currently duplicity supports deleted files, full unix permissions, directories, symbolic links, fifos, etc., but not hard links. |
| PackageMaintainer | umeabot <umeabot> |
| PackageName | duplicity |
| PackageRelease | 3.mga9 |
| PackageVersion | 0.8.21 |
| SHA-1 | 533D9DEBFA72FA940BB6B88AC977A2DD25C11434 |
| SHA-256 | 6D3B8C1229F3F6D8DD1ACE0895B3C32255073E0F674CE03EA21852B1CAD208EE |