hyprwm
hyprpm update - won't update
after the new hyprland update, i've been unable to run hyprbars ever since, wondering if this is a me issue or something wrong with the system. i've tried building hyprland from source, but it keeps going to a recursive dependency loop issue. i can't get out of it.
hyprctl version Hyprland 0.47.2 built from branch at commit 882f7ad7d2bbfc7440d0ccaef93b1cdd78e8e3ff (version: bump to 0.47.2). Date: Sun Feb 2 00:47:17 2025 Tag: v0.47.2, commits: 5767 built against: aquamarine 0.7.2 hyprlang 0.6.0 hyprutils 0.5.0 hyprcursor 0.1.11 hyprgraphics 0.1.1 no flags were set
hyprpm update ✔ Headers up to date. → checking for updates for hyprland-plugins
→ Cloning https://github.com/hyprwm/hyprland-plugins
✔ repository hyprland-plugins has updates.
→ Building hyprland-plugins
✔ found hyprpm manifest
→ Manifest has 28 pins, checking
✔ commit pin 3e51162d83b0cd9ee35acbd3b91e6d7ba856f5eb matched hl, resetting
→ Building borders-plus-plus
━━━━━━━━━━━━━━━━╍━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ 2 / 6 Updating hyprland-plugins
✖ Plugin borders-plus-plus failed to build. This likely means that the plugin is either outdated, not yet available for your version, or broken. If you are on -git, update first. Try re-running with -v to see more verbose output. → Building csgo-vulkan-fix
━━━━━━━━━━━━━━━━╍━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ 2 / 6 Updating hyprland-plugins
✖ Plugin csgo-vulkan-fix failed to build. This likely means that the plugin is either outdated, not yet available for your version, or broken. If you are on -git, update first. Try re-running with -v to see more verbose output. → Building hyprbars
━━━━━━━━━━━━━━━━╍━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ 2 / 6 Updating hyprland-plugins
✖ Plugin hyprbars failed to build. This likely means that the plugin is either outdated, not yet available for your version, or broken. If you are on -git, update first. Try re-running with -v to see more verbose output. → Building hyprexpo
━━━━━━━━━━━━━━━━╍━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ 2 / 6 Updating hyprland-plugins
✖ Plugin hyprexpo failed to build. This likely means that the plugin is either outdated, not yet available for your version, or broken. If you are on -git, update first. Try re-running with -v to see more verbose output. → Building hyprtrails
━━━━━━━━━━━━━━━━╍━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ 2 / 6 Updating hyprland-plugins
✖ Plugin hyprtrails failed to build. This likely means that the plugin is either outdated, not yet available for your version, or broken. If you are on -git, update first. Try re-running with -v to see more verbose output. → Building hyprwinwrap
━━━━━━━━━━━━━━━━╍━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ 2 / 6 Updating hyprland-plugins
✖ Plugin hyprwinwrap failed to build. This likely means that the plugin is either outdated, not yet available for your version, or broken. If you are on -git, update first. Try re-running with -v to see more verbose output. → Building xtra-dispatchers
━━━━━━━━━━━━━━━━╍━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ 2 / 6 Updating hyprland-plugins
✖ Plugin xtra-dispatchers failed to build. This likely means that the plugin is either outdated, not yet available for your version, or broken. If you are on -git, update first. Try re-running with -v to see more verbose output. ✔ updated hyprland-plugins
→ checking for updates for hy3
→ Cloning https://github.com/outfoxxed/hy3
✔ repository hy3 is up-to-date.
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ 6 / 6 Done!
✔ Ensuring plugin load state ✔ Plugin load state ensured
uname -a Linux archlinux 6.13.2-zen1-1-zen #1 ZEN SMP PREEMPT_DYNAMIC Sat, 08 Feb 2025 18:54:38 +0000 x86_64 GNU/Linux
I thing it is broken because the time.hpp and other headers are missing on v0.48.1 of hyprland. I managed to have the plugins back (just using hyprexpo really) removing this repository, and readding it sticked to v0.48.0 tag (I guess since you have v0.47.2 you should stick to v0.47.0)
hyprpm remove https://github.com/hyprwm/hyprland-plugins
hyprpm add https://github.com/hyprwm/hyprland-plugins v0.48.0
It's quite a bummer to stick it to a version, and my uneducated guess is that usually hyprpm tries to find the same tag as the hyprland version in the plugin repository, defaulting to the main branch - so, since v0.48.1 tag isn't present in this repository, it would use code that isn't compatible to v0.48.1, but it is compatible with the main hyprland branch. Or maybe it always uses the main branch.
time.hpp is for git. What do you mean v0.48.1 is not present? The pin is there?
time.hpp is for git.
Exactly: hyprpm is cloning the git repo and building the plugins, and it doesn't find some header files (time.hpp and another one that I don't remember)
What do you mean v0.48.1 is not present? The pin is there?
In this repo there isn't the v0.48.1 tag, but only v0.48.0.
Edit: I just explored a little bit more and found the commit pins for the versions. I'd investigate the pinned version for v0.48.1 then, because it was searching for that header file...
check with https://github.com/hyprwm/hyprland-plugins/commit/bd929f71ef74d3e2569091ec307ad699399a8b3a