Set a sane umask to create a proper snap
Metadata
Current evaluation
PR #358 (duplicate of merged PR #360) set a default umask during snap creation so a restrictive host umask no longer yields an invalid snap. Closed unmerged; #360 landed the fix for LP #1515394.
Resolution: closed superseded
Reason: PR #358 was closed without merging; maintainer @kyrofa approved the approach and it was landed instead via the duplicate PR #360, which set a default umask during snap creation and closed LP bug #1515394.
Evaluated by: mr-cal-bot
No scores available.
Issue body
This seems to solve the bug, I'm not sure how to add tests for this though (and not even sure it is worth it).
Evaluation history
| Date | Model | Scores | Action | Summary |
|---|---|---|---|---|
| stealth/space-bunny-alpha | — | closed superseded | PR #358 (duplicate of merged PR #360) set a default umask during snap creation so a restrictive host umask no longer yields an invalid snap. Closed unmerged; #360 landed the fix for LP #1515394. | |
| stealth/space-bunny-alpha | — | closed resolved | Merged PR #360, setting a default umask during snap creation so restrictive process permissions do not produce an invalid snap. Resolved LP #1515394. | |
| qwen/qwen3.6-35b-a3b | — | — | Merged to fix a snap creation bug by setting a proper umask. A reviewer approved the change as sensible, acknowledging that automated testing would be difficult. | |
| qwen3.6-35b-a3b-mtp-q6 | — | — | Merged a fix to set a sane umask, resolving a snap creation bug. Reviewer approved the change and concurred that additional testing was unnecessary. |
Update history
No update history recorded yet.
Related work
-
Duplicate Of:
snapcraft#360
(confidence 92%)
Same title and same +3-line umask change; #360 is the merged PR that actually landed the fix.
-
Likely Fixed By:
snapcraft#360
(confidence 88%)
Merged PR carrying the umask default that #358 proposed.
Related issues
| Issue | Project | State | Summary | Similarity |
|---|---|---|---|---|
| #360 Set a sane umask to create a proper snap | snapcraft | closed | Merged PR #360 set a default umask during snap creation, preventing restrictive process permissions from producing invalid snaps and resolving LP #1515394. | |
| #1515394 Restrictive umask and permissions may cause a built snap to be unusable | snapcraft (launchpad) | closed | Closed by maintainer in Jan 2019 as a non-issue for the general case, since consistent build environments make a restrictive host umask irrelevant; no snapcraft code changes made. |