You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
With the changes implemented in #381, now software probing is done during the config phase instead of the installation phase. This was moved because the probing needs to be performed in order to validate the software proposal. But, this makes easier to spot issues because the repositories could not be reachable at that moment. Note that the network connection might not be configed yet, or there might be some firewall issues, etc.
If software probing fails, then there is not way to reprobe it again. This is especially critical in scenarios where a WIFI conneciton needs to be configured. The proposal will always fail, and it will continue wrong after configuring the WIFI connection.
The text was updated successfully, but these errors were encountered:
https://build.opensuse.org/request/show/1066106
by user IGonzalezSosa + dimstar_suse
- Version 0.7
- Do not use a proxy to get the errors lists
(gh#openSUSE/agama#424).
- Add live reloading feature for easing the front-end development
process (gh#openSUSE/agama#419).
- Fix storage section crashing when proposal is not ready
(gh#openSUSE/agama#418).
- Better handling of software repositories
(gh#openSUSE/agama#414):
* Report issues when reading the software repositories.
* Inform the user about the software proposal progress.
* Add a button to reload the repositories
(gh#openSUSE/agama#388).
- Added a button for displaying the YaST logs
(related to gh#openSUSE/agama#379)
- UI fixes (gh#openSUSE/agama#401):
* Add a fallback height for the layout
* Fix some miss-alignments
* Add missing icon
* Ensure tooling serving and loading fo
With the changes implemented in #381, now software probing is done during the config phase instead of the installation phase. This was moved because the probing needs to be performed in order to validate the software proposal. But, this makes easier to spot issues because the repositories could not be reachable at that moment. Note that the network connection might not be configed yet, or there might be some firewall issues, etc.
If software probing fails, then there is not way to reprobe it again. This is especially critical in scenarios where a WIFI conneciton needs to be configured. The proposal will always fail, and it will continue wrong after configuring the WIFI connection.
The text was updated successfully, but these errors were encountered: