Updating PACE
Julia never updates a package on its own, and Pkg.update() gives no warning when it cannot
reach the latest version: it keeps the newest set of versions that fit together and says
nothing more. This page shows how to update, how to see what was left behind, and how to remove
what holds it back.
1. Before updating
Quit Maple, MATLAB, the Jupyter notebooks and every Julia session that uses PACE. A running session keeps the old version loaded, and on Windows it locks the files to be replaced.
2. Update an environment
Packages are installed in an environment, a folder with Project.toml and Manifest.toml;
each environment is updated on its own. The usual ones:
| used by | environment | in Julia |
|---|---|---|
Julia without --project |
the default one, ~/.julia/environments/v1.x |
Pkg.activate() |
| the worksheets | ~/pace-worksheets/pace, control, robots |
Pkg.activate(joinpath(homedir(), "pace-worksheets", "pace")) |
| PACE for Maple | ~/.julia/environments/pace-maple |
Pkg.activate("pace-maple"; shared = true) |
| PACE for MATLAB | the one given to udx.setup |
Pkg.activate("/path/to/it") |
Then:
using Pkg
Pkg.update() # updates the registries, then the packages
Pkg.status(outdated = true) # what is still not at its latest version, and why
From a terminal, for the environment of PACE for Maple:
julia --project=@pace-maple -e 'using Pkg; Pkg.update(); Pkg.status(outdated = true)'
Pkg.status(outdated = true) lists the packages that are not at their latest version:
⌅ [2edaba10] Nemo v0.56.2 (<v0.57.2): CurveTopology, LACE, PACE, ...
⌃ [f671135e] PACE v1.0.2 (<v1.1.0)
⌅: held back by the compatibility bounds of the packages listed after the colon. Here PACE does not accept Nemo 0.57 yet: this is expected, nothing to do.⌃: a newer version exists and nothing listed prevents it, yetPkg.update()did not install it. Something else holds it back: see section 3.
The latest versions of the PACE packages are those of the PACE registry.
3. When PACE does not update
Ask for the version explicitly; where Pkg.update() is silent, this tells why:
Pkg.add(name = "PACE", version = "1.1")
The answer is either the update, or a message such as:
ERROR: Unsatisfiable requirements detected for package CurveTopology [5b3f0c1e]:
├─restricted by compatibility requirements with PACE [f671135e] to versions: 1.1.0
└─restricted by compatibility requirements with LACE [645ffd07] to versions: 1.0.0 — no versions left
└─LACE [645ffd07] log:
└─restricted to versions 1.0.0 by an explicit requirement, leaving only versions: 1.0.0
Read it from the bottom: the last line names the cause (here, LACE fixed at 1.0.0). The usual causes:
A package is pinned: ⚲ after its version in Pkg.status(). Release it:
Pkg.free("LACE")
Pkg.update()
A package was installed from its repository or a local folder: Pkg.status() shows a URL
(https://gitlab.inria.fr/...#main) or a path after its version. It then follows that repository
or that folder, not the registry. Return to the registry:
Pkg.free("PACE")
Pkg.update()
Another package of the environment needs other versions of a package shared with PACE (Nemo,
AbstractAlgebra, DynamicPolynomials, through the packages that depend on them). The message then
ends on that other package, restricted by compatibility requirements with ..., or on the
project itself if you added Nemo with a version of your own. The two cannot live in the same
environment: give PACE an environment of its own (section 4) and
keep the other package in yours.
Your Project.toml has a [compat] section that fixes a version (restricted to versions
0.57 by project). Remove or widen that line, then Pkg.update().
Julia is too old: the message mentions julia. Update Julia (juliaup update), then the
packages.
When PACE is installed in an environment that already has a recent Nemo, Pkg.add("PACE") may
also go the other way and downgrade Nemo, without an error (↓ Nemo v0.57.2 ⇒ v0.56.2). This is
the same conflict; if the other packages need the recent Nemo, use an environment of their own.
4. Start again from a clean environment
When an environment has accumulated too many constraints, it is quicker to make a new one than to untangle it. Keep only PACE and what you use with it:
using Pkg
Pkg.activate(joinpath(homedir(), "pace-env"))
Pkg.add(["PACE", "Nemo", "AbstractAlgebra"])
then run Julia with julia --project=~/pace-env. For the worksheets, rename the folder of the
family (~/pace-worksheets/pace, …) and run its installation block again
(Running the worksheets).
For PACE for Maple, quit Maple and rename the folder ~/.julia/environments/pace-maple (on
Windows %USERPROFILE%\.julia\environments\pace-maple): the next with(PACE): followed by a call
installs it again, at the latest versions (a few minutes).
5. The registries
Pkg.update() updates the registries first. If the PACE registry cannot be updated (network,
interrupted update), Pkg.update() stops with an error naming PACE Julia Registry. Add it
again:
using Pkg
Pkg.Registry.rm("PACE Julia Registry")
Pkg.Registry.add(url = "https://gitlab.inria.fr/pace/pace-julia-registry.git")
Pkg.Registry.status() lists the registries installed: both General and PACE Julia Registry
must be there.
6. The Maple toolboxes
The Maple archives are not updated by Julia:
- PACE for Maple: download the new archive, quit Maple, extract it over the old one as in the
installation. At its first call, a new toolbox updates
the Julia packages of
pace-mapleonce (a few minutes). In between,PACE:-update();in Maple updates them to the latest versions of the registry; Julia restarts at the next call. Toolboxes older than November 2026 do neither: install the new one, or updatepace-maplefrom a terminal (section 2). - LACE for Maple: download the new archive, quit Maple, extract it over the old one
(installation). On macOS,
xattr -cragain.
7. Reporting a problem
If an update still fails, send the output of:
using Pkg
versioninfo()
Pkg.status(mode = Pkg.PKGMODE_MANIFEST)
Pkg.add(name = "PACE", version = "1.1") # the version you are trying to reach
run in the environment concerned.