See https://pagure.io/fedora-kiwi-descriptions/pull-request/203 -
same change, same justification. This only pulls in anaconda-gui
and anaconda-tui, and we do not necessarily want those now that
anaconda-webui exists.
Lives that really need to use GTK UI not web UI can include
anaconda-gui in their own manifests.
Signed-off-by: Adam Williamson <awilliam@redhat.com>
It seems like this worked for Cinnamon and Games, and Sway has
the same problem, so let's do it there too.
Signed-off-by: Adam Williamson <awilliam@redhat.com>
Cinnamon image build is failing at the moment, and I see this in
the logs:
2025-07-22T15:44:31+0000 [260] INFO RPM callback start %posttrans scriptlet "kernel-core-0:6.16.0-0.rc7.58.fc43.x86_64"
2025-07-22T15:44:31+0000 [260] INFO [scriptlet] grub2-probe: error: ../grub-core/kern/fs.c:123:unknown filesystem.
2025-07-22T15:44:38+0000 [260] INFO [scriptlet] dracut[W]: Running in hostonly mode in a container!
2025-07-22T15:44:38+0000 [260] INFO [scriptlet] dracut[E]: No '/dev/log' or 'logger' included for syslog logging
2025-07-22T15:45:09+0000 [260] INFO [scriptlet] dracut[E]: No '/dev/log' or 'logger' included for syslog logging
2025-07-22T15:46:20+0000 [260] INFO [scriptlet] cp:
2025-07-22T15:46:20+0000 [260] INFO [scriptlet] error copying '/var/tmp/dracut.dGGDh1v/initramfs.img' to '/boot/initramfs-0-rescue-bc1937eee2a84a8bb3c665a062c4566f.img': No space left on device
2025-07-22T15:46:20+0000 [260] INFO [scriptlet] dracut[F]: Creation of /boot/initramfs-0-rescue-bc1937eee2a84a8bb3c665a062c4566f.img failed
2025-07-22T15:46:20+0000 [260] INFO [scriptlet] /usr/lib/kernel/install.d/51-dracut-rescue.install failed with exit status 1.
2025-07-22T15:46:20+0000 [260] WARNING [rpm] %posttrans(kernel-core-6.16.0-0.rc7.58.fc43.x86_64) scriptlet failed, exit status 1
2025-07-22T15:46:20+0000 [260] INFO RPM callback stop %posttrans scriptlet "kernel-core-0:6.16.0-0.rc7.58.fc43.x86_64" return code 1
I *think* that's probably the issue. So let's try bumping the
root fs size and see if it helps.
Signed-off-by: Adam Williamson <awilliam@redhat.com>
This bumps the root size because image build is currently failing
and I *think* it's a space issue causing kernel-core %post to
fail. If it doesn't work we can revert the space bump.
Also:
* Drop some commented-out lines for packages that have been retired
* Update the comment for leaving out libreoffice
* Add back rogue, since it's building now
Signed-off-by: Adam Williamson <awilliam@redhat.com>
The compose-tracker app doesn't handle groups, so it ends up notifying
@neuro (a user) instead. Drop this so they don't keep getting
notifications they don't care about.
Signed-off-by: Kevin Fenzi <kevin@scrye.com>
Remove the `fedora-disk-minimal.ks` file. Fedora Minimal disk images
are not built by ImageFactory/oz. Having this file here is confusing.
Signed-off-by: Simon de Vlieger <supakeen@redhat.com>
Remove the `fedora-iot.ks` file. Fedora IoT disk images are not built by
ImageFactory/oz. Having this file here is confusing.
Signed-off-by: Simon de Vlieger <supakeen@redhat.com>
The previous maintainers have been inactive on the Games SIG and
lab spin for a couple of years and the most recent keepalive was
answered by JT Pennington.
Thus, reassign to myself as de facto Games SIG chair and JT Pennington
as the last responder for the lab spin.
Reference: https://pagure.io/fedora-pgm/schedule/issue/160
It's failing on Rawhide and F41 because it's running out of
space. It's a few hundred megs over, so let's give it an extra
gig.
Signed-off-by: Adam Williamson <awilliam@redhat.com>
Installed file size is already near limit, and
on rawhide (F42), now compose began to fail at
kernel posttrans scriptlet due to disk size shortage.
So now let's increase size by 20%.
ppc64le live compose for the F41 Beta candidate failed with
"needs 110MB more space on the / filesystem". Here's 384M for a
little bit of headroom.
Signed-off-by: Adam Williamson <awilliam@redhat.com>
This time I actually tested things to confirm that there was enough
size. x86_64 builds fine with this size. aarch64 fails, but not due to
size, it's the dbus aarch64 bug.
Signed-off-by: Kevin Fenzi <kevin@scrye.com>
It seems to need about 1.4G more according to recent failure logs.
Let's give it a bit of a buffer.
Signed-off-by: Adam Williamson <awilliam@redhat.com>
I added a tiny bit of space, but turns out theres not quit enough for
the initramfs to be generated and the compose still fails.
So, lets add 100MB. That should be enough for the scriptlets to
complete.
I'd like to cherry pick this into f40 as well.
Signed-off-by: Kevin Fenzi <kevin@scrye.com>
This is meant to distinguish OCI containers and images that are designed
specifically for Toolbx from others. Toolbx containers are long-lasting
pet containers for interactive command line use, which makes them
substantially different from short-lived containers running services.
Therefore, it can be useful to be able to identify Toolbx containers and
images when generating statistics about Fedora usage.
https://pagure.io/Fedora-Council/tickets/issue/449https://pagure.io/fedora-kickstarts/pull-request/1015
Per https://fedoraproject.org/wiki/Changes/Wget2asWget , wget
has been retired from Rawhide and replaced by wget2-wget.
I think kickstarts *do* resolve Provides so this probably works
okay as-is, but it seems clearer to update the name.
Signed-off-by: Adam Williamson <awilliam@redhat.com>
The initial-setup packages for firstboot were split into their own
comps group that ensures initial-setup-gui is configured to use
kwin as the Wayland compositor.
Since change 48e2c3b559 this kickstart
is pulling in systemd.
This was noticed because since
49306cb6ea started bringing in
weak-dependencies, we started installing systemd-resolved is which
created a symlinked /etc/resolv.conf in the image. Toolbox will not
currently reset this on container start, as it is a symlink (this
behaviour is a bit complicated; see [1]). This leads to an
incompatability running the toolbox on *non* systemd-resolved hosts
(e.g. RHEL9); you are left with a dangling symlink and no
name-resolution in the toolbox.
We do not want systemd in the toolbox image by default it; remove it
from the list. Exclude systemd-resolved specifically, so if something
else brings in systemd we still don't include this.
[1] https://github.com/containers/toolbox/issues/1410
This is a continuation from commit 69555b7b91, which tried to
ensure that all languages are present in the fedora-toolbox OCI image by
removing --inst-langs=en from fedora-container-toolbox.ks. Sadly, this
wasn't enough.
The image was still missing various localization bits like translations
for programs and manuals. All translations for all programs, such as
LC_MESSAGES and LC_TIME, were missing, except for those coming from
glibc-all-langpacks. eg., see:
$ LANG=cs_CZ.UTF-8 cp foo bar
cp: cannot stat 'foo': Adresář nebo soubor neexistuje
Only the part coming from glibc is translated. The part coming from
coreutils isn't. There are lots and lots of such packages. eg., bash,
coreutils, dnf, grep, rpm, sed, tar, etc..
Any package with translated manuals marked with %lang() in their %files
section were missing them. eg., man-db, passwd, psmisc, etc..
Finally, even though the %pre section in fedora-container-toolbox.ks
removes %_install_langs from /etc/rpm/macros.image-language-conf, it was
still set to en_US in the final image.
This was happening because fedora-container-toolbox.ks includes
fedora-container-common.ks, and some unintended bits from the latter
were leaking into the fedora-toolbox OCI image's build.
The image was still being built with '%packages --inst-langs=en',
possibly since fedora-container-common.ks has '%package --instLangs=en'.
That option wasn't just being applied to the packages being installed by
fedora-container-common.ks, but also to those being installed by
fedora-container-toolbox.ks [1].
Secondly, fedora-container-common.ks sets %_install_langs to en_US in
its %post section. This will strip out all non-English languages from
future RPM transactions in containers created from the image.
To address this, fedora-container-toolbox.ks has now been decoupled from
fedora-container-common.ks, by copying over the relevant bits.
[1] https://koji.fedoraproject.org/koji/buildinfo?buildID=2311452https://kojipkgs.fedoraproject.org//packages/Fedora-Container-Toolbox/Rawhide/20231025.n.0/images/fedora-container-toolbox.kshttps://kojipkgs.fedoraproject.org//packages/Fedora-Container-Toolbox/Rawhide/20231025.n.0/images/koji-f40-build-108073454-base.kshttps://kojipkgs.fedoraproject.org//packages/Fedora-Container-Toolbox/Rawhide/20231025.n.0/data/logs/image/oz-aarch64.loghttps://bugzilla.redhat.com/show_bug.cgi?id=2244503https://pagure.io/fedora-kickstarts/pull-request/1002
The base container should always install tzdata to ensure that it is
available for applications built on top of the base container.
The minimal container should never have tzdata installed, and the
application should install it as part of the application dependencies.
Starting with Fedora 39 we have the capability to remove tzdata from
the minimal images without resorting to deleting files:
https://fedoraproject.org/wiki/Changes/AllowRemovalOfTzdata
The Container/Dockerfile equivalent of the fedora-toolbox OCI images
installed all languages by removing %_install_langs (set to en_US by the
fedora base image) from /etc/rpm/macros.image-language-conf [1]. The
Kickstart does the same in the %pre section.
Therefore, it's self-contradictory to have '%packages --inst-langs=en'.
The fedora-toolbox OCI image is meant for interactive command line
environments, not for deploying server applications. Therefore, they
need a fully featured CLI user experience at par with what's offered on
Fedora Silverblue and Workstation. Among the Kickstart files defined
here, other than fedora-container-toolbox.ks, only these ones don't
install all languages:
* fedora-cloud-base.ks
* fedora-container-base-minimal.ks
* fedora-container-base.ks
* fedora-container-common.ks
* fedora-eln-container-base.ks
* fedora-server-vm-full.ks
All the other Kickstarts, and definitely those for Fedora Workstation,
install all languages.
[1] https://src.fedoraproject.org/container/fedora-toolboxhttps://github.com/containers/toolbox/tree/main/images/fedorahttps://bugzilla.redhat.com/show_bug.cgi?id=2244503https://pagure.io/fedora-kickstarts/pull-request/997
The snippet to fix the /run/lock breakage and the lines following it
were copied from the first %post section in fedora-container-base.ks.
However, the %end marker to terminate the previous %pre section, and the
starting %post marker went missing in fedora-container-toolbox.ks
https://pagure.io/fedora-kickstarts/pull-request/993
systemd-boot is not yet supported on live media. Yet we
want it to appear on images where anaconda is installing
a system from RPMs (ex: the server dvd image).
The fix for this problem at the moment is to exclude anaconda
packages during the live media creation.
Signed-off-by: Jeremy Linton <jeremy.linton@arm.com>
It is FTI with Python 3.12, and fixing it requires handling two
rather complex dependency chains:
https://bugzilla.redhat.com/show_bug.cgi?id=2220598
so it's not going to be fixed overnight. Let's drop it from the
spins for now to get them building again.
Signed-off-by: Adam Williamson <awilliam@redhat.com>
This reverts commit ce5b31416f.
The anaconda update with the webUI changes is failing tests,
and we do not have time to resolve this right away. We can't
leave this in place without also pushing the anaconda update
stable and adjusting the openQA tests, so let's revert it for
now so tests pass on other updates, until we can come back and
clean up the webUI stuff tomorrow.
This failed a few weeks ago because the Python 3.12 rebuild was still
going and some dependencies for tracer were missing. I'm now able to
install tracer and its dependencies in rawhide and this change should be
ready to go once more.
https://fedoraproject.org/wiki/Changes/Automatic_Cloud_Reboot_On_Updates
Signed-off-by: Major Hayden <major@redhat.com>
Right now python3-dnf-plugins-extras is not rebuilt against python 3.12,
which causes composes to fail. Lets disable this for now and re-enable
it as soon as it's sorted out.
Signed-off-by: Kevin Fenzi <kevin@scrye.com>
standard pulls in sssd
core pulls in sssd-common
both of those pull in sssd-client, which is excluded in container-common
(to minimize size/deps).
If we need these, we can look at another solution.
Signed-off-by: Kevin Fenzi <kevin@scrye.com>
The guest-configs package does not require oslogin any longer as
upstream dropped the requirement. Add oslogin explicitly here to ensure
it is always present for GCP images.
Signed-off-by: Major Hayden <major@redhat.com>
KDE PIM Apps were previsouly part of @kde-desktop or @kde-apps groups.
We've split them into their own group in [1] and we thus
explicitely include them here.
This should be a nop change for the KDE Spin.
[1] https://pagure.io/fedora-comps/pull-request/824
We can now use a single U-Boot firmware to boot all 64 bit variants
of the Rasperry Pi so we can now simplify this some what.
Signed-off-by: Peter Robinson <pbrobinson@fedoraproject.org>
A recent change to Anaconda[1] now requires that this be available on
the installed system, due to grub2-tools-extra now being part of the
EFI GRUB2 install.
[1] 1891b0f306
Signed-off-by: Stephen Gallagher <sgallagh@redhat.com>
See https://bugzilla.redhat.com/show_bug.cgi?id=2175244#c15 .
We really need libxkbcommon for initial-setup to work properly,
since an ordering change in systemd 253. This exclusion causes
it to get dropped. libxkbcommon requires xkeyboard-config; since
systemd only recommends libxkbcommon (rather than hard requiring
it), the solver decides to honor the request to exclude
xkeyboard-config by dropping both it and libxkbcommon.
Signed-off-by: Adam Williamson <awilliam@redhat.com>
There's a few bits of armhfp dregs hanging around so lets
clean them up as they're no longer used.
Signed-off-by: Peter Robinson <pbrobinson@fedoraproject.org>
fedora-kde-minimization.ks only tried to remove scim* and iok.
iok hasn't existed since F30. scim* packages still exist, but
nothing requires or recommends any of them, and none of them are
listed as default or mandatory in comps, so I don't think this
does anything.
mariadb: we do still ship both mariadb and community-mysql, and
they have overlapping provides. However, the only thing that
requires 'mysql-server' is kf5-akonadi-server-mysql , and that
also recommends 'mariadb-server', which should break the tie
without needing these lines.
system-config-*: none of these exist any more.
desktop-backgrounds-basic: no longer listed in base-x.
gnome-disk-utility: we already drop the entire admin-tools
group above, so there's no need to try and drop one package from
it too.
kdeaccessibility and kdeartwork don't exist any more.
Commented-out lines were dropped, there's no point having
commented-out lines with no explanation why they're there.
Signed-off-by: Adam Williamson <awilliam@redhat.com>
These are not useful on the KDE desktop and come in through a
weak dependency in GTK3.
We don't need or want this, as it's redundant with what KDE Plasma
provides already.
Fixes: https://pagure.io/fedora-kde/SIG/issue/124
mpage is only 60K in size and requires only libc and rtld. Seems
worthless to drop it.
isdn4k-utils doesn't exist any more.
For the sane stuff: nothing sane-related is pulled into most
images any more. cinnamon-desktop, design-suite and
gnome-desktop list some SANE packages, but that clearly means
they *want* to include them, and the kickstarts for those
spins don't include fedora-live-minimization anyway. The
'graphics' group lists xsane-gimp conditional on gimp being
included, but no desktop environment or kickstart includes the
'graphics' group as a default, so it won't be on any live images.
This leaves only hplip in the file. That *is* of significant
size and *would* be pulled into most of the spins which include
this file, so we can't drop it yet at least. There may be an
argument for dropping it from comps with the current state of
IPP Everywhere support, I guess.
Signed-off-by: Adam Williamson <awilliam@redhat.com>
Extend cloud base image and customize for Azure:
1. Don't install QEMU guest agent
2. Install WALinuxAgent
3. Configure chrony to use virtual PHC
4. Configure sshd with ClientAliveTimeout 120 to prevent
ssh timeouts
Performed some basic tests by generating an image with:
1. Using QEMU (using direct kernel boot) with
Fedora-Server-netinst-x86_64-36-1.5.iso and a flattened
kickstart with poweroff instead of reboot
2. Converted QCOW2 to VHD using:
qemu-img convert -o subformat=fixed,force_size -O vpc ...
3. Uploading image and created VM, verifying:
- cloud-init configures system
- chrony using PTP configuration
- waagent service installed (but not running until presets
are approved)
- SSH configuration and functional
Signed-off-by: Chris Patterson <cpatterson@microsoft.com>
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>
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>
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>
This actually led to the filesystems being bigger.
The most recent Fedora Rawhide images were ~900MB instead of ~300MB.
Clearly, we need this to make it smaller.
This reverts commit d4d8bffb2c.
Signed-off-by: Neal Gompa <ngompa@fedoraproject.org>
Without this, there is no guarantee that BIOS would
be correctly set up if the install environment is UEFI.
Fixes: 611edda149
Signed-off-by: Neal Gompa <ngompa13@gmail.com>
Fedora Cloud is now set up so that it builds the disk with
GPT partitioning and has a specific partitioning layout so
that the resulting images are equipped to boot either with
legacy BIOS or UEFI.
Reference: https://fedoraproject.org/wiki/Changes/FedoraCloudHybridBoot
Signed-off-by: Neal Gompa <ngompa13@gmail.com>
The Plasma Wayland session does not work when kernel mode-setting has
been disabled, so fall back to X11 automatically in this scenario.
Signed-off-by: Neal Gompa <ngompa13@gmail.com>
There is a potential issue with how dtb files are symlinked in /boot
if the kernel-lpae is installed last the symlink is pointed there and
not all dtb files will be available. kernel-lpae should be installed
intentionally
Signed-off-by: Dennis Gilmore <dennis@ausil.us>
We already install glibc-minimal-langpack and langpacks-en_GB
pulls the dejavu-sans-fonts which is almost 6MB.
Signed-off-by: Clement Verna <cverna@tutanota.com>
NetworkManager has changed the defaults for where the config
files are retained and by default we don't ship the traditional
Sys-V network scripts so we can clean-up those bits.
Signed-off-by: Peter Robinson <pbrobinson@fedoraproject.org>
Primarily changes for UEFI on ARMv7 but also some cleanups/updates
for the arm/aarch64 images.
Signed-off-by: Peter Robinson <pbrobinson@fedoraproject.org>
This commit restore workstation-release needed for workstation
base installation and attempt to fix post-installation favourite apps on
dash board.
Signed-off-by: Luya Tshimbalanga <luya@fedoraproject.org>
Commit 3dadef5a21 didn't actually work
because it set the value as root. This commit fixes it to set it under
the liveuser instead.
Thanks to adamw for figuring out what's going on!
This update restore the workstation-release to make the installation easier
in addition of minor fixes
Signed-off-by: Luya Tshimbalanga <luya@fedoraproject.org>
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.