My project is a monorepo using Yarn Workspaces.
Why does my Yarn Lockfile give this warning? How does it happen? What can you do to fix it?
Yarn version 1.22.19
warning Lockfile has incorrect entry for "#typescript-eslint/parser#^2.34.0". Ignoring it.
warning Lockfile has incorrect entry for "#typescript-eslint/eslint-plugin#2.x". Ignoring it.
warning Lockfile has incorrect entry for "#typescript-eslint/parser#2.x". Ignoring it.
warning Lockfile has incorrect entry for "#pmmmwh/react-refresh-webpack-plugin#^0.4.3". Ignoring it.
warning Lockfile has incorrect entry for "tslib#^1.10.0". Ignoring it.
warning Lockfile has incorrect entry for "graphql#^14.5.8". Ignoring it.
warning Lockfile has incorrect entry for "tslib#^1.9.3". Ignoring it.
warning Lockfile has incorrect entry for "graphql#^14.7.0". Ignoring it.
warning Lockfile has incorrect entry for "browserslist#4.10.0". Ignoring it.
warning Lockfile has incorrect entry for "graphql-tag#2.12.4". Ignoring it.
warning Lockfile has incorrect entry for "browserslist#4.7.0". Ignoring it.
warning Lockfile has incorrect entry for "browserslist#^2.11.3". Ignoring it.
warning Lockfile has incorrect entry for "browserslist#4.1.1". Ignoring it.
warning Lockfile has incorrect entry for "tslib#~2.4.0". Ignoring it.
warning Lockfile has incorrect entry for "browserslist#^4.20.3". Ignoring it.
warning Lockfile has incorrect entry for "tslib#1.11.1". Ignoring it.
warning Lockfile has incorrect entry for "tslib#^1.11.1". Ignoring it.
warning Lockfile has incorrect entry for "prettier#~2.2.1". Ignoring it.
warning Lockfile has incorrect entry for "emeth#^1.0.2". Ignoring it.
warning Lockfile has incorrect entry for "tslib#^1.9.0". Ignoring it.
warning Lockfile has incorrect entry for "typescript#~4.1.3". Ignoring it.
warning Lockfile has incorrect entry for "browserslist#4.14.2". Ignoring it.
warning Lockfile has incorrect entry for "prettier#^1.9.2". Ignoring it.
warning Lockfile has incorrect entry for "tslib#~2.1.0". Ignoring it.
warning Lockfile has incorrect entry for "browserslist#^4.20.2". Ignoring it.
warning Lockfile has incorrect entry for "browserslist#^4.21.2". Ignoring it.
warning Lockfile has incorrect entry for "tslib#^1.8.1". Ignoring it.
warning Lockfile has incorrect entry for "tslib#~2.2.0". Ignoring it.
warning Lockfile has incorrect entry for "tslib#^1". Ignoring it.
warning Lockfile has incorrect entry for "browserslist#^3.2.6". Ignoring it.
warning Lockfile has incorrect entry for "eslint#^4.0.0". Ignoring it.
warning Lockfile has incorrect entry for "prettier#^1.7.0". Ignoring it.
warning Lockfile has incorrect entry for "typescript#^2.5.1". Ignoring it.
warning Lockfile has incorrect entry for "node-gyp#^5.0.2". Ignoring it.
warning Lockfile has incorrect entry for "tslib#^1.0.0". Ignoring it.
Related
I can't install ruby 3.0.0 through my powershell, when I try rvm install 3.0.0 I receive a beautiful error:
Error running 'requirements_osx_brew_libs_install gcc#6',
please read /Users/ben/.rvm/log/1673079096_ruby-3.0.0/package_install_gcc#6.log
Requirements installation failed with status: 1.
I feel like I've tried everything to resolve this problem but without success.
-This is my gcc version:
Configured with: --prefix=/Library/Developer/CommandLineTools/usr --with-gxx-include-dir=/usr/include/c++/4.2.1 Apple LLVM version 10.0.0 (clang-1000.10.44.4) Target: x86_64-apple-darwin17.7.0 Thread model: posix InstalledDir: /Library/Developer/CommandLineTools/usr/bin
-homebrew version:
Homebrew 3.6.17-66-g974984d Homebrew/homebrew-core (git revision 0149ce7e63e; last commit 2023-01-07)
-rvm version:
rvm 1.29.12 (latest) by Michal Papis, Piotr Kuczynski, Wayne E. Seguin [https://rvm.io]
-ruby version:
ruby 2.3.7p456 (2018-03-28 revision 63024) [universal.x86_64-darwin17]
-which ruby:
/usr/bin/ruby
And when I run rvm install 3.0.0 this is what I receive:
Error: Invalid usage: This command requires at least 1 text or regex argument.
Usage: brew search, -S [options] text|/regex/ [...]
Perform a substring search of cask tokens and formula names for text. If
text is flanked by slashes, it is interpreted as a regular expression. The
search for text is extended online to homebrew/core and homebrew/cask.
--formula, --formulae Search online and locally for formulae.
--cask, --casks Search online and locally for casks.
--desc Search for formulae with a description
matching text and casks with a name or
description matching text.
--eval-all Evaluate all available formulae and casks,
whether installed or not, to search their
descriptions. Implied if HOMEBREW_EVAL_ALL is
set.
--pull-request Search for GitHub pull requests containing
text.
--open Search for only open GitHub pull requests.
--closed Search for only closed GitHub pull requests.
--repology Search for text in the given database.
--macports Search for text in the given database.
--fink Search for text in the given database.
--opensuse Search for text in the given database.
--fedora Search for text in the given database.
--archlinux Search for text in the given database.
--debian Search for text in the given database.
--ubuntu Search for text in the given database.
-d, --debug Display any debugging information.
-q, --quiet Make some output more quiet.
-v, --verbose Make some output more verbose.
-h, --help Show this message.
Error: Invalid usage: This command requires at least 1 text or regex argument.
Installing requirements for osx_brew.
Updating system..........
Installing required packages: gcc#6........There were package installation errors, make sure to read the log.
Try `brew tap --repair` and make sure `brew doctor` looks reasonable.
Check Homebrew requirements https://docs.brew.sh/Installation
.
Error running 'requirements_osx_brew_libs_install gcc#6',
please read /Users/benoitlardinois/.rvm/log/1673081014_ruby-3.0.0/package_install_gcc#6.log
Requirements installation failed with status: 1.
So, if I run brew install gcc#6, I receive:
Warning: You are using macOS 10.13.
We (and Apple) do not provide support for this old version.
It is expected behaviour that some formulae will fail to build in this old version.
It is expected behaviour that Homebrew will be buggy and slow.
Do not create any issues about this on Homebrew's GitHub repositories.
Do not create any issues even if you think this message is unrelated.
Any opened issues will be immediately closed without response.
Do not ask for help from MacHomebrew on Twitter.
You may ask for help in Homebrew's discussions but are unlikely to receive a response.
Try to figure out the problem yourself and submit a fix as a pull request.
We will review it but may or may not accept it.
Warning: gcc#6 has been deprecated because it is deprecated upstream!
==> Fetching dependencies for gcc#6: isl, mpfr and libmpc
==> Fetching isl
==> Downloading https://raw.githubusercontent.com/Homebrew/formula-patches/03cf8088210822aa2c1ab544ed
Already downloaded: /Users/benoitlardinois/Library/Caches/Homebrew/downloads/195208ba31cadc265ea97bb8aad4e78caab1200daf4d855e6c839b5f987f92db--configure-big_sur.diff
==> Downloading https://libisl.sourceforge.io/isl-0.25.tar.xz
Already downloaded: /Users/benoitlardinois/Library/Caches/Homebrew/downloads/dce6d1ed4d25c923a4ad350c4b9cdf03406f649cd55be8c385814703502b5c81--isl-0.25.tar.xz
==> Fetching mpfr
==> Downloading https://ftp.gnu.org/gnu/mpfr/mpfr-4.2.0.tar.xz
Already downloaded: /Users/benoitlardinois/Library/Caches/Homebrew/downloads/2b7a1efec00f58b200d550146d18563516f005674020aa39ca2cd6666cb1d215--mpfr-4.2.0.tar.xz
==> Fetching libmpc
==> Downloading https://ftp.gnu.org/gnu/mpc/mpc-1.3.1.tar.gz
Already downloaded: /Users/benoitlardinois/Library/Caches/Homebrew/downloads/22a255b07a458ea7bd9717c0d1509282a69135dd842aa6b64144820c50bfd208--mpc-1.3.1.tar.gz
==> Fetching gcc#6
==> Downloading https://ftp.gnu.org/gnu/gcc/gcc-6.5.0/gcc-6.5.0.tar.xz
Already downloaded: /Users/benoitlardinois/Library/Caches/Homebrew/downloads/0a7c1b4768113746153c6e06f4ea6b2abf2d8ba48a68bf28f7c686b70117540e--gcc-6.5.0.tar.xz
==> Installing dependencies for gcc#6: isl, mpfr and libmpc
==> Installing gcc#6 dependency: isl
==> Patching
==> Applying configure-big_sur.diff
patching file configure
Hunk #1 succeeded at 13866 (offset 5133 lines).
==> ./configure --prefix=/usr/local/Cellar/isl/0.25 --with-gmp=system --with-gmp-prefix=/usr/local/op
==> make
Last 15 lines from /Users/benoitlardinois/Library/Logs/Homebrew/isl/02.make:
constexpr value_type& value() &
^
/Library/Developer/CommandLineTools/usr/include/c++/v1/optional:933:33: note: candidate function has been explicitly made unavailable
constexpr value_type const& value() const&
^
/Library/Developer/CommandLineTools/usr/include/c++/v1/optional:951:28: note: candidate function not viable: no known conversion from 'optional<...>' to 'optional<...>' for object argument
constexpr value_type&& value() &&
^
/Library/Developer/CommandLineTools/usr/include/c++/v1/optional:960:34: note: candidate function not viable: no known conversion from 'optional<...>' to 'const optional<...>' for object argument
constexpr value_type const&& value() const&&
^
2 errors generated.
make[2]: *** [isl_test_cpp17.o] Error 1
make[1]: *** [all-recursive] Error 1
make: *** [all] Error 2
Do not report this issue to Homebrew/brew or Homebrew/core!
Error: You are using macOS 10.13.
We (and Apple) do not provide support for this old version.
It is expected behaviour that some formulae will fail to build in this old version.
It is expected behaviour that Homebrew will be buggy and slow.
Do not create any issues about this on Homebrew's GitHub repositories.
Do not create any issues even if you think this message is unrelated.
Any opened issues will be immediately closed without response.
Do not ask for help from MacHomebrew on Twitter.
You may ask for help in Homebrew's discussions but are unlikely to receive a response.
Try to figure out the problem yourself and submit a fix as a pull request.
We will review it but may or may not accept it.
I'm in despair, I don't know what I'm supposed to do.
The warning is clearly stating that macOS 10.13 is too old, so the best thing is to upgrade the OS - there were several failed attempts to build Ruby 3.0 - see https://github.com/rvm/rvm/issues/5055
Also, GCC below version 10 are deprecated - see homebrew issue https://github.com/Homebrew/homebrew-core/pull/110163
Though, you can first try switching from rvm to rbenv - seems like someone get it done with rbenv on High Sierra - https://github.com/rvm/rvm/issues/5012#issuecomment-811858777
I am messing with this error. I can't install packages.
warning package.json: No license field
warning No license field
[1/4] Resolving packages...
[2/4] Fetching packages...
error An unexpected error occurred: "https://registry.yarnpkg.com/commander/-/commander-2.20.0.tgz: error:0909006C:PEM routines:get_name:no start line".```
Thank you for your help.
I solved that. Problem was in yarn config. I have there unnecessary attribute for certificate, the attribute says where the certificate is stored. But for registry.yarnpkg.com you need no local PEM certifikate. So I just deleted the attribute and that was it.
Following the suggestion of #liberforce, I am running Mingw-w64 64bit shell.
I got less warnings than with msys2 shell.
Here are the warnings I got.
warning: could not get file information for clang32/
warning: could not get file information for clang32/bin/
warning: could not get file information for clang32/etc/
warning: could not get file information for clang32/etc/config.site
warning: could not get file information for clang32/include/
warning: could not get file information for clang32/lib/
warning: could not get file information for clang32/share/
warning: could not get file information for clang64/
warning: could not get file information for clang64/bin/
warning: could not get file information for clang64/etc/
warning: could not get file information for clang64/etc/config.site
warning: could not get file information for clang64/include/
warning: could not get file information for clang64/lib/
warning: could not get file information for clang64/share/
warning: could not get file information for opt/
warning given when extracting /usr/bin/cygpath.exe (Can't create '/usr/bin/cygpath.exe')
warning given when extracting /usr/bin/cygwin-console-helper.exe (Can't create '/usr/bin/cygwin-console-helper.exe')
warning given when extracting /usr/bin/locale.exe (Can't create '/usr/bin/locale.exe')
warning given when extracting /usr/bin/tzset.exe (Can't create '/usr/bin/tzset.exe')
warning: terminate MSYS2 without returning to shell and check for updates again
warning: for example close your terminal window instead of calling exit
Normally when I follow the last instruction, when I run the shell again, it just opens the terminal window, quickly shows an error, I can't read quick enough, and quickly closes.
So, I reinstall, and don't use pacman -Syu, to update, but install each module with pacman -S.
However, at this point, I want to know, will the above warnings prove problematic going forward?
error inputting api key into cointop.sh.
I say "installing $: cointop
FATA[0000] Near line 80 (last key parsed 'coinmarketcap.pro_api_key'): unexpected EOF"
I need to put back in the proper API key as i goofed up the system,
I have deleted cointop from brew and reran the cointop but unfortently
i get the error below:
FATA[0000] Near line 80 (last key parsed 'coinmarketcap.pro_api_key'): unexpected EOF``
<code>
cointop
FATA[0000] Near line 80 (last key parsed 'coinmarketcap.pro_api_key'): unexpected EOF
</code>
I just wanted a simple install script for this but i'm not smart
and wanted to say oops to cointop for this error/fix.
cointop author here; this might have been fixed in the latest release but if you encounter issues like this even after installing the latest version then you can reset the config with cointop --reset (make sure to backup relevant changes first)
I'm having trouble reinstalling ProFTPD on a FreeBSD 10.1 setup. The server is newly upgraded from 10.0 to 10.1. When I start the make install clean process, these warnings first shows on screen.
===> proftpd-1.3.5_4 depends on shared library: libpcre.so
/usr/share/misc/magic, 93: Warning: Printf format `l' is not valid for type `lelong' in description `, %ld pages'
...
/usr/share/misc/magic, 15118: Warning: Printf format `l' is not valid for type `belong' in description `Volume %ld,'
/usr/share/misc/magic, 15609: Warning: Current entry does not yet have a description for adding a MIME type
file: File 5.19 supports only version 12 magic files. `/usr/share/misc/magic.mgc' is version 8
[: =: unexpected operator
- not found
And after i while, the make process stops with this error:
/bin/ln -s libpcre.so.1 /usr/ports/devel/pcre/work/stage/usr/local/lib/libpcre.so.3
====> Compressing man pages (compress-man)
===> Installing for pcre-8.35_2
===> Checking if pcre already installed
===> pcre-8.35_2 is already installed
You may wish to ``make deinstall'' and install this port again
by ``make reinstall'' to upgrade it properly.
If you really wish to overwrite the old port of pcre
without deleting it first, set the variable "FORCE_PKG_REGISTER"
in your environment or the "make install" command line.
*** Error code 1
Stop.
make[3]: stopped in /usr/ports/devel/pcre
*** Error code 1
Stop.
make[2]: stopped in /usr/ports/devel/pcre
*** Error code 1
Stop.
make[1]: stopped in /usr/ports/ftp/proftpd
*** Error code 1
Stop.
make: stopped in /usr/ports/ftp/proftpd
Seems that the file /usr/share/misc/magic.mgc is of a wrong version?
This might happens when I was upgrading from 10.0-RELEASE-p12 to 10.1-RELESE-p1?
If i run make install clean of the ProFTP port, and disable support for pcre, the process and install is successful.
But I believe that something is still broken?
My programming skills are limited, and also this level of error.
Please let me know if you have any ideas,
Thanks,
First of all, proftpd 1.3.5 is available as a binary package, it's much simpler to install it that way (pkg install proftpd).
Second - at first it looked like a port bug; as Etan said, there is a shell syntax error (something like '[ x == y ]' instead of '[ x = y ]'); those are common, and ports contain patches to fix those. However, there is a binary package, and packages are built from ports ("make package"), so port obviously does work on package build machines. So it's probably something specific to your environment.
If you really want to build from ports, try this: first, reinstall pcre. For some reason it had to be rebuilt, but failed to install, because it's already installed. So, "cd /usr/ports/*/pcre && make clean all deinstall reinstall". That should get rid of the second error. Then go back to "../*/proftpd" and see how far it goes.
But really, I'd try packages first. They have nothing in common with old pkg_add system, and are really nice.
freebsd-update diff for FreeBSD-SA-14:28.file seems wrong, and it breaks file(1).
Therefore simply pkg install file will be a workaround.