Mario Limonciello
Mario Limonciello
What does `fwupdmgr get-history` show? I'm a bit confused by this result you've shared so far.
> I have also encountered a problem with the update not being applied on reboot on a Dell system, in this case an XPS 15 7590. > > ``` >...
So one thing unexpected to me is that a distro signed systemd bootloader would not be in a distro specific directory. That is if you had a dual boot system...
> No, it should not, this is working as intended: sd-boot is a single-manager for the whole system by design Ah, I see. Thanks for clarifying. > The correct setup...
> With multiple distros theres then the question of who should manage the systemd directory. This is a concern I have as well. If you install Debian and it puts...
> Ok, I've prepared a manifest. Can submit it after the next release: https://github.com/FrameworkComputer/winget-pkgs/tree/fwupd Who/how does it get signed? I think that part needs to be solved first doesn't it?
Do you have an EV cert? I think we need that as a CI secret.
I would be really surprised if Winget worked with unsigned content. But as for publishing to the release, it's [supposed to be happening automagically](https://github.com/fwupd/fwupd/blob/main/.github/workflows/matrix.yml#L180). We've had some problems ever since...
Fresh eyes let me fix the documentation publishing. Just re-ran that and it's working. Hopefully https://github.com/fwupd/fwupd/pull/9107 will fix the windows publishing on the next tagged release.
Yeah; I believe someone will need to pay for a cert to be able to sign and have it trusted by Windows.