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>
2023-02-28 10:39:14 +00:00
56 changed files with 487 additions and 373 deletions
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.
