| Commit message (Collapse) | Author | Age | Files | Lines |
... | |
|
|
|
|
|
| |
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
|
| |
|
| |
|
|
|
|
| |
Commit e49cd1fd introduced an extra space.
|
| |
|
|
|
|
|
|
|
| |
makebumpver needs to make sure that single percent signs (%) are
escaped in RPM changelog lines. Leaving single percent signs in the
changelog entries causes problems for rpmlint and, theoretically,
rpmbuild.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Specifically:
anaconda.src:183: W: unversioned-explicit-obsoletes booty
anaconda.src:262: E: hardcoded-library-path in /lib/systemd/system/*
anaconda.src:263: E: hardcoded-library-path in /lib/systemd/system-generators/*
anaconda.src:287: E: files-attr-not-set
anaconda.src:288: E: files-attr-not-set
anaconda.src:289: E: files-attr-not-set
anaconda.src:290: E: files-attr-not-set
anaconda.src:293: E: files-attr-not-set
anaconda.src:294: E: files-attr-not-set
anaconda.src:295: E: files-attr-not-set
anaconda.src:296: E: files-attr-not-set
anaconda.src:299: E: hardcoded-library-path in /usr/lib/dracut/modules.d/80%{name}
anaconda.src:299: E: files-attr-not-set
anaconda.src:300: E: hardcoded-library-path in /usr/lib/dracut/modules.d/80%{name}/*
anaconda.src:300: E: files-attr-not-set
anaconda.src:624: W: macro-in-%changelog %packages
anaconda.src:1234: W: macro-in-%changelog %include
anaconda.src:1680: W: macro-in-%changelog %{nil}
anaconda.src:1733: W: macro-in-%changelog %post
anaconda.src:2160: W: macro-in-%changelog %{nil}
anaconda.src:2325: W: macro-in-%changelog %includes
anaconda.src:2564: W: macro-in-%changelog %packages
anaconda.src:2565: W: macro-in-%changelog %post
anaconda.src:2592: W: macro-in-%changelog %pre
anaconda.src:2788: W: macro-in-%changelog %pre
Updated data/ and data/systemd/ to install to /usr/lib rather than
/lib since the UsrMove thing happened.
Removed the newt and slang BuildRequires since we do not use those
anymore.
|
| |
|
|
|
|
|
|
|
| |
LUKSDevice instances were getting into the partition list, so instead
of setting the partition's max_size we were instead adding that
attribute to the LUKSDevice and the following partition allocation run
was failing due to incorrect settings on the partitions.
|
|
|
|
|
|
|
|
|
| |
Now that StorageDevice's format and originalFormat attributes are
distinct instances of a DeviceFormat class we have to explicitly
duplicate partition removals when we aren't reinitializing the disklabel.
All removals are currently done on originalFormat and format still has
all of its original partitions, which becomes a problem when we try
to add new ones to it.
|
| |
|
| |
|
|
|
|
|
| |
When editing a non-lv and changing the device type to lvm it is
possible that there are no vg instances in the devicetree.
|
| |
|
|
|
|
| |
It should be done by modifying the VG via the RHS.
|
|
|
|
|
| |
VGs have a freeSpace attribute while btrfs vols do not. Choose the
existing container with the most free space or the most total space.
|
|
|
|
|
|
|
|
|
| |
The code to decide when to lock the encryption checkbutton was too
simple. It was possible to toggle it for existing LVs that had been
marked for reformat previously. It was also possible to toggle it for
new LVs in existing VGs whose PVs were encrypted. It should be active
and insensitive whenever there is encryption on existing devices
anywhere in the stack since we cannot change that.
|
|
|
|
|
|
| |
You can choose from any of the defined VGs or you can create a new VG.
Also provided is some basic editing for new VGs: name and disk set.
|
| |
|
|
|
|
|
| |
Doing this automatically causes some odd side effects like jumping into the
storage spoke without user intervention.
|
|
|
|
|
| |
This saves us from having to type the same GTK constants again and again in
python land.
|
|
|
|
|
| |
For that matter, no GTK anything may be called from outside the main thread.
Otherwise, all bets are off with the UI.
|
|
|
|
|
|
|
|
| |
Somehow (I cannot reproduce it) it could happen that on_server_edited
gets None as path and instead of crashing it should just do nothing in
such cases.
Resolves: rhbz#880430
|
| |
|
| |
|
|
|
|
|
| |
Instead of crashing, inform users they should use integer values when
entering partition sizes.
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Cases I tested:
(spoke is pre-hub network spoke)
Link has (slow) dhcp:
- connected in payload init, connected in spoke
- not connected in payload init, connected in spoke
- fixed by the patch
- not connected in payload init, not connected in spoke
- subcases: - wait for connection in spoke
- leave spoke while connecting
- fixed by the patch
Link does not have dhcp:
- configure static connection and leave spoke
|
| |
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
There are three problems with the current resize action UI:
(1) You can't discover that there's a drop down in the action column because
there's no down arrow. GTK simply doesn't do that.
(2) We can't filter out shrink from the drop down on a per-filesystem basis
without layering on all the usual filter store crud.
(3) Something about interacting with a GtkCellRendererCombo causes the layering
of dialogs to get screwed up such that coming back to the storage spoke after
visiting the resize dialog appears locked up, because the dialog is displayed
under the spoke.
This commit fixes all these problems by getting rid of the drop downs in the
action column and adding a communal set of tool buttons for setting the action
you want.
|
|
|
|
|
| |
This gets rid of some warnings on tty1. I'm surprised no one's filed bugs
about them yet.
|