The current ELN builds lack a number of firmware subpackages because
pungi/comps can't resolve the provides/obsoletes for the iwl firmware:
2023-11-08 08:43:12 [ERROR ] No package matches pattern iwl1000-firmware
2023-11-08 08:43:12 [ERROR ] No package matches pattern redhat-release
2023-11-08 08:43:12 [ERROR ] No package matches pattern iwl2030-firmware
2023-11-08 08:43:12 [ERROR ] No package matches pattern iwl2000-firmware
2023-11-08 08:43:12 [ERROR ] No package matches pattern iwl100-firmware
2023-11-08 08:43:12 [ERROR ] No package matches pattern iwl135-firmware
2023-11-08 08:43:12 [ERROR ] No package matches pattern libertas-sd8787-firmware
2023-11-08 08:43:12 [ERROR ] No package matches pattern iwl5150-firmware
2023-11-08 08:43:12 [ERROR ] No package matches pattern iwl6000g2a-firmware
from https://odcs.fedoraproject.org/composes/production/latest-Fedora-ELN/work/x86_64/pungi/BaseOS.x86_64.comps.log
Also add some of the other firmware packages to the hardware-support
group to simply get them into the repos for now.
Signed-off-by: Josh Boyer <jwboyer@fedoraproject.org>
Because the ELN comps are handled differently, they don't automatically
get included in the XMLINFILES and XMLFILES globs. This patch ensures
that they are properly generated when running `make all`.
Fixes: https://github.com/fedora-eln/eln/issues/161
Signed-off-by: Stephen Gallagher <sgallagh@redhat.com>
Both the GNOME (Workstation) and KDE Plasma environments use Wayland
by default and have built-in Wayland-based fallback modes.
If users do not want to have X11 session stuff installed, let them
exclude it. For now, we still install it by default, though.
Now that the sdubby has been reviewed, it needs to be included
in the list of packages that anaconda _may_ install on the target
machine. It should not be installed in the install media/etc
which is grub based, and is explicitly marked as conflicting with
grubby to avoid that.
Futher to avoid grubby and sdubby from both being installed on live
media there is a change in fedora-live-base.ko which excludes
sdubby from live media.
Signed-off-by: Jeremy Linton <jeremy.linton@arm.com>
The issue has been fixed in imsettings. So there are no issues
reverting this commit.
Plus, imsettings-plasma is still needed for X11 session and
to get X11 apps working on Wayland session even.
This reverts commit 7553747fb0.
The issue has been fixed in imsettings. So there are no issues
reverting this commit.
Plus, imsettings-plasma is still needed for X11 session and
to get X11 apps working on Wayland session even.
This reverts commit 98e56a9cf0.
As we found out today -
https://pagure.io/releng/issue/11663 -
the GNOME "classic session" is included in Workstation lives.
Consequently, if its dependencies are broken, Workstation lives
can't be built, and the gating tests fail. So, it should be in
the critical path.
Signed-off-by: Adam Williamson <awilliam@redhat.com>
It is uninstallable as we cannot yet rebuild it with Python 3.12.
Unlike those dropped in the previous commit, upstream still
maintains this project and has a plan for it going forward, so
just comment it out with an explanation instead of removing it.
Signed-off-by: Adam Williamson <awilliam@redhat.com>
These ROS projects are all marked upstream as being unused and
unmaintained. They all do not build or install on Python 3.12.
Rather than spending time fixing unmaintained code, we should
just drop these from the image.
Signed-off-by: Adam Williamson <awilliam@redhat.com>
It's definitely critical (you can wind up with an unusable system
if it's broken). The attempt to land the anaconda webUI change
highlighted that we need to make this change.
Signed-off-by: Adam Williamson <awilliam@redhat.com>
With the advent of alternative bootloaders (systemd-boot) whether
or not grubby gets installed should be dependent on whether grub
is selected as the bootloader. This currently happens correctly
with anaconda and the grub dependencies, so it can be removed
safely. That allows systemd-boot to be installed cleanly without
grubby drippings confusing it.
Sync F40 with F39 since the branch happened before the commit was
merged.
Signed-off-by: Jeremy Linton <jeremy.linton@arm.com>
It's critical for build because we always build packages in mock,
and it's critical for compose because we build live images in
mock.
Signed-off-by: Adam Williamson <awilliam@redhat.com>
With the advent of alternative bootloaders (systemd-boot) whether
or not grubby gets installed should be dependent on whether grub
is selected as the bootloader. This currently happens correctly
with anaconda and the grub dependencies, so it can be removed
safely. That allows systemd-boot to be installed cleanly without
grubby drippings confusing it.
While anaconda may now request sdubby and systemd-boot, i'm
told the comment in the anaconda section isn't 100% accurate
as anaconda may try to install all those selections to the live
images. So, lets not add those to the anaconda comps yet.
Signed-off-by: Jeremy Linton <jeremy.linton@arm.com>
