User `umask` interferes with packaging

[tslilc]

• Does this issue occur in master?

Description

Set umask 077 in ~/.profile, then do kiss b <pkg> and observe that the resulting files are all read/write/execute for root only. In particular the resulting installed package is not usable by ordinary users (eg kiss manifest <pkg> will fail, among all actions requiring access to the installed files/directories).

Presumably somewhere in the packaging/build/installation process umask 022 should be ensured, or perhaps after install some form of chmod a=u $(cat /path/to/manifest) or something?

Error message

N/A

Verbose log

N/A

---

Issues without attached log file will be closed unless steps to reproduce the
problem are provided in place of it. Issues not using the template will be
closed. Feature requests and otherwise non-issues can disregard this notice.