We were previously using the compose url where pungi created the
ostree. We now need to use the prod url (the one that clients use)
since we aren't currently building ostrees and qcows in the same
pungi run. Bodhi is currently building the ostrees outside of pungi.
These are our dev images we create from the updates ref. Once
tested and verified we then promote that ref from the tested
images to an officially release ostree version.
Signed-off-by: Dusty Mabe <dusty@dustymabe.com>
There's a number of dependencies that are being excluded but are needed by core
MATE components so the arm images fail because of this. Also fix the mp3 support
package as that's now in gstreamer1-plugins-ugly-free
Signed-off-by: Peter Robinson <pbrobinson@fedoraproject.org>
Taking the first step towards enabling gpg verification for our
users we'll make it so that the media they download will verify
gpg signatures of commits by default.
The next step is to enable gpg verification during install as well
but there is a race condition where the commit that was just created
might not yet be signed. See [1] for more details.
[1] https://pagure.io/pungi/issue/650
(cherry picked from commit 467f7dcb3c)
The installs don't quite hit on the default base image size so
increase it for both spins so they will build.
Signed-off-by: Peter Robinson <pbrobinson@fedoraproject.org>
So make is needed by openssl and compat-openssl10 which is turn is needed
by key things such as qt5-qtbase, mariadb and other core things that are
explictly needed in the KDE spin. I have no idea why the ARM images fail
and the live media does not because all arches have this dep.
Signed-off-by: Peter Robinson <pbrobinson@fedoraproject.org>
So MATE removes PackageKit and then tried to add PackageKit-command-not-found
which is contradictary and will fail to install so drop the later so things
will at least compose.
Signed-off-by: Peter Robinson <pbrobinson@fedoraproject.org>
a59dfe5 caused us a few problems:
- sed was breaking the symlink on atomic systems
- /boot/grub2/grub.cfg is not the right file on a UEFI system
- etc..
We'll solve this problem a different way by just not installing
plymouth in our systems, which is another way [1] to make sure
rhgb/quiet don't appear on your kernel command line.
[1] ee91db6fa3/pyanaconda/payload/__init__.py (L722-L726)
(cherry picked from commit 68804358d8)
We are seeing an error on aarch64 cloud image creation because
of the vfat filesystem and the fixfiles command failing:
+ /usr/sbin/fixfiles -R -a restore
/sbin/restorecon: Could not set context for /boot/efi/EFI/fedora/fonts/unicode.pf2: Operation not supported
/sbin/restorecon: Could not set context for /boot/efi/EFI/fedora/gcdaa64.efi: Operation not supported
/sbin/restorecon: Could not set context for /boot/efi/EFI/fedora/grub.cfg: Operation not supported
/sbin/restorecon: Could not set context for /boot/efi/EFI/fedora/grubaa64.efi: Operation not supported
/sbin/restorecon: Could not set context for /boot/efi/EFI/fedora/grubenv: Operation not supported
/sbin/restorecon: Could not set context for /boot/efi/EFI/BOOT/BOOTAA64.EFI: Operation not supported
/sbin/restorecon: Could not set context for /boot/efi/EFI/BOOT/fallback.efi: Operation not supported
/sbin/restorecon: Could not set context for /boot/efi/EFI/fedora/BOOT.CSV: Operation not supported
/sbin/restorecon: Could not set context for /boot/efi/EFI/fedora/MokManager.efi: Operation not supported
/sbin/restorecon: Could not set context for /boot/efi/EFI/fedora/shim-fedora.efi: Operation not supported
/sbin/restorecon: Could not set context for /boot/efi/EFI/fedora/shim.efi: Operation not supported
(cherry picked from commit ba950669f1)
Ignore the return code of the systemd-tmpfiles command because
at this point we have already removed the /etc/machine-id (8f3beac)
and all tmpfiles lines with %m in them will fail and cause a bad
return code. Example failure:
[/usr/lib/tmpfiles.d/systemd.conf:26] Failed to replace specifiers: /run/log/journal/%m
(cherry picked from commit a4ae071339)
In 96a6711 we added re-running systemd-tmpfiles to add files to /run
on the root fs of the container. Here we'll limit where systemd-tmpfiles
puts files by passing it --prefix /var and --prefix /var/run/
(cherry picked from commit 93205adc7d)
There is an anaconda bug [1] where passing in metalink urls no longer
works after f25. Use mirrorlist urls to workaround.
[1] https://bugzilla.redhat.com/show_bug.cgi?id=1450129
(cherry picked from commit 77a25abded)
Signed-off-by: Mohan Boddu <mboddu@redhat.com>
similar change was done for docker/cloud in f6ecdc3
cmdline makes it so that %post --erroronfail won't actually stop the
installation in a way that imagefactory will detect the problem and
fail the build. See [1] for more details.
[1] https://github.com/rhinstaller/anaconda/issues/931
(cherry picked from commit 8f142150ba)
Removing python3-mpi4py-openmpi since there is no python3 version of
mpi4py. It should fix the "Non interactive installation failed:
python3-mpi4py-openmpi." issue from the logs.
Signed-off-by: Mohan Boddu <mboddu@redhat.com>
