Can't set up a dev environment due to libvips.so.42 not being found. #9492
Comments
|
Hi.. first thing to try is installing libvips and libvips-dev. Something like |
|
Hrrm, now I see you're already installing libvips-dev. I think vips.42 is part of libvips. It might be the case that you need to (re)compile ruby after you have libvips and libvips-dev installed. |
|
The DEVSETUP document has not been updated in a while, but we can fix it once we solve this issue. A good cheatsheet is the Dockerfile which has clear instructions on what libraries are needed to setup Loomio for production. |
I might be wrong as to what recompiling entails, but I just threw away I tried installing what I could from the Dockerfile: I omitted Looking at those warnings once again, it seems that built-in |
|
You don't need to worry about warnings, just errors. It's the missing libvips42 error eh? That library should be installed with libvips-dev. Can you repost the latest statement of error? |
@robguthrie I sincerely apologise - the vips error has been dealt with after installing
I believe I was too worried about the various warnings still persisting after dealing with the
What follows are stack traces and steps that I've done to arrive at this solution and are not a necessary read for anything, I think. This is my current stack trace when running Since it complains about the database not existing, I decided to try I tried creating the database manually and running I can start the app and don't see any errors at the moment or have any issues. |
|
Oh, great that you have it working! Yes, createdb can help so rails can setup the schema. It depends on the OS and postgres settings.. some platforms you can I've updated the DEVSETUP file a little. |
|
Aight, did another test run from scratch on a Xubuntu 20.04 VM this time and Interestingly or maybe not,
|
|
Ok nice. So you can start the server now? Can you also start the frontend ( One thing to note is that I changed the nvm commands to install node 14, rather than "stable", because we're stuck on 14 specifically for now. |
Yup, everything worked without any issues - I set up the app on a fresh Xubuntu 20.04 VM. The only thing that I could see is warnings but I assume they're expected. At least in this run from scratch So in the end, I'm able to run the app on Ubuntu 22.04 WSL, bare metal install of Xubuntu 22.04 and Xubuntu 22.04/20.04 VMs. |
|
Oh that's great. Is there anything you want to do with Loomio next? |
|
Wanted to see if I have any chance at #8148. Haven't dug into it at all yet since I figured I need to have a development setup done first to check how tagging works in the application in the first place before diving into code. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Summary
On Ubuntu 22.04 WSL, Xubuntu 22.04 VM & bare metal install, the
rake db:setupcommand fails with:due to this, I can't set up a development environment using the Setup a Loomio developer environment document.
Information about setups
All the setups already had rbenv (and Ruby 3.1.2), nvm (and some version of Node), postgres installed, configured and used for other projects. There were no issues with installing packages besides the
pythonone:which I chose to ignore until something Python-related came up as IIRC Ubuntu itself depends on Python so it has to have some kind of Python installed anyway.
I had to make a fresh install of Ruby
2.7.6on all of the setups because I did not have it.bundle installandnpm installworked without any issues besidesnpmoutputting warnings there and there about deprecated stuff and such. Nothing critical that'd stop it from finishing.Full stack trace
All the stack traces are the same on all of the setups, I'm going to show the one from a bare metal Xubuntu install here:
Alternatively, WSL stack trace, Xubuntu VM stack trace.
Steps to reproduce
rake db:setup.Expected behaviour
Additional information
If I run
bundle exec rails --trace s, I get a very similar trace:My attempts at troubleshooting
I googled:
to possibly deal with this on my own and found somewhat-maybe related issues libvips/ruby-vips#219 rails/rails#43976 and decided to run
sudo apt install libvips-devon my bare metal Xubuntu 22.04 install.This has changed the stack trace:
I'm not good with postgreSQL or SQL at all but tried creating the database manually, then running
rake db:seedand thenrake db:migratebut it didn't look promising - the error still persists. Can start the app though, many errors and I guess functionality is broken but it starts.The text was updated successfully, but these errors were encountered: