Closed solomon-b closed 1 year ago
Looks like the issue is that the opam-repository input to the flake is locked to an old commit. Is there a way for me to tell opam-nix to use a newer version of repository?
I solved this in my project by making opam-repository
an input my project's flake and forcing opam-nix to follow my pinned version:
inputs = {
+ opam-repository = {
+ url = "github:ocaml/opam-repository";
+ flake = false;
+ };
opam-nix.url = "github:tweag/opam-nix";
+ opam-nix.inputs.opam-repository.follows = "opam-repository";
flake-utils.url = "github:numtide/flake-utils";
nixpkgs.follows = "opam-nix/nixpkgs";
};
- outputs = { self, flake-utils, opam-nix, nixpkgs }@inputs:
+ outputs = { self, flake-utils, opam-nix, opam-repository, nixpkgs }@inputs:
Describe the bug I can see in
opam-repository
thatbwd-2.2
andyuujinchou-5.0.2
are available:https://github.com/ocaml/opam-repository/blob/master/packages/bwd/bwd.2.2.0/opam https://github.com/ocaml/opam-repository/blob/master/packages/yuujinchou/yuujinchou.5.0.2/opam
However
Opam-nix
is giving mebwd-2.1
andyuujinchou-4.0.2
.To Reproduce
Expected behavior I would expect the latest version from opam-repository to be provided.
Environment