Add support for _daemon_ as a valid system-username in snapcraft.yaml
Metadata
Current evaluation
Validation schema in snapcraft doesn't accept _daemon_ as a valid system-username, requiring passthrough workaround. Issue is 3 years old with no maintainer response.
Suggested action: needs triage
Reason: The issue has no labels, no maintainer response, and no assignee after 3 years, indicating it hasn't been triaged. The bug report is clear with reproduction steps, but the current state of the validation schema is unknown due to tool limitations preventing code verification.
Impact:
30
Quick Win:
25.5
Staleness:
95
Complexity:
15
Confidence:
50
Support Request:
0
Issue body
With the release of snapd 2.61, a system-username of `_daemon_` is now supported and preferred over `snap_daemon`.
https://github.com/snapcore/snapd/pull/13052
A value of `_daemon_` cannot currently be parsed in snapcraft (7.5.3.post117+git2d596621) without using `passthrough:`
For example, the following:
system-usernames:
_daemon_: shared
produces the following error:
Issues while validating snapcraft.yaml: The 'system-usernames' property does not match the required schema: '_daemon_' is not a valid system-username.
Evaluation history
| Date | Model | Scores | Action | Summary |
|---|---|---|---|---|
| qwen3.6-35b-a3b-mtp-q6 |
Impact:
30
Quick Win:
25.5
Staleness:
95
Complexity:
15
Confidence:
50
Support Request:
0
|
needs triage | Validation schema in snapcraft doesn't accept _daemon_ as a valid system-username, requiring passthrough workaround. Issue is 3 years old with no maintainer response. | |
| qwen/qwen3.6-35b-a3b |
Staleness:
95
Complexity:
15
Confidence:
90
Support Request:
5
|
needs triage | Request to add daemon as a valid system-username in snapcraft.yaml to match snapd 2.61+. Currently untriaged, no maintainer response, and inactive for over two years. | |
| qwen/qwen3.6-35b-a3b |
Staleness:
95
Complexity:
15
Confidence:
85
Support Request:
5
|
close stale | Request to update snapcraft.yaml schema to recognize _daemon_ as a valid system-username. The issue remains unlabelled, has zero comments, and has been inactive for nearly three years. | |
| qwen3.6-35b-a3b-mtp-q6 |
Staleness:
90
Complexity:
15
Confidence:
85
Support Request:
5
|
needs triage | Snapcraft fails to validate _daemon_ as a system-username in snapcraft.yaml, introduced in snapd 2.61. Issue is unlabelled, has zero comments, and has been inactive for nearly three years. | |
| qwen3.6-35b-a3b-mtp-q6 |
Staleness:
95
Complexity:
15
Confidence:
85
Support Request:
5
|
close stale | snapcraft rejects _daemon_ as a valid system-username in snapcraft.yaml, causing validation errors. Open for ~2.6 years with no maintainer response or labels. |
Update history
No update history recorded yet.
Related issues
No related issues found above the similarity threshold.