| Commit message (Collapse) | Author | Age | Files | Lines |
... | |
| | |
| | |
| | |
| | |
| | | |
Without gui.py and iw/, they're not useful anymore except as examples of
what not to do on newui.
|
| | | |
|
| | |
| | |
| | |
| | | |
space)
|
| | | |
|
| | | |
|
| | | |
|
| | | |
|
| | |
| | |
| | |
| | | |
Password spoke
|
| | | |
|
| | | |
|
| | | |
|
|/ / |
|
| | |
|
| |
| |
| |
| |
| |
| |
| |
| | |
Rule #1 of Computing: It Works Better When You Turn It On.
Make anaconda.target request anaconda-cleanup-initramfs.service so it
actually gets started.
(cherry picked from commit d0ca82e99bc817bbe18ed8c06cb5c957c72e0f7a)
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| |
| |
| |
| |
| |
| | |
Note that this does not yet handle the fact that we want to skip firstboot
on most kickstart installs (unless the user specifies otherwise). We need
a place to load those defaults, which will be a separate patch.
|
| |
| |
| |
| | |
It looks a little silly to have it sitting there and stopped.
|
| | |
|
| | |
|
| |
| |
| |
| |
| |
| |
| | |
Our tangled set of imports means that anaconda was still trying to import
partIntfHelpers through dispatch and rescue mode. This patch breaks those
imports (which likely further breaks rescue and upgrade modes) and makes
the gui work again.
|
| | |
|
| |
| |
| |
| |
| | |
I discovered this searching for "iw" to make sure I deleted everything related
to the old interface.
|
| |
| |
| |
| |
| |
| | |
It's now only used by the text UI, which you can't even get to right now and
won't be able to until we create a whole new text interface. That one will not
be using partIntfHelpers either.
|
| |
| |
| |
| |
| | |
We're not using it for anything, and I don't want people looking at it for any
reason anyway. If we really need to, it's still in version control.
|
| | |
|
| |
| |
| |
| |
| |
| |
| | |
The only places where we might want to run a check method are already being
handled by other means, and I never figured out how to handle killing a
check thread in the generic case anyway. This is clearly code we can live
without.
|
| |
| |
| |
| | |
Doing so will print a GTK assertion on tty1.
|
| |
| |
| |
| | |
They're making it more difficult for me to see real error messages.
|
| |
| |
| |
| |
| |
| | |
We don't get any notification that the post-trans has started, so this is the
best we can do. At least now it doesn't look like the last package is taking
forever to install.
|
| | |
|
| | |
|
| |
| |
| |
| |
| |
| |
| |
| |
| | |
If you're on a spoke when all other spokes become ready and complete, the
install will continue automatically when you hit back. If you're on the hub,
the install will continue automatically when all spokes are ready and
complete.
It's a little jarring, but that's just how it's gotta be.
|
| |
| |
| |
| |
| |
| |
| | |
It can only be sensitive both if there's no incomplete spokes and no not
ready spokes. By not tracking not ready spokes, it's possible to hit
continue while things are still downloading. This can lead to very bad
situations, and it's only by accident that we've not hit this yet.
|
| |
| |
| |
| |
| |
| |
| |
| |
| | |
This first requires splitting out the chunk that calls execute methods into its
own function, then adding an execute method to spokes, then making sure it gets
called from everywhere. I have also added a way to make sure the execute
methods do not get run when spokes are ready, since at least the storage check
function will set the spoke not ready and then ready again which will lead to
an infinite loop.
|
| |
| |
| |
| |
| |
| |
| | |
If you're doing an install with just Core, or with some special set of groups
that somehow doesn't include one of our desktop environments (even though Base
is currently a DE), make sure to set the spoke to complete and give a useful
status message.
|
| |
| |
| |
| |
| |
| |
| |
| | |
This removes a lot of the special purpose code that made up the special
AnacondaKSHandler subclass. There's also no need for the _dataObjs
attribute anymore since we can't just blindly iterate over all kickstart
objects any more. Some need to be run at one point, and some at another
point.
|
| |
| |
| |
| |
| | |
This gets their execute methods to be ready to be called from somewhere else,
but that does not yet happen.
|
| | |
|
| |
| |
| |
| |
| | |
When package metadata fails to download suggest that the user check the
repo url and, if enabled, the proxy settings.
|
| | |
|
| |
| |
| |
| |
| | |
It's easier to search through the available layouts manually if
they are sorted.
|
| | |
|
| |
| |
| |
| |
| |
| |
| |
| |
| | |
We still do the final check against the software's disk space
requirement with the assumption that the user is doing autopart.
Even when we have the tug of war, we're still checking free space
before the user has had a chance to choose between autopart and
custom. That will need to be addressed at some point.
|
| | |
|
| | |
|