Add support for _daemon_ as a valid system-username in snapcraft.yaml

Bug #2039971 reported by Graham Morrison
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Snapcraft
New
Undecided
Unassigned

Bug Description

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.

description: updated
description: updated
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.