| Commit message (Collapse) | Author | Age | Files | Lines |
|---|
| ... | |
| |
|
|
|
| |
These may not fix anything we've got right now, but it's the more correct
way to do it.
|
| |
|
|
| |
We're not going to have this done in time for F18 anyway.
|
| |
|
|
|
|
|
|
| |
This time it shoves all the logging data into packaging.log
This commit has some hacks to work around yum issues. I've discussed
with upstream and they're going to work on better APIs around logging in
the future.
|
| |
|
|
|
| |
transifex-client shouldn't be listed as a BuildReq; only check for it
and install as needed if the target requiring it is called by make
|
| |
|
|
|
|
|
|
|
| |
We could have method of nfs:server:/path/ or nfs:server:/path/foo.iso.
Dracut could have left stuff mounted to /run/install/repo or
/run/install/isodir or both. In any case we should detect what's been
left over and setup yum the right way.
This introduces a couple new constants as well.
|
| |
|
|
|
|
|
|
|
| |
Fix translation from AUTOPART_TYPE_BTRFS to DEVICE_TYPE_BTRFS so
we create new devices as btrfs instead of md when btrfs is the
default.
Also close gaps in raid feature selection ui and add checks to
save_right_side to prevent some invalid raid setups.
|
| | |
|
| |
|
|
|
|
| |
The keyboard layout testing text box had no padding and any text you
typed in it looked weird. This patch adds a 6 px border around the
inside to give it some padding.
|
| |
|
|
|
|
|
|
| |
This patch adjusts the coloring for selected mountpoints in the
mountpoint selector widget. Previously, some of the text labels appeared
grey or black on the blue selected background, making it harder to read
them. This patch adjusts those so they go white when selected, and black
or gray (depending on the label) when not selected.
|
| |
|
|
|
| |
Otherwise, previously unselected disks on the storage overview will never
be allowed to be selected.
|
| | |
|
| | |
|
| |
|
|
|
| |
This is not handled by similar code in the software spoke, because that code
is never run for kickstart installs containing a %packages section.
|
| |
|
|
|
|
| |
From libxklavier's changelog:
* Thu Apr 19 2012 Matthias Clasen <mclasen@redhat.com> - 5.2.1-2
- Add a runtime dependency on iso-codes (#813833)
|
| |
|
|
|
|
|
| |
This does the same sort of stuff the previous storage patch did, but for
the custom partitioning screen. It takes the grid that was outside of
the alignment and moves it inside, and also resets the xscale/yscale on
the alignment to 1,1, and sets some of the expand stuff.
|
| |
|
|
|
|
|
|
|
|
|
|
| |
The glade changes here move the grid3 widget into the main alignment
widget in the storage.glade file; previously the grid3 alignment was
adjacent to the alignment widget. When grid3 was outside of the
alignment, there was a consistent and noticeable upper-left-corner =>
lower-right-corner growth motion visible when first entering the spoke.
After putting grid3 inside the alignment, the screen loads up in one go
without any growing or shifting beforehand. Various expand settings and
scale settings on container widgets from the alignment down were also
tweaked.
|
| |
|
|
|
| |
There is an entry for filtering, searching doesn't work (it probably
uses the underlaying non-sorted model) as it not needed.
|
| |
|
|
|
|
|
|
|
| |
Previously, the disk overview widget (visible on the first storage
screen) would display black text on a blue-colored background for
selected items. Attempts to set the foreground color to white using GTK
overrides proved futile, so this patch removes all color overrides and
instead uses GTK state flag setting to achieve the desired affect:
unselected text is black on white; selected text is white on blue.
|
| |
|
|
|
|
|
|
| |
Emitting signals from the function that handles other signals is dangerous
given the synchronous nature of GTK signals, so this was never a good idea
to start with. Then, displaying the dialog from the main loop means it
gets displayed in the lightbox correctly instead of over a completely grey
background.
|
| |
|
|
|
|
| |
This removes code duplicated in desktop.py, and will short circuit the
routine if the user has indicated that they want a graphical boot by way
of kickstart data.
|
| | |
|
| | |
|
| |
|
|
| |
Get rid of unused import, use super(), remove some spaces
|
| |
|
|
|
|
| |
This uses the new constant to link to the right target by name. It also
removes any fiddling with /etc/inittab as we don't want/need to touch
that any more.
|
| | |
|
| | |
|
| |
|
|
| |
We don't provide you with the chance to do anything anyway.
|
| |
|
|
|
|
| |
We are trying to prevent the user from getting to the hub with a space
error, hence why you can only quit. It's still helpful to catch the
errors just in case something sneaks through later.
|
| | |
|
| |
|
|
| |
Related: rhbz#872833
|
| |
|
|
| |
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.
|
