Both the kickstart itself and imgcreate expect chkconfig to be
available in the installed system, so we'd better make sure it
is. Up till Fedora 30 Beta it was getting pulled in somehow;
since Fedora-30-20190330.n.3 it seems it is not (probably not
in Rawhide either). In any case, it's clearly correct to list it
explicitly.
See https://bugzilla.redhat.com/show_bug.cgi?id=1695637
Signed-off-by: Adam Williamson <awilliam@redhat.com>
As livesys and livesys-late are still SysV services, they need
systemd-sysv-install to work, which is part of chkconfig. Until
now chkconfig was getting pulled into live images via packages
that require update-alternatives, which was previously part of
chkconfig - but it just got split into its own package, so now
those packages don't pull in chkconfig any more.
This broke the KDE live image and probably several others in
recent Rawhide, livesys and livesys-late don't run so there's
no 'liveuser' and root isn't accessible. Workstation didn't
break because a java package still pulls chkconfig into it.
Signed-off-by: Adam Williamson <awilliam@redhat.com>
Now lxqt-l10n package is obsoleted. And we are adding a @lxqt-l10n to compos. So adjusting kickstart files accordingly.
Signed-off-by: Zamir SUN <sztsian@gmail.com>
Recently all Anaconda files required only for the live installation
(the liveinst script, the desktop file and others) have been split into a sub-package
called anaconda-live.
This was done to prevent these files from littering both network
installation images as well as user systems when Anaconda gets pulled
in as a dependency during a package installation transaction.
At the moment anaconda-live is stilled pulled in as a direct dependency
of the anaconda-gui sub package, but once this commit has been merged
into the Fedora kickstart repository, we can drop this temporary
dependency, removing the package from non-live installations.
It was removed from the @core group in fedora-comps d7faeb5,
but we are still using stone-age sysv-style scripts for the
early boot live image setup stuff (livesys and livesys-late),
so we need it installed in live images. Without this, lives are
utterly broken, because livesys fails almost immediately and
does not do any of the expected live customizations.
Signed-off-by: Adam Williamson <awilliam@redhat.com>
For livemedia-creator builds, inject install code into the lorax
template live/x86.tmpl that copies the script livecd-iso-to-disk
into the .iso filesystem at /LiveOS when livecd-tools is present in
the install image. This fixes commit 18d30b3, which failed in this.
From Adam Williamson:
The Python Classroom spin images no longer build in recent Rawhide,
because of a dnf behaviour change that exposes dependency issues as
failures rather than hiding them by silently excluding packages. (This
change will likely get into F29 soon too).
The issue is this. fedora-live-python-classroom.ks includes
fedora-live-minimization.ks , which does this:
-sane-backends
but it also includes fedora-live-workstation.ks, which includes fedora-
workstation-common.ks, which does this:
@gnome-desktop
...and @gnome-desktop includes sane-backends-drivers-scanners and
libsane-hpaio, which both require sane-backends.
Until recently dnf was simply silently excluding sane-backends-drivers-
scanners and libsane-hpaio from the image, to 'resolve' this. Now it
fails on the problem, and we get to make a choice.
You basically have three options:
1. Just drop fedora-live-minimization.ks from fedora-live-python-
classroom.ks . It's pretty old and random at this point. It's basically
trying to drop printing and scanning stuff to save a bit of space. Do
you actually want printing and scanning not to work on your image?
2. Keep fedora-live-minimization.ks but explicitly add back `sane-
backends` to %packages in fedora-live-python-classroom.ks . This would
override the exclusion and fix the dep issue, and include the scanning
bits in the image.
3. Keep fedora-live-minimization.ks and add excludes for sane-backends-
drivers-scanners and libsane-hpaio to fedora-live-python-classroom.ks .
This would lose scanning support, and save a bit of space.
I went with option 1.
Make sure that we do not install grubby on the
container base image.
https://pagure.io/releng/issue/7872
Signed-off-by: Clement Verna <cverna@tutanota.com>
