Remove outdated license text. See COPYING and the description
at http://liero.be/ for more information.

--- a/data/LIEROENG.TXT
+++ b/data/LIEROENG.TXT
@@ -11,14 +11,6 @@
 -----------------------------------------------------------------------------
 
 GENERAL STUFF
-
-	Liero is freeware. What that means is that you don't have to pay
-	for it and using it has not been restricted in any way. You may
-        distribute it to anyone and anyhow WITHOUT ANY CHANGES MADE TO IT'S 
-	CONTAINMENTS.
-
-	The source code of this game is not distributed freely (neither
-        commercially). So if you thought that maybe you could... forget it. 
 	
 	Liero is a wormgame with weapons for 2 players. The object of the
 	game is definately what you think it is. Liero is excellent for 
--- a/data/LIERO.TXT
+++ b/data/LIERO.TXT
@@ -12,15 +12,6 @@
 
 YLEISTŽ
 
-        Liero on freeware, mik„ tarkoittaa ett„ sen k„yt”st„ ei tarvitse
-        maksaa mit„„n eik„ k„ytt”„ ole rajoitettu mitenk„„n. Lieroa saa
-        kopioida kelle tahansa ja miten tahansa SISŽLT™Ž MITENKŽŽN
-        MUUTTAMATTA.
-
-        Todettakoon t„ss„ ett„ Lieron l„hdekoodi ei ole vapaassa (sen
-        enenp„„ kuin kaupallisessakaan) jakelussa. Joten jos ajattelit
-        ett„... niin j„t„ ajatukset sikseen.
-
         Liero on kahden pelattava aseellinen matosimulaatiopeli. Pelin
         p„„m„„r„n„ on ep„ilem„tt„ se mit„ luuletkin. Liero sopii
         erinomaisen hyvin aggressioiden purkuun ja kaverin rokitt„miseen
ht' method='get' action='/guix/log/tests/guix-build.sh'>
<input type='hidden' name='id' value='3fd15479af70e9f86f42af6dc0971ea123a6cb44'/><select name='qt'>
<option value='grep'>log msg</option>
<option value='author'>author</option>
<option value='committer'>committer</option>
<option value='range'>range</option>
</select>
<input class='txt' type='search' size='10' name='q' value=''/>
<input type='submit' value='search'/>
</form>
</td></tr></table>
<div class='path'>path: <a href='/guix/log/?id=3fd15479af70e9f86f42af6dc0971ea123a6cb44'>root</a>/<a href='/guix/log/tests?id=3fd15479af70e9f86f42af6dc0971ea123a6cb44'>tests</a>/<a href='/guix/log/tests/guix-build.sh?id=3fd15479af70e9f86f42af6dc0971ea123a6cb44'>guix-build.sh</a></div><div class='content'><table class='list nowrap'><tr class='nohover'><th class='left'>Age</th><th class='left'>Commit message (<a href='/guix/log/tests/guix-build.sh?id=3fd15479af70e9f86f42af6dc0971ea123a6cb44&amp;showmsg=1'>Expand</a>)</th><th class='left'>Author</th></tr>
<tr><td><span title='2023-08-17 17:33:53 +0200'>2023-08-17</span></td><td><a href='/guix/commit/tests/guix-build.sh?id=3363ff1867bb02c4aa4955db917ef1d67f2c47e6'>ui: 'load*' accepts /dev/fd/N files pointing to a pipe.</a><span class='msg-avail'>...<span class='msg-tooltip'>This allows users to write Bash commands like:

  guix time-machine -C &lt;(echo %default-channels) -- ...

or:

  guix build -m &lt;(echo '(specifications-&gt;manifest (list "guile"))')

Previously, on GNU/Linux, they would fail with:

  error: failed to load '/dev/fd/63': No such file or directory

* guix/ui.scm (try-canonicalize-path): New procedure.
(load*): Use it.
* tests/guix-build.sh: Test 'guix build -m' with a /dev/fd/N file.
</span></span></td><td>Ludovic Courtès</td></tr>
<tr><td><span title='2023-04-28 19:50:36 +0200'>2023-04-28</span></td><td><a href='/guix/commit/tests/guix-build.sh?id=5c26e69118128f6ef162cabddfe5726f03abe4ae'>tests: guix-build.sh: Don't use hidden gcc for transformation tests.</a><span class='msg-avail'>...<span class='msg-tooltip'>* tests/guix-build.sh: Do not try to rewrite gcc, it is hidden and so will not
be rewritten, as per eee95b5a879b7096dffd533f24107cf8926b621e.  Instead, try
to build grep with coreutils rewritten to hello.

Signed-off-by: Ludovic Courtès &lt;ludo@gnu.org&gt;
</span></span></td><td>Josselin Poiret</td></tr>
<tr><td><span title='2023-04-21 16:16:38 +0200'>2023-04-21</span></td><td><a href='/guix/commit/tests/guix-build.sh?id=37dd69b44511dc73eb04bdebe8d82c9a0386338e'>tests: Fix checks for expected failures.</a><span class='msg-avail'>...<span class='msg-tooltip'>Addresses &lt;https://issues.guix.gnu.org/62406&gt;.

With 'set -e', a return status inverted with '!' does not cause the shell to
exit immediately.  Instead use '&amp;&amp; false' to indicate an expected failure.

* tests/guix-archive.sh, tests/guix-build-branch.sh, tests/guix-build.sh,
tests/guix-daemon.sh, tests/guix-download.sh,
tests/guix-environment-container.sh, tests/guix-environment.sh,
tests/guix-gc.sh, tests/guix-git-authenticate.sh, tests/guix-graph.sh,
tests/guix-hash.sh, tests/guix-home.sh, tests/guix-pack-relocatable.sh,
tests/guix-pack.sh, tests/guix-package-aliases.sh, tests/guix-package-net.sh,
tests/guix-package.sh, tests/guix-refresh.sh, tests/guix-shell.sh,
tests/guix-style.sh, tests/guix-system.sh: Replace uses of '! ...' with
'... &amp;&amp; false' or `test ! ...` as appropriate.

Signed-off-by: Ludovic Courtès &lt;ludo@gnu.org&gt;
</span></span></td><td>Eric Bavier</td></tr>