@dftxbs3e added aarch64 and ppc64le to the silverblue composes recently. I see this error for aarch64 from 34695826. See https://pagure.io/dusty/failed-composes/issue/1781
error: Packages not found: hyperv-daemons, mcelog, microcode_ctl, open-vm-tools-desktop, virtualbox-guest-additions, xorg-x11-drv-intel, xorg-x11-drv-openchrome, xorg-x11-drv-vesa, xorg-x11-drv-vmware
@dftxbs3e - can you try to update the list of arch specific packages in the silverblue config. You'll probably need to run your own rpm-ostree compose tree on each platform. Don't worry, it's not too hard.
rpm-ostree compose tree
One other problem I'm seeing is that arch specific packages (for example microcode_ctl) are in the arch specific list but also getting pulled in via comps-sync. I think we need to add anything that is arch specific into the comps-sync-blacklist.yml. i.e. if they are in an arch specific list in fedora-common-ostree.yaml then they also need to be added to the blacklist.
microcode_ctl
fedora-common-ostree.yaml
Fedora Atomic was built for ppc64le, is there a way we can take this information from there?
Oh sorry, I just saw this is for aarch64. Mhm, well I don't have an aarch64 machine.
ppc64le silverblue should fail with the same problem, most of the listed packages are x86 specific
yep a lot of the information was already taken from there to populate the ppc64le list in https://www.pagure.io/workstation-ostree-config/blob/master/f/fedora-common-ostree.yaml#_52. The problem is that silverblue has a larger package set so we need to identify arch specific packages in that larger package set and put them into the arch specific sections of the config.
you can concentrate on ppc64le for now if you like. that should get us most of the way there.
Okay, I understand the issue now. Let's find out how to replicate the environment!
Fixed here: https://pagure.io/workstation-ostree-config/pull-request/151
cool thanks. let's see if it works in the rawhide run tonight
Fixed by https://pagure.io/workstation-ostree-config/pull-request/151
Metadata Update from @dustymabe: - Issue close_status updated to: Fixed - Issue status updated to: Closed (was: Open)
Login to comment on this ticket.