I can't install postgresql-simple on haskell - sql

When I write this command: cabal install postgres-simple or cabal install postgresql-simple
This error appears:
cabal: Error: some packages failed to install: postgresql-libpg-0.9.4.2 failed during the configure step. The exception was: ExitFailure 1
postgresql-simple-0.6.2 depends on postgresql-libpg-0.9.4.2 which failed to install.
I tried on windows and Ubuntu, the same error appears.

As the comment notes, you need to have postgres already installed on your system.

Related

Not able to install Yarn through corepack

Environment: Windows, Node 16.18.0, Corepack 0.14.1
I am following these instructions to install Yarn.
When I run corepack prepare yarn#3.2.4 or corepack prepare yarn#3.2.4 --activate
I get the following error:
Preparing yarn#3.2.4... Internal Error: ENOENT: no such file or directory, stat 'C:\Users\rashiditaba\AppData\Local\node\corepack\yarn\3.2.4' Error: ENOENT: no such file or directory, stat 'C:\Users\***\AppData\Local\node\corepack\yarn\3.2.4'
Hello I experienced the same problem. Corepack is an experimental tool to help with managing versions of your package managers. Due to its experimental status, Corepack currently needs to be explicitly enabled to have any effect.
Disable Corepack with the command:
corepack disable
You will now be able to install yarn via npm:
npm install -g yarn --force
To check the installed version of yarn use:
yarn -v
To upgrade the version use (stable version 3.2.4):
yarn set version stable
Now you can enable corepack again (if it fails keep it disabled):
corepack enable
Try the failed command:
corepack prepare yarn#3.2.4 --activate
I leave you the link with the description of the solution:
https://nodejs.org/dist/latest/docs/api/corepack.html
I hope it helps you
From the error your getting it seems like you have to wrong directory PATH to yarn. Find the directory where yarn is installed and update it's PATH in the environment variables.

Module build failed: Error: `sass-loader` requires `node-sass` >=4. Please install a compatible version

Can you help me? I got this error when I hit ng s
ERROR in ./src/styles.scss (./node_modules/raw-loader!./node_modules/postcss-loader/lib??embedded!./node_modules/sass-loader/lib/loader.js??ref--14-3!./src/styles.scss)
Module build failed: Error: `sass-loader` requires `node-sass` >=4. Please install a compatible version.
at Object.sassLoader (E:\Ibtikar\shop\node_modules\sass-loader\lib\loader.js:31:19)
ERROR in ./src/app/app.component.scss
Module build failed: Error: `sass-loader` requires `node-sass` >=4. Please install a compatible version.
at Object.sassLoader (E:\Ibtikar\shop\node_modules\sass-loader\lib\loader.js:31:19)
ERROR in ./src/app/detail-view/detail-view.component.scss
Module build failed: Error: `sass-loader` requires `node-sass` >=4. Please install a compatible version.
at Object.sassLoader (E:\Ibtikar\shop\node_modules\sass-loader\lib\loader.js:31:19)
ERROR in ./src/app/footer/footer.component.scss
Module build failed: Error: `sass-loader` requires `node-sass` >=4. Please install a compatible version.
at Object.sassLoader (E:\Ibtikar\shop\node_modules\sass-loader\lib\loader.js:31:19)
ERROR in ./src/app/products/products.component.scss
Module build failed: Error: `sass-loader` requires `node-sass` >=4. Please install a compatible version.
at Object.sassLoader (E:\Ibtikar\shop\node_modules\sass-loader\lib\loader.js:31:19)
ERROR in ./src/app/slider/slider.component.scss
Module build failed: Error: `sass-loader` requires `node-sass` >=4. Please install a compatible version.
at Object.sassLoader (E:\Ibtikar\shop\node_modules\sass-loader\lib\loader.js:31:19)
ERROR in ./src/app/header/header.component.scss
Module build failed: Error: `sass-loader` requires `node-sass` >=4. Please install a compatible version.
at Object.sassLoader (E:\Ibtikar\shop\node_modules\sass-loader\lib\loader.js:31:19)
You need to run npm rebuild (or npm rb) in your project folder.
This command runs the npm build command on the matched folders. This is useful when you install a new version of node, and must recompile all your C++ addons with the new binary.
Source
This worked for me
npm install --save-dev node-sass
npm rebuild node-sass --force : should work
npm rebuild --force - this will rebuild all packages. Only this worked for me
Try rebuilding node-sass using npm rebuild node-sass and check if that fixes your issue.
working solution
Step 1 rm -rf node_modules it removes the directory recursively (the existing node modules, takes a min or two)
Step 2 npm install this will work for sure, i did try and it worked.
If you are facing this issue even after upgrading node-saas to version above 4 then follow below thread
Sass-loader requires node-sass >=4 even if that exist
Re-installing webpack solved the issue for me.
npm install --save-dev webpack
or, you can try :
npm rebuild node-sass
check for the supported version. As on date I had node 12.x installed on my machine and spent an hour running npm install node-sass and npm rebuild node-sass with --force and --save-dev hints.
Nothing worked until I uninstalled the node 12.x and installed node 10.x. So if you're hitting the same problem and could not get it to work, try following
Check if your Node version (Run node -v) if it's higher than 10.x
Uninstall the Node 12.x from your machine
Download and Install Node 10.x
Restart the console/editor (not required for all and may work without this step)

How do I install RSelenium on raspberry pi 3 (raspbian)?

I'm trying to install the RSelenium package on my Raspberry Ri Rstudio-server but I get alot of error messages when I try to install the package, some of them are posted below. How do I solve this problem?
/usr/lib/R/etc/Makeconf:141: recipe for target 'RcppExports.o' failed
make: *** [RcppExports.o] Error 1
ERROR: compilation failed for package 'semver'
* removing '/usr/local/lib/R/site-library/semver'
Warning in install.packages :
installation of package 'semver' had non-zero exit status
ERROR: dependency 'semver' is not available for package 'binman'
* removing '/usr/local/lib/R/site-library/binman'
Warning in install.packages :
installation of package 'binman' had non-zero exit status
ERROR: dependencies 'binman', 'subprocess', 'semver' are not available for package 'wdman'
* removing '/usr/local/lib/R/site-library/wdman'
Warning in install.packages :
installation of package 'wdman' had non-zero exit status
ERROR: dependencies 'wdman', 'binman' are not available for package 'RSelenium'
* removing '/usr/local/lib/R/site-library/RSelenium'
Warning in install.packages :
installation of package 'RSelenium' had non-zero exit status
So... i'm getting the same error today. I've formatted my computer and now i can't install RSelenium anymore.
i'm running R version 3.4.2 (2017-09-28) -- "Short Summer"
and i've installed r-base and r-base-dev
Try to run in your terminal the following commands:
sudo apt-get install libxml2-dev
and then install the "binman" package in your R:
install.packages("binman")
then install the dev version of Rselenium from github.
For this, you shoud have installed in your R the devtools package.
after install devtools run:
devtools::install_github("ropensci/RSelenium")
This works for me.

Installing specific node version using NVM gives an error

I want to install node v6.10.3. but when I tried to install it gives the following error. What causes this error?
creating .\config.gypi
creating .\config.mk
bash: make: command not found
nvm: install v6.10.3 failed!
(nvm maintainer here) Could you file this on http://nvm.sh, and fill out the issue template? This kind of question is more appropriate for the repo than for SO.

migrate command not found error even if migrate is installed

I have executed command -
npm install migrate
and it has executed successfully. But when I try to execute the command migrate in terminal it gives me error as migrate command not found
Please find image here.
Has anyone got the same error?
try installing it globally
npm install migrate -g
I have two solutions to this problem.
The first is to attempt to install the package globally.
npm install -g migrate
If above  solution not worked, it could be due to the current user's undefined ExecutionPolicy.
As an administrator, run the following PowerShell command:
Set-ExecutionPolicy RemoteSigned