Keep the more important stuff outlining how to get to the sources first since the 'signatures' section will be extended. Signed-off-by: Peter Krempa <pkrempa(a)redhat.com&gt; --- docs/downloads.html.in | 28 ++++++++++++++-------------- 1 file changed, 14 insertions(+), 14 deletions(-) diff --git a/docs/downloads.html.in b/docs/downloads.html.in index aa0bb23d45..f3152d7557 100644 --- a/docs/downloads.html.in +++ b/docs/downloads.html.in @@ -493,20 +493,6 @@ <li><a href="https://libvirt.org/sources/">libvirt.org HTTPS server</a></li> </ul> - <h2><a id="keys">Signing keys</a></h2> - - <p> - Source RPM packages and tarballs for libvirt and libvirt-python published - on this project site are signed with a GPG signature. You should always - verify the package signature before using the source to compile binary - packages. The following key is currently used to generate the GPG - signatures: - </p> - <pre> -pub 4096R/10084C9C 2020-07-20 Jiří Denemark &amp;lt;jdenemar(a)redhat.com&amp;gt; -Fingerprint=453B 6531 0595 5628 5547 1199 CA68 BE80 1008 4C9C -</pre> - <h2><a id="schedule">Primary release schedule</a></h2> <p> @@ -615,5 +601,19 @@ git clone git://libvirt.org/[module name].git</pre> <a href="https://github.com/libvirt/">https://github.com/libvir... <a href="https://gitlab.com/libvirt/libvirt">https://gitlab.com... + <h2><a id="keys">Signing keys</a></h2> + + <p> + Source RPM packages and tarballs for libvirt and libvirt-python published + on this project site are signed with a GPG signature. You should always + verify the package signature before using the source to compile binary + packages. The following key is currently used to generate the GPG + signatures: + </p> + <pre> +pub 4096R/10084C9C 2020-07-20 Jiří Denemark &amp;lt;jdenemar(a)redhat.com&amp;gt; +Fingerprint=453B 6531 0595 5628 5547 1199 CA68 BE80 1008 4C9C +</pre> + </body> </html> -- 2.29.2