Bug #16594

release_process: maybe drop torsocks

Added by CyrilBrulebois 2019-03-21 00:43:34 . Updated 2019-03-21 09:29:03 .

Status:
Resolved
Priority:
Normal
Assignee:
Category:
Target version:
Start date:
2019-03-21
Due date:
% Done:

100%

Feature Branch:
Type of work:
Contributors documentation
Blueprint:

Starter:
Affected tool:
Deliverable for:

Description

Current post-release step:

1. Delete Git branches that were merged:

        cd "${MASTER_CHECKOUT:?}" && \
        git checkout master && \
        git fetch && \
        git submodule update && \
        bare_repo=$(mktemp -d)
        torsocks git clone --bare --reference "${MASTER_CHECKOUT:?}" \
           gitolite@d53ykjpeekuikgoq.onion:tails \
           "${bare_repo:?}" && \
        PYTHONPATH=lib/python3 ./bin/delete-merged-git-branches \
           --repo "${bare_repo:?}" && \
        rm -rf "${bare_repo:?}"

Note the torsocks in the middle, which can error out depending on one’s git/ssh configuration? I had to drop it to have a successful run; should it be dropped entirely?

Subtasks

History

#1 Updated by intrigeri 2019-03-21 09:29:03

  • Status changed from Confirmed to Resolved
  • % Done changed from 0 to 100

Applied in changeset commit:tails|a173a66bcf68a00bc598f40cf91ce4f77684124b.