Explicitly sort pages that list other pages using meta(date).

Let's see if this helps fixing weird issues I see when building
on my local Jenkins (old news showing up before new ones) that
break reproducibility.

Also, fallback to sorting by path: some of our old security advisories have the
exact same publication name, so without any means of disambiguation, the
resulting sort order is random.

wiki/src/index.html

@@ -41,7 +41,7 @@ It aims at preserving your <strong>privacy</strong> and
 
 <h1>News</h1>
 
-[[!inline pages="page(news/*) and !news/*/* and !news/discussion and (currentlang() or news/report_2* or news/version_0* or news/test_0* or news/test_*-rc?)" show="2" feeds="no" archive="yes" sort="age"]]
+[[!inline pages="page(news/*) and !news/*/* and !news/discussion and (currentlang() or news/report_2* or news/version_0* or news/test_0* or news/test_*-rc?)" show="2" feeds="no" archive="yes" sort="-meta(date) age -path"]]
 
 <p>See [[News]] for more.</p>
 
@@ -51,7 +51,7 @@ It aims at preserving your <strong>privacy</strong> and
 
 <h1>Security</h1>
 
-[[!inline pages="page(security/*) and !security/audits and !security/audits.* and !security/audits/* and !security/*/* and !security/discussion and currentlang()" show="2" feeds="no" archive="yes" sort="age"]]
+[[!inline pages="page(security/*) and !security/audits and !security/audits.* and !security/audits/* and !security/*/* and !security/discussion and currentlang()" show="2" feeds="no" archive="yes" sort="-meta(date) age -path"]]
 
 <p>See [[Security]] for more.</p>
 

wiki/src/news.html

@@ -18,6 +18,6 @@
 
 </ul>
 
-[[!inline pages="page(news/*) and !news/*/* and !news/discussion and (currentlang() or news/report_2* or news/version_0* or news/test_0* or news/test_*-rc?)" show="10" sort="age"]]
+[[!inline pages="page(news/*) and !news/*/* and !news/discussion and (currentlang() or news/report_2* or news/version_0* or news/test_0* or news/test_*-rc?)" show="10" sort="-meta(date) age -path"]]
 [[!inline pages="page(news/*) and !news/*/* and !news/discussion and (currentlang() or news/report_2* or news/version_0* or news/test_0* or news/test_*-rc?) and tagged(announce)"
-show="10" feeds="yes" feedonly="yes" feedfile="emails" sort="age"]]
+show="10" feeds="yes" feedonly="yes" feedfile="emails" sort="-meta(date) age -path"]]

wiki/src/security.mdwn

@@ -3,7 +3,7 @@
 [[!toc levels=3]]
 
 [[!inline pages="page(security/*) and !security/audits and !security/audits.* and !security/audits/* and currentlang()"
-actions=no archive=yes feedonly=yes show=10 sort="age"]]
+actions=no archive=yes feedonly=yes show=10 sort="-meta(date) age -path"]]
 
 Since Tails is based on Debian, it takes advantage of all the work done by the
 Debian security team. As quoted from <http://security.debian.org/>:
@@ -26,7 +26,7 @@ Debian.
 [[!inline pages="page(security/*) and ! tagged(security/probable)
 and !security/audits and !security/audits.* and !security/audits/*
 and ! tagged(security/fixed) and currentlang() and created_after(security/Numerous_security_holes_in_1.2)"
-actions=no archive=yes feeds=no show=0 sort="age"]]
+actions=no archive=yes feeds=no show=0 sort="-meta(date) age -path"]]
 
 # Probable holes
 
@@ -35,7 +35,7 @@ applications is done, information leakages at the protocol level
 should be considered as − at the very least − possible.
 
 [[!inline pages="page(security/*) and tagged(security/probable) and currentlang()"
-actions=no archive=yes feeds=no show=0 sort="age"]]
+actions=no archive=yes feeds=no show=0 sort="-meta(date) age -path"]]
 
 # Fixed holes
 
@@ -43,7 +43,7 @@ actions=no archive=yes feeds=no show=0 sort="age"]]
 Please carefully read the "Affected versions" sections below.
 
 [[!inline pages="page(security/*) and tagged(security/fixed) and (currentlang() or security/Numerous_security_holes_in_0*)"
-actions=no archive=yes feeds=no show=0 sort="age"]]
+actions=no archive=yes feeds=no show=0 sort="-meta(date) age -path"]]
 
 # Audits