I'm trying to install the emacs-x11 package on SLES 15 and getting the following error:
nothing provides libm17n-core.so.0()(64bit) needed by emacs-x11-25.3-3.3.18.x86_64
Has anyone else encountered this error, and more importantly know how to resolve it?
I found that using YaST to add the M17N software repository at http://download.opensuse.org/repositories/M17N/SLE_15/ solved my problem.
Related
I get the following error when running install-agraph for agraph-6.6.0
An unhandled error occurred during initialization:
Loading sys:aclissl.so failed with error:
/home/<username>/agraph-6.6.0/aclissl.so: undefined symbol: CRYPTO_set_locking_callback.
[physical pathname is /home/<username>/agraph-6.6.0/aclissl.so]
Cannot find much with google-fu on this error - at least nothing useful. Any leads would be helpful.
This problem has been fixed in the upcoming 7.0 release of AllegroGraph. Your workaround, using a system with OpenSSL 1.0.x is the correct one, for the currently released version of AllegroGraph.
I created a project with vue-cli 4.1.1, and after running yarn serve, i got the following error
Error: [BABEL] C:\dev\vuestudy\src\main.js: Cannot find module './src/data' (While processing: "C:\\dev\\vuestudy\\node_modules\\#vue\\cli-plugin-babel\\preset.js")
Any tips on this?
Thanks in advance.
UPDATE:
Kousha and Dave are right,after waiting for the core-js package update, I created a new project, and now it's working.
It looks like there's been a bad build of npm package core-js-compat. This is a deep-down dependency of Babel. Lots of things will be affected, things that use Babel.
You will experience this problem if you have core-js-compat v.3.4.6. You can check this by doing npm list core-js-compat. The problem is apparently fixed by v.3.4.7, which was pushed out pretty quickly, about half-an-hour later, but unfortunately it takes a while to spread out through the repositories. You can either wait until an npm update gets you v.3.4.7 or you can go manually download v.3.4.7 if you want to get going right away.
This is a bug with core-js-compat v3.4.6, but already the fix has gone with v3.4.7. See https://github.com/zloirock/core-js/issues/712 for more detail.
You may be able to force install the not-broken version with
npm i core-js-compat#3.4.7 --save
It worked on my machine™
With Vue / Nuxt, you can delete package-lock.json and node_modules and do an npm install to fix this issue.
I managed to get the latest Yarn v1.13.0 installed on Xubuntu 16 with their curl installation instruction.
Now I'm getting this errors trying to install a project's dependencies.
An expected error occurred:
"https://registry.yarnpkg.com/event-stream/-/event-stream-3.3.6.tgz:
Request failed \"404 Not Found\
Same 'Not Found' message is displayed by the error url.
Seems to be caused by the security issue https://github.com/dominictarr/event-stream/issues/116?utm_content=educational&utm_campaign=2018-11-28&utm_source=email-sendgrid&utm_term=13952972&utm_medium=833442
How do I fix it? How do I find the project deps that use the corrupted version of event-stream?
Seemingly was caused by an older version of Nodemon prolly affected by the security issue above. Updating it to the latest version in package.json seemed to have helped.
Attempting to install Specio::Constraint::Simple, running into the following error:
Can't resolve method "???" overloading "&{}" in package
"Specio::Constraint::Simple" at Specio::Constraint::Simple->new line
35.
Only related article I have found has been: https://rt.cpan.org/Public/Bug/Display.html?id=117975
Any suggestions would be appreciated.
Thank you
This is caused by a bug in older versions of Role::Tiny that was fixed in version 1.003003:
overloads specified as method names rather than subrefs are now applied
properly
Upgrading Role::Tiny should fix it and allow Specio::Constraint::Simple to be installed normally.
Actually, you don't even need to do that manually: Version 0.26 of Specio now requires at least version 1.003003 of Role::Tiny. Any future attempt to install Specio will upgrade Role::Tiny automatically (if required).
When I start MATLAB I suddenly receive the following error message on the command line:
ERROR: Can't check 8.0 VCRTs (starter line:956) System Error:
0x00000005 ERROR: Can't check 9.0 VCRTs (starter line:995) System
Error: 0x00000005 Installing required 8.0 run-time libraries. This may
take a few minutes...
I tried to repair and reinstall the Visual C++ Redistributables (2005 and 2008), but that didn't solve the problem. Doing online research I mainly found out that people who had a similar problem reinstalled windows. Well, does anyone have another idea what I could try in order to solve that?