| Commit message (Collapse) | Author | Age | Files | Lines |
|---|
| ... | |
| |
|
|
| |
The logic for handling it implicitly only works for partitions.
|
| |
|
|
|
|
|
|
|
|
|
| |
I don't especially want to do this, but as stated elsewhere changing language
during installation is not at all easy. It's especially not easy from this
spoke, where everything's already been imported.
Eventually I think this spoke should allow for picking which languages you
want supported on the finished system (sort of a language-specific package
selection screen), but there's no time and this will at least prevent people
from hitting a really annoying bug.
|
| | |
|
| |
|
|
|
|
| |
We don't use unicode strings (as a type) in anaconda.
XklWrapperr.switch_to_show_str should thus use encode("utf-8")
and also contain byte strings.
|
| |
|
|
| |
Forgot to commit the spec and configure.ac changes for 18.28-1
|
| | |
|
| |
|
|
|
|
|
|
|
|
|
| |
The mountpoint selector has a problem where all mountpoints except the
selected one are flush with 0 margin against the right wall of the box
they're in, and the selected mountpoint gets 6 px of margin between it
and the wall.
This patch makes that margin more consistent, so both selected and
unselected mountpoints in the mountpoint selector list on the left hand
side of the custom partitioning spoke get a consistent 12 px margin.
|
| | |
|
| | |
|
| | |
|
| | |
|
| |
|
|
|
|
|
| |
We don't want to display an error dialog (and we don't even support displaying
a dialog for this exception). We should instead raise an exception we know
how to handle, and then the status line for the source spoke will be set
correctly.
|
| |
|
|
| |
Don't display what you entered, because it's all wrong.
|
| | |
|
| |
|
|
|
| |
It's not necessarily intuitive, but your only option is to delete and
re-create.
|
| | |
|
| | |
|
| |
|
|
|
| |
The old method only worked once. After that, it was trying to cancel
create actions that had already been canceled.
|
| |
|
|
|
|
|
| |
If the storage spoke was completed prior to entering the custom spoke
and that visit introduced errors, the storage spoke status wasn't
getting updated accordingly, allowing users with faulty configurations
to proceed with a doomed install.
|
| |
|
|
|
| |
This doesn't come up much because someone's always activating the
md arrays before anaconda gets run.
|
| |
|
|
|
|
|
|
|
|
|
| |
I hit a bug triggered by repeatedly toggling encryption for a vg
while also doing some size changes that revealed a problem in the
current apply/propagate_actions approach. There's just too much
that can happen to try to duplicate/cover it all.
Just replacing the main Storage instance isn't an option since each
of the ui spokes holds a reference to it. However, all of the data
is really in just a few data attributes of Storage and DeviceTree.
|
| |
|
|
|
| |
Also make it a bit easier to see what's going on by performing removals
from the container's disk set separately from toggling member encryption.
|
| | |
|
| |
|
|
|
|
|
| |
In this case what's really being done is we're creating a new device
with the old parameters since we failed to apply the new settings.
Either way, we shouldn't be passing the new/failed encryption, raid
level, or disk set when trying to recreate the previous device setup.
|
| |
|
|
|
| |
If the user selects btrfs as device type and there is a new btrfs volume
defined, populate the raid options based on that volume's raid settings.
|
| |
|
|
|
|
|
|
|
|
|
|
| |
old:
Wireless (wlan0) connected to anaconda_wifi_test4
new:
Wireless connected to anaconda_wifi_test4
old:
Connected devices: eth0, wlan0 (anaconda_wifi_test4)
new:
Connected: eth0, anaconda_wifi_test4
|
| | |
|
| | |
|
| | |
|
| |
|
|
|
|
|
| |
Depending on the filesystem choices for stage2 grub2's core.img may be
too large to fit into the area between the mbr and the first partition.
This adds a check that will show an error if the stage2 fs isn't extX
and the first partition starts lower than 512K.
|
| |
|
|
|
|
| |
We use PANGO_ELLIPSIZE_MIDDLE to show the status and one cannot
get the whole status. Also screen readers could probably work with
this.
|
| |
|
|
|
|
|
|
|
|
| |
Without these lines, the IO blocks everything in python until complete, which
means setting up a bad NFS mount in the source spoke gives you an unresponsive
hub until the NFS timeout hits.
This is only a patch. The better fix would be to use subprocess for mounting
instead of our own C blob. The only reason this C blob exists is because
loader also required it, and no one's found the time to convert this old code.
|
| |
|
|
| |
I guess I'm the only person to touch isys in a very long time, huh?
|
| | |
|
| | |
|
| |
|
|
|
|
|
|
|
| |
- default auto connections are run by NM
- device can be configured also using dracut options
- in rescue, nmcli can be used, it is going to be enhanced to
offer also configuration
- rescue is using obsolete text mode network configuration which
is incomplete, not maintained and doesn't work currently
|
| |
|
|
|
|
|
|
|
|
| |
Add a very basic U-Boot bootloader class for ARM platforms.
This addresses the following needs.
- avoids using GRUB2 as a placeholder for the bootloader.
- installs the required uboot-tools package by default.
- ensures the boot/uboot partition is bootable.
Signed-off-by: Brian C. Lane <bcl@redhat.com>
|
| | |
|
| |
|
|
|
|
|
|
|
| |
In the resize/reclaim dialog you can trigger creation of a disklabel
on a disk containing whole-disk formatting by selecting "Delete".
In custom, you can set mountpoint, reformat, encrypt. If you want to
remove the filesystem and set the disk up with a disklabel, hit the
minus/remove button while the whole-disk filesystem is selected.
|
| |
|
|
| |
Related: rhbz#870476
|
| |
|
|
|
|
|
|
|
|
|
| |
Stop using the AUTOPART_TYPE constants since there aren't enough of
them to cover all the device types we'll want to handle.
This also removes some conversion between DEVICE_TYPE constants
(previously used only in the custom spoke) and AUTOPART_TYPE constants
(previously used only in storage).
Related: rhbz#870476
|
| | |
|
| | |
|
| |
|
|
|
|
|
| |
Additional fix.
If the info refresh is caused by device state change, use the state
that triggered the callback (do not read the state in the callback)
to prevent race with SECONDARIES state.
|
| |
|
|
|
|
|
|
|
| |
With 1a1e7ee8405f44585801d368b139d9e0d3e3abfd we now can use this
trick, because the script (and encoding) is parsed from sr_RS@latin
(i.e. before mangleLocale call). The result is that english_name,
display_name and territory are taken from the babel.Locale object that
understands "sr_Latn_RS" and value for $LANG is valid locale
"sr_RS.UTF-8@latin" as returned by LocaleInfo.__repr__.
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
