dustymabe commented on the pull-request: `Add packages needed to support aarch64 single
board computers` that you are following:
Why would two packages with no dependencies on a single arch affect
the rest of the release?
Unfortunately I am not familiar with those two packages (obviously I've heard of
u-boot before, but not familiar with the specific details of those packages). I just feel
it would be safer if we waited to merge this until after we did this week's release,
which is currently waiting on the next updates run to happen so we can include a security
update. Obviously this change only affects aarch64, but we happen to release aarch64 now
so if it were to come up DOA then we'd have to revert this change and also wait for
the next updates run to happen.
I would like to get them in so I can continue to test.
I understand that. Here are some options:
- We did merge the [rawhide PR](https://pagure.io/fedora-atomic/pull-request/105), so the
the next iteration of that should have the changes.
- We could open a new PR to just update the [manifest for
until the release is out.
- You can use the `fedora/27/aarch64/atomic-host` ref in [this
I just created using [this
your patch applied to it. You can use an `ostreesetup` line in your kickstart like:
ostreesetup --osname=fedora-atomic --remote=fedora-atomic
Hopefully one of those will do.
Else I can just fork the whole lot and go off and do my own stuff
I really don't feel like that was an appropriate response.
To reply, visit the link below or just reply to this email