please support system-usernames, new in snapd 2.41
Metadata
Current evaluation
System-username support was implemented, including both YAML forms and long-form snap.yaml output, by merged PR snapcore/snapcraft#2858 (commit bad4d2d69).
Resolution: closed resolved
Reason: PR snapcore/snapcraft#2858 was merged as commit bad4d2d69 with the title "add support for system-usernames". The earlier draft was PR snapcore/snapcraft#2838.
Evaluated by: mr-cal-bot
No scores available.
Issue body
Note there are two forms:
system-usernames:
<name>: <scope>
and:
system-usernames:
<name>:
scope: <scope>
The only supported value for <name> is 'snap_daemon' and the only supported value for <scope> is 'shared'.
References:
* https://forum.snapcraft.io/t/system-usernames/13386
* https://forum.snapcraft.io/t/multiple-users-and-groups-in-snaps/1461
Evaluation history
| Date | Model | Scores | Action | Summary |
|---|---|---|---|---|
| stealth/space-bunny-alpha | — | closed resolved | System-username support was implemented, including both YAML forms and long-form snap.yaml output, by merged PR snapcore/snapcraft#2858 (commit bad4d2d69). | |
| stealth/space-bunny-alpha | — | closed resolved | Added snapcraft.yaml system-usernames support and schema tests; merged via snapcraft#2858 in commit bad4d2d69. | |
| stealth/space-bunny-alpha | — | closed resolved | Implemented system-usernames support via merged PR #2858 (commit bad4d2d69), including snap_daemon/shared schema validation and tests for LP #1845267. | |
| qwen/qwen3.6-35b-a3b | — | — | Closed without resolution. The feature request for snapd 2.41 system-usernames support was abandoned due to inactivity. | |
| qwen/qwen3.6-35b-a3b | — | — | Closed without implementation, indicating the request was abandoned. No comments or resolution details were recorded. | |
| qwen/qwen3.6-35b-a3b | — | — | Requesting support for snapd 2.41 system-usernames was closed without comments or resolution. The request appears abandoned or superseded by later snapd releases, with no implementation or discussion recorded. | |
| qwen3.6-35b-a3b-mtp-q6 | — | — | Closed without implementation. The request to support snapd 2.41 system-usernames was abandoned after six years with no comments or resolution. |
Update history
| Date | Change |
|---|---|
| created |
Related work
-
Likely Fixed By:
snapcore/snapcraft#2858
(confidence 100%)
Merged commit bad4d2d69 added system-username support.
-
Related To:
snapcore/snapcraft#2838
(confidence 95%)
Earlier draft containing schema and implementation commits for the feature.
Related issues
| Issue | Project | State | Summary | Similarity |
|---|---|---|---|---|
| #3964 schema,tests: add support for new system usernames | snapcraft | merged | Merged #3964 as 92a9614f5, updating the schema and tests to accept additional system usernames supported by snapd. | |
| #3746 project: support system-usernames | snapcraft | merged | Merged #3746 added support for system-usernames, relaxing project validation and deferring stricter errors to snap pack; merge commit 1122de9d0. | |
| #2039971 Add support for _daemon_ as a valid system-username in snapcraft.yaml | snapcraft (launchpad) | open | Snapcraft formerly rejected `_daemon_` as a system username; current validation accepts arbitrary usernames, resolving the reported parsing failure. | |
| #2838 add support for system-usernames | snapcraft | closed | Closed while the rebased work was split into smaller PRs; system-usernames support and schema tests landed separately in merged PR #2858 via commit bad4d2d69. | |
| #2858 add support for system-usernames | snapcraft | merged | Merged as bad4d2d69, adding system-usernames support and schema tests for LP #1845267. |