mirror of
https://github.com/JakeStanger/ironbar.git
synced 2026-07-11 06:15:21 +01:00
[GH-ISSUE #1148] Binary CI job failing #1760
Labels
No labels
A:Build
A:CI
A:Client
A:Config
A:Core
A:Documentation
A:Documentation
A:IPC
A:Testing
A:UX/UI
blocked
BREAKING CHANGE
duplicate
good first issue
GTK4
help wanted
invalid
M:Battery
M:Battery
M:Bindmode
M:Bluetooth
M:Brightness
M:Cairo
M:Clipboard
M:Clock
M:Clock
M:Custom
M:Focused
M:Keyboard
M:Launcher
M:Menu
M:Music
M:Music
M:Music
M:Network Manager
M:Notifications
M:SysInfo
M:Tray
M:Volume
M:Workspaces
partially resolved
P:Critical
P:High
P:Low
P:Medium
pull-request
T:Bug
T:Bug
T:Core Enhancement
T:Module Enhancement
T:New Module
T:Question
wontfix
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
JakeStanger/ironbar#1760
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @JakeStanger on GitHub (Sep 7, 2025).
Original GitHub issue: https://github.com/JakeStanger/ironbar/issues/1148
Describe the bug
The binary CI job is failing when attempting to link to the
colpettocrate. This occurs indifr the GH Actions Runner at least, when compiling under Cross on both x86_64 and ARM64.https://github.com/JakeStanger/ironbar/actions/runs/17534068248/job/49794809579
It's currently unknown whether the build succeeds when run outside of CI; further investigation is needed.
Tagging @morr0ne for visibility.
@JakeStanger commented on GitHub (Sep 8, 2025):
Testing shows this is due to Cross using Ubuntu 20.02 images, which ships neolithic package versions. Trying to use a custom image and get cross-compilation working, and trying to build a newer libinput version are both painful, so waiting for this:
https://github.com/cross-rs/cross/pull/1580
@puppymati commented on GitHub (Sep 9, 2025):
To add some context: this issue is pretty much not ironbar fault but cross shipping a nearly 6 years old version of libinput. Colpetto's libinput support was originally based on Debian 12, which was the stable release at that time.
@slowsage commented on GitHub (Sep 16, 2025):
I think cross is more pain than what it is worth. I vote for ditching cross and only outputting x86_64 binary for now.
This and this are probably relevant for a new approach with the latest packages on arm.
@puppymati commented on GitHub (Sep 16, 2025):
If there's arm images available. Can't we just ditch cross in favor of having a build action happen on the arm images?
@JakeStanger commented on GitHub (Sep 16, 2025):
Oh neat, I didn't know about those. Sounds easy enough to test...
@JakeStanger commented on GitHub (Sep 16, 2025):
Well that worked for x64 at least. The ARM runner seems to be a single RPi running on somebody's desk, judging by the queue times, so we'll see about that later I guess
@slowsage commented on GitHub (Sep 17, 2025):
Relevant: https://github.com/orgs/community/discussions/148648#discussioncomment-11858287. Try ubuntu-24.04-arm.
FWIW: I was working on a way to cross compile without cross - may be a backup if native arm64 image does not work.
@JakeStanger commented on GitHub (Sep 17, 2025):
You'd think that if you provided an invalid runner name, it'd do something intelligent like tell you that, and not sit there indefinitely.
I've updated the Docker image to support ARM64, and updated the binary job to run on both platforms, and that's got it. Binaries are now available on the latest release for both platforms.
I'll work to clear up Cross now that it's no longer required.
Cheers both