| Age | Commit message (Collapse) | Author |
|
These are ported over from fedora-kickstarts with some small
cleanups.
|
|
These are ported over from fedora-kickstarts with some small
cleanups.
|
|
These are ported over from fedora-kickstarts with some small
cleanups.
|
|
These are ported over from fedora-kickstarts with some small
cleanups.
|
|
These are ported over from fedora-kickstarts with some small
cleanups.
|
|
This is only needed for disk images that aren't for cloud environments
or server workloads.
|
|
This now exists as of fedora-release-44-0.9.
This reverts commit b6d7ae177da96ac9d472a1309b96ae9514ba749f.
|
|
The conditional was getting skipped due to a missing whitespace and
the editenv command was never getting run. Additionally, we should
be using the boot_indeterminate flag for first boot instead of boot_success.
|
|
A useful default /etc/sysconfig/kernel is now shipped as part of
grubby as of grubby-8.40-86, so this is not needed.
Reference: https://src.fedoraproject.org/rpms/grubby/c/482a2825c47c4fd28a18beb279a3e826461bf878
|
|
https://pagure.io/fedora-kiwi-descriptions/c/1e74928eb0719b1cb3548434a58d9ffd0c4d21fd
https://pagure.io/fedora-comps/pull-request/1206
|
|
This lets us free up the space allocated for the partition and gives
us dynamically allocated space for boot data like we have with the
rest of the operating system.
We do not do this for s390x because zipl does not support it.
Reference: https://fedoraproject.org/wiki/Changes/BtrfsBootForCloud
|
|
Plasma Setup is an out of box setup experience service
that is now included by default with KDE Plasma.
Reference: https://fedoraproject.org/wiki/Changes/Unified_KDE_OOBE
|
|
The Fedora LXDE spin does not have a fedora-release variant,
so the image build fails when trying to request one.
This is an error in fedora-release and will (hopefully) be eventually
fixed. For now, disable the block requesting it so we can restore it
later.
|
|
This is once again present in Fedora, so ship it again.
This reverts commit 01d839d633816b2f9804c64331379d4051a15805.
|
|
Since`rootfiles` now uses systemd-tmpfiles to install dotfiles under
root folder instead of copying.
|
|
Since`rootfiles` now uses systemd-tmpfiles to install dotfiles under
root folder instead of copying.
|
|
Excluding the locale data allows programs running under FEX to use the
hosts locale data and thus the use of any non-english locale already
installed by the user.
|
|
Wine in Fedora 43 is built with WoW64 which supports running 32-bit
Windows applications with 64-bit wine build.
While this might cause regressions in some corner cases it reduces the
image size considerably. The xz compressed erofs image shrank from
~1090MB to ~933MB.
|
|
Those are no longer needed. The system mesa contains fully functioning
asahi OpenGL/Vulkan drivers so there is no need to provide older
llvm-libs and clang-libs for mesa overlays.
|
|
Signed-off-by: Troy Dawson <tdawson@redhat.com>
|
|
Signed-off-by: Troy Dawson <tdawson@redhat.com>
|
|
With the increase in content in initramfs, a long-overdue raise
of the default size for /boot is warranted.
Reference: https://fedoraproject.org/wiki/Changes/2GbootPartition
|
|
With the increase in content in initramfs, a long-overdue raise
of the default size for /boot is warranted.
Reference: https://fedoraproject.org/wiki/Changes/2GbootPartition
|
|
See https://bugzilla.redhat.com/show_bug.cgi?id=2360056#c45 .
python3-boto3 is a very optional dependency of sos, not worth the
space.
Signed-off-by: Adam Williamson <awilliam@redhat.com>
|
|
Anaconda Initial Setup is no longer used for Fedora COSMIC images.
|
|
Signed-off-by: Troy Dawson <tdawson@redhat.com>
|
|
This ensures that there's empty space for arm-image-installer to
inject firmware blobs into images as part of preparing to install
for various single board computers.
|
|
This ensures that there's empty space for arm-image-installer to
inject firmware blobs into images as part of preparing to install
for various single board computers.
|
|
nss-mdns is not included in RHEL, and mesa-vulkan-drivers is x86_64 only.
|
|
Signed-off-by: Troy Dawson <tdawson@redhat.com>
|
|
WSL does not support SELinux, so at best it's pointless to install. This
also actively breaks WSL 1 users, although I don't think we should
suggest that we support that, and if the policy on the builder doesn't
match the target things break during the build.
It also reduced the build time from ~80 seconds to ~70 seconds for me,
so that's nice.
See: 39b379f7d ("wsl: drop the SELinux packages from the WSL base image")
Signed-off-by: Jeremy Cline <jeremycline@linux.microsoft.com>
|
|
WSL does not support SELinux, so at best it's pointless to install. This
also actively breaks WSL 1 users, although I don't think we should
suggest that we support that, and if the policy on the builder doesn't
match the target things break during the build.
It also reduced the build time from ~80 seconds to ~70 seconds for me,
so that's nice.
Signed-off-by: Jeremy Cline <jeremycline@linux.microsoft.com>
|
|
shim-ia32 no longer exists at present. We can talk with pjones
about bringing it back, but for now, this is preventing Rawhide
composes from working.
Signed-off-by: Adam Williamson <awilliam@redhat.com>
|
|
|
|
The anaconda-webui package is now installed by default for live
media, so these are no longer necessary.
|
|
The package called 'anaconda' is empty and only depends on two
things, anaconda-gui and anaconda-tui. Since anaconda 43.32,
anaconda runs the GTK UI if it's installed; it will only run the
web UI if anaconda-gui is not installed. So by including anaconda
we are forcing lives to run GTK UI and not really gaining
anything - we don't want anaconda-tui on lives anyway, I don't
think.
The anaconda-live package will pull in anaconda-webui, so all we
need to do is stop including anaconda. This will cause all live
images to use web UI, which was the intent of
https://github.com/rhinstaller/anaconda/pull/6530 . I guess if
any lives really want/need to use GTK UI, they can put
anaconda-gui into their profiles.
Signed-off-by: Adam Williamson <awilliam@redhat.com>
|
|
|
|
This restores support for booting on 64-bit x86 systems that use
32-bit EFI platforms.
Reference: https://fedoraproject.org/wiki/Changes/32BitUefiSupport
|
|
This reverts commit 24c4fc39c2995e12610173acfdce689497a84120.
With a PR we can run the tests on openQA staging, identify any
problems with the change, and extend the tests to cover the
additional screens that show up with KDE.
|
|
Signed-off-by: Troy Dawson <tdawson@redhat.com>
|
|
This reverts commit e4d801674c86b0675f0ff6fed8c8fee0e5e47546.
openQA has not yet been prepared for this change and it is
causing all updates to fail gating. We need to prepare the tests
before merging this.
|
|
dedupe
Per erofs upstream, this results in faster and more efficient build times
with improved runtime performance.
Signed-off-by: Neal Gompa <ngompa@fedoraproject.org>
|
|
While the Web UI is still missing two features outlined in the Change Proposal [1], enabling it
early will help identify additional issues and improve integration. The missing features are:
- Date/Time Configuration Screen (currently implemented by GIS in Workstation)
- Configurable Browser Support (currently hardcoded to Firefox)
[1] https://fedoraproject.org/wiki/Changes/AnacondaWebUIforFedoraSpins#Detailed_Description
|
|
Fixes https://github.com/fedora-cloud/docker-brew-fedora/issues/119
Signed-off-by: Clement Verna <cverna@tutatnota.com>
|
|
The sshfs sharing backend doesn't work in containers where the default
one works just fine. To make the --isolated builds more accessible just
use the default.
The default in kiwi is currently: --9p-sharing
|
|
Signed-off-by: Troy Dawson <tdawson@redhat.com>
|
|
The serial device name on Arm is ttyAMA, not ttyS. This splits the
configuration for ELN images based on the architecture and adjusts the
kernel command line.
Note that prior to this change, aarch64 would still output kernel logs
to the ttyAMA0 console (on Azure, at least) due to the ACPI SPCR table.
On aarch64 the console in this table, if it's present, is _always_
configured as the kernel's default console. However, systemd logs would
not be sent to the serial console because it seems it was honoring the
kernel command line configuration which had ttyS0 as the default.
Note: this is the exact same change as 4979662a547e ("Cloud: Adjust
aarch64 images to use the correct serial console"), if you're reverting
this, you probably want to also revert that one.
Also see: https://pagure.io/cloud-sig/issue/394
Also see: https://bugzilla.redhat.com/show_bug.cgi?id=1661288
Signed-off-by: Jeremy Cline <jeremycline@linux.microsoft.com>
|
|
The serial device name on Arm is ttyAMA, not ttyS. This splits the
configuration for Cloud images based on the architecture and adjusts the
kernel command line.
Note that prior to this change, aarch64 would still output kernel logs
to the ttyAMA0 console (on Azure, at least) due to the ACPI SPCR table.
On aarch64 the console in this table, if it's present, is _always_
configured as the kernel's default console. However, systemd logs would
not be sent to the serial console because it seems it was honoring the
kernel command line configuration which had ttyS0 as the default.
Also see: https://pagure.io/cloud-sig/issue/394
Also see: https://bugzilla.redhat.com/show_bug.cgi?id=1661288
Signed-off-by: Jeremy Cline <jeremycline@linux.microsoft.com>
|
|
This introduces extra validation for WSL image creation to ensure
the result is usable.
|
|
This introduces extra validation for WSL image creation to ensure
the result is usable.
|