| Commit message (Collapse) | Author | Age | Files | Lines |
|---|
| ... | |
| | |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
To start hub use the following command:
make runhub HUB_MODULE=summary
or
make runhub HUB_MODULE=summary HUB_CLASS=SummaryHub
|
| | |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
make runspoke SPOKE_MODULE=source
or
make runspoke SPOKE_MODULE=source SPOKE_CLASS=InstallSource
- runspoke now accepts the name of the module containing
the spoke the user wants to run on command line and
will find the spoke automatically
- as an optional second argument, the script accepts the
name of the spoke class
- install classes and gi introspection files are looked for
in anaconda sources first, so there is no need to install
the anaconda-widgets package to the system
- anaconda should use ANACONDA_DATA, ANACONDA_WIDGETS_DATA and
ANACONDA_INSTALL_CLASSES env variables to look for data files
if those variables are defined
- there was a circular dependency between yuminstall,
backend and kickstart modules, which caused import yuminstall
to fail, because:
yuminstall called backend, which called kickstart, which
requested NoSuchGroup from yuminstall. NoSuchGroup was
present in the source, but much later, so it hadn't been
evaluated yet and the import failed with missing symbol error.
|
| | | |
|
| | |
| |
| |
| |
| |
| |
| | |
There are a lot of UI problems with this one right now. Alignment is all over
the place, clicking on things doesn't do anything, stuff like that. However
it's more important to get this in front of people in a rough state than have
it perfect right this second.
|
| | | |
|
| | |
| |
| |
| |
| |
| |
| | |
upgrade is bringing in findExistingRootDevices, which no longer exists. I
could instead fix upgrade, but we are going to fix it in a far more
comprehensive manner later by moving it out of anaconda. Thus there's no
need to deal with it here now.
|
| | | |
|
| | | |
|
| | | |
|
| | | |
|
| | | |
|
| | |
| |
| |
| |
| | |
When the NTP switch is turned ON/OFF we want to start/stop the chronyd.service
and make the date/time setting widgets (in)active.
|
| | |
| |
| |
| |
| |
| |
| |
| |
| | |
This removes the previous store and tree view code, adding instead the Accordion
and Page code. It also adds the Page that prompts you for how to create a new
partitioning layout and makes that the default for now.
So, no partitioning is yet displayed here and the creation button doesn't do
anything. But it's a start.
|
| | |
| |
| |
| |
| | |
This is the thing on the left hand side of the custom partitioning interface,
allowing you to select a mount point and do some configuration on it.
|
| | | |
|
| | | |
|
| | |
| |
| |
| |
| |
| | |
I don't know why, but you can't set the background on a GtkBox using CSS like
I was elsewhere. So, I've introduced some intermediate Viewports that do
nothing but allow for background coloring.
|
| | | |
|
| | | |
|
| | |
| |
| |
| |
| |
| |
| | |
Really, I'd like them to be grey only when the spoke is not ready and then
turn black afterwards. But I can't make that work, and it has to be done
in C since the labels aren't exposed outside of that. So this will have
to work for now.
|
| | |
| |
| |
| |
| |
| |
| | |
When a spoke is created, initialize should always be called before readiness is
checked. However for those spokes that spawn off a thread in the initialize
method, readiness could be checked before that thread is done. We need to make
sure to check that the watcher is still running as well.
|
| | |
| |
| |
| |
| | |
Since the code adding a language-related layout may return from the
apply method, move timezone preseting before it.
|
| | |
| |
| |
| |
| | |
When user adds/removes a layout, we want to add/remove it from the
X runtime configuration so that the change really happens.
|
| | |
| |
| |
| |
| | |
An empty list is more reasonable for something treated like a normal
attribute.
|
| | | |
|
| | | |
|
| | | |
|
| | | |
|
| | | |
|
| | | |
|
| | | |
|
| | |
| |
| |
| |
| | |
Since the spoke's status is queried even before the refresh method is invoked we
need to populate the store in the initialize method.
|
| | | |
|
| | | |
|
| | |
| |
| |
| |
| |
| |
| |
| | |
We need to set the timezone in the initialization method because
the Datetime spoke's status is queried before the refresh method
gets invoked. However the change of timezone results in a change
of the displayed date/time and we don't want to start timers for
updating the date/time when the spoke is not shown.
|
| | |
| |
| |
| |
| | |
Once we have a GeoIP available, we should use it for guessing
right timezone, but for now, try to use the chosen language.
|
| | | |
|
| | |
| |
| |
| |
| |
| |
| | |
Some keyboard layouts have pathologically long names, and we're already
trimming the status for network sources so just do it for all spokes. Note
that this does not change the text of the status, so it can still be used
for string comparisons.
|
| | |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
When we first try payloadInitialize from anaconda, it's possible there's no
network active. Thus, the thread fails. However if the network is brought
up on the network standalone spoke, we should try again. We also need to
limit trying again to only the cases where no base repo is set up (so, skip
doing anything on media installs).
Long story short, a netinst.iso boot with no configured repo and no network
should now work correctly.
|
| | |
| |
| |
| |
| |
| |
| | |
This is coming up for me when booting a netinst.iso with no network active.
Trying to load groups later will fail and throw a traceback. It'd be better
if we just made sure the software spoke was unavailable and let the user
fix the lack of network.
|
| | | |
|
| | |
| |
| |
| |
| |
| |
| |
| | |
Remove cache dirs for "anaconda" repo when resetting since that repo
name can apply to any base repo configured manually by the user.
Disable all built-in repos when setup of user-specified base repo fails
and we were instructed not to fall back on the on-disk repo configs.
|
| | |
| |
| |
| |
| |
| | |
The software spoke should only be ready when a valid source is
configured. Downloading of repo metadata happens in the background, as
does dependency checking.
|
| | |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Just try once to resolve dependencies. Callers can catch the
DependencyError and present UI as needed to amend the software
set or repos and then try again.
This also changes spaceRequired. After successfully resolving
dependencies we explicitly trigger calculation of the required
space. Less magic to run amuck, more reliable results.
|
| | |
| |
| |
| |
| |
| | |
Doing a YumBase.close() leads to problems when you try to resume
use of that instance. Resetting the package sacks does not appear
to present any such problems.
|
| | | |
|
| | |
| |
| |
| | |
Filtering is separate from target disk selection.
|
| | | |
|
| | | |
|
| | | |
|
