Helps troubleshoot SELinux problems
bb3d75bf71
The argument was never used since sealert always crashed on GUI setup, but it iss still better to remove it to avoid issues in the future. |
||
|---|---|---|
| tests | ||
| .gitignore | ||
| README.translations | ||
| setroubleshoot-po.patch | ||
| setroubleshoot.init | ||
| setroubleshoot.logrotate | ||
| setroubleshoot.spec | ||
| setroubleshoot.tmpfiles | ||
| sources | ||
Setroubleshoot translations currently live in the following locations:
- https://fedora.zanata.org/project/view/setroubleshoot
- contains translations for both stable (RHEL) and master (Fedora) branches
- maintains large number of languages (several of which do not actually contain any translated strings)
- updated by community and partially by RH localization effort
- setroubleshoot source repositories (https://pagure.io/setroubleshoot and https://github.com/fedora-selinux/setroubleshoot)
- is kept up-to-date with fedora.zanata
How to update source files on fedora.zanata:
$ git clone git@github.com:fedora-selinux/setroubleshoot.git
$ cd setroubleshoot/framework
# Update Makefile
$ ./autogen.sh
# generate new potfile
$ cd po
$ make setroubleshoot.pot
# Repeat the process for plugins
# Push potfiles to zanata
$ zanata-cli push --push-type source
How to pull new translations from zanata
$ git clone git@github.com:fedora-selinux/setroubleshoot.git
$ cd setroubleshoot
# Make sure "zanata.xml" file pointing to corresponding translations branch is present
# Optionally update source files on zanata
# Pull new translations from zanata
$ zanata-cli -e pull --pull-type trans