| Commit message (Collapse) | Author | Age | Files | Lines |
... | |
| |
|
|
|
|
| |
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.
|
|
|
|
|
| |
Live environments have their own way of rebooting, and anaconda doesn't need
to interfere with that.
|
| |
|
| |
|
|
|
|
|
| |
You do this by simply highlighting the currently selected boot device and
clicking the Boot Device button again.
|
| |
|
|
|
|
| |
Related: rhbz#877871
|
|
|
|
|
|
| |
Our current plan for handling of incomplete preexisting LVM does not
involve filtering out or ignoring anything, so this is a good first
step.
|
| |
|
|
|
|
|
|
|
|
|
| |
The obvious example is a VG with no LVs, which could happen because it
actually has no LVs or because only some of its encrypted PVs have been
unlocked.
This may end up being how we handle degraded md and incomplete lvm in
the future.
|
|
|
|
|
| |
Fix the TypeError problem with iutil.execWithCapture() when fatal
and process returns a non-zero exit code.
|
|
|
|
| |
This is so we can test this from unit tests running as non-root.
|
|
|
|
|
| |
Re-arranges a bit of code and handles dracut mounted hd isos.
Also handles a None type on self._currentIsoFile better.
|
| |
|
| |
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
The case:
1) Dracut does not use network so it does not write any ifcfg file
(e.g. DVD install)
2) NM creates default auto connection (DHCP) because it can't find
any ifcfg file for a device.
3) Anaconda writes out default ifcfg file (e.g. ifcfg-eth0)
4) When editing a connection in nm-c-e, ifcfg file of edited default
auto connection (Wired connection 1) is created
(ifcfg-Wired_connection_1).
5) If anaconda tweaks any ifcfg file later (setting ONBOOT, NM_CONTROLLED),
it is the ifcfg-eth0.
6) Both ifcfg files are copied to the target system at the end of
installation
Luckily, the ifcfg-Wired_connection_1 seems to be used after installation,
but bug #870922 suggests it might be not so in all cases.
Anyway, we shouldn't create anaconda's ifcfg-ethX default file in this case.
|
| |
|
| |
|
| |
|
| |
|