- Mar 22, 2015
-
-
intrigeri authored
-
intrigeri authored
-
intrigeri authored
Fix-committed: #6394
-
intrigeri authored
Fix-committed: #9094
-
intrigeri authored
-
intrigeri authored
Fix-committed: #6558
-
intrigeri authored
Fix-committed: #8991
-
intrigeri authored
-
intrigeri authored
-
intrigeri authored
-
intrigeri authored
-
intrigeri authored
This is now done with an [[!inline]] directive.
-
intrigeri authored
-
intrigeri authored
-
kytv authored
-
intrigeri authored
-
intrigeri authored
-
intrigeri authored
It breaks parsechangelog.
-
intrigeri authored
-
127.0.0.1 authored
-
intrigeri authored
-
intrigeri authored
-
intrigeri authored
-
intrigeri authored
-
bertagaz authored
-
bertagaz authored
-
bertagaz authored
-
bertagaz authored
-
intrigeri authored
Fix-committed: #9070, #9071
-
intrigeri authored
-
intrigeri authored
-
intrigeri authored
-
intrigeri authored
We use *.changes above, so let's just do the same again.
-
intrigeri authored
-
intrigeri authored
We check their hashes anyway, but hey, why not. And anyway, otherwise this curl command doesn't work (unless one adds --location to honor redirect — to HTTPS — headers).
-
intrigeri authored
- Mar 21, 2015
-
-
intrigeri authored
Fix-committed: #8964, #6985
-
intrigeri authored
Closes: #9085
-
intrigeri authored
We've merged feature/8740-new-signing-key-phase-2 into stable a few days ago, so the code in stable/devel/etc. only trusts the new signing key, while the 1.3 UDF are still signed with our old signing key. Tails 1.3 trusts both the old and new signing keys, so this should be alright both for it and for anything that has feature/8740-new-signing-key-phase-2 merged in. Will-fix: #9085
-