Created attachment 1229956 [details]
Description of problem:
fc25 ppc64 iso kickstart firewall test reports missing libcript.so
Version-Release number of selected component (if applicable):
fc25 ppc64 iso from
Steps to Reproduce:
if you have an openQA instance for fedora PowerPC then simply execute command:
/var/lib/openqa/script/client jobs post ISO=Fedora-Server-dvd-ppc64-25.iso DISTRI=fedora VERSION=25 FLAVOR=Server-dvd-iso ARCH=ppc64 BACKEND=qemu BUILD=Server-25-GA GRUB="inst.ks=http://fedorapeople.org/groups/qa/kickstarts/firewall-configured-net.ks" KICKSTART=1 MACHINE=ppc64 OFW=1 POSTINSTALL=firewall_configured QEMU=ppc64 QEMUCPU=host QEMURAM=4096 ROOT_PASSWORD=anaconda TEST=install_kickstart_firewall_configured USER_LOGIN=false VGA=std WORKER_CLASS=qemu_ppc64
Actual results: popup error message about missing packages as per
nothing provides libcrypt.so.1()(64bit)
nothing provides glibc-common = 2.24-3.fc25
* There is no such problem for same test executed for ppc64le.
Created attachment 1229960 [details]
On the http://dl.fedoraproject.org/pub/fedora-secondary/releases/25/Everything/ppc64/os/Packages/l/ page (and associated mirrors), libcrypt is only provided for ppc64p7:
For Server packages (i.e http://dl.fedoraproject.org/pub/fedora-secondary/releases/25/Server/ppc64/os/Packages/l/ and mirrors) both versions are provided (ppc64 and ppc64p7):
The error is probably due to the missing libcrypt-2.24-3.fc25.ppc64.rpm package in case of the "Everything" flavour.
oh my, the subarch issue with the compose tools again :-(
(In reply to Dan Horák from comment #3)
> oh my, the subarch issue with the compose tools again :-(
So it's too late to fix this for F-25 now, should have tested it properly, and we've killed ppc64p7 in F-26 due to these issues, so I'm not sure how best to deal with it. Updated glibc into updates will fix the issue for F-25 but not for install media. F-26 there won't be a problem. That's likely about the best we can fix it.
Assuming this bug is limited to ppc64 f25 install media that will not be fixed as per above comment #4
I have created a new bug https://bugzilla.redhat.com/show_bug.cgi?id=1429575
to track the upgrade that is failing now with last f25 updates.
Closing this can't fix, F-25 is long out, won't be an issue with F-26