f10e7ed2f3## Problem - Related to https://github.com/agama-project/agama/pull/2117 - As discussed on the review, there should be just one automatic retry to report a failure quicker to the user ## Solution - Change the number - Additionally the logic has been changed so the retry count really means the retry count. Before it was actually the total amount of attempts, not just the retries. |
||
|---|---|---|
| .. | ||
| bin | ||
| conf.d | ||
| etc | ||
| lib | ||
| package | ||
| po | ||
| share | ||
| test | ||
| .editorconfig | ||
| .gitignore | ||
| .rspec | ||
| .rubocop.yml | ||
| agama-yast.gemspec | ||
| agama-yast.spec.in | ||
| Gemfile | ||
| Gemfile.lock | ||
| README.md | ||
| run_tests_in_container.sh | ||
Agama YaST
According to Agama's architecture this project implements the following components:
- The Agama YaST, the layer build on top of YaST functionality.
Testing Changes
The easiest way to test changes done to Ruby code on Agama live media is to build
the gem with modified sources with gem build agama-yast. Then copy the resulting file
to Agama live image. Then run this sequence of commands:
# ensure that only modified sources are installed
gem uninstall agama-yast
# install modified sources including proper binary names
gem install --no-doc --no-format-executable <path to gem>
If the changes modify the D-Bus part, then restart related D-Bus services.