snapcraft remote-build for a non-existent user gives me a 500 error
Metadata
Current evaluation
⚠️ This summary may be outdated — the issue content or evaluation prompts have changed since this evaluation was made.
Abandoned due to inactivity. The report detailed a 500 error when using a non-existent Launchpad user with snapcraft remote-build. No fix or follow-up was provided.
Suggested action: —
No scores available.
Issue body
Having authed as doismellburning, I then:
```
$ snapcraft remote-build --launchpad-user devnull
<snip>
Sorry, an error occurred in Snapcraft:
HTTP Error 500: Internal Server Error
Response headers:
---
-content-encoding: gzip
connection: close
content-length: 147
content-type: text/html;charset=utf-8
date: Wed, 13 Nov 2019 19:44:25 GMT
server: zope.server.http (HTTP)
status: 500
vary: Accept-Encoding
x-powered-by: Zope (www.zope.org), Python (www.python.org)
---
Response body:
---
b'<html><head><title>GitRepositoryCreatorNotOwner</title></head>\n<body><h2>GitRepositoryCreatorNotOwner</h2>\nA server error occurred.\n</body></html>\n'
---
We would appreciate it if you anonymously reported this issue.
No other data than the traceback and the version of snapcraft in use will be sent.
Would you like to send this error data? (Yes/No/Always/View) [no]: no
You can find the traceback in file '/tmp/tmpmfb2bc63/trace.txt'.
```
I would expect a nice user-facing error message from snapcraft (and a better response from Launchpad than a 500)
Evaluation history
| Date | Model | Scores | Action | Summary |
|---|---|---|---|---|
| qwen/qwen3.6-35b-a3b | — | — | Abandoned due to inactivity. The report detailed a 500 error when using a non-existent Launchpad user with snapcraft remote-build. No fix or follow-up was provided. | |
| qwen/qwen3.6-35b-a3b | — | — | Closed without resolution. No discussion or fix was implemented. The 500 error when specifying a non-existent Launchpad user was not addressed and the issue appears abandoned. | |
| qwen3.6-35b-a3b-mtp-q6 | — | — | Abandoned. Reported a 500 error when using a non-existent Launchpad user with snapcraft remote-build, requesting better error handling. Closed without a fix or follow-up comments. |
Update history
No update history recorded yet.
Related issues
| Issue | Project | State | Summary | Similarity |
|---|---|---|---|---|
| #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. | |
| #1593409 snapcraft cleanbuild 500 internal server error | snapcraft (launchpad) | closed | Closed due to inactivity. The report details a persistent 500 Internal Server Error during snapcraft cleanbuild apt operations, potentially caused by apt-cacher-ng. No fix or resolution was provided. |