* gnu/packages/firmware.scm (make-openbios-package)[native-inputs]: Use
the default gcc and cross-gcc.
Change-Id: I1cff253521add005a8245e96a4bf328bf663c35f
This commit was made by running this command:
sed -e's/modify-inputs (package-\([a-z-]*\)inputs [a-zA-Z0-9-]\+)/modify-inputs \1inputs/g' -i gnu/packages/*.scm
… and then reverting individual hunks where the change would trigger unbound
variable warnings or other issues (such as ‘native-inputs’ is bound in the
body of the ‘inputs’ field, but it refers to the ‘native-inputs’ thunk defined
just above).
Change-Id: I6d94819f2809313fa1fbefc61897502ee7d66fab
This commit was made by running this command:
sed -e's/substitute-keyword-arguments (package-arguments [a-zA-Z0-9-]\+)/substitute-keyword-arguments arguments/g' -i gnu/packages/*.scm
… and then:
1. reverting changes from ‘gnu/packages/rust.scm’ and
‘gnu/packages/java.scm’ since they would incur derivation changes and/or
breakage;
2. reverting the change for ‘gcc-final’ in ‘gnu/packages/commencement.scm’;
3. reverting the change for ‘onnx-optimizer’, ‘openquest’, and ‘certbot’,
which use ‘substitute-keyword-arguments’ for arguments that are not
inherited (and thus ‘arguments’ would be unbound);
4. reverting the change for ‘insight-toolkit-legacy’ and ‘wine64-staging’
which make bogus assumptions about inherited arguments.
Change-Id: I122a7cf517b6b63cae38944b5d33ade4b1f5a89c
QEMU's virt machine on AArch64 requires pflash devices to be exactly
64 MiB. The raw QEMU_EFI.fd produced by EDK2 is only ~2 MiB, causing
GRUB EFI tests to fail with:
cfi.pflash01 device requires 67108864 bytes, pflash0 block backend
provides 2097152 bytes
Pad the firmware file to match, as Nix does.
* gnu/packages/firmware.scm (ovmf-aarch64)[arguments]: Pad
ovmf_aarch64.bin to 64 MiB with truncate-file.
Change-Id: I589325294f264b0af69a9a0261c35d9a862e03c5
Signed-off-by: Efraim Flashner <efraim@flashner.co.il>
Use ‘define-deprecated-package’ instead of (define x (deprecated-package …))
throughout gnu/packages/*.scm.
Change-Id: I4e176da9ac660327489dab256ca4d12c4e78fe8d
* gnu/packages/firmware.scm (format-qemu-firmware-config-options): New helper
procedure.
(seabios-qemu) [#:phases] {build}: Sync configuration options with those
found in QEMU 10.1.0. Simplify the data representation logic a bit, to allow
for more automation in future changes.
Change-Id: Icd94da3824993754d98e8f748dc4e50e22d02c0b
This package provides a file that is vital for the process of firmware
installation and updates on EFI systems using fwupd.
* gnu/packages/firmware.scm (fwupd-efi): New variable.
Change-Id: I3e610f47016af962b9f2675f645534cca076df2e
Signed-off-by: Ludovic Courtès <ludo@gnu.org>
The polkit rules check in fwupdmgr doesn't make sense with Guix packaging, as
it's checking if there is fwupd policy files in the polkit's store path.
This will never be true, and the check will always fail.
One fix would be to skip the check completely. But that seems unnecessary as
the polkit actions are always in /etc/polkit-1/actions on the Guix system.
On foreign distros, it will be necessary to turn the check off manually by
FWUPD_POLKIT_NOCHECK=1. But it's important to note that this was the case even
till now, there is no new breakage. I think it's unlikely someone will be
using fwupd package from Guix on foreign distros anyway.
* gnu/packages/firmware.scm (fwupd)[arguments]{phases}: substitute polkit
actions directory to point to /etc/polkit-1/actions
Change-Id: Ia29d7a32f68a3da7951f45fe823e3ab8059cb670
Signed-off-by: Ludovic Courtès <ludo@gnu.org>
The fwupd package doesn't contain the dbus service in
share/dbus-1/system-service, that is because it is installed only
conditionally when elogind is available.
This will introduce the service in the output, so user's won't have to start
fwupd themselves, it will get started by dbus on demand.
I don't think this should break anything for systems that do not use elogin,
the only places this is used will fall back to error:
- https://github.com/fwupd/fwupd/blob/1.8.14/src/fu-util-common.c#L242,
- https://github.com/fwupd/fwupd/blob/1.8.14/src/fu-util-common.c#L287
Meaning users without elogind will get error either way, just a different kind
of error.
* gnu/packages/firmware.scm: (fwupd)[inputs]: Add elogind
Change-Id: Id44001de6950bb6b39f1b3bba316a08ce6640fc0
Signed-off-by: Ludovic Courtès <ludo@gnu.org>
* gnu/packages/firmware.scm (arm-trusted-firmware-rk3588): New variable.
* gnu/packages/bootloaders.scm (make-u-boot-rockchip-package): Support
'rk3588.
