not working for a Mac M3 pro
Nobody has claimed this yet.
Assessment
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Newbie friendliness
- 30/100
- Issue type
- Bug
- Clarity
- Needs clarification
- Activity status
- Stale
- Tech stack
- ruby
- Domain
- build-system
Research direction
Start with the repository's Gemfile and reproduce bundle install on a Mac M3 Pro running Sequoia 15.3.1, focusing on the asciidoctor-epub3 → gepub → nokogiri dependency chain. Done means bundle install completes successfully for the source files.
Written by the indexing model from the issue text.
Description
There's no existing/similar bug report.
- I have searched the existing issues
This report is about a single actionable bug.
- I'm reporting a single actionable bug
This report is about the ProGit book, version 2, English language.
- This bug is not about a translation or old version
Bug covers book website/pdf
- I confirm the bug is about the book as found on the website/pdf
Problem is present in the Pro Git book on the website?
- This bug also affects the Pro Git book as published on the website.
Which version of the book is affected?
Source files
Describe the bug:
nokogiri seems to not work with M3 getting this error below : An error occurred while installing nokogiri (1.13.10), and Bundler cannot continue.
In Gemfile:
asciidoctor-epub3 was resolved to 2.1.3, which depends on
gepub was resolved to 1.0.15, which depends on
nokogiri
Steps to reproduce:
- Go to '...'
- Click on '...'
- 'Scroll down to '...'
- See error
Expected behavior:
not able to execute the bundle install
Screenshots:
No response
Additional context:
No response
Device
mackbook Appel M3 pro
Operating system
Sequoia 15.3.1
Browser/application + version
No response
- Dominant language
- CSS
- Stars
- 6.6k
- Forks
- 2.1k
- PR merge metrics
- No merged PRs in 30d
Getting set up
- No Dockerfile or Docker Compose file
- Has a pull request template
- Read the contributing guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from progit/progit2
-
Difficulty 1/5 Under an hour Newbie friendliness 87/100
-
enhancement
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
-
enhancement
Difficulty 1/5 Under an hour Newbie friendliness 82/100
Similar issues
-
Pin Python to 3.14 in the era5grib-parallel environment specificationPossibly taken @atteggiani claimed this today. Open
Difficulty 1/5 Under an hour Newbie friendliness 85/100
ACCESS-NRI/containerised-environments-infra#129 ·
Maintainers usually reply within 2 days
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 79/100
Feyisara2108/stellargive#1374 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
stac-utils/pystac#1857 ·
Maintainers usually reply within 1 day