knot-resolver_5.7.0-cznic.1_amd64.deb and Packages, md5sum mismatch

[bobykus31]

md5sum of https://download.opensuse.org/repositories/home:/CZ-NIC:/knot-resolver-latest/xUbuntu_22.04/amd64/knot-resolver_5.7.0-cznic.1_amd64.deb is

md5sum knot-resolver_5.7.0-cznic.1_amd64.deb b499935ecfbfbe8c0800cddddc84a4a9 knot-resolver_5.7.0-cznic.1_amd64.deb

Package: **knot-resolver**
Version: 5.7.0-cznic.1
Architecture: **amd64**
Maintainer: Knot Resolver <[email protected]>
Installed-Size: 1048
Depends: adduser, dns-root-data, systemd, libc6 (>= 2.34), libcap-ng0 (>= 0.7.9), libdnssec8 (>= 3.1.0), libedit2 (>= 2.11-20080614-0), libgcc-s1 (>= 3.3.1), libgnutls30 (>= 3.7.2), libjemalloc2 (>= 2.1.1), libknot12 (>= 3.1.0), liblmdb0 (>= 0.9.9), libluajit-5.1-2 (>= 2.0.4+dfsg), libnghttp2-14 (>= 1.3.0), libstdc++6 (>= 5), libsystemd0 (>= 227), libuv1 (>= 1.7.0), libzscanner4 (>= 3.1.0)
Recommends: lua-basexx, lua-cqueues, lua-http, lua-psl
Suggests: knot-resolver-module-http
Breaks: libkres9 (<< 3.2.1-2)
Replaces: libkres9 (<< 3.2.1-2)
Filename: amd64/knot-resolver_5.7.0-cznic.1_amd64.deb
Size: 346568
MD5sum: **6a0aab0ad0d8e5f9bf79afd904c8c78f**
SHA1: 447e3aaf84839d1824e063e10a3b449ca920e1e6
SHA256: bca49480d98030ded758f44757aecfe6f823dfbf115e53b91017f91742cfbad8
Section: net
Priority: optional
Homepage: https://www.knot-resolver.cz/
Description: caching, DNSSEC-validating DNS resolver
 The Knot Resolver is a caching full resolver implementation
 written in C and LuaJIT, including both a resolver library and a
 daemon. Modular architecture of the library keeps the core tiny and
 efficient, and provides a state-machine like API for
 extensions. There are three built-in modules - iterator, cache,
 validator, and many external.
 .
 The Lua modules, switchable and shareable cache, and fast FFI
 bindings makes it great to tap into resolution process, or be used
 for your recursive DNS service. It's the OpenResty of DNS.
 .
 The server adopts a different scaling strategy than the rest of the
 DNS recursors - no threading, shared-nothing architecture (except
 MVCC cache that may be shared). You can start and stop additional
 nodes depending on the contention without downtime.

6a0aab0ad0d8e5f9bf79afd904c8c78f in Package vs b499935ecfbfbe8c0800cddddc84a4a9 in reality