Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

integration with rpm-ostree/split bootloader rpms #50

Open
cgwalters opened this issue Oct 1, 2020 · 1 comment
Open

integration with rpm-ostree/split bootloader rpms #50

cgwalters opened this issue Oct 1, 2020 · 1 comment
Assignees
@cgwalters
Labels
jira For syncing with Jira

Comments

@cgwalters
Copy link
Member

As noted in the README.md today rpm -q shim-x64 is a lie. Ultimately what we want to do I think is:

  • move the bootloader packages out of the manifest into a separate manifest-bootloader.yaml
  • add a separate rpm-ostree compose tree run to coreos-assembler using that manifest, writing to a separate ref
  • teach cosa's create_disk.sh to use that (we only need that ref if doing a disk image build note!), including passing data from that ref to /usr/libexec/bootupd generate-update-metadata

This would mean that rpm -q shim-x64 would say it's not installed, which is correct - from the perspective of rpm and rpm-ostree. It's not tracked by that system, it's tracked by bootupd. Instead the single source of truth for versioning would then be bootupctl status.
@cgwalters cgwalters mentioned this issue Oct 13, 2020
Open
cgwalters added a commit to cgwalters/fedora-coreos-config that referenced this issue Oct 13, 2020
@cgwalters
manifests/bootloader: Drop armhfp
7027ab0 
We don't produce 32 bit ARM images and are unlikely to anytime
in the near future.  Drop this bit which was cargo culted from
the Atomic Host manifests I believe.

Motivated by looking at bootupd work in: coreos/bootupd#50
@cgwalters cgwalters mentioned this issue Oct 13, 2020
Merged
@cgwalters cgwalters self-assigned this Oct 13, 2020
cgwalters added a commit to coreos/fedora-coreos-config that referenced this issue Oct 14, 2020
@cgwalters
manifests/bootloader: Drop armhfp
32963ad 
We don't produce 32 bit ARM images and are unlikely to anytime
in the near future.  Drop this bit which was cargo culted from
the Atomic Host manifests I believe.

Motivated by looking at bootupd work in: coreos/bootupd#50
@cgwalters cgwalters mentioned this issue Oct 14, 2020
Merged
@travier travier added the jira For syncing with Jira label Oct 21, 2020
kelvinfan001 pushed a commit to kelvinfan001/fedora-coreos-config that referenced this issue Dec 14, 2020
@cgwalters @kelvinfan001
manifests/bootloader: Drop armhfp
3420419 
We don't produce 32 bit ARM images and are unlikely to anytime
in the near future.  Drop this bit which was cargo culted from
the Atomic Host manifests I believe.

Motivated by looking at bootupd work in: coreos/bootupd#50
@cgwalters
Copy link
Member Author

I actually got confused by this today; we should probably at least do rpm -e on the RPM content that we take ownership of in bootupd.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@cgwalters cgwalters

Labels
jira For syncing with Jira
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@cgwalters @travier