bug: remote-build broke in snapcraft 8.0
Metadata
Current evaluation
Abandoned after investigation identified a libgit2 issue with large repositories causing SSL/broken pipe errors during remote builds. No fix was implemented.
Suggested action: —
No scores available.
Issue body
### Bug Description
Remote build doesn't push.
Reverting back to 7.x fixes it.
### To Reproduce
```
git clone https://github.com/telegramdesktop/tdesktop
cd tdesktop
snapcraft remote-build
```
I expect it to push to launchpad and build. But this happens.
```
snapcraft remote-build
snapcraft remote-build is experimental and is subject to change - use with caution.
All data sent to remote builders will be publicly available. Are you sure you want to continue? [y/N]: y
No existing build found
If interrupted, resume with: 'snapcraft remote-build --recover --build-id snapcraft-telegram-desktop-e070194130e7a78db0be5f0185c57587'
remote-build error: Git operation failed.aunchpad: https://popey:<token>@git.launchpad.net/~popey/+git/snapcraft-telegram-desktop-e070194130e7a78db0be5f0185c57587/
Could not push 'HEAD' to 'https://popey:<token>@git.launchpad.net/~popey/+git/snapcraft-telegram-desktop-e070194130e7a78db0be5f0185c57587/' with refspec 'refs/heads/dev:refs/heads/main' for the git repository in '/home/alan/.cache/snapcraft/remote-build/snapcraft-telegram-desktop-e070194130e7a78db0be5f0185c57587/repo': SSL error: syscall failure: Broken pipe
Full execution log: '/home/alan/.local/state/snapcraft/log/snapcraft-20231205-101855.575700.log'
```
### Environment
snapcraft 8.0.0 on Ubuntu 23.10.
### snapcraft.yaml
```shell
https://github.com/telegramdesktop/tdesktop/blob/dev/snap/snapcraft.yaml
```
### Relevant log output
```shell
Full log
2023-12-05 10:18:55.576 Starting Snapcraft 8.0.0
2023-12-05 10:18:55.577 snapcraft remote-build is experimental and is subject to change - use with caution.
2023-12-05 10:18:55.577 Emitter: Pausing control of the terminal
2023-12-05 10:18:57.021 Emitter: Resuming control of the terminal
2023-12-05 10:18:57.050 Got base 'core22' from 'snap/snapcraft.yaml'
2023-12-05 10:18:57.051 Running new remote-build because project is in a git repository
2023-12-05 10:18:57.051 Setting up launchpad environment
2023-12-05 10:18:57.083 Using project name 'telegram-desktop' from 'snap/snapcraft.yaml'
2023-12-05 10:18:57.625 Setting up launchpad environment.
2023-12-05 10:18:58.131 Looking for existing build
2023-12-05 10:18:58.183 No existing build found
2023-12-05 10:18:58.183 If interrupted, resume with: 'snapcraft remote-build --recover --build-id snapcraft-telegram-desktop-e070194130e7a78db0be5f0185c57587'
2023-12-05 10:18:58.184 Starting build
2023-12-05 10:18:59.464 Cached project at /home/alan/.cache/snapcraft/remote-build/snapcraft-telegram-desktop-e070194130e7a78db0be5f0185c57587/repo
2023-12-05 10:18:59.531 creating git repo: name=snapcraft-telegram-desktop-e070194130e7a78db0be5f0185c57587, owner=/~popey, target=/~popey
2023-12-05 10:19:01.275 Sending build data to Launchpad: https://popey:<token>@git.launchpad.net/~popey/+git/snapcraft-telegram-desktop-e070194130e7a78db0be5f0185c57587/
2023-12-05 10:19:01.276 Resolved reference 'refs/heads/dev' for name 'HEAD'
2023-12-05 10:19:01.276 Pushing 'HEAD' to remote 'https://popey:<token>@git.launchpad.net/~popey/+git/snapcraft-telegram-desktop-e070194130e7a78db0be5f0185c57587/' with refspec 'refs/heads/dev:refs/heads/main'.
2023-12-05 10:21:13.897 remote-build error: Git operation failed.
Could not push 'HEAD' to 'https://popey:<token>@git.launchpad.net/~popey/+git/snapcraft-telegram-desktop-e070194130e7a78db0be5f0185c57587/' with refspec 'refs/heads/dev:refs/heads/main' for the git repository in '/home/alan/.cache/snapcraft/remote-build/snapcraft-telegram-desktop-e070194130e7a78db0be5f0185c57587/repo': SSL error: syscall failure: Broken pipe
2023-12-05 10:21:13.898 Full execution log: '/home/alan/.local/state/snapcraft/log/snapcraft-20231205-101855.575700.log'
```
```
### Additional context
_No response_
Evaluation history
| Date | Model | Scores | Action | Summary |
|---|---|---|---|---|
| qwen/qwen3.6-35b-a3b | — | — | Abandoned after investigation identified a libgit2 issue with large repositories causing SSL/broken pipe errors during remote builds. No fix was implemented. | |
| qwen/qwen3.6-35b-a3b | — | — | Closed without a documented fix after investigation into a libgit2 SSL error causing broken pipes during large repository pushes to Launchpad. | |
| qwen/qwen3.6-35b-a3b | — | — | Closed without a fix. Investigation identified large repository size triggering libgit2 SSL errors during Launchpad pushes. No resolution was provided. | |
| qwen3.6-35b-a3b-mtp-q6 | — | — | Closed without a fix. Developers investigated the Git SSL broken pipe error and suspected it stemmed from large repository size and libgit2 limitations. | |
| qwen3.6-35b-a3b-mtp-q6 | — | — | Closed without a fix. Developers suspected a libgit2 issue with large repositories causing SSL broken pipe errors during remote-build pushes. No resolution was provided, and the issue was abandoned. |
Update history
No update history recorded yet.
Related issues
| Issue | Project | State | Summary | Similarity |
|---|---|---|---|---|
| #4520 regression: remote-build fails OpenSSL error | snapcraft | closed | Resolved a regression in snapcraft 8.0.1 where remote-build failed with a pygit2 OpenSSL certificate error on Arch Linux. The fix was verified and deployed to the candidate channel. | |
| #1876123 remote-build failed | snapcraft (launchpad) | closed | A snapcraft remote-build crash causing a NoneType error was closed without resolution or further discussion, indicating abandonment. No fix or merge details were provided. | |
| #1973199 Temporary repo for snapcraft remote-build has no git tags | snapcraft (launchpad) | closed | Closed without resolution, likely abandoned. The report details snapcraft remote-build creating a temporary repository without git tags, breaking version detection via snapcraftctl set-version. | |
| #1860526 source-type breaks remote-build | snapcraft (launchpad) | open | snapcraft remote-build fails when source-type is git because the source directory differs from the working directory, causing go dep to fail. The remote-build command has since been removed from snapcraft, making this issue obsolete. | |
| #4142 snapcraft remote-build exits with return code 0 even when some snaps failed to build for a given arch | snapcraft | closed | Closed without comments or resolution, indicating the request was abandoned. No official fix or merge details were provided. | |
| #2149 Snap build breaking on non-amd64 architectures | charmcraft | closed | Closed without a public fix. The snap build failure on non-amd64 architectures due to a missing libgit2 dependency was abandoned, with no resolution or code changes provided. |