Package Base Details: system76-firmware

Git Clone URL: (read-only, click to copy)
Submitter: yochananmarqos
Maintainer: yochananmarqos
Last Packager: yochananmarqos
Votes: 8
Popularity: 0.000000
First Submitted: 2021-02-05 19:26 (UTC)
Last Updated: 2023-03-23 16:15 (UTC)

Pinned Comments

yochananmarqos commented on 2021-02-16 08:30 (UTC)

PSA: The CLI and daemon are now split into separate packages to match upstream. You'll have to uninstall system76-firmware-daemon <=1.0.23-1 to upgrade to >=1.0.23-2.

Latest Comments

1 2 3 4 Next › Last »

nox404 commented on 2023-02-18 10:21 (UTC) (edited on 2023-02-18 10:26 (UTC) by nox404)

I got the following error while upgrading:

==> Making package: system76-firmware 1.0.50+4+gd24f401-1 (Sat Feb 18 11:11:41 2023)
==> Checking runtime dependencies...
==> Checking buildtime dependencies...
==> Retrieving sources...
  -> Updating system76-firmware git repo...
==> Validating source files with sha256sums...
    system76-firmware ... Skipped
==> Removing existing $srcdir/ directory...
==> Extracting sources...
  -> Creating working copy of system76-firmware git repo...
Cloning into 'system76-firmware'...
Switched to a new branch 'makepkg'
==> Starting prepare()...
    Updating index
error: failed to select a version for the requirement `security-framework = "^2.0.0"`
candidate versions found which didn't match: 2.8.1, 2.8.0, 2.7.0, ...
location searched: index
required by package `native-tls v0.2.11`
    ... which satisfies dependency `native-tls-crate = "^0.2.10"` (locked to 0.2.11) of package `reqwest v0.11.14`
    ... which satisfies dependency `reqwest = "^0.11.11"` (locked to 0.11.14) of package `buildchain v0.4.12`
    ... which satisfies dependency `buildchain = "^0.4"` (locked to 0.4.12) of package `system76-firmware v1.0.50 (/tmp/makepkg/system76-firmware/src/system76-firmware)`
    ... which satisfies path dependency `system76-firmware` (locked to 1.0.50) of package `system76-firmware-daemon v0.1.0 (/tmp/makepkg/system76-firmware/src/system76-firmware/daemon)`
==> ERROR: A failure occurred in prepare().
 -> error making: system76-firmware (system76-firmware system76-firmware-daemon)

Solved it by removing rustup and switching to rust.

zoltanszabo commented on 2022-08-02 20:40 (UTC)

@yochananmarqos: Thank you for the prompt response and the hint; this solves my question.

yochananmarqos commented on 2022-08-02 18:07 (UTC)

@zoltanszabo: You need to add the key to your public keyring.


zoltanszabo commented on 2022-08-02 17:47 (UTC)

Thank you for this nice package. The installation (makepkg -sic) seems to result in a PGP issue:

==> Verifying source file signatures with gpg...
    system76-firmware git repo ... FAILED (unknown public key 87F211AF2BE4C2FE)
==> ERROR: One or more PGP signatures could not be verified!

Could you please check/adjust/(help to) resolve it? Note: I have the latest archlinux-keyring installed.

yochananmarqos commented on 2021-02-16 08:30 (UTC)

PSA: The CLI and daemon are now split into separate packages to match upstream. You'll have to uninstall system76-firmware-daemon <=1.0.23-1 to upgrade to >=1.0.23-2.

yochananmarqos commented on 2021-02-05 21:58 (UTC)

@spastorino: Again, that's the point of building in a chroot. You can keep your rustup and build in a chroot using rust.

spastorino commented on 2021-02-05 21:17 (UTC)

@yochananmarqos ahhh I see, it depends on rust but:

rust (rust-i586-git, rust-git, rust-mrustc, rust-bin, rustup-git, rust-nightly, rust-nightly-bin, rust-wasm, rustup)

On my machine:

$ pacman -Q | grep rust rustup 1.23.1-1 $

And as listed, rustup provides rust. So when I run makepkg, it downloads whatever version rustup-toolchain file says and that's why it doesn't work on my machine. So whoever has the same setup I have which is to have rustup to manage all the rust installations, would have the same issue. Anyway, I saw Jeremy released and you updated the package so everyone happy :).

yochananmarqos commented on 2021-02-04 23:58 (UTC)

@spastorino: Yes, I did read it. However, it seems to be irrelevant to this package since it depends on rust which is currently at 1.49.0.

spastorino commented on 2021-02-04 23:42 (UTC)

@yochananmarqos yeah I understand that, did you read my comments on the github commit I've shared?. What I don't understand is how this 1.0.22 version even works. 1.0.22 is using a version of the object crate that uses slice patterns, which was introduced in Rust 1.42 and the repo states in rust-toolchain that the Rust version used is 1.41. All I can think is that rust-toolchain on certain setups is ignored or something like that.

yochananmarqos commented on 2021-02-04 21:36 (UTC)

@spastorino: Building in a clean chroot helps ensure a reproducible build without interference from environment / user variables.