Fedora Checksum Tester
Fedora Checksum Tester is a little script that can automatically run checksum tests as defined in https://fedoraproject.org/wiki/QA:Testcase_Mediakit_Checksums.
Installation
The program is packed for PyPi, so you can install it easily using the pip command.
pip install --user fedora_checksum_tester
Usage
Navigate into the directory where you have downloaded the images to check and
run fedora_checksum_tester with those options. If you have not downloaded any
images to check, the program downloads the images automatically from Koji.
Options
--release : The release number of the Fedora compose, for which you want to download the images. Rawhide is used by default.
--compose : The compose identification. Mostly, this is a date in the form of YYYYMMDD except for the release candidates. If left out, the program connects to the release validation matrix and gets the number of the current compose. This is probably how this program will be used mostly.
--arch : Architecture for which to download the images. x86_64 used by default.
--variant : One possible variant, such as Cloud, Everything, Server, Spins, Workstation. If not chosen, the Everything will be used as default.
--subvariant : Can be used with Spins variant, to distinguish between various spins, such as KDE, LXCD, Xfce. If left out, all spins will be tested.
--type : Can be used with Server to distinguish between boot and dvd. If not selected, both images will be checked.
--purge : If set to True, all downloaded images will be deleted after the test has finished, independently of the result.
--forcedownload : Not yet implemented. Normally, if the script finds out that the requested image has already been downloaded, it will not download it again to save time and bandwidth. If you explicitely want to download it anyway, use True to download the image.
--report : If this is set to True, the script will report the results to the Wiki matrix automatically. Also see --user.
--user : The name of the user who reports the results. If left out, user donkey will be used.
Bugs
If you find a bug, report an issue at https://github.com/lruzicka/checksum-tester.
1 maintainer
Metadata
1 maintainer
Release files for fedora-checksum-tester 1.3
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | Actions |
|---|---|---|---|---|
| fedora_checksum_tester-1.3.tar.gz | 5.1 kB | Without provenance | Details for fedora_checksum_tester-1.3.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| fedora_checksum_tester-1.3-py3-none-any.whl | Python 3 | none | any | Details for fedora_checksum_tester-1.3-py3-none-any.whl |
Total release size: 23.1 kB
Release files / fedora_checksum_tester-1.3.tar.gz
| Download URL | fedora_checksum_tester-1.3.tar.gz |
|---|---|
| Size | 5.1 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
8fc04d53f607a67e6111209ab53c3ea918a090793ee215444c9e7418ebaed955
|
|
BLAKE2b-256 checksum How to use checksums |
d0f2f349c73d32ea03705ea8d7dc94084b6d48760ef9d47ac451173a6fc8cde7
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/3.1.1 pkginfo/1.5.0.1 requests/2.22.0 setuptools/44.0.0 requests-toolbelt/0.9.1 tqdm/4.41.1 CPython/3.7.6
|
Release files / fedora_checksum_tester-1.3-py3-none-any.whl
| Download URL | fedora_checksum_tester-1.3-py3-none-any.whl |
|---|---|
| Size | 17.9 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
09fc62e4188b6d6087deea656fe7d0aea21ec20a09bbc1ea55bd8fb9bd169dbe
|
|
BLAKE2b-256 checksum How to use checksums |
733ed8b4d47f15ac79ccbdd02dd0dfe3c0541479d6763693b117097ee2371265
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/3.1.1 pkginfo/1.5.0.1 requests/2.22.0 setuptools/44.0.0 requests-toolbelt/0.9.1 tqdm/4.41.1 CPython/3.7.6
|
Security for fedora-checksum-tester 1.3
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.
