2pisoftware / 2pisoftware/weedremeed-scripts

requirements.txt & pyproject.toml pin weedremeed-client to inaccessible internal GitLab

Open
#2 1 comment 0 reactions 0 assignees View on GitHub
Dominant language
Python
Stars
0
Forks
0
PR merge metrics
No merged PRs in 30d

Description

## Summary
`requirements.txt` and `pyproject.toml` install `weedremeed-client` from the **internal GitLab** repo, which external users can't access:

`requirements.txt`:
```
weedremeed-client @ git+ssh://git@gitlab.internal.2pisoftware.com/customers/CISS/weedremeed/weedremeed-python@ff93f46f91f7a016847f90e9f32591d2fef6d78b
```

`pyproject.toml` (`[tool.uv.sources]`):
```
weedremeed-client = { git = "ssh://git@gitlab.internal.2pisoftware.com/customers/CISS/weedremeed/weedremeed-python" }
```

The host is reachable, but the repo is private (requires an SSH key registered to a GitLab account **and** a repo grant), so `pip install -r requirements.txt` fails for anyone outside 2pisoftware with `Permission denied (publickey)`.

## Suggested fix
The library is now publicly mirrored at https://github.com/2pisoftware/weedremeed-python, and its `main` HEAD matches the pinned commit `ff93f46f91f7a016847f90e9f32591d2fef6d78b`. Pointing both files at the public mirror would let external users install directly, e.g.:

```
weedremeed-client @ git+https://github.com/2pisoftware/weedremeed-python@ff93f46f91f7a016847f90e9f32591d2fef6d78b
```

(plus the equivalent change in `pyproject.toml`). Verified: installing from the mirror builds `weedremeed-client 1.0.0` identically to the GitLab pin.

cc @careck

Contributor guide

No contributing guide indexed for this repository

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.