| +- public-package-0.1.tar.gz.blake2_256
| +- public-package-0.1.1.tar.gz.blake2_256
| +- public-package-0.2.tar.gz
- | +- public-package-0.2.tar.gz.asc
| +- public-package-0.2.tar.gz.sha256
| +- public-package-0.2.tar.gz.blake2_256
+-- private-package
| +- .internal
| +- .metadata.rec
| +- private-package-0.1.tar.gz
- | +- private-package-0.1.tar.gz.asc
| +- private-package-0.1.tar.gz.sha256
| +- private-package-0.1.tar.gz.blake2_256
|...
long time ago with MD5 checksum. @code{0.1.1} version is downloaded more
recently with BLAKE2b-256 checksum, also storing that checksum for
@code{0.1}. @code{0.2} version is downloaded tarball, having forced
-SHA256 and BLAKE2b-256 recalculated checksums. Also upstream has
-corresponding @file{.asc} signature file.
+SHA256 and BLAKE2b-256 recalculated checksums.
@file{private-package} is private package, because it contains
@file{.internal} file. It can be uploaded and queries to it are not