Point links at the extant2000 GitLab group

The messenger repositories move from gitlab.com/paulhitt to
gitlab.com/extant2000. Old web and git URLs redirect; the relay's container
image path does not, so docker-compose.yml names the new registry path.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
This commit is contained in:
Paul Hitt
2026-09-28 14:38:57 -04:00
co-authored by Claude Opus 5.5
parent d53f6a81bb
commit 41dbfeb19d
4 changed files with 5 additions and 5 deletions
+1 -1
View File
@@ -1,6 +1,6 @@
# Why this repository pins flamenet-e2e
`.e2e-ref` is the commit of [flamenet-e2e](https://gitlab.com/paulhitt/flamenet-e2e)
`.e2e-ref` is the commit of [flamenet-e2e](https://gitlab.com/extant2000/flamenet-e2e)
whose protocol vectors the `unit-tests` job checks against. `AccountKdfTest`,
`PQVectorTest` and `PublishedVectorsTest` all read them.
+2 -2
View File
@@ -73,7 +73,7 @@ unit-tests:
# `flamenet-e2e` is public, so no credentials are needed.
- FLAMENET_E2E_PIN=$(cat "$CI_PROJECT_DIR/.e2e-ref")
- rm -rf "$CI_PROJECT_DIR/.ci-vectors"
- git clone -q https://gitlab.com/paulhitt/flamenet-e2e.git "$CI_PROJECT_DIR/.ci-vectors"
- git clone -q https://gitlab.com/extant2000/flamenet-e2e.git "$CI_PROJECT_DIR/.ci-vectors"
- git -C "$CI_PROJECT_DIR/.ci-vectors" checkout -q "$FLAMENET_E2E_PIN"
- export FLAMENET_VECTORS="$CI_PROJECT_DIR/.ci-vectors/test/vectors/protocol-v1.json"
- export FLAMENET_PQ_VECTORS="$CI_PROJECT_DIR/.ci-vectors/test/vectors/pqx3dh-v2.json"
@@ -195,7 +195,7 @@ vectors-head:
- export JAVA_HOME=/opt/homebrew/opt/openjdk@21
- export ANDROID_HOME=$HOME/Library/Android/sdk
- rm -rf "$CI_PROJECT_DIR/.ci-vectors-head"
- git clone --depth 1 https://gitlab.com/paulhitt/flamenet-e2e.git "$CI_PROJECT_DIR/.ci-vectors-head"
- git clone --depth 1 https://gitlab.com/extant2000/flamenet-e2e.git "$CI_PROJECT_DIR/.ci-vectors-head"
- |
echo "pinned: $(cat "$CI_PROJECT_DIR/.e2e-ref")"
echo "at HEAD: $(git -C "$CI_PROJECT_DIR/.ci-vectors-head" rev-parse HEAD)"
+1 -1
View File
@@ -47,7 +47,7 @@ less than the two existing engines quietly agreed on, but only if it is
written against the spec and the published vectors rather than against a
reading of our own Swift and JavaScript. So the engine is held to
`test/vectors/protocol-v1.json` in
[flamenet-e2e](https://gitlab.com/paulhitt/flamenet-e2e), the same file the
[flamenet-e2e](https://gitlab.com/extant2000/flamenet-e2e), the same file the
other two engines are checked against, read from that repository rather than
copied here, because a copied vector file drifts and a drifting vector file
stops being a check. `PublishedVectorsTest` looks for it beside this checkout
@@ -30,7 +30,7 @@ class PublishedVectorsTest {
file != null,
"published vectors not found. Looked in: " +
candidates.joinToString(", ") { it.absolutePath } +
". Clone https://gitlab.com/paulhitt/flamenet-e2e beside this repo, " +
". Clone https://gitlab.com/extant2000/flamenet-e2e beside this repo, " +
"or set FLAMENET_VECTORS to protocol-v1.json.",
)
JSONObject(file!!.readText())