| Commit message (Collapse) | Author | Age | Files | Lines |
... | |
| |
|
| |
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
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.
|
| |
|
|
|
|
|
|
|
| |
This is required if we actually want to do UI stuff from more than one
thread. We've avoided this in large part up to now by using the communication
queues, but it's not going to be possible to avoid forever. Error reporting
in particular requires this.
|
|
|
|
|
|
| |
kickstart.selectPackages can go away entirely, since all it does is add stuff
to ksdata and we've got that anyway. Having done that, the handling for
--ignoremissing then needs to move into _applyYumSelections.
|
| |
|
|
|
|
|
|
|
|
| |
This is a little touchy, but you first have to go to the source spoke. This
will cause all widgets to be displayed. Then go to the destination spoke and
choose to autopart all your drives. Then go back to the source spoke. We need
to both set the ISO-related widgets to no_show_all and hide them due to the
previous visit.
|
| |
|
|
|
|
|
|
|
| |
When testing for membership of the NoSuchPackage/NoSuchGroup exceptions,
they appear to be first converted with str(), resulting in the name of the
group or package in question. There are bound to be more instances of this
in the future. Thus, let's just go by the names of things.
|
| |
|
|
|
|
|
| |
When writing new NTP servers configuration the temporary file has to
be closed before moving it to the right place.
|
| |
|
|
|
|
|
|
|
|
|
|
| |
By hardcoding a color, it makes the status text almost invisible on the KDE
live disc where the theme is darker to begin with. Instead, use the theme
colors for everything.
This isn't a perfect fix: If you focus a SpokeSelector, the text will still
be black instead of white like everything else. However, I've been unable to
make that work.
|
| |
|
|
|
|
|
| |
Some machines require a leading backslash, some don't require it. None
seem to break with it there.
|
|
|
|
|
| |
We don't have full access to the initrd anymore, so we've had to move
where we put the cmdline files. Read from the new location.
|
|
|
|
|
| |
We need these after the pivot and we can't get to them without copying
them into /run ourselves.
|
| |
|
|
|
|
| |
Turns out it's been broken for a while anyway.
|
| |
|
|
|
|
| |
Now that _D is in use for the Done button, this one has to change.
|
| |
|
|
|
|
|
| |
This is handled by glade, and the fact that the spinner doesn't spin right now
is due to a GTK bug.
|
|
|
|
|
| |
This provides room to display the personalization on the same screen as the
progress bar, which is what the mockups call for.
|