Package Details: system76-firmware-daemon 1.0.28-1

Git Clone URL: https://aur.archlinux.org/system76-firmware.git (read-only, click to copy)
Package Base: system76-firmware
Description: System76 systemd service that exposes a DBUS API for handling firmware updates
Upstream URL: https://github.com/pop-os/system76-firmware
Licenses: GPL3
Conflicts: system76-firmware-daemon-git
Submitter: yochananmarqos
Maintainer: yochananmarqos
Last Packager: yochananmarqos
Votes: 9
Popularity: 0.024758
First Submitted: 2021-02-05 19:26
Last Updated: 2021-07-14 00:19

Pinned Comments

yochananmarqos commented on 2021-02-16 08:30

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 Next › Last »

yochananmarqos commented on 2021-02-16 08:30

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

@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

@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

@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

@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

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

spastorino commented on 2021-02-04 21:00

@yochananmarqos to be honest I did not investigate too deeply but I've seen people saying that it compiles for them and I can't understand how, unless you're not using rust-toolchain provided Rust version. rust-toolchain on the system76-firmware repo states that the Rust version used is 1.41, so the script on my machines downloads Rust 1.41 and that version fails because 1.41 doesn't support slice patterns. I guess you may be using system rust or something? and that version is newer than 1.41?.

yochananmarqos commented on 2021-02-04 16:33

@spastorino: It builds fine for me with rust in a clean chroot.

spastorino commented on 2021-02-04 14:28

The new 1.0.22 version does not compile. I've explained why here https://github.com/pop-os/system76-firmware/commit/7f66e87e82270ab388db9246195fed7c147d94b2#r46742575

Just pushed a PR mainstream https://github.com/pop-os/system76-firmware/pull/51 to fix this, Jeremy told me that they are going to merge my PR and make a new release soon.

yochananmarqos commented on 2020-12-13 00:08

@dreieck. Please see my comment here.