This is needed in the astronomy spin when trying to install the
plasma-desktop. This is the error that is seen without it:
```
- package plasma-applet-redshift-control-1.0.18-4.fc28.noarch requires plasma-desktop, but none of the providers can be installed
- nothing provides libibus-1.0.so.5 needed by plasma-desktop-5.12.2-1.fc29.i686
- nothing provides libibus-1.0.so.5()(64bit) needed by plasma-desktop-5.12.2-1.fc29.x86_64
```
Signed-off-by: Dusty Mabe <dusty@dustymabe.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>
koji task 25278678 Fedora-Python-Classroom-armhfp
DEBUG util.py:439: At least 52MB more space needed on the / filesystem.
koji task: 25278682 Spins armhfp KDE
DEBUG util.py:439: At least 104MB more space needed on the / filesystem.
Signed-off-by: Dusty Mabe <dusty@dustymabe.com>
All of these images are failing because more disk space is needed
to install the required rpms. This PR bumps the sizes so that they
should succeed. See [1].
Here are the current failures in rawhide:
koji task: 25182851 Workstation armhfp live image
DEBUG util.py:439: At least 93MB more space needed on the / filesystem.
koji task: 25182858 Spins armhfp LXDE
DEBUG util.py:439: At least 926MB more space needed on the / filesystem.
koji task: 25182869 Spins armhfp Mate
DEBUG util.py:439: At least 121MB more space needed on the / filesystem.
koji task: 25182901 Spins armhfp LXQt
DEBUG util.py:439: At least 180MB more space needed on the / filesystem.
koji task: 25182854 Spins armhfp KDE
DEBUG util.py:439: At least 294MB more space needed on the / filesystem.
[1] https://pagure.io/dusty/failed-composes/issue/9#comment-495037
Signed-off-by: Dusty Mabe <dusty@dustymabe.com>
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>
Needed by a few different things. For example to build the security live
image you run into these problems if you exclude wget:
Problem 1: conflicting requests
- nothing provides /usr/bin/wget needed by openvas-scanner-5.1.1-4.fc27.x86_64
Problem 2: package wireshark-gtk-1:2.4.4-2.fc28.x86_64 requires wireshark-cli = 1:2.4.4-2.fc28, but none of the providers can be installed
- package wireshark-cli-1:2.4.4-2.fc28.i686 requires libsmi.so.2, but none of the providers can be installed
- package wireshark-cli-1:2.4.4-2.fc28.x86_64 requires libsmi.so.2()(64bit), but none of the providers can be installed
- conflicting requests
- nothing provides wget needed by libsmi-0.4.8-21.fc28.i686
- nothing provides wget needed by libsmi-0.4.8-21.fc28.x86_64
Problem 3: package wireshark-1:2.4.4-2.fc28.x86_64 requires wireshark-cli = 1:2.4.4-2.fc28, but none of the providers can be installed
- package wireshark-cli-1:2.4.4-2.fc28.i686 requires libsmi.so.2, but none of the providers can be installed
- package wireshark-cli-1:2.4.4-2.fc28.x86_64 requires libsmi.so.2()(64bit), but none of the providers can be installed
- conflicting requests
- nothing provides wget needed by libsmi-0.4.8-21.fc28.i686
- nothing provides wget needed by libsmi-0.4.8-21.fc28.x86_64
Signed-off-by: Dusty Mabe <dusty@dustymabe.com>
Needed by anaconda. See [1].
```
- package anaconda-28.22-1.fc28.x86_64 requires anaconda-core = 28.22-1.fc28, but none of the providers can be installed
- nothing provides realmd needed by anaconda-core-28.22-1.fc28.x86_64.
```
[1] https://pagure.io/dusty/failed-composes/issue/9#comment-495037
Signed-off-by: Dusty Mabe <dusty@dustymabe.com>
This exclusion has never actually worked. Look at a successful
F27 container-minimal build:
https://koji.fedoraproject.org/koji/taskinfo?taskID=25064051
If you check one of the tasks and look at the oz log, it shows
that libusbx is actually installed.
This is because both dnf and microdnf require libdnf, which
requires librepo, which requires gpgme, which requires gnupg2,
which requires libusb.
In Fedora 27, anaconda/dnf handle this by ignoring the attempt
to exclude libusbx and just installing it anyway.
In Rawhide, however, anaconda/dnf behaviour is different. I
don't know when it changed, but now anaconda/dnf honor the
kickstart and exclude libusbx from the install transaction...
which means the image build just fails, because the deps for
dnf/microdnf cannot be satisfied. So we should just ditch the
exclusion, it's bogus. See a failed Rawhide build attempt:
https://koji.fedoraproject.org/koji/taskinfo?taskID=25077542
Signed-off-by: Adam Williamson <awilliam@redhat.com>
In cloud Images we do this becaue it's generally accepted that
in a cloud environment there are higher level firewall constructs
(i.e. security groups).
The arch-specific sub-packages that provide grub2-efi on each
arch are listed in @anaconda-tools comps group anyway (so this
is redundant), and requiring it by name in a kickstart causes
i686 live image composes to fail because it is no longer built
for i686.
Signed-off-by: Adam Williamson <awilliam@redhat.com>
because Xfce spin is release blocking for arm, and firefox currently
does not build on arm so is excluding it until a fix is landed.
See https://bugzilla.redhat.com/show_bug.cgi?id=1523912
This should be reverted as soon as the above bug is fixed.
When building Fedora Server base images (such as when building F27
Modular Server), the --noboot option results in the container image
attempting to mount /boot with XFS like the rest of the system.
This results in the image-creation failing.
Since the partitions don't matter in the end (the files are tarred
up and shipped that way), we'll skip this optimization.
Signed-off-by: Stephen Gallagher <sgallagh@redhat.com>
This bit was cargo culted from the old school Fedora Cloud image, but we have
also been using `net.ifnames=0` on the kernel command line, which ensures that
we get `eth0` as "the" NIC name. (There's a huge amount of history behind
this and I'm not trying to change that behavior here)
The problem is that those udev rules do *other* things that we do want, such as
ensure that `veth` devices get `NM_CONTROLLED=no`. Without that e.g.
NetworkManager might try to do DHCP on those devices, which is at best slow
since they appear and disappear frequently, and at worst risks the host network
configuration.
For more information, see [RH bz#1503347](https://bugzilla.redhat.com/show_bug.cgi?id=1503347)
Signed-off-by: Colin Walters <walters@verbum.org>
We don't include firstboot in AH, we use cloud-init, so nothing
is ever going to parse this. Drop it, since it shows up as a delta
in `ostree admin config-diff`, and further we want to reduce the
amount of stuff in this ks.
Signed-off-by: Colin Walters <walters@verbum.org>
The `setup` package has this same content, let's not duplicate it. The only
difference between them today is trailing whitespace in our version.
Just trying to reduce the amount of stuff we do here to avoid deltas with bare
metal installs, containers, etc.
Signed-off-by: Colin Walters <walters@verbum.org>
Version 25 of livecd-tools has new tools to help in rebuilding LiveOS images. For example,
* editliveos permits overlay merging and image refreshing,
* editliveos allows overlay and home file system resizing and format changes
* livecd-iso-to-disk allows multi image installation on a single USB disk device
* livecd-iso-to-disk allows sourcing and writing to the same disk device.
Having the livecd-iso-to-disk installer onboard the .iso makes installation of a persistent overlay easier. (Persistent overlays are the standard for SoaS image in a pocket deployment.)
The new tools also work with OverlayFS overlays.
While booting Atomic cloudImage, we want to see kernel messages
on both VGA and serial console. It works fine with
tty1(vga console) and ttyS0(serial console) on x86_64 arch.
But, aarch64 and ppc64le doesn't use ttyS0 as serial console.
Instead, they use ttyAMA0(aarch64) and hvc0 (ppc64le).
Also, good point is that if a serial console specified in kernel
boot parameter is not supported on a given hardware platform, it
gets ignored. For example: console=ttyAMA0 and console=hvc0 will
get ignored on x86_64
Fixes: https://pagure.io/atomic-wg/issue/347
Signed-off-by: Sinny Kumari <sinny@redhat.com>
