-
Notifications
You must be signed in to change notification settings - Fork 183
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
Install: rake setup fails with "cannot load such file -- ruby_http_parser" #1405
Comments
Hm, I can't reproduce this, and it shouldn't be different from upstream. Did you run |
bundle install ran fine with no errors (and yarn install, after I found out that /usr/bin/yarn in Debian (& therefore Raspbian) is a different tool altogether). The error on It might be something related to arm7; something related to Debian 10, or to the Raspbian flavour of it. I can test on an amd64 vanilla Debian 10 later. (curiously, bundle install failed on vanilla masto – it was trying to install bcrypt 3.1.13, which fails on arm7. per a hard-to-find bug report, I changed Gemfile.lock to 3.1.12 and it worked. glitch-soc evades this cause it's on 3.1.15.) |
Oh, I hadn't noticed bcrypt had been updated. 3.1.13 had a build issue on non-x86 for a long time, this is great! I can't really see what may be causing the issue, though. It would be interesting if you tried vanilla Mastodon's latest development version on the same hardware. In either case, it seems |
Confirmed that it doesn’t reproduce on latest mastodon commit (0f38f97 from Aug 13). …And I tried it again on a fresh glitch-soc checkout and couldn’t reproduce it myself. I guess I must have borked the 1st attempt somehow? In any case I think it’s safe to close this, especially if |
Following the mastodon install docs until I reach this point:
RAILS_ENV=production bundle exec rake mastodon:setup
This fails for me with:
Same steps on vanilla masto (v3.2.0) work.
OS is Raspbian 10 (Buster).
The text was updated successfully, but these errors were encountered: