Can't get newest why3 version from opam - ocaml

I am using Linux Slackware 14.2, opam version 1.2.2, ocaml 4.03.0 and wanted to install why3 module. As far as I can see in the Internet, the last version of why3 package is 1.2.0.
But even after I ran
opam update
It still suggests my to install why3 1.0.0.
What should I do to update the packages list?
How can I install why3 module system wide as root? Is it safe enough?

Your opam and ocaml installations are both seriously out of date. The latest version of OCaml is 4.07.1, and the latest version of opam is 2.0.4. Linux distro repositories are unfortunately often not very up to date, and as I understand it, packages published for opam v2 aren't backwards-compatible with opam v1.x.
Try installing the latest opam by following the installation guide. Then, using opam, install a more recent version of OCaml and you should be able to get the latest version of why3.
It's recommended to manage your OCaml installations and associated packages with opam instead of installing them globally, since that can potentially cause an unruly mess of broken dependencies over time.

Related

aws-RunPatchBaseline doesn´t install new packages through apt-get

After running a few tests through AWS SSM Document aws-RunPatchBaseline, the content code used for Debian based OS like Ubuntu doesn´t truly install any required packages even setting this with "install" parameter and being executed. Is this something that needs to be fixed or why does this SSM document work this way without truly installing packages.
From documentation, please see below:
apt-get update downloads the package lists from the repositories and "updates" them to get information on the newest versions of packages and their dependencies. It will do this for all repositories and PPAs. From http://linux.die.net/man/8/apt-get:
Used to re-synchronize the package index files from their sources. The indexes of available packages are fetched from the location(s) specified in /etc/apt/sources.list(5). An update should always be performed before an upgrade or dist-upgrade.
apt-get upgrade will fetch new versions of packages existing on the machine if APT knows about these new versions by way of apt-get update.
From http://linux.die.net/man/8/apt-get:
Used to install the newest versions of all packages currently installed on the system from the sources enumerated in /etc/apt/sources.list(5). Packages currently installed with new versions available are retrieved and upgraded; under no circumstances are currently installed packages removed, nor are packages that are not already installed retrieved and installed. New versions of currently installed packages that cannot be upgraded without changing the install status of another package will be left at their current version. [Emphasis mine] An update must be performed first so that apt-get knows that new versions of packages are available.
Currently code content has this:
" apt-get update >/dev/null",
" fi",
"}",
¿Should I add a custom line or create a custom ssm with apt-get upgrade -y after apt-get update?, this document is supossed to work by installing packages, but so far on Ubuntu for example it just doesn´t do anything besides updating the package lists from repos (without installing any).
In my experience, on Ubuntu 20.04, it works. You can verify this by checking apt logs after you run AWS-RunPatchBaseline on such an instance. The logs are located in:
/var/log/apt/history.log
and
/var/log/apt/term.log
Since you have provided any details on what where your tests, which linux distribution did you use, nor provided any log output with possible errors of ssm agent or apt, it is difficult to speculate why it does not work for you.
The actual upgrade is performed by a python script, not the command you listed. You can inspect its code after you run AWS-RunPatchBaseline:
/var/log/amazon/ssm/patch-baseline-operations

Opam could install latest package and told 'Already up-to-date'?

I wanna use opam to install dune package whose version is 1.11.0 or higher. But it told me Already up-to-date while dune is still 1.2.1.
pasting my operations:
$ opam update
=-=- Updating package repositories =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
[default] synchronized from https://opam.ocaml.org/1.2.2
And then:
$ opam upgrade dune
Already up-to-date.
But dune didn't be upgraded.. It's still 1.2.1.. How can I install higher version I wanted?
opam --version is 1.2.2
dune --version is 1.2.1
The culprit is this phrase
[default] synchronized from https://opam.ocaml.org/1.2.2
^^^^^^
The 1.2.2 version of opam is long ago deprecated and is never updated, so you can't get anything new. You shall install opam 2.0 to get access to the newest packages.

Later version of GEOS on pypi

I am trying to install GEOS 3.3.3 on my workstation. When I look at pypi (https://pypi.org/search/?q=geos), I only see versions up to 0.2.1. Do I need to install it from somewhere else?
If you are needing to setup GEOS for a python environment, you should check out Anaconda's python distribution environment. They provide pre-built GEOS for many platforms. https://anaconda.org/search?q=geos
see https://www.anaconda.com/distribution/

How to install Xeus-cling without Anaconda?

Why is Anaconda package manager necessary to install Xeus-cling?
I have only used pip so far, and switching to a new package manager seems like a lot of work. I want to start using C++ with Jupyter, but all the installation instructions assume conda package manager.
Does anyone know of Xeus-cling installation which doesn't require Anaconda?
Pip is a package manager for python. It is mostly meant for packaging pure Python packages even though shipping some binary extensions is possible.
xeus-cling is a native application, which relies on a number of other libraries, including LLVM, Clang, Cling, Xeus, OpenSSL, libzmq and other. Vendoring the entire LLVM stack in a pip package would be unreasonable.
The developers of xeus-cling have made the choice of conda because it is a general-purpose cross-platform package manager, but it could be packaged for other general-purpose package managers, such as Debian's dpkg, OSX's Homebrew, conan.io or others.

RHEL 7 installing tkinter with python 2.7

I've disabled the subscription manager and registered a few repos, epel and remi, but am unable to install tkinter. Keep getting the error no package available. The only package available is for python 3.4. Was wondering whether anyone else had run into this issue. Not sure how to resolve it there's not a lot of documentation on the RHEL website.
I've also tried installing tcl/tk and yum can't seem to find these packages either. The one package with tcl in it it fails because of dependency problems. No luck with yum groupinstall -y "development tools" either. I'm mostly just trying to install pyautogui which requires tkinter be installed already.
The tkinter package is in the rhel-7-server-optional-rpms repo, though I don't see pyautogui available in RHEL.
Your mileage may vary on whether tkinter is at the right version needed.