Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Fix pacman install within a parallel bundler install -jX #403

Merged
merged 1 commit into from
Dec 30, 2024

Conversation

larskanis
Copy link
Member

pacman invocation must be serialized to avoid locking error.

Add a second gem using libidn2, so that two different libraries are requested and the test case fails if anyone isn't available after parallel pacman execution.

The test case requires bundler-2.6.x to trigger the failure due to rubygems/rubygems#8248 .

Fixes #397

pacman invocation must be serialized to avoid locking error.

Add a second gem using libidn2, so that two different libraries are requested and the test case fails if anyone isn't available after parallel pacman execution.

The test case requires bundler-2.6.x to trigger the failure due to rubygems/rubygems#8248 .

Fixes #397
@larskanis larskanis merged commit 80fd075 into master Dec 30, 2024
15 of 20 checks passed
@larskanis larskanis deleted the pacman-lock branch December 30, 2024 13:27
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

parallel gem installation with bundler can result in a pacman locking error
1 participant