| Commit message (Collapse) | Author | Age | Files | Lines |
... | |
|
|
|
|
|
| |
Without this whole GUI hangs in case this dialog is run to choose
replacement for the last layout in the list of added layouts (minus
button clicked).
|
|
|
|
|
| |
This makes the specific test of changing the VNC password work, since it
relies on that object existing.
|
|
|
|
|
|
| |
This cleans up a lot of stuff in this file by making use of the spoke we
have instead of newt. There are also a few whitespace fixes and
removals of unnecessary imports.
|
| |
|
| |
|
|
|
|
|
|
| |
Moves the checks that were in the VNC question out to the prep for the
VNC question. We don't get a simple true/false out of the question
anymore.
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
|
|
|
|
|
|
|
|
|
| |
Using "if flags.liveCDinstall or flags.imageInstall or flags.testing" over
and over is incovinient, one may forget to involve some of the conditions
and there is no logging of the skipped actions.
This patch adds flags.can_touch_runtime_system function, that can be used as
a guard and that logs skipped actions. It can also be easily mocked or
masked for the needs of testing.
|
|
|
|
|
| |
Now that we have a spoke to handle the UI, set things up to prompt the
user once again.
|
|
|
|
|
|
| |
This gets used if text mode is requested or if X startup fails. We
don't (yet) prompt the user for advanced VNC configuration such as port
number or to connect to an existing system.
|
|
|
|
|
| |
cmdline means no prompting, so if we have spokes that are incomplete,
raise the error.
|
|
|
|
|
|
|
| |
cmdline mode means do not prompt for missing kickstart data. We need a
way to expose this setting to the interface, so create a flag for it.
"cmdline" cannot be used because that already exists as a flag, so
"ksprompt" is created as a bool. Defaults to true.
|
|
|
|
|
| |
createLuserConf needs to be called before the first use of User().
Also cleaned up some whitespace.
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Add/set mountpoint:
- new device
- add selector to new install page
- new filesystem on old device
- add selector to new install page
- remove selector(s) from old install root page(s)
- old filesystem on old device
- add selector to new install page
- leave selector(s) in old install root page(s)
Remove mountpoint from new install page:
- new device
- destroy the device (cancel its scheduled creation)
- remove the selector from the new install page
- new filesystem on old device
- reset the device to its initial state
- remove the selector from the new install page
- add the selector(s) back to any old install page(s)
- old filesystem on old device
- reset the device to its initial state (mountpoint)
- remove the selector from the new install page
- leave the selector(s) in any old install page(s)
Remove mountpoint from old install page:
- destroy the device
- remove selector(s) from any old or new install page(s)
Other changes:
- Remove remove_from_root method.
- We don't want to modify the Root instances. We won't be showing
devices that are no longer present, so there should be no harm
in leaving the Roots intact.
- Remove _update_ui_for_removals since it's only called from one method.
- Protect more signal handlers from running during refresh.
- Use constants for flipping pages in the partitionsNotebook.
|
| |
|
| |
|
|
|
|
| |
This allows users to assign mountpoints to existing devices.
|
| |
|
| |
|
| |
|
|
|
|
|
| |
Changed attributes of device.format should not also be reflected in
device.originalFormat. That's the whole point of saving the original.
|
| |
|
| |
|
| |
|
| |
|
|
|
|
|
| |
Especially the year set in HW clock (and thus as system date) may
be out of our range of years, that can be selected in the combobox.
|
|
|
|
|
| |
Pass -d to bumpver to turn on debug logging or run:
BZDEBUG=1 make bumpver
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
This follows the same design as GUI. If the install is automated, and
all the spokes are complete, proceed into the installation phase.
However if there are incomplete spokes, let the user finish those
spokes. As soon as all spokes are complete jump straight to the install
phase.
Note that any new spoke that has a background process that could make it
not be "ready" immediately is going to have to be accounted for here,
which is ugly. Perhaps a object attribute that is a list of potential
threads to join would work?
|
|
|
|
|
|
| |
We were just eating all errors, which is not correct. This will accept
errors that might be fixable, but lets other errors bubble up and end
the install. It also manipulates the ready status correctly.
|
|
|
|
|
| |
This brings things more in-line with the GUI spoke. Also it imports the
thread stuff only once rather than multiple times.
|
|
|
|
|
|
|
| |
This is necessary for doing installs via kickstart where we've got the
data even though we haven't gone through the spoke.
Also handle the case where the account could be locked.
|
| |
|
| |
|
| |
|
|
|
|
| |
It's unused anymore and clutters my grep results.
|
|
|
|
|
| |
Python will detect a thread has raised a SystemError and throw it away, so what
I was trying to do here doesn't actually work.
|
|
|
|
|
| |
We need this to quit when handling errors, since doing a sys.exit() from a
thread only kills the thread and not the main program.
|