fixed packages introduce conflicting requirements for BinDeps: - julia

After installing JuliaPro_v0.6.0.1_build-78.exe from scratch I tried to update packages via Pkg.update() I've got the following Error message:
fixed packages introduce conflicting requirements for BinDeps:
available versions are 0.0.1, 0.2.0, 0.2.1, 0.2.2, 0.2.3, 0.2.4,
0.2.5, 0.2.6, 0.2.7, 0.2.8, 0.2.9, 0.2.10, 0.2.11, 0.2.12, 0.2.13, 0.2.14,
0.3.0, 0.3.1, 0.3.2, 0.3.3, 0.3.4, 0.3.5, 0.3.6, 0.3.7, 0.3.8, 0.3.9, 0.3.10, 0.3.11, 0.3.12, 0.3.13, 0.3.14, 0.3.15, 0.3.16, 0.3.17, 0.3.18, 0.3.19, 0.3.20, 0.3.21, 0.3.22, 0.3.23, 0.4.0, 0.4.1, 0.4.2, 0.4.3, 0.4.4, 0.4.5, 0.4.7, 0.5.0 and 0.6.0
in update at base\pkg\pkg.jl:228
in #cd#1 at base\pkg\dir.jl:32
in withenv at base\env.jl:157
in cd at base\file.jl:59
in #3 at base\pkg\dir.jl:33
in update at base\pkg\entry.jl:461
in resolve at base\pkg\entry.jl:496
in check_requirements at base\pkg\query.jl:222
Trying to add an another Pkg leads to a same error message. Thus it is not possible to add further packages without solving this problem.
Any advice to resolve this problem are appreciated.

This just fixed it for me:
Pkg.rm("BinDeps")
The effect was downgrading BinDeps from 0.7.0 to 0.6.0.
Out of curiosity I did Pkg.update() afterwards, which has brought BinDeps back to 0.7.0, but it seems that previous conflicts are now gone.
I think the issue might have been that version 0.7.0 was installed but not registered as available.

Related

Issue running airflow on Mac M1: error in Flask-OpenID setup command: use_2to3 is invalid

Having an issue running airflow on my M1 Mac. Keeps erroring out with error in Flask-OpenID setup command: use_2to3 is invalid. I have setuptools < 58 and still having issues.
ERROR: Could not find a version that satisfies the requirement flask-openid==1.2.5 (from versions: 0.9, 0.9.1, 1.0, 1.0.1, 1.1, 1.1.1, 1.2, 1.2.1, 1.2.2, 1.2.3, 1.2.4, 1.2.5, 1.3.0)
ERROR: No matching distribution found for flask-openid==1.2.5
Yes. It's been fixed in flask_openid 1.2.6 (It's not a problem with Airflow but with FlaskOpenID).
Looks like for some reason your setuptools is not what you think it is. See:
https://github.com/pallets-eco/flask-openid/issues/59
You have not explained a crucial things - how you are installing airflow, neither which version of Airflow you try to install - which does not help in trying to help you unfortunately, so I have to make some guesses. Here is what you can do if you cannot - for any reason - downgrade to setuptools < 0.58.
If you are using Airlfow 2 and using constraints (as you should - this is the only supported way https://airflow.apache.org/docs/apache-airflow/stable/installation/installing-from-pypi.html) for some older version of Airflow, then possibly flask-openid is 1.2.5 in those old constraint versions. Please check it and if you REALLY want to stay with an older version, then you can download the constraint file locally, modify flask-openid version to 1.2.6 and point to the file instead of the github URL as you should do normally (If you don't use constraints - start using them immediately).
However, better option than installing an old version of Airflow, will be to update to the latest version of Airflow (currently 2.2.2 but we are about to start voting on 2.2.3), where this problem is for sure fixed (also in few other versions). Airflow folows SemVer so you should be generally safe to migrate to 2.2.2 if you've used an earlier version of Airflow 2.
If you are trying to install Airflow 1.10.* - then don't do it. Move Airflow 2 immediately. Airflow 1.10 has reached end of life in June 2021 and it's almost half a year as it did not receive any fixes - it won't receive any fixes for the Flask OpenID problem, so you are pretty much on your own here.
Also you make yourself vulnerable to unpatched security issues (Airlfow 1.10 stopped receiving also critical security fixes as of June 2021).

Error NU1202 Package Microsoft.Data.Sqlite.Core 2.0.0 is not compatible with uap10.0.14393 (UAP,Version=v10.0.14393) / win10-x64.

I've downloaded a working UWP solution targeting 16299 which I changed to target 14393 (Anniversary) so it would work on all Windows 10 Phones as well. Apart from the obvious errors where the solution uses newer W10 version methods and namespaces, I also get:
Error NU1202 Package Microsoft.Data.Sqlite.Core 2.0.0 is not compatible with uap10.0.14393 (UAP,Version=v10.0.14393) / win10-x64. (multiple times)
But according to https://blogs.windows.com/buildingapps/2017/02/06/using-sqlite-databases-uwp-apps/ Microsoft SQLite should work from 14393.
I've tried installing the oldest version number available (2.0.0 instaed of 2.1.0 now included) but that doesn't change the error.
How can I solve this problem?
Dick
sqlite.core is the core version and will work only from fall creators update and above. if you want to use sqlite on older versions then you can see details here : https://learn.microsoft.com/en-us/windows/uwp/data-access/sqlite-databases

Keep hitting the error ""loop_apply" not resolved from current namespace (plyr)" in ggplot2 with example codes

i keep hitting this error today and I already download the plyr from github but it still doesn't work. I restarted R-studio even my PC after installing plyr..
It appears the problem may be due to a change made to the way R resolves references to external DLLs, as mentioned halfway through the thread here.
Adding the parameter PACKAGE="plyr" to the .Call function call on line 12 of R/loop_apply.R in the source (clone from github), and then installing the package from that source (install.packages("<path to plyr source>", type="source", repos=NULL)) seems to fix it.

Error when trying to add meteor-jade

I'm surprised that I can not find anything regarding the error I am seeing... basically, when I do mrt add jade (https://github.com/mquandalle/meteor-jade/), I get the following:
=> Errors while scanning packages:
While building package `jade`:
packages/compileJade/plugin/compiler.js:126: HTML is not defined (compiling tests/tests.jade)
at _.extend.visitTag (packages/compileJade/plugin/compiler.js:126)
at _.extend.visitNode (packages/compileJade/plugin/compiler.js:90)
at _.extend.visitBlock (packages/compileJade/plugin/compiler.js:74)
at _.extend.visitNode (packages/compileJade/plugin/compiler.js:84)
at _.extend.visitBlock (packages/compileJade/plugin/compiler.js:74)
at _.extend.compile (packages/compileJade/plugin/compiler.js:21)
at sourceHandler (packages/compileJade/plugin/handler.js:11)
While building plugin `compileJade` in package `jade`:
error: no such package: 'html-tools'
error: no such package: 'spacebars-compiler'
I did mrt update but still the same thing, any clue what is going on?
Try doing:
meteor update --release blaze-rc0
As explained on the meteor-jade github page:
Warning: This package is made for the new Meteor UI system, which is not released as a stable version yet. You'll need to run the blaze-rc0 release.
I believe the next major release of Meteor (0.8 or 1.0) is supposed to include the stable release of Blaze UI. At that point, you should be able to just do:
meteor update

Julia: Problems with Adding Packages (BinDeps)

I am new to Julia's package manager, and I am having trouble installing GLPK and LinProgGLPK.
I have already run Pkg.Init() and have successfully installed Curl using Pkg.add("Curl"). However, when I try to install GLPK or LinProgGLPK (using Pkg.add("GLPK") and Pkg.add("LinProgGLPK")), I get the following message:
MESSAGE: Installing BinDeps v0.0.0
ERROR: Path BinDeps already exists! Please remove to allow installation.
in _resolve at pkg.jl:345
in anonymous at no file:163
in cd at file.jl:26
in cd_pkgdir at pkg.jl:42
in add at pkg.jl:143
in add at pkg.jl:175
I seem to get the same message for other packages that are dependent on BinDeps (including Winston).
I have tried calling Pkg.rm("BinDeps"), Pkg.add("BinDeps"), Pkg.update(), and Pkg.resolve(), and then returned to trying to add GLPK, but the same message persists. I have also entered ~/.julia to remove the BinDeps folder, but that did not work either. What am I missing?
P.S. I am running julia in Linux Ubuntu.
Honestly, when something gets screwed up, it's best just to wipe ~/.julia and re-add the packages.
Just make sure you back up your local changes!

Resources