[GH-ISSUE #569] Cargo error when insalling Ironbar from the AUR #8615

New issue

Closed

opened 2026-05-23 03:53:05 +01:00 by JakeStanger · 1 comment

JakeStanger commented

2026-05-23 03:53:05 +01:00

Owner

Originally created by @ForgotMyPasswd on GitHub (May 4, 2024).
Original GitHub issue: https://github.com/JakeStanger/ironbar/issues/569

Describe the bug
When I try to install ironbar-git from the AUR, iI get this error when building the package:
error: the lock file /home/fahmed/.cache/yay/ironbar-git/src/ironbar/Cargo.lock needs to be updated but --locked was passed to prevent this

To Reproduce
Steps to reproduce the behavior:

Install ironbar-git from AUR
Once dependencies are set up and the buid process starts, the error should appear

Expected behavior
Ironbar to compile properly and to prompt me to install it

System information:

Distro: Arch Linux
Compositor: Hyprland
Ironbar version: 0.15.

Originally created by @ForgotMyPasswd on GitHub (May 4, 2024). Original GitHub issue: https://github.com/JakeStanger/ironbar/issues/569 **Describe the bug** When I try to install ironbar-git from the AUR, iI get this error when building the package: `error: the lock file /home/fahmed/.cache/yay/ironbar-git/src/ironbar/Cargo.lock needs to be updated but --locked was passed to prevent this` **To Reproduce** Steps to reproduce the behavior: 1. Install ironbar-git from AUR 4. Once dependencies are set up and the buid process starts, the error should appear **Expected behavior** Ironbar to compile properly and to prompt me to install it **System information:** - Distro: Arch Linux - Compositor: Hyprland - Ironbar version: 0.15.

JakeStanger

2026-05-23 03:53:05 +01:00

closed this issue
added the
T:Bug
label

JakeStanger commented

2026-05-23 03:53:06 +01:00

Author

Owner

@JakeStanger commented on GitHub (May 4, 2024):

Sounds like an issue brought about by a dep update yesterday. Cloning and building locally should update the lockfile to check in - I should be able to do this tonight if nobody beats me to it :)

@JakeStanger commented on GitHub (May 4, 2024): Sounds like an issue brought about by a dep update yesterday. Cloning and building locally should update the lockfile to check in - I should be able to do this tonight if nobody beats me to it :)