- Sep 14, 2021
-
-
anarcat authored
The support page is the go-to page for the "how to get help" question, which previously was hidden inside the TPA-RFC-2 standard. This basically copies that part of the TPA-RFC-2 policy, but could eventually diverge without needing to update the policy, for informal stuff. I started working on this page while trying to address team#40382 ("document the triage process"), but I'm not actually sure triage documentation should go there, as this page feels more targeted at users, and only users. howto/incident-response.md would seem like a better space for this. Also, this is a toplevel page because it's more important than everything else, so it warrants its own special space.
-
anarcat authored
This is non-normative, so doesn't need discussion.
-
anarcat authored
-
anarcat authored
-
anarcat authored
-
- Sep 10, 2021
-
-
anarcat authored
-
- Sep 09, 2021
-
-
anarcat authored
-
anarcat authored
-
anarcat authored
-
anarcat authored
-
anarcat authored
-
anarcat authored
-
anarcat authored
-
anarcat authored
The bootstrap starts from `/target`, which is unusual in the FHS, but it's better to live with what's out there than the ideal world.
-
anarcat authored
-
anarcat authored
-
anarcat authored
-
- Sep 08, 2021
- Sep 07, 2021
- Sep 03, 2021
-
-
anarcat authored
-
anarcat authored
-
anarcat authored
-
anarcat authored
-
anarcat authored
Those do not work for people not using TB, while the reverse was working for both. The change was also hard to decode: it turns out it only changed to links to point to the roadmap items instead of the issues.
-
anarcat authored
-
- Sep 02, 2021
-
-
anarcat authored
-
anarcat authored
-
anarcat authored
-
anarcat authored
-
anarcat authored
-
anarcat authored
-
anarcat authored
When the `bullseye.mdwn` page was renamed (to `bullseye.md`) in this commit: commit 6fe448dc Author: Antoine Beaupré <anarcat@debian.org> Date: Wed Sep 1 11:33:12 2021 -0400 rename bullseye upgrade procedure file This is the only .mdwn file out there, strangely. Let's hope this is going to fix the garbled display issues, where code blocks show up with <pre><code> blobs. diff --git a/howto/upgrades/bullseye.mdwn b/howto/upgrades/bullseye.md similarity index 100% rename from howto/upgrades/bullseye.mdwn rename to howto/upgrades/bullseye.md ... the CI failed, because the hook couldn't find the `.mdwn` file to check: https://gitlab.torproject.org/tpo/tpa/wiki-replica/-/jobs/35296 The actual error was: $ ./bin/mdl-wrapper $(cat changed-files.txt) checking file howto/upgrades/bullseye.md... checking howto/upgrades/bullseye.mdwn... /usr/lib/ruby/gems/2.6.0/gems/mdl-0.11.0/lib/mdl/doc.rb:50:in `read': No such file or directory @ rb_sysopen - howto/upgrades/bullseye.mdwn (Errno::ENOENT) from /usr/lib/ruby/gems/2.6.0/gems/mdl-0.11.0/lib/mdl/doc.rb:50:in `new_from_file' from /usr/lib/ruby/gems/2.6.0/gems/mdl-0.11.0/lib/mdl.rb:82:in `block in run' from /usr/lib/ruby/gems/2.6.0/gems/mdl-0.11.0/lib/mdl.rb:80:in `each' from /usr/lib/ruby/gems/2.6.0/gems/mdl-0.11.0/lib/mdl.rb:80:in `run' from /usr/lib/ruby/gems/2.6.0/gems/mdl-0.11.0/bin/mdl:10:in `<top (required)>' from /usr/bin/mdl:23:in `load' from /usr/bin/mdl:23:in `<main>' Cleaning up file based variables 00:03 ERROR: Job failed: exit code 1 In our code, we assume that if a path is not a file, it's a directory, but that's not quite right: it could also be just missing! So handle that other case more elegantly.
-
anarcat authored
It's where I looked for it first, and the gitlab page is waay to long. We keep a pointer anyways, so that people can find it in both places.
-
anarcat authored
Seems like this may fix team#40376
-
anarcat authored
-