Every time I install a new package, I see this error message:
---> Found 1 broken file(s), matching files to ports
Warning: No port py24-scipy found in the index; can't rebuild
---> Broken files found, but all associated ports are not in the index and so cannot be rebuilt.
It got into this state after I did a "port upgrade outdated".
I'm pretty sure I'm not using py24-scipy (I use py27), so I'd simply like to find the file which is triggering the warning and remove it.
I tried running "port install XXX -d", to see if it would show me where the broken file is, but it didn't.
Based on comment from #Vortexfive (thanks), this solved the problem:
SCML-JRichardson:pdf2html5 jric$ port installed py24-scipy
The following ports are currently installed:
py24-scipy #0.11.0_0+gcc45 (active)
That's weird:
SCML-JRichardson:pdf2html5 jric$ port installed all | grep scipy
py-scipy #0.11.0_0
py-scipy #0.13.2_0 (active)
py27-scipy #0.11.0_0+gcc45
py27-scipy #0.13.2_0+gcc45 (active)
But anyway,
Password:
---> Unable to uninstall py24-scipy #0.11.0_0+gcc45, the following ports depend on it:
---> py-scipy #0.11.0_0
Error: org.macports.uninstall for port py24-scipy returned: Please uninstall the ports that depend on py24-scipy first.
Please see the log file for port py24-scipy for details:
/opt/local/var/macports/logs/_opt_local_var_macports_registry_portfiles_py24- scipy_0.11.0_0+gcc45/py24-scipy/main.log
Warning: Failed to execute portfile from registry for py24-scipy #0.11.0_0+gcc45
---> Unable to uninstall py24-scipy #0.11.0_0+gcc45, the following ports depend on it:
---> py-scipy #0.11.0_0
Error: port uninstall failed: Please uninstall the ports that depend on py24-scipy first.
Try Deactivate py-scipy so it does not block py24-scip removal
SCML-JRichardson:pdf2html5 jric$ sudo port deactivate py-scipy
---> Deactivating py-scipy #0.13.2_0
---> Cleaning py-scipy
uninstall py24-scipy - bt does not work as py-scipy is still there
SCML-JRichardson:pdf2html5 jric$ sudo port uninstall py24-scipy
---> Unable to uninstall py24-scipy #0.11.0_0+gcc45, the following ports depend on it:
---> py-scipy #0.11.0_0
Error: org.macports.uninstall for port py24-scipy returned: Please uninstall the ports that depend on py24-scipy first.
Please see the log file for port py24-scipy for details:
/opt/local/var/macports/logs/_opt_local_var_macports_registry_portfiles_py24-scipy_0.11.0_0+gcc45/py24-scipy/main.log
Warning: Failed to execute portfile from registry for py24-scipy #0.11.0_0+gcc45
---> Unable to uninstall py24-scipy #0.11.0_0+gcc45, the following ports depend on it:
---> py-scipy #0.11.0_0
Error: port uninstall failed: Please uninstall the ports that depend on py24-scipy first.
Now try removing both py24-scipy py-scipy#0.11.0_0
SCML-JRichardson:pdf2html5 jric$ sudo port uninstall py24-scipy py-scipy#0.11.0_0
---> Uninstalling py-scipy #0.11.0_0
---> Cleaning py-scipy
---> Deactivating py24-scipy #0.11.0_0+gcc45
---> Cleaning py24-scipy
---> Uninstalling py24-scipy #0.11.0_0+gcc45
---> Cleaning py24-scipy
SCML-JRichardson:pdf2html5 jric$ sudo port activate py-scipy
---> Computing dependencies for py-scipy
---> Activating py-scipy #0.13.2_0
---> Cleaning py-scipy
Related
I'm trying to install dependencies in my project but when I run yarn install I get the following error
[2/5] 🔍 Resolving packages...
info There appears to be trouble with the npm registry (returned undefined). Retrying...
info There appears to be trouble with the npm registry (returned undefined). Retrying...
info There appears to be trouble with the npm registry (returned undefined). Retrying...
info There appears to be trouble with the npm registry (returned undefined). Retrying...
⠁ axios#0.21.1/usr/local/Cellar/yarn/1.22.10/libexec/lib/cli.js:66965
throw new (_errors || _load_errors()).ResponseError(_this3.reporter.lang('requestFailed', description), res.statusCode);
^
ResponseError: Request failed "502 Bad Gateway"
at ResponseError.ExtendableBuiltin (/usr/local/Cellar/yarn/1.22.10/libexec/lib/cli.js:696:66)
at new ResponseError (/usr/local/Cellar/yarn/1.22.10/libexec/lib/cli.js:802:124)
at Request.params.callback [as _callback] (/usr/local/Cellar/yarn/1.22.10/libexec/lib/cli.js:66965:19)
at Request.self.callback (/usr/local/Cellar/yarn/1.22.10/libexec/lib/cli.js:140749:22)
at Request.emit (events.js:315:20)
at Request.<anonymous> (/usr/local/Cellar/yarn/1.22.10/libexec/lib/cli.js:141721:10)
at Request.emit (events.js:315:20)
at IncomingMessage.<anonymous> (/usr/local/Cellar/yarn/1.22.10/libexec/lib/cli.js:141643:12)
at Object.onceWrapper (events.js:421:28)
at IncomingMessage.emit (events.js:327:22) {
responseCode: 502
}
I tried
to remove yarn.lock file and run yarn install again
to increase network timeout yarn install --network-timeout 100000
Still getting the same error
this worked for me:
Delete any "*.lock" and rm node_modules. Or rm -rf node_modules/
Clean a flush all connections things like DNS, caches and so on.
Terminal commands:
set http_proxy=
set https_proxy=
yarn config delete proxy
npm config rm https-proxy
npm config rm proxy
npm config set registry "http://registry.npmjs.org" or npm config set registry "https://registry.npmjs.org"
Restart your terminal and Try.
Use : yarn add mypckge --network-timeout 100000 or yarn --network-timeout 100000
but first try just yarn
Restart your terminal and Try yarn again and/or with --network-timeout.
link to MichelDiz answer
I am trying to install react-snap using this command 'sudo npm install --save-dev react-snap' in ubuntu 18 it's give me the error
ERROR: Failed to download Chromium r686378! Set "PUPPETEER_SKIP_CHROMIUM_DOWNLOAD" env variable to skip download.
after search i will get the solution to run this command
sudo npm install -g puppeteer --unsafe-perm=true --allow-root
after running this command still, i am facing this error, My react version is 16.8
ERROR: Failed to download Chromium r686378! Set "PUPPETEER_SKIP_CHROMIUM_DOWNLOAD" env variable to skip download
npm ERR! code ELIFECYCLE
npm ERR! errno 1
npm ERR! puppeteer#1.20.0 install: `node install.js`
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the puppeteer#1.20.0 install script.
npm ERR! This is probably not a problem with npm. There is likely additional logging output above.
The best way is to export default env var PUPPETEER_SKIP_CHROMIUM_DOWNLOAD
PUPPETEER_SKIP_CHROMIUM_DOWNLOAD=true yarn add puppeteer or
PUPPETEER_SKIP_CHROMIUM_DOWNLOAD=true npm install puppeteer
I fixed it by installing Chromium manually using this command:
node node_modules/puppeteer/install.js
I had same issue with puppeteer#1.20 install when trying to run npm i aws-azure-login on mac, after doing sudo npm install -g puppeteer --unsafe-perm=true --allow-root. It seems Puppeteer doesn't install globally with execution permissions for all users so you'll need to modify them (https://libraries.io/npm/aws-azure-login). You can try sudo chmod -R go+rx $(npm root -g)
I finally got aws-azure-login to install without any issues by changing npm default behavior to install global packages in my home directory:
mkdir ~/.npm-global
npm config set prefix '~/.npm-global'
export PATH=~/.npm-global/bin:$PATH
source ~/.profile
echo 'export PATH=~/.npm-global/bin:$PATH' >> ~/.profile
source ~/.profile
See https://docs.npmjs.com/resolving-eacces-permissions-errors-when-installing-packages-globally
PS C:\Users\myuser> $env:PUPPETEER_SKIP_CHROMIUM_DOWNLOAD=0
PS C:\Users\myuser> npm install puppeteer --unsafe-perm=true --allow-root
works at my local windows10. similar issues https://github.com/puppeteer/puppeteer/issues/2173
In our case, when we try to install "aws-azure-login" using npm install, our enterprise proxy client trying to inspect the SSL traffic by presenting its own Self Signed certificate which is trusted in my local truststore. So we have to download these CAcert using OpenSSL commands & using "NODE_EXTRA_CA_CERTS" argument to specify the additional downloaded cert path, we were able to download & install the puppeteer on my MacOS.
Here are the steps:
download the CAcert that enterprise proxy presents when we try to connect to any domain [storage.googleapis.com].
> openssl s_client -showcerts -verify 5 -servername storage.googleapis.com -connect storage.googleapis.com:443 < /dev/null | awk '/BEGIN/,/END/{ if(/BEGIN/){a++}; out="cert"a".crt"; print >out}' && for cert in *.crt; do newname=$(openssl x509 -noout -subject -in $cert | sed -n 's/^.*CN=\(.*\)$/\1/; s/[ ,.*]/_/g; s/__/_/g; s/^_//g;p').pem; mv $cert $newname; done
The above command will download all the domain, intermediate & root certificates of the Proxy. Concatenate all the certificates into a single PEM file.
cat domain1.crt intermediate.crt root.crt >extra_cacert.pem
Specify the NODE_EXTRA_CA_CERTS argument while installing the puppeteer using npm
NODE_EXTRA_CA_CERTS=./extra_cacert.pem node /Users/velayutham/aws-azure-login/node_modules/puppeteer/install.js
The above steps were tested in MacOS!!!
I'm rebuilding after a crash & subsequent upgrade to Ubuntu 18.04 LTS. Everything seems to be back to normal except for Python's pkg manager.
Below is launched by:
$sudo apt update
$sudo apt install python3-pip
The logs at first say that python3-pip is already installed:
python3-pip is already the newest version (9.0.1-2.3~ubuntu1.18.04.1).
Then the installation apparently bombs as shown:
dpkg: error processing package libclojure-java (--configure):
dpkg: dependency problems prevent configuration of librobert-hooke-clojure:
dpkg: error processing package librobert-hooke-clojure (--configure):
Also at the bottom of the error message:
E: Sub-process /usr/bin/dpkg returned an error code (1)
I understand dpkg is the Debian pkg manager but I am unsure of the best next step.
do you try to missing package by this command
sudo apt-get install -f
and then for update missing try
sudo apt-get update --fix-missing
and for upgrade missing package
sudo apt-get upgrade --fix-missing
I'm getting this error when I run npm run test for a create-react-app application for the sample test provided. I tried looking for the EMFILE error but I'm unable to understand what's going wrong.
Error: Error watching file for changes: EMFILE
at exports._errnoException (util.js:1022:11)
at FSEvent.FSWatcher._handle.onchange (fs.js:1406:11)
I had the same issue and discovered watchman was not installed.
Run brew install watchman.
Issue is happening since watchman is not installed on your system.
On Linux, you need to do following
Install Watchman using following commands
git clone https://github.com/facebook/watchman.git
cd watchman/
git checkout v4.9.0
sudo apt-get install -y autoconf automake build-essential python-dev libssl-dev libtool
./autogen.sh
./configure
make
sudo make install
Execute tests
sudo npm test
it failed to install unix.
C:\Windows\system32>cabal install hdevtools
Resolving dependencies...
Configuring unix-2.6.0.1...
cabal: The package has a './configure' script. This requires a Unix
compatibility toolchain such as MinGW+MSYS or Cygwin.
Failed to install unix-2.6.0.1
cabal: Error: some packages failed to install:
hdevtools-0.1.0.5 depends on unix-2.6.0.1 which failed to install.
unix-2.6.0.1 failed during the configure step. The exception was:
ExitFailure 1
C:\Windows\system32>
For Windows you may use this fork https://github.com/mvoidex/hdevtools.