logo

blog

My website can't be that messy, right? git clone https://anongit.hacktivis.me/git/blog.git/
commit: af1acb783d88d86d7a991350515d7e5d943bc202
parent 48e62299df5fb37f13c48e734b77703b74ee9e1b
Author: Haelwenn (lanodan) Monnier <contact@hacktivis.me>
Date:   Fri, 21 Feb 2025 21:07:40 +0100

/releases/ => https://distfiles.hacktivis.me/releases/

Diffstat:

Mprojects/badwolf.shtml4++--
Mprojects/utils-std.shtml8++++----
2 files changed, 6 insertions(+), 6 deletions(-)

diff --git a/projects/badwolf.shtml b/projects/badwolf.shtml @@ -47,13 +47,13 @@ <h2>Releases</h2> <ul> <li>From packages: <a href="https://repology.org/project/badwolf/versions">list of repositories</a></li> - <li>From source: <code><a href="/releases/<!--#echo var="baseName" -->.tar.gz"><!--#echo var="baseName" -->.tar.gz</a></code> (<a href="/releases/<!--#echo var="baseName" -->.tar.gz.sign">signify/minisign</a>) <a href="/releases/<!--#echo var="baseName" -->.txt">changelog</a></li> + <li>From source: <code><a href="https://distfiles.hacktivis.me/releases/<!--#echo var="baseName" -->.tar.gz"><!--#echo var="baseName" -->.tar.gz</a></code> (<a href="https://distfiles.hacktivis.me/releases/<!--#echo var="baseName" -->.tar.gz.sign">signify/minisign</a>) <a href="https://distfiles.hacktivis.me/releases/<!--#echo var="baseName" -->.txt">changelog</a></li> </ul> <p>BadWolf is using <a href="https://semver.org/spec/v2.0.0.html">Semantic Versioning</a> with considering that the User-Interface is part of the interface stabilisation. Release branches (ie. <code>1.0.x</code>) are supported for 6 months for any bug fixes and 2 years for security fixes.</p> <p> Tarball signature check: <a href="https://flak.tedunangst.com/post/signify">signify</a> (<a href="https://github.com/aperezdc/signify/">portable version maintained by Adrian Perez</a>) is the recommended tool to use. - You can find the key at <a href="/releases/signify/<!--#echo var="signifyName" -->.pub">/releases/signify/<!--#echo var="signifyName" -->.pub</a>, + You can find the key at <a href="https://distfiles.hacktivis.me/releases/signify/<!--#echo var="signifyName" -->.pub">https://distfiles.hacktivis.me/releases/signify/<!--#echo var="signifyName" -->.pub</a>, you can find more info about how I manage the keyset in: <a href="/articles/Bootstrapping%20signify%20for%20my%20assets">Bootstrapping signify for my assets</a>.<br /> The command to verify the tarball looks like this: <code><kbd>signify -V -p signify/<!--#echo var="signifyName" -->.pub -x <!--#echo var="baseName" -->.tar.gz.sign -m <!--#echo var="baseName" -->.tar.gz</kbd></code> diff --git a/projects/utils-std.shtml b/projects/utils-std.shtml @@ -45,9 +45,9 @@ <ul> <!--<li>From packages: <a href="https://repology.org/project/utils-std/versions">list of repositories</a></li>--> <li>From source: - <code><a href="/releases/utils-std/<!--#echo var="baseName" -->.tar.gz"><!--#echo var="baseName" -->.tar.gz</a></code> - (<a href="/releases/utils-std/<!--#echo var="baseName" -->.tar.gz.sign">signify/minisign</a>) - <a href="/releases/utils-std/<!--#echo var="baseName" -->.txt">changelog</a> + <code><a href="https://distfiles.hacktivis.me/releases/utils-std/<!--#echo var="baseName" -->.tar.gz"><!--#echo var="baseName" -->.tar.gz</a></code> + (<a href="https://distfiles.hacktivis.me/releases/utils-std/<!--#echo var="baseName" -->.tar.gz.sign">signify/minisign</a>) + <a href="https://distfiles.hacktivis.me/releases/utils-std/<!--#echo var="baseName" -->.txt">changelog</a> </li> </ul> <p> @@ -57,7 +57,7 @@ <p> Tarball signature check: <a href="https://flak.tedunangst.com/post/signify">signify</a> (<a href="https://github.com/aperezdc/signify/">portable version maintained by Adrian Perez</a>) is the recommended tool to use. - You can find the key at <a href="/releases/signify/<!--#echo var="signifyName" -->.pub">/releases/signify/<!--#echo var="signifyName" -->.pub</a>, + You can find the key at <a href="https://distfiles.hacktivis.me/releases/signify/<!--#echo var="signifyName" -->.pub">https://distfiles.hacktivis.me/releases/signify/<!--#echo var="signifyName" -->.pub</a>, you can find more info about how I manage the keyset in: <a href="/articles/Bootstrapping%20signify%20for%20my%20assets">Bootstrapping signify for my assets</a>.<br /> The command to verify the tarball looks like this: <code><kbd>signify -V -p signify/<!--#echo var="signifyName" -->.pub -x <!--#echo var="baseName" -->.tar.gz.sign -m <!--#echo var="baseName" -->.tar.gz</kbd></code>