This release adds the following features: Drop heap as part of a housekeeping action Retry downloads to workaround flaky network connections This release fixes the following bugs: Assume new ME versions are called CSME Fix a buffer-overread when parsing invalid CoSWID entity data Fix a logic thinko when parsing GUID strings Fix downloading files on Windows with libcurl >= 7.77.0 Revert back to a simpler syscall blocklist-based filter This release adds support for the following hardware: Acer U32 dock Luxshare 7-in-1 dock Pixart models 2404, 4206, 2440, 2418, 2752, 2840 and 2818 Current 1.9.18 is somewhat broken, see https://github.com/fwupd/fwupd/issues/7166
I suffer from a different fwupd problem which is also fixed by 1.9.19: "Failed to load daemon: syscall filtering is configured but not working" https://github.com/fwupd/fwupd/issues/7144 (last two comments)
Might as well go to 1.9.20 I guess
Gentle ping...
I would highly recommend you became a proxied maintainer of fwupd, Joakim. Since the retirement of slashbeast both sys-apps/fwupd and several of its core dependencies have only got one maintainer, and they really could use at least one more.
The bug has been closed via the following commit(s): https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=8ac5bf219699feaacb62ad4e48e3ecf0b8781925 commit 8ac5bf219699feaacb62ad4e48e3ecf0b8781925 Author: Marek Szuba <marecki@gentoo.org> AuthorDate: 2024-06-01 00:09:09 +0000 Commit: Marek Szuba <marecki@gentoo.org> CommitDate: 2024-06-01 00:17:22 +0000 sys-apps/fwupd: add 1.9.20, drop 1.9.18 Closes: https://bugs.gentoo.org/931500 Signed-off-by: Marek Szuba <marecki@gentoo.org> sys-apps/fwupd/Manifest | 2 +- sys-apps/fwupd/{fwupd-1.9.18.ebuild => fwupd-1.9.20.ebuild} | 0 2 files changed, 1 insertion(+), 1 deletion(-)
(In reply to Marek Szuba from comment #4) > I would highly recommend you became a proxied maintainer of fwupd, Joakim. > Since the retirement of slashbeast both sys-apps/fwupd and several of its > core dependencies have only got one maintainer, and they really could use at > least one more. How would that work w.r.t adding new versions of fwupd?
(In reply to Joakim Tjernlund from comment #6) > How would that work w.r.t adding new versions of fwupd? Basically you would check if the dependencies need updating, confirm that the new version builds, tests and installs correctly (ideally for several different USE-flag combinations but it may well depend on how big changes have been introduced upstream), and that pkgcheck does not complain about anything major (or preferably does not complain at all). Then let proxy-maint - as well as other maintainers should there be any, I am retiring from Gentoo in 2 weeks and it isn't known at this point if any other dev(s) step in - know that there is a new ebuild to merge into the tree; apparently GitHub PRs are now quite frequently used for this.
