| Commit message (Collapse) | Author | Age | Files | Lines |
... | |
| |
|
| |
|
| |
|
|
|
|
|
|
|
|
|
| |
Should storage ever get reset (which it can in the case of moving back to
the hub from reclaim, resulting in an error), any protected attributes will
be wiped. protectedDevSpecs is the definitive source for what's protected
and what's not.
The dev.protected lines are still there in case we do not hit an error.
|
| |
|
| |
|
| |
|
|
|
|
| |
You always want to let things settle, so just take care of it.
|
|
|
|
|
| |
The same complicated rules apply when reformat is toggled as when
populating the right side.
|
|
|
|
| |
Related: rhbz#884270
|
| |
|
| |
|
| |
|
| |
|
| |
|
|
|
|
|
| |
Then later when we are setting up filesystems, do not tear down protected
devices.
|
|
|
|
|
|
|
|
|
|
|
|
| |
mdadm 3.2.4 made a major change in the amount of space used for 1.1 and
1.2 metadata in order to reserve space for reshaping. See commit
508a7f16 in the upstream mdadm repository.
This has resulted in a large difference between what anaconda thinks the
size of the array should be and what it actually is.
We now use 2.0MB for metadata that isn't 1.1 or 1.2
For 1.1 and 1.2 we calculate the reserved space value and use that.
|
|
|
|
|
| |
Also removes urlgrabber.grabber.reset_curl_obj() from getDefaultHostname()
where all its job were to cause races occasionally.
|
| |
|
| |
|
|
|
|
|
|
| |
In dracut we set ONBOOT=yes for --activate so that NM activates
the device upon its start, in anaconda we set the real value
of ONBOOT.
|
|
|
|
| |
It was replaced by self.set_info, self.set_error and self.set_warning.
|
|
|
|
|
|
|
| |
Commit 2c367ec88e7385892cb1cdd1f2e1a61079d2e5de brings set_info,
set_warning and set_error methods for our BaseWindow, but neither
Chris writing the patch nor me doing the review noticed that set_info
is used in all cases in the GUIObject's methods.
|
| |
|
|
|
|
|
|
|
|
|
| |
Basically, _setupDevice gets confused when there's a symlink involved in the
path and /proc/mounts does not match what we expect. Thus, just make sure
we resolve symlinks to their real path before feeding them to get_mount_device.
Also, don't print some mount-related log messages if they'd say something like
"None is already mounted".
|
|
|
|
|
| |
There's no translation work to be done here, since "_Done" should already
be translated from earlier changes.
|
| |
|
|
|
|
|
| |
It's pretty confusing to click "Set as Boot Loader" to toggle installing a
boot loader off.
|
|
|
|
|
|
| |
Write only /etc/vconsole.conf.
Signed-off-by: Brian C. Lane <bcl@redhat.com>
|
|
|
|
|
|
| |
Write only /etc/locale.conf.
Signed-off-by: Brian C. Lane <bcl@redhat.com>
|
|
|
|
|
|
| |
Write the hostname to /etc/hostname instead of /etc/sysconfig/network.
Signed-off-by: Brian C. Lane <bcl@redhat.com>
|
| |
|
| |
|
|
|
|
|
|
| |
This prevents their strings from being translated before we know what language
to translate them into, thus skipping the need for the whole retranslate
thing.
|
| |
|
|
|
|
|
| |
Except on the hub, which is special and is going to need special work done
for it.
|
|
|
|
|
|
|
| |
What we've got now is a string names new_install_name with the product and
version substituted into it, then that string being looked up for translation.
There's no string that matches, of course, so the new install header on the
LHS is not being displayed translated.
|
|
|
|
|
| |
We don't want to re-set up installation source just because someone's using a
different language than we expect.
|
|
|
|
|
|
| |
Everything in the beginning of anaconda_base_window_retranslate is critical to
making sure we can change translations at runtime. Translations are still not
totally working, but this gets us a lot closer.
|
|
|
|
|
|
| |
Without this check, ENABLE_NLS will not be defined, which means gettext.h will
not do anything, which means strings in C lang will not be translated no matter
how hard we try.
|
|
|
|
| |
It might as well do it on its own.
|
|
|
|
|
| |
It doesn't work completely, and isn't needed now that we do not support changing
language from the hub via the language spoke.
|
|
|
|
| |
Also, add a tooltip to describe why you can't do something to a given device.
|
| |
|
| |
|
|
|
|
| |
This is just causing assertions on tty1.
|
|
|
|
|
|
|
|
|
| |
If some layout is related to two (or more) languages, we get it twice
while iterating over languages and their related layouts. Since we use
a mapping from a layout name (e.g. 'us') to decription ('English (English (US))')
the result is that some items are listed twice in the list of all available
layouts. This needs some further fixing, but I'm leaving this for the related
post-F18 UI changes (see #859465 for more information).
|
| |
|
|
|
|
|
|
|
| |
The rules for hostname are more strict. Also, it was not easy to use
this function because of its return values.
Related: rhbz#865869
|
| |
|