As the message shows, the failure was at the point of verifying the packages after download and before it began the actual install. Nothing was installed since the verification failed..
Run the command again and it should actually complete after downloading that package and passing the verification step.
Using the command sudo dnf download texlive-scheme-full will download a package named texlive-scheme-full-11:svn54074-80.fc43.noarch
If instead using sudo dnf download texlive-scheme-full-* I get No package "texlive-scheme-full-svn54074-80.fc43.noarch.rpm" available
If I then run rpm --checksig -v texlive-scheme-full-svn54074-80.fc43.noarch.rpm it succeeds
but if I try the package name downloaded it fails. rpm --checksig -v texlive-scheme-full-11:svn54074-80.fc43.noarch.rpm
or rpm --checksig -v texlive-scheme-full-11:svn54074-80.fc43.noarch
It appears there may be something wrong in the metadata that identifies that package when downloaded and the wrong info is displayed on screen
It also is confusing that when using dnf download the package being downloaded is placed in the PWD and not in the dnf cache area. That really should not be unless you specify the location where it should be saved. This is what caused my error with the *.
dnf download -h tells that the default download location is the PWD, but it is not intuitively obvious that it the default behavior.
Someone pointed out that, because that particular package set is so large, running sudo dnf clean all would be a bit painful and it is probably unnecessary. If the file is really corrupt, dnf should detect that when you just rerun the original download command, without having to delete and redownload everything.
I don’t think there is a dnf command to flush just that one file from the download cache. If I were in that situation, I might try sudo rm /var/cache/libdnf5/fedora-fe4b228be7d3c150/packages/texlive-scheme-full-svn54074-80.fc43.noarch.rpm, since dnf was kind enough to provide the full path to the file with the apparent problem.
Of course, if you are getting a bad copy from the mirror (as opposed to a file that was corrupted in-transit), you might have to adjust what mirror you are using before you will be able to get a good copy.
Sorry about the poor initial advice. I defaulted to what I thought would be “easiest”, but different approaches have different trade-offs. I’ll scratch out my initial reply and link to this update.
You are comparing package names to file names, aren’t you? They differ by file extension already and –apparantly - by epoch (in order to avoid problems with the colon).
Thanks for all the comments and insights.
From a practical point of view my two-cent solution was to repeate the installation command:
sudo dnf install texlive-scheme-full
This time the download phase took few minuets (unlike the first try when it took 32 minuets to download all 4000 files) and then the installation started and completed seamlesly.