From 84ef10b88eb43c82aa2ef6f33d7ae21747df938f Mon Sep 17 00:00:00 2001 From: haemka Date: Thu, 13 Aug 2026 15:35:16 +0000 Subject: [PATCH] Force IPv4 for git.haemka.in SSH connections too Missed two spots: the git.haemka.in keyscan and the submodule fetch's GIT_SSH_COMMAND. If git.haemka.in's DNS answer includes an AAAA record (depends on which resolver the runner hits), these hit the same no IPv6 route issue intermittently, explaining the flaky failures. --- .gitea/workflows/build-deploy.yml | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/.gitea/workflows/build-deploy.yml b/.gitea/workflows/build-deploy.yml index 3d27336..03c077c 100644 --- a/.gitea/workflows/build-deploy.yml +++ b/.gitea/workflows/build-deploy.yml @@ -31,7 +31,7 @@ jobs: mkdir -p ~/.ssh printf '%s\n' "$DEPLOY_SSH_KEY" > ~/.ssh/deploy_key chmod 600 ~/.ssh/deploy_key - ssh-keyscan -H git.haemka.in >> ~/.ssh/known_hosts + ssh-keyscan -4 -H git.haemka.in >> ~/.ssh/known_hosts ssh-keyscan -4 -H -p "${DEPLOY_PORT:-22}" "$DEPLOY_HOST" >> ~/.ssh/known_hosts - name: Fetch theme submodule @@ -40,7 +40,7 @@ jobs: # so it's fetched over SSH with the deploy key instead of needing a # token with access to both repos. git config submodule.themes/latex.url git@git.haemka.in:hmk/pelican-latex.git - GIT_SSH_COMMAND="ssh -i ~/.ssh/deploy_key -o StrictHostKeyChecking=yes" \ + GIT_SSH_COMMAND="ssh -4 -i ~/.ssh/deploy_key -o StrictHostKeyChecking=yes" \ git submodule update --init --recursive - name: Install Python dependencies