Fedora 28 builder is failing #2955

Closed
opened 2019-01-23 15:42:52 +00:00 by exarkun · 2 comments
/tmp/project/.circleci/setup-virtualenv.sh \
    "${TAHOE_LAFS_TOX_ENVIRONMENT}" \
    "${TAHOE_LAFS_TOX_ARGS}"
sudo: virtualenv: command not found
Exited with code 1

https://circleci.com/gh/tahoe-lafs/tahoe-lafs/1649

```/bin/bash -eo pipefail /tmp/project/.circleci/setup-virtualenv.sh \ "${TAHOE_LAFS_TOX_ENVIRONMENT}" \ "${TAHOE_LAFS_TOX_ARGS}" sudo: virtualenv: command not found Exited with code 1 ``` <https://circleci.com/gh/tahoe-lafs/tahoe-lafs/1649>
exarkun added the
dev-infrastructure
supercritical
defect
1.12.1
labels 2019-01-23 15:42:52 +00:00
exarkun added this to the undecided milestone 2019-01-23 15:42:52 +00:00
exarkun self-assigned this 2019-01-23 15:43:02 +00:00
Author

This is because the Fedora 28 builder didn't pin the Fedora image and when Fedora 29 came out it silently switched to Fedora 29. On Fedora 29, virtualenv is provided by a different package.

This is because the Fedora 28 builder didn't pin the Fedora image and when Fedora 29 came out it silently switched to Fedora 29. On Fedora 29, virtualenv is provided by a different package.
Author

Fixed by https://github.com/tahoe-lafs/tahoe-lafs/pull/533 in f0ce490c9e431c024bb5af8833388aad0a7ecdc1

Fixed by <https://github.com/tahoe-lafs/tahoe-lafs/pull/533> in f0ce490c9e431c024bb5af8833388aad0a7ecdc1
exarkun added the
fixed
label 2019-01-23 17:31:24 +00:00
Sign in to join this conversation.
No Milestone
No Assignees
1 Participants
Notifications
Due Date
The due date is invalid or out of range. Please use the format 'yyyy-mm-dd'.

No due date set.

Reference: tahoe-lafs/trac-2024-07-25#2955
No description provided.