ferium: Do not read `config.json` for the `complete` commands. Breaks builds
Currently the ferium complete $shell depends on both config.json existing and having at least read and write permissions on it. Even if it does not use any data from the file to run.
This is problematic as during packaging ferium you do not have access to /home/$user/. Leading to ferium returning Permission denied (os error 13) for the missing permissions.
Currently one workaround would be shipping a minimal config.json file with +rw permissions to allow complete to run. But this should not be intended behaviour as it is quite a hack.
To Reproduce
- Change to a system account
- Attempt to run
ferium complete bash - See permission denied error as system accounts do not have
/home/$userdirectories.
Software version
- OS (macOS/Windows/Linux) Linux --> Fedora 35
- Ferium Version (output of
ferium -V) ferium 4.1.4
Additional information
Add any other context about the problem here.
About this issue
- Original URL
- State: closed
- Created 2 years ago
- Comments: 15 (1 by maintainers)
Ferium attempts to both read and write to
/home/$user/.config/ferium/config.json. Under most build environments you do not use a local user to build the software, therefore a home folder would not exist for that account.https://github.com/gorilla-devs/ferium/issues/131 Duplicate and already fixed Update ferium