Stream: Hierarchy Builder devs & users

Topic: coq-elpi nix package breaks


view this post on Zulip Cyril Cohen (May 18 2020 at 17:27):

I'm preparing elpi-1.11(.2) package and of course it breaks the last release of coq-elpi :-/

view this post on Zulip Enrico Tassi (May 18 2020 at 17:30):

I'm about to release coq-elpi 1.4 that works with elpi 1.11.2

view this post on Zulip Enrico Tassi (May 18 2020 at 17:32):

At least in opam, coq-elpi has a strict dependency on elpi. It is expected. I don't know which is the model of nix to handle transition of multiple packages with strict dependencies. If it is like in debian, you will have to wait until coq-elpi 1.4 is out, which is in a few days

view this post on Zulip Enrico Tassi (May 18 2020 at 17:33):

The changes in the ML API between elpi 1.10 and 1.11 are very small, so a backport of coq-elpi 1.3 is possible, but I don't think it is worth it.

view this post on Zulip Cyril Cohen (May 18 2020 at 17:41):

Enrico Tassi said:

At least in opam, coq-elpi has a strict dependency on elpi. It is expected. I don't know which is the model of nix to handle transition of multiple packages with strict dependencies. If it is like in debian, you will have to wait until coq-elpi 1.4 is out, which is in a few days

The policy is that both may exist, but only one is promoted (i.e. accessible via the minimum number of characters) and it is generally the most recent one with enough working dependencies (so in short, yes I will wait ;))

view this post on Zulip Cyril Cohen (May 18 2020 at 17:41):

but I can use my nixpkgs branch + coq-elpi master to provide a shell for hb

view this post on Zulip Cyril Cohen (May 18 2020 at 17:42):

Enrico Tassi said:

The changes in the ML API between elpi 1.10 and 1.11 are very small, so a backport of coq-elpi 1.3 is possible, but I don't think it is worth it.

Yeah don't bother

view this post on Zulip Enrico Tassi (May 19 2020 at 15:13):

I made the tag for coq-elpi 1.4

view this post on Zulip Enrico Tassi (May 26 2020 at 14:40):

We should make a tag on master, then merge it also in coq-master, then branch from that point a coq-v8.12 branch that will be followed by 8.12 beta, final and point releases. I should do the same for coq-elpi (I've already the tag, and it is merged in coq-master). CI should be updated accordingly, so that if we need to push a fix to coq-8.12 we can test it.


Last updated: Jan 29 2023 at 15:02 UTC