$ the-wire · showcase
Yanked wnaf crate forces signstar dependency bump
By RepoJournal · Filed · About Arch Linux · Composed from the cited sources · methodology
Signstar's dependency on wnaf moves to 0.14.1 after 0.14.0 was yanked, while package updates land across Arch's extra repo.
The signstar project updated its wnaf crate dependency to 0.14.1 because version 0.14.0 has been yanked [1]. This is a dependency fix, but it affects anyone building signstar from source: Cargo will no longer resolve to the yanked 0.14.0, so the lockfile must be updated before your next build.
On the packaging side, four packages moved in Arch's state repo. fvm updates to 4.3.1-1 in extra-x86_64 [2], and ruby-process-metrics to 0.14.0-1 in extra-any [3]. Also, the testing repo sees sing-geosite-rule-set 20260904020013-1 and v2ray-geoip 202609050329-1 both in extra-testing-any [4][5]. These are routine package bumps, but if you track testing, note the geoip and geosite rule sets are refreshed with newer data.
Action items
- → Update signstar's Cargo.lock to wnaf 0.14.1 before rebuilding archlinux/signstar [immediate]
- → Update fvm to 4.3.1-1 in your extra-x86_64 environment archlinux/state [plan]
- → Monitor testing for the new sing-geosite-rule-set and v2ray-geoip builds archlinux/state [monitor]
References
- [1] fix(deps): Update crate `wnaf` to 0.14.1 because 0.14.0 has been yanked ↗ archlinux/signstar
- [2] update fvm to 4.3.1-1 in extra-x86_64 ↗ archlinux/state
- [3] update ruby-process-metrics to 0.14.0-1 in extra-any ↗ archlinux/state
- [4] update sing-geosite-rule-set to 20260904020013-1 in extra-testing-any ↗ archlinux/state
- [5] update v2ray-geoip to 202609050329-1 in extra-testing-any ↗ archlinux/state
