The zram package and its zram-swap service are obsoleted as part
of the swaponzram change.
https://fedoraproject.org/wiki/Changes/SwapOnZRAM
Signed-off-by: Chris Murphy <chrismurphy@fedoraproject.org>
This is done so that it's easy spot large packages that are not
necessary and identify packages that have grown in size too much
by diffing the image compose logs.
sed "s/rpm -qa/rpm -qa --qf '%{size}\\\\t%{name}-%{version}-%{release}.%{arch}\\\\n' |sort -rn/" -i *.ks
The "auth --useshadow --passalgo=sha512" is long default and auth option
itself has moved to authselect and is obsolete so this actually pulls
in extra dependencies. Drop it as the shadaow and sha512 are defaults.
Signed-off-by: Peter Robinson <pbrobinson@fedoraproject.org>
The livecd-tools/imgcreate issue where it still used chkconfig to enable services
was resolved with release 27.0-1 so the chkconfig requirement can now be dropped.
Signed-off-by: Peter Robinson <pbrobinson@fedoraproject.org>
We don't ship traditional network scripts in any of the arm
images anymore so this is a no-op.
Signed-off-by: Peter Robinson <pbrobinson@fedoraproject.org>
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>
ksvalidate complains that "bootloader extlinux" is invalid
ksflatten changes the bootloader option to
"bootloader --location=mbr" we get working configuration using
the updated option so setting the default to it. The Jenkins
job on pagure is failing due to invalide syntax
Signed-off-by: Dennis Gilmore <dennis@ausil.us>
When trying to build python classroom for armhfp we end up
in quite a dependency hell. Hunspell was the first issue
(fixed in the previous commit). Then there was all of this:
```
Problem 1: conflicting requests
- nothing provides libedataserver-1.2.so.23()(64bit) needed by gnome-shell-3.27.1-5.fc28.x86_64
Problem 2: conflicting requests
- nothing provides dleyna-renderer needed by gnome-photos-3.27.90-1.fc28.x86_64
Problem 3: conflicting requests
- nothing provides gnome-user-docs needed by gnome-getting-started-docs-3.26.2-2.fc28.noarch
Problem 4: package NetworkManager-openconnect-gnome-1.2.4-9.fc28.x86_64 requires libopenconnect.so.5()(64bit), but none of the providers can be installed
- conflicting requests
- nothing provides libtspi.so.1()(64bit) needed by openconnect-7.08-5.fc28.x86_64
Problem 5: package gnome-initial-setup-3.27.90-2.fc28.x86_64 requires gdm, but none of the providers can be installed
- package gdm-1:3.27.4-4.fc28.i686 requires gnome-shell, but none of the providers can be installed
- package gdm-1:3.27.4-4.fc28.x86_64 requires gnome-shell, but none of the providers can be installed
- conflicting requests
- nothing provides libedataserver-1.2.so.23()(64bit) needed by gnome-shell-3.27.1-5.fc28.x86_64
Problem 6: package gnome-shell-extension-window-list-3.27.1-3.fc28.noarch requires gnome-shell-extension-common = 3.27.1-3.fc28, but none of the providers can be installed
- package gnome-classic-session-3.27.1-3.fc28.noarch requires gnome-shell-extension-window-list = 3.27.1-3.fc28, but none of the providers can be installed
- package gnome-shell-extension-common-3.27.1-3.fc28.noarch requires gnome-shell >= 3.27.1, but none of the providers can be installed
- conflicting requests
- nothing provides libedataserver-1.2.so.23()(64bit) needed by gnome-shell-3.27.1-5.fc28.x86_64
Problem 7: conflicting requests
- package gdm-1:3.27.4-4.fc28.i686 requires gnome-shell, but none of the providers can be installed
- package gdm-1:3.27.4-4.fc28.x86_64 requires gnome-shell, but none of the providers can be installed
- nothing provides libedataserver-1.2.so.23()(64bit) needed by gnome-shell-3.27.1-5.fc28.x86_64
```
Note: I used an x86_64 machine to do the dependency debugging.
So here is what I decided to do:
- remove `-evolution*` (evolution-data-server provides libedataserver-1.2.so.23()(64bit))
- remove `-trousers-lib` (trousers-lib provides libtspi.so.1()(64bit))
- add `-gnome-photos` since a lot of other gnome apps were excluded
- add `-gnome-getting-started-docs` since gnome-user-docs was excluded
Signed-off-by: Dusty Mabe <dusty@dustymabe.com>
So is seems that if you remove the machine-id file it won't regenerate the file
but if you touch the file and leave it empty on boot it'll put a new machine-id
in the empty file. So work around this bug ("feature"?) by touching the file
so we don't have other issues in the process.
We're track the outcome of this in RHBZ 1379800
images without any change to the process (except they have a small 30Mb
partition at the begining of the image) but all exisiting documented
processe work for image writing. The RPi is auto configured and a pure
dd to the card, plug and boot.
As referenced on the arm list [1] and as already being done on the docker image we
should remove the unique /etc/machine-id file on compose artifacts to ensure it's
regenerated and unique on each deployed host/device. This unifies the process across
all base ks so it's inherited for each artifact.
[1] https://lists.fedoraproject.org/archives/list/arm@lists.fedoraproject.org/message/Q3YZVF5P2OLLPUJQ2LYZSTKWGGDIU6QO/
Signed-off-by: Peter Robinson <pbrobinson@gmail.com>
Due to #1369794 , anaconda cannot currently manipulate sysv
services in F25+. So to work around this, take 'network' out of
the services lines in all kickstarts and instead manipulate
it in the %post section, with chkconfig.
Also remove rsyslog from the Atomic image services line because
it doesn't appear to be included in the OStree tree at present
and so attempting to enable the service breaks Atomic image
compose, see e.g.:
https://kojipkgs.fedoraproject.org//work/tasks/9022/15349022/oz-x86_64.log
also correct the name of the ssh service in fedora-arm-base.ks;
it's sshd not ssh.
With e2fsprogs after 1.43 the 64bit and metadata_csum features are
enabled by default. These features are not currently supported in
u-boot and the 64bit feature introduces changes such that it cannot
be read by implementations that do not support it. U-Boot does not
support the functionality and hence now won't mount it just in case
it corrupts the filesystem, which is a reasonable response, this how
ever stops us from booting when we have a ext4 /boot file system
which means basically we end up with a pot plant. Go back to using
ext3 for the time being as the mkfs.ext3 option doesn't enable these
features and we get booting systems!! YAY \o/
initail-setup.service now handles running both the gui mode and text
mode running of initial-setup so just enable the one service and no
longer do any special handling rhbz#1296495
Signed-off-by: Dennis Gilmore <dennis@ausil.us>
This is pretty cosmetic as live and cloud images don't use passwords
and they install with sha512 fine, but some people may use these
kickstarts as a base for their spins, so we should use best practices.
remove vfat kickstarts, we are going to use u-boot in raw space
without needing two sets of images with different partitioning we
can remove the seperate partitioning snippets and put the
partitioning in base.
