summaryrefslogtreecommitdiffstats
Commit message (Collapse)AuthorAgeFilesLines
* Import updated tailslibbugfix/16273-pkexec-errorAlan2019-03-211-0/+0
|
* ASP: always ask for admin passwordAlan2019-03-211-1/+1
| | | | | | | Else, when started from persistence-setup, tails-persistence-setup password (inexistant) is prompted. Will-fix: #16273
* ASP: set SHELL environnment variable required by pkexecAlan2019-03-211-1/+1
| | | | Will-fix: #16273
* Release process: document bulk-edits for Redmine (Closes: #16588)intrigeri2019-03-211-1/+8
|
* Release process: clarify valid, expected results (Closes: #16581)intrigeri2019-03-211-1/+2
| | | | | | | When preparing a bugfix release, or when one has correctly resolved merged conflicts in the previous step, this operation is a no-op. That's fine. But let's keep it around as a fail-safe, in case a mistake was made during the merge conflict resolution previously.
* Release process: make profiling independent from re-partitioning (Closes: ↵intrigeri2019-03-211-1/+3
| | | | #16582)
* Release process: avoid some back'n'forth (Closes: #16584)intrigeri2019-03-211-6/+3
|
* Release process: clarify timestamp-related checks (Closes: #16599)intrigeri2019-03-211-2/+2
|
* Release process: mention need for encryption when sharing the pad (Closes: ↵intrigeri2019-03-211-1/+1
| | | | #16578)
* Release process: fix broken link (Closes: #16579)intrigeri2019-03-211-1/+1
|
* Release process: update transmission removal instructions (Closes: #16593)intrigeri2019-03-211-3/+5
|
* Release process: avoid the need to reason about compression settings ↵intrigeri2019-03-211-0/+2
| | | | (Closes: #16583)
* Release process: make Twitter section more infra-bug-proof (Closes: #16587)intrigeri2019-03-211-1/+1
|
* Release process: clarify where one should go through tickets from (Closes: ↵intrigeri2019-03-211-0/+1
| | | | #16589)
* Release process: clarify which tech writer the RM should contact (Closes: ↵intrigeri2019-03-211-1/+1
| | | | #16590)
* Release process: clarify how to ensure the release announce is sent by email ↵intrigeri2019-03-211-5/+8
| | | | (Closes: #16591)
* Release process: remove useless and confusing implementation detail (refs: ↵intrigeri2019-03-211-1/+1
| | | | #16591)
* Release process: drop torsocks (Closes: #16594)intrigeri2019-03-211-1/+1
| | | | | Most RMs should already have Git/SSH configuration to use torsocks for our canonical Git repo.
* Release process: fix typo (Closes: #16595)intrigeri2019-03-211-1/+1
|
* Release process: make more links copy-paste-able (Closes: #16596)intrigeri2019-03-211-3/+3
|
* updated PO filesIkiWiki2019-03-206-57/+42
|
* Merge remote-tracking branch 'origin/master'sajolida2019-03-2015-108/+126
|\
| * updated PO filesIkiWiki2019-03-206-14/+44
| |
| * Fix indentation.intrigeri2019-03-201-3/+3
| |
| * Drop deleted role.intrigeri2019-03-201-1/+0
| |
| * Merge remote-tracking branch 'origin/master'intrigeri2019-03-2010-141/+105
| |\
| | * updated PO filesIkiWiki2019-03-206-90/+78
| | |
| * | Add another GNOME bug migrated to GitLab.intrigeri2019-03-201-0/+1
| | |
* | | Remove sentence related to donation campaignsajolida2019-03-201-4/+0
| | |
* | | Update number of bootssajolida2019-03-201-1/+1
| |/ |/|
* | Add anchorsajolida2019-03-201-0/+2
| |
* | Merge branch 'master' of d53ykjpeekuikgoq.onion:tailsUlrike Uhlig2019-03-201-30/+83
|\ \ | |/
| * [fr] Fix PO syntax.intrigeri2019-03-201-2/+2
| |
| * Merge remote-tracking branch 'xin/translate/3.13'intrigeri2019-03-201-29/+82
| |\
| | * Merge remote-tracking branch 'origin' into translate/3.13xin2019-03-2059-695/+1433
| | |\
| | * | [fr] translate 3.13 newsxin2019-03-191-33/+84
| | | |
* | | | Delete role merged with FT.Ulrike Uhlig2019-03-201-51/+0
| | | |
* | | | Add what's not in the scope of Debian maintenance.Ulrike Uhlig2019-03-201-0/+7
| | | |
* | | | Explicit that Debian maintainer does not need to attend FTUlrike Uhlig2019-03-201-5/+5
| | | |
* | | | Add Debian role to FT role. Simplify.Ulrike Uhlig2019-03-201-0/+15
| | | |
* | | | Merge branch 'master' of d53ykjpeekuikgoq.onion:tailsUlrike Uhlig2019-03-20143-8694/+9176
|\ \ \ \ | |/ / /
| * | | Directly verify what we mean to (refs: #12629)intrigeri2019-03-201-6/+6
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | When I automated this step, I was confused due to the problem I've fixed in the previous commit, so I wrote code that checks the published products against the IDF, while here we want to check the locally built products against the IDF. Granted, here again, this was valid *transitively*, because of the implicit (and so far correct) assumption that, at this point, we've already verified that what we have built matches SHA512SUMS.txt, and that the published products match SHA512SUMS.txt too, so both sets of products are equivalent at this point. Still, for the same reason as in the previous commit, let's simplify and directly do the check we want.
| * | | Make verification process more straightforward (refs: #12629)intrigeri2019-03-201-2/+17
| | |/ | |/| | | | | | | | | | | | | | | | | | | | | | | | | | | | The previous instructions did the check we want… *transitively*: we checked that the published products matched SHA512SUMS.txt, in a step that claims to compare them with locally built products; this was only valid because of the implicit (and so far correct) assumption that, at this point, we've already verified that what you have built matches SHA512SUMS.txt. This adds complexity and makes it needlessly hard to understand and review this process. Instead, let's directly do the check we want.
| * | Custom APT repo: drop obsolete instruction (refs: #16576).intrigeri2019-03-201-4/+0
| | | | | | | | | | | | | | | | | | | | | | | | The version of reprepro we currently run does not choke on .buildinfo files. The only remaining issue is that reprepro leaves these files in the "incoming" directory after successfully importing a package, but that should be dealt with elsewhere (e.g. on the infra side) — if at all — instead of requiring everyone who uploads a package to do some extra work.
| * | Custom APT repo: drop obsolete instruction (refs: #16576).intrigeri2019-03-201-1/+1
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | dbgsym are supported and imported just fine into our custom APT repo. For example we currently have: thunderbird-dbgsym | 1:60.5.1-1~deb9u1.0tails1 | tor+http://jenw7xbd6tf7vfhp.onion stable/main amd64 Packages thunderbird-dbgsym | 1:60.5.1-1~deb9u1.0tails1 | tor+http://jenw7xbd6tf7vfhp.onion devel/main amd64 Packages thunderbird-dbgsym | 1:60.3.0-1~deb9u1.0tails1 | tor+http://jenw7xbd6tf7vfhp.onion testing/main amd64 Packages
| * | updated PO filesIkiWiki2019-03-1930-341/+1182
| | |
| * | Merge branch 'web/release-3.13' (Fix-committed: #16470, #16565).Cyril Brulebois2019-03-19108-8455/+8073
| |\ \
| | * \ Merge branch 'web/16398-3.13-release-notes' into web/release-3.13sajolida2019-03-196-20/+98
| | |\ \ | | | |/ | | |/|
| | | * Merge branch 'web/16470-better-install-vs-upgrade' into ↵sajolida2019-03-193-20/+59
| | | |\ | | | | | | | | | | | | | | | web/16398-3.13-release-notes (Will-fix: #16470)
| | | | * Remove useless level of <ul>sajolida2019-03-192-8/+4
| | | | |