This reverts commit 1841b368ce. It
turns out we need to revert to older lorax that uses syslinux for
now - see https://pagure.io/pungi/issue/1608 - so we need it back
in the live kickstart too.
It only has syslinux in it (it used to also have memtest86+ till
we dropped that), and we're not using syslinux any more.
syslinux was also listed in anaconda-tools so this was really
kinda redundant; we will replace syslinux with the necessary
grub2 packages in comps.
Signed-off-by: Adam Williamson <awilliam@redhat.com>
It's mounting non-removable devices and causing problems for
anaconda. Note, KDE will still show a notification with a
button for mounting the device, and it shows in the file manager
where clicking on it mounts it; the behaviour is about the same
as Fedora 35 (slightly better, as the notification shows on
subsequent plugs of the same stick, which it did not in F35).
Signed-off-by: Adam Williamson <awilliam@redhat.com>
This reverts commit 093733933f.
BuildError: Failed to parse kickstart file '.../fedora-disk-python-classroom.ks' : The following problem occurred on line 12 of the kickstart file:
The part/partition and autopart commands can't be used at the same time.
Just setting `download-updates=false` seems not to be enough any
more, we get update notifications in live images currently. This
should fix that and also disable the Updates pane on GNOME
Software in the live environment, which is a nice improvement.
https://gitlab.gnome.org/GNOME/gnome-software/-/issues/1683#note_1408750
Signed-off-by: Adam Williamson <awilliam@redhat.com>
Appending console=tty0 is problematic for many arm use cases.
lets make sure we remove it so systems can just boot
https://bugzilla.redhat.com/show_bug.cgi?id=2022757
Signed-off-by: Dennis Gilmore <dennis@ausil.us>
If the file was not present, the command would fail and the compose
would not proceed.
This is currently blocking container base image generation for ELN.
Signed-off-by: Stephen Gallagher <sgallagh@redhat.com>
ELN needs to import the current key as well as keys a few releases
back, since it doesn't (currently) re-sign at Fedora branching.
Signed-off-by: Stephen Gallagher <sgallagh@redhat.com>
In 1f3645b72d we added a removal of
util-linux, so this section had both:
%packages --excludedocs --instLangs=en --nocore --excludeWeakdeps
util-linux
...
-util-linux
This changes the first of those two entries to include
util-linux-core instead of util-linux, so these two directives do
not conflict.
Signed-off-by: Stephen Gallagher <sgallagh@redhat.com>
This stuff is now properly part of the cloud-init package,
so we don't need this anymore.
This reverts commit 88452ac290.
Signed-off-by: Neal Gompa <ngompa@fedoraproject.org>
It does not work properly on Wayland by default and Plasma
has its own language selector.
Fixes: https://pagure.io/fedora-kde/SIG/issue/143
Signed-off-by: Neal Gompa <ngompa@fedoraproject.org>
Todays rawhide failed due to needing another 14MB.
Increase it a bit more than that tho because it may have failed when it
hit the first package it ran out of space on. We should of course figure
out why it's growing too.
Signed-off-by: Kevin Fenzi <kevin@scrye.com>
Set up the generic aarch64 Raspberry Pi U-Boot so that we can
boot any new device that we may not have specific support for.
We'll use this method to support the new Zero 2 W.
Signed-off-by: Peter Robinson <pbrobinson@fedoraproject.org>
- make it leaner by limiting to comp neuro tools only, and removing
extra analysis tools (which users can install when required)
Signed-off-by: Ankur Sinha (Ankur Sinha Gmail) <sanjay.ankur@gmail.com>
During the kickstart of the cloud image, NetworkManager writes an
/etc/resolv.conf that contains `nameserver 192.168.122.1`. This causes
boot delays with cloud-init since it does some early boot DNS
redirection tests before talking to the cloud's metadata service. On
some clouds/architectures, this delay is 15 seconds or more.
Truncate the /etc/resolv.conf so it can be replaced properly by
NetworkManager and cloud-init on the first boot.
Signed-off-by: Major Hayden <major@redhat.com>
This reverts both commits trying to enable initial-setup on first boot
for the KDE Live Spin as this is not working as expected right now.
This reverts commit 8afe142dcb.
This reverts commit 8e6d33c408.
Previous change enabled it for the LiveISO directly instead of the final
system as this was meant for usage in RAW disk images and not in
LiveISOs.
This change should enable it for both, be a NOP for the LiveISO and
effectively enable it on the final system until we find a better
solution in Anaconda itself.
See discussion in https://github.com/rhinstaller/initial-setup/issues/136
Fixes: 8a3b18b fedora-live-kde.ks: Enable initial-setup on firstboot
To make OEM installs, we need to move the user account, timezone and
network setup to first boot setup steps. This enables initial-setup to
do just that. Once this is confirmed as working, we can remove the user
setup spoke from the initial Anaconda installation dialog.
VM images on POWER require a PReP partition to be able to boot.
Since we don't have a way to define this archfully for now,
let's just always create it. Losing 4MB isn't that bad, anyway...
Signed-off-by: Neal Gompa <ngompa@fedoraproject.org>
These are tiny packages that just add the desktop files to access
functionality that's already included as part of the rest of LibreOffice.
Fixes: https://pagure.io/fedora-kde/SIG/issue/103
Signed-off-by: Neal Gompa <ngompa@fedoraproject.org>
