Separate builds on network-level #113
Labels
No Label
blocked upstream
bug
build-failure
duplicate
enhancement
help wanted
informational
invalid
invalid/corrupt package
packaging issue
priority: high
question
support
wontfix
No Milestone
No project
No Assignees
2 Participants
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: ALHP/ALHP.GO#113
Loading…
Reference in New Issue
No description provided.
Delete Branch "%!s(<nil>)"
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?
Well, I think there's a conflict between building some packages at the same time - maybe even Firefox twice - as the build process wants to start a server on an IP/Port which is already in use and fails:
Yep, this is a know issue. I already experimented with separating the builds on a network level via systemd-nspawn. There is only firewall integration left, otherwise this already worked in my tests. But this change probably should go upstream in devtools - there is already an open issue for that: https://gitlab.archlinux.org/archlinux/devtools/-/issues/72
Firefox (x86_64v2) build failedto Separate builds on network-levelAh cool 😎
Thanks for the fast update!
Quick update here: Since
ece8c4c7d9
we do not build the same packages concurrently. That does not solve this issue completely, there can still be a overlap of used ports between different package builds, but it lowered the chance of occurring significantly.