| Commit message (Collapse) | Author | Age | Files | Lines |
... | |
| |
|
| |
|
| |
|
|
|
|
|
| |
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.
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
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.
|
|
|
|
|
| |
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.
|
| |
|
|
|
|
| |
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.
|
| |
|
|
|
|
|
|
|
| |
Since the newui custom spoke creates all partitions with a base
size of 1MB this check had to be moved to after allocation is
complete since the base size is nearly meaningless in the context
of these checks.
|
|
|
|
|
|
|
|
|
|
|
| |
In the case where the new partition is going to be the first logical
partition on the disk (and therefore require creation of an extended
partition) we were failing to correctly set things up to perform the
growth calculation. This led to sub-optimal placement of partitions.
This also fixes a small bug that caused us to jump to the new
candidate free region even when it offered the same growth
potential as the old/current one.
|
|
|
|
|
|
|
| |
Subvolume size is the same as the volume size. Adding a new
subvolume means growing the volume, which requires us to
update the other subvolumes' selectors' sizes to keep them
all in sync (and prevent spurious size adjustment operations).
|
| |
|
|
|
|
|
| |
This prevents automatic selection of stage2 as stage1, which is
something we never want to happen.
|
| |
|
|
|
|
|
|
|
|
| |
Instead of adding command line option throwing exception in one place
of the code, let's use SIGURS1 as signal for raising exception in anaconda.
This way, it is possible to raise exception in different phases of the
installation and we can add code to prepare worst case scenario testing
as much resolved bugs in exception handling as possible.
|
| |
|
|
|
|
|
|
| |
The #2 and #3 dialogs already grab the correct labels so by trying to do so
again in _set_free_space_labels, we're making sure to get the wrong thing
and end up with a traceback.
|
|
|
|
|
| |
It's all because doKickstartStorage and StorageChecker.run can take a long
time, and they were being run synchronously.
|
| |
|
|
|
|
|
| |
Also switches the reformat check to use format names instead of
types since the names are what we populate the fstype combo with.
|
| |
|
| |
|
| |
|
|
|
|
| |
Leading space isn't useful for growing a filesystem.
|