| Commit message (Collapse) | Author | Age | Files | Lines |
... | |
|
|
|
|
| |
Invalidate previous depcheck/transaction to ensure the selection has
been validated when we arrive in hub 2.
|
|
|
|
|
|
|
|
| |
Clean up mountImage and opticalInstallMedia to match their new surroundings.
Allow a path to a specific image file to be specified to mountImage.
Don't automatically mount optical media we detect in opticalInstallMedia.
|
| |
|
|
|
|
|
|
| |
Note that if you delete an LV, it won't change the numbers. This is because
there's still a partition filling all the space, and empty space in a VG
is not taken into account.
|
|
|
|
| |
Also, don't translate it. That doesn't make any sense.
|
| |
|
|
|
|
|
|
| |
This is more for better organization of code than any need to use them from
elsewhere, but they're pretty separate from the rest of the stuff in custom.py
so they stand pretty well on their own.
|
|
|
|
|
|
|
| |
We don't want users to be able to remove devices after they're in the custom
partitioning interface since that'll be very difficult to deal with. However
we would like them to be able to see what devices they have selected for
installation.
|
|
|
|
|
| |
It's going to be needed by both the regular storage interface and the custom
interface, so it would be helpful to have it in a common place.
|
|
|
|
|
| |
There sure are a lot of rough edges to this patch, though. Refer to the
TODO list at the top of the file for things that need to be done.
|
|
|
|
|
|
|
|
|
| |
This means the accordion and page methods to get the current selector are
temporarily unused, but I can imagine such code will find a use again. Thus
I will leave it in for now.
Also, save the format's label as entered from the UI as a test to make sure
this all works. It still won't make it onto the disk yet.
|
| |
|
| |
|
| |
|
| |
|
|
|
|
| |
Also, do a bit of a workaround to make sure free space is not displayed in PB.
|
|
|
|
|
| |
This eliminates PV and RAID options from the file system combo, since those
should appear in the device type combo instead.
|
|
|
|
|
|
|
| |
This only works for disks that have enough space for autopart to work, for
now. Assuming that, you click on the "Click here to create them automatically"
button on the LHS. We run autopart and display the results as a new installation
on the LHS and you can look at the details of each mount point on the RHS.
|
| |
|
|
|
|
|
|
| |
Since we have a text entry for testing layouts, people testing their
layouts settings will expect to have the ordering of the layouts in X
same as in the tree view (store).
|
| |
|
| |
|
|
|
|
|
|
| |
Providing and option to use NTP we also need to allow users to set up
NTP servers, because default servers may not be reachable, there could
be internal NTP servers etc.
|
|
|
|
|
| |
We need some more keyboard related code that could go to the same
file as XklWrapper. keyboard.py is a better name for such file.
|
|
|
|
|
| |
Otherwise, you'll get a disk-sized entry for the partition table in there,
and that looks pretty weird.
|
|
|
|
| |
Feel free to work on any of this stuff.
|
| |
|
|
|
|
| |
Also, set the combo boxes to default to whatever's on the device already.
|
| |
|
| |
|
| |
|
| |
|
|
|
|
|
|
|
|
|
|
|
| |
ACTIVATED state of device doesn't ensure immediate availability
of its configuration (NMIP4Config object) so we might need to
make more tries.
Using separate callbacks for updating just config UI connected to
config property change event would be overcomplicated because we are
waiting for two properties (ipv4 and ipv6), and modifications of UI
of one protocol depends on values of both of them.
|
| |
|
|
|
|
|
|
| |
Otherwise, we end up in a situation where it can change size with every
individual filesystem, which causes everything else on the screen to
jump back and forth horizontally. Very distracting.
|
| |
|
| |
|
|
|
|
|
|
| |
My intention was that people would set up the title in the UI file when they
made a spoke with glade, but that's not always how it works out. Plus having
two places to set the title is confusing. So just make sure they both work.
|
| |
|
|
|
|
|
|
| |
Shares most of the code with WelcomeLanguageSpoke and
transfers the selection ListView and label between the
two display variants as needed.
|
| |
|
| |
|
|
|
|
|
|
| |
A side effect of this is that the whole left hand side is now wider, but I
think that can be fixed by adjusting the stuff that goes in the right hand
side.
|
|
|
|
| |
anaconda sources for testing
|
| |
|
|
|
|
|
|
|
|
|
|
| |
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.
|
| |
|